Information processing methods, apparatus, communication devices, and storage media

Abstract

Embodiments of this disclosure provide information processing methods, apparatus, communication devices, and storage media. [Solution] The information processing method performed by the sender includes the step of sending a Sidelink Positioning Protocol (SLPP) message, the SLPP message containing a transaction identifier (ID) of a first transaction, and the transaction ID is used to determine the initiator of the first transaction.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication technology, but is not limited to the field of wireless communication technology. In particular, it relates to an information processing method, apparatus, communication device, and storage medium.

Background Art

[0002] In a communication system, positioning based on sidelink (SL) between user equipments (UEs) includes absolute positioning, relative positioning, and ranging.

[0003] Normally, only two UEs are involved in ranging. That is, ranging is performed between two UEs. However, in absolute positioning and relative positioning, multiple UEs may be involved in positioning to improve the accuracy of absolute positioning and relative positioning.

Summary of the Invention

Problems to be Solved by the Invention

[0004] Embodiments of this disclosure provide an information processing method, apparatus, communication device, and storage medium.

Means for Solving the Problems

[0005] According to a first aspect of embodiments of this disclosure, there is provided an information processing method executed by a transmitting side, including the step of transmitting a sidelink positioning protocol (SLPP) message, wherein the SLPP message includes a transaction identifier (ID) of a first transaction, and the transaction ID is used to determine an initiator of the first transaction.

[0006] According to a second embodiment of the embodiments of the present disclosure, there is a method for information processing performed by a receiver, comprising the step of receiving an SLPP message, wherein the SLPP message includes a transaction ID for a first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0007] According to a third aspect of the embodiments of the present disclosure, an information processing device is provided, which includes a transmission module configured to transmit an SLPP message, wherein the SLPP message includes a transaction ID of a first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0008] According to a fourth aspect of the embodiments of the present disclosure, an information processing device is provided, which includes a receiving module configured to receive an SLPP message, wherein the SLPP message includes a transaction ID of a first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0009] A fifth aspect of the embodiments of the present disclosure provides a communication device comprising a processor, a transceiver, memory, and an executable program stored in the memory and executable by the processor, wherein when the processor executes the executable program, it performs an information processing method provided in the first or second aspect described above.

[0010] A sixth aspect of the embodiments of the present disclosure provides a communication system comprising a transmitter configured to perform an information processing method provided in the first aspect, and a receiver configured to perform an information processing method provided in the second aspect.

[0011] According to a seventh aspect of the embodiments of this disclosure, a computer storage medium is provided which stores an executable program, and which, when the executable program is executed by a processor, implements the information processing method provided in the first or second aspect described above. [Effects of the Invention]

[0012] In the technical proposal provided by the embodiments of this disclosure, an SLPP message is sent, the SLPP message includes a transaction ID of a first transaction, and the transaction ID is used to determine the initiator of the first transaction. In this way, the transaction initiator can be determined using the transaction ID included in the SLPP message, which reduces situations where the transaction initiator cannot be distinguished when multiple participants are participating in the same transaction, or where different participants in the same transaction determine different initiators, thereby improving the accuracy of information interaction in the transaction process. Because the transaction initiator can be distinguished more accurately based on the transaction ID, positioning using an SLPP message containing a transaction ID can improve the accuracy of positioning.

[0013] Please understand that the general descriptions above and the detailed descriptions below are for illustrative purposes only and do not limit the embodiments of this disclosure. [Brief explanation of the drawing]

[0014] The following drawings are incorporated herein and constitute part of this specification, illustrating embodiments consistent with the present invention and are used to illustrate the principles of embodiments of the present invention together with the detailed description. [Figure 1] This is a schematic diagram of a wireless communication system according to one exemplary embodiment. [Figure 2] This is a schematic diagram of a positioning framework according to one exemplary embodiment. [Figure 3] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 4] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 5] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 6] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 7] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 8] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 9] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 10] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 11] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 12] It is a schematic flowchart of an information processing method according to an exemplary embodiment. [Figure 13] It is a schematic configuration diagram of an information processing apparatus according to an exemplary embodiment. [Figure 14] It is a schematic configuration diagram of an information processing apparatus according to an exemplary embodiment. [Figure 15] It is a schematic configuration diagram of a terminal according to an exemplary embodiment.

Embodiments for Carrying Out the Invention

[0015] Hereinafter, exemplary embodiments of the present disclosure will be described in detail. The examples are shown in the drawings. When referring to the drawings in the following description, unless otherwise indicated, the same numerals in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments that coincide with the embodiments of the present invention. Rather, they are the embodiments of the present invention These are merely examples of apparatus and methods consistent with some aspects of the present disclosure.

[0016] The terms used in the embodiments of the present disclosure are for the sole purpose of describing particular embodiments and are not intended to limit the embodiments of the present disclosure. The singular forms "a species", "the", and "said" used in the present disclosure shall include the plural forms as well, unless the context clearly dictates otherwise. Also, the term "and / or" used herein refers to any and all possible combinations of the associated listed items and is to be understood as inclusive.

[0017] In the embodiments of the present disclosure, terms such as first, second, third, etc. may be used to describe various information, but it should be understood that this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may be referred to as the second information. Similarly, the second information may be referred to as the first information. Depending on the context, for example, the word "when" used in this specification may be interpreted as "if" or "when" or "in response to a determination".

[0018] Referring to FIG. 1, FIG. 1 is a schematic configuration diagram of a wireless communication system according to an embodiment of the present disclosure. As shown in FIG. 1, the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system can include a plurality of user equipment 11 and a plurality of access network devices 12.

[0019] User equipment 11 may refer to a device that provides voice and / or data connectivity to a user. User equipment 11 can communicate with one or more core networks via a Radio Access Network (RAN). User equipment 11 may also be an Internet of Things terminal, such as a sensor device, a mobile phone (or called a "cellular" phone), or a computer with Internet of Things capabilities, and may be, for example, a fixed, portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted device. For example, it may be a Station (STA), subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment. Alternatively, user equipment 11 may be a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, or a VR / AR hybrid headset. Alternatively, user equipment 11 may be a device on an unmanned aerial vehicle. Alternatively, user equipment 11 may be an in-vehicle device such as a driving computer with wireless communication capabilities, or wireless user equipment connected to an external driving computer. Alternatively, user equipment 11 may be a roadside device, such as a streetlamp, traffic light, or other roadside device with wireless communication capabilities.

[0020] The access network device 12 may be a device that communicates with user equipment 11 in a wireless communication system, a base station, or an access point, or a network device, or a device that communicates with a wireless terminal via an air interface through one or more sectors in the access network. The network device is used to convert received airframes to and from IP packets and acts as a router between the wireless terminal and the rest of the access network, of which the rest of the access network may include an Internet Protocol (IP) network. The network device can also coordinate the property management of the air interface. The wireless communication system is the fourth-generation mobile communication technology, also known as the Long Term Evolution (LTE) system. The wireless communication system may be a 4G system. Alternatively, the wireless communication system may be a 5G system, also called a new radio (NR) system or a 5G NR system. Alternatively, the wireless communication system may be a next-generation system of the 5G system. Here, the access network in the 5G system is NG-RAN (New Generation-Radio). It may also be called an Access Network (or a new generation wireless access network).

[0021] The access network device 12 may be an evolved access device (eNB) used in a 4G system. Alternatively, the access network device 12 may be an access device (gNB) employing a centralized distributed architecture in a 5G system. When the access network device 12 employs a centralized distributed architecture, it typically includes a central unit (CU) and at least two distributed units (DUs). The central unit is provided with a protocol stack for the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Media Access Control (MAC) layer, while the distributed units are provided with a physical (PHY) layer protocol stack. However, the specific implementation of the access network device 12 is not limited in the embodiments of this disclosure.

[0022] A wireless connection can be established between the access network device 12 and the user equipment 11 via a wireless air interface. In different embodiments, the wireless air interface may be a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard, or it may be a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard. For example, the wireless air interface may be a new air interface, or it may be a wireless air interface based on the 5G next-generation mobile communication network technology standard.

[0023] In some embodiments, an E2E (End to End) or D2D (Device to Device) connection can also be established between user equipment 11. For example, vehicle-to-device communication (vehicle-to-device communication) These include scenarios such as V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), and V2P (vehicle-to-pedestrian) communication in the context of V2X (vehicle-to-everything).

[0024] In some embodiments, the wireless communication system may further include a core network device 13. Multiple access network devices 12 are each connected to the core network device 13.

[0025] In some embodiments, the core network device 13 is an advanced data packet controller. The core network device may be a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, the core network device may be a Serving Gateway (SGW), Public Data Network Gateway (PGW), Policy and Charging Rules Function (PCRF), or Home Subscriber Server (HSS).

[0026] In some embodiments, the core network device 13 may include one or more network elements such as Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), and Network Repository Function (NRF) entities.

[0027] The PCF, SMF, UPF, etc. in the embodiments of this disclosure may be implemented by a single entity device or by multiple entity devices. Furthermore, the PCF, SMF, etc. in the embodiments of this disclosure may be a single logical function module within an entity device or a single logical function module composed of multiple entity devices; however, the embodiments of this disclosure are not limited to these.

[0028] To facilitate understanding for those skilled in the art, the embodiments of this disclosure list several embodiments in order to clearly illustrate the technical solutions of the embodiments of this disclosure. Of course, those skilled in the art will understand that the several embodiments provided in the embodiments of this disclosure may be performed individually, or in combination with methods of other embodiments of the embodiments of this disclosure, or after being performed individually or in combination, they may be performed together with some methods of other related technologies. This is not limited to the embodiments of the present invention.

