Communication method and apparatus used for SL positioning service scenario, device, and medium

Abstract

The present application relates to the field of sidelink (SL) positioning, and provides a communication method and apparatus used for an SL positioning service scenario, a device, and a medium. The method comprises: a target UE receives a ranging / SL positioning service request; the target UE determines an SL positioning service UE, wherein the SL positioning service UE is a UE configured to implement an SL positioning service function. By using the described solution, the target UE can select the SL positioning service UE.

Description

Communication method, device, equipment and medium applied to SL positioning service scenario Technical Field

[0001] The present application relates to the field of side-by-side positioning, and in particular to a communication method, apparatus, device and medium applied to SL positioning service scenarios. Background Art

[0002] SL (Sidelink) positioning refers to positioning between UEs (User Equipment).

[0003] In the IC (In-Coverage) scenario of SL positioning, both the anchor UE and the target UE are connected to the 5G (5th Generation Mobile Communication Technology) system. SL positioning assistance information between the target UE and the anchor UE is uploaded to the LMF (Location Management Function) network element. The LMF aggregates and calculates the results to achieve positioning.

[0004] In the OOC (Out-Of-Coverage) scenario of SL positioning, both the anchor UE and the target UE are disconnected from the 5G system. In this scenario, there is no LMF, and how to implement sideways positioning is still under discussion.

[0005] Summary of the Invention

[0006] This application provides a communication method, apparatus, device, and medium for use in SL positioning service scenarios. The technical solution is as follows:

[0007] According to one aspect of the present application, a communication method applied to a SL positioning service scenario is provided, the method comprising:

[0008] The target UE receives the ranging / SL positioning service request;

[0009] The target UE determines the SL positioning service UE;

[0010] Among them, the SL positioning service UE is a UE used to undertake the SL positioning service function.

[0011] According to one aspect of the present application, a communication method applied to a SL positioning service scenario is provided, the method comprising:

[0012] The second UE receives the request message sent by the target UE;

[0013] The second UE sends a response message to the target UE, where the response message carries information used by the target UE to determine the SL positioning service UE;

[0014] The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the request message is used to request the second UE to serve as the SL positioning service UE.

[0015] According to one aspect of the present application, a communication method applied to a SL positioning service scenario is provided, the method comprising:

[0016] The SL positioning service UE receives the request message sent by the target UE;

[0017] The SL positioning service UE sends a response message to the target UE;

[0018] The request message is used to request the receiving UE to serve as the SL positioning service UE, and the response message is used to indicate whether the receiving UE agrees to serve as the SL positioning service UE.

[0019] According to one aspect of the present application, a communication method applied to a SL positioning service scenario is provided, the method comprising:

[0020] The anchor UE receives the notification message;

[0021] The notification message is used to indicate the SL positioning service UE.

[0022] According to one aspect of the present application, a communication device applied to a SL positioning service scenario is provided, the device being used to implement a target UE, the device comprising:

[0023] Receiving module, used to receive ranging / SL positioning service requests;

[0024] A determination module, configured to determine a SL positioning service UE;

[0025] Among them, the SL positioning service UE is a UE used to undertake the SL positioning service function.

[0026] According to one aspect of the present application, a communication device applied to a SL positioning service scenario is provided, the device being used to implement a second UE, the device including:

[0027] A receiving module, configured to receive a request message sent by a target UE;

[0028] A sending module, configured to send a response message to the target UE, wherein the response message contains information for the target UE to determine the SL positioning service UE;

[0029] The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the request message is used to request the second UE to serve as the SL positioning service UE.

[0030] According to one aspect of the present application, a communication device for use in a SL positioning service scenario is provided, the device comprising:

[0031] A receiving module, configured to receive a request message sent by a target UE;

[0032] A sending module, configured to send a response message to the target UE;

[0033] The request message is used to request the receiving UE to serve as the SL positioning service UE, and the response message is used to indicate whether the receiving UE agrees to serve as the SL positioning service UE.

[0034] According to one aspect of the present application, a communication device for use in a SL positioning service scenario is provided, the device comprising:

[0035] A receiving module, used for receiving notification messages;

[0036] The notification message is used for SL positioning service UE.

[0037] According to one aspect of the present application, a terminal is provided, comprising:

[0038] processor;

[0039] a transceiver connected to the processor;

[0040] a memory for storing executable instructions for the processor;

[0041] The processor is configured to load the executable instructions so that the terminal implements the communication method applied to the SL positioning service scenario as described above.

[0042] According to one aspect of the present application, a computer-readable storage medium is provided, in which executable instructions are stored. The executable instructions are loaded and executed by a processor to implement the communication method applied to the SL positioning service scenario as described above.

[0043] According to one aspect of the present application, a chip is provided, which includes a programmable logic circuit or a program, and the chip is used to implement the communication method applied to the SL positioning service scenario as described above based on the programmable logic circuit or the program.

[0044] According to one aspect of the present application, a computer program product is provided, which includes computer instructions, which are stored in a computer-readable storage medium. A processor of a communication device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the communication device executes the communication method applied to the SL positioning service scenario as described above.

[0045] The technical solutions provided by the embodiments of the present application include at least the following beneficial effects:

[0046] In the communication method for the SL positioning service scenario provided in the embodiments of the present application, the target UE may determine the SL positioning service UE based on at least one of the following methods:

[0047] Method 1: The target UE determines the SL positioning service UE based on the RSRP information between the first UE and at least one anchor UE, and / or the target UE determines the SL positioning service UE based on the RSRP information between the first UE and each anchor UE in the UE list. In this method, the target UE can obtain richer auxiliary information, and the target UE can evaluate the channel transmission quality between the first UE and each anchor UE, thereby determining the SL positioning service UE.

[0048] Method 2: The target UE determines the SL positioning service UE based on the indication information of whether SL unicast communication can be established between the first UE and at least one anchor UE, and / or the target UE determines the SL positioning service UE based on the indication information of whether SL unicast communication can be established between the first UE and each anchor UE in the UE list. The target UE of this method can evaluate the channel transmission quality between the first UE and each anchor UE, and then determine the SL positioning service UE. Compared with Method 1, the signaling overhead is greatly reduced.

[0049] Method 3: The target UE determines the SL positioning service UE based on the number of SL unicast communications that can be established between the first UE and at least one anchor UE, and / or the target UE determines the SL positioning service UE based on the number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list. The target UE of this method can evaluate the channel transmission quality between the first UE and each anchor UE, and then determine the SL positioning service UE. Compared with Methods 1 and 2, the signaling overhead is further reduced.

[0050] In addition, certain embodiments of the present application have further technical advantages, namely, after the target UE determines the SL positioning service UE, the target UE sends a notification message to at least one anchor UE, where the notification message is used to indicate the SL positioning service UE. Accordingly, the target UE can notify at least one anchor UE of the selection result of the SL positioning service UE. This allows the anchor UE to be aware of the SL positioning service UE, and further enables steps such as exchanging SL positioning assistance information with the SL positioning service UE and sending SL-PRS measurement data. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0052] FIG1 is a schematic diagram of a communication system provided by an exemplary embodiment of the present application;

[0053] FIG2 is a schematic diagram of side communication provided by an exemplary embodiment of the present application;

[0054] FIG3 is a schematic diagram of side communication provided by an exemplary embodiment of the present application;

[0055] FIG4 is a schematic diagram of sideline communication provided by an exemplary embodiment of the present application;

[0056] FIG5 is a schematic diagram of an SL discovery process provided by an exemplary embodiment of the present application;

[0057] FIG6 is a schematic diagram of an SL discovery process provided by an exemplary embodiment of the present application;

[0058] FIG7 is a schematic diagram of an SL positioning process provided by an exemplary embodiment of the present application;

[0059] FIG8 is a schematic diagram of an SL positioning process provided by an exemplary embodiment of the present application;

[0060] FIG9 is a schematic diagram of an SL positioning process provided by an exemplary embodiment of the present application;

[0061] FIG10 is a schematic diagram of a communication method applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0062] FIG11 is a schematic diagram of a communication method applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0063] FIG12 is a schematic diagram of a communication method applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0064] FIG13 is a schematic diagram of a communication method applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0065] FIG14 is a schematic diagram of a communication method applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0066] FIG15 is a structural block diagram of a communication device applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0067] FIG16 is a structural block diagram of a communication device applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0068] FIG17 is a structural block diagram of a communication device applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0069] FIG18 is a structural block diagram of a communication device applied to a SL positioning service scenario provided by an exemplary embodiment of the present application;

[0070] FIG19 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0071] To make the objectives, technical solutions, and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail herein, with examples shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are merely examples of devices and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0072] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0073] It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining."

[0074] FIG1 shows a schematic diagram of a network architecture provided by an embodiment of the present application. The network architecture 100 may include: a terminal 10 , an access network device 20 , and a core network device 30 .

[0075] The terminal 10 may refer to a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user device. Optionally, the terminal 10 may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in the fifth generation mobile communication system (5GS) or a terminal in the future evolved public land mobile communication network (PLMN), etc., and the embodiments of the present application are not limited to this. For the convenience of description, the devices mentioned above are collectively referred to as terminals. The number of terminals 10 is usually multiple, and one or more terminals 10 can be distributed in each cell managed by the access network device 20.

[0076] The access network device 20 is a device deployed in the access network to provide wireless communication functions for the terminal 10. The access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems using different wireless access technologies, the names of devices with access network device functions may be different. For example, in the 5G NR system, it is called gNodeB or gNB (next Generation Node B, next generation node B (or new generation access network node)). With the evolution of communication technology, the name "access network device" may change. For the convenience of description, in the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal 10 are collectively referred to as access network devices. Optionally, a communication relationship can be established between the terminal 10 and the core network device 30 through the access network device 20. For example, in a Long Term Evolution (LTE) system, the access network device 20 may be an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or one or more eNodeBs in the EUTRAN. In a 5G NR system, the access network device 20 may be a Radio Access Network (RAN) or one or more gNBs in the RAN. In the embodiments of the present application, unless otherwise specified, the network device referred to herein refers to the access network device 20, such as a base station.

