Information exchange method, core network device, terminal, communication device, and storage medium

Abstract

The present disclosure relates to an information exchange method, a first network element, a terminal, a communication device, and a storage medium. The method comprises: a first terminal receiving first information sent by a first network element, wherein the first information comprises at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used for exchanging the service information of the associated second terminal, and the routing identifier is used for identifying a service request; and sending second information to the second terminal on the basis of the first information, wherein the second information comprises the second message associated with the second terminal, and first identifier information, the first identifier information is used for identifying the service request, and the routing identifier is associated with the first identifier information. Therefore, when the service information of a terminal that is not connected to a network element is exchanged, the present disclosure can effectively associate a service request process with the routing identifier sent by the network element, thereby effectively improving the exchange accuracy of the service information.

Description

Information interaction method, core network equipment, terminal, communication equipment and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an information interaction method, core network equipment, a terminal, a communication device, and a storage medium. Background Art

[0002] In order to support direct communication between terminals, a sidelink (SL) communication method is introduced. Ranging refers to determining the distance between two or more terminals, or the direction from one terminal to another, through a PC5 interface. A PC5 interface refers to a communication interface between terminals, such as a short-range direct communication interface between vehicles, people, and road infrastructure. Sidelink SL positioning refers to estimating the position of a located terminal based on the sidelink SL. For example, ranging or sidelink SL positioning can be performed on a located terminal (e.g., a target terminal (target user equipment, target UE)) based on information from a terminal (e.g., a positioning terminal (located user equipment, located UE)). The reference terminal can be, for example, an SL reference terminal whose position is known or can be known in ranging or sidelink SL positioning. For another example, the relative position information of a terminal (e.g., a target terminal (target user equipment, target UE)) and another terminal (e.g., an SL reference terminal (sidelink reference user equipment, sidelink reference UE)) can be determined through ranging or sidelink SL positioning.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide an information interaction method, a core network device, a terminal, a communication device, a chip system, a storage medium, a computer program, and a computer program product, which can be applied in the field of communication technology to solve the technical problem that "the relevant technology cannot effectively associate the service business request process and the routing identifier sent by the network element when interacting with the business information of the terminal that is not connected to the network element, thereby affecting the interaction accuracy of the business information."

[0005] The present disclosure provides an information interaction method, core network equipment, a terminal, a communication device, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, an information interaction method is proposed, which is executed by a first terminal, including: receiving first information sent by a first network element, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with service information of the associated second terminal, and the routing identifier is used to identify the service request; based on the first information, sending second information to the second terminal, wherein the second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other.

[0007] According to the second aspect of an embodiment of the present disclosure, an information interaction method is proposed, which is executed by a first network element, including: sending first information to a first terminal, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with the service information of the associated second terminal, and the routing identifier is used to identify the service request.

[0008] According to a third aspect of an embodiment of the present disclosure, an information interaction method is provided, executed by a second terminal, comprising: receiving second information sent by a first terminal, wherein the second information includes: a second message associated with the second terminal and first identification information, the first identification information being used to identify a service request; and a routing identifier being associated with the first identification information, the routing identifier being used to identify the service request.

[0009] According to the fourth aspect of an embodiment of the present disclosure, a first network element is proposed, including: a transceiver module, used to send first information to a first terminal, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with the service information of the associated second terminal, and the routing identifier is used to identify the service request.

[0010] According to the fifth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: a transceiver module, used to receive first information sent by a first network element, wherein the first information comprises: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with the service information of the associated second terminal, the routing identifier is used to identify the service request, and based on the first information, second information is sent to the second terminal, wherein the second information comprises: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other; or, a transceiver module, used to receive second information sent by the first terminal, wherein the second information comprises: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, the routing identifier and the first identification information are associated with each other, and the routing identifier is used to identify the service request.

[0011] According to the sixth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the information interaction method of any one of the first aspect, the second aspect, and the third aspect.

[0012] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a first terminal, a first network element, and a second terminal, wherein the first terminal is configured to implement the information interaction method of the first aspect, the first network element is configured to implement the information interaction method of the second aspect, and the second terminal is configured to implement the information interaction method of the third aspect.

[0013] According to the eighth aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes an information interaction method as described in any one of the first, second, and third aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0015] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0016] FIG2A is an interaction diagram illustrating an information interaction method according to an embodiment of the present disclosure;

[0017] FIG2B is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure;

[0018] FIG3A is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure;

[0019] FIG3B is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure;

[0020] FIG3C is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure;

[0021] FIG4A is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure;

[0022] FIG4B is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure;

[0023] FIG5A is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure;

[0024] FIG5B is an interaction diagram illustrating an information interaction method according to yet another embodiment of the present disclosure;

[0025] FIG6 is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure;

[0026] FIG7A is a schematic diagram of SLPP message exchange according to an embodiment of the present disclosure;

[0027] FIG7B is a schematic diagram of SLPP message exchange according to another embodiment of the present disclosure;

[0028] FIG8A is a schematic structural diagram of a first network element proposed in an embodiment of the present disclosure;

[0029] FIG8B is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure;

[0030] FIG9A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0031] FIG9B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] The present disclosure provides an information interaction method and apparatus, a communication device, a communication system, and a storage medium. In some embodiments, the terms "information interaction method" and "information processing method" and "communication method" are interchangeable; the terms "information interaction apparatus" and "information processing apparatus" and "communication apparatus" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0033] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0034] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0035] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0036] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0037] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0038] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0039] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0040] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0041] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0042] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0043] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0044] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0045] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0046] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0047] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0048] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0049] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0050] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0051] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 may include a terminal 101 and a core network device 102 .

[0052] In some embodiments, the terminal 101 may include, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0053] In some embodiments, the core network device 102 may be a single device including a first network element 1021, a second network element 1022, a third network element 1023, etc., or may be a plurality of devices or a device group including all or part of the first network element 1021, the second network element 1022, and the third network element 1023. The network elements may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0054] In some embodiments, the first network element 1021 is, for example, a location management function (LMF) network element that provides positioning services, although the name is not limited thereto. The LMF network element is located on the core network (CN) side and is used to provide location management function services to terminals. The LMF network element is used to coordinate the overall positioning and resource scheduling of terminals registered with or accessing the 5G core network (5GCN).

[0055] In some embodiments, the first network element 1021 is used to provide location management functionality.

[0056] In some embodiments, the second network element 1022 is, for example, an Access and Mobility Management Function (AMF) network element, but the name is not limited thereto. The AMF network element is a logical node function network element on the core network side. It is the core network control plane access point for terminals and wireless devices, receives all connection and session-related information from user equipment, and performs registration, connection, reachability, and mobility management. In addition, the AMF network element provides a session management message transmission channel for terminal devices and session management function (SMF) devices, and provides authentication and authorization functions for user access.

[0057] In some embodiments, the second network element 1022 is used to provide access and mobility management functions.

[0058] In some embodiments, the third network element 1023 is, for example, a network element that can process external positioning requests, trigger the network to initiate positioning, and return the positioning result to the client that initiated the positioning.

[0059] In some embodiments, the third network element 1023 is, for example, a Gateway Mobile Location Center (GMLC) network element, but the name is not limited thereto.

[0060] In some embodiments, the terminal 101 and the core network device 102 can be connected through an access network device. Optionally, the access network device is, for example, a node or device that accesses the terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0061] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0062] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0063] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other user plane connection establishment methods, and next-generation systems based on and extending these systems. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0064] Optionally, the target terminal is a terminal whose distance, direction and / or position is measured based on SL in ranging or SL service with the support of one or more SL reference terminals.

[0065] Optionally, the SL reference terminal is a terminal that supports positioning of a target terminal, for example, by using SL to send and / or receive reference signals for positioning, provide information related to positioning, etc.

[0066] Optionally, the positioning terminal is a SL reference terminal whose position is known or can be known using positioning based on the Uu interface. The positioning terminal can be used to determine the position of the target terminal using SL positioning.

[0067] Optionally, the SL positioning client terminal refers to a third-party terminal other than the SL reference terminal, target terminal, positioning terminal, etc., which initiates ranging or SL positioning service requests on behalf of the application resident thereon.

[0068] Optionally, in the SL positioning process involving 5GC, the position of the target terminal can be estimated with the help of the network by using the position of one or more positioning terminals, and the distance and / or direction between the target terminal and the positioning terminal, or the relative position, or distance and direction between the target terminal and one or more SL reference terminals, without limitation.

[0069] Optionally, the ranging / SL positioning results may include: absolute position, relative position, distance, and direction, depending on the service requirements. If the target terminal decides to initiate the Sidelink Mobile Originated Location Request (SL-MO–LR) process, the target terminal may include information about one or more SL reference terminals and / or positioning terminals in the service request message. If the Location Services Client (LCS Client) or Application Function (AF) network element decides to obtain ranging / SL positioning results for a group of n terminals (n≥2), i.e., terminal 1, terminal 2, ..., terminal n, the Gateway Mobile Location Center (GMLC) may specify the target terminal from the n terminals, and specify one or more reference terminals and / or positioning terminals, and then the Sidelink Mobile Terminated Location Request (SL-MT–LR) process may be applied.

[0070] Optionally, the 5GC Mobile Originated Location Request (5GC-MO-LR) and 5GC Mobile Terminated Location Request (5GC-MT-LR) services can be applied to obtain the absolute position of the target terminal based on SL positioning.

[0071] Optionally, in a process involving SL positioning and 5GC for terminal positioning, the capabilities of all terminals are transmitted to the LMF network element, but only one terminal (e.g., a target terminal with a non-access stratum (NAS) connection) is directly connected to the LMF network element.

[0072] Optionally, in addition to exchanging terminal capabilities related to ranging / SL positioning, the sidelink positioning protocol (SLPP) also supports the exchange of auxiliary data required for ranging / SL positioning, and exchanges measurement data and / or results of ranging / SL positioning in the ranging / SL positioning process, wherein the auxiliary data is provided by the LMF network element or requested by the terminal and provided by the LMF network element, and the measurement data and / or results are provided by the terminal or requested by the LMF network element and provided by the terminal.

[0073] Optionally, in some communication protocols, SLPP sessions are used between terminals or between a positioning server and a terminal to obtain location-related measurements, location estimates, or transmission assistance data based on NR PC5 radio signals. A single SLPP session is used to support a single location request (for example, for a single SL-MT-LR or SL-MO-LR). Multiple SLPP sessions can be used between the same endpoints to support multiple different location requests. For operations involving only terminals, the initiator of the SLPP session (i.e., the endpoint that receives the LCS request) initiates the SLPP session by sending an SLPP message containing an assigned session ID (session identifier) ​​to the other endpoints. All component messages in the session should contain the same session ID. For operations involving LMF, the session identifier (IDentifier, ID) is allocated by the target terminal and included in the SLPP message used for communication between terminals. The session ID can be included in the SLPP message for communication between the target terminal and the location management function network element LMF (Location Management FUEnction, LMF).

[0074] Optionally, each SLPP session includes one or more SLPP interactions. Each SLPP interaction (SLPP transaction) performs a single operation (capability exchange, auxiliary data transmission, or location information transmission). The SLPP interaction is implemented as an SLPP process. The initiator of the SLPP session always initiates the first SLPP interaction, but subsequent services may be initiated by either end. The SLPP interactions in the session can occur serially or in parallel. The SLPP interaction is represented by a transaction identifier (ID) at the SLPP protocol level to associate messages with each other (for example, requests and responses).