[0029] In each embodiment of this disclosure, the terminology and / or descriptions between embodiments are consistent and mutually referential unless otherwise stated or logically contradictory. Technical features in different embodiments can be combined based on their inherent logical relationships to form new embodiments. The terms used in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the disclosure.

[0030] Sidelink (SL) positioning between UEs includes absolute positioning, relative positioning, and ranging, and sidelinks are also called straightlinks. Absolute positioning determines the absolute coordinates of UEs, relative positioning determines the coordinates of UEs relative to a single reference point, and ranging determines the distance and / or angle of UEs relative to a single reference point. While ranging typically involves only two UEs, absolute and relative positioning may involve multiple UEs.

[0031] In the embodiments of this disclosure, as shown in Figure 2, the downlink arrival time difference (Downlink Taking positioning based on time difference of arrival (DL-TDOA) as an example, the UE uses multiple Road Side Units (RSUs) and Sidelink Positioning Reference Signals (SSUs). By measuring the ence signal (SL PRS), the specific location of the UE relative to the RSU can be determined.

[0032] In addition to positioning based on DL-TDOA, the proposed positioning method can achieve positioning using one or more of the following information: uplink time difference of arrival (UL-TDOA), multiple round trip time (Multiple RTT), angle-of-arrival (AOA) or angle-of-departure (AOD), and carrier phase positioning.

[0033] If the positioning result has not been converted to absolute position coordinates based on absolute position information such as the RSU's Global Positioning System (GPS), the positioning result will be relative positioning. Otherwise, the positioning result will be absolute positioning.

[0034] The UE being positioned is the target UE, and other UEs supporting the positioning of the target UE are anchor UEs. If only two UEs are involved in the positioning, they become each other's anchor UEs.

[0035] Anchor UEs come in different types, and for example, they can include RSU-type anchor UEs. RSU-type anchor UEs are infrastructure that can work with other RSUs to provide positioning services. For example, a regular UE can also function as an anchor UE, but it is difficult for a regular UE to work with other UEs to provide positioning services. Also, some anchor UEs have location information such as GPS and can support absolute positioning for other UEs, while other anchor UEs may not have location information such as GPS.

[0036] The protocol for exchanging positioning messages between two UEs is called the Sidelink Positioning Protocol (or sidelink positioning protocol). This includes LPP, SLPP, or the Ranging and Sidelink Positioning Protocol (RSPP).

[0037] In the case of LPP (LTE (Long Term Evolution) Positioning Protocol), one LPP session is created for each positioning request, and a single positioning request may be, for example, a Mobile Terminated Location Request (MT-LR), a Mobile Originated Location Request (MO-LR), or a Network Induced Location Request (NI-LR). Only two nodes are involved in one LPP session, for example, only one UE and one Location Management Function (LMF). Multiple transactions can be created in a single session, each transaction corresponding to one LPP operation. An LPP message must include a transaction ID, which can indicate that the initiator (also called the "initiator") is a server-type node, or that the initiator is a client-type node.

[0038] In the case of an SLPP session, multiple UEs may be involved in a single session, and the client and server modes in LPP may not be applicable. Therefore, transaction IDs cannot simply distinguish initiators using either server or client. In addition to initiators, participants must also be considered.

[0039] Furthermore, in the case of an LPP transaction, since only two UEs are involved, it is possible to determine that the transaction has ended after one UE sends an end transaction instruction. In SLPP, if multiple UEs may be involved in a single transaction, it is also necessary to consider how to determine the end of the transaction.

[0040] Figure 3 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 3, the information processing method is performed by the transmitting side, and the information processing method may include the following step 301. In step 301, an SLPP message is sent, the SLPP message containing the transaction ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0041] In some examples, the first transaction may be any one of all transactions in a single session.

[0042] In some examples, the sender may be the initiator of the first transaction, or the sender may be a participant in the first transaction, where the participant in the first transaction is different from the initiator of the first transaction.

[0043] In some examples, the initiator of the first transaction may be the initiator of the session in which the first transaction resides. Alternatively, the initiator of the first transaction may be a participant in the session in which the first transaction resides, and the initiator of the session in which the first transaction resides may be different from a participant in the session in which the first transaction resides.

[0044] In some examples, the initiator of the first transaction may be the anchor UE, and the participants of the first transaction may be the target UE. Alternatively, the initiator of the first transaction may be the target UE, and the participants of the first transaction may be the anchor UE. For example, the anchor UE may be an RSU type anchor UE and / or a UE of a different type from the RSU type.

[0045] In some examples, a participant different from the initiator of the first transaction may be a single UE or a group of UEs. A group of UEs may contain multiple UEs.

[0046] In this embodiment, the transaction ID of the first transaction is used to identify the first transaction and to determine who initiated the first transaction.

[0047] In some examples, the transaction ID of the first transaction may include the UE ID of the first transaction initiator.

[0048] In some examples, the transaction ID of the first transaction may include directive information to determine who initiated the first transaction.

[0049] For example, the instruction information may be a UE type, and the UE type may include a server type or a client type.

[0050] For example, if there are two UEs involved in the first transaction, the UE ID of the UE that initiated the first transaction can be specified using the UE type.

[0051] For example, the server type can be used to indicate that the server UE is the initiator, or the client type can be used to indicate that the client UE is the initiator.

[0052] When two UEs (User Entities) are involved in the same transaction, UE types can be used to distinguish between the two different UEs. In this way, UE types can be used to distinguish the initiator of the same transaction, improving compatibility with related technologies.

[0053] In some examples, the initiator of the first transaction is a server UE, the transaction ID of the first transaction includes the UE type, and the UE type is used to indicate the UE ID of the initiator of the first transaction.

[0054] In some examples, in step 301 above, the sender sends an SLPP message to the receiver that includes the transaction ID of the first transaction.

[0055] For example, the sender is the initiator of the first transaction, and the receiver includes participants different from the initiator of the first transaction.

[0056] For example, the sender is a participant in the first transaction, and the receiver includes a different initiator than the participants in the first transaction.

[0057] For example, the sender may be the first participant among multiple participants in the first transaction, and the receiver may include other participants different from the first participant in the first transaction.

[0058] In some examples, the first transaction can be used for an SLPP operation, which may include at least one of capability exchange, support data transmission, and location information transmission.

[0059] In some cases, different SLPP messages within the same transaction use the same transaction number.

[0060] In some examples, an SLPP message includes at least one of the following: an SLPP transaction creation request message, an SLPP transaction creation completion message, and an SLPP message containing the transaction content.

[0061] In some examples, the SLPP message contains the transaction ID of the first transaction to trigger the creation of the first transaction.

[0062] For example, the SLPP message is the first SLPP message containing the transaction ID of the first transaction, and the SLPP message is used to trigger the creation of the first transaction. In this case, the SLPP message may also be a transaction creation request message for the first transaction.

[0063] For example, the SLPP message received by the receiving end is the first SLPP message containing the transaction ID of the first transaction, and it triggers the creation of the first transaction. In this case, the SLPP message may also be a transaction creation request message for the first transaction.

[0064] In some examples, if an SLPP message contains an SLPP message body, the SLPP message contains a transaction ID. The SLPP message body may be, for example, slpp-MessageBody.

[0065] In the information processing method provided by the embodiments of this disclosure, an SLPP message is sent, the SLPP message includes a transaction ID of a first transaction, and the transaction ID is used to determine the initiator of the first transaction. In this way, the transaction initiator can be determined using the transaction ID included in the SLPP message, which reduces situations where the transaction initiator cannot be distinguished when multiple participants participate in the same transaction, or where different participants in the same transaction determine different initiators, thereby improving the accuracy of information interaction in the transaction process. Because the transaction initiator can be distinguished more accurately based on the transaction ID, positioning using an SLPP message containing a transaction ID can improve the accuracy of positioning.

[0066] In some embodiments, the transaction ID may include a first ID for identifying the initiator of the first transaction.

[0067] In some examples, the first ID may include the UE ID of the initiator of the first transaction. UE IDs can be used to identify UEs. For example, different UEs involved in the same transaction will have different UE IDs.

[0068] In another example, the same UE may have different UE IDs in different transactions.

[0069] In some examples, the first ID may be a substring of the first specified position in the transaction ID string.

[0070] For example, a substring may contain a single character, or it may contain multiple characters that are distributed consecutively.

[0071] For example, the transaction ID string contains M characters, and the first ID may be a string composed of the first N characters of the M characters, or the first ID may be a string composed of the last N characters of the M characters, or the first ID may contain N characters distributed consecutively from any intermediate position in the M characters, where N is a positive integer greater than or equal to 1 and less than M.

[0072] In this embodiment, the substring at the first specified position in the transaction ID string constitutes the first ID string, thereby facilitating rapid decoding by the subsequent receiving end and enabling quick determination of the initiator of the first transaction.

[0073] In this embodiment, the transaction ID includes a first ID, and the first ID is used to indicate the initiator of the first transaction, so the recipient of the SLPP message is This allows for more accurate identification of the transaction initiator, and enables different participants in the first transaction to uniquely determine the initiator of the first transaction based on the first ID, contributing to improved accuracy of information interactions within the same transaction.

[0074] In some embodiments, the first ID is the source layer 2 ID of the initiator and the destination layer 2 ID of the initiator. It may include at least one of the following: Layer 2 ID, Initiator's Application Layer ID, and Initiator's SLPP UE ID.

[0075] In some embodiments, the transaction ID may further include a second ID for identifying the participants in the first transaction.

[0076] In some examples, the second ID may include the UE ID of a participant in the first transaction. UE IDs can be used to identify UEs. For example, different UEs involved in the same transaction will have different UE IDs.

[0077] In another example, the same UE may have different UE IDs in different transactions.

