Dynamic discovery of user equipment

Abstract

Example embodiments of the present disclosure relate to a solution for dynamically discovering a user equipment (UE), in particular a solution for dynamically discovering a UE utilizing features required in sidelink (SL) positioning. In an example method, a first terminal device obtains at least one criterion of a second terminal device for a sidelink positioning procedure performed by the first terminal device. The first terminal device then determines, during the discovery process, whether the second terminal device satisfies the at least one criterion. If the first terminal device determines that the second terminal device satisfies at least one criterion, the first terminal device determines that the second terminal device is to be discovered for a sidelink positioning procedure. In this manner, the performance of the discovery process may be improved and the traffic overhead in the discovery process may be reduced.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority and the benefits of international application number PCT / CN2023 / 111751 filed on August 8, 2023, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] The example embodiments of the present disclosure relate generally to the field of communications, and specifically to terminal devices, network entities, methods, apparatuses and computer-readable media for dynamically discovering user equipment (UE), especially for dynamically discovering UE by utilizing features required in side link (SL) positioning. Background Art

[0004] In communication technology, there is a continuous evolution to provide efficient and reliable solutions for utilizing wireless communication networks. Each new generation of technology has its own technical challenges and requires handling different situations and processes to connect and service devices connected to wireless networks. To meet the demand for increased wireless data traffic since the deployment of the fourth generation (4G) communication system, we strive to develop improved fifth generation (5G), pre-5G, 6G or higher level communication systems.

[0005] In recent years, fifth generation (5G) New Radio (NR) positioning has attracted much attention in the field of wireless communications. However, in high-density areas, detection is critical and very difficult, so further research is needed. Summary of the invention

[0006] In general, example embodiments of the present disclosure provide a solution for dynamically discovering a user equipment (UE), and in particular, a solution for dynamically discovering a UE using features required in sidelink (SL) positioning.

[0007] In a first aspect, a first terminal device is provided. The first terminal device includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the first terminal device to at least: obtain at least one criterion of a second terminal device for a sidelink positioning procedure performed by the first terminal device; during a discovery procedure, determine whether the second terminal device satisfies the at least one criterion; and based on determining that the second terminal device satisfies the at least one criterion, determine that the second terminal device is to be discovered for the sidelink positioning procedure.

[0008] In a second aspect, a second terminal device is provided. The second terminal device includes at least one processor and at least one memory storing instructions, which when executed by the at least one processor, causes the second terminal device to at least: determine information related to at least one criterion of the second terminal device for a sidelink positioning procedure performed by a first terminal device; and provide the information to the first terminal device.

[0009] In a third aspect, a first network entity is provided. The first network entity includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the first network entity to at least: determine at least one criterion of a second terminal device for a sidelink positioning procedure performed by the first terminal device; and send the at least one criterion to the first terminal device.

[0010] In a fourth aspect, a second network entity is provided. The second network entity includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the second network entity to at least: receive from the first network entity a request from at least one terminal device for at least one capability report of a sidelink positioning procedure performed by the first terminal device; and send the at least one capability report to the first network entity.

[0011] In a fifth aspect, a method is provided. The method includes: obtaining, at a first terminal device, at least one criterion of a second terminal device for a sidelink positioning procedure performed by the first terminal device; during a discovery procedure, determining whether the second terminal device satisfies the at least one criterion; and determining that the second terminal device is to be discovered for the sidelink positioning procedure based on determining that the second terminal device satisfies the at least one criterion.

[0012] In a sixth aspect, a method is provided. The method comprises: determining, at a second terminal device, information relating to at least one criterion of the second terminal device for a sidelink positioning procedure performed by a first terminal device; and providing the information to the first terminal device.

[0013] In a seventh aspect, a method is provided. The method comprises: determining, at a first network entity, at least one criterion for a second terminal device for a sidelink positioning procedure performed by a first terminal device; and sending the at least one criterion to the first terminal device.

[0014] In an eighth aspect, a method is provided. The method comprises: receiving, at a second network entity, from a first network entity, a request from at least one terminal device for at least one capability report of a sidelink positioning procedure performed by the first terminal device; and sending the at least one capability report to the first network entity.

[0015] In a ninth aspect, an apparatus is provided. The apparatus comprises: means for obtaining, at a first terminal device, at least one criterion of a second terminal device for a sidelink positioning procedure performed by the first terminal device; means for determining, during a discovery procedure, whether the second terminal device satisfies the at least one criterion; and means for determining that the second terminal device is to be discovered for the sidelink positioning procedure based on determining that the second terminal device satisfies the at least one criterion.

[0016] In a tenth aspect, an apparatus is provided. The apparatus comprises: means for determining, at a second terminal device, information about at least one criterion of the second terminal device for a sidelink positioning procedure performed by a first terminal device; and means for providing the information to the first terminal device.

[0017] In an eleventh aspect, an apparatus is provided. The apparatus comprises: means for determining, at a first network entity, at least one criterion for a second terminal device for a sidelink positioning procedure performed by a first terminal device; and means for sending the at least one criterion to the first terminal device.

[0018] In a twelfth aspect, an apparatus is provided. The apparatus comprises: means for receiving, at a second network entity, from a first network entity, a request for at least one capability report of at least one terminal device for a sidelink positioning procedure performed by the first terminal device; and means for sending the at least one capability report to the first network entity.

[0019] In a thirteenth aspect, a non-transitory computer-readable storage medium storing instructions is provided. When the instructions are executed on at least one processor, the at least one processor is caused to perform the method according to any one of the fifth to eighth aspects.

[0020] In a fourteenth aspect, a computer program is provided comprising instructions which, when executed by an apparatus, cause the apparatus to at least: obtain at least one criterion of a second terminal device for a side link positioning process performed by a first terminal device; determine, during a discovery process, whether the second terminal device satisfies at least one criterion; and determine that the second terminal device will be discovered for the side link positioning process based on determining that the second terminal device satisfies at least one criterion.

[0021] In a fifteenth aspect, a computer program is provided comprising instructions which, when executed by an apparatus, cause the apparatus to at least: determine information relating to at least one criterion of a second terminal device for a sidelink positioning procedure performed by a first terminal device; and provide information to the first terminal device.

[0022] In a sixteenth aspect, a computer program is provided comprising instructions which, when executed by an apparatus, cause the apparatus to at least: determine at least one criterion of a second terminal device for a sidelink positioning process performed by a first terminal device; and send the at least one criterion to the first terminal device.

[0023] In a seventeenth aspect, a computer program is provided comprising instructions which, when executed by an apparatus, cause the apparatus to at least: receive from a first network entity a request from at least one terminal device for at least one capability report of a side link positioning process performed by the first terminal device; and send at least one capability report to the first network entity.

[0024] In an eighteenth aspect, a first terminal device is provided. The first terminal device includes: an acquisition circuit system, the acquisition circuit system is configured to acquire at least one criterion of a second terminal device for a sidelink positioning process performed by the first terminal device; a determination circuit system, the determination circuit system is configured to determine whether the second terminal device meets the at least one criterion during the discovery process; and based on determining that the second terminal device meets the at least one criterion, the determination circuit system is configured to determine that the second terminal device will be discovered for the sidelink positioning process.

[0025] In a nineteenth aspect, a second terminal device is provided. The second terminal device includes: a determination circuit system configured to determine information related to at least one criterion of the second terminal device for a sidelink positioning procedure performed by the first terminal device; and a providing circuit system configured to provide information to the first terminal device.

[0026] In a twentieth aspect, a first network entity is provided. The first network entity comprises: a determining circuit system configured to determine at least one criterion of a second terminal device for a sidelink positioning procedure performed by a first terminal device; and a transmitting circuit system configured to transmit the at least one criterion to the first terminal device.

[0027] In a twenty-first aspect, a second network entity is provided. The second network entity comprises: a receiving circuit system configured to receive a request from a first network entity for at least one terminal device for at least one capability report of a sidelink positioning procedure performed by the first terminal device; and a transmitting circuit system configured to send the at least one capability report to the first network entity.

[0028] It should be understood that the invention summary is not intended to determine the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0030] Figure 1 illustrates an example of a network environment in which some example embodiments of the present disclosure may be implemented;

[0031] Figure 2 illustrates a signaling diagram illustrating an example communication process according to some example embodiments of the present disclosure;

[0032] Figure 3 illustrates a signaling diagram illustrating another example communication process according to some example embodiments of the present disclosure;

[0033] Figure 4 illustrates a signaling diagram illustrating another example communication process according to some example embodiments of the present disclosure;

[0034] Figure 5 A flowchart illustrating an example method implemented at a first terminal device according to some embodiments of the present disclosure is illustrated;