[0075] Optionally, messages in an SLPP interaction are associated by a common interaction identifier.

[0076] Optionally, according to the definition of some communication protocols, the LCS association identifier is allocated in the AMF when sending a location request to the LMF, and the LCS association identifier is used as the session ID between the AMF network element and the LMF network element, and as the routing identifier between UE1 and AMF, used to identify the LMF that provides services for the location request served by the exchange information. The relevant messages exchanged between UE1 and AMF include supplementary service messages or SLPP messages.

[0077] Optionally, the session identification ID in the SLPP message can be used to correlate all SLPP messages to support a single location request.

[0078] Optionally, the ranging or line link positioning capabilities can be exchanged, ranging or line link positioning auxiliary data can be exchanged, or ranging or line link positioning measurement data / results can be exchanged. Only SLPP messages are supported between UE1 and LMF, and SLPP messages are supported between UE1 and UE2 to UEn. UE1 can associate the messages of UE2 to UEn with the location requests by using the session ID in the SLPP messages of UE2 to UEn and the routing identifier in the supplementary service messages exchanged between UE1 and LMF, where UE1 is the terminal connected to the LMF, and UE2 to UEn are other UEs other than the UE connected to the LMF. It should be noted that the connection between the terminal and the LMF means that the terminal can establish a NAS connection with the network and interact with the LMF of the service terminal through the AMF. Except for the terminal that establishes a NAS connection, other terminals interact with the network through the terminal that establishes a NAS with the network.

[0079] Optionally, in some cases, SLPP messages related to UE2~UEn are transparently transmitted between UE 2 to UEn and LMF through UE1, for example, LMF requests location information and measurement data from UE2~UEn, and UE2~UEn responds to LMF, LMF provides auxiliary data to UE2~UEn, LMF requests UE2~UEn and responds to LMF, but when the SLPP messages of UE2~UEn are transparently transmitted in UE1, UE-1 cannot determine which location request these SLPP messages serve.

[0080] Therefore, it is necessary to improve the SLPP message transmission involving LMF to support transparent transmission of SLPP messages related to UE2~UEn between UE2~UEn and LMF through UE1, so as to accurately deliver messages related to their related location requests.

[0081] Figure 2A is a schematic diagram illustrating an information interaction method according to an embodiment of the present disclosure. As shown in Figure 2A, the present disclosure embodiment relates to an information interaction method that can be used in a communication system 100, which includes a first network element, a first terminal, and at least one second terminal. The method includes:

[0082] Step S2101: A first network element sends first information to a first terminal.

[0083] The first information includes: at least one second message and a routing identifier. The second message is associated with a second terminal and is used to exchange service information of the associated second terminal. The routing identifier is used to identify a service request, or in other words, to identify the process corresponding to the service request. That is, the routing identifier carried in the first information indicates that the information serves the service request or the process corresponding to the service request corresponding to the routing identifier. For example, the information exchange involved in the entire process of a specific service request can be associated through the routing identifier, and the processes of multiple service requests can also share the routing identifier.

[0084] In some embodiments, the first network element may specifically be, for example, a location management function (LMF) network element. The first terminal may be a terminal connected to the first network element among multiple terminals. If applied to ranging / SL positioning services, the first terminal may be, for example, a target terminal or a positioning terminal or a SL reference terminal (SL Reference UE), without limitation. The terminal being connected to the first network element means that the terminal interacts with the first network element by being connected to the network, and there is no limitation on the terminal being directly connected to the first network element. For example, the terminal being connected to the LMF means that the terminal can establish a NAS connection with the network and interact with the LMF of the service terminal through the AMF.

[0085] In some embodiments, the second terminal refers to a terminal that is not connected to the first network element. If applied to ranging / SL positioning services, the second terminal may be, for example, a positioning terminal, a SL reference terminal (SL Reference UE), or a target terminal, without limitation.

[0086] In some embodiments, the first information may be carried by a supplementary ranging or sidelink positioning protocol (Ranging and Sidelink Positioning Protocol, RSPP) transmission request message, for example, the first network element sends the first information by sending a supplementary RSPP transmission request message to the first terminal.

[0087] In some embodiments, the first terminal may execute multiple service requests with the first network element, and the routing identifier may be used to identify one or several of the service requests to ensure accurate data communication between the first terminal and the first network element.

[0088] In some embodiments, the service information may include at least one of the following: terminal capabilities, service results, service measurement data, and service assistance data, so that at least one of the terminal capabilities, service results, service measurement data, and service assistance data of the second terminal can be accurately transmitted.

[0089] Among them, terminal capability refers to the functions and capabilities of the terminal. For example, in ranging or SL positioning services, the terminal capability may be the SL positioning method supported by the terminal. Service results refer to the service execution results generated during the service interaction process. For example, in ranging or SL positioning services, the service results may be the actual positioning calculation results obtained after making a location request to the target terminal. Service measurement data refers to the relevant measurement data during the service execution process. For example, in ranging or SL positioning services, the service measurement data may be information used by the relevant terminal to calculate the position, such as positioning signal measurement information. Service auxiliary data refers to some data that assists in the implementation of the service. In ranging or SL positioning services, service auxiliary data may be, for example, measurement signal information configured for the positioning terminal or target terminal, or position calculation information that assists in positioning the target terminal. There is no limitation on this.

[0090] In some embodiments, the service information may include terminal capabilities, service results, and service measurement data. The first network element may request the second terminal, via the first terminal, to obtain the second terminal's terminal capabilities, service results, and service measurement data. For example, if applied to a ranging / SL positioning service, the first terminal may be, for example, a target terminal, and the second terminal, as a neighboring positioning terminal, may request the first terminal's absolute position with the help of the second terminal. The first network element may then request the second terminal's terminal capabilities, service results, and service measurement data from the second terminal, as a positioning terminal, via the first terminal connected to the first network element.

[0091] In some embodiments, the first information also includes at least one of the following: at least one second terminal information, wherein the second terminal information is used to describe the second terminal and indicate the business information of the first terminal to interact with the corresponding second terminal, a second terminal information list, wherein the second terminal information list includes: at least one second terminal information, a first message, wherein the first message is used to interact with the business information of the first terminal, and indication information, wherein the indication information is used to instruct the first terminal to forward the second message. Since the first information can contain multiple types of information, the rich data effectively improves the flexibility of information sending, so that it can be applied to multiple business scenarios.

[0092] In some embodiments, multiple second terminals may exist in a business scenario. In this case, the second terminal information may be included in the first information. The second terminal information may also indicate that the first terminal and the corresponding second terminal exchange the corresponding second terminal's business information. The first information may also include a second terminal information list, which may include one or more second terminal information. The first information may also include a first message and an indication message. The first message may be used to exchange the first terminal's business information, and the indication message may be used to instruct the first terminal to forward the second message, thereby ensuring the accuracy of the business information transmission between the first and second terminals.

[0093] In some embodiments, the first terminal receives the first information sent by the first network element. After the first network element sends the first information to the first terminal, the first terminal can receive the first information sent by the first network element, so that the first terminal can receive the first message to carry out subsequent business information transmission process.

[0094] In some embodiments, the first terminal receives a first supplementary service request message sent by the first network element, wherein the first supplementary service request message includes first information, and the second message is used to request terminal capabilities and / or service results and / or service measurement data of the associated second terminal.

[0095] In some embodiments, when a first terminal receives first information sent by a first network element, the first network element may send a first supplementary service transmission message to the first terminal, wherein the first supplementary service transmission message includes the first information, and the first terminal receives the first supplementary service request message sent by the first network element, so that the first terminal receives the first information carried in the first supplementary service request message, and the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with the service information of the associated second terminal, and the routing identifier is used to identify the service request.

[0096] In some embodiments, the first terminal receives a first supplementary service transmission message sent by the first network element, wherein the first supplementary service transmission message includes first information, and the second message is used to request terminal capabilities and / or service results and / or service measurement data of the associated second terminal.

[0097] In some embodiments, the first network element may use a first supplementary service transmission message that is different from the first supplementary service request message. The first network element sends the first message to the first network element by sending the first supplementary service transmission message to the first terminal. Since the first information can be transmitted using either the supplementary service request message or the supplementary service transmission message, the flexibility of information sending can be effectively improved, and thus it can be applicable to a variety of business scenarios.

[0098] Step S2102: The first terminal sends second information to the second terminal based on the first information.

[0099] The second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other.

[0100] In an embodiment of the present disclosure, a first terminal can associate a routing identifier sent by a first network element with first identification information to identify a service request. Specifically, during information exchange between a first terminal and a second terminal, first identification information is transmitted and associated with the routing identifier exchanged between the first terminal and the first network element. During downlink communication, the association can be performed on the first terminal and then transmitted to the second terminal. During uplink communication, after receiving the first identification information sent by the second terminal, the first terminal can determine the routing identifier exchanged between the first network elements based on the first representation information, thereby determining to which first network element the information carrying the first identification should be sent. This allows the first terminal to accurately locate the routing identifier based on the first identification information received from the second terminal and send information to the first network element based on the routing identifier. This allows the first terminal to effectively associate the service request process with the routing identifier sent by the network element when exchanging service information with a terminal not connected to the network element, thereby effectively improving the accuracy of service information exchange.

[0101] In some embodiments, the first identification information includes at least one of the following: an association identifier, a routing identifier. Using the association identifier and / or the routing identifier to identify the service request process can effectively ensure accurate transmission of service information.

[0102] In some embodiments, a service request may be identified based on a correlation identifier, a routing identifier, or both. For example, to identify a process for a service request, multiple service request processes may share a correlation identifier and / or a routing identifier.

[0103] In some embodiments, the first identification information and the routing identifier have a mapping relationship, and / or the first identification information and the SLPP session information have a mapping relationship, wherein the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for the business service, and / or the routing identifier and the SLPP session information have a mapping relationship, which can effectively improve the identification accuracy of the association identifier and / or the routing identifier.

[0104] In some embodiments, the mapping relationship between the first identification information and the routing identifier can be one-to-one, and / or the mapping relationship between the first identification information and the SLPP session information can be one-to-one, and / or the mapping relationship between the routing identifier and the SLPP session information can be one-to-one, without limitation.

[0105] In some embodiments, the first identification information includes at least one of the following: an association identifier and a routing identifier. A message between the first terminal and the second terminal includes a correlation identifier to identify the positioning service served by the message. The association identifier can be allocated by the first terminal and has a one-to-one mapping relationship with the received routing identifier and / or SLPP session information allocated for the SLPP session. The SLPP session also has a one-to-one mapping relationship with the routing identifier. The first identification information is a routing identifier, that is, the message between the first terminal and the second terminal includes a routing identifier sent by the first network element, which is used to associate the process of the service request for the message interaction service between the first terminal and the second terminal with the process of the service request corresponding to the routing identifier sent by the network element.

[0106] In some embodiments, the association identifier and the routing identifier have the same value, and / or the association identifier and the SLPP session information have the same value, wherein the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for the business service.

[0107] In some embodiments, the association identifier may have the same value as the routing identifier and / or SLPP session information allocated for the SLPP session, where the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for the service.

[0108] Therefore, the flexibility of configuring the association identifier and / or routing identifier can be effectively improved, and can be effectively applied to personalized application scenarios.