[0077] The core network device 30 is a device deployed in the core network. The function of the core network device 30 is mainly to provide user connection, user management, and service carrying, and to provide an interface to the external network as a bearer network. For example, the core network equipment in the 5G NR system may include an access and mobility management function (AMF) network element, an authentication server function (AUSF) network element, a user plane function (UPF) network element, a session management function (SMF) network element, a location management function (LMF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, etc.

[0078] In one example, the access network device 20 and the core network device 30 communicate with each other via an interface technology, such as the NG interface in the 5G NR system. The access network device 20 and the terminal 10 communicate with each other via an air interface technology, such as the Uu interface.

[0079] Access network equipment is the device that allows terminals to access the network architecture wirelessly. It is primarily responsible for radio resource management, Quality of Service (QoS) management, data compression and encryption, etc. on the air interface side. Examples include NodeBs, evolved eNodeBs, base stations in 5G mobile communication systems or next-generation wireless (NR) communication systems, and base stations in future mobile communication systems.

[0080] The core network equipment includes NSSF (Network Slice Selection Function), AUSF (Authentication Server Function), UDM (Unified Data Management), AMF (Access and Mobility Management Function), SMF (Session Management Function), PCF (Policy Control Function), and UPF (User Plane Function).

[0081] The UE establishes an access layer connection with the (R)AN (Access Network) through the Uu interface, exchanging access layer messages and wireless data transmission. The UE establishes a non-access layer (None Access Stratum, NAS) connection with the AMF through the N1 interface, exchanging NAS messages. The AMF is the mobility management function in the core network, and the SMF is the session management function in the core network. In addition to managing the mobility of the UE, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The PCF is the policy management function in the core network, responsible for formulating policies related to the mobility management, session management, and billing of the UE. The PCF transmits data with the external application function (AF) through the N5 interface. The UPF is a user plane function in the core network, which transmits data with the external data network (DN) through the N6 interface and with the AN through the N3 interface.

[0082] The "5G NR system" in the embodiments of the present application may also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in the embodiments of the present application may be applicable to LTE systems, 5G NR systems, subsequent evolution systems of 5G NR systems, and other communication systems such as Narrow Band Internet of Things (NB-IoT) systems, and this application does not limit this.

[0083] First, the relevant contents involved in this application are introduced.

[0084] SL positioning client UE: A third-party UE other than the anchor UE and target UE, which initiates ranging / SL positioning service requests on behalf of the applications residing on it.

[0085] In some embodiments, the SL positioning client UE may not have to support ranging / SL positioning capabilities, but communication between the SL positioning client UE and the anchor UE / target UE must be established through PC5 or 5GC to transmit ranging / SL positioning service requests and results.

[0086] Target UE: In ranging / SL positioning based services, the UE whose distance, direction and / or position is measured with the support of one or more anchor UEs of the SL.

[0087] Anchor UE: A UE that supports the positioning of a target UE, for example, by using the SL to send and / or receive reference signals for SL positioning, provide positioning-related information, etc.

[0088] In some embodiments, the anchor UE is a UE used to send and / or receive reference signals for SL positioning using SL.

[0089] In some embodiments, the anchor UE is a UE that provides positioning related information to the target UE or serving UE.

[0090] In some embodiments, the anchor UE is also called a SL reference UE (SL Reference UE).

[0091] In some embodiments, an anchor UE whose location is known or can obtain its own location by using Uu positioning is also referred to as an anchor UE (Located UE) that can obtain its own location.

[0092] SL positioning service UE: A UE that assists in data distribution and / or position calculation functions based on ranging / SL positioning service request.

[0093] In some embodiments, the SL positioning service UE interacts with the target UE, anchor UE or other UEs other than the anchor UE and target UE through PC5 when necessary to determine the ranging / SL positioning method, distribute auxiliary data and calculate the position of the target UE.

[0094] In some embodiments, the SL positioning service UE may be at least one of the following UEs:

[0095] Target UE;

[0096] Anchor UE;

[0097] Other UEs except the anchor UE and the target UE.

[0098] SL (Sidelink) transmission technology

[0099] Unlike traditional cellular systems where communication data is received or sent through access network equipment, SL transmission refers to direct communication data transmission between terminals through side links.

[0100] Regarding SL transmission, 3GPP (3rd Generation Partnership Project) defines two transmission modes: Mode A and Mode B.

[0101] Mode A: The transmission resources of SL UE (User Equipment) are allocated by the access network device. The SL UE transmits communication data on the side link according to the transmission resources allocated by the access network device. The access network device can allocate transmission resources for single transmission to the SL UE, or allocate transmission resources for semi-static transmission to the SL UE.

[0102] Mode B: The SL UE selects one or more transmission resources in the resource pool to transmit communication data. The SL UE can select transmission resources in the resource pool by listening or by random selection. When performing SL transmission on the unlicensed spectrum, the access network device can pre-configure multiple resource pools (SL PRS resource pool, SL-U communication resource pool, etc.) for the UE. When performing specific services, the UE can select resources from the corresponding resource pool to perform the LBT (Listen Before Talk) process. If the LBT is successful, the UE can occupy this part of the resources for sidelink transmission on the unlicensed spectrum. When the UE sends sidelink data on this part of the resources, it also sends SCI. The SCI indicates the resources occupied by the UE's current sidelink transmission. In addition, the SCI can also be used to indicate the resources reserved by the UE. For example, if the UE occupies a part of the resources in the SL PRS resource pool through LBT to send SL PRS, the UE sends SL PRS and SCI-P on this part of the resources. The SCI-P indicates the resources occupied by this SL PRS and the resources reserved for subsequent SL PRS.

[0103] In SL transmission, according to the network coverage of the communicating terminals, it can be divided into network coverage inner line communication, partial network coverage side line communication, and network coverage outer line communication, as shown in Figure 2, Figure 3 and Figure 4 respectively.

[0104] Figure 2: In sideline communications within network coverage, all terminals 21 performing sideline communications are within the coverage of the same base station 10. Therefore, the above terminals 21 can all perform sideline communications based on the same sideline configuration by receiving configuration signaling from the base station 10.

[0105] Figure 3: In the case of partial network coverage and sidelink communication, some terminals 21 performing sidelink communication are within the coverage of the base station 10. These terminals 21 can receive configuration signaling from the base station 10 and perform sidelink communication according to the configuration of the base station 10. However, terminals 22 outside the network coverage cannot receive configuration signaling from the base station 10. In this case, the terminal 22 outside the network coverage will determine the sidelink configuration based on pre-configuration information and information carried in the Physical Sidelink Broadcast Channel (PSBCH) sent by the terminal 21 within the network coverage, and perform sidelink communication.

[0106] Figure 4: For sideline communications outside the network coverage, all terminals 22 performing sideline communications are located outside the network coverage, and all terminals 22 determine the sideline configuration according to the pre-configured information to perform sideline communications.

[0107] SL Positioning

[0108] As shown in Figure 2, in the IC (In-Coverage) scenario for SL positioning, both the anchor UE and the target UE are connected to the 5G (Fifth Generation Mobile Communication Technology) system. In this case, the SL-PRS configuration is managed by the LMF and / or gNB. The SL positioning assistance information between the target UE and the anchor UE is uploaded to the LMF network element. The LMF aggregates and calculates the results to achieve positioning.

[0109] As shown in Figure 3, in the PC (Partial Coverage) scenario for SL positioning, some anchor UEs and target UEs are in IC scenarios, while others are in OOC scenarios. In this case, it is necessary to consider whether the SL-PRS configuration still requires LMF and / or gNB control. The SL positioning assistance information between the target UE and the anchor UE, which requires LMF control, is uploaded to the LMF network element. The LMF aggregates and calculates the results to achieve positioning.

[0110] As shown in Figure 4, in the OOC (Out-Of-Coverage) scenario of SL positioning, both the anchor UE and the target UE are in a state of being disconnected from the 5G system. In this case, their SL-PRS are not controlled by the location management function LMF and / or gNB. In the OOC scenario, the 5G system performs measurements on the SL-PRS sent by the target UE through the anchor UE, or the target UE performs measurements on the SL-PRS sent by the anchor UE, and completes positioning in combination with the anchor UE's own location information. The target UE needs to discover and select a UE as the SL positioning service UE (Server UE), and transmit the SL positioning assistance information between the target UE and the anchor UE and the SL positioning service UE to the SL positioning service UE. The SL positioning service UE will summarize and calculate the results to achieve positioning.

[0111] Related technologies support absolute positioning, which is the process of obtaining the absolute position of the target UE. However, relative positioning is an important function of SL positioning. The target UE can obtain relative position information with respect to the anchor UE, such as the distance and angle relative to the anchor UE.

[0112] SL Discovery Process

[0113] Model A Discovery (“I’m Here”)

[0114] As shown in Figure 5, this model defines two roles for UEs participating in discovery: 1. Announcing UEs: These announce certain information through announcement messages, which can be used by nearby discovery-authorized UEs; 2. Monitoring UEs: These monitor nearby UEs for information of interest. In this model, announcing UEs broadcast announcement messages at predefined discovery intervals. Interested listening UEs read and process these discovery messages. Because announcing UEs broadcast information about themselves, this model is equivalent to an "I am here" scenario.

[0115] Step 1. The announcing UE (UE-1) sends a ranging / SL positioning notification message.

[0116] The ranging / SL positioning notification message includes the discovery message type, security protection elements, RSPP metadata information, and the user information ID of the announced UE.

[0117] Configure the Destination Layer-2 ID used to send ranging / SL positioning announcement messages.

[0118] The Source Layer-2 ID for sending the ranging / SL positioning announcement message is allocated by the announcing UE. The announcing UE sends the announcement message only when it is authorized to play the corresponding UE role in the RSPP metadata information.

[0119] For a declaring UE that is an anchor UE (Located UE) that can obtain its own position, the ranging / SL positioning notification message also includes the serving PLMN of the declaring UE.

[0120] The user information ID of the announced UE is the application layer ID of the announced UE.

[0121] The monitoring UE determines the destination layer 2 ID for signaling reception based on the above configuration.

[0122] The listening UE selects the announcing UE based on the information received in step 1.

[0123] In some embodiments, RSPP metadata information (eg, the role of the announced UE) is included as metadata in the notification message. In some embodiments, the roles of the announced UE include anchor UE, target UE, SL positioning service UE, and anchor UE capable of obtaining its own location.

[0124] In some embodiments, the anchor UE capable of obtaining its own position refers to an anchor UE whose position is known or which can obtain its own position by using Uu positioning, and may also be referred to as a SL reference UE (SL Reference UE).

[0125] Model A Discovery (“Who’s there?” / “Are you there?”)

[0126] As shown in Figure 6, this model defines two roles for UEs participating in discovery: 1. Discoverer UE: The discoverer UE sends a request message containing information about what it is interested in discovering. 2. Discoverer UE: The UE that receives the request message can respond with information related to the discoverer UE's request message. Since the discoverer UE sends information about other UEs that wish to receive a response, such as a ProSe application identifier corresponding to a group, members of the group can respond. Therefore, this model is equivalent to the "Who's there / Are you there?"

[0127] Step 1. The discoverer UE (UE-1) sends a ranging / SL positioning request message. The ranging / SL positioning request message includes the type of discovery message, a security protection element, optionally the user information ID of the discoverer UE, target information, the discoverer UE user information ID, and optionally RSPP metadata information.

[0128] The destination layer 2 ID for sending ranging / SL positioning request messages is configured.

[0129] The source layer 2 ID used to send the ranging / SL positioning request message is allocated by the discoverer UE.

[0130] The discovered UE sends a response message only when it is authorized to play the corresponding UE role in the request message.

[0131] If the role of the discovered UE is Located UE, the ranging / SL positioning response message also includes the serving PLMN of the discovered UE.

[0132] The user information ID of the discoverer UE is the discoverer UE application layer ID.

[0133] The user information ID of the discoverer UE is used to identify the specific UE that the discoverer UE wants to discover. The specific UE is identified by the discoverer UE application layer ID.

[0134] The discovered UE determines the target layer 2 ID for signaling reception based on the aforementioned configuration.

[0135] In some embodiments, RSPP metadata information (e.g., specific UE roles to be discovered) is included in the request message as metadata. In some embodiments, the specific UE roles to be discovered include anchor UE, target UE, SL positioning service UE, and anchor UE capable of obtaining its own location.

[0136] Step 2. The discoverer UE that matches the ranging / SL positioning request message (e.g., RSPP metadata information) responds to the discoverer UE with a ranging / SL positioning response message. The ranging / SL positioning response message includes the discovery message type, security protection element, RSPP metadata information, and the user information ID of the discoverer UE.

[0137] Configure the source layer 2 ID used to send ranging / SL positioning response messages.

[0138] • The destination layer 2 ID is set to the source layer 2 ID of the received ranging / SL positioning request message.

[0139] The user information ID of the discoverer UE is the application layer ID of the discoverer UE.

[0140] In some embodiments, RSPP metadata information (e.g., the role of the discoverer UE) is included as metadata in the response message. In some embodiments, the role of the discoverer UE includes anchor UE, target UE, SL positioning service UE, and anchor UE capable of obtaining its own position.

[0141] SL positioning process

[0142] In some embodiments, it is provided that in the ranging / SL positioning process, either UE-only operation or network-based operation is applied.

[0143] In some embodiments, UE-only operation applies to the following situations:

[0144] NG-RAN provides services neither for target UE nor for anchor UE.

[0145] 5GC network does not support network-based operation: When the 5GC network does not support network-based operation, the target UE shall consider whether to initiate the UE-only operation procedure to indicate whether the UE is allowed to perform ranging / SL positioning using UE-only operation, which is carried in the policy / parameters provided to the UE.

[0146] The SL-MO-LR request was rejected by the network.

[0147] In some embodiments, as for any other cases, network-based operations are applicable.

[0148] Figure 7 shows a schematic diagram of the SL positioning process provided by an exemplary embodiment of the present application. Figure 7 includes the SL positioning client UE, UE1, UE2 / … / UEn, and the SL positioning service UE. UE1 is also referred to as the target UE, UE2 / … / UEn is also referred to as the anchor UE, and the SL positioning service UE is also referred to as the serving UE. The relevant steps of the SL positioning process are briefly described as follows:

[0149] Step 1. UE1 receives a ranging / SL positioning service request.

[0150] In some embodiments, step 1 can be implemented as step 1a or step 1b.

[0151] Step 1a. The SL positioning client UE sends a ranging / SL positioning service request from PC5 to UE1.

[0152] In some embodiments, during the process of exposing ranging / SL positioning services through PC5, the SL positioning client UE is positioned through PC5, that is, the SL positioning client sends a ranging / SL positioning service request to UE1 through the PC5 interface.

[0153] In some embodiments, for absolute positioning, the ranging / SL positioning service request includes the user information of the SL positioning client UE and the user information of the target UE, as well as the required positioning QoS.

[0154] In some embodiments, for relative position or ranging information, the ranging / SL positioning service request includes user information of the SL positioning client UE, user information of UE1, user information of UE2 / … / UEn and ranging / SL positioning QoS information.

[0155] Step 1b. UE1 receives the ranging / SL positioning service request from the application layer.

[0156] In some embodiments, UE1 receives a ranging / SL positioning service request from the application layer.

[0157] In some embodiments, the ranging / SL positioning service request includes a result type and a required QoS, wherein the result type includes absolute position, relative position, or ranging information.

[0158] Step 2. UE1 discovers UE2 / … / UEn.

[0159] In some embodiments, UE2 / … / UEn serves as an anchor UE. For example, UE2 / … / UEn is configured to send an SL-PRS to UE1, and UE1 performs SL-PRS measurements; or, UE1 is configured to send an SL-PRS to UE2 / … / UEn, and each UE2 / … / UEn performs SL-PRS measurements.

[0160] Step 3. UE1 determines that only UE is operating.

[0161] In some embodiments, if any of UE1 / ... / UEn is not served by NG-RAN or the serving network does not support ranging / SL positioning, it is determined that UE-only operation is applied. In some embodiments, if UE1 / ... / UEn is in an OOC scenario, it is determined that UE-only operation is applied.

[0162] Step 4. UE1 and UE2 / … / UEn perform capability exchange.

[0163] In some embodiments, step 4 may be performed during steps 5 and 6 under the coordination of the SL positioning service UE.

[0164] Step 5. UE1 discovers and selects the SL positioning service UE.

[0165] In some embodiments, when UE1 does not support the SL positioning service UE function, UE1 discovers and selects the SL positioning service UE. The SL positioning service UE can be a UE in UE2 / … / UEn, or a separate UE.

[0166] In some embodiments, when the SL positioning service UE is a UE in UE2 / … / UEn or another separate UE, UE1 discovers and selects the SL positioning service UE, and requests the SL positioning service UE to participate in ranging / SL positioning.

[0167] Step 6: Transmit SL positioning assistance information.

[0168] In some embodiments, SL positioning assistance information is transmitted between UE1, UE2 / … / UEn and the SL positioning service UE.

[0169] Step 7. Measure SL-PRS.

[0170] In some embodiments, SL-PRS is measured between UE1 and UE2 / ... / UEn.

[0171] In some embodiments, SL-PRS is measured between UE2 / ... / UEn.

[0172] Step 8. Transmit SL-PRS measurement data and calculate ranging / SL positioning results.

[0173] In some embodiments, UE1 and / or UE2 / … / UEn transmits SL-PRS measurement data to a SL positioning service UE. The SL positioning service UE calculates a ranging / SL positioning result and sends the ranging / SL positioning result to UE1. Based on the result type received in step 1, the SL positioning service UE calculates an absolute position, a relative position, or ranging information.

[0174] In some embodiments, if UE1 supports the SL positioning service UE function, UE2 / … / UEn transmits SL-PRS measurement data to UE1, and UE1 calculates the ranging / SL positioning result. Based on the result type received in step 1, UE1 calculates the absolute position, relative position, or ranging information.

[0175] In some embodiments, UE1 sends a SL-PRS to UE2 / … / UEn, which then measures the SL-PRS. UE2 / … / UEn transmits the SL-PRS measurement data to a SL positioning service UE. The SL positioning service UE locates UE2 / … / UEn based on the SL-PRS measurement data and calculates UE1's absolute position, relative position, or ranging information.

[0176] Step 9. UE1 responds to the ranging / SL positioning service request.

[0177] Step 9a. UE1 responds to the ranging / SL positioning service request sent by the SL positioning client UE from PC5.

[0178] Step 9b. UE1 responds to the ranging / SL positioning service request from the application layer.

[0179] Discover and select SL positioning service UE

[0180] In some embodiments, when the target UE meets one or more of the following criteria or conditions, the target UE discovers and selects the SL positioning service UE:

[0181] The target UE and anchor UE currently do not have network services that support ranging / SL positioning. For example, the target UE and anchor UE are out of coverage, or the serving network does not support ranging / SL positioning. Ranging / SL positioning support is configured in the AMF according to network capabilities. If the AMF receives that the UE supports ranging / SL positioning capabilities, the AMF may include a ranging / SL positioning support indicator in the registration reception message to indicate that the serving network supports ranging / SL positioning. The anchor UE and target UE may indicate to each other whether their serving network supports ranging / SL positioning. When the UE does not have an available NAS connection, the indication that the serving network does not support ranging / SL positioning may be reused to notify each other.

[0182] The target UE cannot support the SL positioning service UE function.

[0183] The anchor UE cannot support the SL positioning service UE function.

[0184] In some embodiments, in case the UE is authorized as a SL location service UE in a given PLMN, the UE may indicate its role "SL location service UE" in its supported role list during discovery.

[0185] In some embodiments, the target UE needs to discover and select a SL positioning serving UE in the same or different serving PLMN of the target UE and the anchor UE.

[0186] As described above, in the OOC scenario, to support SL positioning services, if the target UE does not support the SL positioning service UE function, the target UE needs to discover and select the SL positioning service UE. The following introduces two selection methods, and different embodiments can adopt either of these two selection methods.

[0187] Option 1: Based on unicast signaling

[0188] Figure 8 shows a schematic diagram of the SL positioning process provided by an exemplary embodiment of the present application. Figure 8 includes the SL positioning client UE, UE1, UE2 / … / UEn, and the SL positioning service UE. UE1 is also referred to as the target UE, UE2 / … / UEn is also referred to as the anchor UE, and the SL positioning service UE is also referred to as the serving UE. The steps of the SL positioning process are briefly described as follows:

[0189] Step 1. UE1 receives a ranging / SL positioning service request.

[0190] In some embodiments, step 1 can be implemented as step 1a or step 1b.

[0191] Step 1a. The SL positioning client UE sends a ranging / SL positioning service request from PC5 to UE1.

[0192] In some embodiments, during the process of exposing ranging / SL positioning services through PC5, the SL positioning client UE is positioned through PC5, that is, the SL positioning client sends a ranging / SL positioning service request to UE1 through the PC5 interface.

[0193] In some embodiments, for absolute positioning, the ranging / SL positioning service request includes the user information of the SL positioning client UE and the user information of the target UE, as well as the required positioning QoS.

[0194] In some embodiments, for relative position or ranging information, the ranging / SL positioning service request includes user information of the SL positioning client UE, user information of UE1, user information of UE2 / … / UEn and ranging / SL positioning QoS information.

[0195] Step 1b. UE1 receives the ranging / SL positioning service request from the application layer.

[0196] In some embodiments, UE1 receives a ranging / SL positioning service request from the application layer.

[0197] In some embodiments, the ranging / SL positioning service request includes a result type and a required QoS, wherein the result type includes absolute position, relative position, or ranging information.

[0198] Step 2. UE1 discovers UE2 / … / UEn.

[0199] In some embodiments, UE2 / … / UEn serves as an anchor UE. For example, UE2 / … / UEn is configured to send an SL-PRS to UE1, and UE1 performs SL-PRS measurements; or, UE1 is configured to send an SL-PRS to UE2 / … / UEn, and each UE2 / … / UEn performs SL-PRS measurements.

[0200] Step 3. UE1 determines that only UE is operating.

[0201] In some embodiments, if any of UE1 / ... / UEn is not served by NG-RAN or the serving network does not support ranging / SL positioning, it is determined that UE-only operation is applied. In some embodiments, if UE1 / ... / UEn is in an OOC scenario, it is determined that UE-only operation is applied.

[0202] Step 4. UE1 and UE2 / … / UEn perform capability exchange.

[0203] In some embodiments, step 4 may be performed during steps 5 and 6 under the coordination of the SL positioning service UE.

[0204] In some embodiments, step 4 may be implemented as step 4a and step 4b.

[0205] Step 4a. UE1 sends a capability request message to UE2 / … / UEn.

[0206] In some embodiments, the capability request message is used to instruct the first UE among UE2 / … / UEn to return at least one of the following information to UE1:

[0207] RSRP information between the first UE and UE2 / … / UEn;

[0208] Indication information indicating whether SL unicast communication can be established between the first UE and UE2 / … / UEn;

[0209] The number of SL unicast communications that can be established between the first UE and UE2 / … / UEn.

[0210] In some embodiments, the capability request message is used to instruct the first UE among UE2 / … / UEn to return at least one of the following information to UE1:

[0211] RSRP information between the first UE and UE2 / … / UEn in the UE list;

[0212] Indication information indicating whether SL unicast communication can be established between the first UE and UE2 / … / UEn in the UE list;

[0213] The number of SL unicast communications that can be established between the first UE and UE2 / … / UEn in the UE list;

[0214] Among them, UE2 / … / UEn in the UE list is a subset of UE2 / … / UEn.

[0215] In some embodiments, the first UE is one of UE2 / ... / UEn, and UE2 / ... / UEn is a UE that performs capability exchange with UE1.

[0216] Step 4b. UE1 receives the capability response message returned by UE2 / … / UEn.

[0217] In some embodiments, the capability response message is further used to carry at least one of the following information of the first UE in UE2 / … / UEn:

[0218] RSRP information between the first UE and UE2 / … / UEn;

[0219] Indication information indicating whether SL unicast communication can be established between the first UE and UE2 / … / UEn;

[0220] The number of SL unicast communications that can be established between the first UE and UE2 / … / UEn.

[0221] In some embodiments, the capability response message is further used to carry at least one of the following information of the first UE in UE2 / … / UEn:

[0222] RSRP information between the first UE and UE2 / … / UEn in the UE list;

[0223] Indication information indicating whether SL unicast communication can be established between the first UE and UE2 / … / UEn in the UE list;

[0224] The number of SL unicast communications that can be established between the first UE and UE2 / … / UEn in the UE list;

[0225] Among them, UE2 / … / UEn in the UE list is a subset of UE2 / … / UEn.

[0226] Step 5. UE1 discovers and selects the SL positioning service UE.

[0227] Step 5-0. UE1 determines the SL location service UE based on the capability response message in step 4;

[0228] Step 5-1a. UE1 sends a SL positioning service UE request message to the SL positioning service UE;

[0229] Step 5-2a. The SL positioning service UE rejects / does not respond to the SL positioning service UE request message;

[0230] Step 5-1b. UE1 sends a SL positioning service UE request message to SL positioning service UE2;

[0231] Step 5-2b. SL positioning service UE2 responds to the SL positioning service UE request message;

[0232] Step 5-3a. UE1 sends a service UE role notification message to UE2 / … / UEn;

[0233] Step 5-3b. The SL positioning service UE sends a service UE role notification message to UE2 / … / UEn;

[0234] In some embodiments, the service UE role notification message carries identification information of the SL positioning service UE.

[0235] In some embodiments, the service UE role notification message also carries identification information of UE1.

[0236] In some embodiments, the served UE role notification message carries at least one of the following information:

[0237] SL positioning assistance information;

[0238] ·Announcement message of SL discovery process;

[0239] Request message of the SL discovery process;

[0240] NAS signaling.

[0241] In some embodiments, step 5-3a and step 5-3b can be performed in either manner.

[0242] Step 6: Transmit SL positioning assistance information.

[0243] In some embodiments, SL positioning assistance information is transmitted between UE1, UE2 / … / UEn and the serving UE.

[0244] Step 7. Measure SL-PRS.

[0245] In some embodiments, SL-PRS is measured between UE1 and UE2 / ... / UEn.

[0246] In some embodiments, SL-PRS is measured between UE2 / ... / UEn.

[0247] Step 8. Transmit SL-PRS measurement data and calculate ranging / SL positioning results.

[0248] In some embodiments, UE1 and / or UE2 / … / UEn transmits SL-PRS measurement data to a SL positioning service UE. The SL positioning service UE calculates a ranging / SL positioning result and sends the ranging / SL positioning result to UE1. Based on the result type received in step 1, the SL positioning service UE calculates an absolute position, a relative position, or ranging information.

[0249] In some embodiments, if UE1 supports the SL positioning service UE function, UE2 / … / UEn transmits SL-PRS measurement data to UE1, and UE1 calculates the ranging / SL positioning result. Based on the result type received in step 1, UE1 calculates the absolute position, relative position, or ranging information.

[0250] In some embodiments, UE1 sends a SL-PRS to UE2 / … / UEn, which then measures the SL-PRS. UE2 / … / UEn transmits the SL-PRS measurement data to a SL positioning service UE. The SL positioning service UE locates UE2 / … / UEn based on the SL-PRS measurement data and calculates UE1's absolute position, relative position, or ranging information.

[0251] Step 9. UE1 responds to the ranging / SL positioning service request.

[0252] Step 9a. UE1 responds to the ranging / SL positioning service request sent by the SL positioning client UE from PC5.

[0253] Step 9b. UE1 responds to the ranging / SL positioning service request from the application layer.

[0254] Using the selection method 1 of this embodiment, UE1 first determines the SL positioning service UE. UE1 only needs to send a SL positioning service UE request message to the SL positioning service UE it has determined each time, which can save signaling interaction and reduce signaling overhead. Since the SL positioning service UE may reject / not respond to the SL positioning service UE request message sent by UE1, the method 1 of this embodiment may cause the problem of a long time to determine the SL positioning service UE.

[0255] Option 2: Based on SL discovery

[0256] Figure 9 shows a schematic diagram of the SL positioning process provided by an exemplary embodiment of the present application. Figure 9 includes the SL positioning client UE, UE1, UE2 / … / UEn, and the SL positioning service UE. UE1 is also referred to as the target UE, UE2 / … / UEn is also referred to as the anchor UE, and the SL positioning service UE is also referred to as the serving UE. The steps of the SL positioning process are briefly described as follows:

[0257] Step 1. UE1 receives a ranging / SL positioning service request.

[0258] In some embodiments, step 1 can be implemented as step 1a or step 1b.

[0259] Step 1a. The SL positioning client UE sends a ranging / SL positioning service request from PC5 to UE1.

[0260] In some embodiments, during the process of exposing ranging / SL positioning services through PC5, the SL positioning client UE is positioned through PC5, that is, the SL positioning client sends a ranging / SL positioning service request to UE1 through the PC5 interface.

[0261] In some embodiments, for absolute positioning, the ranging / SL positioning service request includes the user information of the SL positioning client UE and the user information of the target UE, as well as the required positioning QoS.

[0262] In some embodiments, for relative position or ranging information, the ranging / SL positioning service request includes user information of the SL positioning client UE, user information of UE1, user information of UE2 / … / UEn and ranging / SL positioning QoS information.

[0263] Step 1b. UE1 receives the ranging / SL positioning service request from the application layer.

[0264] In some embodiments, UE1 receives a ranging / SL positioning service request from the application layer.

[0265] In some embodiments, the ranging / SL positioning service request includes a result type and a required QoS, wherein the result type includes absolute position, relative position, or ranging information.

[0266] Step 2. UE1 discovers UE2 / … / UEn.

[0267] In some embodiments, UE2 / … / UEn serves as an anchor UE. For example, UE2 / … / UEn is configured to send an SL-PRS to UE1, and UE1 performs SL-PRS measurements; or, UE1 is configured to send an SL-PRS to UE2 / … / UEn, and each UE2 / … / UEn performs SL-PRS measurements.

[0268] Step 3. UE1 determines that only UE is operating.

[0269] In some embodiments, if any of UE1 / ... / UEn is not served by NG-RAN or the serving network does not support ranging / SL positioning, it is determined that UE-only operation is applied. In some embodiments, if UE1 / ... / UEn is in an OOC scenario, it is determined that UE-only operation is applied.

[0270] Step 4. UE1 and UE2 / … / UEn perform capability exchange.

[0271] In some embodiments, step 4 may be performed during steps 5 and 6 under the coordination of the SL positioning service UE.

[0272] Step 5. UE1 discovers and selects the SL positioning service UE.

[0273] In some embodiments, step 5 can be implemented as at least one of step 5-0, step 5-1, step 5-2, and step 5-3. Step 5-1 can be implemented as step 5-1a and / or step 5-1b, step 5-2 can be implemented as step 5-2a and / or step 5-2b, and step 5-3 can be implemented as step 5-3a and / or step 5-3b.

[0274] Step 5-1. UE1 sends a SL positioning service UE request message to UE2 / … / UEn, SL positioning service UE, and SL positioning service UE2;

[0275] In some embodiments, UE1 sends a SL positioning service UE request message to UE2 / … / UEn, SL positioning service UE, and SL positioning service UE2 by broadcasting.

[0276] In some embodiments, the SL positioning service UE request message is used to instruct the second UE among UE2 / … / UEn, SL positioning service UE, and SL positioning service UE2 to return at least one of the following information to the target UE:

[0277] RSRP information between the second UE and UE2 / … / UEn;

[0278] Indication information indicating whether SL unicast communication can be established between the second UE and UE2 / … / UEn;

[0279] The number of SL unicast communications that can be established between the second UE and UE2 / … / UEn.

[0280] In some embodiments, the SL positioning service UE request message is further used to instruct the second UE among UE2 / … / UEn, SL positioning service UE, and SL positioning service UE2 to return at least one of the following information to the target UE:

[0281] RSRP information between the second UE and UE2 / … / UEn in the UE list;

[0282] Indication information indicating whether SL unicast communication can be established between the second UE and UE2 / … / UEn in the UE list;

[0283] The number of SL unicast communications that can be established between the second UE and UE2 / … / UEn in the UE list;

[0284] Among them, UE2 / … / UEn in the UE list is a subset of UE2 / … / UEn.

[0285] In some embodiments, the second UE is one of the candidate UEs. The candidate UE is a UE that is a candidate to become a SL positioning service UE, and the candidate UE includes at least one of UE2 / … / UEn, SL positioning service UE, and SL positioning service UE2.

[0286] Step 5-2. UE2 / … / UEn, SL positioning service UE, and SL positioning service UE2 respond to the SL positioning service UE request message;

[0287] In some embodiments, the SL positioning service UE response message is used to carry at least one of the following information of UE2 / … / UEn, the SL positioning service UE, and the second UE in the SL positioning service UE2:

[0288] RSRP information between the second UE and UE2 / … / UEn;

[0289] Indication information indicating whether SL unicast communication can be established between the second UE and UE2 / … / UEn;

[0290] The number of SL unicast communications that can be established between the second UE and UE2 / … / UEn.

[0291] In some embodiments, the SL positioning service UE response message is used to carry at least one of the following information of UE2 / … / UEn, the SL positioning service UE, and the second UE in the SL positioning service UE2:

[0292] RSRP information between the second UE and UE2 / … / UEn in the UE list;

[0293] Indication information indicating whether SL unicast communication can be established between the second UE and UE2 / … / UEn in the UE list;

[0294] The number of SL unicast communications that can be established between the second UE and UE2 / … / UEn in the UE list;

[0295] Among them, UE2 / … / UEn in the UE list is a subset of UE2 / … / UEn.

[0296] Step 5-3. UE1 determines the SL positioning service UE according to the SL positioning service UE response message in step 5-2;

[0297] Step 5-4. UE1 sends a SL positioning service UE confirmation message to the SL positioning service UE;

[0298] Step 5-5. UE1 sends a service UE role notification message to UE2 / … / UEn;

[0299] In some embodiments, the service UE role notification message carries identification information of the SL positioning service UE.

[0300] In some embodiments, the service UE role notification message also carries identification information of UE1.

[0301] In some embodiments, the served UE role notification message carries at least one of the following information:

[0302] SL positioning assistance information;

[0303] ·Announcement message of SL discovery process;

[0304] Request message of the SL discovery process;

[0305] NAS signaling.

[0306] Step 6: Transmit SL positioning assistance information.

[0307] In some embodiments, SL positioning assistance information is transmitted between UE1, UE2 / … / UEn and the SL positioning service UE.

[0308] Step 7. Measure SL-PRS.

[0309] In some embodiments, SL-PRS is measured between UE1 and UE2 / ... / UEn.

[0310] In some embodiments, SL-PRS is measured between UE2 / ... / UEn.

[0311] Step 8. Transmit SL-PRS measurement data and calculate ranging / SL positioning results.

[0312] In some embodiments, UE1 and / or UE2 / … / UEn transmits SL-PRS measurement data to a SL positioning service UE. The SL positioning service UE calculates a ranging / SL positioning result and sends the ranging / SL positioning result to UE1. Based on the result type received in step 1, the SL positioning service UE calculates an absolute position, a relative position, or ranging information.

[0313] In some embodiments, if UE1 supports the SL positioning service UE function, UE2 / … / UEn transmits SL-PRS measurement data to UE1, and UE1 calculates the ranging / SL positioning result. Based on the result type received in step 1, UE1 calculates the absolute position, relative position, or ranging information.

[0314] In some embodiments, UE1 sends a SL-PRS to UE2 / … / UEn, which then measures the SL-PRS. UE2 / … / UEn transmits the SL-PRS measurement data to a SL positioning service UE. The SL positioning service UE locates UE2 / … / UEn based on the SL-PRS measurement data and calculates UE1's absolute position, relative position, or ranging information.

[0315] Step 9. UE1 responds to the ranging / SL positioning service request.

[0316] Step 9a. UE1 responds to the ranging / SL positioning service request sent by the SL positioning client UE from PC5.

[0317] Step 9b. UE1 responds to the ranging / SL positioning service request from the application layer.

[0318] By adopting the second selection method of this embodiment, UE1 sends a SL positioning service UE request message to UE2 / … / UEn, SL positioning service UE, and SL positioning service UE2, so that the SL positioning service UE can be determined relatively quickly. Since UE1 needs to send SL positioning service UE request messages to multiple UEs each time, the second method of this embodiment may cause frequent signaling interactions and high signaling overhead.

[0319] The following introduces two selection methods for the target UE to select the SL positioning service UE. Different embodiments can adopt either of these two selection methods.

[0320] Option 1: Based on unicast signaling

[0321] Exemplarily, the method 1 of this embodiment is implemented based on the mode A discovery process.

[0322] FIG10 shows a schematic diagram of a communication method for an SL positioning service scenario provided by an exemplary embodiment of the present application. The method is executed by a target UE and includes at least one of the following steps:

[0323] Step 200: The target UE receives a ranging / SL positioning service request.

[0324] In some embodiments, the target UE receives a ranging / SL positioning service request sent by the SL positioning client UE.

[0325] In some embodiments, during the process of exposing ranging / SL positioning services via PC5, the SL positioning client UE is positioned via PC5, that is, the SL positioning client sends a ranging / SL positioning service request to the target UE via the PC5 interface.

[0326] In some embodiments, for absolute positioning, the ranging / SL positioning service request includes the user information of the SL positioning client UE and the user information of the target UE, as well as the required positioning QoS.

[0327] In some embodiments, for relative position or ranging information, the ranging / SL positioning service request includes user information of the SL positioning client UE, user information of the target UE, user information of the anchor UE and ranging / SL positioning QoS information.

[0328] In some embodiments, the target UE receives a ranging / SL positioning service request from the application layer.

[0329] In some embodiments, the ranging / SL positioning service request includes a result type and a required QoS, wherein the result type includes absolute position, relative position, or ranging information.

[0330] Step 210: The target UE sends a capability request message to multiple UEs.

[0331] In some embodiments, during the capability exchange process, the target UE sends a capability request message to multiple UEs.

[0332] In some embodiments, the capability exchange process is also referred to as at least one of an exchange process, a capability interaction process, a SL positioning capability exchange process, and a SL positioning capability interaction process.

[0333] In some embodiments, the capability request message is also called at least one of a request message, an exchange request message, an interaction request message, a capability exchange request message, a capability interaction request message, a SL positioning capability request message, a SL positioning capability exchange request message, and a SL positioning capability interaction request message.

[0334] In some embodiments, the plurality of UEs include an anchor UE and / or other UEs other than the anchor UE and the target UE.

[0335] In some embodiments, the first UE is one UE among a plurality of UEs.

[0336] In some embodiments, the plurality of UEs are UEs that perform capability exchange with a target UE.

[0337] In some embodiments, the capability request message is further used to instruct a first UE among the multiple UEs to return at least one of the following information to the target UE:

[0338] RSRP information between the first UE and at least one anchor UE;

[0339] Indication information indicating whether SL unicast communication can be established between the first UE and at least one anchor UE;

[0340] The number of SL unicast communications that can be established between the first UE and at least one anchor UE.

[0341] In some embodiments, each RSRP between the first UE and the anchor UE may be represented by n bits.

[0342] In some embodiments, the n bits corresponding to RSRP are used to represent the absolute value of RSRP. The absolute value of RSRP corresponds to the number of bits in a one-to-one correspondence.

[0343] In some embodiments, the indication information of whether SL unicast communication can be established between the first UE and the anchor UE can be represented by a bit sequence (bitmap). Each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the first UE and each anchor UE.

[0344] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the first UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0345] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the first UE and the anchor UE is 0, indicating that SL unicast communication cannot be established between the first UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the first UE and the anchor UE is 1, indicating that SL unicast communication can be established between the first UE and the anchor UE.