[0035] Figure 6 A flowchart illustrating an example method implemented at a second terminal device according to some embodiments of the present disclosure is illustrated;

[0036] Figure 7 illustrates a flow chart of an example method implemented at a first network entity according to some embodiments of the present disclosure;

[0037] Figure 8 illustrates a flow chart of another example method implemented at a second network entity according to some embodiments of the present disclosure;

[0038] Fig. 9 illustrates a simplified block diagram of a device suitable for implementing some example embodiments of the present disclosure; and

[0039] Fig.10 A block diagram illustrating an example of a computer readable medium according to some example embodiments of the present disclosure is illustrated.

[0040] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0041] The principle of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes and to help those skilled in the art understand and implement the present disclosure, and do not represent any limitation on the scope of the present disclosure. The present disclosure described herein can be implemented in various ways except for the way described below.

[0042] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0043] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not necessarily every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0044] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used to distinguish one element from another element. For example, without departing from the scope of the exemplary embodiments, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0045] The terms used herein are used to describe the purpose of a particular embodiment, and are not intended to limit the exemplary embodiments. Unless the context clearly states otherwise, as used herein, the singular forms "one", "one" and "described" also include plural forms. It will be further understood that the terms "include", "comprise", "have", "have" and / or "contain" specify the presence of the features, elements and / or components etc. when used herein, but do not exclude the presence or addition of one or more other features, elements, components and / or their combinations. As used herein, "at least one of the following items: a list of two or more elements>" and "at least one of the list of <two or more elements>" and similar wordings where the list of two or more elements is connected by "and" and "or", refer to at least one element in the element, or at least any two or more elements in the element, or at least all elements.

[0046] As used in this application, the term "circuitry" may refer to one, more, or all of the following:

[0047] (a) a pure hardware circuit implementation (such as an implementation of analog and / or digital circuitry only), and

[0048] (b) a combination of hardware circuitry and software such as (where applicable):

[0049] (i) a combination of analog and / or digital hardware circuits and software / firmware, and (ii) any portion of hardware processor(s) (including digital signal processors) with software, software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions, and

[0050] (c) multiple) hardware circuits and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) to operate, but the software may not be present when not required for operation.

[0051] The definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0052] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), Wireless Fidelity (WiFi), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to any suitable generation of communication protocol, including but not limited to the fourth generation (4G), 4.5G, the future fifth generation (5G), IEEE 802.11 communication protocol and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be future types of communication technologies and systems that can implement the present disclosure. It should not be considered that the scope of the present disclosure is limited to the above-mentioned system.

[0053] As used herein, the term "network device" refers to a node in a communication network, and a terminal device accesses the network via the node and receives services from it. A network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a WiFi device, a repeater, a low-power node (such as Femto, Pico, etc.), depending on the terminology and technology applied. In the following description, the terms "network device", "AP device", "AP" and "access point" may be used interchangeably.

[0054] The term "terminal device" refers to any terminal device that can perform wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), a station (STA) or a station device or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device (such as a digital camera), a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless client device (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a VR (virtual reality) device, an XR (extended reality) device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated processing chain), consumer electronic devices, devices operating on a commercial and / or industrial wireless network, etc. In the following description, the terms "station", "station device", "STA", "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0055] As mentioned above, in recent years, 5G NR positioning has attracted much attention in the field of wireless communications. The embodiments of the present disclosure relate to 5G NR positioning studied by the 3rd Generation Partnership Project (3GPP) in the Enhanced Positioning Work Item (WI) in Release 18. Specifically, it relates to reference UE discovery and selection for SL positioning purposes as defined in the "For Future Study" item agreed upon during the last RAN2#122 meeting, which states that "anchor UE selection is supported by information related to candidate anchor UEs. The meeting also pointed out which information will be determined statically / dynamically for future study. However, to date, there is still no runtime selection criteria for anchor / reference UE in the relevant 3GPP specifications. Since discovery is critical and very difficult in high-density areas, further study is needed.

[0056] Figure 1 An example communication system 100 in which some embodiments of the present disclosure may be implemented is illustrated. The communication system 100 is part of a communication network and includes a first terminal device 110-1, a second terminal device 110-2, a first network entity 120, and a second network entity 130. In the following, the first terminal device 110-1 may be referred to as a "target UE" that performs positioning of the second terminal device (i.e., performs discovery of the second terminal device), and the second terminal device 110-2 may be referred to as an "other terminal device" or an "anchor UE" that will be discovered by the first terminal device. The first network entity 120 may be a location management function (AMF) or a server UE. The second network entity 130 may be an access and mobility management function (AMF). The terminal devices 110-1 and 110-2 may be collectively referred to as "terminal device 110" or individually referred to as "terminal device 110". The first network entity 120 and the second network entity 130 may be deployed at a core network (CN), for example, deployed at a core network such as a UE. Figure 1 At the core network in the cloud 140 shown. Figure 1 2 shows that the first network entity 120 and the second network entity 130 are deployed in the same cloud, but they may be deployed in different clouds.

[0057] like Figure 1As shown, the first terminal device 110-1 communicates with the second terminal device 110-2, for example, via a PC5 interface. In other words, the first terminal device 110-1 and the second terminal device 110-2 can communicate with each other via a side link therebetween. The first terminal device 110-1 and the second terminal device 110-2 can each communicate with the second network entity 130. For example, the first terminal device 110-1 and the second terminal device 110-2 can each report their capabilities to the second network entity 130. The second network entity 130 can store the capabilities of the first terminal device 110-1 and the second terminal device 110-2, and the stored capabilities can be retrieved later by the first network entity 120 and / or the first terminal device 110-1 and / or the second terminal device 110-2.

[0058] In addition, the first network entity 120 may communicate with the second network entity 130. In the case where the second network entity 130 is an AMF, the first network entity 120 may retrieve information of the second terminal device 110-2 from the second network entity 130. The first terminal device 110-1 may also communicate with the first network entity 120. For example, the first terminal device 110-1 may receive a request from the first network entity 120 and may send a report to the first network entity 120.

[0059] The communications in the communication system 100 may conform to any suitable standard, including but not limited to Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM), etc. In addition, the communications may be performed according to any generation of communication protocols currently known or developed in the future. Examples of communication protocols include but are not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), 5.5G, 5G-Advanced networks, or sixth generation (6G) communication protocols.

[0060] It should be understood that Figure 1 The number of devices (including the terminal device 110, the first network entity 120 and the second network entity 130) and their connection relationships and types shown in the figure are for illustrative purposes only and do not impose any limitation. The communication system 100 may include any suitable number of devices adapted to implement the embodiments of the present disclosure.

[0061] In sidelink positioning, a target UE may be positioned by a nearby UE, for example, based on triangulation relative to multiple reference / positioning UEs. In order to meet the procedures defined in the sidelink positioning specifications in 3GPP TS23.273 and TS23.586, such a nearby UE must exhibit minimum requirements for its capabilities (e.g., sufficient bandwidth) and configuration and runtime / environmental parameters (referred to as "non-capability" parameters, such as line of sight (LOS), signal strength / synchronization, processing power, transmit (TX) power) to meet predefined positioning accuracy requirements and other quality of service (QoS) parameters, such as error confidence intervals.

[0062] However, this is a difficult problem, because the discovery message does not carry or only carries minimal information about the complex capability parameters of a given reference / positioning UE and its (usually time-varying) non-capability parameters. In other words, it is not possible to directly discover a reference / positioning / server UE that meets a specific (minimum) requirement, regardless of whether the specific (minimum) requirement is capability or non-capability.

[0063] Currently, these standards only define procedures for retrieving full capability reports, but these procedures must be performed from each single discovered UE. In addition to the fact that non-capability information such as runtime / environmental parameters cannot be retrieved, this obviously overhead-intensive approach will scale greatly when dozens or hundreds of candidate reference UEs participate in a dense network (such as a busy intersection or street), and will not be able to track topology changes even under very moderate mobility, causing the problem of information aging.

[0064] In view of the above discussion and analysis, some embodiments of the present disclosure provide a solution for dynamically discovering user equipment (UE), and in particular, a solution for dynamically discovering UE using features required in side link (SL) positioning. According to some embodiments of the present disclosure, a decision node (e.g., a target UE performing a discovery process, or an LMF or server UE) specifies a feature "ReqFeat" required for target UE discovery / selection (minimum bandwidth or a specific synchronization source) (generally, this can be either UE capabilities or non-capability information, such as runtime parameters, measurements, dynamic environment information, etc.).