[0109] In some embodiments, the second information may be carried by a second supplementary service transmission message. For example, the second supplementary service transmission message may be a supplementary RSPP service message, which may be a general message used to transmit SLPP messages between terminals, so that the first terminal can send the second information to the second terminal.

[0110] In some embodiments, first identification information can be transmitted during the interaction between the first terminal and the second terminal. The first identification information can be associated with the routing identifier for the interaction between the terminal and the first network element. Therefore, when interacting with business information of a terminal that is not connected to the network element, the business request process and the routing identifier sent by the network element can be effectively associated, thereby effectively improving the interaction accuracy of the business information.

[0111] In some embodiments, the first terminal determines the first identification information based on the routing identifier, thereby being able to accurately determine the first identification information associated with the routing identifier.

[0112] In some embodiments, the first terminal determines the first identification information based on the routing identifier, including any of the following: if second identification information exists, associating the second identification information with the routing identifier to obtain the first identification information, where the second identification information is available identification information already allocated for the interaction between the first terminal and the second terminal based on the service request; if the second identification information does not exist, allocating new identification information to the service request and associating the routing identifier with the new identification information to obtain the first identification information. This can effectively apply to personalized service application scenarios.

[0113] In some embodiments, the first identification information is used to identify the service request. Different service requests have corresponding first identification information. The first terminal can determine the first identification information based on the routing identifier to identify different service requests. When the first terminal determines the first identification information based on the routing identifier, it can process separately whether the second identification information exists. If the second identification information exists, that is, the available identification information allocated for the interaction between the first terminal and the second terminal based on the service request, the second identification information and the routing identifier can be associated to obtain the first identification information after the association process. If the second identification information does not exist, new identification information is allocated to the service request, and the routing identifier and the new identification information are associated to obtain the first identification information.

[0114] In some embodiments, the first terminal sends a second supplementary service transmission message to the second terminal based on the first information, wherein the second supplementary service transmission message includes the second information. Thus, the supplementary service transmission message can be used to transmit the first identification information and the second message used to obtain service information of the second terminal between the first terminal and the second terminal.

[0115] In some embodiments, when the first terminal sends the second information to the second terminal based on the first information, the first information can be carried by the second supplementary service transmission message, the first message includes at least one second message and a routing identifier, the second message is associated with a second terminal, and the second supplementary service transmission message is sent to the second terminal based on the first information by the first terminal, thereby sending the second message to the second terminal.

[0116] Step S2103: The second terminal receives the second information, and sends the terminal capability and / or service result and / or service measurement data of the second terminal and the first identification information to the first terminal.

[0117] The service information includes the terminal capability and / or service results and / or service measurement data of the second terminal.

[0118] In some embodiments, the second message is associated with a second terminal, and the second message is used to interact with business information of the associated second terminal, the business information including the terminal capabilities and / or business results and / or business measurement data of the second terminal. After the second terminal receives the second information, it can obtain the required terminal capabilities and / or business results and / or business measurement data of the second terminal based on the second message associated with the second terminal in the second information, and send the terminal capabilities and / or business results and / or business measurement data of the second terminal and the first identification information to the first terminal based on the first identification information.

[0119] Step S2104: The first terminal receives the terminal capability and / or service result and / or service measurement data of the second terminal, and the first identification information.

[0120] In some embodiments, the first terminal receives a third supplementary service transmission message sent by the second terminal, where the third supplementary service transmission message includes: terminal capabilities and / or service results and / or service measurement data of the second terminal, and first identification information.

[0121] In some embodiments, the first terminal determines the routing identifier based on the first identification information sent by the second terminal.

[0122] In some embodiments, after the first terminal receives the terminal capabilities and / or service results and / or service measurement data, and the first identification information sent by the second terminal, the first terminal can map the associated routing identifier according to the first identification information, thereby carrying the corresponding routing identifier in the message received from the second terminal. Then, when the first terminal sends a message to the first network element, it carries the routing identifier, and the first terminal sends the terminal capabilities and / or service results and / or service measurement data, and the first identification information to the first network element, thereby realizing the first terminal's request for the terminal capabilities and / or service results and / or service measurement data of the second terminal.

[0123] In some embodiments, the terminal capabilities and / or service results and / or service measurement data of the second terminal, and the first identification information can be carried in a third supplementary service transmission message. The second terminal sends the third supplementary service transmission message to the first terminal, carrying the terminal capabilities and / or service results and / or service measurement data of the second terminal, so as to send the terminal capabilities and / or service results and / or service measurement data of the second terminal to the first terminal, and the first terminal receives the terminal capabilities and / or service results and / or service measurement data of the second terminal, and the first identification information.

[0124] Step S2105: The first terminal sends the terminal capability and / or service result and / or service measurement data of the second terminal and a routing identifier to the first network element.

[0125] In some embodiments, the first terminal may send a first supplementary service response message to the first network element, wherein the first supplementary service response message includes: the terminal capabilities and / or service results and / or service measurement data of the second terminal, and a routing identifier. Thus, based on the routing identifier, the first network element of the service service request process can be accurately determined, ensuring that the terminal capabilities and / or service results and / or service measurement data of the second terminal can be accurately transmitted to the corresponding first network element.

[0126] In some embodiments, after the first terminal receives the terminal capabilities and / or service results and / or service measurement data, and the first identification information of the second terminal, the first terminal can forward the received terminal capabilities and / or service results and / or service measurement data, and the first identification information of the second terminal to the first network element, so that the first network element requests to obtain the terminal capabilities and / or service results and / or service measurement data of the second terminal, wherein the terminal capabilities and / or service results and / or service measurement data, and the routing identifier of the second terminal can be carried in the first supplementary service response message, and the routing identifier can be used by the first terminal to identify the first network element that requests to obtain the terminal capabilities and / or service results and / or service measurement data of the second terminal, so as to accurately transmit the terminal capabilities and / or service results and / or service measurement data, and the routing identifier of the second terminal to the first network element.

[0127] In some embodiments, after receiving the first identification information sent by the second terminal, the first terminal can determine the routing identifier for interaction with the first network element through the first identification information, thereby determining to which first network element the information carrying the first identification should be sent or to which service request process served by the first network element to be associated. This enables the first terminal to find the accurate routing identifier based on the first identification information received from the second terminal and to send information to the first network element based on the routing identifier. This allows the first terminal to effectively associate the service request process with the routing identifier sent by the network element when interacting with service information of a terminal that is not connected to the network element.

[0128] In some embodiments, the first terminal may send a fourth supplementary service transmission message to the first network element, wherein the fourth supplementary service transmission message includes: the terminal capability and / or service results and / or service measurement data of the second terminal, and a routing identifier. Thus, based on the supplementary service transmission message carrying the routing identifier, it can also be ensured that the first terminal can accurately transmit the terminal capability and / or service results and / or service measurement data of the second terminal to the corresponding first network element.

[0129] In some embodiments, a fourth supplementary service transmission message different from the first supplementary service response message can also be used. The fourth supplementary service transmission message carries the terminal capabilities and / or service results and / or service measurement data of the second terminal, and a routing identifier. The first terminal transmits the terminal capabilities and / or service results and / or service measurement data, and the routing identifier of the second terminal to the accurate first network element based on the routing identifier.

[0130] Step S2106: The first network element receives the terminal capability and / or service result and / or service measurement data of the second terminal and the routing identifier sent by the first terminal.

[0131] In some embodiments, after the first terminal sends the terminal capabilities and / or service results and / or service measurement data, and routing identifier of the second terminal to the first network element, the first network element can receive the terminal capabilities and / or service results and / or service measurement data, and routing identifier of the second terminal sent by the first terminal.

[0132] In some embodiments, the service is a ranging or sidelink SL positioning service. For example, the service process may be: the first terminal acts as the target terminal, and the network or the application layer of the first terminal triggers a ranging or sidelink SL positioning service request, and requests the absolute position of the first terminal with the help of a neighboring positioning terminal. The second terminal is located near the first terminal that supports the ranging or sidelink SL positioning service and can serve as a neighboring positioning terminal.

[0133] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2106. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S2101+S2102 can be implemented as independent embodiments, and steps S2101+S2102+S2103 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0134] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0135] In this embodiment, a first network element sends first information to a first terminal. The first terminal sends second information to a second terminal based on the first information. The second terminal receives the second information and sends the second terminal's terminal capabilities and / or service results and / or service measurement data, and first identification information to the first terminal. The first terminal receives the second terminal's terminal capabilities and / or service results and / or service measurement data, and the first identification information. The first terminal sends the second terminal's terminal capabilities and / or service results and / or service measurement data, and a routing identifier to the first network element. The first network element receives the second terminal's terminal capabilities and / or service results and / or service measurement data, and the routing identifier sent by the first terminal. Thus, when exchanging terminal capabilities and / or service results and / or service measurement data of a terminal not connected to the network element, the service request process can be effectively associated with the routing identifier sent by the network element, effectively improving the accuracy of exchanging terminal capabilities and / or service results and / or service measurement data.

[0136] FIG2B is an interactive diagram of an information interaction method according to another embodiment of the present disclosure. As shown in FIG2B , the present disclosure embodiment relates to an information interaction method that can be used in a communication system 100. The method includes:

[0137] Step S2201: The second terminal sends third information to the first terminal.

[0138] The third information includes: a second message associated with the second terminal and first identification information.

[0139] In some embodiments, the first network element may specifically be, for example, a Location Management Function (LMF) network element. The first terminal may be a terminal connected to the first network element among multiple terminals. If applied to a ranging / SL positioning service, the first terminal may be, for example, a target terminal, without limitation.

[0140] In some embodiments, the second terminal refers to a terminal that is not connected to the first network element. If applied to ranging / SL positioning services, the second terminal may be, for example, a positioning terminal, which is not limited.

[0141] In some embodiments, the third information can be carried by a supplementary RSPP transmission request message. For example, the second terminal sends the third information by sending a supplementary RSPP transmission request message to the first terminal. The third information includes: a second message associated with the second terminal and first identification information. The second message is used to exchange service information of the associated second terminal, and the first identification information is used to identify the service request.

[0142] In some embodiments, the first terminal receives third information sent by the second terminal.

[0143] In some embodiments, after the second terminal sends the third information to the first terminal, the first terminal may receive the third information sent by the second terminal.

[0144] In some embodiments, the first terminal receives the third information sent by the second terminal, and the first terminal may receive the fifth supplementary service transmission message sent by the second terminal, wherein the fifth supplementary service transmission message includes the third information, and the second message associated with the second terminal is used to request service auxiliary data of the associated second terminal.

[0145] In some embodiments, when the first terminal receives the third information sent by the second terminal, the first terminal may receive a fifth supplementary service transmission message sent by the second terminal. The fifth supplementary service transmission message may be a general message used to transmit SLPP messages between terminals.

[0146] In some embodiments, the third information further includes at least one of the following: second terminal information, where the second terminal information is used to describe the second terminal that sends the third information, and instructs the first terminal to exchange service information of the second terminal; and indication information, where the indication information is used to instruct the first terminal to forward the second message. The second terminal information indicates that the first terminal exchanges service information of the second terminal, specifically, for example, using the second terminal information to instruct the first terminal to exchange service information of the second terminal with the first network element.

[0147] Step S2202: The first terminal sends fourth information to the first network element based on the third information.

[0148] The fourth information includes: a second message associated with the second terminal and a routing identifier.