[0078] In some examples, the second ID may be a substring of the second specified position in the transaction ID string.

[0079] For example, a substring may contain a single character, or it may contain multiple characters that are distributed consecutively.

[0080] For example, a different second ID indicates a different participant in the first transaction, and a different second ID corresponds to a substring at a different position in the transaction ID string.

[0081] For example, if the first ID is a substring of the first specified position in the transaction ID string, the second specified position is different from the first specified position.

[0082] In this embodiment, the substring at the second specified position in the transaction ID string constitutes the second ID string, thereby facilitating rapid decoding by the subsequent receiving end and enabling quick determination of the participants in the first transaction.

[0083] In this embodiment, since the transaction ID includes a second ID for identifying the participants in the first transaction, when the recipient of an SLPP message receives an SLPP message containing the transaction ID of the first transaction, it can determine whether or not it is a participant in the first transaction based on the second ID included in the transaction ID of the first transaction. For example, in a process that uses SLPP messages for positioning, some UEs have absolute position information, while others do not. If a participant in a transaction that requires positioning needs to perform absolute positioning, the second ID can be used to specify a UE with absolute position information as the participant.

[0084] In some embodiments, the participant in the first transaction is one UE, and the aforementioned ID 2 may include at least one of the following: the participant's source layer 2 ID, the participant's destination layer 2 ID, the participant's application layer ID, and the participant's SLPP user equipment (UE) ID.

[0085] In some embodiments, the participant is a UE group, and the second ID is the group ID of the UE group, the source layer 2 groupcast ID of the UE group, and the destination layer 2 groupcast ID of the UE group. It may include at least one of the following: ID, Application Layer group ID of the UE group, and SLPP group ID of the UE group.

[0086] In some examples, at least one of the source layer 2 group cast ID, destination layer 2 group cast ID, and application layer group ID of the UE group may be provided by the session initiator's application layer and provided to session participants via a message for session establishment.

[0087] In some cases, the SLPP UE group ID may be created by the session initiator and provided to session participants via a message for session establishment.

[0088] In some embodiments, the participant in the first transaction is a UE group, and the second ID includes at least one of the participant's source layer 2 ID list, the participant's destination layer 2 ID list, the participant's application layer ID list, and the participant's SLPP UE ID list.

[0089] In some embodiments, the first transaction is created in broadcast mode, and the transaction ID of the first transaction may or may not include the second ID.

[0090] In this embodiment, the first transaction is created in broadcast mode, and there are multiple recipients of the SLPP message. These recipients receive the SLPP message containing the transaction ID of the first transaction, and if the transaction ID of the first transaction contains a second ID, they can determine whether or not they are a participant in the first transaction based on the second ID. If a recipient determines that they are a participant in the first transaction, they participate in the first transaction. If a recipient determines that they are not a participant in the first transaction, they can ignore the SLPP message.

[0091] For example, if one or more nodes surrounding a target UE are nodes that themselves possess location information, these nodes can be designated as anchor UEs. Therefore, by using a second ID included in the transaction ID of the first transaction, it is possible to instruct the anchor UEs to be participants in the first transaction, thereby improving the efficiency and accuracy of positioning the target UE.

[0092] In some embodiments, the first transaction is created in broadcast mode, and the second ID included in the transaction ID of the first transaction includes at least one of the participants' source Layer 2 broadcast ID, destination Layer 2 broadcast ID, and SLPP broadcast ID.

[0093] In some examples, the participant's source Layer 2 broadcast ID and destination Layer 2 At least one of the IDs may be provided by the session initiator's application layer and provided to session participants via a message for session establishment. The SLPP broadcast ID may be created by the session initiator and provided to session participants via a message for session establishment.

[0094] In some embodiments, the participant in the first transaction is a single UE or group of UEs, and the transaction ID includes the second ID.

[0095] Compared to a single UE, a UE group can contain one or more UEs. Transactions based on a UE group can enable multi-party transactions and / or positioning if the UE group contains multiple UEs. Positioning accuracy can be improved by positioning the initiator using a UE group, or positioning the UE group using the initiator can improve positioning efficiency.

[0096] In some embodiments, the first transaction is created in broadcast mode, and the transaction ID does not include the second ID.

[0097] In this embodiment, the first transaction is created in broadcast mode, and the transaction ID of the first transaction includes the first ID but does not include the second ID. In this way, if the receiving party is not the initiator of the first transaction, it can determine that it is a participant in the first transaction.

[0098] In some embodiments, the transaction ID of the first transaction is different from the transaction ID of the second transaction, and the first and second transactions are concurrent transactions in the same session.

[0099] In some examples, the transaction ID of the first transaction can be used to identify a third transaction in the first session in which the first transaction resides, and the third transaction is a transaction that is not concurrent with the first transaction.

[0100] For example, the third transaction may be a transaction created before the first transaction in the first session is created, or the third transaction may be a transaction created after the first transaction in the first session has finished.

[0101] In some embodiments, the fact that the transaction ID of the first transaction is different from the transaction ID of the second transaction indicates at least one of the following: the initiator of the first transaction is different from the initiator of the second transaction; the participants of the first transaction are different from the participants of the second transaction; and the transaction ID includes a transaction number, and the transaction number of the first transaction is different from the transaction number of the second transaction.

[0102] In some cases, different SLPP messages within the same transaction use the same transaction number.

[0103] In some embodiments, the information processing method may further include the step of sending an SLPP message containing instruction information, which is used to indicate that the first transaction is terminated, and that the SLPP message is the last message sent by the sender in the first transaction, or the last message containing the SLPP message body.

[0104] In some cases, if the number of UEs involved in the first transaction is two or less, the initiator or participant of the first transaction may send an SLPP message containing instructions to terminate the first transaction. Alternatively, if the number of UEs involved in the first transaction is more than two, the initiator of the first transaction may send an SLPP message containing instructions to terminate the first transaction. For example, the SLPP message containing the instruction information may be the last SLPP message containing the body of the first transaction.

[0105] In this example, after the receiving party receives an SLPP message containing instruction information and confirms that the first transaction has ended, or after confirming that the SLPP message is the last SLPP message containing the body of the first transaction, it no longer expects to receive any further SLPP messages related to the first transaction, or any SLPP messages containing the body of the first transaction. In other words, if the receiving party receives an SLPP message for a transaction with the same transaction ID as the first transaction, or an SLPP message containing the body of the SLPP message for a transaction with the same transaction ID as the first transaction, it will treat that SLPP as an SLPP message for a new transaction.

[0106] In some examples, if the number of UEs involved in the first transaction is greater than two, the participants in the first transaction may send an SLPP message containing instruction information, which is used to indicate that the SLPP message is the last message sent by the sender in the first transaction or the last message containing an SLPP message body.

[0107] In some embodiments, the number of UEs involved in the first transaction is two or less, and the information processing method further includes the step of sending an SLPP message containing first instruction information, the first instruction information being used to terminate the first transaction, and the SLPP message containing the first instruction information including one of the last SLPP message involved in the first transaction and the last SLPP message containing the body of the SLPP message involved in the first transaction.

[0108] In some embodiments, the participants in the first transaction are a group of UEs, the sender is a UE within the group of UEs, and the information processing method further includes sending an SLPP message containing second directive information, the second directive information being used to indicate that the SLPP message containing the second directive information is the sender's last message in the first transaction or the last message containing the body of an SLPP message.

[0109] In some embodiments, the participants in the first transaction are a UE group, the sender is the initiator of the first transaction, and the information processing method further includes the step of sending an SLPP message containing third instruction information in response to a decision to terminate the first transaction, the third instruction information being the first transaction Used to terminate the action.

[0110] In some embodiments, the participants in the first transaction are a group of UEs, the sender is any one of the UEs involved in the first transaction, and the information processing method further includes the step of sending an SLPP message containing a fourth directive, the fourth directive is used to indicate that the SLPP message containing the fourth directive is the last message from the sender in the first transaction or the last message containing an SLPP message body.

[0111] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0112] Next, the information processing method performed by the receiving side will be described. This is similar to the description of the information processing method performed by the transmitting side, and for technical details not disclosed in the embodiment of the information processing method performed by the receiving side, refer to the description of the embodiment of the information processing method performed by the transmitting side; therefore, a detailed explanation will be omitted here.

[0113] Figure 4 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 4, the information processing method is performed by the receiving side, and the information processing method may include the following step 401. In step 401, an SLPP message is received, the SLPP message contains the transaction ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0114] In some examples, the first transaction may be any one of all transactions in a single session.

[0115] In some examples, in step 401 above, the receiver receives an SLPP message sent by the sender that contains the transaction ID of the first transaction.

[0116] In some examples, if the sender is the initiator of the first transaction, the receiver is a participant in the first transaction. Alternatively, if the sender is a participant in the first transaction, the receiver may include participants different from the initiator and / or sender of the first transaction. The participants in the first transaction are different from the initiator of the first transaction.

[0117] In this embodiment, the transaction ID of the first transaction is used to identify the first transaction and to determine who initiated the first transaction.

[0118] In some examples, the explanation of the relationship between the contents, such as the transaction ID, can be found in step 301 of Figure 3, so the explanation is omitted here.

[0119] The information processing method provided by the embodiments of this disclosure receives an SLPP message, the SLPP message contains a transaction ID of a first transaction, and the transaction ID is used to determine the initiator of the first transaction. By doing so, the receiving party can determine the transaction initiator using the transaction ID included in the SLPP message, reducing situations where it is impossible to distinguish the transaction initiator when multiple participants are participating in the same transaction, or where different participants in the same transaction determine different initiators, thereby improving the accuracy of information interaction in the transaction process. Because the transaction initiator can be distinguished more accurately based on the transaction ID, positioning using an SLPP message containing the transaction ID can improve the accuracy of positioning.