[0346] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the first UE and the anchor UE is 0, indicating that SL unicast communication can be established between the first UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the first UE and the anchor UE is 1, indicating that SL unicast communication cannot be established between the first UE and the anchor UE.

[0347] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0348] In some embodiments, the capability request message also carries RSRP threshold information.

[0349] In some embodiments, when the RSRP between the first UE and the anchor UE is greater than the RSRP threshold, the requirements for establishing SL unicast communication are met, and SL unicast communication can be established between the first UE and the anchor UE. The indication information is used to indicate that SL unicast communication can be established between the first UE and the anchor UE.

[0350] In some embodiments, when the RSRP between the first UE and the anchor UE is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the first UE and the anchor UE. The indication information is used to indicate that SL unicast communication cannot be established between the first UE and the anchor UE.

[0351] In some embodiments, when the RSRP between the first UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is 1. When the RSRP between the first UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is 0.

[0352] In some embodiments, when the RSRP between the first UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is 0. When the RSRP between the first UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is 1.

[0353] In some embodiments, the number of SL unicast communications that can be established between the first UE and the anchor UEs can be represented by a bit sequence, where each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the first UE and each anchor UE.

[0354] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the first UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0355] In some embodiments, the number of SL unicast communications that can be established between the first UE and the anchor UE can be represented by a code point. The number of SL unicast communications that can be established between the first UE and the anchor UE has a one-to-one correspondence with the value of the code point.

[0356] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the first UE and the anchor UE. For example, 001 represents that the number of SL unicast communications that can be established between the first UE and the anchor UE is 1, and 010 represents that the number of SL unicast communications that can be established between the first UE and the anchor UE is 2.

[0357] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the first UE and the anchor UE, which can be determined through negotiation, or agreed upon by protocol, or indicated by the target UE in a capability request message.

[0358] In some embodiments, the capability request message is further used to instruct a first UE among the multiple UEs to return at least one of the following information to the target UE:

[0359] RSRP information between the first UE and each anchor UE in the UE list;

[0360] Indication information indicating whether SL unicast communication can be established between the first UE and each anchor UE in the UE list;

[0361] The number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list;

[0362] The anchor UEs in the UE list are a subset of the anchor UEs.

[0363] In some embodiments, the UE list is a subset of the set of at least one anchor UE.

[0364] In some embodiments, the first UE is one of a plurality of UEs.

[0365] In some embodiments, the plurality of UEs are UEs that perform capability exchange with a target UE.

[0366] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0367] In some embodiments, the capability request message also carries RSRP threshold information.

[0368] In some embodiments, when the RSRP between the first UE and an anchor UE in the UE list is greater than an RSRP threshold, the requirement for establishing SL unicast communication is met, and SL unicast communication can be established between the first UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication can be established between the first UE and the anchor UE in the UE list.

[0369] In some embodiments, when the RSRP between the first UE and an anchor UE in the UE list is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the first UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication cannot be established between the first UE and the anchor UE in the UE list.

[0370] In some embodiments, when the RSRP between the first UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 1. When the RSRP between the first UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 0.

[0371] In some embodiments, when the RSRP between the first UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the first UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[0372] In some embodiments, the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the first UE and each anchor UE.

[0373] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the first UE and the i-th anchor UE in the UE list, wherein the i-th anchor UE is an anchor UE in the UE list.

[0374] In some embodiments, the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list can be represented by a code point. The number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list corresponds to the value of the code point.

[0375] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list. For example, 001 represents that the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list is 1, and 010 represents that the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list is 2.

[0376] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the first UE and the anchor UE in the UE list, which can be determined through negotiation, or through protocol agreement, or indicated by the target UE in the capability request message.

[0377] In some embodiments, the first UE among the plurality of UEs includes a UE among the anchor UEs and / or a UE among other UEs except the anchor UE and the target UE.

[0378] In some embodiments, RSRP information is obtained based on measurements of announcement messages in the SL discovery process.

[0379] In some embodiments, the RSRP information is obtained based on measurements of request messages in the SL discovery process.

[0380] In some embodiments, the indication information is indicated by at least one of numbers, letters, symbols, and bits.

[0381] In some embodiments, step 210 is performed after step 2. UE1 discovers UE2 / ... / UEn.

[0382] In some embodiments, step 210 is performed during step 4: UE1 and UE2 / ... / UEn perform capability exchange.

[0383] Step 220: The target UE receives capability response messages returned by multiple UEs.

[0384] In some embodiments, during the capability exchange process, the target UE receives capability response messages returned by multiple UEs.

[0385] In some embodiments, the capability exchange process is also referred to as at least one of an exchange process, a capability interaction process, a SL positioning capability exchange process, and a SL positioning capability interaction process.

[0386] In some embodiments, the capability response message is also referred to as at least one of a response message, an exchange response message, an interaction response message, a capability exchange response message, and a capability interaction response message.

[0387] In some embodiments, the plurality of UEs include an anchor UE, and / or other UEs other than the anchor UE and the target UE.

[0388] In some embodiments, the capability response message is further used to carry at least one of the following information of the first UE among the multiple UEs:

[0389] RSRP information between the first UE and at least one anchor UE;

[0390] Indication information indicating whether SL unicast communication can be established between the first UE and at least one anchor UE;

[0391] The number of SL unicast communications that can be established between the first UE and at least one anchor UE.

[0392] In some embodiments, the first UE is one of a plurality of UEs.

[0393] In some embodiments, the plurality of UEs are UEs that perform capability exchange with a target UE.

[0394] In some embodiments, the capability response message is further used to carry at least one of the following information of the first UE among the multiple UEs:

[0395] RSRP information between the first UE and each anchor UE in the UE list;

[0396] Indication information indicating whether SL unicast communication can be established between the first UE and each anchor UE in the UE list;

[0397] The number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list;

[0398] The anchor UEs in the UE list are a subset of the anchor UEs.

[0399] In some embodiments, the UE list is a subset of the set of at least one anchor UE.

[0400] In some embodiments, the first UE is one of a plurality of UEs.

[0401] In some embodiments, the plurality of UEs are UEs that perform capability exchange with a target UE.

[0402] In some embodiments, the first UE among the plurality of UEs includes an anchor UE, and / or a UE among other UEs other than the anchor UE and the target UE.

[0403] In some embodiments, step 220 is performed after step 2. UE1 discovers UE2 / ... / UEn.

[0404] In some embodiments, step 220 is performed during step 4: UE1 and UE2 / ... / UEn perform capability exchange.

[0405] Step 230: The target UE determines the SL positioning service UE according to the capability response message.

[0406] In some embodiments, the SL positioning service UE is a UE that undertakes the SL positioning service UE function.

[0407] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning UE, SL service UE, positioning UE, and positioning service UE.

[0408] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning service role UE, SL positioning role UE, SL service role UE, positioning role UE, positioning service role UE, and role UE.

[0409] In some embodiments, the target UE calculates the RSRP average of the first UE based on the RSRP information between the first UE and the anchor UE in the capability response information, and determines the first UE with the largest RSRP average as the SL positioning service UE.

[0410] In some embodiments, the target UE determines the number of RSRPs of the first UEs that are greater than the RSRP threshold based on the RSRP information between the first UE and the anchor UE in the capability response information, and determines the first UE with the largest number of RSRPs greater than the RSRP threshold as the SL positioning service UE.

[0411] In some embodiments, the target UE determines the number of anchor UEs with which SL unicast communication can be established based on the indication information in the capability response information indicating whether SL unicast communication can be established between the first UE and the anchor UE. The first UE that can establish SL unicast communication with the largest number of anchor UEs is determined as the SL positioning service UE.

[0412] In some embodiments, the target UE determines the first UE that can establish SL unicast communication with the largest number of anchor UEs as the SL positioning service UE based on the number of SL unicast communications that can be established between the first UE and the anchor UEs in the response capability information.

[0413] In some embodiments, the SL positioning service UE is one of the following UEs:

[0414] Target UE;

[0415] Anchor UE;

[0416] Other UEs except the target UE and anchor UE.

[0417] In some embodiments, step 230. is performed after step 2. UE1 discovers UE2 / ... / UEn.

[0418] In some embodiments, step 230 is performed during step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0419] Step 240: The target UE sends a request message to the SL positioning service UE.

[0420] In some embodiments, the request message is used to request the recipient UE to serve as a SL positioning service UE.

[0421] In some embodiments, the receiving UE is also referred to as at least one of SL positioning service receiving UE, SL positioning receiving UE, SL service receiving UE, positioning receiving UE, and positioning service receiving UE.

[0422] In some embodiments, the request message is also called at least one of SL positioning service UE request message, SL positioning service request message, SL positioning UE request message, SL positioning request message, positioning service UE request message, positioning service request message, and positioning request message.

[0423] In some embodiments, step 240 is performed after step 2. UE1 discovers UE2 / ... / UEn.

[0424] In some embodiments, step 240 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0425] Step 250: The target UE receives the response message returned by the SL positioning service UE.

[0426] In some embodiments, the response message is used to indicate whether the receiving UE agrees to serve as a SL positioning service UE.

[0427] In some embodiments, the response message is also called at least one of SL positioning service UE response message, SL positioning service response message, SL positioning UE response message, SL positioning response message, positioning service UE response message, positioning service response message, and positioning response message.

[0428] In some embodiments, the response message includes a first bit, the bit value of which is used to indicate whether the receiving UE agrees to serve as a SL positioning service UE. The first bit is one of the bits corresponding to the response message.

[0429] In some embodiments, the bit value corresponding to the first bit is 0, indicating that the receiving UE does not agree to serve as a SL positioning service UE. The bit value corresponding to the first bit is 1, indicating that the receiving UE agrees to serve as a SL positioning service UE.

[0430] In some embodiments, the bit value corresponding to the first bit is 1, indicating that the receiving UE does not agree to serve as a SL positioning service UE. The bit value corresponding to the first bit is 0, indicating that the receiving UE agrees to serve as a SL positioning service UE.

[0431] In some embodiments, when the response message indicates that the recipient UE does not agree to serve as the SL positioning service UE, the target UE redetermines the SL positioning service UE.

[0432] In some embodiments, when the target UE does not receive a response message, the target UE re-determines the SL positioning service UE.

[0433] Step 260: The target UE sends a notification message to the anchor UE.

[0434] In some embodiments, the notification message is used to indicate the SL positioning service UE that assumes the SL positioning service UE function.

[0435] In some embodiments, the notification message is also called at least one of SL positioning service UE notification message, SL positioning service notification message, SL positioning UE notification message, SL positioning notification message, positioning service UE notification message, positioning service notification message, and positioning notification message.

[0436] In some embodiments, the notification message is also called at least one of SL positioning service UE role notification message, SL positioning service role notification message, SL positioning UE role notification message, SL positioning role notification message, positioning service UE role notification message, positioning service role notification message, and positioning role notification message.

[0437] In some embodiments, the notification message carries identification information of the SL positioning service UE.

[0438] In some embodiments, the notification message also carries identification information of the target UE.

[0439] In some embodiments, the notification message also carries a positioning session identifier (SLPP Session ID) information, which is used to indicate that for a specific positioning session and / or a specific ranging / SL positioning service request, the SL positioning service UE assumes the SL positioning service UE function. The positioning session identifier information is used to distinguish different positioning sessions or ranging / SL positioning service requests.

[0440] In some embodiments, the identification information includes user information.

[0441] In some embodiments, the user information may be a user ID.

[0442] In some embodiments, the user information may be a layer-2 ID.

[0443] In some embodiments, the user information may be an application layer ID.

[0444] In some embodiments, the notification message may be sent via at least one of broadcast, unicast, and multicast.

[0445] In some embodiments, the notification message carries at least one of the following information:

[0446] SLPP Positioning Assistant Data;

[0447] ·Announcement message of SL discovery process;

[0448] Request message of the SL discovery process;

[0449] NAS (None Access Stratum) signaling

[0450] In some embodiments, the notification message is carried in metadata of the announcement message and / or the request message to save signaling interaction.

[0451] In some embodiments, the notification message is carried in the metadata of the announcement message. For example, the role of the announced UE is indicated as the target UE, without indicating the serving UE role, and the metadata carries the identification information of the SL positioning service UE to save signaling interaction.

[0452] In some embodiments, the target UE may have different positioning service requests. In order to further distinguish the positioning session or ranging / SL positioning service request to which the SL positioning service UE belongs, the notification message may also carry positioning session identification information.

[0453] In some embodiments, the notification message is carried in the SL positioning assistance information. The SL positioning assistance information is sent in a broadcast or multicast manner. By carrying the notification message in the SL positioning assistance information, even if the target UE may have different positioning service requests, the SL positioning assistance information itself is within a certain positioning session, so there is no need to additionally indicate the positioning session identification information, and no new signaling can be introduced, which is used to save signaling interaction.