[0149] In some embodiments, after the second terminal sends third information to the first terminal, the first terminal receives the third information sent by the second terminal. The third information may include second terminal information, and the second terminal information may be used to indicate that the first terminal exchanges service information of the second terminal with the first network element. Based on the second terminal information, the first terminal may include a second message and a routing identifier associated with the second terminal described in the second terminal information in fourth information, and send the fourth information to the first network element.

[0150] In some embodiments, after receiving the first identification information sent by the second terminal, the first terminal can determine the routing identifier for interaction with the first network element through the first identification information, thereby determining to which first network element the information carrying the first identification should be sent or to which service request process served by the first network element to be associated. This enables the first terminal to find the accurate routing identifier based on the first identification information received from the second terminal and to send information to the first network element based on the routing identifier. This allows the first terminal to effectively associate the service request process with the routing identifier sent by the network element when interacting with service information of a terminal that is not connected to the network element.

[0151] In some embodiments, the first terminal sends fourth information to the first network element based on the third information, and may send a second supplementary service request message to the first network element based on the third information, wherein the second supplementary service request message includes: the fourth information.

[0152] In some embodiments, fourth information is sent to the first network element according to the third information, and a sixth supplementary service transmission message may be sent to the first network element, wherein the sixth supplementary service transmission message includes: the fourth information.

[0153] In some embodiments, the fourth message can be carried in the sixth supplementary service transmission message. When the first terminal sends the fourth information to the first network element according to the third information, it can send the sixth supplementary service transmission message to the first network element to send the fourth message to the first network element.

[0154] Step S2203: The first network element receives the fourth information sent by the first terminal, and sends the service assistance data and the routing identifier of the second terminal to the first terminal.

[0155] The fourth information includes: a second message associated with the second terminal and a routing identifier.

[0156] Step S2204: The first terminal receives the service assistance data and the routing identifier of the second terminal.

[0157] In some embodiments, the first terminal receives a second supplementary service response message sent by the first network element, wherein the second supplementary service response message includes: service assistance data of the second terminal and a routing identifier.

[0158] In some embodiments, when the first terminal receives the service auxiliary data and routing identifier of the second terminal, the service auxiliary data and routing identifier of the second terminal can be carried in a second supplementary service response message, and the first network element sends the second supplementary service response message carrying the service auxiliary data and routing identifier of the second terminal to the first terminal. The first terminal receives the second supplementary service response message sent by the first network element to receive the service auxiliary data and routing identifier of the second terminal.

[0159] In some embodiments, a seventh supplementary service transmission message sent by the first network element is received, wherein the seventh supplementary service transmission message includes: service auxiliary data of the second terminal, and a routing identifier. Thus, the routing identifier is carried by the supplementary service transmission message, so that the service auxiliary data of the second terminal can be accurately transmitted to the first network element.

[0160] In some embodiments, a seventh supplementary service transmission message that is different from the second supplementary service response message can be used to carry the service auxiliary data and routing identifier of the second terminal. The first network element sends the second supplementary service response message to the first terminal, and the first terminal receives the seventh supplementary service transmission message sent by the first network element to receive the service auxiliary data and routing identifier of the second terminal.

[0161] Step S2205: The first terminal sends the service auxiliary data and first identification information of the second terminal to the second terminal.

[0162] In some embodiments, the first terminal determines the first identification information based on the routing identifier sent by the first network, including any of the following: if second identification information exists, the second identification information and the routing identifier are associated to obtain the first identification information, wherein the second identification information is the available identification information allocated for the interaction between the first terminal and the second terminal based on the service request; if the second identification information does not exist, new identification information is allocated to the service request, and the routing identifier sent by the first network is associated with the new identification information to obtain the first identification information.

[0163] In some embodiments, the first terminal sends an eighth supplementary service transmission message to the second terminal, where the eighth supplementary service transmission message includes: service assistance data of the second terminal and first identification information.

[0164] In some embodiments, the service auxiliary data of the second terminal and the first identification information can be carried in the eighth supplementary service transmission message. The first terminal sends the eighth supplementary service transmission message to each second terminal according to the routing identifier, thereby enabling the first terminal to send the service auxiliary data of the second terminal to each second terminal. The eighth supplementary service transmission message can be a general message used to transmit SLPP messages between the first terminal and the second terminal.

[0165] Step S2206: The second terminal receives the service assistance data and the routing identifier of the second terminal.

[0166] In some embodiments, after the first terminal sends the service assistance data and the route identifier of the second terminal to the second terminal, the second terminal may receive the service assistance data and the route identifier of the second terminal.

[0167] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2206. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S2201+S2202 can be implemented as independent embodiments, and steps S2201+S2202+S2203 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0168] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0169] In this embodiment, a second terminal sends third information to a first terminal. The first terminal sends fourth information to a first network element based on the third information. The first network element receives the fourth information sent by the first terminal and sends service assistance data and a routing identifier of the second terminal to the first terminal. The first terminal receives the service assistance data and routing identifier of the second terminal. The first terminal sends the service assistance data and routing identifier of the second terminal to the second terminal, and the second terminal receives the service assistance data and routing identifier of the second terminal. Thus, when exchanging service assistance data with a terminal not connected to the network element, the service request process can be effectively associated with the routing identifier sent by the network element, effectively improving the accuracy of exchanging service assistance data.

[0170] FIG3A is an interactive diagram of an information interaction method according to another embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information interaction method that can be used in a first terminal. The above method includes:

[0171] Step S3101: Receive first information sent by a first network element, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to exchange service information of the associated second terminal, and the routing identifier is used to identify the service request.

[0172] Step S3102: Send second information to the second terminal based on the first information, where the second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other.

[0173] The information interaction method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S3101 and S3102 may be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0174] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0175] FIG3B is an interactive diagram of an information interaction method according to another embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to an information interaction method that can be used in a first terminal. The above method includes:

[0176] Step S3201: Receive a first supplementary service request message sent by a first network element, wherein the first supplementary service request message includes first information, and the second message is used to request terminal capabilities and / or service results and / or service measurement data of an associated second terminal.

[0177] Step S3202: Determine first identification information according to the routing identifier.

[0178] Step S3203: Obtain service information of the first terminal according to the first message in the first information, wherein the first message is used to exchange service information of the first terminal, and the service information includes: terminal capabilities and / or service results and / or service measurement data.

[0179] Step S3204: Send the terminal capability and / or service result and / or service measurement data of the first terminal to the first network element.

[0180] Step S3205: Send a second supplementary service transmission message to the second terminal according to the first information, wherein the second supplementary service transmission message includes the second information.

[0181] Step S3206: Send a first supplementary service response message to the first network element, where the first supplementary service response message includes: terminal capabilities and / or service results and / or service measurement data of the second terminal, and a routing identifier.

[0182] The information interaction method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3206. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S3201+S3202 may be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0183] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0184] FIG3C is an interactive diagram of an information interaction method according to another embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to an information interaction method that can be used in a first terminal. The above method includes:

[0185] Step S3301: Receive third information sent by a second terminal, where the third information includes: a second message associated with the second terminal and first identification information.

[0186] Step S3302: Determine a routing identifier according to the first identification information sent by the second terminal.

[0187] Step S3303: Send fourth information to the first network element according to the third information, where the fourth information includes: a second message associated with the second terminal and a routing identifier.

[0188] Step S3304: Receive a fifth supplementary service transmission message sent by the second terminal, wherein the fifth supplementary service transmission message includes third information, and the second message associated with the second terminal is used to request service assistance data of the associated second terminal.

[0189] Step S3305: Send a first supplementary service response message to the first network element, where the first supplementary service response message includes: terminal capabilities and / or service results and / or service measurement data of the second terminal, and a routing identifier.

[0190] The information interaction method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3305. For example, step S3301 can be implemented as an independent embodiment, step S3302 can be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S3301+S3302 can be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0191] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0192] FIG4A is an interactive diagram of an information interaction method according to another embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to an information interaction method that can be used in a first network element. The above method includes:

[0193] Step S4101: Send first information to a first terminal, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to exchange service information of the associated second terminal, and the routing identifier is used to identify a service request.

[0194] The information interaction method involved in the embodiment of the present disclosure may include step S4101 and may be implemented as an independent embodiment, but is not limited thereto.

[0195] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0196] FIG4B is an interactive diagram of an information interaction method according to another embodiment of the present disclosure. As shown in FIG4B , the present disclosure embodiment relates to an information interaction method that can be used for a first network element. The above method includes:

[0197] Step S4201: Send a first supplementary service request message to a first terminal, wherein the first supplementary service request message includes first information, and a second message is used to request terminal capabilities and / or service results and / or service measurement data of an associated second terminal.

[0198] Step S4202: Receive terminal capabilities and / or service results and / or service measurement data of the first terminal sent by the first terminal.

[0199] The information interaction method involved in the embodiments of the present disclosure may include at least one of steps S4201 and S4202. For example, step S4201 can be implemented as an independent embodiment, step S4202 can be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S4201+S4202 can be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0200] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0201] FIG5A is an interactive diagram of an information interaction method according to another embodiment of the present disclosure. As shown in FIG5A , the present disclosure embodiment relates to an information interaction method that can be used in a second terminal. The above method includes:

[0202] Step S5101: Receive second information sent by the first terminal, wherein the second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other, and the routing identifier is used to identify the service request.

[0203] The information interaction method involved in the embodiment of the present disclosure may include step S5101 which may be implemented as an independent embodiment.

[0204] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0205] FIG5B is an interactive diagram of an information interaction method according to another embodiment of the present disclosure. As shown in FIG5B , the present disclosure embodiment relates to an information interaction method that can be used in a second terminal. The above method includes:

[0206] Step S5201: Receive a second supplementary service transmission message sent by a first terminal, where the second supplementary service transmission message includes second information.

[0207] Step S5202: Send third information to the first terminal, where the third information includes: a second message associated with the second terminal and first identification information.

[0208] The information interaction method involved in the embodiments of the present disclosure may include at least one of steps S5201 and S5202. For example, step S5201 can be implemented as an independent embodiment, step S5202 can be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S5201 and S5202 can be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0209] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0210] FIG6 is an interaction diagram illustrating an information interaction method according to another embodiment of the present disclosure.

[0211] As shown in FIG6 , the method can be used in a communication system, and includes:

[0212] In step S6101, a first network element sends first information to a first terminal, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to exchange service information of the associated second terminal, and the routing identifier is used to identify a service request.

[0213] Step S6102: The first terminal determines first identification information according to the routing identifier.

[0214] Step S6103: The first terminal sends second information to the second terminal based on the first information, where the second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other.

[0215] Step S6104: The second terminal receives the second information sent by the first terminal.

[0216] The information interaction method involved in the embodiments of the present disclosure may include at least one of steps S6101 to S6104. For example, step S6101 can be implemented as an independent embodiment, step S6102 can be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S6101+S6102 can be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0217] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0218] The following is an exemplary introduction to the above method.

[0219] Optional embodiment:

[0220] As shown in Figure 7A, Figure 7A is a schematic diagram of SLPP message exchange according to an embodiment of the present disclosure. Figure 7A may include UE1, UE2, ..., UEn (n is a positive integer), AMF network element, LMF network element, and Next Generation Radio Access Network (NG-RAN).