[0120] In some embodiments, the transaction ID includes a first ID for identifying the initiator of the first transaction.

[0121] In some embodiments, the first ID includes at least one of the initiator's source layer 2 ID, the initiator's destination layer 2 ID, the initiator's application layer ID, and the initiator's SLPP UE ID.

[0122] In some embodiments, the transaction ID further includes a second ID for identifying the participants in the first transaction.

[0123] In some embodiments, the participant is a single UE, and the second ID includes at least one of the participant's source layer 2 ID, the participant's destination layer 2 ID, the participant's application layer ID, and the participant's SLPP user equipment (UE) ID.

[0124] In some embodiments, the participant is a UE group, and the second ID includes at least one of the following: the group ID of the UE group, the source layer 2 group cast ID of the UE group, the destination layer 2 group cast ID of the UE group, the application layer group ID of the UE group, and the SLPP UE group ID of the UE group.

[0125] In some embodiments, the participant is a UE group, and the second ID includes at least one of the participant's source layer 2 ID list, the participant's destination layer 2 ID list, the participant's application layer ID list, and the participant's SLPP UE ID list.

[0126] In some embodiments, the first transaction is created in broadcast mode, and the second ID includes at least one of the participant's source Layer 2 broadcast ID, destination Layer 2 broadcast ID, and SLPP broadcast ID, or the participant in the first transaction is a single UE or group of UEs, and the transaction ID includes the second ID. Alternatively, the first transaction is created in broadcast mode, and the transaction ID does not include the second ID.

[0127] In some embodiments, the transaction ID of the first transaction is different from the transaction ID of the second transaction, and the first and second transactions are concurrent transactions in the same session.

[0128] In some embodiments, the initiator of the first transaction is different from the initiator of the second transaction, and / or the participant in the first transaction is different from the first. Unlike the participants in the second transaction, and / or, the transaction ID includes a transaction number, and the transaction number of the first transaction is different from the transaction number of the second transaction.

[0129] In some embodiments, the number of UEs involved in the first transaction is two or less, and the information processing method further includes the step of receiving an SLPP message containing first instruction information, the first instruction information being used to terminate the first transaction, and the SLPP message containing the first instruction information including one of the last SLPP message involved in the first transaction and the last SLPP message containing the body of the SLPP message involved in the first transaction.

[0130] In some embodiments, the participants in the first transaction are a UE group, the recipient is the initiator of the first transaction, and the information processing method is The process further includes receiving an SLPP message sent by the sender, which includes a second instruction information, the second instruction information being used to indicate that the SLPP message including the second instruction information is the last message from the sender in the first transaction or the last message including the SLPP message body.

[0131] In some embodiments, the participants in the first transaction are a group of UEs, the recipient is a UE within the group of UEs, and the information processing method further includes the step of deciding to terminate the first transaction in response to the receipt of an SLPP message containing the third instruction information, or determining that the SLPP message containing the third instruction information is the last message containing the SLPP message body of the first transaction.

[0132] In some embodiments, the participants in the first transaction are a group of UEs, and the information processing method further includes: deciding to terminate the first transaction in response to the receipt of an SLPP message containing a fourth instruction information, the SLPP message containing the fourth instruction information being sent by all other UEs except the receiving party involved in the first transaction.

[0133] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0134] Figure 5 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 5, the information processing method is performed by the transmitting side and may include the following step 501. In step 501, an SLPP message containing first instruction information is sent, the first instruction information is used to terminate the first transaction, and the number of UEs involved in the first transaction is two or less.

[0135] In some examples, the SLPP message containing the first instruction information includes one of the last SLPP messages involved in the first transaction, and the last SLPP message containing the body of the SLPP message involved in the first transaction.

[0136] For example, if two UEs are involved in the first transaction, and the SLPP message that the sender needs to send is the last SLPP message in the first transaction, or the last message containing the SLPP message body in the first transaction, the sender adds the first instruction information to that SLPP message, and then... You can instruct the end of transaction 1.

[0137] For example, if two UEs are involved in the first transaction, and the sender is the initiator of the first transaction, the sender can send an SLPP message containing the first instruction information, so that the receiver (where the receiver is a participant in the first transaction) can know that the first transaction has ended when it receives the first SLPP message.

[0138] In some examples, the first instruction information may be included in the message header or message body of the SLPP message. For example, if both the first instruction information and the transaction content are included in the message body of an SLPP message, the message body will further include a distinguishing mark to differentiate the first instruction information from the transaction content within the message body.

[0139] In some examples, the first instruction information may be a transaction termination instruction. For example, a transaction end instruction is a single end marker, which may be "end session", or it may be a bit sequence that indicates termination.

[0140] If the SLPP message of the first transaction includes a message body, and that SLPP message is the last SLPP message to include a message body, then that SLPP message can include a transaction termination instruction. This eliminates the need to construct a separate dedicated message containing the transaction termination instruction in addition to the SLPP message containing the message body, thus allowing the SLPP message to be reused and simplifying the implementation.

[0141] In some examples, the transaction termination instruction may be included in an SLPP message that does not contain the SLPP message body. In such examples, the SLPP message containing the first instruction information may be understood as a dedicated SLPP message or a specific SLPP message for instructing the termination of a transaction. For example, after the transmission of the last SLPP message of the first transaction, which includes the message body, is complete, an SLPP message containing a transaction termination instruction is sent.

[0142] In the embodiments of this disclosure, the number of UEs involved in the first transaction is two or less, the sender can send an SLPP message containing first instruction information to terminate the first transaction, and the receiver can directly terminate the first transaction based on the first instruction information.

[0143] Figure 6 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 6, the information processing method is performed by the transmitting side, and the information processing method may include the following step 601. In step 601, an SLPP message containing a second instruction information is sent, the second instruction information being used to indicate that the SLPP message containing the second instruction information is the last message from the sender in the first transaction or the last message containing the SLPP message body, the participants in the first transaction being a UE group, and the sender being a UE within the UE group.

[0144] In some cases, the second instruction information may be included in the message header or message body of the SLPP message. For example, if both the second instruction information and the transaction content are included in the message body of an SLPP message, the message body will further include a distinguishing mark to differentiate the second instruction information from the transaction content within the message body.

[0145] In some examples, the second instruction information may be a transaction termination instruction. For example, a transaction end instruction is a single end marker, which may be "end session", or a transaction end instruction may be a bit sequence indicating termination.

[0146] If the SLPP message sent by the sender in the first transaction includes a message body, it can also include a transaction termination instruction. Thus, the SLPP message is reused, simplifying the implementation, as there is no need to construct a separate dedicated message containing the transaction termination instruction in addition to the SLPP message containing the message body.

[0147] In some examples, the transaction termination instruction may be included in an SLPP message that does not contain the SLPP message body. In such examples, the SLPP message containing the second instruction information may be understood as a dedicated SLPP message or a specific SLPP message. For example, after the transmission of the last SLPP message, including the message body, sent by the sender in the first transaction, is complete, an SLPP message containing a transaction termination instruction is sent.

[0148] In some cases, the sender can send the SLPP message containing the second instruction information via unicast, groupcast, or broadcast.

[0149] In this embodiment, the sender sends an SLPP message containing second instruction information, and if the receiver is the initiator of the first transaction, the receiver can confirm, based on the second instruction information contained in the SLPP message, that the SLPP message is the sender's last message in the first transaction or the last message containing the SLPP message body. This contributes to improving the accuracy with which the initiator and multiple participants of the same transaction determine the end of the transaction.

[0150] In some embodiments, the information processing method further includes the step of receiving an SLPP message containing a third instruction information, the third instruction information being used to terminate the first transaction, and the SLPP message containing the third instruction information being an SLPP message sent by the initiator of the first transaction.

[0151] In some embodiments, the information processing method further includes the step of confirming that the first transaction has ended, or confirming that the SLPP message containing the third instruction information is the last message containing the SLPP message body in the first transaction, based on an SLPP message containing a third instruction information sent by the initiator of the first transaction.

[0152] In this embodiment, after a participant in the first transaction confirms that the first transaction has ended based on the third instruction information, or after confirming that the SLPP message containing the third instruction information is the last message containing the SLPP message body in the first transaction, any SLPP messages relating to the first transaction You will no longer expect to receive any SLPP messages, including the SLPP message body related to the first transaction. In other words, if you receive an SLPP message for a transaction with the same transaction ID as the first transaction, or an SLPP message containing the SLPP message body for a transaction with the same transaction ID as the first transaction, you will treat that SLPP as the SLPP message for a new transaction.

[0153] In this embodiment, since multiple different participants are involved in the same transaction, by receiving an SLPP message containing third instruction information sent by the initiator of the first transaction, the participants of the first transaction can know that the first transaction has ended based on the third instruction information, thereby contributing to improved accuracy in determining transaction termination by the initiator and multiple participants of the same transaction.

[0154] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0155] Figure 7 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 7, the information processing method is performed by the transmitting side, and the information processing method may include the following step 701. In step 701, in response to the decision to terminate the first transaction, an SLPP message containing third instruction information is sent, the third instruction information is used to terminate the first transaction, the sender is the initiator of the first transaction, and the participants of the first transaction are the UE group.

[0156] In some examples, the third instruction may be a transaction termination instruction.

[0157] In some examples, deciding to terminate the first transaction may include deciding that it is necessary to terminate the first transaction.

[0158] In some cases, the initiator of the first transaction sends an SLPP message containing third instruction information, allowing the recipient to know that the first transaction has ended after receiving the SLPP message.

[0159] For example, the initiator of the first transaction decides to terminate the first transaction based on an SLPP message containing second instruction information sent by all participants of the first transaction that it received.