[0454] In some embodiments, step 260 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange. In this embodiment, steps 210, 220, 230, 240, 250, and 260 are optional. In different embodiments, one or more of these steps may be omitted or replaced. Steps 210, 220, 230, 240, 250, and 260 may be performed in a swapped order or simultaneously.

[0455] Step 210 and step 220 can be implemented as independent embodiments; step 240 and step 250 can be implemented as independent embodiments; step 230 and step 260 can be implemented as independent embodiments; steps 210 to 230 can be implemented as independent embodiments; steps 210, 220, and 260 can be implemented as independent embodiments; steps 240 to 260 can be implemented as independent embodiments; steps 210, 220, 230, and 260 can be implemented as independent embodiments; steps 230, 240, 250, and 260 can be implemented as independent embodiments; but are not limited to this.

[0456] Step 230 can be implemented as an independent embodiment, such as being implemented separately as a determination method and an information determination method for SL positioning service UE; step 260 can be implemented as an independent embodiment, such as being implemented separately as a notification method, an information determination method, an information sending method, and a notification message sending method for SL positioning service UE; steps 210 and 220 can be implemented as independent embodiments, such as being implemented separately as a capability notification method and a capability information determination method; steps 240 and 250 can be implemented as independent embodiments, such as being implemented separately as an information determination method and a determination method for SL positioning service UE; steps 230 and 260 can be implemented as independent embodiments, such as being implemented separately as a notification method, an information determination method, an information sending method, and a notification message sending method for SL positioning service UE; steps Steps 210 to 230 can be implemented as independent embodiments, such as being implemented separately as an information determination method or a method for determining the SL positioning service UE; steps 210, 220, and 260 can be implemented as independent embodiments, such as being implemented separately as a method for sending a notification message; steps 240 to 260 can be implemented as independent embodiments, such as being implemented separately as a method for sending a notification message; steps 210, 220, 230, and 260 can be implemented as independent embodiments, such as being implemented separately as an information determination method or a method for sending a notification message; steps 230, 240, 250, and 260 can be implemented as independent embodiments, such as being implemented separately as a notification method, an information determination method, an information sending method, and a method for sending a notification message of the SL positioning service UE.

[0457] Based on the selection method 1 provided in this embodiment, the target UE may determine the SL positioning service UE based on at least one of the following methods:

[0458] Method 1: The target UE determines the SL positioning service UE based on the RSRP information between the first UE and the anchor UE. In this method, the target UE can obtain richer auxiliary information and evaluate the channel transmission quality between the first UE and each anchor UE to determine the SL positioning service UE.

[0459] Method 2: The target UE determines the SL location service UE based on the indication information indicating whether SL unicast communication can be established between the first UE and the anchor UE. In this method, the target UE can evaluate the channel transmission quality between the first UE and each anchor UE and then determine the SL location service UE. Compared with method 1, the signaling overhead is significantly reduced.

[0460] Method three: The target UE determines the SL positioning service UE based on the number of SL unicast communications that can be established between the first UE and the anchor UE. In this method, the target UE can evaluate the channel transmission quality between the first UE and each anchor UE, and then determine the SL positioning service UE. Compared with methods one and two, the signaling overhead is further reduced. The above-mentioned selection method one provided in this embodiment, by introducing the three types of auxiliary information selected by the above-mentioned SL positioning service UE, can help the target UE select the SL positioning service UE that can establish more unicast connections with the anchor UE, which is conducive to the exchange of SL positioning auxiliary information and SL-PRS measurement data. When the target UE determines the SL positioning service UE, the target UE sends a notification message to at least one anchor UE, so that at least one anchor UE can know the SL positioning service UE, and then continue with the processes of transmitting SL positioning auxiliary information and measuring SL-PRS.

[0461] Option 2: Based on SL discovery process

[0462] Exemplarily, the second method of this embodiment is implemented based on the discovery process of mode B.

[0463] FIG11 shows a schematic diagram of providing SL positioning according to an exemplary embodiment of the present application. The method is performed by the target UE and includes at least one of the following steps:

[0464] Step 300: The target UE receives a ranging / SL positioning service request.

[0465] In some embodiments, the target UE receives a ranging / SL positioning service request sent by the SL positioning client UE.

[0466] In some embodiments, during the process of exposing ranging / SL positioning services through PC5, the SL positioning client UE is positioned through PC5, that is, the SL positioning client sends a ranging / SL positioning service request to UE1 through the PC5 interface.

[0467] In some embodiments, for absolute positioning, the ranging / SL positioning service request includes the user information of the SL positioning client UE and the user information of the target UE, as well as the required positioning QoS.

[0468] In some embodiments, for relative position or ranging information, the ranging / SL positioning service request includes user information of the SL positioning client UE, user information of the target UE, user information of the anchor UE and ranging / SL positioning QoS information.

[0469] In some embodiments, the target UE receives a ranging / SL positioning service request from the application layer.

[0470] In some embodiments, the ranging / SL positioning service request includes a result type and a required QoS, wherein the result type includes absolute position, relative position, or ranging information.

[0471] Step 310: The target UE sends a request message to multiple second UEs.

[0472] In some embodiments, the second UE is one of the candidate UEs.

[0473] In some embodiments, the candidate UE is a UE that is a candidate to become a SL positioning service UE.

[0474] In some embodiments, the second UE may be at least one of an anchor UE, a UE other than the anchor UE, and a target UE.

[0475] In some embodiments, the second UE is a UE that supports SL positioning service UE function.

[0476] In some embodiments, the second UE may also be referred to as at least one of SL positioning service second UE, SL positioning second UE, SL service second UE, positioning second UE, and positioning service second UE.

[0477] In some embodiments, the request message is used to request the second UE to serve as a SL positioning service UE.

[0478] In some embodiments, the request message is also called at least one of SL positioning service UE request message, SL positioning service request message, SL positioning UE request message, SL positioning request message, positioning service UE request message, positioning service request message, and positioning request message.

[0479] In some embodiments, the request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[0480] RSRP information between the second UE and at least one anchor UE;

[0481] Indication information indicating whether SL unicast communication can be established between the second UE and at least one anchor UE;

[0482] The number of SL unicast communications that can be established between the second UE and at least one anchor UE.

[0483] In some embodiments, each RSRP between the second UE and the anchor UE may be represented by n bits.

[0484] In some embodiments, the n bits corresponding to RSRP are used to represent the absolute value of RSRP. The absolute value of RSRP corresponds to the number of bits in a one-to-one correspondence.

[0485] In some embodiments, the indication information of whether SL unicast communication can be established between the second UE and the anchor UE can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0486] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0487] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 0, indicating that SL unicast communication cannot be established between the second UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 1, indicating that SL unicast communication can be established between the second UE and the anchor UE.

[0488] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 0, indicating that SL unicast communication can be established between the second UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 1, indicating that SL unicast communication cannot be established between the second UE and the anchor UE.

[0489] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0490] In some embodiments, the request message also carries RSRP threshold information.

[0491] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the requirements for establishing SL unicast communication are met, and SL unicast communication can be established between the second UE and the anchor UE. The indication information is used to indicate that SL unicast communication can be established between the second UE and the anchor UE.

[0492] In some embodiments, when the RSRP between the second UE and the anchor UE is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the second UE and the anchor UE. The indication information is used to indicate that SL unicast communication cannot be established between the second UE and the anchor UE.

[0493] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is 1. When the RSRP between the second UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is 0.

[0494] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the second UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[0495] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs can be represented by a bit sequence, where each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0496] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0497] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UE can be represented by a code point. The number of SL unicast communications that can be established between the second UE and the anchor UE has a one-to-one correspondence with the value of the code point.

[0498] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the second UE and the anchor UE. For example, 001 represents that the number of SL unicast communications that can be established between the second UE and the anchor UE is 1, and 010 represents that the number of SL unicast communications that can be established between the second UE and the anchor UE is 2.

[0499] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the second UE and the anchor UE, which can be determined through negotiation, or agreed upon by protocol, or indicated by the target UE in the request message.

[0500] In some embodiments, the request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[0501] RSRP information between the second UE and each anchor UE in the UE list;

[0502] Indication information indicating whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[0503] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[0504] The anchor UEs in the UE list are a subset of the anchor UEs.

[0505] In some embodiments, the UE list is a subset of the set of at least one anchor UE.

[0506] In some embodiments, RSRP information is obtained based on measurements of announcement messages in the SL discovery process.

[0507] In some embodiments, the RSRP information is obtained based on measurements of request messages in the SL discovery process.

[0508] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0509] In some embodiments, the request message also carries RSRP threshold information.

[0510] In some embodiments, when the RSRP between the second UE and an anchor UE in the UE list is greater than an RSRP threshold, the requirement for establishing SL unicast communication is met, and SL unicast communication can be established between the second UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication can be established between the second UE and the anchor UE in the UE list.

[0511] In some embodiments, when the RSRP between the second UE and an anchor UE in the UE list is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the second UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication cannot be established between the second UE and the anchor UE in the UE list.

[0512] In some embodiments, when the RSRP between the second UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 1. When the RSRP between the second UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 0.

[0513] In some embodiments, when the RSRP between the second UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the second UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[0514] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0515] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE in the UE list, wherein the i-th anchor UE is an anchor UE in the UE list.

[0516] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list can be represented by a code point. The number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list corresponds to the value of the code point.

[0517] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list. For example, 001 represents that the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list is 1, and 010 represents that the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list is 2.

[0518] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the second UE and the anchor UE in the UE list, which can be determined through negotiation, or through protocol agreement, or indicated by the target UE in the request message.

[0519] In some embodiments, the indication information is indicated by at least one of numbers, letters, symbols, and bits.

[0520] In some embodiments, step 310 is performed during step 2. UE1 discovers UE2 / … / UEn.

[0521] In some embodiments, step 310 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0522] Step 320: The target UE receives response messages returned by multiple second UEs.

[0523] In some embodiments, the response message is used to indicate whether the second UE agrees to serve as a SL positioning service UE.

[0524] In some embodiments, the response message is also called at least one of SL positioning service UE response message, SL positioning service response message, SL positioning UE response message, SL positioning response message, positioning service UE response message, positioning service response message, and positioning response message.

[0525] In some embodiments, the response message is further used to carry at least one of the following information of the second UE:

[0526] RSRP information between the second UE and at least one anchor UE;

[0527] Indication information indicating whether SL unicast communication can be established between the second UE and at least one anchor UE;

[0528] The number of SL unicast communications that can be established between the second UE and at least one anchor UE.

[0529] In some embodiments, the second UE is one of the candidate UEs.

[0530] In some embodiments, the candidate UE is a UE that is a candidate to become a SL positioning service UE.

[0531] In some embodiments, the response message is further used to carry at least one of the following information of the second UE:

[0532] RSRP information between the second UE and each anchor UE in the UE list;

[0533] Indication information indicating whether SL unicast communication can be established between the second UE and the anchor UE in the UE list;

[0534] The number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list;

[0535] The anchor UEs in the UE list are a subset of the anchor UEs.

[0536] In some embodiments, the UE list is a subset of the set of at least one anchor UE.

[0537] In some embodiments, step 320 is performed during step 2. UE1 discovers UE2 / ... / UEn.

[0538] In some embodiments, step 320 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0539] Step 330: The target UE determines the SL positioning service UE.

[0540] In some embodiments, the SL positioning service UE is a UE that undertakes the SL positioning service UE function.

[0541] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning UE, SL service UE, positioning UE, and positioning service UE.

[0542] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning service role UE, SL positioning role UE, SL service role UE, positioning role UE, positioning service role UE, and role UE.

[0543] In some embodiments, the target UE calculates the RSRP average of the second UEs based on the RSRP information between the second UE and the anchor UE in the response information, and determines the second UE with the largest RSRP average as the SL positioning service UE.

[0544] In some embodiments, the target UE determines the number of RSRPs of the second UEs that are greater than the RSRP threshold based on the RSRP information between the second UE and the anchor UE in the response information, and determines the second UE with the largest number of RSRPs greater than the RSRP threshold as the SL positioning service UE.

[0545] In some embodiments, the target UE determines the number of anchor UEs with which SL unicast communication can be established with the second UE based on the indication information in the response information as to whether SL unicast communication can be established between the second UE and the anchor UE. The second UE with which SL unicast communication can be established with the largest number of anchor UEs is determined as the SL positioning service UE.

[0546] In some embodiments, the target UE determines the second UE that can establish SL unicast communication with the largest number of anchor UEs as the SL positioning service UE based on the number of second UEs and anchor UEs that can establish SL unicast communication in the response information.

[0547] In some embodiments, the SL positioning service UE is one of the following UEs:

[0548] Target UE;

[0549] Anchor UE;

[0550] Other UEs except the target UE and anchor UE.

[0551] In some embodiments, the target UE determines the SL positioning service UE based on the response message.

[0552] In some embodiments, step 330 is performed during step 2. UE1 discovers UE2 / … / UEn.

[0553] In some embodiments, step 330 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0554] Step 340: The target UE sends a confirmation message to the SL positioning service UE.

[0555] In some embodiments, the confirmation message is used to confirm that the recipient UE is a SL positioning service UE.

[0556] In some embodiments, the confirmation message is also called at least one of SL positioning service UE confirmation message, SL positioning service confirmation message, SL positioning UE confirmation message, SL positioning confirmation message, positioning service UE confirmation message, positioning service confirmation message, and positioning confirmation message.

[0557] In some embodiments, the confirmation message is also called at least one of SL positioning service UE role confirmation message, SL positioning service role confirmation message, SL positioning UE role confirmation message, SL positioning role confirmation message, positioning service UE role confirmation message, positioning service role confirmation message, and positioning role confirmation message.

[0558] In some embodiments, step 340 is performed during step 2. UE1 discovers UE2 / ... / UEn.

[0559] In some embodiments, step 340 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0560] Step 350: The target UE sends a notification message to the anchor UE.

[0561] In some embodiments, the notification message is used to indicate the SL positioning service UE that assumes the SL positioning service UE function.

[0562] In some embodiments, the notification message is also called at least one of SL positioning service UE notification message, SL positioning service notification message, SL positioning UE notification message, SL positioning notification message, positioning service UE notification message, positioning service notification message, and positioning notification message.

[0563] In some embodiments, the notification message is also called at least one of SL positioning service UE role notification message, SL positioning service role notification message, SL positioning UE role notification message, SL positioning role notification message, positioning service UE role notification message, positioning service role notification message, and positioning role notification message.

[0564] In some embodiments, the notification message carries identification information of the SL positioning service UE.

[0565] In some embodiments, the notification message also carries identification information of the target UE.

[0566] In some embodiments, the identification information includes user information.

[0567] In some embodiments, the user information may be a user ID.

[0568] In some embodiments, the user information may be a layer-2 ID.

[0569] In some embodiments, the user information may be an application layer ID.

[0570] In some embodiments, the notification message may be sent via at least one of broadcast, unicast, and multicast.

[0571] In some embodiments, the notification message carries at least one of the following information:

[0572] SLPP Positioning Assistant Data;

[0573] ·Announcement message of SL discovery process;

[0574] Request message of the SL discovery process;

[0575] NAS signaling.

[0576] In some embodiments, the notification message is carried in metadata of the announcement message and / or the request message to save signaling interaction.

[0577] In some embodiments, the notification message is carried in the metadata of the announcement message. For example, the role of the announced UE is indicated as the target UE, the SL positioning service UE role is not indicated, and the identification information of the SL positioning service UE is carried in the metadata to save signaling interaction.

[0578] In some embodiments, the target UE may have different positioning service requests. In order to further distinguish the positioning session or ranging / SL positioning service request to which the SL positioning service UE belongs, the notification message may also carry positioning session identification information.

[0579] In some embodiments, the notification message is carried in the SL positioning assistance information. The SL positioning assistance information is sent in a broadcast or multicast manner. By carrying the notification message in the SL positioning assistance information, even if the target UE may have different positioning service requests, the SL positioning assistance information itself is within a certain positioning session, so there is no need to additionally indicate the positioning session identification information, and no new signaling can be introduced, which is used to save signaling interaction.

[0580] In some embodiments, step 350 is performed after step 2. UE1 discovers UE2 / ... / UEn.

[0581] In some embodiments, step 350 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0582] In this embodiment, step 310, step 320, step 330, step 340, and step 350 are optional. In different embodiments, one or more of these steps may be omitted or replaced, and step 310, step 320, step 330, step 340, and step 350 may be executed in an interchangeable order or simultaneously. Step 310 and step 320 can be implemented as independent embodiments; step 330 and step 340 can be implemented as independent embodiments; step 340 and step 350 can be implemented as independent embodiments; steps 310 to step 330 can be implemented as independent embodiments; step 310, step 320, and step 340 can be implemented as independent embodiments; step 310, step 320, and step 350 can be implemented as independent embodiments; step 330, step 340, and step 350 can be implemented as independent embodiments; step 310, step 320, step 330, and step 340 can be implemented as independent embodiments; step 310, step 320, step 330, and step 350 can be implemented as independent embodiments, but are not limited to this.

[0583] Step 330 can be implemented as an independent embodiment, such as being implemented separately as a determination method and information determination method of SL positioning service UE; step 350 can be implemented as an independent embodiment, such as being implemented separately as a notification method, information determination method, information sending method, and notification message sending method of SL positioning service UE; steps 310 and 320 can be implemented as independent embodiments, such as being implemented separately as an information determination method and a message sending method; steps 330 and 340 can be implemented as independent embodiments, such as being implemented separately as an information determination method and a determination method of SL positioning service UE; steps 340 and 350 can be implemented as independent embodiments, such as being implemented separately as a notification method, information determination method, information sending method, and notification message sending method of SL positioning service UE; steps 310 to 330 can be implemented as independent embodiments, such as being implemented separately as an information determination method and a determination method of SL positioning service UE; step 31 0 and step 320 and step 340 can be implemented as independent embodiments, such as being implemented separately as the confirmation method and information sending method of the SL positioning service UE; step 310 and step 320 and step 350 can be implemented as independent embodiments, such as being implemented separately as the notification method, information determination method, information sending method, and notification message sending method of the SL positioning service UE; step 330 and step 340 and step 350 can be implemented as independent embodiments, such as being implemented separately as the information determination method and the determination method of the SL positioning service UE; step 310 and step 320 and step 330 and step 340 can be implemented as independent embodiments, such as being implemented separately as the information determination method and the determination method of the SL positioning service UE; step 310 and step 320 and step 330 and step 350 can be implemented as independent embodiments, such as being implemented separately as the notification method, information determination method, information sending method, and notification message sending method of the SL positioning service UE.

[0584] Based on the second selection method provided in this embodiment, the target UE may determine the SL positioning service UE based on at least one of the following methods:

[0585] Method 1: The target UE determines the SL positioning service UE based on the RSRP information between the second UE and the anchor UE. In this method, the target UE can obtain richer auxiliary information and evaluate the channel transmission quality between the second UE and each anchor UE to determine the SL positioning service UE.

[0586] Method 2: The target UE determines the SL location service UE based on the indication information indicating whether SL unicast communication can be established between the second UE and the anchor UE. In this method, the target UE can evaluate the channel transmission quality between the second UE and each anchor UE and then determine the SL location service UE. Compared with Method 1, the signaling overhead is significantly reduced.

[0587] Method 3: The target UE determines the SL location service UE based on the number of SL unicast communications that can be established between the second UE and the anchor UE. In this method, the target UE can evaluate the channel transmission quality between the second UE and each anchor UE to determine the SL location service UE. Compared with Methods 1 and 2, the signaling overhead is further reduced.

[0588] The second selection method of this embodiment introduces the three types of auxiliary information selected by the SL positioning service UE, which can help the target UE select the SL positioning service UE, and is conducive to the exchange of SL positioning auxiliary information and SL-PRS measurement data. When the target UE determines the SL positioning service UE, the target UE sends a notification message to at least one anchor UE, so that the at least one anchor UE can know the SL positioning service UE, and then continue the process of transmitting SL positioning auxiliary information and measuring SL-PRS.

[0589] FIG12 shows a schematic diagram of a communication method for a SL positioning service scenario provided by an exemplary embodiment of the present application, the method being performed by a second UE. The method includes at least one of the following steps:

[0590] Step 410: The second UE receives the request message sent by the target UE.

[0591] In some embodiments, the second UE is one of the candidate UEs.

[0592] In some embodiments, the candidate UE is a UE that is a candidate to become a SL positioning service UE.

[0593] In some embodiments, the second UE may be at least one of an anchor UE, a UE other than the anchor UE, and a target UE.

[0594] In some embodiments, the second UE is a UE that supports SL positioning service UE function.

[0595] In some embodiments, the second UE may also be referred to as at least one of SL positioning service second UE, SL positioning second UE, SL service second UE, positioning second UE, and positioning service second UE.