[0221] In this embodiment, for example, UE1 acts as the target terminal, and the network triggers or the application layer of UE1 triggers the ranging or sidelink SL positioning service request, and requests the absolute position of UE1 with the help of the neighboring positioning terminal. UE2 to UEn are located near UE1 that supports ranging or sidelink SL positioning services, and can serve as neighboring positioning terminals. The SLPP messages related to UE2~UEn include SLPP messages sent by the LMF network element to UE2~UEn and SLPP messages sent by UE2~UEn to the LMF network element.

[0222] 1. Trigger the SL-MO-LR or SL-MT-LR process.

[0223] In some embodiments, the ranging or sidelink (SL) positioning service request is triggered by the network or the application layer of UE1, and the absolute position of UE1 is requested with the assistance of a nearby positioning terminal.

[0224] 2. Positioning request.

[0225] In some embodiments, a location request is sent to a LMF network element, and the corresponding service operation includes an LCS-related identifier to identify the positioning service.

[0226] 3-4 Capability transfer process.

[0227] 3. Supplementary RSPP transport (routing identifier, SLPPs for UEx)

[0228] In some embodiments, the LMF network element may use a supplementary service message with an embedded SLPP container or SLPP message to send a request for the capabilities required by UE1 to UEn to UE1, wherein the request includes a routing identifier, and may also include an embedded SLPP message for requesting UE1 capabilities with only a corresponding SLPP message, and may include an SLPP message for requesting UE2~UEn capabilities, which includes an embedded SLPP message for the relevant UE and the relevant UE ID.

[0229] 3a. Supplementary RSPP transmission (association identifier, SLPP used to request capabilities from UEn).

[0230] 3b. Supplementary RSPP transmission (association identifier, used to request SLPP capabilities from UE2).

[0231] In some embodiments, according to the message received in step 3, if it carries an SLPP message, UE1 parses the SLPP message and its corresponding UE ID (if available). If the SLPP message is sent to UE1, it is processed in UE1. If the SLPP message is sent to other UEs, UE1 sends the SLPP message received from the LMF to UE2~UEn according to the corresponding UE ID received in step 3 (for example, the supplementary service message carries the UE application layer ID corresponding to the SLPP message). The supplementary service message can be a general supplementary service message used to transmit SLPP messages between terminals.

[0232] In some embodiments, the message between UE1 and UE2~UEn includes an association identifier to identify the positioning service provided by the message. The association identifier can be allocated by UE1 and has a one-to-one mapping relationship with the routing identifier received in step 3 and / or the session ID allocated for the SLPP session. The SLPP session also has a one-to-one mapping relationship with the routing identifier received in step 3, or the association identifier can have the same value as the routing identifier received in step 3 and / or the session ID allocated for the SLPP session.

[0233] 4a. Supplementary RSPP transmission (association identifier, SLPP with UEn capabilities)

[0234] 4b. Supplementary RSPP transmission (association identifier, SLPP of UE2 provided capabilities)

[0235] In some embodiments, UEn~UE2 sends a SLPP message providing capabilities to the LMF network element through UE1, wherein UEn~UE2 sends a corresponding SLPP message providing capabilities for each UE, for example, it can be sent in the form of a supplementary service message, and the supplementary service message can be a general message used to transmit SLPP messages between terminals.

[0236] In some embodiments, the message between UE1 and UE2~UEn includes an association identifier to identify the positioning service served by the message. The association identifier can be an identifier received from UE1, or it can be mapped from the session ID of the SLPP session included in the SLPP message of the same positioning service request previously received.

[0237] 4. Supplement RSPP capability response (routing identifier, SLPP of UEx).

[0238] In some embodiments, UE1 determines which positioning service the message serves based on the SLPP message received from UE2 to UEn, and determines the routing identifier mapped to the message. UE1 encodes the SLPP messages and information (such as SLPP messages and other information) received from UE2 to n, and sends them to the LMF network element together with the same routing identifier. The embedded SLPP message of "providing capabilities for UE1" only contains the corresponding SLPP message, and the SLPP message of "providing capabilities for UE2" contains the SLPP message of the relevant UE and the ID of the corresponding relevant UE.

[0239] 5-6 Auxiliary data transmission process.

[0240] 5a. Supplementary RSPP transmission (association identifier, SLPP for which UEn requests assistance data).

[0241] 5b. Supplementary RSPP transmission (association identifier, SLPP for which UE2 requests assistance data).

[0242] In some embodiments, UEn~UE2 sends an SLPP message requesting auxiliary data to the LMF network element through UE1, wherein UEn~UE2 sends a corresponding SLPP message requesting auxiliary data for each UE. For example, a supplementary service message can be used. The supplementary service message can be a general message used to transmit SLPP messages between terminals.

[0243] In some embodiments, a correlation identifier is included in the message between UE1 and UE2~UEn to identify the positioning service served by the message. The correlation identifier can be an identifier of the same positioning service request received from UE1 through previous interaction with UE1, or an identifier mapped from the session ID of the SLPP session to the same positioning request through previous interaction with UE1.

[0244] 5. Supplement RSPP request assistance data (routing identifier, SLPP for UEx)

[0245] In some embodiments, based on the SLPP messages received from UE2 to n, UE1 determines the positioning services served by these messages and the mapped routing identifiers, and then UE1 encodes the SLPP messages and information (e.g., SLPP messages and other information) received from UE2 to UEn and sends them to the LMF network element together with the same routing identifier. The embedded SLPP message for UE1 requesting auxiliary data only contains the corresponding SLPP message, and the embedded SLPP message for UE2 to n requesting auxiliary data contains the SLPP message of the relevant UE and the relevant UE ID.

[0246] 6. Supplement RSPP to provide auxiliary data (routing identifier, SLPP for UEx)

[0247] In some embodiments, the LMF network element uses an embedded SLPP container or SLPP message to send a message to UE1 through a supplementary service message to provide auxiliary data for UE1 to n, and the routing identifier is included. When the embedded SLPP message is used to provide auxiliary data for UE1, it only includes the corresponding SLPP message, and may also include an SLPP message that provides auxiliary data for UE2 to n, which includes the embedded SLPP message of the relevant UE and the associated UE ID.

[0248] 6a. Supplementary RSPP transmission (association identifier, SLPP providing assistance data for UEn).

[0249] 6b. Supplementary RSPP transmission (association identifier, SLPP providing assistance data for UE2).

[0250] In some embodiments, according to the message received in step 6, if it carries an SLPP message, UE1 parses the SLPP message and its corresponding UE ID. If the SLPP message is sent to UE1, it is processed in UE1. If the SLPP message is sent to other UEs, UE1 sends the SLPP message received from the LMF network element to UE2 to UEn according to the corresponding UE ID received in step 6 (for example, using a supplementary service message to carry the UE application layer ID corresponding to the SLPP message), where the supplementary service message can be a general message used to transmit SLPP messages between terminals.

[0251] In some embodiments, a correlation identifier is included in the message between UE1 and UE2 to n to identify the positioning service provided by the message. The correlation identifier has a one-to-one mapping with the routing identifier received in step 6 and / or the session ID assigned to the SLPP session, and the SLPP session also has a one-to-one mapping with the routing identifier received in step 6. Alternatively, the correlation identifier can have the same value as the routing identifier received in step 6 and / or the session ID assigned to the SLPP session for the same location request.

[0252] 7-8 Positioning information transmission process.

[0253] 7. Supplement RSPP request location information (routing identifier, for SLPPs of UEx).

[0254] In some embodiments, the LMF network element may send a request to UE1 using a supplementary service message with an embedded SLPP container to obtain the location information required by UE1 to UEn. The message may include a routing identifier, may include an embedded SLPP message for requesting UE1's location information that only includes the corresponding SLPP message, and may include an SLPP message for requesting UE2's location information that includes the embedded SLPP message for the relevant UE and the relevant UE ID.

[0255] 7a. Supplementary RSPP transmission (association identifier, SLPP requesting positioning information from UEn).

[0256] 7b. Supplement RSPP transmission (association identifier, SLPP requesting positioning information from UE2).

[0257] In some embodiments, according to the message received in step 7, if it carries an SLPP message, UE1 parses the SLPP message and its corresponding UE ID. If the SLPP message is sent to UE1, it is processed in UE1. If the SLPP message is sent to other UEs, UE1 sends the SLPP message received from the LMF network element to UE2~UEn according to the corresponding UE ID received in step 7 (for example, using a supplementary service message to carry the UE application layer ID corresponding to the SLPP message), wherein the supplementary service message can be a general supplementary service message for transmitting SLPP messages between terminals.

[0258] In some embodiments, a correlation identifier is included in the message between UE1 and UE2 to n to identify the positioning service provided by the message, and the correlation identifier has a one-to-one mapping with the routing identifier received in step 3 and / or the session ID assigned to the SLPP session, and the SLPP session also has a one-to-one mapping with the routing identifier received in step 7, or the correlation identifier can have the same value as the routing identifier received in step 7 and / or the session ID assigned to the SLPP session.

[0259] 8a. Supplementary RSPP transmission (association identifier, SLPP where UEn provides positioning information).

[0260] 8b. Supplementary RSPP transmission (association identifier, SLPP for UE2 to provide positioning information).

[0261] In some embodiments, UEn~UE2 sends an SLPP message providing location information to the LMF network element through UE1, and UEn~UE2 sends a corresponding SLPP message providing location information for each UE, for example, using a supplementary service message. The supplementary service message can be a general message used to transmit SLPP messages between terminals.

[0262] In some embodiments, a message between UE1 and UE2-UEn includes a correlation identifier to identify the positioning service provided by the message. The correlation identifier can be an identifier received from UE1, or can be mapped from the session ID of the SLPP session included in a previously received SLPP message for the same positioning request.

[0263] 8. Supplement RSPP to provide positioning information (routing identifier, SLPPs of UEx).

[0264] 8. Based on the SLPP messages received from UEs 2-UEn, UE1 determines which positioning service the message serves and the mapped routing identifier. UE1 encodes the SLPP messages received from UEs 2-UEn and other information related to UE1 (e.g., SLPP messages) into the message sent to the LMF, using the same routing identifier. For embedded SLPP messages providing location information for UE1, only the corresponding SLPP message is included. For SLPP messages providing location information for UEs 2-n, the SLPP messages related to the relevant UE and the SLPP message with the relevant UE ID are included.

[0265] NOTE 1 The steps of capability transmission, auxiliary data transmission and position information transmission may be performed in any order and may be repeated.

[0266] Note 2: During the interaction between the LMF network element and the UE, the SLPP message can be included in other messages in the same manner as listed in this embodiment.

[0267] 9. Positioning information response.

[0268] 9. The LMF network element returns a location response to the AMF network element, which contains any obtained ranging or sidelink SL positioning results.

[0269] As shown in Figure 7B, Figure 7B is a schematic diagram of another SLPP message exchange according to an embodiment of the present disclosure. Figure 7B may include UE1, UE2, ..., UEn (n is a positive integer), AMF network element, LMF network element, and Next Generation Radio Access Network (NG-RAN).

[0270] In this embodiment, for example, UE1 serves as the target terminal, and the network triggers or the application layer of UE1 triggers the ranging or sidelink SL positioning service request, and requests the absolute position of UE1 with the help of the adjacent positioning terminal. UE2~UEn are located near UE1 that supports ranging or sidelink SL positioning services, and the SLPP messages related to UE2~UEn include SLPP messages sent by LMF to UE2~UEn and SLPP messages sent by UE2~UEn to the LMF network element.