[0065] During the discovery process, if the discovery UE (e.g., target UE) receives a Model A discovery notification / (multiple) Model B discovery response message indicating compliance with "ReqFeat" (e.g., within the "ReqFeat" range, or a value above / below the "ReqFeat" threshold) from other UEs, or a Model B discovery response message indicating that "ReqFeat" complies with the associated discovery request message, or a Model A discovery notification / (multiple) Model B discovery response message without a "ReqFeat" related indication (whose "ReqFeat" compliance has been verified by the AMF (LMF)), the discovery UE (e.g., target UE) accepts (e.g., from a reference / server UE) other UEs.

[0066] The decision node then performs the selection of a UE that meets the "ReqFeat" for positioning purposes (e.g., as a reference / server UE). Figures 2 to 4 Here, "ReqFeat" compliance means that the feature configuration of another UE (eg, anchor UE) meets the criteria on the required features specified by the decision node.

[0067] More specifically, some embodiments of the present disclosure provide a first terminal device that performs a discovery process. The first terminal device obtains at least one criterion of a second terminal device (e.g., an anchor UE) for a side link positioning process performed by the first terminal device (e.g., obtained from a first network entity, the first network entity may be a location management function (LMF) or a server UE, or the first terminal device may determine at least one criterion by itself). During the discovery process, the first terminal device determines whether the second terminal device meets at least one criterion. Based on determining that the second terminal device meets at least one criterion, the first terminal device determines that the second terminal device will be discovered for the side link positioning process. In this way, the performance of the discovery process can be improved. And the traffic overhead in the discovery can be reduced.