[0596] In some embodiments, the request message is used to request the second UE to serve as a SL positioning service UE.

[0597] In some embodiments, the request message is also called at least one of SL positioning service UE request message, SL positioning service request message, SL positioning UE request message, SL positioning request message, positioning service UE request message, positioning service request message, and positioning request message.

[0598] In some embodiments, the request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[0599] RSRP information between the second UE and at least one anchor UE;

[0600] Indication information indicating whether SL unicast communication can be established between the second UE and at least one anchor UE;

[0601] The number of SL unicast communications that can be established between the second UE and at least one anchor UE.

[0602] In some embodiments, the request message further comprises a capability request message.

[0603] In some embodiments, during the capability exchange process, the second UE receives a capability request message sent by the target UE.

[0604] In some embodiments, the capability exchange process is also referred to as at least one of an exchange process, a capability interaction process, a SL positioning capability exchange process, and a SL positioning capability interaction process.

[0605] In some embodiments, the capability request message is also called at least one of a request message, an exchange request message, an interaction request message, a capability exchange request message, a capability interaction request message, a SL positioning capability request message, a SL positioning capability exchange request message, and a SL positioning capability interaction request message.

[0606] In some embodiments, the capability request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[0607] RSRP information between the second UE and at least one anchor UE;

[0608] Indication information indicating whether SL unicast communication can be established between the second UE and at least one anchor UE;

[0609] The number of SL unicast communications that can be established between the second UE and at least one anchor UE.

[0610] In some embodiments, each RSRP between the second UE and the anchor UE may be represented by n bits.

[0611] In some embodiments, the n bits corresponding to RSRP are used to represent the absolute value of RSRP. The absolute value of RSRP corresponds to the number of bits in a one-to-one correspondence.

[0612] In some embodiments, the indication information of whether SL unicast communication can be established between the second UE and the anchor UE can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0613] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0614] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 0, indicating that SL unicast communication cannot be established between the second UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 1, indicating that SL unicast communication can be established between the second UE and the anchor UE.

[0615] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 0, indicating that SL unicast communication can be established between the second UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 1, indicating that SL unicast communication cannot be established between the second UE and the anchor UE.

[0616] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0617] In some embodiments, the request message also carries RSRP threshold information.

[0618] In some embodiments, the capability request message also carries RSRP threshold information.

[0619] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the requirements for establishing SL unicast communication are met, and SL unicast communication can be established between the second UE and the anchor UE. The indication information is used to indicate that SL unicast communication can be established between the second UE and the anchor UE.

[0620] In some embodiments, when the RSRP between the second UE and the anchor UE is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the second UE and the anchor UE. The indication information is used to indicate that SL unicast communication cannot be established between the second UE and the anchor UE.

[0621] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is 1. When the RSRP between the second UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is 0.

[0622] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the second UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[0623] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs can be represented by a bit sequence, where each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0624] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0625] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UE can be represented by a code point. The number of SL unicast communications that can be established between the second UE and the anchor UE has a one-to-one correspondence with the value of the code point.

[0626] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the second UE and the anchor UE. For example, 001 represents that the number of SL unicast communications that can be established between the second UE and the anchor UE is 1, and 010 represents that the number of SL unicast communications that can be established between the second UE and the anchor UE is 2.

[0627] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the second UE and the anchor UE, which can be determined through negotiation, or agreed upon by protocol, or indicated by the target UE in the request message.

[0628] In some embodiments, the request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[0629] RSRP information between the second UE and each anchor UE in the UE list;

[0630] Indication information indicating whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[0631] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[0632] The anchor UEs in the UE list are a subset of the anchor UEs.

[0633] In some embodiments, the UE list is a subset of the set of at least one anchor UE.

[0634] In some embodiments, the capability request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[0635] RSRP information between the second UE and each anchor UE in the UE list;

[0636] Indication information indicating whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[0637] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[0638] The anchor UEs in the UE list are a subset of the anchor UEs.

[0639] In some embodiments, the UE list is a subset of the set of at least one anchor UE.

[0640] In some embodiments, RSRP information is obtained based on measurements of announcement messages in the SL discovery process.

[0641] In some embodiments, the RSRP information is obtained based on measurements of request messages in the SL discovery process.

[0642] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0643] In some embodiments, the request message also carries RSRP threshold information.

[0644] In some embodiments, when the RSRP between the second UE and an anchor UE in the UE list is greater than an RSRP threshold, the requirement for establishing SL unicast communication is met, and SL unicast communication can be established between the second UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication can be established between the second UE and the anchor UE in the UE list.

[0645] In some embodiments, when the RSRP between the second UE and an anchor UE in the UE list is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the second UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication cannot be established between the second UE and the anchor UE in the UE list.

[0646] In some embodiments, when the RSRP between the second UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 1. When the RSRP between the second UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 0.

[0647] In some embodiments, when the RSRP between the second UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the second UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[0648] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0649] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE in the UE list, wherein the i-th anchor UE is an anchor UE in the UE list.

[0650] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list can be represented by a code point. The number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list corresponds to the value of the code point.

[0651] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list. For example, 001 represents that the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list is 1, and 010 represents that the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list is 2.

[0652] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the second UE and the anchor UE in the UE list, which can be determined through negotiation, or through protocol agreement, or indicated by the target UE in the request message.

[0653] In some embodiments, the indication information is indicated by at least one of numbers, letters, symbols, and bits.

[0654] In some embodiments, step 410 is performed during step 2. UE1 discovers UE2 / ... / UEn.

[0655] In some embodiments, step 410 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0656] Step 420: The second UE sends a response message to the target UE.

[0657] In some embodiments, the response message carries information used by the target UE to determine the SL location serving UE.

[0658] In some embodiments, the response message is also called at least one of SL positioning service UE response message, SL positioning service response message, SL positioning UE response message, SL positioning response message, positioning service UE response message, positioning service response message, and positioning response message.

[0659] In some embodiments, the response message is further used to carry at least one of the following information of the second UE:

[0660] RSRP information between the second UE and at least one anchor UE;

[0661] Indication information indicating whether SL unicast communication can be established between the second UE and at least one anchor UE;

[0662] The number of SL unicast communications that can be established between the second UE and at least one anchor UE.

[0663] In some embodiments, the response message is further used to carry at least one of the following information of the second UE:

[0664] RSRP information between the second UE and each anchor UE in the UE list;

[0665] Indication information indicating whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[0666] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[0667] The anchor UEs in the UE list are a subset of the anchor UEs.

[0668] In some embodiments, the UE list is a subset of the set of at least one anchor UE.

[0669] In some embodiments, the response message also includes a capability response message.

[0670] In some embodiments, during the capability exchange process, the second UE returns a capability response message to the target UE.

[0671] In some embodiments, the capability exchange process is also referred to as at least one of an exchange process, a capability interaction process, a SL positioning capability exchange process, and a SL positioning capability interaction process.

[0672] In some embodiments, the capability response message is also referred to as at least one of a response message, an exchange response message, an interaction response message, a capability exchange response message, and a capability interaction response message.

[0673] In some embodiments, the capability response message is further used to carry at least one of the following information of the second UE:

[0674] RSRP information between the second UE and at least one anchor UE;

[0675] Indication information indicating whether SL unicast communication can be established between the second UE and at least one anchor UE;

[0676] The number of SL unicast communications that can be established between the second UE and at least one anchor UE.

[0677] In some embodiments, the capability response message is further used to carry at least one of the following information of the second UE:

[0678] RSRP information between the second UE and each anchor UE in the UE list;

[0679] Indication information indicating whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[0680] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[0681] The anchor UEs in the UE list are a subset of the anchor UEs.

[0682] In some embodiments, the UE list is a subset of the set of at least one anchor UE.

[0683] In some embodiments, step 420 is performed during step 2. UE1 discovers UE2 / ... / UEn.

[0684] In some embodiments, step 420 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0685] In this embodiment, steps 410 and 420 are optional. In different embodiments, one or more of these steps may be omitted or replaced. Steps 410 and 420 may be swapped in order or performed simultaneously. Steps 410 and 420 may be implemented as independent embodiments, such as as separate information sending methods or message sending methods, but are not limited thereto.

[0686] By adopting the method of this embodiment, the second UE can receive the request message sent by the target UE, and the second UE can return response information to the target UE, which can help the target UE select the SL positioning service UE that supports the SL positioning service UE function, which is conducive to the interaction of SL positioning auxiliary information and SL-PRS measurement data.

[0687] FIG13 shows a schematic diagram of a communication method for a SL positioning service scenario provided by an exemplary embodiment of the present application, the method being executed by a SL positioning service UE. The method comprises at least one of the following steps:

[0688] Step 510: The SL positioning service UE receives the request message sent by the target UE.

[0689] In some embodiments, the request message is used to request the recipient UE to serve as a SL positioning service UE.

[0690] In some embodiments, the receiving UE is also referred to as at least one of SL positioning service receiving UE, SL positioning receiving UE, SL service receiving UE, positioning receiving UE, and positioning service receiving UE.

[0691] In some embodiments, the request message is also called at least one of SL positioning service UE request message, SL positioning service request message, SL positioning UE request message, SL positioning request message, positioning service UE request message, positioning service request message, and positioning request message.

[0692] In some embodiments, step 510 is performed during step 2. UE1 discovers UE2 / ... / UEn.

[0693] In some embodiments, step 510 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0694] Step 520: The SL positioning service UE sends a response message to the target UE.

[0695] In some embodiments, the response message is used to indicate whether the receiving UE agrees to serve as a SL positioning service UE.

[0696] In some embodiments, the response message is also called at least one of SL positioning service UE response message, SL positioning service response message, SL positioning UE response message, SL positioning response message, positioning service UE response message, positioning service response message, and positioning response message.

[0697] In some embodiments, the response message includes a first bit, the bit value of which is used to indicate whether the receiving UE agrees to serve as a SL positioning service UE. The first bit is one of the bits corresponding to the response message.

[0698] In some embodiments, the bit value corresponding to the first bit is 0, indicating that the receiving UE does not agree to serve as a SL positioning service UE. The bit value corresponding to the first bit is 1, indicating that the receiving UE agrees to serve as a SL positioning service UE.

[0699] In some embodiments, the bit value corresponding to the first bit is 1, indicating that the receiving UE does not agree to serve as a SL positioning service UE. The bit value corresponding to the first bit is 0, indicating that the receiving UE agrees to serve as a SL positioning service UE.

[0700] In some embodiments, when the response message indicates that the recipient UE does not agree to serve as the SL positioning service UE, the target UE redetermines the SL positioning service UE.

[0701] In some embodiments, when the target UE does not receive a response message, the target UE re-determines the SL positioning service UE.

[0702] In some embodiments, step 520 is performed during step 2. UE1 discovers UE2 / ... / UEn.

[0703] In some embodiments, step 520 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0704] Step 530: The SL positioning service UE receives a confirmation message sent by the target UE.

[0705] In some embodiments, the confirmation message is used to confirm that the recipient UE is a SL positioning service UE.

[0706] In some embodiments, the confirmation message is also called at least one of SL positioning service UE confirmation message, SL positioning service confirmation message, SL positioning UE confirmation message, SL positioning confirmation message, positioning service UE confirmation message, positioning service confirmation message, and positioning confirmation message.

[0707] In some embodiments, the confirmation message is also called at least one of SL positioning service UE role confirmation message, SL positioning service role confirmation message, SL positioning UE role confirmation message, SL positioning role confirmation message, positioning service UE role confirmation message, positioning service role confirmation message, and positioning role confirmation message.

[0708] In some embodiments, step 530 is performed during step 2. UE1 discovers UE2 / ... / UEn.

[0709] In some embodiments, step 530 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0710] Step 540: The SL positioning service UE sends a notification message to at least one anchor UE.

[0711] In some embodiments, the SL positioning service UE is a UE that undertakes the SL positioning service UE function.

[0712] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning UE, SL service UE, positioning UE, and positioning service UE.

[0713] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning service role UE, SL positioning role UE, SL service role UE, positioning role UE, positioning service role UE, and role UE.

[0714] In some embodiments, the SL positioning service UE is one of the following UEs:

[0715] Target UE;

[0716] Anchor UE;

[0717] Other UEs except the target UE and anchor UE.

[0718] In some embodiments, the notification message is used to indicate the SL positioning service UE that assumes the SL positioning service UE function.

[0719] In some embodiments, the notification message is also called at least one of SL positioning service UE notification message, SL positioning service notification message, SL positioning UE notification message, SL positioning notification message, positioning service UE notification message, positioning service notification message, and positioning notification message.

[0720] In some embodiments, the notification message is also called at least one of SL positioning service UE role notification message, SL positioning service role notification message, SL positioning UE role notification message, SL positioning role notification message, positioning service UE role notification message, positioning service role notification message, and positioning role notification message.

[0721] In some embodiments, the notification message carries identification information of the SL positioning service UE.

[0722] In some embodiments, the notification message also carries identification information of the target UE.

[0723] In some embodiments, the notification message also carries a positioning session identifier (SLPP Session ID) information, which is used to indicate that for a specific positioning session and / or a specific ranging / SL positioning service request, the SL positioning service UE assumes the SL positioning service UE function. The positioning session identifier information is used to distinguish different positioning sessions or ranging / SL positioning service requests.

[0724] In some embodiments, the identification information includes user information.

[0725] In some embodiments, the user information may be a user ID.

[0726] In some embodiments, the user information may be a layer-2 ID.

[0727] In some embodiments, the user information may be an application layer ID.

[0728] In some embodiments, the notification message may be sent via at least one of broadcast, unicast, and multicast.

[0729] In some embodiments, the notification message does not carry identification information of the SL positioning service UE.

[0730] In some embodiments, the notification message is also used to indicate that the SL positioning service UE is this UE.

[0731] In some embodiments, when the identification information of the SL positioning service UE in the notification message does not exist, it is understood that the SL positioning service UE indicated is the current UE.

[0732] In some embodiments, when the identification information of the SL positioning service UE in the notification message is a special ID, it is understood that the SL positioning service UE indicates this UE.

[0733] In some embodiments, the notification message carries bit indication information. When the bit value of the bit indication information is 1 or true, it indicates that the SL positioning service UE indication is this UE.

[0734] In the above case, the notification message may not carry the identification information of the SL positioning service UE, saving signaling overhead.

[0735] In some embodiments, the notification message carries bit indication information. When the bit value of the bit indication information is 0 or false, or the notification message does not carry the bit indication information, the notification message needs to carry complete identification information of the SL positioning service UE.

[0736] In some embodiments, the notification message carries at least one of the following information:

[0737] SLPP Positioning Assistant Data;

[0738] ·Announcement message of SL discovery process;

[0739] Request message of the SL discovery process;

[0740] NAS (None Access Stratum) signaling

[0741] In some embodiments, the notification message is carried in metadata of the announcement message and / or the request message to save signaling interaction.

[0742] In some embodiments, the roles of the declared UE include target UE, SL positioning service UE, anchor UE, and anchor UE that can obtain its own position. Declaring the UE role as a SL positioning service UE means that the declared UE can assume the functions of a SL positioning service UE. However, it does not determine the SL positioning service UE for a specific SL positioning service request.

[0743] In some embodiments, the notification message is carried in the metadata of the declaration message, and by introducing a new UE role, such as "authorized service UE" or "confirmed service UE", it implicitly indicates that it is a SL positioning service UE, which is used to save signaling interaction.

[0744] In some embodiments, the notification message is carried in the SL positioning assistance information. The SL positioning assistance information is sent in a broadcast or multicast manner. The SL positioning service UE carries the notification message in the SL positioning assistance information. Even if the target UE may have different positioning service requests, the SL positioning assistance information itself is within a certain positioning session. Therefore, there is no need to additionally indicate the positioning session identification information, and no new signaling may be introduced, thereby saving signaling interaction.

[0745] In some embodiments, step 540 is performed after step 2. UE1 discovers UE2 / ... / UEn.

[0746] In some embodiments, step 540 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0747] In this embodiment, steps 510, 520, 530, and 540 are optional. In different embodiments, one or more of these steps may be omitted or replaced. Steps 510, 520, 530, and 540 may be performed in a swapped order or simultaneously. Step 530 may be implemented as an independent embodiment; 540 may be implemented as an independent embodiment; steps 510 and 520 may be implemented as independent embodiments; steps 530 and 540 may be implemented as independent embodiments; steps 510, 520, and 530 may be implemented as independent embodiments; steps 510, 520, and 540 may be implemented as independent embodiments, but are not limited thereto.

[0748] Step 530 can be implemented as an independent embodiment, such as being implemented separately as a message receiving method or an information confirmation method; step 540 can be implemented as an independent embodiment, such as being implemented separately as a notification method, a notification message sending method, or an information sending method of the SL positioning service UE; steps 510 and 520 can be implemented as independent embodiments, such as being implemented separately as a message receiving method, a message sending method, or an information sending method; steps 530 and 540 can be implemented as independent embodiments, such as being implemented separately as a notification method, an information determination method, an information sending method, or a notification message sending method of the SL positioning service UE; steps 510, 520, and 530 can be implemented as independent embodiments, such as being implemented separately as a message receiving method or an information confirmation method; steps 510, 520, and 540 can be implemented as independent embodiments, such as being implemented separately as a notification method, an information determination method, an information sending method, or a notification message sending method of the SL positioning service UE.

[0749] By adopting the method of this embodiment, the SL positioning service UE can receive the confirmation message sent by the target UE, confirming that it is a SL positioning service UE, and can help the target UE select a SL positioning service UE that supports the SL positioning service UE function, which is conducive to the exchange of SL positioning assistance information and SL-PRS measurement data. When the target UE determines the SL positioning service UE, the SL positioning service UE can also send a notification message to at least one anchor UE so that at least one anchor UE can know the SL positioning service UE, and then continue the process of transmitting SL positioning assistance information and measuring SL-PRS.

[0750] FIG14 is a schematic diagram showing a communication method for an SL positioning service scenario provided by an exemplary embodiment of the present application. The method is executed by an anchor UE and includes the following steps:

[0751] Step 710: The anchor UE receives the notification message.

[0752] In some embodiments, the anchor UE receives the notification message sent by the target UE.

[0753] In some embodiments, the anchor UE receives a notification message sent by the SL positioning service UE.

[0754] In some embodiments, the notification message is used to indicate the SL positioning service UE that assumes the SL positioning service UE function.

[0755] In some embodiments, the notification message is also called at least one of SL positioning service UE notification message, SL positioning service notification message, SL positioning UE notification message, SL positioning notification message, positioning service UE notification message, positioning service notification message, and positioning notification message.

[0756] In some embodiments, the notification message is also called at least one of SL positioning service UE role notification message, SL positioning service role notification message, SL positioning UE role notification message, SL positioning role notification message, positioning service UE role notification message, positioning service role notification message, and positioning role notification message.

[0757] In some embodiments, the notification message carries identification information of the SL positioning service UE.

[0758] In some embodiments, the notification message also carries identification information of the target UE.

[0759] In some embodiments, the notification message also carries a positioning session identifier (SLPP Session ID) information, which is used to indicate that for a specific positioning session and / or a specific ranging / SL positioning service request, the SL positioning service UE assumes the SL positioning service UE function. The positioning session identifier information is used to distinguish different positioning sessions or ranging / SL positioning service requests.

[0760] In some embodiments, the identification information includes user information.

[0761] In some embodiments, the user information may be a user ID.

[0762] In some embodiments, the user information may be a layer-2 ID.

[0763] In some embodiments, the user information may be an application layer ID.

[0764] In some embodiments, the notification message may be sent via at least one of broadcast, unicast, and multicast.

[0765] In some embodiments, the notification message does not carry identification information of the SL positioning service UE.

[0766] In some embodiments, the notification message is also used to indicate that the SL positioning service UE is this UE.

[0767] In some embodiments, when the identification information of the SL positioning service UE in the notification message does not exist, it is understood that the SL positioning service UE indicated is the current UE.

[0768] In some embodiments, when the identification information of the SL positioning service UE in the notification message is a special ID, it is understood that the SL positioning service UE indicates this UE.

[0769] In some embodiments, the notification message carries bit indication information. When the bit value of the bit indication information is 1 or true, it indicates that the SL positioning service UE indication is this UE.

[0770] In the above case, the notification message may not carry the identification information of the SL positioning service UE, saving signaling overhead.

[0771] In some embodiments, the notification message carries bit indication information. When the bit value of the bit indication information is 0 or false, or the notification message does not carry the bit indication information, the notification message needs to carry complete identification information of the SL positioning service UE.

[0772] In some embodiments, the notification message carries at least one of the following information:

[0773] SLPP Positioning Assistant Data;

[0774] ·Announcement message of SL discovery process;

[0775] Request message of the SL discovery process;

[0776] NAS (None Access Stratum) signaling