[0271] In this embodiment, the main difference from the embodiment of Figure 7A above is that the supplementary service message used between UE1 and the LMF network element is a general SLPP supplementary service message message used to transmit SLPP messages. The SLPP message can be encoded and processed according to the relevant communication protocol, and the routing identifier used between UE1 and the LMF network element is directly used between UE1 and other UEs.

[0272] 1. Trigger the SL-MO-LR or SL-MT-LR process.

[0273] In some embodiments, the ranging or sidelink (SL) positioning service request is triggered by the network or the application layer of UE1, and the absolute position of UE1 is requested with the assistance of a nearby positioning terminal.

[0274] 2. Positioning request.

[0275] In some embodiments, a location request is sent to a LMF network element, and the corresponding service operation includes an LCS association identifier to identify the positioning service.

[0276] 3-4. Capability transfer process.

[0277] 3. Supplement RSPP transport (routing identifier, SLPPs requesting capabilities from UEx)

[0278] In some embodiments, the LMF network element may use a supplementary service message with an embedded SLPP container or SLPP message to send a SLPP message requesting a function to UE1 to obtain the functions required by UE1 to UEn, including a routing identifier, and may include an embedded SLPP message for requesting UE1 capabilities that only contains the corresponding SLPP message, and may include an SLPP message for requesting UE2~UEn capabilities (including an embedded SLPP message for the relevant UE and the relevant UE ID) in any of the ways listed in the above embodiments.

[0279] 3a. Supplementary RSPP transport (routing identifier, SLPP requesting capabilities from UEn).

[0280] 3b. Supplementary RSPP transmission (routing identifier, SLPP requesting capabilities from UE2).

[0281] In some embodiments, according to the message received in step 3, if it carries an SLPP message, UE1 parses the SLPP message and its corresponding UE ID. If the SLPP message is sent to UE1, it is processed in UE1. If the SLPP message is sent to other UEs, UE1 sends the SLPP message received from the LMF network element to UE2 to n according to the corresponding UE ID received in step 3 (for example, using a supplementary service message to carry the UE application layer ID corresponding to the SLPP message). The supplementary service message can be a general supplementary service message for transmitting SLPP messages between terminals or a supplementary service message for transmitting capability information between terminals.

[0282] In some embodiments, the routing identifier received in step 3 is included in a message between UE1 and UE2 to n.

[0283] 4a. Supplementary RSPP transport (routing identifier, SLPP for which UEn provides capabilities).

[0284] 4b. Supplement RSPP transmission (routing identifier, SLPP of which UE2 provides capabilities).

[0285] In some embodiments, UEn~UE2 sends a SLPP message providing capabilities to the LMF network element through UE1, wherein UEn~UE2 sends a corresponding SLPP message providing capabilities to each UE, for example, using a supplementary service message, which can be a general supplementary service message for transmitting SLPP messages between terminals or a supplementary service message of an SLPP message for transmitting capability information between terminals.

[0286] In some embodiments, a routing identifier is included in a message between UE1 and UE2 to n to identify the positioning service served by the message. The routing identifier may be an identifier of the same location request service previously received from UE1.

[0287] 4. Supplement RSPP transport (routing identifier, SLPPs with UEx capabilities)

[0288] In some embodiments, based on the received SLPP messages from UE2 to UEn, UE1 determines which location service the message serves based on the routing identifier, and encodes the SLPP messages and information received from UE2 to UEn (such as UE1's SLPP messages and other information) into the message sent to the LMF, using the same routing identifier. The SLPP message providing UE1 capabilities only includes the corresponding embedded SLPP message, while the SLPP message providing UE2 to UEn capabilities uses a general supplementary service message embedded in the SLPP container, which includes the SLPP message of the relevant UE and the associated UE ID information.

[0289] 5-6 Auxiliary data transmission process.

[0290] 5a. Supplementary RSPP transmission (routing identifier, SLPP for UEn requesting assistance data).

[0291] 5b. Supplementary RSPP transmission (routing identifier, SLPP for UE2 requesting assistance data).

[0292] In some embodiments, UEn~UE2 sends an SLPP message requesting auxiliary data to the LMF network element through UE1, wherein UEn~UE2 sends a corresponding SLPP message requesting auxiliary data for each UE, for example, using a supplementary service message, which can be a general supplementary service message for transmitting SLPP messages between terminals or a supplementary service message for the SLPP message for transmitting auxiliary data between terminals.

[0293] In some embodiments, the routing identifier is included in the message between UE1 and UE2-UEn to identify the positioning service served by the message, and the association identifier may be an identifier of the same positioning service request received from UE1 through previous interaction with UE1.

[0294] 5. Supplementary RSPP transmission (routing identifier, SLPPs for UEx request assistance data).

[0295] In some embodiments, UE1 determines which positioning service the SLPP message received from UE2 to UEn serves based on the routing identifier, and encodes the SLPP message and information received from UE2 to UEn (such as UE1's SLPP message and other information) into the message sent to the LMF network element, using the same routing identifier. The embedded SLPP message requesting auxiliary data of UE1 only contains the corresponding SLPP message, and the SLPP message requesting auxiliary data of UE2 to UEn includes the SLPP message of the relevant UE and the relevant UE ID, and uses a general supplementary service message embedded in the SLPP container or SLPP message.

[0296] 6. Supplementary RSPP transmission (routing identifier, SLPPs providing assistance data to UEx).

[0297] In some embodiments, the LMF network element sends a message to UE1, providing auxiliary data for UE1 to UEn through a supplementary service message embedded in an SLPP container, which may include a routing identifier, may include an embedded SLPP message containing only the corresponding SLPP message for providing auxiliary data for UE1, may include an embedded SLPP message for the relevant UE and an SLPP message for providing auxiliary data to UE2 with the relevant UE ID, and use a general supplementary service message for transmitting SLPP messages using an embedded SLPP container.

[0298] 6a. Supplementary RSPP transmission (routing identifier, SLPP providing assistance data to UEn).

[0299] 6b. Supplementary RSPP transmission (routing identifier, SLPP providing assistance data to UE2).

[0300] In some embodiments, according to the message received in step 6, if it carries an SLPP message, UE1 parses the SLPP message and its corresponding UE ID. If the SLPP message is sent to UE1, it is processed in UE1. If the SLPP message is sent to other UEs, UE1 sends the SLPP message received from the LMF network element to UE2~UEn according to the corresponding UE ID received in step 6 (for example, using a supplementary service message to carry the UE application layer ID corresponding to the SLPP message). The supplementary service message can be a general supplementary service message for transmitting SLPP messages between terminals or a supplementary service message of an SLPP message for transmitting auxiliary data between terminals.

[0301] In some embodiments, a routing identifier is included in the message between UE1 and UE2 to n to identify the positioning service served by the message, and the routing identifier is received in step 6.

[0302] 7-8 Position information transmission process.

[0303] 7. Supplement RSPP transmission (routing identifier, SLPPs requesting positioning information from UEx).

[0304] In some embodiments, the LMF network element sends an SLPP message requesting location information of UE1 to UEn through a supplementary service message embedded in an SLPP container or SLPP message, including a routing identifier, and may include an embedded SLPP message for requesting UE1 location information that only contains the corresponding SLPP message, and may include an SLPP message for requesting location information of UE2 to UEn, including an embedded SLPP message for the relevant UE and an embedded SLPP message for the relevant UE ID, using any of the methods listed in the above embodiments, using a general supplementary service message for transmitting SLPP messages using an embedded SLPP container.

[0305] 7a. Supplementary RSPP transmission (routing identifier, SLPP requesting positioning information from UEn).

[0306] 7b. Supplement RSPP transmission (routing identifier, SLPP requesting positioning information from UE2).

[0307] In some embodiments, according to the message received in step 7, if it carries an SLPP message, UE1 parses the SLPP message and its corresponding UE ID. If the SLPP message is sent to UE1, it is processed in UE1. If the SLPP message is sent to other UEs, UE1 sends the SLPP message received from the LMF network element to UE2 to UEn based on the corresponding UE ID received in step 7 (for example, using a supplementary service message to carry the UE application layer ID corresponding to the SLPP message). The supplementary service message can be a general supplementary service message for transmitting SLPP messages between terminals or a supplementary service message for transmitting location information between terminals.

[0308] In some embodiments, a routing identifier is included to identify the positioning service served by the message, and the routing identifier is received in step 7.

[0309] 8a. Supplementary RSPP transmission (routing identifier, SLPP where UEn provides positioning information).

[0310] 8b. Supplement RSPP transmission (routing identifier, SLPP for UE2 to provide positioning information).

[0311] In some embodiments, UEn~UE2 sends an SLPP message providing location information to the LMF network element through UE1, and UEn~UE2 sends a corresponding SLPP message providing location information for each UE, for example, using a supplementary service message. The supplementary service message can be a general supplementary message for transmitting SLPP messages between terminals or a supplementary service message for the SLPP message for transmitting location information between terminals.

[0312] In some embodiments, a routing identifier is included to identify the positioning service served by the message. The routing identifier may be an identifier of the same location request previously received from UE1.

[0313] 8. Supplement RSPP transmission (routing identifier, SLPPs where UEx provides positioning information).

[0314] In some embodiments, UE1 determines which positioning service the SLPP message received from UE2 to UEn serves based on the routing identifier, and encodes the SLPP messages and information received from UE2 to UEn (e.g., UE1's SLPP message and other information) into the message sent to the LMF network element using the same routing identifier. The embedded SLPP message for "providing location information for UE1" only includes the corresponding SLPP message, and the SLPP message for "providing location information for UE2" includes the SLPP message for the relevant UE and the relevant UE ID in any of the ways listed in the above embodiments, using an embedded SLPP container or a SLPP message for SLPP message transmission.

[0315] Note 1: The steps of the capability transmission process, auxiliary data transmission process and location information transmission process can be performed in any order or simultaneously.

[0316] Note 2: During the interaction between the LMF network element and the UE, the SLPP message can be included in other messages in the same manner as listed in this embodiment.

[0317] 9. Position response.

[0318] In some embodiments, the LMF network element returns a location response to the AMF network element, which includes any obtained ranging or sidelink SL positioning results.

[0319] FIG8A is a schematic diagram of the structure of the first network element proposed in an embodiment of the present disclosure. As shown in FIG8A , the first network element 8100 may include at least one of a transceiver module 8101 and a processing module 8102. The first network element 8100 may include:

[0320] The transceiver module 8101 is used to send first information to the first terminal, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to exchange business information of the associated second terminal, and the routing identifier is used to identify the business request.

[0321] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0322] receiving third information sent by the second terminal, wherein the third information includes: a second message associated with the second terminal and first identification information;

[0323] According to the third information, fourth information is sent to the first network element, where the fourth information includes: a second message associated with the second terminal and a routing identifier.

[0324] In some embodiments of the present disclosure, the first identification information includes at least one of the following:

[0325] association identifier;

[0326] Route identifier.

[0327] In some embodiments of the present disclosure, the business information includes at least one of the following:

[0328] Terminal capabilities;

[0329] business results;

[0330] Business measurement data;

[0331] Business auxiliary data.

[0332] In some embodiments of the present disclosure, the first information further includes at least one of the following:

[0333] at least one second terminal information, wherein the second terminal information is used to describe the second terminal and indicate service information of the first terminal interacting with the corresponding second terminal;

[0334] A second terminal information list, wherein the second terminal information list includes: at least one second terminal information;

[0335] A first message, wherein the first message is used to exchange service information of the first terminal;

[0336] Indication information, wherein the indication information is used to instruct the first terminal to forward the second message.

[0337] In some embodiments of the present disclosure, the third information further includes at least one of the following:

[0338] Second terminal information, where the second terminal information is used to describe the second terminal that sends the third information and service information indicating that the first terminal interacts with the second terminal;

[0339] Indication information, wherein the indication information is used to instruct the first terminal to forward the second message.

[0340] In some embodiments of the present disclosure, the first identification information and the routing identifier have a mapping relationship; and / or

[0341] The first identification information and the SLPP session information have a mapping relationship, wherein the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for the business service; and / or

[0342] There is a mapping relationship between the routing identifier and the SLPP session information.

[0343] In some embodiments of the present disclosure,

[0344] The association identifier and the routing identifier have the same value; and / or

[0345] The association identifier and the SLPP session information have the same value, wherein the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for the business service.

[0346] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0347] The first identification information is determined according to the routing identifier.

[0348] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0349] There is second identification information, and the second identification information is associated with the routing identifier to obtain the first identification information, wherein the second identification information is available identification information allocated for interaction between the first terminal and the second terminal based on the service request;