[0160] In some examples, the initiator of the first transaction decides to terminate the first transaction itself. In such examples, the initiator of the first transaction can terminate the first transaction proactively, that is, it does not have to directly decide to terminate the first transaction based on an SLPP message containing second instruction information sent by a participant in the first transaction.

[0161] In some cases, the third instruction information may be included in the message header or message body of the SLPP message. For example, if both the third instruction information and the transaction content are included in the message body of an SLPP message, the message body will further include a distinguishing mark to differentiate between the third instruction information and the transaction content within the message body. .

[0162] In some examples, the third instruction may be a transaction termination instruction. For example, a transaction end instruction is a single end marker, which may be "end session", or the transaction end instruction may be a bit sequence indicating termination.

[0163] If the SLPP message sent by the sender in the first transaction includes a message body, it can also include a transaction termination instruction. In this way, the SLPP message is reused, simplifying the implementation because it is not necessary to construct a separate dedicated message containing the transaction termination instruction in addition to the SLPP message containing the message body.

[0164] In some examples, the transaction termination instruction may be included in an SLPP message that does not contain the SLPP message body. In such examples, the SLPP message containing the third instruction information may be understood as a dedicated SLPP message or a specific SLPP message. For example, after the transmission of the last SLPP message, including the message body, sent by the sender in the first transaction, is complete, an SLPP message containing a transaction termination instruction is sent.

[0165] In some cases, the sender can send an SLPP message containing third instruction information via unicast, groupcast, or broadcast.

[0166] In this embodiment, the initiator of the first transaction sends an SLPP message containing third instruction information, allowing participants who receive the SLPP message to know that the first transaction has ended based on the third instruction information contained in the SLPP message. This contributes to improving the accuracy with which the initiator and multiple participants of the same transaction determine transaction termination.

[0167] Figure 8 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 8, the information processing method is performed by the transmitting side, and the information processing method may include the following step 801. In step 801, an SLPP message containing a fourth instruction is sent, the fourth instruction is used to indicate that the SLPP message containing the fourth instruction is the last message from the sender in the first transaction or the last message containing the SLPP message body, the participants in the first transaction are a group of UEs, and the sender is any one of the UEs involved in the first transaction. For example, a UE group can contain multiple UEs.

[0168] In some examples, the fourth instruction information may be included in the message header or message body of the SLPP message. For example, if both the fourth instruction information and the transaction content are included in the message body of the SLPP message, the message body will further include a distinguishing mark to distinguish between the fourth instruction information and the transaction content within the message body.

[0169] In some examples, the fourth instruction may be a transaction termination instruction. For example, a transaction end instruction is a single end marker, which may be "end session", or the transaction end instruction may be It may also be a bit sequence indicating completion.

[0170] If the SLPP message sent by the sender in the first transaction includes a message body, it can also include a transaction termination instruction. In this way, the SLPP message is reused, simplifying the implementation because it is not necessary to construct a separate dedicated message containing the transaction termination instruction in addition to the SLPP message containing the message body.

[0171] In some examples, the transaction termination instruction may be included in an SLPP message that does not contain the SLPP message body. In such examples, the SLPP message containing the fourth instruction information may be understood as a dedicated SLPP message or a specific SLPP message. For example, after the transmission of the last SLPP message, including the message body, sent by the sender in the first transaction, is complete, an SLPP message containing a transaction termination instruction is sent.

[0172] In some cases, the sender can send the SLPP message containing the fourth instruction information via unicast, groupcast, or broadcast.

[0173] In this embodiment, if the participants in the first transaction are a group of UEs, and the sender is one of the UEs involved in the first transaction, the sender sends an SLPP containing fourth instruction information. When the receiver receives an SLPP message containing fourth instruction information from the sender, it can confirm that the SLPP message is the last message sent by the sender in the first transaction, or the last message containing the SLPP message body. This contributes to improving the accuracy with which the initiator and multiple participants of the same transaction determine the end of the transaction.

[0174] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0175] Next, the information processing method performed by the receiving side will be described. This is similar to the description of the information processing method performed by the transmitting side, and for technical details not disclosed in the embodiment of the information processing method performed by the receiving side, refer to the description of the embodiment of the information processing method performed by the transmitting side; therefore, a detailed explanation will be omitted here.

[0176] Figure 9 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 9, the information processing method is performed by the receiving side, and the information processing method may include the following step 901. In step 901, an SLPP message containing first instruction information is received, the first instruction information is used to terminate the first transaction, and the number of UEs involved in the first transaction is two or less.

[0177] In some examples, the SLPP message containing the first instruction information includes one of the last SLPP messages involved in the first transaction, and the last SLPP message containing the body of the SLPP message involved in the first transaction.

[0178] For example, two UEs are involved in the first transaction, and the SLPP message that the sender needs to send is the last SLPP message in the first transaction, If it is the last message containing the SLPP message body in the first transaction, the sender may add the first instruction information to the SLPP message to indicate the termination of the first transaction.

[0179] For example, if two UEs are involved in the first transaction, and the sender is the initiator of the first transaction, the sender can send an SLPP message containing the first instruction information, and when the receiver (where the receiver is a participant in the first transaction) receives the first SLPP message, it can decide to terminate the first transaction.

[0180] In some examples, the first instruction information may be included in the message header or message body of the SLPP message. For example, if both the first instruction information and the transaction content are included in the message body of an SLPP message, the message body will further include a distinguishing mark to differentiate the first instruction information from the transaction content within the message body.

[0181] In some examples, the first instruction information may be a transaction termination instruction. For example, a transaction end instruction is a single end marker, which may be "end session", or a transaction end instruction may be a bit sequence indicating termination.

[0182] If the SLPP message of the first transaction includes a message body, it can also include a transaction termination instruction. This eliminates the need to construct a separate, dedicated message containing the transaction termination instruction in addition to the SLPP message containing the message body, thus allowing the SLPP message to be reused and simplifying the implementation.

[0183] In some examples, the transaction termination instruction may be included in an SLPP message that does not contain the SLPP message body. In such examples, the SLPP message containing the first instruction information may be understood as a dedicated SLPP message or a specific SLPP message that instructs transaction termination.

[0184] For example, after the transmission of the last SLPP message, which includes the message body in the first transaction, is complete, an SLPP message containing a transaction termination instruction is sent.

[0185] In the embodiments of this disclosure, the number of UEs involved in the first transaction is two or less, and the receiving party can directly terminate the first transaction based on the first instruction information after receiving an SLPP message containing the first instruction information.

[0186] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0187] Figure 10 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 10, the information processing method is performed by the receiving side, and the information processing method may include the following step 1001. In step 1001, the sender receives an SLPP message containing second instruction information, and the second instruction information is the last message or SLPP message from the sender in the first transaction. This is used to indicate that it is the last message containing a body, and the participants in the first transaction are a UE group, with the sender being a UE within that UE group.

[0188] In some cases, the second instruction information may be included in the message header or message body of the SLPP message. For example, if both the second instruction information and the transaction content are included in the message body of an SLPP message, the message body will further include a distinguishing mark to differentiate the second instruction information from the transaction content within the message body.

[0189] In some examples, the second instruction information may be a transaction termination instruction. For example, a transaction end instruction is a single end marker, which may be "end session", or a transaction end instruction may be a bit sequence indicating termination.

[0190] If the SLPP message sent by the sender in the first transaction includes a message body, it can also include a transaction termination instruction. In this way, the SLPP message is reused, simplifying the implementation because it is not necessary to construct a separate dedicated message containing the transaction termination instruction in addition to the SLPP message containing the message body.

[0191] In some examples, the transaction termination instruction may be included in an SLPP message that does not contain the SLPP message body. In such examples, the SLPP message containing the second instruction information may be understood as a dedicated SLPP message or a specific SLPP message. For example, the sender sends an SLPP message containing a transaction termination instruction after the transmission of the last SLPP message, which includes the message body, in the first transaction is complete.

[0192] In some cases, the receiving end may receive the SLPP message containing the second instruction information via unicast, groupcast, or broadcast.

[0193] In this embodiment, if the receiving party is the initiator of the first transaction, upon receiving an SLPP message containing second instruction information, it can confirm, based on the second instruction information contained in the SLPP message, that the SLPP message is the last message sent by the sender in the first transaction, or the last message containing the SLPP message body. This contributes to improving the accuracy with which the initiator and multiple participants of the same transaction determine the end of the transaction.

[0194] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0195] Figure 11 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 11, the information processing method is performed by the receiving side, and the information processing method may include the following step 1101. In step 1101, in response to receiving an SLPP message containing third instruction information, it is decided to terminate the first transaction, or it is determined that the SLPP message containing third instruction information is the last message containing the SLPP message body in the first transaction, and the participants in the first transaction are the UE group. The receiving side is a UE within the UE group.

[0196] In some examples, the relevant explanation of the content of the third instruction information, etc., can be found by referring to the relevant explanation of the content of the third instruction information, etc., in the embodiments described above, so the explanation is omitted here.

[0197] In some cases, the receiving end may receive the SLPP message containing the third instruction information via unicast, groupcast, or broadcast.

[0198] In this embodiment, after a participant in the first transaction confirms that the first transaction has ended based on the third instruction information, or after confirming that the SLPP message containing the third instruction information is the last message containing the SLPP message body in the first transaction, they no longer expect to receive any SLPP messages relating to the first transaction, or any SLPP messages containing the SLPP message body relating to the first transaction. In other words, if a participant in the first transaction receives an SLPP message for a transaction with the same transaction ID as the first transaction, or an SLPP message containing the SLPP message body for a transaction with the same transaction ID as the first transaction, that SLPP is treated as an SLPP message for a new transaction.