[0777] In some embodiments, the roles of the declared UE include target UE, SL positioning service UE, anchor UE, and anchor UE that can obtain its own position. Declaring the UE role as a SL positioning service UE means that the declared UE can assume the functions of a SL positioning service UE. However, it does not determine the SL positioning service UE for a specific SL positioning service request.

[0778] In some embodiments, the notification message is carried in the metadata of the declaration message, and by introducing a new UE role, such as "authorized service UE" or "confirmed service UE", it implicitly indicates that it is a SL positioning service UE, which is used to save signaling interaction.

[0779] In some embodiments, the notification message is carried in the SL positioning assistance information. The SL positioning assistance information is sent in a broadcast or multicast manner. The SL positioning service UE carries the notification message in the SL positioning assistance information. Even if the target UE may have different positioning service requests, the SL positioning assistance information itself is within a certain positioning session. Therefore, there is no need to additionally indicate the positioning session identification information, and no new signaling may be introduced, thereby saving signaling interaction.

[0780] In some embodiments, the SL positioning service UE is a UE that undertakes the SL positioning service UE function.

[0781] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning UE, SL service UE, positioning UE, and positioning service UE.

[0782] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning service role UE, SL positioning role UE, SL service role UE, positioning role UE, positioning service role UE, and role UE.

[0783] In some embodiments, the SL positioning service UE is one of the following UEs:

[0784] Target UE;

[0785] Anchor UE;

[0786] Other UEs except the target UE and anchor UE.

[0787] In some embodiments, step 710 is performed after step 2. UE1 discovers UE2 / ... / UEn.

[0788] In some embodiments, step 710 is performed after step 4. UE1 and UE2 / ... / UEn perform capability exchange.

[0789] In this embodiment, step 710 is optional. In different embodiments, one or more of these steps may be omitted or replaced. Step 710 may be implemented as an independent embodiment, such as, but not limited to, an information notification method, a notification message sending method, or a method for notifying a SL location service UE.

[0790] Using the method of this embodiment, the anchor UE receives the notification message sent by the SL positioning service UE, or the anchor UE receives the notification message sent by the target UE, so that the anchor UE can know the SL positioning service UE, and then continue to transmit SL positioning auxiliary information and measure SL-PRS and other processes.

[0791] FIG15 shows a structural block diagram of a communication device for a SL positioning service scenario provided by an exemplary embodiment of the present application. The device can be implemented as all or part of a target UE in the SL positioning service scenario. The device includes:

[0792] Receiving module 12, used to receive ranging / SL positioning service request;

[0793] Determination module 13, used to determine the SL positioning service UE;

[0794] Among them, the SL positioning service UE is a UE used to undertake the SL positioning service function.

[0795] In some embodiments, the target UE receives a ranging / SL positioning service request sent by the SL positioning client UE.

[0796] In some embodiments, during the process of exposing ranging / SL positioning services via PC5, the SL positioning client UE is positioned via PC5, that is, the SL positioning client sends a ranging / SL positioning service request to the target UE via the PC5 interface.

[0797] In some embodiments, for absolute positioning, the ranging / SL positioning service request includes the user information of the SL positioning client UE and the user information of the target UE, as well as the required positioning QoS.

[0798] In some embodiments, for relative position or ranging information, the ranging / SL positioning service request includes user information of the SL positioning client UE, user information of the target UE, user information of the anchor UE and ranging / SL positioning QoS information.

[0799] In some embodiments, the target UE receives a ranging / SL positioning service request from the application layer.

[0800] In some embodiments, the ranging / SL positioning service request includes a result type and a required QoS, wherein the result type includes absolute position, relative position, or ranging information.

[0801] In some embodiments, the target UE determines the SL positioning service UE based on at least one of the following information:

[0802] RSRP reference signal received power information between the first UE and at least one anchor UE;

[0803] Indication information indicating whether SL unicast communication can be established between the first UE and the at least one anchor UE;

[0804] The number of SL unicast communications that can be established between the first UE and the at least one anchor UE;

[0805] The first UE is one of multiple UEs, and the multiple UEs are UEs that exchange capabilities with the target UE.

[0806] In some embodiments, the target UE determines the SL positioning service UE based on at least one of the following information:

[0807] RSRP information between the first UE and each anchor UE in the UE list;

[0808] Indication information of whether SL unicast communication can be established between the first UE and each anchor UE in the UE list;

[0809] The number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list;

[0810] The first UE is one of a plurality of UEs, the plurality of UEs are UEs that perform capability exchange with the target UE, and the UE list is a subset of a set consisting of at least one anchor UE.

[0811] In some embodiments, the target UE determines the SL positioning service UE based on at least one of the following information:

[0812] RSRP information between the second UE and at least one anchor UE;

[0813] Indication information indicating whether SL unicast communication can be established between the second UE and the at least one anchor UE;

[0814] The number of SL unicast communications that can be established between the second UE and the at least one anchor UE;

[0815] The second UE is one of the candidate UEs, and the candidate UE is a UE that is a candidate to become the SL positioning service UE.

[0816] In some embodiments, the target UE determines the SL positioning service UE based on at least one of the following information:

[0817] RSRP information between the second UE and each anchor UE in the UE list;

[0818] Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[0819] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[0820] The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the UE list is a subset of a set consisting of at least one anchor UE.

[0821] In some embodiments, the apparatus further comprises a sending module 14;

[0822] The sending module 14 is used to send a request message to the SL positioning service UE;

[0823] The receiving module 12 is configured to receive a response message returned by the SL positioning service UE;

[0824] The request message is used to request the receiving UE to serve as the SL positioning service UE, and the response message is used to indicate whether the receiving UE agrees to serve as the SL positioning service UE.

[0825] In some embodiments, when the response message indicates that the receiving UE does not agree to serve as the SL positioning service UE, the determination module 13 is used to re-determine the SL positioning service UE.

[0826] In some embodiments, when the response message is not received, the determination module 13 is used to re-determine the SL positioning service UE.

[0827] In some embodiments, the sending module 14 is configured to send a capability request message to the multiple UEs;

[0828] The receiving module 12 is configured for the target UE to receive capability response messages returned by the multiple UEs;

[0829] The determination module 13 is configured to determine the SL positioning service UE according to the capability response message.

[0830] In some embodiments, during the capability exchange process, the target UE sends a capability request message to multiple UEs.

[0831] In some embodiments, the capability exchange process is also referred to as at least one of an exchange process, a capability interaction process, a SL positioning capability exchange process, and a SL positioning capability interaction process.

[0832] In some embodiments, the capability request message is also called at least one of a request message, an exchange request message, an interaction request message, a capability exchange request message, a capability interaction request message, a SL positioning capability request message, a SL positioning capability exchange request message, and a SL positioning capability interaction request message.

[0833] In some embodiments, the plurality of UEs include an anchor UE and / or other UEs other than the anchor UE and the target UE.

[0834] In some embodiments, the first UE is one of a plurality of UEs, and the plurality of UEs are UEs that perform capability exchange with the target UE.

[0835] In some embodiments, the capability request message is further used to instruct the first UE among the multiple UEs to return at least one of the following information to the target UE:

[0836] RSRP information between the first UE and at least one anchor UE;

[0837] Indication information indicating whether SL unicast communication can be established between the first UE and the at least one anchor UE;

[0838] The number of SL unicast communications that can be established between the first UE and the at least one anchor UE.

[0839] In some embodiments, each RSRP between the first UE and the anchor UE may be represented by n bits.

[0840] In some embodiments, the n bits corresponding to RSRP are used to represent the absolute value of RSRP. The absolute value of RSRP corresponds to the number of bits in a one-to-one correspondence.

[0841] In some embodiments, the indication information of whether SL unicast communication can be established between the first UE and the anchor UE can be represented by a bit sequence (bitmap). Each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the first UE and each anchor UE.

[0842] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the first UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0843] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the first UE and the anchor UE is 0, indicating that SL unicast communication cannot be established between the first UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the first UE and the anchor UE is 1, indicating that SL unicast communication can be established between the first UE and the anchor UE.

[0844] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the first UE and the anchor UE is 0, indicating that SL unicast communication can be established between the first UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the first UE and the anchor UE is 1, indicating that SL unicast communication cannot be established between the first UE and the anchor UE.

[0845] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0846] In some embodiments, the capability request message also carries RSRP threshold information.

[0847] In some embodiments, when the RSRP between the first UE and the anchor UE is greater than the RSRP threshold, the requirements for establishing SL unicast communication are met, and SL unicast communication can be established between the first UE and the anchor UE. The indication information is used to indicate that SL unicast communication can be established between the first UE and the anchor UE.

[0848] In some embodiments, when the RSRP between the first UE and the anchor UE is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the first UE and the anchor UE. The indication information is used to indicate that SL unicast communication cannot be established between the first UE and the anchor UE.

[0849] In some embodiments, when the RSRP between the first UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is 1. When the RSRP between the first UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is 0.

[0850] In some embodiments, when the RSRP between the first UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is 0. When the RSRP between the first UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is 1.

[0851] In some embodiments, the number of SL unicast communications that can be established between the first UE and the anchor UEs can be represented by a bit sequence, where each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the first UE and each anchor UE.

[0852] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the first UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0853] In some embodiments, the number of SL unicast communications that can be established between the first UE and the anchor UE can be represented by a code point. The number of SL unicast communications that can be established between the first UE and the anchor UE has a one-to-one correspondence with the value of the code point.

[0854] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the first UE and the anchor UE. For example, 001 represents that the number of SL unicast communications that can be established between the first UE and the anchor UE is 1, and 010 represents that the number of SL unicast communications that can be established between the first UE and the anchor UE is 2.

[0855] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the first UE and the anchor UE, which can be determined through negotiation, or agreed upon by protocol, or indicated by the target UE in a capability request message.

[0856] In some embodiments, the capability request message is further used to instruct the first UE among the multiple UEs to return at least one of the following information to the target UE:

[0857] RSRP information between the first UE and each anchor UE in the UE list;

[0858] Indication information of whether SL unicast communication can be established between the first UE and each anchor UE in the UE list;

[0859] The number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list;

[0860] The anchor UEs in the UE list are a subset of the anchor UEs.

[0861] In some embodiments, the UE list is a subset of a set of at least one anchor UE.

[0862] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0863] In some embodiments, the capability request message also carries RSRP threshold information.

[0864] In some embodiments, when the RSRP between the first UE and an anchor UE in the UE list is greater than an RSRP threshold, the requirement for establishing SL unicast communication is met, and SL unicast communication can be established between the first UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication can be established between the first UE and the anchor UE in the UE list.

[0865] In some embodiments, when the RSRP between the first UE and an anchor UE in the UE list is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the first UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication cannot be established between the first UE and the anchor UE in the UE list.

[0866] In some embodiments, when the RSRP between the first UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 1. When the RSRP between the first UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 0.

[0867] In some embodiments, when the RSRP between the first UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the first UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[0868] In some embodiments, the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the first UE and each anchor UE.

[0869] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the first UE and the i-th anchor UE in the UE list, wherein the i-th anchor UE is an anchor UE in the UE list.

[0870] In some embodiments, the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list can be represented by a code point. The number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list corresponds to the value of the code point.

[0871] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list. For example, 001 represents that the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list is 1, and 010 represents that the number of SL unicast communications that can be established between the first UE and the anchor UEs in the UE list is 2.

[0872] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the first UE and the anchor UE in the UE list, which can be determined through negotiation, or through protocol agreement, or indicated by the target UE in the capability request message.

[0873] In some embodiments, the first UE among the plurality of UEs includes a UE among the anchor UEs and / or a UE among other UEs except the anchor UE and the target UE.

[0874] In some embodiments, RSRP information is obtained based on measurements of announcement messages in the SL discovery process.

[0875] In some embodiments, the RSRP information is obtained based on measurements of request messages in the SL discovery process.

[0876] In some embodiments, the indication information is indicated by at least one of numbers, letters, symbols, and bits.

[0877] In some embodiments, during the capability exchange process, the target UE receives capability response messages returned by multiple UEs.

[0878] In some embodiments, the capability exchange process is also referred to as at least one of an exchange process, a capability interaction process, a SL positioning capability exchange process, and a SL positioning capability interaction process.

[0879] In some embodiments, the capability response message is also referred to as at least one of a response message, an exchange response message, an interaction response message, a capability exchange response message, and a capability interaction response message.

[0880] In some embodiments, the plurality of UEs include an anchor UE, and / or other UEs other than the anchor UE and the target UE.

[0881] In some embodiments, the capability response message is further used to carry at least one of the following information of the first UE among the multiple UEs:

[0882] RSRP information between the first UE and the at least one anchor UE;

[0883] Indication information indicating whether SL unicast communication can be established between the first UE and the at least one anchor UE;

[0884] The number of SL unicast communications that can be established between the first UE and the at least one anchor UE.

[0885] In some embodiments, the capability response message is further used to carry at least one of the following information of the first UE among the multiple UEs:

[0886] RSRP information between the first UE and each anchor UE in the UE list;

[0887] Indication information of whether SL unicast communication can be established between the first UE and each anchor UE in the UE list;

[0888] The number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list;

[0889] The anchor UEs in the UE list are a subset of the anchor UEs.

[0890] In some embodiments, the UE list is a subset of a set of at least one anchor UE.

[0891] In some embodiments, the SL positioning service UE is a UE that undertakes the SL positioning service UE function.

[0892] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning UE, SL service UE, positioning UE, and positioning service UE.

[0893] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning service role UE, SL positioning role UE, SL service role UE, positioning role UE, positioning service role UE, and role UE.

[0894] In some embodiments, the target UE calculates the RSRP average of the first UE based on the RSRP information between the first UE and the anchor UE in the capability response information, and determines the first UE with the largest RSRP average as the SL positioning service UE.

[0895] In some embodiments, the target UE determines the number of RSRPs of the first UEs that are greater than the RSRP threshold based on the RSRP information between the first UE and the anchor UE in the capability response information, and determines the first UE with the largest number of RSRPs greater than the RSRP threshold as the SL positioning service UE.

[0896] In some embodiments, the target UE determines the number of anchor UEs with which SL unicast communication can be established based on the indication information in the capability response information indicating whether SL unicast communication can be established between the first UE and the anchor UE. The first UE that can establish SL unicast communication with the largest number of anchor UEs is determined as the SL positioning service UE.

[0897] In some embodiments, the target UE determines the first UE that can establish SL unicast communication with the largest number of anchor UEs as the SL positioning service UE based on the number of SL unicast communications that can be established between the first UE and the anchor UEs in the response capability information.

[0898] In some embodiments, the SL positioning service UE is one of the following UEs:

[0899] Target UE;

[0900] Anchor UE;

[0901] Other UEs except the target UE and anchor UE.

[0902] In some embodiments, the sending module 14 is configured to send a request message to multiple second UEs;

[0903] The receiving module 12 is configured to receive response messages returned by the multiple second UEs;

[0904] The request message is used to request the second UE to serve as the SL positioning service UE, and the response message is used to indicate whether the second UE agrees to serve as the SL positioning service UE.

[0905] In some embodiments, the second UE is one of the candidate UEs.

[0906] In some embodiments, the candidate UE is a UE that is a candidate to become a SL positioning service UE.

[0907] In some embodiments, the second UE may be at least one of an anchor UE, a UE other than the anchor UE, and a target UE.

[0908] In some embodiments, the second UE is a UE that supports SL positioning service UE function.

[0909] In some embodiments, the second UE may also be referred to as at least one of SL positioning service second UE, SL positioning second UE, SL service second UE, positioning second UE, and positioning service second UE.

[0910] In some embodiments, the request message is used to request the second UE to serve as a SL positioning service UE.

[0911] In some embodiments, the request message is also called at least one of SL positioning service UE request message, SL positioning service request message, SL positioning UE request message, SL positioning request message, positioning service UE request message, positioning service request message, and positioning request message.

[0912] In some embodiments, the request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[0913] RSRP information between the second UE and the at least one anchor UE;

[0914] Indication information indicating whether SL unicast communication can be established between the second UE and the at least one anchor UE;

[0915] The number of SL unicast communications that can be established between the second UE and the at least one anchor UE.

[0916] In some embodiments, each RSRP between the second UE and the anchor UE may be represented by n bits.

[0917] In some embodiments, the n bits corresponding to RSRP are used to represent the absolute value of RSRP. The absolute value of RSRP corresponds to the number of bits in a one-to-one correspondence.

[0918] In some embodiments, the indication information of whether SL unicast communication can be established between the second UE and the anchor UE can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0919] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0920] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 0, indicating that SL unicast communication cannot be established between the second UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 1, indicating that SL unicast communication can be established between the second UE and the anchor UE.

[0921] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 0, indicating that SL unicast communication can be established between the second UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 1, indicating that SL unicast communication cannot be established between the second UE and the anchor UE.

[0922] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0923] In some embodiments, the request message also carries RSRP threshold information.

[0924] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the requirements for establishing SL unicast communication are met, and SL unicast communication can be established between the second UE and the anchor UE. The indication information is used to indicate that SL unicast communication can be established between the second UE and the anchor UE.

[0925] In some embodiments, when the RSRP between the second UE and the anchor UE is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the second UE and the anchor UE. The indication information is used to indicate that SL unicast communication cannot be established between the second UE and the anchor UE.

[0926] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is 1. When the RSRP between the second UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is 0.

[0927] In some embodiments, when the RSRP between the second UE and the anchor UE is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the second UE and the anchor UE is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[0928] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs can be represented by a bit sequence, where each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0929] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[0930] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UE can be represented by a code point. The number of SL unicast communications that can be established between the second UE and the anchor UE has a one-to-one correspondence with the value of the code point.

[0931] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the second UE and the anchor UE. For example, 001 represents that the number of SL unicast communications that can be established between the second UE and the anchor UE is 1, and 010 represents that the number of SL unicast communications that can be established between the second UE and the anchor UE is 2.

[0932] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the second UE and the anchor UE, which can be determined through negotiation, or agreed upon by protocol, or indicated by the target UE in the request message.

[0933] In some embodiments, the request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[0934] RSRP information between the second UE and each anchor UE in the UE list;

[0935] Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[0936] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[0937] The anchor UEs in the UE list are a subset of the anchor UEs.

[0938] In some embodiments, the UE list is a subset of a set of at least one anchor UE.

[0939] In some embodiments, RSRP information is obtained based on measurements of announcement messages in the SL discovery process.

[0940] In some embodiments, the RSRP information is obtained based on measurements of request messages in the SL discovery process.

[0941] In some embodiments, the indication information is determined based on a magnitude relationship between RSRP information and RSRP threshold information.

[0942] In some embodiments, the request message also carries RSRP threshold information.

[0943] In some embodiments, when the RSRP between the second UE and an anchor UE in the UE list is greater than an RSRP threshold, the requirement for establishing SL unicast communication is met, and SL unicast communication can be established between the second UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication can be established between the second UE and the anchor UE in the UE list.

[0944] In some embodiments, when the RSRP between the second UE and an anchor UE in the UE list is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the second UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication cannot be established between the second UE and the anchor UE in the UE list.

[0945] In some embodiments, when the RSRP between the second UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 1. When the RSRP between the second UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 0.

[0946] In some embodiments, when the RSRP between the second UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the second UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[0947] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[0948] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE in the UE list, wherein the i-th anchor UE is an anchor UE in the UE list.

[0949] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list can be represented by a code point. The number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list corresponds to the value of the code point.

[0950] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list. For example, 001 represents that the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list is 1, and 010 represents that the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list is 2.

[0951] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the second UE and the anchor UE in the UE list, which can be determined through negotiation, or through protocol agreement, or indicated by the target UE in the request message.

[0952] In some embodiments, the indication information is indicated by at least one of numbers, letters, symbols, and bits.

[0953] In some embodiments, the response message is further used to carry at least one of the following information of the second UE:

[0954] RSRP information between the second UE and the at least one anchor UE;

[0955] Indication information indicating whether SL unicast communication can be established between the second UE and the at least one anchor UE;

[0956] The number of SL unicast communications that can be established between the second UE and the at least one anchor UE.

[0957] In some embodiments, the response message is further used to carry at least one of the following information of the second UE:

[0958] RSRP information between the second UE and each anchor UE in the UE list;

[0959] Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[0960] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[0961] The anchor UEs in the UE list are a subset of the anchor UEs.

[0962] In some embodiments, the response message is used to indicate whether the receiving UE agrees to serve as a SL positioning service UE.

[0963] In some embodiments, the response message is also called at least one of SL positioning service UE response message, SL positioning service response message, SL positioning UE response message, SL positioning response message, positioning service UE response message, positioning service response message, and positioning response message.

[0964] In some embodiments, the determination module 13 is used to determine the SL positioning service UE according to the response message.

[0965] In some embodiments, the SL positioning service UE is a UE that undertakes the SL positioning service UE function.