[0350] If the second identification information does not exist, new identification information is allocated to the service request, and the routing identifier is associated with the new identification information to obtain the first identification information.

[0351] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0352] Acquire service information of the first terminal according to the first message in the first information, wherein the first message is used to exchange service information of the first terminal, and the service information includes: terminal capabilities and / or service results and / or service measurement data;

[0353] The terminal capability and / or service result and / or service measurement data of the first terminal are sent to the first network element.

[0354] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0355] A first supplementary service request message sent by a first network element is received, wherein the first supplementary service request message includes first information, and the second message is used to request terminal capabilities and / or service results and / or service measurement data of an associated second terminal.

[0356] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0357] A first supplementary service transmission message sent by a first network element is received, wherein the first supplementary service transmission message includes first information, and the second message is used to request terminal capabilities and / or service results and / or service measurement data of an associated second terminal.

[0358] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0359] A second supplementary service transmission message is sent to the second terminal according to the first information, wherein the second supplementary service transmission message includes the second information.

[0360] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0361] A third supplementary service transmission message sent by the second terminal is received, where the third supplementary service transmission message includes: terminal capability and / or service result and / or service measurement data of the second terminal, and first identification information.

[0362] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0363] A routing identifier is determined according to the first identification information sent by the second terminal.

[0364] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0365] A first supplementary service response message is sent to the first network element, wherein the first supplementary service response message includes: terminal capability and / or service result and / or service measurement data of the second terminal, and a routing identifier.

[0366] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0367] A fourth supplementary service transmission message is sent to the first network element, where the fourth supplementary service transmission message includes: terminal capability and / or service result and / or service measurement data of the second terminal, and a routing identifier.

[0368] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0369] A fifth supplementary service transmission message sent by the second terminal is received, wherein the fifth supplementary service transmission message includes third information, and the second message associated with the second terminal is used to request service assistance data of the associated second terminal.

[0370] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0371] According to the third information, a second supplementary service request message is sent to the first network element, where the second supplementary service request message includes: fourth information.

[0372] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0373] A second supplementary service response message sent by the first network element is received, wherein the second supplementary service response message includes: service auxiliary data of the second terminal and a routing identifier.

[0374] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0375] A sixth supplementary service transmission message is sent to the first network element, where the sixth supplementary service transmission message includes: fourth information.

[0376] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0377] A seventh supplementary service transmission message sent by the first network element is received, where the seventh supplementary service transmission message includes: service auxiliary data of the second terminal and a routing identifier.

[0378] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0379] An eighth supplementary service transmission message is sent to the second terminal, where the eighth supplementary service transmission message includes: service auxiliary data of the second terminal and first identification information.

[0380] In some embodiments of the present disclosure, the service is ranging or sidelink (SL) positioning service.

[0381] FIG8B is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG8B , the terminal 8200 may include at least one of a transceiver module 8201 and a processing module 8202. The terminal 8200 may include:

[0382] The transceiver module 8201 is configured to receive first information sent by a first network element, where the first information includes: at least one second message and a routing identifier, the second message being associated with a second terminal, the second message being used to exchange service information of the associated second terminal, the routing identifier being used to identify a service request, and sending second information to the second terminal based on the first information, where the second information includes: a second message associated with the second terminal and first identification information, the first identification information being used to identify the service request, and the routing identifier and the first identification information being associated with each other; or

[0383] The transceiver module 8201 is used to receive the second information sent by the first terminal, wherein the second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, the routing identifier and the first identification information are associated with each other, and the routing identifier is used to identify the service request.

[0384] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0385] Fourth information sent by the first terminal is received, where the fourth information includes: a second message associated with the second terminal and a routing identifier.

[0386] In some embodiments of the present disclosure, the business information includes at least one of the following:

[0387] Terminal capabilities;

[0388] business results;

[0389] Business measurement data;

[0390] Business auxiliary data.

[0391] In some embodiments of the present disclosure, the first information further includes at least one of the following:

[0392] at least one second terminal information, wherein the second terminal information is used to describe the second terminal and indicate service information of the first terminal interacting with the corresponding second terminal;

[0393] A second terminal information list, wherein the second terminal information list includes: at least one second terminal information;

[0394] A first message, wherein the first message is used to exchange service information of the first terminal;

[0395] Indication information, wherein the indication information is used to instruct the first terminal to forward the second message.

[0396] In some embodiments of the present disclosure,

[0397] The routing identifier and the SLPP session information have a mapping relationship, wherein the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for the business service.

[0398] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0399] Receive terminal capabilities and / or service results and / or service measurement data of the first terminal sent by the first terminal.

[0400] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0401] A first supplementary service request message is sent to the first terminal, wherein the first supplementary service request message includes first information, and the second message is used to request terminal capabilities and / or service results and / or service measurement data of the associated second terminal.

[0402] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0403] A first supplementary service transmission message is sent to the first terminal, wherein the first supplementary service transmission message includes first information, and the second message is used to request terminal capabilities and / or service results and / or service measurement data of the associated second terminal.

[0404] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0405] A first supplementary service response message sent by the first terminal is received, wherein the first supplementary service response message includes: terminal capability and / or service result and / or service measurement data of the second terminal, and a routing identifier.

[0406] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0407] A fourth supplementary service transmission message sent by the first terminal is received, where the fourth supplementary service transmission message includes: terminal capability and / or service result and / or service measurement data of the second terminal, and a routing identifier.

[0408] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0409] A second supplementary service request message sent by the first terminal is received, where the second supplementary service request message includes: fourth information.

[0410] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0411] A second supplementary service response message is sent to the first terminal, wherein the second supplementary service response message includes: service assistance data of the second terminal and a routing identifier.

[0412] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0413] A sixth supplementary service transmission message sent by the first terminal is received, where the sixth supplementary service transmission message includes: fourth information.

[0414] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0415] A seventh supplementary service transmission message is sent to the first terminal, where the seventh supplementary service transmission message includes: service auxiliary data of the second terminal and a routing identifier.

[0416] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0417] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules each execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0418] Figure 9A is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure. Communication device 9100 can be a terminal, a network device, a chip, a chip system, or a processor that supports a terminal implementing any of the above methods, or a chip, a chip system, or a processor that supports a network device implementing any of the above methods. Communication device 9100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0419] As shown in Figure 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 9100 is used to perform any of the above methods.

[0420] In some embodiments, the communication device 9100 further includes one or more memories 9102 for storing instructions. Optionally, all or part of the memories 9102 may be located outside the communication device 9100.

[0421] In some embodiments, the communication device 9100 further includes one or more transceivers 9103. When the communication device 9100 includes one or more transceivers 9103, the transceiver 9103 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 9101 performs the other steps.

[0422] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0423] In some embodiments, the communication device 9100 may include one or more interface circuits 9104. Optionally, the interface circuit 9104 is connected to the memory 9102. The interface circuit 9104 may be configured to receive signals from the memory 9102 or other devices, and may be configured to send signals to the memory 9102 or other devices. For example, the interface circuit 9104 may read instructions stored in the memory 9102 and send the instructions to the processor 9101.

[0424] The communication device 9100 described in the above embodiments may be a terminal, a network device, or a third entity, but the scope of the communication device 9100 described in the present disclosure is not limited thereto, and the structure of the communication device 9100 may not be limited by FIG. 9A . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0425] FIG9B is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. If the communication device 9100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 9200 shown in FIG9B , but the present disclosure is not limited thereto.

[0426] The chip 9200 includes one or more processors 9201 , and the chip 9200 is configured to execute any of the above methods.

[0427] In some embodiments, the chip 9200 further includes one or more interface circuits 9202. Optionally, the interface circuit 9202 is connected to the memory 9203. The interface circuit 9202 can be used to receive signals from the memory 9203 or other devices, and can be used to send signals to the memory 9203 or other devices. For example, the interface circuit 9202 can read instructions stored in the memory 9203 and send the instructions to the processor 9201.

[0428] In some embodiments, the interface circuit 9202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 9201 performs the other steps.

[0429] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0430] In some embodiments, the chip 9200 further includes one or more memories 9203 for storing instructions. Alternatively, all or part of the memories 9203 may be located outside the chip 9200.

[0431] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 9100, causes the communication device 9100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0432] The present disclosure also provides a program product, which, when executed by the communication device 9100, enables the communication device 9100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0433] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0434] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0435] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0436] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0437] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. An information interaction method, characterized in that, Executed by a first terminal, the method includes: Receiving first information sent by a first network element, where the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with service information of the associated second terminal, and the routing identifier is used to identify a service request; According to the first information, sending second information to the second terminal, where the second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other.

2. The method according to claim 1, characterized in that, The method further includes: Receiving third information sent by the second terminal, where the third information includes: a second message associated with the second terminal and the first identification information; According to the third information, sending fourth information to the first network element, where the fourth information includes: the second message associated with the second terminal and the routing identifier.

3. The method according to any one of claims 1-2, characterized in that, The first identification information includes at least one of the following: An association identifier; The routing identifier.

4. The method according to any one of claims 1 to 3, characterized in that, The service information includes at least one of the following: Terminal capabilities; Service results; Service measurement data; Service auxiliary data.

5. The method according to any one of claims 1 to 4, characterized in that, The first information further includes at least one of the following: At least one second terminal information, where the second terminal information is used to describe the second terminal and indicate that the first terminal interacts with service information of the corresponding second terminal; A second terminal information list, where the second terminal information list includes: the at least one second terminal information; A first message, where the first message is used to interact with service information of the first terminal; Indication information, where the indication information is used to indicate that the first terminal forwards the second message.

6. The method according to any one of claims 2-5, characterized in that, The third information further includes at least one of the following: Second terminal information, where the second terminal information is used to describe the second terminal sending the third information and indicate that the first terminal interacts with service information of the second terminal; Indication information, where the indication information is used to indicate that the first terminal forwards the second message.

7. The method according to any one of claims 1-6, characterized in that, Where The first identification information and the routing identifier have a mapping relationship; and / or The first identification information and SLPP session information have a mapping relationship, where the SLPP session information is used to describe an SLPP session allocated by the first terminal or the second terminal for service; and / or The routing identifier and the SLPP session information have a mapping relationship.