[0199] In this embodiment, since multiple different participants are involved in the same transaction, the initiator of the first transaction sends an SLPP message containing third instruction information, which allows the participants of the first transaction to decide to terminate the first transaction based on the third instruction information. This contributes to improving the accuracy with which the initiator and multiple participants of the same transaction decide to terminate the transaction.

[0200] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0201] Figure 12 is a flowchart of an information processing method according to an exemplary embodiment. As shown in Figure 12, the information processing method is performed by the receiving side, and the information processing method may include the following step 1201. In step 1201, in response to receiving an SLPP message containing the fourth instruction information, it is decided to terminate the first transaction, and the SLPP message containing the fourth instruction information is sent by all other UEs involved in the first transaction, excluding the receiver, and the participants in the first transaction are the UE group.

[0202] In some examples, the explanation of the content of the fourth instruction information and other related information can be found in the explanation of the content of the fourth instruction information and other related information in the embodiments described above, so the explanation is omitted here.

[0203] In some cases, the receiving end may receive the SLPP message containing the fourth instruction information via unicast, groupcast, or broadcast.

[0204] In this embodiment, if the participants in the first transaction are a group of UEs and the sender is one of the UEs involved in the first transaction, when the receiver receives an SLPP message containing fourth instruction information sent by the sender, the SL It is possible to verify that the PP message is the last message from the sender in the first transaction, or the last message containing the SLPP message body. This contributes to improving the accuracy with which the initiator and multiple participants of the same transaction determine the end of the transaction.

[0205] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0206] Those skilled in the art will understand that the methods provided in the embodiments of this disclosure may be performed alone or in combination with some of the methods in the embodiments of this disclosure or some of the methods of related technology.

[0207] To further illustrate any embodiment of this disclosure, several specific embodiments are given below. Embodiments of the present disclosure provide an information processing method which may include the step of a first UE (e.g., UE A) sending an SLPP message, the SLPP message including a transaction ID, the transaction ID including at least the UE ID of the transaction initiator.

[0208] In some cases, the transaction ID may also include the transaction number.

[0209] In some cases, SLPP messages within the same transaction use the same transaction number.

[0210] In some cases, the transaction ID is included in the SPP message only if the SLPP message contains an SLPP message body (e.g., slpp-MessageBody).

[0211] In some cases, if only two UEs are involved in a transaction, the initiator UE The ID can be indicated by the UE type, for example, by a server UE or a client UE.

[0212] In some cases, if the transaction initiator is the server UE, The ID can be indicated by the UE type, i.e., the server UE.

[0213] In some cases, the initial SLPP message containing the transaction ID received by the UE triggers the establishment of that transaction.

[0214] In some embodiments, the UE ID of the transaction initiator may be the initiator's source Layer 2 ID, destination Layer 2 ID, application layer ID, or SLPP UE ID.

[0215] In some embodiments, the transaction ID further includes the UE IDs of the transaction participants.

[0216] In some examples, if the transaction has one participant, the participant's UE ID is either the participant's source Layer 2 ID, destination Layer 2 ID, application layer ID, or SLPP UE ID. That's good too.

[0217] In some examples, if the participants in the transaction are a single group of UEs, the UE ID of the transaction participants may be the participant's source Layer 2 / destination Layer 2 groupcast ID, application layer group ID, or SLPP group ID.

[0218] In some cases, the source layer 2 / destination layer 2 groupcast ID, or application layer group ID, is provided by the application layer of the session initiator and is provided to session participants via a message for session establishment. The SLPP group ID is created by the session initiator and is provided to session participants via a message for session establishment.

[0219] In some examples, if the participants in the transaction are a single group of UEs, the UE IDs of the participants in the transaction are the source layer 2 / destination layer 2 IDs of each participant. This could be an ID list, or a list of application layer IDs for each participant, or a list of SLPP UE IDs for each participant.

[0220] In some examples, if the transaction is created in broadcast mode, the UE ID of the transaction participant may be the source Layer 2 / destination Layer 2 broadcast ID or the SLPP broadcast ID.

[0221] In some examples, the source layer 2 / destination layer 2 broadcast ID is provided by the session initiator's application layer and provided to session participants via a message for session establishment. The SLPP broadcast ID is created by the session initiator and provided to session participants via a message for session establishment.

[0222] In some examples, the transaction ID includes the participant's UE ID only if the transaction participants are a single UE or a group of UEs.

[0223] In some cases, if the transaction is created in broadcast mode, the transaction ID does not include the participant's UE ID.

[0224] In some embodiments, the transaction IDs of concurrent transactions within the same session must be different.

[0225] In some cases, after a transaction has ended, the transaction ID can continue to be used to create new transactions within that session.

[0226] In some examples, the requirement that the transaction IDs be different includes at least one of the transaction initiators and transaction numbers being different.

[0227] In some examples, the requirement that the transaction IDs be different includes at least one of the transaction initiator, participants, and transaction number being different.

[0228] In some embodiments, if only two UEs are involved in an SLPP transaction, and the SLPP message that a UE is about to send is the last message of a transaction, or the last message containing the SLPP message body, the UE adds an end transaction instruction (e.g., end transaction) to the SLPP message.

[0229] In some embodiments, if a group of UEs are involved in an SLPP transaction, the participating UEs in the transaction add directive information (e.g., end transaction) to the SLPP message to indicate that the SLPP message currently being sent is the last message for that UE in that transaction, or the last message containing the SLPP message body.

[0230] In some examples, the SLPP message, including the end transaction, can be sent via unicast, groupcast, or broadcast.

[0231] In some examples, the initiating UE of a transaction decides to terminate the transaction and sends a single SLPP message containing the end transaction to the other UEs in the transaction.

[0232] In some cases, if the initiating UE sends an SLPP message containing the end transaction, that SLPP message does not need to contain the SLPP packet body (i.e., the message body).

[0233] In some examples, deciding to terminate a transaction involves deciding to terminate the transaction based on an end transaction instruction sent by a participating UE in the transaction.

[0234] In some examples, the SLPP message, including the end transaction, can be sent via unicast, groupcast, or broadcast.

[0235] In some examples, after other UEs in an SLPP transaction receive an SLPP message containing the end transaction sent by the transaction's initiating UE, they verify that the transaction has ended or that it is the last message containing the SLPP packet body for that transaction.

[0236] In some cases, after the UE confirms that a transaction has ended or that it is the last message containing the SLPP packet body for that transaction, it no longer expects to receive any SLPP messages for that transaction, or any SLPP messages containing the SLPP packet body for that transaction. In other words, the UE considers any received SLPP message with the same transaction ID, or any SLPP message containing the SLPP packet body with the same transaction ID, as the SLPP message for a single new SLPP transaction.

[0237] In some examples, after one UE in a transaction receives an SLPP message containing the end transaction sent by all other UEs in the transaction, it verifies that the transaction has ended or that it is the last message containing the SLPP packet body for that transaction.

[0238] In some cases, after the UE confirms that a transaction has ended, or that it is the last message containing the SLPP packet body for that transaction, it no longer expects to receive any SLPP messages for that transaction, or any SLPP messages containing the SLPP packet body for that transaction. In other words, the UE treats any SLPP message received with the same transaction ID, or any SLPP message containing the SLPP message packet body with the same transaction ID, as SLPP messages for a single new transaction.

[0239] In the embodiments of this disclosure, some or all of the selectable embodiments of the steps can be optionally combined with some or all of the steps of other embodiments, or with selectable embodiments of other embodiments.

[0240] Those skilled in the art will understand that the methods provided in the embodiments of this disclosure may be performed alone or in combination with some of the methods in the embodiments of this disclosure or some of the methods of related technology.

[0241] Figure 13 is a schematic diagram of an information processing device according to an exemplary embodiment. As shown in Figure 13, the information processing device 100 includes a transmission module 110 configured to send an SLPP message, the SLPP message containing a transaction identifier (ID) of a first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0242] In some embodiments, the transaction ID includes a first ID for identifying the initiator of the first transaction.

[0243] In some embodiments, the first ID includes at least one of the initiator's source layer 2 ID, the initiator's destination layer 2 ID, the initiator's application layer ID, and the initiator's SLPP UE ID.

[0244] In some embodiments, the transaction ID further includes a second ID for identifying the participants in the first transaction.

[0245] In some embodiments, the participant is a single UE, and the second ID includes at least one of the participant's source layer 2 ID, the participant's destination layer 2 ID, the participant's application layer ID, and the participant's SLPP user equipment (UE) ID.

[0246] In some embodiments, the participant is a UE group, and the second ID includes at least one of the following: the group ID of the UE group, the source layer 2 group cast ID of the UE group, the destination layer 2 group cast ID of the UE group, the application layer group ID of the UE group, and the SLPP UE group ID of the UE group.

[0247] In some embodiments, the participant is a UE group, and the second ID includes at least one of the participant's source layer 2 ID list, the participant's destination layer 2 ID list, the participant's application layer ID list, and the participant's SLPP UE ID list.

[0248] In some embodiments, the first transaction is created in broadcast mode, and the second ID includes at least one of the participant's source Layer 2 broadcast ID, destination Layer 2 broadcast ID, and SLPP broadcast ID; or the participant in the first transaction is a single UE or group of UEs, and the transaction ID includes the second ID; or the first transaction is created in broadcast mode, and the transaction ID does not include the second ID.

[0249] In some embodiments, the transaction ID of the first transaction is different from the transaction ID of the second transaction, and the first and second transactions are concurrent transactions in the same session.

[0250] In some embodiments, the initiator of the first transaction is different from the initiator of the second transaction, and / or the participants of the first transaction are different from the participants of the second transaction, and / or the transaction ID includes a transaction number, and the transaction number of the first transaction is different from the transaction number of the second transaction.