[0966] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning UE, SL service UE, positioning UE, and positioning service UE.

[0967] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning service role UE, SL positioning role UE, SL service role UE, positioning role UE, positioning service role UE, and role UE.

[0968] In some embodiments, the target UE calculates the RSRP average of the second UEs based on the RSRP information between the second UE and the anchor UE in the response information, and determines the second UE with the largest RSRP average as the SL positioning service UE.

[0969] In some embodiments, the target UE determines the number of RSRPs of the second UEs that are greater than the RSRP threshold based on the RSRP information between the second UE and the anchor UE in the response information, and determines the second UE with the largest number of RSRPs greater than the RSRP threshold as the SL positioning service UE.

[0970] In some embodiments, the target UE determines the number of anchor UEs with which SL unicast communication can be established with the second UE based on the indication information in the response information as to whether SL unicast communication can be established between the second UE and the anchor UE. The second UE with which SL unicast communication can be established with the largest number of anchor UEs is determined as the SL positioning service UE.

[0971] In some embodiments, the target UE determines the second UE that can establish SL unicast communication with the largest number of anchor UEs as the SL positioning service UE based on the number of second UEs and anchor UEs that can establish SL unicast communication in the response information.

[0972] In some embodiments, the sending module 14 is configured to send a confirmation message to the SL positioning service UE;

[0973] The confirmation message is used to confirm that the receiving UE serves as the SL positioning service UE.

[0974] In some embodiments, the confirmation message is used to confirm that the recipient UE is a SL positioning service UE.

[0975] In some embodiments, the confirmation message is also called at least one of SL positioning service UE confirmation message, SL positioning service confirmation message, SL positioning UE confirmation message, SL positioning confirmation message, positioning service UE confirmation message, positioning service confirmation message, and positioning confirmation message.

[0976] In some embodiments, the confirmation message is also called at least one of SL positioning service UE role confirmation message, SL positioning service role confirmation message, SL positioning UE role confirmation message, SL positioning role confirmation message, positioning service UE role confirmation message, positioning service role confirmation message, and positioning role confirmation message.

[0977] In some embodiments, the sending module 14 is configured to send a notification message to at least one anchor UE;

[0978] Among them, the notification message is used to indicate the SL positioning service UE.

[0979] In some embodiments, the notification message is used to indicate the SL positioning service UE that assumes the SL positioning service UE function.

[0980] In some embodiments, the notification message is also called at least one of SL positioning service UE notification message, SL positioning service notification message, SL positioning UE notification message, SL positioning notification message, positioning service UE notification message, positioning service notification message, and positioning notification message.

[0981] In some embodiments, the notification message is also called at least one of SL positioning service UE role notification message, SL positioning service role notification message, SL positioning UE role notification message, SL positioning role notification message, positioning service UE role notification message, positioning service role notification message, and positioning role notification message.

[0982] In some embodiments, the notification message carries identification information of the SL positioning service UE.

[0983] In some embodiments, the notification message also carries identification information of the target UE.

[0984] In some embodiments, the notification message also carries a positioning session identifier (SLPP Session ID) information, which is used to indicate that for a specific positioning session and / or a specific ranging / SL positioning service request, the SL positioning service UE assumes the SL positioning service UE function. The positioning session identifier information is used to distinguish different positioning sessions or ranging / SL positioning service requests.

[0985] In some embodiments, the identification information includes user information.

[0986] In some embodiments, the user information may be a user ID.

[0987] In some embodiments, the user information may be a layer-2 ID.

[0988] In some embodiments, the user information may be an application layer ID.

[0989] In some embodiments, the notification message may be sent via at least one of broadcast, unicast, and multicast.

[0990] In some embodiments, the notification message carries at least one of the following information:

[0991] SLPP Positioning Assistant Data;

[0992] ·Announcement message of SL discovery process;

[0993] Request message of the SL discovery process;

[0994] NAS (None Access Stratum) signaling

[0995] In some embodiments, the notification message is carried in metadata of the announcement message and / or the request message to save signaling interaction.

[0996] In some embodiments, the notification message is carried in metadata of the announcement message. For example, the role of the announced UE is indicated as the target UE, not the serving UE role, and the metadata carries identification information of the serving UE to save signaling interaction.

[0997] In some embodiments, the target UE may have different positioning service requests. In order to further distinguish the positioning session or ranging / SL positioning service request to which the SL positioning service UE belongs, the notification message may also carry positioning session identification information.

[0998] In some embodiments, the notification message is carried in the SL positioning assistance information. The SL positioning assistance information is sent in a broadcast or multicast manner. By carrying the notification message in the SL positioning assistance information, even if the target UE may have different positioning service requests, the SL positioning assistance information itself is within a certain positioning session, so there is no need to additionally indicate the positioning session identification information, and no new signaling can be introduced, which is used to save signaling interaction.

[0999] In some embodiments, the sending modules 14 for implementing different functions can be implemented as the same sending module or as different sending modules. The receiving modules 12 for implementing different functions can be implemented as the same receiving module or as different receiving modules. The determining modules 13 for implementing different functions can be implemented as the same determining module or as different determining modules. This embodiment does not impose any restrictions on this.

[1000] FIG16 shows a block diagram of a communication device for a SL positioning service scenario provided by an exemplary embodiment of the present application. The device may be implemented as all or part of an anchor UE in the SL positioning service scenario. The device includes:

[1001] Receiving module 22, used to receive notification messages;

[1002] The notification message is used to indicate the SL positioning service UE.

[1003] In some embodiments, the anchor UE receives the notification message sent by the target UE.

[1004] In some embodiments, the anchor UE receives a notification message sent by the SL positioning service UE.

[1005] In some embodiments, the notification message is used to indicate the SL positioning service UE that assumes the SL positioning service UE function.

[1006] In some embodiments, the notification message is also called at least one of SL positioning service UE notification message, SL positioning service notification message, SL positioning UE notification message, SL positioning notification message, positioning service UE notification message, positioning service notification message, and positioning notification message.

[1007] In some embodiments, the notification message is also called at least one of SL positioning service UE role notification message, SL positioning service role notification message, SL positioning UE role notification message, SL positioning role notification message, positioning service UE role notification message, positioning service role notification message, and positioning role notification message.

[1008] In some embodiments, the notification message carries identification information of the SL positioning service UE.

[1009] In some embodiments, the notification message also carries identification information of the target UE.

[1010] In some embodiments, the notification message also carries a positioning session identifier (SLPP Session ID) information, which is used to indicate that for a specific positioning session and / or a specific ranging / SL positioning service request, the SL positioning service UE assumes the SL positioning service UE function. The positioning session identifier information is used to distinguish different positioning sessions or ranging / SL positioning service requests.

[1011] In some embodiments, the identification information includes user information.

[1012] In some embodiments, the user information may be a user ID.

[1013] In some embodiments, the user information may be a layer-2 ID.

[1014] In some embodiments, the user information may be an application layer ID.

[1015] In some embodiments, the notification message may be sent via at least one of broadcast, unicast, and multicast.

[1016] In some embodiments, the notification message does not carry identification information of the SL positioning service UE.

[1017] In some embodiments, the notification message is also used to indicate that the SL positioning service UE is this UE.

[1018] In some embodiments, when the identification information of the SL positioning service UE in the notification message does not exist, it is understood that the SL positioning service UE indicated is the current UE.

[1019] In some embodiments, when the identification information of the SL positioning service UE in the notification message is a special ID, it is understood that the SL positioning service UE indicates this UE.

[1020] In some embodiments, the notification message carries bit indication information. When the bit value of the bit indication information is 1 or true, it indicates that the SL positioning service UE indication is the current UE.

[1021] In the above case, the notification message may not carry the identification information of the SL positioning service UE, saving signaling overhead.

[1022] In some embodiments, the notification message carries bit indication information. When the bit value of the bit indication information is 0 or false, or the notification message does not carry the bit indication information, the notification message needs to carry complete identification information of the SL positioning service UE.

[1023] In some embodiments, the notification message carries at least one of the following information:

[1024] SLPP Positioning Assistant Data;

[1025] ·Announcement message of SL discovery process;

[1026] Request message of the SL discovery process;

[1027] NAS (None Access Stratum) signaling

[1028] In some embodiments, the notification message is carried in metadata of the announcement message. For example, the role of the announced UE is indicated as the target UE, not the serving UE role, and the metadata carries identification information of the serving UE to save signaling interaction.

[1029] In some embodiments, the target UE may have different positioning service requests. In order to further distinguish the positioning session or ranging / SL positioning service request to which the SL positioning service UE belongs, the notification message may also carry positioning session identification information.

[1030] In some embodiments, the roles of the declared UE include target UE, SL positioning service UE, anchor UE, and anchor UE that can obtain its own position. Declaring the UE's role as a SL positioning service UE means that the declared UE can assume the functions of a SL positioning service UE. However, it does not determine who the SL positioning service UE is for a particular SL positioning service request.

[1031] In some embodiments, the notification message is carried in the SL positioning assistance information. The SL positioning assistance information is sent in a broadcast or multicast manner. By carrying the notification message in the SL positioning assistance information, even if the target UE may have different positioning service requests, the SL positioning assistance information itself is within a certain positioning session, so there is no need to additionally indicate the positioning session identification information, and no new signaling can be introduced, which is used to save signaling interaction.

[1032] In some embodiments, the notification message is carried in the metadata of the declaration message, and by introducing a new UE role, such as "authorized service UE" or "confirmed service UE", it implicitly indicates that it is a SL positioning service UE, which is used to save signaling interaction.

[1033] In some embodiments, the SL positioning service UE is a UE that undertakes the SL positioning service UE function.

[1034] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning UE, SL service UE, positioning UE, and positioning service UE.

[1035] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning service role UE, SL positioning role UE, SL service role UE, positioning role UE, positioning service role UE, and role UE.

[1036] In some embodiments, the SL positioning service UE is one of the following UEs:

[1037] Target UE;

[1038] Anchor UE;

[1039] Other UEs except the target UE and anchor UE.

[1040] In some embodiments, the receiving modules 22 for implementing different functions may be implemented as the same receiving module or as different receiving modules, which is not limited in this embodiment.

[1041] FIG17 shows a structural block diagram of a communication device applied to a SL positioning service scenario provided by an exemplary embodiment of the present application. The device is used to implement a second UE in the SL positioning service scenario. The device includes:

[1042] A receiving module 32 is configured to receive a request message sent by a target UE;

[1043] The sending module 34 is configured to send a response message to the target UE; the response message carries information used by the target UE to determine the SL positioning service UE;

[1044] The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the request message is used to request the second UE to serve as the SL positioning service UE.

[1045] In some embodiments, the response message carries at least one of the following information:

[1046] RSRP information between the second UE and at least one anchor UE;

[1047] Indication information indicating whether SL unicast communication can be established between the second UE and the at least one anchor UE;

[1048] The number of UEs that can establish SL unicast communication between the second UE and the at least one anchor UE.

[1049] In some embodiments, the response message carries at least one of the following information:

[1050] RSRP information between the second UE and each anchor UE in the UE list;

[1051] Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[1052] The number of UEs that can establish SL unicast communication between the second UE and all anchor UEs in the UE list;

[1053] The anchor UEs in the UE list are a subset of the anchor UEs.

[1054] In some embodiments, the UE list is a subset of a set of at least one anchor UE.

[1055] In some embodiments, the second UE is a UE that is a candidate to become a SL positioning service UE.

[1056] In some embodiments, the second UE may be at least one of an anchor UE, a UE other than the anchor UE, and a target UE.

[1057] In some embodiments, the second UE is a UE that supports SL positioning service UE function.

[1058] In some embodiments, the second UE may also be referred to as at least one of SL positioning service second UE, SL positioning second UE, SL service second UE, positioning second UE, and positioning service second UE.

[1059] In some embodiments, the request message is used to request the second UE to serve as a SL positioning service UE.

[1060] In some embodiments, the request message is also called at least one of SL positioning service UE request message, SL positioning service request message, SL positioning UE request message, SL positioning request message, positioning service UE request message, positioning service request message, and positioning request message.

[1061] In some embodiments, the request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[1062] RSRP information between the second UE and the at least one anchor UE;

[1063] Indication information indicating whether SL unicast communication can be established between the second UE and the at least one anchor UE;

[1064] The number of UEs that can establish SL unicast communication between the second UE and the at least one anchor UE.

[1065] In some embodiments, the request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[1066] RSRP information between the second UE and each anchor UE in the UE list;

[1067] Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[1068] The number of UEs that can establish SL unicast communication between the second UE and all anchor UEs in the UE list;

[1069] The anchor UEs in the UE list are a subset of the anchor UEs.

[1070] In some embodiments, the UE list is a subset of a set of at least one anchor UE.

[1071] In some embodiments, the response message further includes a capability response message.

[1072] In some embodiments, the request message further comprises a capability request message.

[1073] In some embodiments, the request message further comprises a capability request message.

[1074] In some embodiments, during the capability exchange process, the second UE receives a capability request message sent by the target UE.

[1075] In some embodiments, the capability exchange process is also referred to as at least one of an exchange process, a capability interaction process, a SL positioning capability exchange process, and a SL positioning capability interaction process.

[1076] In some embodiments, the capability request message is also called at least one of a request message, an exchange request message, an interaction request message, a capability exchange request message, a capability interaction request message, a SL positioning capability request message, a SL positioning capability exchange request message, and a SL positioning capability interaction request message.

[1077] In some embodiments, the capability request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[1078] RSRP information between the second UE and at least one anchor UE;

[1079] Indication information indicating whether SL unicast communication can be established between the second UE and at least one anchor UE;

[1080] The number of SL unicast communications that can be established between the second UE and at least one anchor UE.

[1081] In some embodiments, the capability request message is further used to instruct the second UE to return at least one of the following information to the target UE:

[1082] RSRP information between the second UE and each anchor UE in the UE list;

[1083] Indication information indicating whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[1084] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[1085] The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the UE list is a subset of a set consisting of at least one anchor UE.

[1086] In some embodiments, each RSRP between the second UE and the anchor UE may be represented by n bits.

[1087] In some embodiments, the n bits corresponding to RSRP are used to represent the absolute value of RSRP. The absolute value of RSRP corresponds to the number of bits in a one-to-one correspondence.

[1088] In some embodiments, the indication information of whether SL unicast communication can be established between the second UE and the anchor UE can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[1089] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE, where the i-th anchor UE is one of the anchor UEs.

[1090] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 0, indicating that SL unicast communication cannot be established between the second UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 1, indicating that SL unicast communication can be established between the second UE and the anchor UE.

[1091] In some embodiments, the bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 0, indicating that SL unicast communication can be established between the second UE and the anchor UE. The bit value corresponding to the indication information of whether SL unicast communication can be established between the second UE and the anchor UE is 1, indicating that SL unicast communication cannot be established between the second UE and the anchor UE.

[1092] In some embodiments, the RSRP information is obtained based on measurements of announcement messages in the SL discovery process.

[1093] In some embodiments, the RSRP information is obtained based on measurements of request messages in the SL discovery process.

[1094] In some embodiments, the indication information is determined based on a size relationship between the RSRP information and RSRP threshold information.

[1095] In some embodiments, the request message also carries the RSRP threshold information.

[1096] In some embodiments, the capability request message also carries RSRP threshold information.

[1097] In some embodiments, when the RSRP between the second UE and an anchor UE in the UE list is greater than an RSRP threshold, the requirement for establishing SL unicast communication is met, and SL unicast communication can be established between the second UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication can be established between the second UE and the anchor UE in the UE list.

[1098] In some embodiments, when the RSRP between the second UE and an anchor UE in the UE list is less than an RSRP threshold, the requirement for establishing SL unicast communication is not met, and SL unicast communication cannot be established between the second UE and the anchor UE in the UE list. The indication information is used to indicate that SL unicast communication cannot be established between the second UE and the anchor UE in the UE list.

[1099] In some embodiments, when the RSRP between the second UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 1. When the RSRP between the second UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 0.

[1100] In some embodiments, when the RSRP between the second UE and the anchor UE in the UE list is greater than the RSRP threshold, the bit value corresponding to the indication information is represented as 0. When the RSRP between the second UE and the anchor UE in the UE list is less than the RSRP threshold, the bit value corresponding to the indication information is represented as 1.

[1101] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list can be represented by a bit sequence, wherein each bit in the bit sequence is used to indicate whether SL unicast communication can be established between the second UE and each anchor UE.

[1102] In some embodiments, the i-th bit in the bit sequence indicates that SL unicast communication can be established between the second UE and the i-th anchor UE in the UE list, wherein the i-th anchor UE is an anchor UE in the UE list.

[1103] In some embodiments, the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list can be represented by a code point. The number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list corresponds to the value of the code point.

[1104] In some embodiments, the binary values ​​corresponding to the three bits form a code point, and each code point represents the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list. For example, 001 represents that the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list is 1, and 010 represents that the number of SL unicast communications that can be established between the second UE and the anchor UEs in the UE list is 2.

[1105] In some embodiments, a correspondence between the number of SL unicast communications and bit sequences and / or code points can be established between the second UE and the anchor UE in the UE list, which can be determined through negotiation, or through protocol agreement, or indicated by the target UE in the request message.

[1106] In some embodiments, the indication information is indicated by at least one of numbers, letters, symbols, and bits.

[1107] In some embodiments, the response message carries information used by the target UE to determine the SL positioning service UE.

[1108] In some embodiments, the response message is also called at least one of SL positioning service UE response message, SL positioning service response message, SL positioning UE response message, SL positioning response message, positioning service UE response message, positioning service response message, and positioning response message.

[1109] In some embodiments, the response message also includes a capability response message.

[1110] In some embodiments, during the capability exchange process, the second UE returns a capability response message to the target UE.

[1111] In some embodiments, the capability exchange process is also referred to as at least one of an exchange process, a capability interaction process, a SL positioning capability exchange process, and a SL positioning capability interaction process.

[1112] In some embodiments, the capability response message is also referred to as at least one of a response message, an exchange response message, an interaction response message, a capability exchange response message, and a capability interaction response message.

[1113] In some embodiments, the capability response message is further used to carry at least one of the following information of the second UE:

[1114] RSRP information between the second UE and at least one anchor UE;

[1115] Indication information indicating whether SL unicast communication can be established between the second UE and at least one anchor UE;

[1116] The number of SL unicast communications that can be established between the second UE and at least one anchor UE.

[1117] In some embodiments, the capability response message is further used to carry at least one of the following information of the second UE:

[1118] RSRP information between the second UE and each anchor UE in the UE list;

[1119] Indication information indicating whether SL unicast communication can be established between the second UE and each anchor UE in the UE list;

[1120] The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list;

[1121] The anchor UEs in the UE list are a subset of the anchor UEs.

[1122] In some embodiments, the UE list is a subset of a set of at least one anchor UE.

[1123] In some embodiments, the sending modules 34 for implementing different functions can be implemented as the same sending module or as different sending modules. The receiving modules 32 for implementing different functions can be implemented as the same receiving module or as different receiving modules. This embodiment does not impose any restrictions on this.

[1124] FIG18 shows a structural block diagram of a communication device applied to a SL positioning service scenario provided by an exemplary embodiment of the present application. The device can implement all or part of a SL positioning service UE in the SL positioning service scenario. The device includes:

[1125] A receiving module 42 is configured to receive a request message sent by a target UE;

[1126] A sending module 44 is configured to send a response message to the target UE;

[1127] The request message is used to request the receiving UE to serve as the SL positioning service UE, and the response message is used to indicate whether the receiving UE agrees to serve as the SL positioning service UE.

[1128] In some embodiments, the request message is used to request the recipient UE to serve as the SL positioning service UE.

[1129] In some embodiments, the receiving UE is also referred to as at least one of SL positioning service receiving UE, SL positioning receiving UE, SL service receiving UE, positioning receiving UE, and positioning service receiving UE.

[1130] In some embodiments, the request message is also called at least one of SL positioning service UE request message, SL positioning service request message, SL positioning UE request message, SL positioning request message, positioning service UE request message, positioning service request message, and positioning request message.

[1131] In some embodiments, the response message is used to indicate whether the receiving UE agrees to serve as a SL positioning service UE.

[1132] In some embodiments, the response message is also called at least one of SL positioning service UE response message, SL positioning service response message, SL positioning UE response message, SL positioning response message, positioning service UE response message, positioning service response message, and positioning response message.

[1133] In some embodiments, the response message includes a first bit, the bit value of which is used to indicate whether the receiving UE agrees to serve as a SL positioning service UE. The first bit is one of the bits corresponding to the response message.

[1134] In some embodiments, the bit value corresponding to the first bit is 0, indicating that the receiving UE does not agree to serve as a SL positioning service UE. The bit value corresponding to the first bit is 1, indicating that the receiving UE agrees to serve as a SL positioning service UE.