8. The method according to any one of claims 2-7, characterized in that, Where The values of the association identifier and the routing identifier are the same; and / or The values of the association identifier and SLPP session information are the same, where the SLPP session information is used to describe an SLPP session allocated by the first terminal or the second terminal for service.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: Determining the first identification information according to the routing identifier.

10. The method according to claim 9, characterized in that, The determining the first identification information according to the routing identifier includes any one of the following: There is second identification information. The second identification information and the routing identifier are associated to obtain the first identification information, where the second identification information is available identification information that has been allocated for the interaction between the first terminal and the second terminal based on the service request; There is no second identification information. New identification information is allocated for the service request, and the routing identifier and the new identification information are associated to obtain the first identification information.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: According to the first message in the first information, obtain the service information of the first terminal, where the first message is used to interact the service information of the first terminal, and the service information includes: terminal capabilities and / or service results and / or service measurement data; Send the terminal capabilities and / or service results and / or service measurement data of the first terminal to the first network element.

12. The method according to any one of claims 2-11, characterized in that, The receiving the first information sent by the first network element includes: Receiving a first supplementary service request message sent by the first network element, where the first supplementary service request message includes the first information, and the second message is used to request the terminal capabilities and / or service results and / or service measurement data of the associated second terminal.

13. The method according to any one of claims 2-11, characterized in that, The receiving the first information sent by the first network element includes: Receiving a first supplementary service transmission message sent by the first network element, where the first supplementary service transmission message includes the first information, and the second message is used to request the terminal capabilities and / or service results and / or service measurement data of the associated second terminal.

14. The method according to any one of claims 12-13, characterized in that, The sending the second information to the second terminal according to the first information includes: According to the first information, send a second supplementary service transmission message to the second terminal, where the second supplementary service transmission message includes the second information.

15. The method according to any one of claims 12 - 14, characterized in that, The method further includes: Receiving a third supplementary service transmission message sent by the second terminal, where the third supplementary service transmission message includes: the terminal capabilities and / or service results and / or service measurement data of the second terminal, and the first identification information.

16. The method according to claim 15, wherein The method further includes: Determine the routing identifier according to the first identification information sent by the second terminal.

17. The method according to any one of claims 12, 14 - 16, characterized in that The method further includes: Send a first supplementary service response message to the first network element, where the first supplementary service response message includes: the terminal capabilities and / or service results and / or service measurement data of the second terminal, and the routing identifier.

18. The method according to any one of claims 13, 14 - 16, characterized in that, The method further includes: Send a fourth supplementary service transmission message to the first network element, where the fourth supplementary service transmission message includes: the terminal capabilities and / or service results and / or service measurement data of the second terminal, and the routing identifier.

19. The method according to any one of claims 2-10, characterized in that, The receiving the third information sent by the second terminal includes: Receiving a fifth supplementary service transmission message sent by the second terminal, where the fifth supplementary service transmission message includes the third information, and the second message associated with the second terminal is used to request the service auxiliary data of the associated second terminal.

20. The method according to claim 19, wherein The sending the fourth information to the first network element according to the third information includes: Send a second supplementary service request message to the first network element according to the third information, where the second supplementary service request message includes: the fourth information.

21. The method according to any one of claims 19-20, characterized in that, The method further includes: Receive a second supplementary service response message sent by the first network element, where the second supplementary service response message includes: the second Service assistance data of the terminal, and the routing identifier.

22. The method according to claim 19, wherein The sending the fourth information to the first network element according to the third information includes: Send a sixth supplementary service transmission message to the first network element, where the sixth supplementary service transmission message includes: the fourth information.

23. The method according to claim 19 or 22, characterized in that, The method further includes: Receive a seventh supplementary service transmission message sent by the first network element, where the seventh supplementary service transmission message includes: service assistance data of the second terminal, and the routing identifier.

24. The method according to any one of claims 19-23, characterized in that, The method further includes: Send an eighth supplementary service transmission message to the second terminal, where the eighth supplementary service transmission message includes: service assistance data of the second terminal, and the first identification information.

25. The method according to any one of claims 1 to 24, characterized in that, The service is ranging or sidelink SL positioning service.

26. An information interaction method, characterized in that, Executed by the first network element, the method includes: Send first information to the first terminal, where the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with the service information of the associated second terminal, and the routing identifier is used to identify a service request.

27. The method according to claim 26, characterized in that, The method further includes: Receive the fourth information sent by the first terminal, where the fourth information includes: the second message associated with the second terminal and the routing identifier.

28. The method according to any one of claims 26-27, characterized in that, The service information includes at least one of the following: Terminal capabilities; Service results; Service measurement data; Service assistance data.

29. The method according to any one of claims 26-28, characterized in that, The first information further includes at least one of the following: At least one second terminal information, where the second terminal information is used to describe the second terminal, and to indicate that the first terminal interacts with the service information of the corresponding second terminal; A list of second terminal information, where the list of second terminal information includes: the at least one second terminal information; A first message, where the first message is used to interact with the service information of the first terminal; An indication information, where the indication information is used to indicate that the first terminal forwards the second message.

30. The method according to any one of claims 26 - 29, characterized in that, Where The routing identifier and the SLPP session information have a mapping relationship, where the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for service.

31. The method according to any one of claims 26 - 30, characterized in that, The method further includes: Receive the terminal capabilities and / or service results and / or service measurement data of the first terminal sent by the first terminal.

32. The method according to any one of claims 27 - 31, characterized in that, The sending the first information to the first terminal includes: Send a first supplementary service request message to the first terminal, where the first supplementary service request message includes the first information, and the second message is used to request the terminal capabilities and / or service results and / or service measurement data of the associated second terminal.

33. The method according to any one of claims 27-31, characterized in that, The sending the first information to the first terminal includes: Send a first supplementary service transmission message to the first terminal, where the first supplementary service transmission message includes the first information, and the second message is used to request the terminal capabilities and / or service results and / or service measurement data of the associated second terminal.

34. The method according to claim 32, wherein The method further includes: Receive a first supplementary service response message sent by the first terminal, where the first supplementary service response message includes: the terminal capabilities and / or service results and / or service measurement data of the second terminal, and the routing identifier.

35. The method according to claim 33, characterized in that, The method further includes: Receive a fourth supplementary service transmission message sent by the first terminal, where the fourth supplementary service transmission message includes: the terminal capabilities and / or service results and / or service measurement data of the second terminal, and the routing identifier.

36. The method according to any one of claims 27 - 31, characterized in that, The receiving the fourth information sent by the first terminal includes: Receive a second supplementary service request message sent by the first terminal, where the second supplementary service request message includes: the fourth information.

37. The method according to claim 36, wherein The method further includes: Send a second supplementary service response message to the first terminal, where the second supplementary service response message includes: the service assistance data of the second terminal, and the routing identifier.

38. The method according to any one of claims 27-31, characterized in that, The receiving the fourth information sent by the first terminal includes: Receive a sixth supplementary service transmission message sent by the first terminal, where the sixth supplementary service transmission message includes: the fourth information.

39. The method according to claim 38, wherein The method further includes: Send a seventh supplementary service transmission message to the first terminal, where the seventh supplementary service transmission message includes: the service assistance data of the second terminal, and the routing identifier.

40. An information interaction method, characterized in that, Executed by a second terminal, the method includes: Receive a second information sent by a first terminal, where the second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify a service request, the routing identifier and the first identification information are associated with each other, and the routing identifier is used to identify the service request.

41. The method according to claim 40, wherein The method further includes: Send a third information to the first terminal, where the third information includes: a second message associated with the second terminal and the first identification information.

42. The method according to any one of claims 40 - 41, characterized in that, The first identification information includes at least one of the following: Association identifier; The routing identifier.

43. The method according to any one of claims 40-42, characterized in that, The service information includes at least one of the following: Terminal capabilities; Service results; Service measurement data; Service assistance data.

44. The method according to any one of claims 41 to 43, characterized in that, The third information further includes at least one of the following: Second terminal information, where the second terminal information is used to describe the second terminal that sends the third information, and to instruct the first terminal to interact with the service information of the second terminal; Indication information, where the indication information is used to instruct the first terminal to forward the second message.

45. The method according to any one of claims 40 to 44, characterized in that, Where The first identification information and the routing identifier have a mapping relationship; and / or The first identification information and the SLPP session information have a mapping relationship, where the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for service; and / or The routing identifier and the SLPP session information have a mapping relationship.

46. The method according to any one of claims 41-45, characterized in that, Wherein, the values of the association identifier and the routing identifier are the same; and / or the values of the association identifier and the SLPP session information are the same, wherein the SLPP session information is used to describe the SLPP session allocated by the first terminal or the second terminal for the service.

47. The method according to any one of claims 41-46, characterized in that, Receiving the second information sent by the first terminal includes: Receiving a second supplementary service transmission message sent by the first terminal, wherein the second supplementary service transmission message includes the second information.

48. The method according to claim 47, wherein The method further includes: Sending a third supplementary service transmission message to the first terminal, wherein the third supplementary service transmission message includes: the terminal capabilities and / or service results and / or service measurement data of the second terminal, and the first identification information.

49. The method according to any one of claims 41 to 46, characterized in that, Sending the third information to the first terminal includes: Sending a fifth supplementary service transmission message to the first terminal, wherein the fifth supplementary service transmission message includes the third information, and the second message associated with the second terminal is used to request service assistance data of the associated second terminal.

50. The method according to claim 49, wherein, The method further includes: Receiving an eighth supplementary service transmission message sent by the first terminal, wherein the eighth supplementary service transmission message includes: the service assistance data of the second terminal, and the first identification information.

51. An information interaction method, characterized in that The method includes: A first network element sends first information to a first terminal, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with the service information of the associated second terminal, and the routing identifier is used to identify a service request; The first terminal sends second information to the second terminal according to the first information, wherein the second information includes: a second message associated with the second terminal and a first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other; The second terminal receives the second information sent by the first terminal.

52. A first network element, characterized in that, The first network element includes: A transceiver module, configured to send first information to a first terminal, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with the service information of the associated second terminal, and the routing identifier is used to identify a service request.

53. A terminal, characterized in that, The terminal includes: A transceiver module, configured to receive the first information sent by the first network element, wherein the first information includes: at least one second message and a routing identifier, the second message is associated with a second terminal, the second message is used to interact with the service information of the associated second terminal, and the routing identifier is used to identify a service request, and send second information to the second terminal according to the first information, wherein the second information includes: a second message associated with the second terminal and a first identification information, the first identification information is used to identify the service request, and the routing identifier and the first identification information are associated with each other; or, The transceiver module is configured to receive second information sent by a first terminal, where the second information includes: a second message associated with the second terminal and first identification information, the first identification information is used to identify a service request, a routing identifier is associated with the first identification information, and the routing identifier is used to identify the service request.

54. A communication device, characterized in that, Comprising: One or more processors; Wherein, the processor is configured to execute the information interaction method according to any one of claims 1-51.

55. A storage medium storing instructions, characterized in that, When the instruction runs on a communication device, the communication device is caused to execute the information interaction method according to any one of claims 1-51.

56. A communication system, characterized in that, Comprising a first terminal, a first network element, and a second terminal, where the first terminal is configured to execute the information interaction method according to any one of claims 1-25, the first network element is configured to execute the information interaction method according to any one of claims 26-39, and the second terminal is configured to execute the information interaction method according to any one of claims 40-50.

Images