[0251] In some embodiments, the number of UEs involved in the first transaction is two or less, the transmitting module 110 is configured to transmit an SLPP message containing first instruction information, the first instruction information is used to terminate the first transaction, and the SLPP message containing the first instruction information includes one of the last SLPP message involved in the first transaction, and the last SLPP message involved in the first transaction, which includes an SLPP message body.

[0252] In some embodiments, the participants in the first transaction are a group of UEs, the sender is a UE within the group of UEs, and the send module 110 is configured to send an SLPP message containing second directive information, the second directive information being used to indicate that the SLPP message containing the second directive information is the last message from the sender in the first transaction or the last message containing an SLPP message body.

[0253] In some embodiments, the participants in the first transaction are a UE group, the sender is the initiator of the first transaction, and the send module 110 is configured to send an SLPP message containing third instruction information in response to a decision to terminate the first transaction, the third instruction information being used to terminate the first transaction.

[0254] In some embodiments, the participants in the first transaction are a group of UEs, the sender is any one of the UEs involved in the first transaction, the send module 110 is configured to send an SLPP message containing a fourth instruction information, the fourth instruction information is used to indicate that the SLPP message containing the fourth instruction information is the sender's last message in the first transaction or the last message containing the SLPP message body. With respect to the information processing apparatus in the above embodiments, embodiments in which each module performs operations have been described in detail in the embodiments of the information processing methods performed by the sender, and therefore a detailed description is omitted here.

[0255] Figure 14 is a schematic diagram of an information processing device according to an exemplary embodiment. As shown in Figure 14, the information processing device 200 is configured to receive SLPP messages. The SLPP message includes a 210, and the transaction identifier (ID) of the first transaction is used to determine the initiator of the first transaction.

[0256] In some embodiments, the transaction ID includes a first ID for identifying the initiator of the first transaction.

[0257] In some embodiments, the first ID includes at least one of the initiator's source layer 2 ID, the initiator's destination layer 2 ID, the initiator's application layer ID, and the initiator's SLPP UE ID.

[0258] In some embodiments, the transaction ID further includes a second ID for identifying the participants in the first transaction.

[0259] In some embodiments, the participant is a single UE, and the second ID includes at least one of the participant's source layer 2 ID, the participant's destination layer 2 ID, the participant's application layer ID, and the participant's SLPP user equipment (UE) ID.

[0260] In some embodiments, the participant is a UE group, and the second ID is the group ID of the UE group, the source layer 2 group cast ID of the UE group, the destination layer 2 group cast ID of the UE group, This includes at least one of the following: the application layer group ID of the UE group, and the SLPP UE group ID of the UE group.

[0261] In some embodiments, the participant is a UE group, and the second ID includes at least one of the source layer 2 ID list of the participant, the destination layer 2 ID list of the participant, the application layer ID list of the participant, and the SLPP UE ID list of the participant.

[0262] In some embodiments, the first transaction is created in broadcast mode, and the second ID includes at least one of the source layer 2 broadcast ID of the participant, the destination layer 2 broadcast ID of the participant, and the SLPP broadcast ID, or the participant of the first transaction is one UE or a UE group, the transaction ID includes the second ID, or the first transaction is created in broadcast mode, and the transaction ID does not include the second ID.

[0263] In some embodiments, the transaction ID of the first transaction is different from the transaction ID of the second transaction, and the first transaction and the second transaction are parallel transactions in the same session.

[0264] In some embodiments, the initiator of the first transaction is different from the initiator of the second transaction, and / or the participants of the first transaction are different from the participants of the second transaction, and / or the transaction ID includes a transaction number, and the transaction number of the first transaction is different from the transaction number of the second transaction.

[0265] In some embodiments, the number of UEs involved in the first transaction is two or less. The receiving module 210 is configured to receive an SLPP message containing first instruction information, the first instruction information is used to terminate the first transaction, and the SLPP message containing the first instruction information includes one of the last SLPP message involved in the first transaction, and the last SLPP message involved in the first transaction, which includes the SLPP message body.

[0266] In some embodiments, the participants in the first transaction are a UE group, the receiver is the initiator of the first transaction, and the receiver module 210 is configured to receive an SLPP message containing second instruction information sent by the sender, the second instruction information being used to indicate that the SLPP message containing the second instruction information is the last message from the sender in the first transaction or the last message containing the SLPP message body.

[0267] In some embodiments, the participants in the first transaction are a group of UEs, the receiver is a UE within the group of UEs, and the information processing device further includes a first decision module configured to decide to terminate the first transaction in response to the receipt of an SLPP message containing the third instruction information, or to decide that the SLPP message containing the third instruction information is the last message containing the SLPP message body in the first transaction.

[0268] In some embodiments, the participants in the first transaction are a group of UEs, and the information processing device further includes a first decision module configured to decide to terminate the first transaction in response to the receipt of an SLPP message containing a fourth instruction information, the SLPP message containing the fourth instruction information being sent by all other UEs except the receiving party involved in the first transaction.

[0269] Regarding the information processing apparatus of the above embodiment, since the embodiment in which each module performs its operation was described in detail in the embodiment of the information processing method performed by the receiving side, a detailed explanation is omitted here.

[0270] Embodiments of the present disclosure provide a communication device, the communication device comprising a memory for storing instructions executable by a processor, and a processor connected to the memory, the processor being configured to perform an information processing method provided by any one of the aforementioned inventions.

[0271] The processor may include various types of storage media, which are non-temporary computer storage media capable of retaining information even after the communication device is powered off. Communication devices include UEs. The processor is connected to memory via a bus or the like, and is used to read executable programs stored in memory and, for example, to implement the information processing method provided by one of the embodiments described above.

[0272] Embodiments of this disclosure provide a computer storage medium in which an executable program is stored and the executable program is executed by a processor, thereby enabling the realization of an information processing method provided by any one of the aforementioned technical proposals.

[0273] Figure 15 shows a block of terminal 800 according to an exemplary embodiment. For example, terminal 800 is a mobile phone, computer, digital broadcasting user device, message sending and receiving device This could include games, tablet devices, medical devices, fitness devices, and personal digital assistants.

[0274] Referring to Figure 15, terminal 800 may include one or more of the following: processing component 802, memory 804, power supply component 806, multimedia component 808, audio component 810, input / output (I / O) interface 812, sensor component 814, and communication component 816.

[0275] The processing component 802 typically controls the overall operation of the terminal 800, including operations related to display, telephone calling, data communication, camera operation, and recording. The processing component 802 may include one or more processors 820 for executing instructions to complete all or some of the steps of the above method. The processing component 802 may also include one or more modules to facilitate interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

[0276] Memory 804 is configured to store various types of data to support the operation of terminal 800. Examples of this data include instructions for any application programs or methods that operate on terminal 800, contact data, phonebook data, messages, images, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.

[0277] The power component 806 provides power to various components of the terminal 800. The power component 806 may include a power management system, one or more power supplies, and other components related to generating, managing, and distributing power for the terminal 800.

[0278] The multimedia component 808 includes a screen that provides an output interface between the terminal 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to detect touches, slides, and gestures on the touch panel. The touch sensors may detect not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide action. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. If the terminal 800 is in an operating mode such as a shooting mode or a video mode, the front camera and / or rear camera may receive external multimedia data. Each front camera and rear camera may have a fixed optical lens system or have a focal length and optical zoom capability.

[0279] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes one microphone (MIC). The terminal 800 operates in a manner such as calling, recording, and voice recognition. If present, the microphone is configured to receive external audio signals. The received audio signals are further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.

[0280] The I / O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to, a home button, volume buttons, a start button, and a lock button.

[0281] The sensor component 814 includes one or more sensors to provide the terminal 800 with state evaluations of each embodiment. For example, the sensor component 814 can detect the on / off state of the terminal 800 and the relative positions of components that are the monitor and keypad of the terminal 800. The sensor component 814 can also detect changes in the position of the terminal 800 or one of its components, whether the user is in contact with the terminal 800, the orientation or acceleration / deceleration of the terminal 800, and temperature changes of the terminal 800. The sensor component 814 may include proximity sensors configured to detect whether or not an object is present in the vicinity when there is no physical contact. The sensor component 814 may further include optical sensors, such as CMOS or CCD image sensors used in imaging applications. In some embodiments, the sensor component 814 may further include acceleration sensors, gyroscopes, magnetic sensors, pressure sensors, or temperature sensors.

[0282] The communication component 816 is configured to facilitate wired or wireless communication between the terminal 800 and other devices. The terminal 800 can access a wireless network based on a communication standard, such as WiFi, 4G, or 5G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT: registered trademark) technology, and other technologies.

[0283] In an exemplary embodiment, the terminal 800 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to execute the above information processing method.

[0284] In an exemplary embodiment, a non-transitory computer-readable storage medium containing instructions, such as the memory 804 containing instructions, is provided, and the above instructions can be executed by the processor 820 of the terminal 800 to generate the above information processing method. For example, the non-transitory computer-readable storage medium can be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

[0285] Unless there is a contradiction, each step in a certain embodiment or example can be implemented as an independent example, and each step can be arbitrarily combined. For example, Technical proposals that omit some steps in an embodiment or example can also be implemented as independent embodiments, and the order of steps in a given embodiment or example can be arbitrarily changed. Furthermore, selectable embodiments or examples in a given embodiment or example can be arbitrarily combined. Moreover, each embodiment or example can be arbitrarily combined. For example, some or all steps from different embodiments or examples can be arbitrarily combined, and one embodiment or example can be combined with a selectable embodiment or example of another embodiment or example.