[1135] In some embodiments, the bit value corresponding to the first bit is 1, indicating that the receiving UE does not agree to serve as a SL positioning service UE. The bit value corresponding to the first bit is 0, indicating that the receiving UE agrees to serve as a SL positioning service UE.

[1136] In some embodiments, when the response message indicates that the recipient UE does not agree to serve as the SL positioning service UE, the target UE redetermines the SL positioning service UE.

[1137] In some embodiments, when the target UE does not receive a response message, the target UE re-determines the SL positioning service UE.

[1138] In some embodiments, the receiving module 42 is configured to receive a confirmation message sent by the target UE;

[1139] The confirmation message is used to confirm that the receiving UE serves as the SL positioning service UE.

[1140] In some embodiments, the confirmation message is used to confirm that the recipient UE is a SL positioning service UE.

[1141] In some embodiments, the confirmation message is also called at least one of SL positioning service UE confirmation message, SL positioning service confirmation message, SL positioning UE confirmation message, SL positioning confirmation message, positioning service UE confirmation message, positioning service confirmation message, and positioning confirmation message.

[1142] In some embodiments, the confirmation message is also called at least one of SL positioning service UE role confirmation message, SL positioning service role confirmation message, SL positioning UE role confirmation message, SL positioning role confirmation message, positioning service UE role confirmation message, positioning service role confirmation message, and positioning role confirmation message.

[1143] In some embodiments, the sending module 44 is configured to send a notification message to at least one anchor UE;

[1144] The notification message is used to indicate the SL positioning service UE.

[1145] In some embodiments, the SL positioning service UE is a UE that undertakes the SL positioning service UE function.

[1146] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning UE, SL service UE, positioning UE, and positioning service UE.

[1147] In some embodiments, the SL positioning service UE is also referred to as at least one of SL positioning service role UE, SL positioning role UE, SL service role UE, positioning role UE, positioning service role UE, and role UE.

[1148] In some embodiments, the SL positioning service UE is one of the following UEs:

[1149] Target UE;

[1150] Anchor UE;

[1151] Other UEs except the target UE and anchor UE.

[1152] In some embodiments, the notification message is used to indicate the SL positioning service UE that assumes the SL positioning service UE function.

[1153] In some embodiments, the notification message is also called at least one of SL positioning service UE notification message, SL positioning service notification message, SL positioning UE notification message, SL positioning notification message, positioning service UE notification message, positioning service notification message, and positioning notification message.

[1154] In some embodiments, the notification message is also called at least one of SL positioning service UE role notification message, SL positioning service role notification message, SL positioning UE role notification message, SL positioning role notification message, positioning service UE role notification message, positioning service role notification message, and positioning role notification message.

[1155] In some embodiments, the notification message carries identification information of the SL positioning service UE.

[1156] In some embodiments, the notification message also carries identification information of the target UE.

[1157] In some embodiments, the notification message also carries a positioning session identifier (SLPP Session ID) information, which is used to indicate that for a specific positioning session and / or a specific ranging / SL positioning service request, the SL positioning service UE assumes the SL positioning service UE function. The positioning session identifier information is used to distinguish different positioning sessions or ranging / SL positioning service requests.

[1158] In some embodiments, the identification information includes user information.

[1159] In some embodiments, the user information may be a user ID.

[1160] In some embodiments, the user information may be a layer-2 ID.

[1161] In some embodiments, the user information may be an application layer ID.

[1162] In some embodiments, the notification message may be sent via at least one of broadcast, unicast, and multicast.

[1163] In some embodiments, the notification message does not carry identification information of the SL positioning service UE.

[1164] In some embodiments, the notification message is also used to indicate that the SL positioning service UE is this UE.

[1165] In some embodiments, when the identification information of the SL positioning service UE in the notification message does not exist, it is understood that the SL positioning service UE indicated is the current UE.

[1166] In some embodiments, when the identification information of the SL positioning service UE in the notification message is a special ID, it is understood that the SL positioning service UE indicates this UE.

[1167] In some embodiments, the notification message carries bit indication information. When the bit value of the bit indication information is 1 or true, it indicates that the SL positioning service UE indication is this UE.

[1168] In the above case, the notification message may not carry the identification information of the SL positioning service UE, saving signaling overhead.

[1169] In some embodiments, the notification message carries bit indication information. When the bit value of the bit indication information is 0 or false, or the notification message does not carry the bit indication information, the notification message needs to carry complete identification information of the SL positioning service UE.

[1170] In some embodiments, the notification message carries at least one of the following information:

[1171] SLPP Positioning Assistant Data;

[1172] ·Announcement message of SL discovery process;

[1173] Request message of the SL discovery process;

[1174] NAS (None Access Stratum) signaling

[1175] In some embodiments, the notification message is carried in metadata of the announcement message and / or the request message to save signaling interaction.

[1176] In some embodiments, the roles of the declared UE include target UE, SL positioning service UE, anchor UE, and anchor UE that can obtain its own position. Declaring the UE role as a SL positioning service UE means that the declared UE can assume the functions of a SL positioning service UE. However, it does not determine the SL positioning service UE for a specific SL positioning service request.

[1177] In some embodiments, the notification message is carried in the metadata of the declaration message, and by introducing a new UE role, such as "authorized service UE" or "confirmed service UE", it implicitly indicates that it is a SL positioning service UE, which is used to save signaling interaction.

[1178] In some embodiments, the notification message is carried in the SL positioning assistance information. The SL positioning assistance information is sent in a broadcast or multicast manner. The SL positioning service UE carries the notification message in the SL positioning assistance information. Even if the target UE may have different positioning service requests, the SL positioning assistance information itself is within a certain positioning session. Therefore, there is no need to additionally indicate the positioning session identification information, and no new signaling may be introduced, thereby saving signaling interaction.

[1179] In some embodiments, the sending modules 44 for implementing different functions can be implemented as the same sending module or as different sending modules. The receiving modules 42 for implementing different functions can be implemented as the same receiving module or as different receiving modules. This embodiment does not impose any restrictions on this.

[1180] Figure 19 shows a structural diagram of a communication device (terminal or network device or SL positioning device) provided by an exemplary embodiment of the present application. The communication device includes: a processor 101, a receiver 102, a transmitter 103, a memory 104 and a bus 105.

[1181] The processor 101 includes one or more processing cores. The processor 101 executes various functional applications and information processing by running software programs and modules.

[1182] The receiver 102 and the transmitter 103 may be implemented as a communication component, which may be a communication chip, and may be referred to as a transceiver.

[1183] The memory 104 is connected to the processor 101 via a bus 105 .

[1184] The memory 104 may be used to store at least one instruction, and the processor 101 may be used to execute the at least one instruction to implement each step in the above method embodiment.

[1185] In addition, the memory 104 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, and programmable read-only memory (PROM).

[1186] Among them, when the communication device is implemented as a terminal, the processor and transceiver in the communication device involved in the embodiments of the present application can execute the steps performed by the terminal in any of the methods shown above, which will not be repeated here.

[1187] In some embodiments, when the above-mentioned communication device is implemented as a terminal, the terminal includes:

[1188] processor;

[1189] a transceiver connected to the processor;

[1190] a memory for storing executable instructions for the processor;

[1191] The processor is configured to load the executable instructions so that the terminal implements the method for sending a notification message of the above method embodiment.

[1192] The present application also provides a computer-readable storage medium, in which executable instructions are stored. The executable instructions are loaded and executed by a processor to implement the method for sending a notification message of the above method embodiment.

[1193] The present application also provides a chip, which includes a programmable logic circuit or a program, and the chip is used to implement the method for sending a notification message of the above method embodiment based on the programmable logic circuit or program.

[1194] The present application also provides a computer program product, which includes computer instructions, which are stored in a computer-readable storage medium. The processor of a communication device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the communication device executes the notification message sending method of the above-mentioned method embodiment.

[1195] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[1196] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A communication method applied to SL positioning service scenarios, characterized in that: The method comprises: The target UE receives the ranging / SL positioning service request; The target UE determines the SL positioning service UE; Among them, the SL positioning service UE is a UE used to undertake the SL positioning service function.

2. The method according to claim 1, characterized in that The target UE determines the SL positioning service UE based on at least one of the following information: RSRP reference signal received power information between the first UE and at least one anchor UE; Indication information of whether SL unicast communication can be established between the first UE and the at least one anchor UE; The number of SL unicast communications that can be established between the first UE and the at least one anchor UE; The first UE is one of a plurality of UEs, and the plurality of UEs are UEs that perform capability exchange with the target UE.

3. The method according to claim 1, characterized in that The target UE determines the SL positioning service UE based on at least one of the following information: RSRP information between the first UE and each anchor UE in the UE list; Indication information of whether SL unicast communication can be established between the first UE and each anchor UE in the UE list; The number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list; The first UE is one of a plurality of UEs, the plurality of UEs are UEs that perform capability exchange with the target UE, and the UE list is a subset of a set consisting of at least one anchor UE.

4. The method according to claim 1, characterized in that: The target UE determines the SL positioning service UE based on at least one of the following information: RSRP information between the second UE and at least one anchor UE; Indication information of whether SL unicast communication can be established between the second UE and the at least one anchor UE; The number of SL unicast communications that can be established between the second UE and the at least one anchor UE; Among them, the second UE is one of the candidate UEs, and the candidate UE is a UE that is a candidate to become the SL positioning service UE.

5. The method according to claim 1, characterized in that The target UE determines the SL positioning service UE based on at least one of the following information: RSRP information between the second UE and each anchor UE in the UE list; Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list; The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list; The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the UE list is a subset of a set consisting of at least one anchor UE.

6. The method according to any one of claims 1 to 5, characterized in that: After the target UE receives the ranging / SL positioning service request and before the target UE determines the SL positioning service UE, the method further includes: The target UE sends a request message to the SL positioning service UE; The target UE receives a response message returned by the SL positioning service UE; The request message is used to request the receiving UE to serve as the SL positioning service UE, and the response message is used to indicate whether the receiving UE agrees to serve as the SL positioning service UE.

7. The method according to claim 6, characterized in that The method further comprises: In the case where the response message indicates that the receiving UE does not agree to serve as the SL positioning service UE, re-determine the SL positioning service UE; or, If the response message is not received, the SL positioning service UE is re-determined.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: The target UE sends a capability request message to the multiple UEs; The target UE receives capability response messages returned by the multiple UEs; The target UE determines the SL positioning service UE, including: The target UE determines the SL positioning service UE according to the capability response message.

9. The method according to claim 8, characterized in that The capability request message is further used to instruct a first UE among the multiple UEs to return at least one of the following information to the target UE: RSRP information between the first UE and at least one anchor UE; Indication information of whether SL unicast communication can be established between the first UE and the at least one anchor UE; The number of SL unicast communications that can be established between the first UE and the at least one anchor UE; The first UE is one of a plurality of UEs, and the plurality of UEs are UEs that perform capability exchange with the target UE.

10. The method according to claim 8, characterized in that The capability request message is further used to instruct a first UE among the multiple UEs to return at least one of the following information to the target UE: RSRP information between the first UE and each anchor UE in the UE list; Indication information of whether SL unicast communication can be established between the first UE and each anchor UE in the UE list; The number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list; The first UE is one of a plurality of UEs, the plurality of UEs are UEs that perform capability exchange with the target UE, and the UE list is a subset of a set consisting of at least one anchor UE.

11. The method according to claim 9, characterized in that The capability response message is further used to carry at least one of the following information of the first UE among the multiple UEs: RSRP information between the first UE and the at least one anchor UE; Indication information of whether SL unicast communication can be established between the first UE and the at least one anchor UE; The number of SL unicast communications that can be established between the first UE and the at least one anchor UE.

12. The method according to claim 8, characterized in that The capability response message is further used to carry at least one of the following information of the first UE among the multiple UEs: RSRP information between the first UE and each anchor UE in the UE list; Indication information of whether SL unicast communication can be established between the first UE and each anchor UE in the UE list; The number of SL unicast communications that can be established between the first UE and all anchor UEs in the UE list.

13. The method according to claim 4 or 5, characterized in that After the target UE receives the ranging / SL positioning service request and before the target UE determines the SL positioning service UE, the method further includes: The target UE sends a request message to multiple second UEs; The target UE receives response messages returned by the multiple second UEs; The request message is used to request the second UE to serve as the SL positioning service UE, and the response message is used to indicate whether the second UE agrees to serve as the SL positioning service UE.

14. The method according to claim 13, characterized in that The request message is also used to instruct the second UE to return at least one of the following information to the target UE: RSRP information between the second UE and at least one anchor UE; Indication information of whether SL unicast communication can be established between the second UE and the at least one anchor UE; The number of SL unicast communications that can be established between the second UE and the at least one anchor UE; Among them, the second UE is one of the candidate UEs, and the candidate UE is a UE that is a candidate to become the SL positioning service UE.

15. The method according to claim 13, characterized in that The request message is also used to instruct the second UE to return at least one of the following information to the target UE: RSRP information between the second UE and each anchor UE in the UE list; Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list; The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list; The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the UE list is a subset of a set consisting of at least one anchor UE.

16. The method according to claim 14, characterized in that The response message is further used to carry at least one of the following information of the second UE: RSRP information between the second UE and the at least one anchor UE; Indication information of whether SL unicast communication can be established between the second UE and the at least one anchor UE; The number of SL unicast communications that can be established between the second UE and the at least one anchor UE.

17. The method according to claim 15, characterized in that The response message is further used to carry at least one of the following information of the second UE: RSRP information between the second UE and each anchor UE in the UE list; Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list; The number of SL unicast communications that can be established between the second UE and all anchor UEs in the UE list.

18. The method according to any one of claims 13 to 17, characterized in that: The target UE determines the SL positioning service UE, including: The target UE determines the SL positioning service UE based on the response message.

19. The method according to claim 18, characterized in that After the target UE determines the SL positioning service UE according to the response message, the method further includes: The target UE sends a confirmation message to the SL positioning service UE; The confirmation message is used to confirm that the receiving UE serves as the SL positioning service UE.

20. The method according to any one of claims 2 to 19, characterized in that: The RSRP information is obtained based on the measurement of the announcement message in the SL discovery process.

21. The method according to any one of claims 2 to 19, characterized in that: The RSRP information is obtained based on the measurement of the request message in the SL discovery process.

22. The method according to any one of claims 2 to 19, characterized in that: The indication information is determined based on a size relationship between the RSRP information and RSRP threshold information.

23. The method according to any one of claims 8 to 12, characterized in that: The capability request message also carries the RSRP threshold information.

24. The method according to any one of claims 13 to 17, characterized in that: The request message also carries the RSRP threshold information.

25. The method according to any one of claims 1 to 24, characterized in that: After the target UE determines the SL positioning service UE, the method further includes: The target UE sends a notification message to at least one anchor UE; Wherein, the notification message is used to indicate the SL positioning service UE.

26. The method according to claim 25, characterized in that The notification message carries at least one of the following information: SL positioning assistance information; Announcement message of SL discovery process; A request message of the SL discovery process; NAS non-access stratum signaling.

27. The method according to claim 25 or 26, characterized in that The notification message carries the identification information of the SL positioning service UE.

28. The method according to claim 27, characterized in that The notification message also carries the identification information of the target UE.

29. The method according to any one of claims 25 to 28, characterized in that: The SL positioning service UE is one of the following UEs: the target UE; The anchor UE; Other UEs except the target UE and the anchor UE.

30. A communication method applied to SL positioning service scenario, characterized in that: The method comprises: The second UE receives a request message sent by the target UE; The second UE sends a response message to the target UE, where the response message carries information used by the target UE to determine the SL positioning service UE; The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the request message is used to request the second UE to serve as the SL positioning service UE.

31. The method according to claim 30, characterized in that The response message carries at least one of the following information: RSRP information between the second UE and at least one anchor UE; Indication information of whether SL unicast communication can be established between the second UE and the at least one anchor UE; The number of UEs that can establish SL unicast communication between the second UE and the at least one anchor UE.

32. The method according to claim 30, characterized in that The response message carries at least one of the following information: RSRP information between the second UE and each anchor UE in the UE list; Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list; The number of UEs that can establish SL unicast communication between the second UE and all anchor UEs in the UE list; The UE list is a subset of a set consisting of at least one anchor UE.

33. The method according to claim 31, characterized in that The request message is also used to instruct the second UE to return at least one of the following information to the target UE: RSRP information between the second UE and the at least one anchor UE; Indication information of whether SL unicast communication can be established between the second UE and the at least one anchor UE; The number of UEs that can establish SL unicast communication between the second UE and the at least one anchor UE.

34. The method according to claim 32, characterized in that The request message is also used to instruct the second UE to return at least one of the following information to the target UE: RSRP information between the second UE and each anchor UE in the UE list; Indication information of whether SL unicast communication can be established between the second UE and each anchor UE in the UE list; The number of UEs that can establish SL unicast communication between the second UE and all anchor UEs in the UE list.

35. The method according to any one of claims 30 to 32, characterized in that: The response message also includes a capability response message.

36. The method according to claim 35, characterized in that The request message also includes a capability request message.

37. The method according to any one of claims 31 to 34, characterized in that: The RSRP information is obtained based on the measurement of the announcement message in the SL discovery process.

38. The method according to any one of claims 31 to 34, characterized in that: The RSRP information is obtained based on the measurement of the request message in the SL discovery process.

39. The method according to any one of claims 31 to 34, characterized in that: The indication information is determined based on a size relationship between the RSRP information and RSRP threshold information.

40. The method according to claim 39, characterized in that The request message also carries the RSRP threshold information.

41. A communication method applied to SL positioning service scenario, characterized in that: The method comprises: The SL positioning service UE receives the request message sent by the target UE; The SL positioning service UE sends a response message to the target UE; The request message is used to request the receiving UE to serve as the SL positioning service UE, and the response message is used to indicate whether the receiving UE agrees to serve as the SL positioning service UE.

42. The method according to claim 41, characterized in that The method further comprises: The SL positioning service UE receives a confirmation message sent by the target UE; The confirmation message is used to confirm that the receiving UE serves as the SL positioning service UE.

43. The method according to claim 41 or 42, characterized in that The method further comprises: The SL positioning service UE sends a notification message to at least one anchor UE; Wherein, the notification message is used to indicate the SL positioning service UE.

44. A communication method applied to SL positioning service scenario, characterized in that: The method comprises: The anchor UE receives the notification message; The notification message is used to indicate the SL positioning service UE.

45. The method according to claim 44, characterized in that The notification message carries at least one of the following information: SL positioning assistance information; Announcement message of SL discovery process; A request message of the SL discovery process; NAS signaling.

46. ​​The method according to claim 44 or 45, characterized in that The notification message carries the identification information of the SL positioning service UE.

47. The method according to claim 46, characterized in that The notification message also carries the identification information of the target UE.

48. The method according to any one of claims 44 to 47, characterized in that The SL positioning service UE is one of the following UEs: the target UE; The anchor UE; Other UEs except the target UE and the anchor UE.

49. A communication device applied to SL positioning service scenario, characterized in that: The device is used to implement a target UE, and the device includes: A receiving module, used for receiving ranging / SL positioning service requests; A determination module, used to determine the SL positioning service UE; Among them, the SL positioning service UE is a UE used to undertake the SL positioning service function.

50. A communication device applied to SL positioning service scenario, characterized in that: The device is used to implement a second UE, and the device includes: A receiving module, used to receive a request message sent by a target UE; A sending module, used to send a response message to the target UE, wherein the response message contains information used by the target UE to determine the SL positioning service UE; The second UE is one of the candidate UEs, the candidate UE is a UE that is a candidate to become the SL positioning service UE, and the request message is used to request the second UE to serve as the SL positioning service UE.

51. A communication device applied to SL positioning service scenario, characterized in that: The device is used to implement SL positioning service UE, and the device includes: A receiving module, used to receive a request message sent by a target UE; A sending module, used to send a response message to the target UE; The request message is used to request the receiving UE to serve as the SL positioning service UE, and the response message is used to indicate the receiving UE. Whether the party UE agrees to serve as the SL positioning service UE.

52. A communication device applied to SL positioning service scenario, characterized in that: The device is used to implement an anchor UE, and the device includes: A receiving module, used for receiving notification messages; The notification message is used for SL positioning service UE.

53. A terminal, characterized in that: The terminal comprises: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load the executable instructions so that the terminal implements the communication method applied to the SL positioning service scenario as described in any one of claims 1 to 48.

54. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores executable instructions, which are loaded and executed by a processor to implement the communication method applied to the SL positioning service scenario as described in any one of claims 1 to 48.

55. A chip, characterized in that: The chip includes a programmable logic circuit or a program, and the chip is used to implement the communication method applied to the SL positioning service scenario as described in any one of claims 1 to 48 based on the programmable logic circuit or the program.

56. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. The processor of the communication device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the communication device executes the communication method applied to the SL positioning service scenario as described in any one of claims 1 to 48.

Images