[0068] Figure 2 A signaling diagram illustrating an example communication process 200 according to some example embodiments of the present disclosure is illustrated. For ease of discussion, reference will be made to Figure 1 The communication process 200 may involve a first terminal device (eg, Figure 1 The terminal device 110-1 shown in FIG. 1 ), the second terminal device (eg, Figure 1 The terminal device 110-2 shown in FIG. 110-2), the first network entity (eg, Figure 1 , and a first network entity 120 and a second network entity (eg, Figure 1 In the following, the communication process 200 will refer to the second network entity 130 shown in FIG. Figure 1The first terminal device 110 - 1 , the second terminal device 110 - 2 , the first network entity 120 , and the second network entity 130 shown in FIG. 1 are described.

[0069] like Figure 2 As shown, at 215, the first terminal device 110-1 obtains at least one criterion of the second terminal device 110-2 for the side link positioning process performed by the first terminal device 110-1. The at least one criterion may be based on capability information of the terminal device (e.g., the second terminal device 110-2). Alternatively or additionally, the at least one criterion may be based on state information of the terminal device. Alternatively or additionally, the at least one criterion may be based on environmental information of the terminal device.

[0070] More specifically, the capability information may include at least one location service (LCS) and ranging capability. As another example, the capability information may include a role during a discovery process. Alternatively or additionally, the capability information may include at least one capability defined in the following: Long Term Evolution (LTE) Positioning Protocol (LPP), Ranging / Side Link Positioning Protocol (RSPP), or Side Link Positioning Protocol (SLPP).

[0071] The state information may include at least one runtime parameter. Additionally or alternatively, the state information may include bandwidth. In some other examples, the state information may include access type. In some other examples, the state information may include location information. As for environmental information, it may include serving radio information. Alternatively or additionally, the environmental information may include beam information, reference signal received power (RSRP) information, reference signal received quality (RSRQ) information, line of sight (LOS) information, non-line of sight (NLOS) information, etc. or any combination of the above options.

[0072] For example, at least one criterion 201 may be determined by the first network entity 120 for a sidelink positioning procedure performed by the first terminal device 110-1 for the second terminal device 110-2, and then sent (210) from the first network entity 120 to the first terminal device 110-1. On the other side of the communication, the first terminal device 110-1 may receive (212) at least one criterion 201 from the first network entity 120. In such a case, in order to receive (212) at least one criterion 201 from the first network entity 120, the first terminal device 110-1 may receive at least one criterion from the first network entity via a message related to a sidelink discovery procedure performed by the first terminal device 110-1 for the discovery procedure. The first network entity 120 may be a location management function (LMF) or a server UE. In the context of sidelink positioning, the server UE is a UE that provides method determination, helper data distribution and / or location calculation functions for a service based on sidelink positioning and ranging (SLPP). The server UE may interact with other UEs via PC5 as needed to determine ranging / SL positioning methods, distribute helper data, and calculate the location of the target UE.

[0073] Alternatively, in order to obtain the at least one criterion, the first terminal device 110-1 may determine the at least one criterion locally at the first terminal device 110-1. Specifically, if the sidelink positioning is triggered by the first terminal device 110-1, the at least one criterion may be determined locally at the first terminal device 110-1. In such a case, the first terminal device 110-1 does not need to receive the at least one criterion from the first network entity 120 to obtain the at least one criterion, that is, in such a case, operations involving receiving (212) and / or sending (210) may be omitted.

[0074] Now return to reference Figure 2 . At 225, the first terminal device 110-1 determines whether the second terminal device 110-2 satisfies at least one criterion during the discovery process. In order to determine whether the second terminal device 110-2 satisfies at least one criterion, for example, the first terminal device 110-1 may send a discovery request message indicating at least one criterion to the second terminal device 110-2. At the second terminal device 110-2, after receiving the discovery request message from the first terminal device 110-1, the second terminal device 110-2 may determine information related to at least one criterion of the second terminal device 110-2 for a side link positioning process performed by the first terminal device 110-1, and may provide (220) information 202 related to the at least one criterion to the first terminal device 110-1.

[0075] Here, the information 202 may include whether the second terminal device 110-2 meets at least one criterion. In this case, the second terminal device 110-2 may receive a discovery request message indicating at least one criterion from the first terminal device 110-1, and then determine whether the second terminal device 110-2 meets at least one criterion. If the second terminal device 110-2 determines that the second terminal device 110-2 meets at least one criterion, the second terminal device 110-2 may send a discovery response message to the first terminal device 110-1 in response to the discovery request message.

[0076] The discovery response message may not include the actual feature configuration of the feature specified in the at least one standard. Otherwise, if the second terminal device 110-2 determines that the second terminal device 110-2 does not meet the at least one standard, the second terminal device 110-2 may block the sending of the discovery response message in response to the discovery request message to the first terminal device 110-1. At the first terminal device 110-1, if a discovery response message in response to the discovery request message is received from the second terminal device 110-2, the first terminal device 110-1 may determine that the second terminal device 110-2 meets the at least one standard.

[0077] Alternatively, the second terminal device 110-2 may determine information related to at least one standard without receiving a discovery request message indicating at least one standard from the first terminal device 110-1. In this case, the information 202 related to at least one standard may include attribute information of the second terminal device 110-2 associated with the at least one standard. Then, the second terminal device 110-2 may send a message including the information to the first terminal device 110-1, for example, by notifying a plurality of terminal devices including the first terminal device 110-1 of the message in the form of a discovery notification message. At the first terminal device 110-1, when it receives a message including attribute information of the second terminal device 110-2 associated with at least one standard from the second terminal device 110-2, the first terminal device 110-1 may determine whether the second terminal device 110-2 satisfies the at least one standard based on the attribute information and the at least one standard.

[0078] Alternatively, the second terminal device 110-2 may determine whether the second terminal device meets at least one criterion with the aid of the second network entity 130. The second network entity is, for example, an access and mobility management function (AMF). In this case, the first terminal device 110-1 may send a request to the second network entity 130 for attribute information of the second terminal device 110-2 associated with at least one criterion. This may occur when a discovery response message or a discovery notification message that responds to the discovery request message does not include attribute information of the second terminal device 110-2 associated with at least one criterion.

[0079] The second network entity 130 may then send the attribute information to the first terminal device 110-1. The second network entity 130 may do so because the second network entity 130 may receive at least one of capability information, state information, or environment information of the first terminal device from the first terminal device 110-1 during the registration process of the first terminal device 110-1, and store such information locally. In addition, the second network entity 130 may receive at least one of capability information, state information, or environment information of the first terminal device from the second terminal device 110-2 during the registration process of the second terminal device 110-2, and store such information locally. Therefore, when the first terminal device 110-1 requests the attribute information of the second terminal device 110-2 from the second network entity 130, the second network entity may provide such information to the first terminal device 110-1. At the first terminal device 110-1, when it receives the attribute information of the second terminal device 110-2 from the second network entity 130, the first terminal device 110-1 may then determine whether the second terminal device 110-2 meets the at least one criterion based on the attribute information and the at least one criterion. This will refer to Figure 3 Describe in more detail.

[0080] Now return to reference Figure 2 At 225, if the first terminal device 110-1 determines that the second terminal device 110-2 meets the at least one criterion, then at 230, the first terminal device 110-1 determines that the second terminal device 110-2 is discovered for the sidelink positioning procedure. The first terminal device 110-1 may then send (235) information 203 indicating that at least one terminal device meets the at least one criterion to the first network entity 120. Here, the at least one terminal device may include the discovered second terminal device 110-2.

[0081] On the other side of the communication, the first network entity may receive (237) information 203 indicating that at least one terminal device meets at least one criterion. The first network entity 120 may not have a capability report of the at least one terminal device locally, so the first network entity 120 may send (240) a request 204 for at least one capability report of the at least one terminal device to the second network entity 130.

[0082] On the other side of the communication, the second network entity 130 may receive (242) a request 204 from at least one terminal device for at least one capability report of a sidelink positioning procedure performed by the first terminal device 110-1. The second network entity 130, having received and stored capability information (e.g., at least one of capability information, state information, or environment information) of each UE (including the first terminal device 110-1 and the second terminal device 110-2) during the registration procedure of the UE, may send (245) at least one capability report 205 to the first network entity 120. On the other side of the communication, the first network entity 120 may receive (247) at least one capability report 205 from the second network entity 130.

[0083] Additionally, the first terminal device 110-1 may send at least one of capability information, status information, or environmental information of the first terminal device 110-1 to the first network entity 120 during the sidelink positioning process or the discovery process. Similarly, the second terminal device 110-2 may send at least one of capability information, status information, or environmental information of the second terminal device 110-2 to the first network entity 120 during the sidelink positioning process or the discovery process for the sidelink positioning process. On the other side of the communication, the first network entity 120 may receive at least one of capability information, status information, or environmental information of at least one terminal device from at least one terminal device (e.g., including the first terminal device 110-1 and / or the second terminal device 110-2) during the sidelink positioning process or the discovery process of at least one terminal device for the sidelink positioning process.

[0084] In this way, the information exchange between the first terminal device 110-1 and the second terminal device 110-2 can be limited to a simple indication (by means of a discovery response message in response to a discovery request message) of simple attribute information (by means of a discovery notification message) that the second terminal device 110-2 meets the standard or the required characteristics specified in the standard, and the information exchange between the first terminal device 110-1 and the first network entity 120 can be limited to a list of UEs that meet the standard (more precisely, a list of UE IDs). Therefore, the information exchange between the first terminal device 110-1 and the second terminal device 110-2 and between the first terminal device 110-1 and the first network entity 120 does not involve the sending of large data (e.g., a complete UE capability report). Therefore, the traffic overhead in discovery can be reduced and the performance of the discovery process can be improved.

[0085] Here, some examples of the present disclosure are generally referred to Figure 2 A high-level signaling diagram of is described. In the following, reference is made to Figure 3-Figure 4 Some other examples of the disclosure are described.

[0086] Figure 3 FIG. 3 illustrates a signaling diagram of another example communication process 300 according to some example embodiments of the present disclosure. Specifically, Figure 3 shows how to discover terminal devices (e.g. Figure 3 Detailed example process of the anchor UE 304) shown in FIG.

[0087] For the sake of discussion, reference will be made to Figure 1 300. The communication process 300 may involve a target UE 302, an anchor UE 304, a LMF 306, and an AMF 308. The target UE 302 is such as Figure 1 In the example of the first terminal device 110-1 shown in FIG. 1 , the anchor UE 304 is as follows Figure 1 In the example of the second terminal device 110-2 shown in FIG. Figure 1 The example of the first network entity 120 shown in FIG. 1 and the AMF 308 is as shown in FIG. Figure 1 The example of the second network entity 130 shown in FIG. The illustration of the anchor UE 304, the target UE 302, the AMF 308, and the LMF 306 here is for illustration purposes only; the present disclosure is not limited thereto. For example, the functions and operations performed by the LMF 306 here can also be implemented by the server UE. Figure 3 In the example shown in , it is assumed that the LMF 306 triggers the SL process and the LMF 306 is a control node (decision node).

[0088] In such Figure 3 In the example shown, at 310, the anchor UE 304 reports its 5GMM capabilities to the AMF 308 upon registration. At 315, the target UE 302 reports its 5GMM capabilities to the AMF 308 upon registration. At the other end of the communication, at 320, the AMF 308 stores the capabilities of the anchor UE 304 and the target UE 302 at the AMF 308.

[0089] At 325, the AMF 308 sends a "determineLocation" request to the LMF 306 for a discovery procedure by, for example, the target UE 302. At 330, the LMF 306 determines that the discovery procedure is performed by the target UE 302 via sidelink communication.

[0090] At 335, based on the knowledge of the anchor / reference UE (e.g., the location of the positioning UE, the QoS guarantee of the positioning server UE, etc.), the LMF 306 transmits a "Request Anchor UE" message ( / request) to the target UE 302 for anchor UE discovery. The "Request Anchor UE" message may include one or more required criteria. For example, the "Request Anchor UE" message may include one or more criteria related to the features required by the anchor UE that the target UE 302 is looking for (hereinafter referred to as "reqFeature" information element). For example, the criteria may be related to bandwidth (BW), and the bandwidth is required to be greater than a minimum value, i.e., "BW_min" here.

[0091] In one example, "ReqFeature" may apply to UE capabilities defined as LCS and ranging capabilities included in 5G Mobility Management (5GMM) capabilities during registration of an anchor UE (capabilities of the anchor UE that the target UE 302 is looking for). Alternatively or additionally, "ReqFeature" may apply to UE capabilities defined as roles that the (anchor) UE may express during discovery, including anchor / reference UE types (target / positioning / positioning server / assistance, etc.). Alternatively or additionally, "ReqFeature" may apply to UE capabilities defined in LPP according to 3GPP TS 37.355, or UE capabilities defined in RSPP / SLPP according to 3GPP TS33.355. LMF 306 is directly or indirectly aware of these capabilities and UE features.

[0092] As described above, the anchor UE 304 and the target UE 302 report their 5GMM capabilities to the AMF 308 when registering. When a location (positioning) session is initiated, in the case where the LMF 306 is a control node (i.e., a decision node), the AMF 308 transmits the relevant capabilities to the LMF 306. During the positioning session, the LMF 306 derives the minimum capabilities required for different types of anchor (reference / positioning) UEs from the required positioning QoS, and the minimum capabilities come from the LPP or the forwarded RSPP information.

[0093] Then, the discovery process in Model B or Model A begins. Figure 3In the model B discovery shown in Example 1 in , a "reqFeature" ("required feature") requirement for "BW_min" is dynamically added to the SLPP meta field of the discovery request message. If the anchor UE 304 meets the requirement, the anchor UE 304 will then respond with a standard discovery response. The discovery response does not need to indicate the actual BW configuration (but it may be preferable to specify the actual parameters for the benefit of the target UE / LMF). The target UE 302 then accepts the message and considers the associated UE (here, the anchor UE 304) to be discovered. Specifically, at 340, the target UE 302 sends a discovery request to the anchor UE 304. The discovery request may include one or more criteria (e.g., BW>BW_min), one or more of which are the same as the "Request Anchor UE" message at 335. In other words, the discovery request at 340 can "inherit" the criteria in the "Request Anchor UE" message received from the LMF 306 (i.e., the decision node). At 345, the anchor UE 304 determines whether its bandwidth is greater than the BW_min specified in the received discovery request. At 345, if the anchor UE 304 determines that its bandwidth is greater than the BW_min, the anchor UE 304 responds to the target UE 302, and at 350, the anchor UE 304 then sends a discovery response to the target UE 302. The discovery response may not include the actual bandwidth configuration of the anchor UE 304. At 355, the target UE 302 accepts the discovery response and considers the anchor UE 304 to be discovered.

[0094] exist Figure 3 In the model A discovery shown in Example 2 of FIG, the anchor UE 304 announces the selected key requirements, such as bandwidth, via the SLPP meta field. If the announced value meets its bandwidth requirements, the receiving target UE (here, the target UE 302) regards the anchor UE 304 as being discovered. Specifically, at 360, the anchor UE 304 announces a discovery notification to the target UE 302. The discovery notification includes the exact value of the bandwidth of the anchor UE 304. Then, upon receiving the exact value of the bandwidth of the anchor UE 304 included in the discovery notification received from the anchor UE 304, the target UE 302 determines at 365 whether the bandwidth of the anchor UE 304 is greater than BW_min. If BW>BW_min according to the requirement, the target UE 302 will accept the anchor UE 304 as the anchor UE for the target UE 302.

[0095] Similarly, in Figure 3In the model B discovery shown in Example 1, as at 340, in the case where the minimum requirement is not actually specified in the discovery request message, the target UE 302 can accept the model B discovery response when evaluating the characteristics indicated therein. Specifically, in this case, at 340, the target UE 302 sends a discovery request to the anchor UE 304. The discovery request does not include one or more criteria (e.g., BW>BW_min). In other words, the target UE 302 sends a discovery request without any criteria to the anchor UE 304, but retains the criteria itself. In this case, the anchor UE 304 cannot determine whether it meets the criteria because it does not know the criteria. Therefore, at 350, the anchor UE 304 sends a discovery response to the target UE 302, and the discovery response includes the actual bandwidth configuration of the anchor UE 304. Therefore, the target UE 302 can use the received actual bandwidth configuration of the anchor UE 304 to determine whether the bandwidth of the anchor UE 304 is greater than BW_min. If so, the target UE 302 regards the anchor UE 304 as being discovered.

[0096] The target UE 302 then reports a list of candidate anchors that meet the minimum bandwidth requirement to the LMF 306. The LMF 306 may then retrieve additional information (e.g., a complete capability report) about each discovered UE from the AMF 308 to avoid lengthy communications with individual UEs (either directly via the gNB or indirectly via the target UE). For example, at 370, the target UE 302 may report the discovered UE (e.g., in this case, the anchor UE 304) to the LMF 306. Upon receiving the discovered UE, the LMF 306 may obtain additional features of the reported discovered UE from the AMF 308 at 375. At 380, the target UE 302 may select an anchor UE and report it to the LMF 306.

[0097] In a specific scenario, the LMF 306 does not specify any minimum requirements for the target UE 302, and the discovery proceeds as usual, and the LMF 306 performs candidate anchor UE filtering based only on the report from the AMF 308. Specifically, in this case, at 335, the LMF 306 delivers a "Request Anchor UE" message without a standard to the target UE 302 for anchor UE discovery. Then, in the model B discovery, the anchor UE 302 can respond to the target UE 302 without the actual configuration of any specific features, because it does not know the standard, more precisely, the LMF 306 does not indicate the standard to the target UE 302. In addition, in the model A discovery, the anchor UE 304 can announce the selected key requirements via the SLPP meta field. Therefore, at the target UE 302, it obtains a list of anchor UEs that respond to it or announce it. Then, the target UE 302 can forward ( / transmit) the list to the LMF 306. Therefore, at the LMF 306, it may use the list from the AMF 308 to retrieve UE information (eg, UE features or UE capabilities) and filter candidate anchor UEs corresponding to the list.

[0098] In this way, SL positioning reference / positioning / server UEs with predefined minimum capability requirements can be discovered, so the discovery process can be improved using dynamic information.

[0099] Figure 4 A signaling diagram of another example communication process 400 according to some example embodiments of the present disclosure is illustrated. Specifically, Figure 4 shows how to discover terminal devices (e.g. Figure 4 Detailed example process of the anchor UE 404) shown in FIG.

[0100] For the sake of discussion, reference will be made to Figure 1 and Figure 3 4. The communication process 400 may involve a target UE 402, an anchor UE 404, a LMF 406, and an AMF 408. The target UE 402 may be Figure 1 In the example of the first terminal device 110-1 shown in FIG. 1 , the anchor UE 404 is as follows Figure 1 In the example of the second terminal device 110-2 shown in FIG. 1 , LMF 406 is as follows Figure 1 The example of the first network entity 120 shown in FIG. 1 and the AMF 408 is as shown in FIG. Figure 1 An example of the second network entity 130 is shown in FIG. Figure 4 In the example, the target UE 402, the anchor UE 404, the LMF 406 and the AMF 408 are connected to the Figure 3The target UE 302, anchor UE 304, LMF 306, and AMF 308 in FIG. 306 are similar. The illustrations of anchor UE 304, target UE 302, AMF 308, and LMF 306 are for illustration purposes only; the present disclosure is not limited thereto. For example, the functions and operations performed by LMF 306 here may also be implemented by a server UE. Figure 4 In the example shown in FIG. 4 , it is assumed that the target UE 402 triggers the SL process and the target UE 402 is a control node (decision node). Figure 4 In the example shown in , the target UE 402 sets the minimum requirements to be met by the anchor UE (here, the anchor UE 404) in terms of positioning QoS requirements, and then performs its discovery and selection.

[0101] In such Figure 4 In the example shown in , at 410, similar to Figure 3 At 310 shown in FIG, the anchor UE 404 reports its 5GMM capabilities to the AMF 408 upon registration. At 415, similar to Figure 3 At 315 shown in FIG. , the target UE 402 reports its 5GMM capabilities to the AMF 408 when registering. At the other end of the communication, at 420, similar to Figure 3 At 320 shown in , the AMF 408 stores the capabilities of the anchor UE 404 and the target UE 402 at the AMF 408.

[0102] At 425, similar to Figure 3 At 330 shown in , the target UE 402, rather than the LMF 406, determines the discovery process performed by the target UE 402 itself via the sidelink communication. At 430, the target UE 402 determines the minimum QoS enabling capabilities. For example, the target UE 402 may determine that the minimum QoS enabling capabilities should meet one or more requirement criteria. For example, the criteria may be set by the target UE 402 for the features required by the anchor UE that the target UE 302 is looking for (i.e., "reqFeature"). As a specific example, the criteria may be about bandwidth (BW), and the bandwidth is required to be greater than a minimum value, i.e., "BW_min" here. The description of "ReqFeature" is similar to that of reference 1. Figure 3 , and therefore, for simplicity, the description is omitted here.

[0103] Then, at 435, as shown in Example 3, the anchor UE sends a Model B discovery response / Model A discovery notification to the target UE 402. However, the Model B discovery response / Model A discovery notification does not contain any specific indications about the required characteristics (e.g., a blank or "empty" information element, or other "not applicable" or irrelevant information is specified). For example, for the criteria set by the target UE 402 at 430, 435 (here BW>BW_min), the discovery response in the Model B discovery or the discovery notification in the Model A discovery does not include a specific indication or information of the bandwidth characteristics of the anchor UE 404, that is, in other words, the discovery response in the Model B discovery or the discovery notification in the Model A discovery does not contain the actual BW configuration, such as the actual BW value of the anchor UE 404.

[0104] Based on the Model B Discovery Response / Model A Discovery Notification received at 435, the target UE 402 may obtain information related to the anchor UE 404, for example, the target UE 402 may obtain an identifier of the anchor UE 404. Then, at 440, the target UE 402 performs checks at the AMF 408 related to the anchor UE (here, the anchor UE 404) and the specific features or capabilities required. For example, Figure 4 As shown in FIG. 4 , at 440, the target UE 402 sends a “getFeature” request to the AMF 408 to retrieve a specific feature or capability required by the anchor UE 404. As a specific feature or capability required by the anchor UE 404, Figure 4 A specific synchronization reference source "SyncRef" is shown as an example.

[0105] As described above, the anchor UE 404 and the target UE 402 report their 5GMM capabilities to the AMF 408 when registering, and the AMF 408 stores such capabilities locally, for example, at a local database. Therefore, in response to the "getFeature" request, the AMF 408 sends a "provideFeature" response to the target UE 402, thereby providing the target UE 402 with the configuration of the requested anchor UE 404 feature (here "SyncRef").

[0106] Next, after receiving the configuration of the feature (here "SyncRef") requested by the anchor UE 404 to the target UE 402, the target UE 402 may determine whether the requested feature meets a certain criterion. For example, the target UE 402 may determine whether the requested feature "SyncRef" is equal to, greater than, or less than a threshold. If the requested feature meets the certain criterion, the target UE 402 may accept the anchor UE 404, and regard the anchor UE 404 as discovered, and add the anchor UE 404 to a candidate anchor UE list for the target UE 402.

[0107] In such Figure 4 In the example shown in , SL positioning reference / positioning / server UEs with predefined minimum capability requirements can be discovered, so the discovery process can be improved using dynamic information.

[0108] According to some example embodiments of the present disclosure, 3GPP TS 23.586 may be enhanced as follows:

[0109]

[0110]

[0111] Figure 5 A flowchart of an exemplary method 500 implemented at a first terminal device according to some other embodiments of the present disclosure is illustrated. For ease of discussion, reference will be made to Figure 1-Figure 2 The method 500 is described from the perspective of the first terminal device 110 - 1 .

[0112] like Figure 5 As shown, at block 510, the first terminal device 110-1 obtains the second terminal device (eg, Figure 1 and Figure 2 The second terminal device 110-2 shown in FIG. 110-2) determines at least one criterion of the side link positioning process performed by the first terminal device (e.g., Figure 2 At least one criterion 201 shown in FIG. 5 ). At block 520, the first terminal device 110-1 determines whether the second terminal device satisfies the at least one criterion during the discovery process. At block 530, based on determining that the second terminal device satisfies the at least one criterion, the first terminal device 110-1 determines that the second terminal device is to be discovered for the sidelink positioning process.

[0113] In some example embodiments, in order to obtain at least one criterion, the first terminal device 110-1 may obtain from the first network entity (eg, Figure 1 and Figure 2 The first network entity 120 shown in the figure receives at least one criterion (eg, Figure 2At least one criterion 201 shown). Alternatively, the first terminal device 110-1 may determine the at least one criterion locally at the first terminal device 110-1. In this case, in order to receive the at least one criterion, the first terminal device 110-1 may receive the at least one criterion from the first network entity via a message related to the sidelink discovery process for the first terminal device to perform the discovery process, so that the first terminal device performs the discovery process. Alternatively, if the sidelink positioning is triggered by the first terminal device 110-1, the at least one criterion may be determined locally at the first terminal device 110-1.

[0114] In some example embodiments, in order to determine whether the second terminal device meets at least one criterion, the first terminal device 110-1 may send a discovery request message indicating the at least one criterion to the second terminal device, and determine that the second terminal device meets the at least one criterion based on receiving a discovery response message in response to the discovery request message from the second terminal device. Here, the discovery response message may not include an actual feature configuration of a feature specified in the at least one criterion.

[0115] Alternatively, in some example embodiments, in order to determine whether the second terminal device satisfies at least one criterion, the first terminal device 110-1 may receive a first message from the second terminal device indicating attribute information of the second terminal device associated with the at least one criterion, and determine whether the second terminal device satisfies the at least one criterion based on the attribute information and the at least one criterion.

[0116] Alternatively, in some example embodiments, in order to determine whether the second terminal device meets at least one criterion, the first terminal device 110-1 may, based on receiving the second message from the second terminal device, send a second message to the second network entity (eg, Figure 1 and Figure 2 The first terminal device 110-1 may then receive the attribute information of the second terminal device from the second network entity. The first terminal device 110-1 may then determine, based on the attribute information and the at least one criterion, whether the second terminal device satisfies the at least one criterion. In this case, at least one of the first message or the second message may be a discovery notification message. Alternatively, at least one of the first message or the second message may be a discovery response message in response to the discovery request message.

[0117] In some example embodiments, the first terminal device 110-1 may further send information indicating that the at least one terminal device meets the at least one criterion to the first network entity. Here, the at least one terminal device may include a second terminal device.

[0118] In some example embodiments, the first terminal device 110-1 may send at least one of capability information, state information, or environment information of the first terminal device 110-1 to the second network entity during a registration process of the first terminal device 110-1. Alternatively or additionally, the first terminal device 110-1 may send at least one of capability information, state information, or environment information of the first terminal device 110-1 to the first network entity during a sidelink positioning process or a discovery process.

[0119] In some example embodiments, at least one criterion may be based on capability information of a terminal device (e.g., a second terminal device). Alternatively or additionally, at least one criterion may be based on state information of a terminal device. Alternatively or additionally, at least one criterion may be based on environmental information of a terminal device. For example, the capability information may include at least one location service (LCS) and ranging capability. Alternatively or additionally, the capability information may include a role during a discovery process. Alternatively or additionally, the capability information may include at least one capability defined in at least one of a Long Term Evolution (LTE) Positioning Protocol (LPP), a Ranging / Side Link Positioning Protocol (RSPP), or a Side Link Positioning Protocol (SLPP). The state information may include at least one runtime parameter. Alternatively or additionally, the state information may include bandwidth. Alternatively or additionally, the state information may include an access type. Alternatively or additionally, the state information may include location information. Environmental information may include serving radio information. Alternatively or additionally, the environmental information may include beam information. Alternatively or additionally, the environmental information may include reference signal received power (RSRP) information. Alternatively or additionally, the environmental information may include reference signal received quality (RSRQ) information.Alternatively or additionally, the environmental information may include line-of-sight (LOS) information.Alternatively or additionally, the environmental information may include non-line-of-sight (NLOS) information.

[0120] In some example embodiments, the first terminal device may be a target user equipment (UE), the second terminal device may be an anchor UE, the first network entity may be a location management function (LMF) or a server user equipment (UE), and the second network entity may be an access and mobility management function (AMF).

[0121] Figure 6 FIG. 6 is a flowchart of an exemplary method 600 implemented at a second terminal device according to some other embodiments of the present disclosure. Figure 1-Figure 2 The method 600 is described from the perspective of the second terminal device 110 - 2 .

[0122] like Figure 6As shown in FIG. 6 , at block 610, the second terminal device 110-2 determines that the second terminal device 110-2 has a request for a request received by the first terminal device (eg, Figure 1 and Figure 2 At least one standard (e.g., Figure 2 At block 620, the second terminal device 110-2 provides information (eg, information 202 related to at least one standard) to the first terminal device.

[0123] In some example embodiments, the information may include whether the second terminal device 110 - 2 satisfies at least one criterion.

[0124] In some example embodiments, to determine the information, second terminal device 110 - 2 may receive a discovery request message indicating at least one criterion from the first terminal device, and determine whether second terminal device 110 - 2 satisfies the at least one criterion.

[0125] In some example embodiments, if the second terminal device 110-2 determines that it meets at least one criterion to provide information to the first terminal device, the second terminal device 110-2 may send a discovery response message to the first terminal device in response to the discovery request message. In some example embodiments, the discovery response message may not include an actual feature configuration of the feature specified in the at least one criterion.

[0126] Alternatively, in some example embodiments, if the second terminal device 110 - 2 determines that it does not meet at least one criterion, the second terminal device 110 - 2 may refrain from sending a discovery response message in response to the discovery request message to the first terminal device.

[0127] In some example embodiments, the information may include attribute information of the second terminal device associated with at least one standard. In this case, in order to provide the information to the first terminal device, the second terminal device 110-2 may send a message including the information to the first terminal device. Here, the message may be a discovery notification message. Alternatively, the message may be a discovery response message in response to the discovery request message.

[0128] In some example embodiments, the second terminal device 110-2 may register with the second network entity (eg, Figure 1 and Figure 2The second network entity 130 shown in the figure sends at least one of the capability information, state information or environment information of the second terminal device 110-2. Alternatively or additionally, the second terminal device 110-2 may send at least one of the capability information, state information or environment information of the second terminal device 110-2 to the first network entity (e.g., as shown in the figure) during the sidelink positioning process or the discovery process for the sidelink positioning process. Figure 1 and Figure 2 The first network entity 120) shown in the figure sends at least one of capability information, state information or environment information of the second terminal device 110-2.

[0129] In some example embodiments, the first terminal device may be a target user equipment (UE), the second terminal device may be an anchor UE, the first network entity may be a location management function (LMF), or a server user equipment (UE), and the second network entity may be an access and mobility management function (AMF).

[0130] Figure 7 A flowchart of an example method 700 implemented at a first network entity according to some other embodiments of the present disclosure is illustrated. For ease of discussion, reference will be made to Figure 1-Figure 2 The method 700 is described from the perspective of the first network entity 120 .

[0131] like Figure 7 As shown in FIG. 7 , at block 710, the first network entity 120 determines a second terminal device (eg, Figure 1 and Figure 2 The second terminal device 110-2 shown in FIG. 1 is used by the first terminal device (eg, Figure 1 and Figure 2 At block 720, the first network entity 120 sets at least one criterion (e.g., Figure 2 At least one standard 201) shown is sent to the first terminal device.

[0132] In some example embodiments, the at least one criterion may be determined by the first network entity. The first network entity 120 may also receive information from the first terminal device indicating that the at least one terminal device satisfies the at least one criterion (e.g., Figure 2 After receiving the information 203, the first network entity 120 may send a message to the second network entity (eg, Figure 1 and Figure 2 The second network entity 130 shown in FIG. 1 sends a request for at least one capability report of at least one terminal device (eg, Figure 2As shown in FIG. 2 , a request 204 for at least one capability report of at least one terminal device is sent, and then the first network entity 120 may receive at least one capability report from the second network entity (e.g., Figure 2 At least one capability report 205 shown in ).

[0133] In some example embodiments, the first network entity 120 may receive at least one of capability information, status information, or environmental information of at least one terminal device from at least one terminal device including the first terminal device during a sidelink positioning procedure or a discovery procedure of at least one terminal device for a sidelink positioning procedure.

[0134] In some example embodiments, the first network entity may be a Location Management Function (LMF) or a server User Equipment (UE), and the second network entity may be an Access and Mobility Management Function (AMF).

[0135] Figure 8 A flowchart of an example method 800 implemented at a second network entity according to some other embodiments of the present disclosure is illustrated. For ease of discussion, reference will be made to Figure 1-Figure 2 The method 800 is described from the perspective of the second network entity 130 .

[0136] like Figure 8 As shown in FIG. 8 , at block 810, the second network entity 130 receives a request from the first network entity (eg, Figure 1 and Figure 2 The first network entity 120 shown in FIG. 1 receives a request for at least one terminal device for a first terminal device (eg, Figure 1 and Figure 2 At block 820, the second network entity 130 sends at least one capability report (e.g., at least one capability report 205) to the first network entity.

[0137] In some example embodiments, the second network entity 130 may receive from the first terminal device a request for at least one terminal device attribute information for sidelink positioning of the first terminal device, and send the attribute information (e.g., information 202 related to at least one standard) to the first terminal device.

[0138] In some example embodiments, the second network entity 130 may receive at least one of capability information, state information or environment information of the second terminal device from the second terminal device during a registration process of the second terminal device.

[0139] In some example embodiments, the first network entity may be a Location Management Function (LMF) or a server User Equipment (UE), and the second network entity may be an Access and Mobility Management Function (AMF).

[0140] In some embodiments, a device capable of performing method 500 (e.g., Figure 1 and Figure 2 The first terminal device 110-1 shown in FIG. 5 , or a part of the first terminal device 110-1) may include components for executing corresponding steps of the method 500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0141] In some example embodiments, the apparatus comprises: Figure 1 and Figure 2 The first terminal device 110-1 shown in FIG. 1 obtains the second terminal device (for example, Figure 1 and Figure 2 The second terminal device 110-2 shown in the figure) has at least one criterion for a side link positioning process performed by the first terminal device; a component for determining whether the second terminal device satisfies the at least one criterion during the discovery process; and a component for determining that the second terminal device will be discovered for the side link positioning process based on determining that the second terminal device satisfies the at least one criterion.

[0142] In some example embodiments, the means for obtaining may include means for obtaining from a first network entity (e.g., Figure 1 and Figure 2 The first network entity 120 shown in FIG. 1 receives at least one criterion (eg, Figure 2 201). Alternatively, the means for obtaining may include means for determining at least one criterion locally at the first terminal device. In this case, the means for receiving at least one criterion may include means for receiving at least one criterion from the first network entity via a message related to a sidelink discovery procedure of the first terminal device for performing the discovery procedure. Alternatively, if the sidelink positioning is triggered by the first terminal device 110-1, the at least one criterion may be determined locally at the first terminal device 110-1.

[0143] In some example embodiments, the means for determining whether the second terminal device satisfies at least one criterion may include: means for sending a discovery request message indicating the at least one criterion to the second terminal device, and determining that the second terminal device satisfies the at least one criterion based on receiving a discovery response message from the second terminal device in response to the discovery request message. Here, the discovery response message may not include an actual feature configuration of a feature specified in the at least one criterion.

[0144] Alternatively, in some example embodiments, the component for determining whether the second terminal device satisfies at least one criterion may include: a component for receiving a first message from the second terminal device indicating attribute information that the second terminal device is associated with at least one criterion, and a component for determining whether the second terminal device satisfies at least one criterion based on the attribute information and the at least one criterion.

[0145] Alternatively, in some example embodiments, the means for determining whether the second terminal device satisfies at least one criterion may be based on receiving a second message from the second terminal device for sending a second message to the second network entity (e.g. Figure 1 and Figure 2 The first message or the second message may be a discovery notification message. Alternatively, at least one of the first message or the second message may be a discovery response message that responds to the discovery request message.

[0146] In some example embodiments, the apparatus may further comprise means for sending information indicating that the at least one terminal device satisfies the at least one criterion to the first network entity.Herein, the at least one terminal device may comprise a second terminal device.

[0147] In some example embodiments, the apparatus may further include a component for sending at least one of capability information, state information, or environment information of the first terminal device to the second network entity during a registration process of the first terminal device. Alternatively or additionally, the apparatus may further include a component for sending at least one of capability information, state information, or environment information of the first terminal device to the first network entity during a sidelink positioning process or a discovery process.

[0148] In some example embodiments, at least one criterion may be based on capability information of a terminal device (e.g., a second terminal device). Alternatively or additionally, at least one criterion may be based on state information of a terminal device. Alternatively or additionally, at least one criterion may be based on environmental information of a terminal device. For example, the capability information may include at least one location service (LCS) and ranging capability. Alternatively or additionally, the capability information may include a role during a discovery process. Alternatively or additionally, the capability information may include at least one capability defined in at least one of a Long Term Evolution (LTE) Positioning Protocol (LPP), a Ranging / Side Link Positioning Protocol (RSPP), or a Side Link Positioning Protocol (SLPP). The state information may include at least one runtime parameter. Alternatively or additionally, the state information may include bandwidth. Alternatively or additionally, the state information may include an access type. Alternatively or additionally, the state information may include location information. Environmental information may include serving radio information. Alternatively or additionally, the environmental information may include beam information. Alternatively or additionally, the environmental information may include reference signal received power (RSRP) information. Alternatively or additionally, the environmental information may include reference signal received quality (RSRQ) information.Alternatively or additionally, the environmental information may include line-of-sight (LOS) information.Alternatively or additionally, the environmental information may include non-line-of-sight (NLOS) information.

[0149] In some example embodiments, the first terminal device may be a target user equipment (UE), the second terminal device may be an anchor UE, the first network entity may be a location management function (LMF), or a server user equipment (UE), and the second network entity may be an access and mobility management function (AMF).

[0150] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 500. In some embodiments, the means comprises at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to perform.

[0151] In some embodiments, a device capable of performing method 600 (e.g., Figure 1 and Figure 2 The first terminal device 110-2 shown in the figure, or a part of the first terminal device 110-2) may include components for executing the corresponding steps of the method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0152] In some example embodiments, the apparatus includes: Figure 1 and 2The second terminal device 110-2 shown in FIG. 1 determines that the second terminal device has a connection with the first terminal device (eg, Figure 1 and Figure 2 1) for performing a sidelink positioning procedure performed by the first terminal device 110-1 as shown in FIG; and a component for providing information to the first terminal device (e.g., Figure 2 A component of information 202 related to at least one standard shown in FIG.

[0153] In some example embodiments, the information may include whether the second terminal device satisfies at least one criterion.

[0154] In some example embodiments, means for determining information related to at least one criterion may include means for receiving a discovery request message indicating at least one criterion from a first terminal device, and means for determining whether the second terminal device satisfies the at least one criterion.

[0155] In some example embodiments, the means for providing may include: determining that the second terminal device satisfies the at least one criterion based on the means for determining whether the second terminal device satisfies the at least one criterion, means for sending a discovery response message to the first terminal device in response to the discovery request message. In some example embodiments, the discovery response message may not include an actual feature configuration of a feature specified in the at least one criterion.

[0156] Alternatively, in some example embodiments, the component for providing may include: determining that the second terminal device does not satisfy at least one criterion based on the component for determining whether the second terminal device satisfies at least one criterion, and preventing a discovery response message from being sent to the first terminal device in response to the discovery request message.

[0157] In some example embodiments, the information may include: attribute information of the second terminal device associated with at least one standard. In this case, the means for providing may include: means for sending a message including the information to the first terminal device. Here, the message may be a discovery notification message. Alternatively, the message may be a discovery response message in response to the discovery request message.

[0158] In some example embodiments, the apparatus may further include: a method for sending a second network entity (e.g., Figure 1 and Figure 2 The apparatus may further include: a component for sending at least one of capability information, state information or environment information of the second terminal device to the first network entity (e.g., the second network entity 130 shown in the figure). Alternatively or additionally, the apparatus may also include: a component for sending at least one of capability information, state information or environment information of the second terminal device to the first network entity (e.g., the second network entity 130 shown in the figure). Figure 1 and Figure 2 The first network entity 120 shown in the figure sends at least one of the capability information, state information or environment information of the second terminal device.

[0159] In some example embodiments, the first terminal device may be a target user equipment (UE), the second terminal device may be an anchor UE, the first network entity may be a location management function (LMF), or a server user equipment (UE), and the second network entity may be an access and mobility management function (AMF).

[0160] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 600. In some embodiments, the means comprises at least one processor and at least one memory with computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform.

[0161] In some embodiments, a device capable of performing method 700 (e.g., Figure 1 and Figure 2 The first network entity 120 shown in FIG. 7 , or a portion of the first network entity 120 , may include components for executing corresponding steps of the method 700 . The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0162] In some example embodiments, the apparatus comprises: Figure 1 and Figure 2 At the first network entity 120 shown in FIG. 1 , a second terminal device (eg, Figure 1 and Figure 2 The second terminal device 110-2 shown in FIG. 1 is used by the first terminal device (eg, Figure 1 and Figure 2 A component for determining at least one standard of a side link positioning process performed by the first terminal device 110-1) shown in FIG; and a component for sending at least one standard to the first terminal device.

[0163] In some example embodiments, the at least one criterion may be determined by the first network entity. The apparatus may also include: receiving information from the first terminal device indicating that the at least one terminal device satisfies the at least one criterion (e.g., Figure 2 As shown in FIG. 2 , the device may further include: a component for providing information 203 indicating that at least one terminal device satisfies at least one criterion. Figure 1 and Figure 2 The second network entity 130 shown in FIG. 1 sends a request for at least one capability report of at least one terminal device (eg, as shown in FIG. 1 ). Figure 2204) for at least one capability report of at least one terminal device, and means for receiving at least one capability report from a second network entity (e.g., Figure 2 Components of at least one capability report 205) shown in.

[0164] In some example embodiments, the apparatus may further include a component for receiving at least one of capability information, status information, or environmental information of at least one terminal device from at least one terminal device including a first terminal device during a side link positioning procedure or a discovery procedure of at least one terminal device for a side link positioning procedure.

[0165] In some example embodiments, the first network entity may be a Location Management Function (LMF) or a server User Equipment (UE), and the second network entity may be an Access and Mobility Management Function (AMF).

[0166] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 700. In some embodiments, the means comprises at least one processor and at least one memory with computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to perform.

[0167] In some embodiments, a device capable of performing method 800 (e.g., Figure 1 and Figure 2 The second network entity 130 shown in FIG. 8 , or a portion of the second network entity 130 , may include components for executing corresponding steps of the method 800 . The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0168] In some example embodiments, the apparatus comprises: Figure 1 and Figure 2 ) and from a first network entity (e.g., Figure 1 and Figure 2 ) receives at least one terminal device for receiving a request from a first terminal device (for example, Figure 1 and Figure 2 A component for requesting at least one capability report of a sidelink positioning procedure performed by the first terminal device 110-1) shown in FIG. 1 ; and a component for sending at least one capability report to the first network entity.

[0169] In some example embodiments, the apparatus may further include a component for receiving, from a first terminal device, a request for attribute information of at least one terminal device for side link positioning of the first terminal device, and a component for sending the attribute information (e.g., information 202 relating to at least one standard) to the first terminal device.

[0170] In some example embodiments, the apparatus may include: a method for receiving, during a registration process of the second terminal device, from the second terminal device (e.g., Figure 1 and Figure 2 The second terminal device 110 - 2 shown in the figure receives at least one of the capability information, status information or environment information of the second terminal device.

[0171] In some example embodiments, the first network entity may be a Location Management Function (LMF) or a server User Equipment (UE), and the second network entity may be an Access and Mobility Management Function (AMF).

[0172] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 800. In some embodiments, the means comprises at least one processor and at least one memory with computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to perform.

[0173] Fig. 9 900 is a simplified block diagram of a device suitable for implementing some example embodiments of the present disclosure. The device 900 may be provided for implementing a communication device, such as Figure 1 The first terminal device 110-1, the second terminal device 110-2, the first network entity 120 and the second network entity 130 are shown. As shown in the figure, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processor 910, and one or more communication modules 940 coupled to the processor 910.

[0174] The communication module 940 is used for two-way communication. The communication module 940 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0175] Processor 910 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 900 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock that synchronizes a main processor.

[0176] The memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 924, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 922 and other volatile memories that do not persist during power outages.

[0177] The computer program 930 includes computer executable instructions executed by the associated processor 910. The program 930 may be stored in the ROM 924. The processor 910 may perform any appropriate actions and processes by loading the program 930 into the RAM 922.

[0178] The embodiments of the present disclosure can be implemented by means of program 930, so that the device 900 can execute the reference Figure 2-Figure 8 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0179] In some example embodiments, the program 930 may be tangibly embodied in a computer-readable medium, which may be included in the device 900 (such as the memory 920) or in other storage devices accessible to the device 900. The device 900 may load the program 930 from the computer-readable medium to the RAM 922 for execution. The computer-readable medium may include any type of tangible non-volatile storage device, such as a ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0180] Fig.10 1000 according to some example embodiments of the present disclosure. The computer readable medium 1000 has a program 930 stored thereon. Note that although the computer readable medium 1000 is Fig.10 Although depicted in the form of a CD or DVD, computer readable medium 1000 may be in any other form suitable for carrying or retaining program 930.

[0181] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0182] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as instructions included in a program module, which are executed in a device on a target real or virtual processor, and the computer executable instructions are executed in a device on a target real or virtual processor to perform the above reference Figure 2-Figure 8 Any of the methods 200-800 described herein. Typically, a program module includes a routine, program, library, object, class, component, data structure, etc. that performs a specific task or implements a specific abstract data type. In various embodiments, the functions of the program modules can be combined or split between program modules as needed. The machine executable instructions of the program modules can be executed in a local or distributed device. In a distributed device, the program modules can be located in local and remote storage media.

[0183] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the function / operation specified in the flow chart and / or block diagram to be realized. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0184] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform the above-mentioned various processes and operations. Examples of carriers include signals, computer-readable media, etc.

[0185] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment or any suitable combination thereof. More specific examples of computer-readable storage media include an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device or any suitable combination thereof. The term "non-transient" as used herein is a limitation on the medium itself (i.e., tangible, not a signal), not a limitation on the persistence of data storage (e.g., RAM and ROM).

[0186] In addition, although the operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in order or performing all the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0187] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Instead, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0188] For the purposes of this document, reference is made to the following defined terms.

[0189] AMF access and mobility management functions

[0190] gNBNext Generation Node B

[0191] GNSS Global Navigation Satellite System

[0192] LMF Location Management Function

[0193] LOS Line of Sight

[0194] LPP LTE Positioning Protocol

[0195] NLOS Non-Line-of-Sight

[0196] NRPPa NR Positioning Protocol A

[0197] OOC Out of Coverage

[0198] PRS Positioning Reference Signal

[0199] RRC Radio Resource Control

[0200] RSU Roadside Unit

[0201] RTT Round Trip Time

[0202] SRS Sounding Reference Signal

[0203] UE User Equipment

[0204] SL Side Link

[0205] TRP Transmission Reception Point

[0206] SDT Small Data Send

[0207] TA Timing Advance

[0208] RRM Radio Resource Measurement

[0209] RACH Random Access Channel

[0210] Msg

[0211] MAC CE MAC Control Element

[0212] MO-LR Positioning request initiated by the mobile terminal

[0213] Enhanced cell identified by ECID

[0214] MT-LR Mobile terminated location request

[0215] PCI physical unit identifier.

Claims

1. A first terminal device, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the first terminal device to at least: Obtaining at least one criterion of a second terminal device for a sidelink positioning process performed by the first terminal device; during the discovery process, determining whether the second terminal device satisfies the at least one criterion; as well as Based on determining that the second terminal device satisfies the at least one criterion, it is determined that the second terminal device is to be discovered for the sidelink positioning procedure.

2. The first terminal device according to claim 1, wherein the first terminal device is configured to obtain the at least one criterion by: receiving from a first network entity the at least one criterion determined by the first network entity; or The at least one criterion is determined locally at the first terminal device.

3. The first terminal device according to claim 2, wherein the first terminal device is caused to receive the at least one criterion by: The at least one criterion is received from the first network entity via a message related to the sidelink discovery procedure of the first terminal device for performing the discovery procedure.

4. The first terminal device according to claim 2, wherein in case the sidelink positioning is triggered by the first terminal device, the at least one criterion is determined locally at the first terminal device.

5. A second terminal device, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the second terminal device to at least: determining information relating to at least one criterion of the second terminal device for a sidelink positioning procedure performed by the first terminal device; and The information is provided to the first terminal device. 6 . The second terminal device according to claim 5 , wherein the information comprises whether the second terminal device meets the at least one criterion.

7. The second terminal device according to claim 6, wherein the second terminal device is configured to determine the information by: receiving, from the first terminal device, a discovery request message indicating the at least one criterion; and Determine whether the second terminal device meets the at least one criterion.

8. The second terminal device according to claim 7, wherein the second terminal device is configured to provide the information to the first terminal device in the following manner: Based on determining that the second terminal device satisfies the at least one criterion, a discovery response message is sent to the first terminal device in response to the discovery request message.

9. A method for communication, comprising: At a first terminal device, obtaining at least one criterion of a second terminal device for a sidelink positioning procedure performed by the first terminal device; during the discovery process, determining whether the second terminal device satisfies the at least one criterion; as well as Based on determining that the second terminal device satisfies the at least one criterion, it is determined that the second terminal device is to be discovered for the sidelink positioning procedure.

10. A method for communication, comprising: determining, at a second terminal device, information relating to at least one criterion used by the second terminal device for a sidelink positioning procedure performed by the first terminal device; as well as The information is provided to the first terminal device.

Images