[0286] A person skilled in the art, after considering the specification and practicing the invention disclosed herein, may readily conceive of other embodiments of the invention. This disclosure is intended to cover any variations, uses, or appropriate modifications of the invention, which may include common technical or conventional means in the art that are not disclosed herein, in accordance with the general principles of the invention. The specification and examples are to be considered merely illustrative, and the true scope and spirit of the invention are defined by the following claims.

[0287] The present invention is not limited to the exact configuration described above and shown in the drawings, and various modifications and changes can be made as long as they do not deviate from its scope. The scope of the present invention is limited only to the appended claims.

Claims

1. An information processing method performed by the sender, The steps include sending a Sidelink Positioning Protocol (SLPP) message, the SLPP message containing a transaction identifier (ID) for a first transaction, and the transaction ID being used to determine the initiator of the first transaction. An information processing method characterized by the following:

2. The aforementioned transaction ID is, Including a first ID for identifying the initiator of the first transaction, The information processing method according to feature 1.

3. The aforementioned first ID is, The source layer 2 ID of the aforementioned initiator, The destination Layer 2 ID of the aforementioned initiator, The application layer ID of the initiator, and The SLPP User Equipment (UE) ID of the aforementioned initiator, including at least one of the following: The information processing method according to feature 2.

4. The aforementioned transaction ID is, Further including a second ID for identifying the participants in the first transaction, The information processing method according to any one of claims 1 to 3.

5. The aforementioned participant is one UE, The second ID mentioned above is, The source layer 2 ID of the aforementioned participant, The destination Layer 2 ID of the aforementioned participant, The application layer ID of the aforementioned participant, and The SLPP UE ID of the aforementioned participant, including at least one of the following: The information processing method according to feature 4.

6. The aforementioned participant is the UE Group, The second ID mentioned above is, The group ID of the aforementioned UE group, The source layer 2 group cast ID of the aforementioned UE group, The destination layer 2 group cast ID of the aforementioned UE group, The application layer group ID of the aforementioned UE group, and The SLPP UE group ID of the aforementioned UE group includes at least one of the following: The information processing method according to feature 4.

7. The aforementioned participant is the UE Group, The second ID mentioned above is, The source layer 2 ID list of the aforementioned participants, The aforementioned participant's destination Layer 2 ID list, The list of application layer IDs of the aforementioned participants, and The list of SLPP UE IDs of the aforementioned participants includes at least one of the following: The information processing method according to feature 4.

8. The first transaction is created in broadcast mode, and the second ID includes at least one of the participant's source layer 2 broadcast ID, destination layer 2 broadcast ID, and SLPP broadcast ID. or The participant in the first transaction is one UE or a group of UEs, and the transaction ID includes the second ID. or The first transaction is created in broadcast mode, and the transaction ID does not include the second ID. The information processing method according to feature 4.

9. The transaction ID of the first transaction differs from the transaction ID of the second transaction, and the first and second transactions are concurrent transactions in the same session. The information processing method according to any one of claims 1 to 8.

10. Unlike the initiator of the second transaction, the initiator of the first transaction is and / or, The participants in the first transaction differ from the participants in the second transaction, and / or, The transaction ID includes a transaction number, and the transaction number of the first transaction is different from the transaction number of the second transaction. The information processing method according to feature 9.

11. The number of UEs involved in the first transaction is two or less, and the information processing method is The step further includes sending an SLPP message containing first instruction information, the first instruction information being used to terminate the first transaction. The SLPP message containing the first instruction information is: The last SLPP message involved in the first transaction, and The first transaction includes one of the last SLPP messages, which include the SLPP message body, The information processing method according to any one of claims 1 to 10.

12. The participants in the first transaction are a UE group, the sender is a UE within the UE group, and the information processing method is The step further includes sending an SLPP message containing a second instruction information, the second instruction information being used to indicate that the SLPP message containing the second instruction information is the last message from the sender in the first transaction or the last message containing the SLPP message body. The information processing method according to any one of claims 1 to 10.

13. The participants in the first transaction are a UE group, the sender is the initiator of the first transaction, and the information processing method is The process further includes sending an SLPP message containing a third instruction information in response to a decision to terminate the first transaction, wherein the third instruction information is used to terminate the first transaction. The information processing method according to any one of claims 1 to 10.

14. The participants in the first transaction are a group of UEs, the sender is any one of the UEs involved in the first transaction, and the information processing method further includes the step of sending an SLPP message containing a fourth instruction information, the fourth instruction information being used to indicate that the SLPP message containing the fourth instruction information is the last message from the sender in the first transaction or the last message containing the body of an SLPP message. The information processing method according to any one of claims 1 to 10.

15. An information processing method performed by the receiving side, The steps include receiving a Sidelink Positioning Protocol (SLPP) message, wherein the SLPP message contains a transaction identifier (ID) for a first transaction, and the transaction ID is used to determine the initiator of the first transaction. An information processing method characterized by the following:

16. The aforementioned transaction ID is, Including a first ID for identifying the initiator of the first transaction, The information processing method according to feature 15.

17. The aforementioned first ID is, The source layer 2 ID of the aforementioned initiator, The destination Layer 2 ID of the aforementioned initiator, The application layer ID of the initiator, and The SLPP User Equipment (UE) ID of the aforementioned initiator, including at least one of the following: The information processing method according to feature 16.

18. The aforementioned transaction ID is, Further including a second ID for identifying the participants in the first transaction, The information processing method according to any one of claims 15 to 17, characterized by the features described herein.

19. The aforementioned participant is one UE, and the second ID is, The source layer 2 ID of the aforementioned participant, The destination Layer 2 ID of the aforementioned participant, The application layer ID of the aforementioned participant, and The SLPP UE ID of the aforementioned participant, including at least one of the following: The information processing method according to feature 18.

20. The aforementioned participant is a UE group, and the second ID is, The group ID of the aforementioned UE group, The source layer 2 group cast ID of the aforementioned UE group, The destination layer 2 group cast ID of the aforementioned UE group, The application layer group ID of the aforementioned UE group, and The SLPP UE group ID of the aforementioned UE group includes at least one of the following: The information processing method according to feature 18.

21. The aforementioned participant is a UE group, and the second ID is, The source layer 2 ID list of the aforementioned participants, The aforementioned participant's destination Layer 2 ID list, The list of application layer IDs of the aforementioned participants, and The list of SLPP UE IDs of the aforementioned participants includes at least one of the following: The information processing method according to feature 18.

22. The first transaction is created in broadcast mode, and the second ID includes at least one of the participant's source layer 2 broadcast ID, destination layer 2 broadcast ID, and SLPP broadcast ID. or The participant in the first transaction is one UE or a group of UEs, and the transaction ID includes the second ID. or The first transaction is created in broadcast mode, and the transaction ID does not include the second ID. The information processing method according to feature 18.

23. The transaction ID of the first transaction differs from the transaction ID of the second transaction, and the first and second transactions are concurrent transactions in the same session. The information processing method according to any one of claims 15 to 22.

24. Unlike the initiator of the second transaction, the initiator of the first transaction is and / or, The participants in the first transaction differ from the participants in the second transaction, and / or, The transaction ID includes a transaction number, and the transaction number of the first transaction is different from the transaction number of the second transaction. The information processing method according to feature 23.

25. The number of UEs involved in the first transaction is two or less, and the information processing method is The process further includes the step of receiving an SLPP message containing first instruction information, wherein the first instruction information is used to terminate the first transaction. The SLPP message containing the first instruction information is: The last SLPP message involved in the first transaction, and The first transaction includes one of the last SLPP messages, which include the SLPP message body, The information processing method according to any one of claims 15 to 24.

26. The participant in the first transaction is the UE group, the recipient is the initiator of the first transaction, and the information processing method is The process further includes receiving an SLPP message sent by the sender, which includes a second instruction information, the second instruction information being used to indicate that the SLPP message including the second instruction information is the last message from the sender in the first transaction or the last message including the SLPP message body. The information processing method according to any one of claims 15 to 24.

27. The participants in the first transaction are a UE group, the receiving side is a UE within the UE group, and the information processing method is The process further includes the step of deciding to terminate the first transaction in response to the receipt of an SLPP message containing the third instruction information, or determining that the SLPP message containing the third instruction information is the last message containing the SLPP message body in the first transaction. The information processing method according to any one of claims 15 to 24.

28. The participant in the first transaction is the UE group, and the information processing method is The process further includes the step of deciding to terminate the first transaction in response to the receipt of an SLPP message containing a fourth instruction information, wherein the SLPP message containing the fourth instruction information is transmitted by all other UEs involved in the first transaction, excluding the receiving side. The information processing method according to any one of claims 15 to 24.

29. An information processing device, Includes a transmitting module configured to send Sidelink Positioning Protocol (SLPP) messages, wherein the SLPP messages include a transaction identifier (ID) of a first transaction, and the transaction ID is used to determine the initiator of the first transaction. An information processing device characterized by the following:

30. An information processing device, The system includes a receiving module configured to receive Sidelink Positioning Protocol (SLPP) messages, wherein the SLPP messages include a transaction identifier (ID) of a first transaction, and the transaction ID is used to determine the initiator of the first transaction. An information processing device characterized by the following:

31. A communication device, The system includes a processor, a transceiver, memory, and an executable program stored in the memory that can be executed by the processor, wherein when the processor executes the executable program, it performs the information processing method described in any one of claims 1 to 14, or the information processing method described in any one of claims 15 to 28. A communication device characterized by the following features.

32. A computer storage medium in which an executable program is stored, When the executable program is executed by a processor, the information processing method described in any one of claims 1 to 14, or the information processing method described in any one of claims 15 to 28, is realized. A computer storage medium characterized by the following features.

Images