Information processing method and apparatus, and communication device and storage medium

By using SLPP messages containing transaction IDs in the wireless communication system, the problem of unknown transaction initiator during positioning between UEs is solved, and the accuracy of positioning and information interaction are improved.

WO2024234208A1PCT designated stage expired Publication Date: 2024-11-21BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/094087
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In wireless communication systems, it is difficult to accurately distinguish the transaction initiator based on the side link positioning between user equipment (UE), resulting in a decrease in inaccuracy and positioning accuracy of information interaction during positioning.

Method used

By sending and receiving Side Link Positioning Protocol (SLPP) messages containing transaction IDs, the transaction ID is used to determine the initiator of the transaction, thereby improving the accuracy of information interaction and positioning accuracy.

Benefits of technology

It effectively solves the problem that multiple participants cannot distinguish the transaction initiator in the same transaction, and improves the accuracy of positioning and the accuracy of information interaction.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023094087_21112024_PF_FP_ABST
    Figure CN2023094087_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present disclosure are an information processing method and apparatus, and a communication device and a storage medium. The information processing method, which is executed by means of a sending end, comprises: sending a sidelink positioning protocol (SLPP) message, wherein the SLPP message comprises a transaction identifier (ID) of a first transaction, and the transaction ID is used for determining an initiator of the first transaction.
Need to check novelty before this filing date? Find Prior Art

Description

Information processing method, device, communication equipment and storage medium Technical Field

[0001] The present disclosure relates to the field of wireless communication technologies but is not limited to the field of wireless communication technologies, and in particular to an information processing method, apparatus, communication device, and storage medium. Background Art

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

[0003] Ranging usually involves only two UEs, that is, ranging is performed between two UEs, but absolute positioning and relative positioning may involve multiple UEs to participate in positioning to improve the accuracy of absolute positioning and relative positioning.

[0004] Summary of the Invention

[0005] Embodiments of the present disclosure provide an information processing method, apparatus, communication device, and storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by a sending end and includes:

[0007] A Sidelink Positioning Protocol (SLPP) message is sent, wherein the SLPP message includes a transaction identification (ID) of a first transaction, and the transaction ID is used to determine an initiator of the first transaction.

[0008] According to a second aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by a receiving end, and the method includes:

[0009] Receive an SLPP message; wherein the SLPP message includes a transaction ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0010] According to a third aspect of an embodiment of the present disclosure, there is provided an information processing device, the device comprising:

[0011] The sending module is configured to send an SLPP message; wherein the SLPP message includes a transaction ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0012] According to a fourth aspect of an embodiment of the present disclosure, there is provided an information processing device, the device comprising:

[0013] The receiving module is configured to receive an SLPP message; wherein the SLPP message includes a transaction ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0014] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided, comprising a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being run by the processor, wherein when the processor runs the executable program, the information processing method provided in the first or second aspect described above is executed.

[0015] According to a sixth aspect of an embodiment of the present disclosure, a communication system is provided, comprising:

[0016] A sending end, configured to execute the information processing method provided by the first aspect;

[0017] The receiving end is configured to execute the information processing method provided by the second aspect.

[0018] According to the seventh aspect of the embodiments of the present disclosure, a computer storage medium is provided, which stores an executable program; after the executable program is executed by a processor, it can implement the information processing method provided by the first aspect or the second aspect mentioned above.

[0019] The technical solution provided by the embodiments of the present disclosure includes a SLPP message that includes a transaction ID for a first transaction. The transaction ID is used to identify the initiator of the first transaction. This allows the transaction ID included in the SLPP message to be used to identify the transaction initiator, thereby reducing the situation where multiple participants in the same transaction are unable to distinguish the transaction initiator, or where different participants in the same transaction determine different initiators. This improves the accuracy of information exchange during the transaction process. Because the transaction initiator can be more accurately distinguished based on the transaction ID, positioning using SLPP messages carrying the transaction ID can improve positioning accuracy.

[0020] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0022] FIG1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment;

[0023] FIG2 is a schematic structural diagram of a positioning framework according to an exemplary embodiment;

[0024] FIG3 is a flow chart showing an information processing method according to an exemplary embodiment;

[0025] FIG4 is a flow chart showing an information processing method according to an exemplary embodiment;

[0026] FIG5 is a flow chart showing an information processing method according to an exemplary embodiment;

[0027] FIG6 is a flow chart showing an information processing method according to an exemplary embodiment;

[0028] FIG7 is a flow chart showing an information processing method according to an exemplary embodiment;

[0029] FIG8 is a flow chart showing an information processing method according to an exemplary embodiment;

[0030] FIG9 is a flow chart showing an information processing method according to an exemplary embodiment;

[0031] FIG10 is a flow chart showing an information processing method according to an exemplary embodiment;

[0032] FIG11 is a flow chart showing an information processing method according to an exemplary embodiment;

[0033] FIG12 is a flow chart showing an information processing method according to an exemplary embodiment;

[0034] FIG13 is a schematic structural diagram of an information processing device according to an exemplary embodiment;

[0035] FIG14 is a schematic structural diagram of an information processing device according to an exemplary embodiment;

[0036] Fig. 15 is a schematic structural diagram of a terminal according to an exemplary embodiment. DETAILED DESCRIPTION

[0037] Exemplary embodiments are described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible implementations consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with certain aspects of the present invention.

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

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

[0040] Please refer to Figure 1, which shows a schematic diagram of the structure of a wireless communication system provided by an embodiment of the present disclosure. As shown in Figure 1, the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: a plurality of user equipment 11 and a plurality of access network equipment 12.

[0041] Among them, the user equipment 11 can be a device that provides voice and / or data connectivity to the user. The user equipment 11 can communicate with one or more core networks via a radio access network (RAN). The user equipment 11 can be an Internet of Things user equipment, such as a sensor device, a mobile phone (or called a "cellular" phone) and a computer with an Internet of Things user equipment. For example, it can be a fixed, portable, pocket-sized, handheld, computer-built-in or vehicle-mounted device. For example, a station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote user equipment (remote terminal), an access terminal, a user terminal, a user agent, a user device, or user equipment. Alternatively, the user equipment 11 can also be a wearable device, a virtual reality (VR) device, an augmented reality (AR) device or a VR / AR hybrid head-mounted device. Alternatively, the user equipment 11 can also be a device of an unmanned aerial vehicle. Alternatively, the user device 11 may be an onboard device, such as a driving computer with wireless communication capabilities, or a wireless user device connected to an external driving computer. Alternatively, the user device 11 may be a roadside device, such as a streetlight, traffic light, or other roadside device with wireless communication capabilities.

[0042] The access network device 12 may be a device in a wireless communication system for communicating with the user equipment 11, and may be a base station, an access point, or a network device, or may refer to a device in the access network that communicates with the wireless terminal through one or more sectors on the air interface. The network device may be used to convert received air frames into IP packets and serve as a router between the wireless terminal and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) network. The network device may also coordinate the attribute management of the air interface. The wireless communication system may be a fourth generation mobile communication technology (4G) system, also known as a long term evolution (LTE) system; or the wireless communication system may be a 5G system, also known as a new radio (NR) system or a 5G NR system. Alternatively, the wireless communication system may be the next generation system of the 5G system. The access network in the 5G system may be called NG-RAN (New Generation-Radio Access Network).

[0043] Among them, the access network device 12 can be an evolved access device (eNB) adopted in a 4G system. Alternatively, the access network device 12 can also be an access device (gNB) adopting a centralized distributed architecture in a 5G system. When the access network device 12 adopts a centralized distributed architecture, it usually includes a centralized unit (CU) and at least two distributed units (DU). The centralized unit is provided with a protocol stack of a packet data convergence protocol (PDCP) layer, a radio link layer control protocol (RLC) layer, and a media access control (MAC) layer; the distributed unit is provided with a physical (PHY) layer protocol stack. The embodiment of the present disclosure does not limit the specific implementation method of the access network device 12.

[0044] A wireless connection can be established between the access network device 12 and the user equipment 11 via a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new air interface; or, the wireless air interface can also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.

[0045] In some embodiments, E2E (End to End) or D2D (Device to Device) connections may be established between user devices 11. For example, in vehicle-to-everything (V2X) communication scenarios such as V2V (vehicle to vehicle), V2I (vehicle to Infrastructure), and V2P (vehicle to pedestrian).

[0046] In some embodiments, the wireless communication system may further include a core network device 13. A plurality of access network devices 12 are connected to the core network device 13 respectively.

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

[0048] 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), network storage function (NRF) entity, etc.

[0049] The PCF, SMF, UPF, etc. in the embodiments of the present disclosure can be implemented by a single physical device or by multiple physical devices. It is understood that the PCF, SMF, etc. in the embodiments of the present disclosure can be a logical functional module within a physical device or a logical functional module composed of multiple physical devices, and the embodiments of the present disclosure are not limited thereto.

[0050] To facilitate understanding by those skilled in the art, the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art will understand that the multiple embodiments provided in the embodiments of the present disclosure can be implemented individually, or can be implemented together with the methods of other embodiments in the embodiments of the present disclosure, or can be implemented together with some methods in other related technologies individually or in combination; the embodiments of the present disclosure do not limit this.

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

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

[0053] Positioning based on the sidelink (SL) between UEs includes absolute positioning, relative positioning, and ranging. The sidelink can also be called a linear link. Absolute positioning is to determine the absolute coordinates of the UE, relative positioning is to determine the coordinates of the UE relative to a reference point, and ranging is to determine the distance and / or angle of the UE relative to a reference point. Ranging usually only involves ranging between two UEs, but absolute positioning and relative positioning may involve multiple UEs to participate in positioning.

[0054] In an embodiment of the present disclosure, as shown in FIG2 , taking positioning based on downlink time difference of arrival (DL-TDOA) as an example, the UE can determine the specific position of the UE relative to multiple road side units (RSUs) and sidelink positioning reference signals (SL PRS).

[0055] In addition to DL-TDOA-based positioning, the positioning solution can also use one or more of the following information to achieve positioning: uplink time difference of arrival (UL-TDOA), multiple round trip time (Multiple RTT), angle of arrival (AOA) or angle of departure (AOD), carrier phase positioning, etc.

[0056] If the positioning result is not converted into absolute position coordinates based on the absolute position information of the Global Positioning System (GPS) of the RSU, then the positioning result is relative positioning. Otherwise, the positioning result is absolute positioning.

[0057] The UE being located is the target UE, and the other UEs that support the positioning of the target UE are anchor UEs. If positioning involves only two UEs, they are each other's anchor UEs.

[0058] Anchor UEs come in different types, including, for example, RSU-type anchor UEs. RSU-type anchor UEs are a type of infrastructure that can collaborate with other RSUs to provide positioning services. For example, a standard UE can also serve as an anchor UE, but it is difficult for a standard UE to assist in providing positioning services with other UEs. Furthermore, some anchor UEs have location information, such as GPS, that can assist other UEs in achieving absolute positioning; others may not.

[0059] The protocols for exchanging positioning messages between two UEs include: Sidelink Positioning Protocol (or sidelink LPP, SLPP) or Ranging and sidelink positioning protocol (RSPP).

[0060] For LPP (LTE (Long Term Evolution) Positioning Protocol), an LPP session is created for a positioning request. A positioning request can be, for example, a mobile terminal positioning request (MT-LR), a mobile originated positioning request (MO-LR), or a network triggered positioning request (NI-LR). An LPP session involves only two nodes, for example, a UE and a location management function (LMF). Multiple transactions can be created within a session, each transaction for an LPP operation. The LPP message must carry a transaction ID, which indicates that the initiator (or "initiator") is a server-type node, or the transaction ID indicates that the initiator is a client-type node.

[0061] For SLPP sessions, multiple UEs may be involved in a session, and the client and server modes used in LPP may no longer apply. Therefore, the transaction ID cannot simply use server or client to distinguish the initiator. In addition to the initiator, participants also need to be considered.

[0062] In addition, for LPP transactions, since only two UEs are involved, the transaction is considered complete when one of the UEs sends an end transaction indication. However, in SLPP transactions, where multiple UEs may participate in a transaction, how to determine the end of the transaction needs to be considered.

[0063] Figure 3 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 3, the method is executed by the sending end and may include the following steps:

[0064] Step 301: Send 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.

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

[0066] In some examples, the sending end may be the initiator of the first transaction, or the sending end may be a participant in the first transaction; wherein the participant in the first transaction is different from the initiator of the first transaction.

[0067] In some examples, the initiator of the first transaction may be the initiator of the session in which the first transaction is located, or the initiator of the first transaction may be a participant in the session in which the first transaction is located; the initiator of the first transaction in the session is different from the participant in the session in which the first transaction is located.

[0068] In some examples, the initiator of the first transaction may be an anchor UE, and the participant of the first transaction may be a target UE; or, the initiator of the first transaction may be a target UE, and the participant of the first transaction may be an anchor UE.

[0069] For example, the anchor UE may be: an RSU-type anchor UE and / or a UE of a type different from the RSU type.

[0070] In some examples, the participant in the first transaction other than the initiator may be a UE or a UE group, wherein the UE group includes multiple UEs.

[0071] In this embodiment, the transaction ID of the first transaction is used to identify the first transaction and to determine the initiator of the first transaction.

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

[0073] In some examples, the transaction ID of the first transaction may include indication information used to determine the initiator of the first transaction.

[0074] Exemplarily, the indication information may be a UE type (type), and the UE type may include: a server type, or a client type.

[0075] For example, when the first transaction involves two UEs, the UE ID of the initiator of the first transaction can be indicated by using the UE type.

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

[0077] If the same transaction involves two UEs, the two different UEs can be distinguished by using UE type. In this way, the initiator of the same transaction can be distinguished by UE type, which can improve compatibility with related technologies.

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

[0079] In some examples, in step 301 above, the sending end sends an SLPP message carrying the transaction ID of the first transaction to the receiving end.

[0080] For example, the sending end is the initiator of the first transaction, and the receiving end includes: participants of the first transaction other than the initiator.

[0081] For example, the sending end is a participant in the first transaction, and the receiving end includes: an initiator of the first transaction who is different from the participant.

[0082] For example, the sending end is the first participant among multiple participants of the first transaction, and the receiving end may include: other participants of the first transaction different from the first participant.

[0083] In some examples, the first transaction may be used for a SLPP operation. For example, the SLPP operation may include at least one of the following: capability exchange, assistance data transmission, and location information transmission.

[0084] In some examples, different SLPP messages within the same transaction use the same transaction number.

[0085] In some examples, the 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 carrying transaction content.

[0086] In some examples, the SLPP message carries a transaction ID of the first transaction, which can be used to trigger creation of the first transaction.

[0087] Exemplarily, the SLPP message is the first SLPP message carrying 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 be a transaction creation request message of the first transaction.

[0088] For example, the SLPP message received by the receiving end is the first SLPP message carrying the transaction ID of the first transaction, triggering the establishment of the first transaction. In this case, the SLPP message may be a transaction creation request message of the first transaction.

[0089] In some examples, when the SLPP message includes an SLPP message body, the SLPP message carries a transaction ID. The SLPP message body may be, for example, slpp-MessageBody.

[0090] The information processing method provided by the embodiments of the present disclosure sends an SLPP message that includes a transaction ID for a first transaction. The transaction ID is used to identify the initiator of the first transaction. This allows the transaction ID included in the SLPP message to be used to identify the transaction initiator, thereby reducing the situation where multiple participants in the same transaction are unable to distinguish the transaction initiator, or where different participants in the same transaction determine different initiators. This improves the accuracy of information exchange during the transaction process. Because the transaction initiator can be more accurately distinguished based on the transaction ID, positioning using an SLPP message carrying the transaction ID can improve positioning accuracy.

[0091] In some embodiments, the transaction ID may include:

[0092] The first ID is used to indicate the initiator of the first transaction.

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

[0094] The UE ID can be used to identify the UE. For example, different UEs involved in the same transaction may have different UE IDs.

[0095] In other examples, the same UE has different UE IDs in different transactions.

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

[0097] For example, the substring may include one character, or the substring may include a plurality of consecutively distributed characters.

[0098] For example, the transaction ID string includes M characters, and the first ID can be a string consisting of the first N characters of the M characters, or the first ID can be a string consisting of the last N characters of the M characters, or the first ID can include N characters distributed continuously starting from any middle position of the M characters, where N is a positive integer greater than or equal to 1 and less than M.

[0099] In this embodiment, the substring at the first designated position in the transaction ID string constitutes the first ID string, which can facilitate rapid decoding at the subsequent receiving end, thereby quickly determining the initiator of the first transaction.

[0100] In this embodiment, since the transaction ID includes the first ID, the first ID is used to indicate the initiator of the first transaction. In this way, the receiving end of the SLPP message can more accurately distinguish the transaction initiator, and different participants in the first transaction can determine the unique initiator of the first transaction based on the first ID, which is conducive to improving the accuracy of information exchange in the same transaction.

[0101] In some embodiments, the first ID may include at least one of the following:

[0102] Source Layer 2 ID of the initiator;

[0103] Destination Layer 2 ID of the initiator;

[0104] The initiator's application layer ID (Application layer ID);

[0105] SLPP UE ID of the initiator.

[0106] In some embodiments, the transaction ID may also include:

[0107] The second ID is used to indicate the participant of the first transaction.

[0108] In some examples, the second ID may include a UE ID of a party to the first transaction.

[0109] The UE ID can be used to identify the UE. For example, different UEs involved in the same transaction may have different UE IDs.

[0110] In other examples, the same UE has different UE IDs in different transactions.

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

[0112] For example, the substring may include one character, or the substring may include a plurality of consecutively distributed characters.

[0113] Exemplarily, different second IDs indicate different participants in the first transaction, and different second IDs correspond to substrings at different positions in the character string of the transaction ID.

[0114] Exemplarily, when the first ID is a substring at a first designated position in a character string of the transaction ID, the second designated position is different from the first designated position.

[0115] In this embodiment, the substring at the second designated position in the transaction ID string constitutes the second ID string, which can facilitate rapid decoding at the subsequent receiving end, thereby quickly determining the participants of the first transaction.

[0116] In this embodiment, since the transaction ID includes a second ID, the second ID is used to indicate a participant in the first transaction. This allows the receiving end of the SLPP message, upon receiving the SLPP message carrying the transaction ID of the first transaction, to determine whether it is a participant in the first transaction based on the second ID included in the transaction ID of the first transaction. For example, during positioning using SLPP messages, some UEs have absolute location information, while others do not. If a transaction participant that requires absolute positioning requires absolute positioning, the second ID can be used to specify a UE with absolute location information as a participant.

[0117] In some embodiments, the participant in the first transaction is a UE, and the second ID may include at least one of the following:

[0118] The source layer 2 ID of the participant;

[0119] The destination layer 2 ID of the participant;

[0120] The application layer ID of the participant;

[0121] SLPP user equipment UE ID of the participant.

[0122] In some embodiments, the participant is a UE group, and the second ID may include at least one of the following:

[0123] The group ID of the UE group;

[0124] Source Layer 2 groupcast ID of the UE group;

[0125] Destination Layer 2 groupcast ID of the UE group;

[0126] Application Layer group ID of the UE group;

[0127] SLPP UE group ID (SLPP group ID) of the UE group.

[0128] In some examples, at least one of the source layer 2 multicast ID, destination layer 2 multicast ID, and application layer group ID of the UE group can be provided by the application layer of the session initiator and provided to the session participants through a message for session establishment.

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

[0130] In some embodiments, the participants in the first transaction are a UE group, and the second ID includes at least one of the following:

[0131] List of source layer 2 IDs of the participants;

[0132] List of destination layer 2 IDs of the participants;

[0133] A list of application layer IDs of the participants;

[0134] List of SLPP UE IDs of participating parties.

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

[0136] In this embodiment, the first transaction is created in broadcast mode, resulting in multiple SLPP message receivers. Upon receiving an SLPP message carrying the transaction ID of the first transaction, if the transaction ID of the first transaction carries the second ID, these receivers can determine whether they are participants in the first transaction based on the second ID. If a receiver determines that it is a participant in the first transaction, it participates in the first transaction. If a receiver determines that it is not a participant in the first transaction, it can ignore the SLPP message.

[0137] For example, if one or more nodes around the target UE have their own location information, these nodes can serve as anchor UEs. Therefore, by using the second ID carried in the transaction ID of the first transaction to indicate that the anchor UE is a participant in the first transaction, the efficiency and accuracy of positioning the target UE can be improved.

[0138] In some embodiments, the first transaction is created in broadcast mode, and the second ID carried by the transaction ID of the first transaction includes: at least one of the source end layer 2 broadcast ID, the destination end layer 2 broadcast ID and the SLPP broadcast ID of the participant.

[0139] In some examples, at least one of the source Layer 2 broadcast ID and the destination Layer 2 ID of the participant can be provided by the application layer of the initiator of the session and provided to the participant of the session through a message used for session establishment. The SLPP broadcast ID can be created by the initiator of the session and provided to the participant of the session through a message used for session establishment.

[0140] In some embodiments, the participants in the first transaction are a UE or a UE group, and the transaction ID includes the second ID.

[0141] Compared to a single UE, a UE group can include one or more UEs. Transactions based on UE groups can facilitate multi-party transactions and / or positioning when a UE group includes multiple UEs. Using a UE group to locate the initiator can improve positioning accuracy, while having the initiator locate the UE group can improve positioning efficiency.

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

[0143] In this embodiment, the first transaction is created in broadcast mode, and the transaction ID of the first transaction may include the first ID but not the second ID. In this way, when the receiving end is not the initiator of the first transaction, it can determine that it is a participant in the first transaction.

[0144] 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.

[0145] In some examples, the transaction ID of the first transaction may be used to identify a third transaction within the first session where the first transaction is located, where the third transaction is not concurrent with the first transaction.

[0146] For example, the third transaction may be a transaction created before the first transaction is created within the first session, or the third transaction may be a transaction created after the first transaction is completed within the first session.

[0147] In some embodiments, the transaction ID of the first transaction is different from the transaction ID of the second transaction, indicating at least one of the following:

[0148] The initiator of the first transaction is different from the initiator of the second transaction;

[0149] The parties involved in the first transaction are different from the parties involved in the second transaction;

[0150] 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.

[0151] In some examples, different SLPP messages within the same transaction use the same transaction number.

[0152] In some embodiments, the method may further include:

[0153] Send an SLPP message carrying indication information;

[0154] The indication information is used to indicate one of the following:

[0155] Ending the first transaction;

[0156] The SLPP message is the last message sent by the sender in the first transaction or the last message carrying the SLPP message body.

[0157] In some examples, when the number of UEs involved in the first transaction is less than or equal to two, the initiator or participant of the first transaction may send an SLPP message carrying indication information for indicating the end of the first transaction; or, when the number of UEs involved in the first transaction is greater than two, the initiator of the first transaction may send an SLPP message carrying indication information for indicating the end of the first transaction.

[0158] For example, the SLPP message carrying the indication information may be the last SLPP message carrying the SLPP message body of the first transaction.

[0159] In this example, after receiving the SLPP message carrying the indication information and confirming the end of the first transaction, or confirming that the SLPP message is the last SLPP message carrying the SLPP message body of the first transaction, the receiving end no longer expects to receive any SLPP messages related to the first transaction, or any SLPP messages carrying the SLPP message body related to the first transaction. In other words, when the receiving end receives any SLPP message for a transaction with the same transaction ID as the first transaction, or any SLPP message carrying the SLPP message body for a transaction with the same transaction ID as the first transaction, it will treat the SLPP message as an SLPP message for a new transaction.

[0160] In some examples, when the number of UEs involved in the first transaction is greater than two, the participants in the first transaction may send an SLPP message carrying indication information; the indication information is used to indicate that the SLPP message is the last message of the sender in the first transaction or the last message carrying the SLPP message body.

[0161] In some embodiments, the number of UEs involved in the first transaction is less than or equal to two, and the method further includes:

[0162] Sending an SLPP message carrying first indication information; wherein the first indication information is used to end the first transaction;

[0163] The SLPP message carrying the first indication information includes one of the following:

[0164] The last SLPP message involved in the first transaction;

[0165] The first transaction involves the last SLPP message carrying the SLPP message body.

[0166] In some embodiments, the participants in the first transaction are a UE group, the sender is a UE in the UE group, and the method further includes:

[0167] Sending an SLPP message carrying second indication information; wherein the second indication information is used to indicate that the SLPP message carrying the second indication information is: the last message of the sending end in the first transaction or the last message carrying the SLPP message body.

[0168] In some embodiments, the participants in the first transaction are a UE group, the sender is an initiator of the first transaction, and the method further includes:

[0169] In response to determining to end the first transaction, sending an SLPP message carrying third indication information; wherein the third indication information is used to end the first transaction.

[0170] In some embodiments, the participants in the first transaction are a UE group, the sender is any UE involved in the first transaction, and the method further includes:

[0171] Send an SLPP message carrying fourth indication information, wherein the fourth indication information is used to indicate that the SLPP message carrying the fourth indication information is: the last message of the sending end in the first transaction or the last message carrying the SLPP message body.

[0172] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0173] Next, the information processing method performed by the receiving end is described, which is similar to the description of the information processing method performed by the sending end mentioned above; and, for technical details not disclosed in the embodiment of the information processing method performed by the receiving end, please refer to the description of the example of the information processing method performed by the sending end, and no detailed description is given here.

[0174] FIG4 is a flow chart of an information processing method according to an exemplary embodiment. As shown in FIG4 , the method is executed by a receiving end and may include the following steps:

[0175] Step 401: 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.

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

[0177] In some examples, in step 401 above, the receiving end receives an SLPP message sent by the sending end that carries the transaction ID of the first transaction.

[0178] In some examples, when the sending end is the initiator of the first transaction, the receiving end is a participant of the first transaction; or, when the sending end is a participant of the first transaction, the receiving end may include: the initiator of the first transaction and / or the participant of the first transaction who is different from the sending end.

[0179] The participant of the first transaction is different from the initiator of the first transaction.

[0180] In this embodiment, the transaction ID of the first transaction is used to identify the first transaction and to determine the initiator of the first transaction.

[0181] In some examples, the description of the transaction ID and other contents can refer to the description of the transaction ID and other contents in step 301 of Figure 3, which will not be repeated here.

[0182] The information processing method provided by the embodiments of the present disclosure receives an SLPP message including a transaction ID for a first transaction. The transaction ID is used to identify the initiator of the first transaction. This allows the receiving end to use the transaction ID included in the SLPP message to determine the initiator of the transaction. This reduces the situation where multiple participants in the same transaction are unable to distinguish the transaction initiator, or where different participants in the same transaction determine different initiators, thereby improving the accuracy of information exchange during the transaction process. Because the transaction initiator can be more accurately distinguished based on the transaction ID, positioning using SLPP messages carrying the transaction ID can improve positioning accuracy.

[0183] In some embodiments, the transaction ID includes:

[0184] The first ID is used to indicate the initiator of the first transaction.

[0185] In some embodiments, the first ID includes at least one of the following:

[0186] The source layer 2 ID of the initiator;

[0187] Destination Layer 2 ID of the initiator;

[0188] The application layer ID of the initiator;

[0189] The SLPP UE ID of the initiator.

[0190] In some embodiments, the transaction ID further includes:

[0191] The second ID is used to indicate the participant of the first transaction.

[0192] In some embodiments, the participant is a UE, and the second ID includes at least one of the following:

[0193] The source layer 2 ID of the participant;

[0194] The destination layer 2 ID of the participant;

[0195] The application layer ID of the participant;

[0196] The SLPP user equipment UE ID of the participant.

[0197] In some embodiments, the participant is a UE group, and the second ID includes at least one of the following:

[0198] The group ID of the UE group;

[0199] The source layer 2 multicast ID of the UE group;

[0200] Destination layer 2 multicast ID of the UE group;

[0201] The application layer group ID of the UE group;

[0202] The SLPP UE group ID of the UE group.

[0203] In some embodiments, the participant is a UE group, and the second ID includes at least one of the following:

[0204] List of source layer 2 IDs of the participants;

[0205] The destination layer 2 ID list of the participants;

[0206] A list of application layer IDs of the participants;

[0207] List of SLPP UE IDs of the participants.

[0208] In some embodiments, the first transaction is created in broadcast mode, and the second ID includes: at least one of a source end layer 2 broadcast ID, a destination end layer 2 broadcast ID, and an SLPP broadcast ID of the participant;

[0209] Alternatively, the participant in the first transaction is a UE or a UE group, and the transaction ID includes the second ID;

[0210] Alternatively, the first transaction is created in a broadcast mode, and the transaction ID does not include the second ID.

[0211] 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.

[0212] In some embodiments, the initiator of the first transaction is different from the initiator of the second transaction;

[0213] and / or, the parties involved in the first transaction are different from the parties involved in the second transaction;

[0214] 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.

[0215] In some embodiments, the number of UEs involved in the first transaction is less than or equal to two, and the method further includes:

[0216] receiving an SLPP message carrying first indication information, wherein the first indication information is used to end the first transaction;

[0217] The SLPP message carrying the first indication information includes one of the following:

[0218] The last SLPP message involved in the first transaction;

[0219] The first transaction involves the last SLPP message carrying the SLPP message body.

[0220] In some embodiments, the participants in the first transaction are a UE group, the receiving end is an initiator of the first transaction, and the method further includes:

[0221] Receive an SLPP message carrying second indication information sent by a sending end; wherein the second indication information is used to indicate that the SLPP message carrying the second indication information is: the last message of the sending end in the first transaction or the last message carrying an SLPP message body.

[0222] In some embodiments, the participants in the first transaction are a UE group, the receiving end is a UE in the UE group, and the method further includes:

[0223] In response to receiving the SLPP message carrying the third indication information, it is determined that the first transaction is ended or that the SLPP message carrying the third indication information is the last message carrying the SLPP message body of the first transaction.

[0224] In some embodiments, the participants in the first transaction are a UE group, and the method further includes:

[0225] In response to receiving an SLPP message carrying fourth indication information, it is determined to end the first transaction; wherein the SLPP message carrying the fourth indication information is sent by all other UEs involved in the first transaction except the receiving end.

[0226] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0227] Figure 5 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 5, the method is executed by the sending end, and the method may include the following steps:

[0228] Step 501: Send an SLPP message carrying first indication information; wherein the first indication information is used to end a first transaction; and the number of UEs involved in the first transaction is less than or equal to two.

[0229] In some examples, the SLPP message carrying the first indication information includes one of the following: the last SLPP message involved in the first transaction; the last SLPP message involved in the first transaction and carrying the SLPP message body.

[0230] For example, when the first transaction involves two UEs and the SLPP message that the sender needs to send is the last SLPP message in the first transaction, or the last message carrying the SLPP message body in the first transaction, the sender can add first indication information in the SLPP message to indicate the end of the first transaction.

[0231] For example, when the first transaction involves two UEs and the sender is the initiator of the first transaction, the sender can send an SLPP message carrying the first indication information so that the receiving end (here, the receiving end is a participant in the first transaction) can know that the first transaction has ended when it receives the first SLPP message.

[0232] In some examples, the first indication information may be carried in a message header or a message body of the SLPP message.

[0233] For example, when the first indication information and the transaction content are both carried in the message body of the SLPP message, the message body further includes a distinguishing mark, which is used to distinguish the first indication information from the transaction content in the message body.

[0234] In some examples, the first indication information may be a transaction end indication.

[0235] For example, the transaction end indication is an end tag, which may be "end session"; or the transaction end indication is a bit sequence indicating the end.

[0236] When the SLPP message of the first transaction carries a message body, if the SLPP message is the last SLPP message carrying a message body, the SLPP message can carry a transaction end indication. There is no need to construct a special message to carry the transaction end indication in addition to the SLPP message carrying the message body, so that the SLPP message is reused and the implementation is simple.

[0237] In some examples, the transaction end indication may be carried in a SLPP message that does not include an SLPP message body. In this example, the SLPP message carrying the first indication information may be understood as a dedicated SLPP message or a specific SLPP message for indicating the transaction end.

[0238] For example, after the last SLPP message carrying the message body of the first transaction is transmitted, an SLPP message carrying a transaction end indication is sent.

[0239] In an embodiment of the present disclosure, the number of UEs involved in the first transaction is less than or equal to two; the sending end can send an SLPP message carrying first indication information to end the first transaction, so that the receiving end can directly end the first transaction according to the first indication information.

[0240] Figure 6 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 6, the method is executed by the sending end and may include the following steps:

[0241] Step 601: Send an SLPP message carrying second indication information; wherein the second indication information is used to indicate that the SLPP message carrying the second indication information is: the last message of the sending end in the first transaction or the last message carrying the SLPP message body; the participant of the first transaction is a UE group, and the sending end is a UE in the UE group.

[0242] In some examples, the second indication information may be carried in a message header or a message body of the SLPP message.

[0243] For example, when the second indication information and the transaction content are both carried in the message body of the SLPP message, the message body further includes a distinguishing mark, which is used to distinguish the second indication information from the transaction content in the message body.

[0244] In some examples, the second indication information may be a transaction end indication.

[0245] For example, the transaction end indication is an end tag, which may be "end session"; or the transaction end indication is a bit sequence indicating the end.

[0246] The SLPP message sent by the sender in the first transaction can carry a transaction end indication when carrying a message body. In this way, there is no need to construct a special message to carry a transaction end indication in addition to the SLPP message carrying the message body, so that the SLPP message is reused and implemented simply.

[0247] In some examples, the transaction end indication may be carried in a SLPP message that does not include an SLPP message body. In this example, the SLPP message carrying the second indication information may be understood as a dedicated SLPP message or a specific SLPP message.

[0248] For example, after the transmission of the last SLPP message carrying the message body sent in the first transaction is completed, the sending end sends an SLPP message carrying the transaction end indication.

[0249] In some examples, the sending end may send the SLPP message carrying the second indication information in a unicast, multicast, or broadcast manner.

[0250] In this embodiment, the sending end sends an SLPP message carrying the second indication information. If the receiving end is the initiator of the first transaction, the receiving end can, based on the second indication information carried in the SLPP message, confirm that the SLPP message is the last message sent by the sending end within the first transaction, or the last message carrying the SLPP message body. This helps improve the accuracy of determining the end of a transaction between the initiator and multiple participants in the same transaction.

[0251] In some embodiments, the method further comprises:

[0252] Receive an SLPP message carrying third indication information; wherein the third indication information is used to end the first transaction; wherein the SLPP message carrying the third indication information is an SLPP message sent by the initiator of the first transaction.

[0253] In some embodiments, the method further comprises:

[0254] According to the SLPP message carrying the third indication information sent by the initiator of the first transaction, the end of the first transaction is confirmed, or the SLPP message carrying the third indication information is confirmed to be the last message carrying the SLPP message body of the first transaction.

[0255] In this embodiment, after the participants in the first transaction confirm, based on the third indication information, that the first transaction has ended, or confirm that the SLPP message carrying the third indication information is the last message carrying an SLPP message body in the first transaction, they no longer expect to receive any SLPP messages related to the first transaction, or any SLPP messages carrying an SLPP message body related to the first transaction. In other words, upon receiving any SLPP message for a transaction with the same transaction ID as the first transaction, or any SLPP message carrying an SLPP message body for a transaction with the same transaction ID as the first transaction, they will treat the SLPP message as an SLPP message for a new transaction.

[0256] In this embodiment, since the same transaction may involve multiple different participants, by receiving the SLPP message carrying the third indication information sent by the initiator of the first transaction, the participants of the first transaction can know the end of the first transaction based on the third indication information, which is conducive to improving the accuracy of the initiator of the same transaction and multiple participants in determining the end of the transaction.

[0257] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0258] Figure 7 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 7, the method is executed by the sending end and may include the following steps:

[0259] Step 701: In response to determining to end the first transaction, send an SLPP message carrying third indication information; wherein the third indication information is used to end the first transaction; the sending end is the initiator of the first transaction; and the participants of the first transaction are the UE group.

[0260] In some examples, the third indication information may be a transaction end indication.

[0261] In some examples, determining to end the first transaction may include determining that the first transaction needs to be ended.

[0262] In some examples, the initiator of the first transaction may send an SLPP message carrying third indication information, so that the receiving end knows that the first transaction ends after receiving the SLPP message.

[0263] For example, the initiator of the first transaction determines to end the first transaction based on receiving the SLPP message carrying the second indication information sent by all participants of the first transaction.

[0264] In some examples, the initiator of the first transaction autonomously determines to terminate the first transaction. In this example, the initiator of the first transaction can proactively terminate the first transaction, that is, it can directly determine to accept the first transaction without relying on the SLPP message carrying the second indication information sent by the participants of the first transaction.

[0265] In some examples, the third indication information may be carried in the message header or message body of the SLPP message.

[0266] For example, when the third indication information and the transaction content are both carried in the message body of the SLPP message, the message body further includes a distinguishing mark, which is used to distinguish the third indication information from the transaction content in the message body.

[0267] In some examples, the third indication information may be a transaction end indication.

[0268] For example, the transaction end indication is an end tag, which may be "end session"; or the transaction end indication is a bit sequence indicating the end.

[0269] The SLPP message sent by the sender in the first transaction can carry a transaction end indication when carrying a message body. In this way, there is no need to construct a special message to carry a transaction end indication in addition to the SLPP message carrying the message body, so that the SLPP message is reused and implemented simply.

[0270] In some examples, the transaction end indication may be carried in a SLPP message that does not include an SLPP message body. In this example, the SLPP message carrying the third indication information may be understood as a dedicated SLPP message or a specific SLPP message.

[0271] For example, after the transmission of the last SLPP message carrying the message body sent in the first transaction is completed, the sending end sends an SLPP message carrying the transaction end indication.

[0272] In some examples, the sending end may send the SLPP message carrying the third indication information in a unicast, multicast, or broadcast manner.

[0273] In this embodiment, the initiator of the first transaction sends an SLPP message carrying the third indication information, so that the participants who receive the SLPP message can know the end of the first transaction based on the third indication information carried in the SLPP message. This helps improve the accuracy of determining the end of the transaction by the initiator and multiple participants of the same transaction.

[0274] Figure 8 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 8, the method is executed by the sending end and may include the following steps:

[0275] Step 801: Send an SLPP message carrying fourth indication information, wherein the fourth indication information is used to indicate that the SLPP message carrying the fourth indication information is: the last message of the sending end in the first transaction or the last message carrying the SLPP message body; wherein the participant of the first transaction is the UE group, and the sending end is any UE involved in the first transaction.

[0276] Exemplarily, a UE group may include multiple UEs.

[0277] In some examples, the fourth indication information may be carried in a message header or a message body of the SLPP message.

[0278] For example, when the fourth indication information and the transaction content are both carried in the message body of the SLPP message, the message body further includes a distinguishing mark, which is used to distinguish the fourth indication information from the transaction content in the message body.

[0279] In some examples, the fourth indication information may be a transaction end indication.

[0280] For example, the transaction end indication is an end tag, which may be "end session"; or the transaction end indication is a bit sequence indicating the end.

[0281] The SLPP message sent by the sender in the first transaction can carry a transaction end indication when carrying a message body. In this way, there is no need to construct a special message to carry a transaction end indication in addition to the SLPP message carrying the message body, so that the SLPP message is reused and implemented simply.

[0282] In some examples, the transaction end indication may be carried in a SLPP message that does not include an SLPP message body. In this example, the SLPP message carrying the fourth indication information may be understood as a dedicated SLPP message or a specific SLPP message.

[0283] For example, after the transmission of the last SLPP message carrying the message body sent in the first transaction is completed, the sending end sends an SLPP message carrying the transaction end indication.

[0284] In some examples, the sending end may send the SLPP message carrying the fourth indication information in a unicast, multicast, or broadcast manner.

[0285] In this embodiment, when the participants in the first transaction are a UE group and the sender is any UE involved in the first transaction, the sender sends an SLPP message carrying fourth indication information. Upon receiving the SLPP message carrying the fourth indication information from the sender, the receiver can confirm that the SLPP message is the last message sent by the sender within the first transaction or the last message carrying an SLPP message body. This helps improve the accuracy of determining the end of a transaction between the initiator and multiple participants in the same transaction.

[0286] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0287] Next, the information processing method performed by the receiving end is described, which is similar to the description of the information processing method performed by the sending end mentioned above; and, for technical details not disclosed in the embodiment of the information processing method performed by the receiving end, please refer to the description of the example of the information processing method performed by the sending end, and no detailed description is given here.

[0288] Figure 9 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 9, the method is executed by a receiving end and may include the following steps:

[0289] Step 901: Receive an SLPP message carrying first indication information; wherein the first indication information is used to end a first transaction; and the number of UEs involved in the first transaction is less than or equal to two.

[0290] In some examples, the SLPP message carrying the first indication information includes one of the following: the last SLPP message involved in the first transaction; the last SLPP message involved in the first transaction and carrying the SLPP message body.

[0291] For example, when the first transaction involves two UEs and the SLPP message that the sender needs to send is the last SLPP message in the first transaction, or the last message carrying the SLPP message body in the first transaction, the sender can add first indication information in the SLPP message to indicate the end of the first transaction.

[0292] For example, when the first transaction involves two UEs and the sender is the initiator of the first transaction, the sender can send an SLPP message carrying the first indication information, so that the receiving end (here, the receiving end is a participant in the first transaction) can determine that the first transaction is over when it receives the first SLPP message.

[0293] In some examples, the first indication information may be carried in a message header or a message body of the SLPP message.

[0294] For example, when the first indication information and the transaction content are both carried in the message body of the SLPP message, the message body further includes a distinguishing mark, which is used to distinguish the first indication information from the transaction content in the message body.

[0295] In some examples, the first indication information may be a transaction end indication.

[0296] For example, the transaction end indication is an end tag, which may be "end session"; or the transaction end indication is a bit sequence indicating the end.

[0297] The SLPP message of the first transaction can carry a transaction end indication when carrying a message body. There is no need to construct a special message to carry the transaction end indication in addition to the SLPP message carrying the message body, so that the SLPP message is reused and implemented simply.

[0298] In some examples, the transaction end indication may be carried in a SLPP message that does not include an SLPP message body. In this example, the SLPP message carrying the first indication information may be understood as a dedicated SLPP message or a specific SLPP message for indicating the transaction end.

[0299] For example, after the last SLPP message carrying the message body of the first transaction is transmitted, an SLPP message carrying a transaction end indication is sent.

[0300] In the embodiment of the present disclosure, the number of UEs involved in the first transaction is less than or equal to two; after the receiving end receives the SLPP message carrying the first indication information, it can directly end the first transaction according to the first indication information.

[0301] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0302] Figure 10 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 10, the method is executed by receiving, and the method may include the following steps:

[0303] Step 1001: Receive an SLPP message carrying second indication information sent by a sending end; wherein the second indication information is used to indicate that the SLPP message carrying the second indication information is: the last message of the sending end in the first transaction or the last message carrying the SLPP message body; the participant in the first transaction is a UE group, and the sending end is a UE in the UE group.

[0304] In some examples, the second indication information may be carried in a message header or a message body of the SLPP message.

[0305] For example, when the second indication information and the transaction content are both carried in the message body of the SLPP message, the message body further includes a distinguishing mark, which is used to distinguish the second indication information from the transaction content in the message body.

[0306] In some examples, the second indication information may be a transaction end indication.

[0307] For example, the transaction end indication is an end tag, which may be "end session"; or the transaction end indication is a bit sequence indicating the end.

[0308] The SLPP message sent by the sender in the first transaction can carry a transaction end indication when carrying a message body. In this way, there is no need to construct a special message to carry a transaction end indication in addition to the SLPP message carrying the message body, so that the SLPP message is reused and implemented simply.

[0309] In some examples, the transaction end indication may be carried in a SLPP message that does not include an SLPP message body. In this example, the SLPP message carrying the second indication information may be understood as a dedicated SLPP message or a specific SLPP message.

[0310] For example, after the transmission of the last SLPP message carrying the message body of the first transaction is completed, the sending end sends an SLPP message carrying a transaction end indication.

[0311] In some examples, the receiving end may receive the SLPP message carrying the second indication information in a unicast, multicast, or broadcast manner.

[0312] In this embodiment, when the receiving end is the initiator of the first transaction, upon receiving an SLPP message carrying the second indication information, the receiving end can confirm, based on the second indication information carried in the SLPP message, that the SLPP message is the last message sent by the sending end within the first transaction, or the last message carrying the SLPP message body. This helps improve the accuracy of determining the end of a transaction between the initiator and multiple participants in the same transaction.

[0313] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0314] Figure 11 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 11, the method is executed by a receiving end, and the method may include the following steps:

[0315] Step 1101: In response to receiving an SLPP message carrying third indication information, determine to end the first transaction or determine that the SLPP message carrying the third indication information is the last message carrying an SLPP message body of the first transaction. The participants in the first transaction are a UE group, and the receiving end is a UE in the UE group.

[0316] In some examples, the relevant description of the third indication information and other contents can be found in the relevant description of the third indication information and other contents in the aforementioned embodiments, and will not be repeated here.

[0317] In some examples, the receiving end may receive the SLPP message carrying the third indication information in a unicast, multicast, or broadcast manner.

[0318] In this embodiment, by receiving an SLPP message carrying third indication information sent by the initiator of the first transaction, the participants in the first transaction, after confirming the completion of the first transaction based on the third indication information, or confirming that the SLPP message carrying the third indication information is the last message carrying an SLPP message body of the first transaction, no longer expect to receive any SLPP messages related to the first transaction, or any SLPP messages carrying an SLPP message body related to the first transaction. In other words, when a participant in the first transaction receives any SLPP message for a transaction with the same transaction ID as the first transaction, or any SLPP message carrying an SLPP message body for a transaction with the same transaction ID as the first transaction, the participant will treat the SLPP message as an SLPP message for a new transaction.

[0319] In this embodiment, since the same transaction may involve multiple different participants, the initiator of the first transaction sends an SLPP message carrying the third indication information, which can enable the participants of the first transaction to determine the end of the first transaction based on the third indication information, which is conducive to improving the accuracy of the initiator of the same transaction and multiple participants in determining the end of the transaction.

[0320] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0321] Figure 12 is a flow chart of an information processing method according to an exemplary embodiment. As shown in Figure 12, the method is executed by receiving, and the method may include the following steps:

[0322] Step 1201: In response to receiving an SLPP message carrying fourth indication information, determine to end the first transaction; wherein, the SLPP message carrying the fourth indication information is sent by all other UEs involved in the first transaction except the receiving end; the participants in the first transaction are the UE group.

[0323] In some examples, the relevant description of the fourth indication information and other contents can be found in the relevant description of the fourth indication information and other contents in the aforementioned embodiments, and will not be repeated here.

[0324] In some examples, the receiving end may receive the SLPP message carrying the fourth indication information in a unicast, multicast, or broadcast manner.

[0325] In this embodiment, when the participants in the first transaction are a UE group and the sender is any UE involved in the first transaction, upon receiving an SLPP message from the sender carrying fourth indication information, the receiver can confirm that the SLPP message is the last message sent by the sender within the first transaction or the last message carrying an SLPP message body. This helps improve the accuracy of determining the end of a transaction between the initiator and multiple participants in the same transaction.

[0326] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0327] It should be noted that those skilled in the art will understand that the method provided in the embodiments of the present disclosure may be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0328] In order to further explain any embodiment of the present disclosure, some specific examples are provided below.

[0329] The present disclosure provides an information processing method, which may include:

[0330] The first UE (eg, UE A) sends an SLPP message. The SLPP message carries a transaction ID. The transaction ID includes at least the UE ID of the transaction initiator.

[0331] In some examples, the transaction ID may also include a transaction number.

[0332] In some examples, SLPP messages within the same transaction use the same transaction number.

[0333] In some examples, the transaction ID is carried in the SPP message only when the SLPP message includes a SLPP message body (eg, slpp-MessageBody).

[0334] In some examples, if the transaction involves only two UEs, the initiator's UE ID may be indicated by the UE type, such as server UE or client UE.

[0335] In some examples, if the transaction initiator is a server UE, the UE ID may be indicated by the UE type, ie, server UE.

[0336] In some examples, the first SLPP message received by the UE that carries a transaction ID triggers the establishment of the transaction.

[0337] In some embodiments, the UE ID of the transaction initiator may be the source end layer 2 ID, the destination end layer 2 ID, the application layer ID, or the SLPP UE ID of the initiator.

[0338] In some embodiments, the transaction ID further includes the UE ID of the transaction participant.

[0339] In some examples, when the transaction participant is a UE, the UE ID of the transaction participant may be the participant's source layer 2 ID, or destination layer 2 ID, or application layer ID, or SLPP UE ID.

[0340] In some examples, when the transaction participant is a group of UEs, the UE ID of the transaction participant may be the source / destination layer 2 multicast ID of the participant, or the application layer group ID, or the SLPP group ID.

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

[0342] In some examples, when the transaction participants are a group of UEs, the UE IDs of the transaction participants may be a list of source / destination layer 2 IDs of each participant, or a list of application layer IDs of each participant, or a list of SLPP UE IDs of each participant.

[0343] In some examples, when the transaction is created in broadcast mode, the UE ID of the transaction participant may be a source / destination layer 2 broadcast ID or an SLPP broadcast ID.

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

[0345] In some examples, only when a transaction participant is a UE or a group of UEs, the transaction ID carries the UE ID of the participant.

[0346] In some examples, if the transaction is created in broadcast mode, the transaction ID does not carry the UE ID of the participant.

[0347] In some embodiments, the transaction IDs of parallel transactions within the same session need to be different.

[0348] In some examples, after the transaction ends, the transaction ID can continue to be used to create new transactions within the session.

[0349] In some examples, the transaction IDs need to be different, including at least one of the transaction initiator and the transaction number being different.

[0350] In some examples, the transaction IDs need to be different, including at least one of the transaction initiator, the participants, and the transaction number.

[0351] In some embodiments, if the SLPP transaction involves only two UEs, if the SLPP message to be sent by the UE is the last message of a transaction, or the last message carrying an SLPP message body, the UE adds an end transaction indication (e.g., end transaction) in the SLPP message.

[0352] In some embodiments, if the SLPP transaction involves a group of UEs, the UEs participating in the transaction add indication information (e.g., end transaction) in the SLPP message to indicate that the currently sent SLPP message is the last message of the transaction for the UE, or the last message carrying the SLPP message body.

[0353] In some examples, the SLPP message carrying the end transaction may be sent by unicast, multicast, or broadcast.

[0354] In some examples, the UE initiating the transaction determines to end the transaction and sends an SLPP message carrying "end transaction" to other UEs in the transaction.

[0355] In some examples, when the initiating UE sends a SLPP message carrying an end transaction, the SLPP message may not have a SLPP body (ie, a message body).

[0356] In some examples, the determining to end the transaction includes determining to end the transaction based on an end transaction indication sent by a transaction participating UE.

[0357] In some examples, the SLPP message carrying the end transaction may be sent by unicast, multicast, or broadcast.

[0358] In some examples, after receiving the SLPP message carrying the end transaction sent by the transaction initiating UE, other UEs in the SLPP transaction confirm that the transaction is ended, or confirm that it is the last message carrying the SLPP packet body of the transaction.

[0359] In some examples, after confirming the end of a transaction or confirming that it is the last message carrying an SLPP body in the transaction, the UE no longer expects to receive any SLPP messages for the transaction or any SLPP messages carrying an SLPP body for the transaction. In other words, the UE will treat any received SLPP message with the same transaction ID or any SLPP message carrying an SLPP body with the same transaction ID as an SLPP message for a new SLPP transaction.

[0360] In some examples, after receiving the SLPP message carrying the end transaction sent by all other UEs in the transaction, a UE in the transaction confirms the end of the transaction, or confirms that it is the last message carrying the SLPP body in the transaction.

[0361] In some examples, after confirming the end of a transaction or confirming that it is the last message carrying an SLPP body in the transaction, the UE no longer expects to receive any SLPP messages for the transaction or any SLPP messages carrying an SLPP body for the transaction. In other words, the UE will treat any received SLPP message with the same transaction ID or any SLPP message carrying an SLPP body with the same transaction ID as an SLPP message for a new SLPP transaction.

[0362] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0363] It should be noted that those skilled in the art will understand that the information processing method provided in the embodiments of the present disclosure may be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0364] FIG13 is a schematic diagram showing the structure of an information processing device according to an exemplary embodiment. As shown in FIG13 , the information processing device 100 includes:

[0365] The sending module 110 is configured as a sending module, configured to send an SLPP message; wherein the SLPP message includes a transaction identification ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0366] In some embodiments, the transaction ID includes:

[0367] The first ID is used to indicate the initiator of the first transaction.

[0368] In some embodiments, the first ID includes at least one of the following:

[0369] The source end layer 2 ID of the initiator;

[0370] The destination layer 2 ID of the initiator;

[0371] The application layer ID of the initiator;

[0372] The SLPP UE ID of the initiator.

[0373] In some embodiments, the transaction ID further includes:

[0374] The second ID is used to indicate the participant of the first transaction.

[0375] In some embodiments, the participant is a UE, and the second ID includes at least one of the following:

[0376] The source layer 2 ID of the participant;

[0377] The destination layer 2 ID of the participant;

[0378] The application layer ID of the participant;

[0379] The SLPP user equipment UE ID of the participant.

[0380] In some embodiments, the participant is a UE group, and the second ID includes at least one of the following:

[0381] The group ID of the UE group;

[0382] The source layer 2 multicast ID of the UE group;

[0383] Destination layer 2 multicast ID of the UE group;

[0384] The application layer group ID of the UE group;

[0385] The SLPP UE group ID of the UE group.

[0386] In some embodiments, the participant is a UE group, and the second ID includes at least one of the following:

[0387] List of source layer 2 IDs of the participants;

[0388] The destination layer 2 ID list of the participants;

[0389] A list of application layer IDs of the participants;

[0390] List of SLPP UE IDs of the participants.

[0391] In some embodiments, the first transaction is created in broadcast mode, and the second ID includes: at least one of a source end layer 2 broadcast ID, a destination end layer 2 broadcast ID, and an SLPP broadcast ID of the participant;

[0392] Alternatively, the participant in the first transaction is a UE or a UE group, and the transaction ID includes the second ID;

[0393] Alternatively, the first transaction is created in a broadcast mode, and the transaction ID does not include the second ID.

[0394] 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.

[0395] In some embodiments, the initiator of the first transaction is different from the initiator of the second transaction;

[0396] and / or, the parties involved in the first transaction are different from the parties involved in the second transaction;

[0397] 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.

[0398] In some embodiments, the number of UEs involved in the first transaction is less than or equal to two, and the sending module 110 is configured to:

[0399] Sending an SLPP message carrying first indication information; wherein the first indication information is used to end the first transaction;

[0400] The SLPP message carrying the first indication information includes one of the following:

[0401] The last SLPP message involved in the first transaction;

[0402] The first transaction involves the last SLPP message carrying the SLPP message body.

[0403] In some embodiments, the participants of the first transaction are a UE group, the sending end is a UE in the UE group, and the sending module 110 is configured to:

[0404] Sending an SLPP message carrying second indication information; wherein the second indication information is used to indicate that the SLPP message carrying the second indication information is: the last message of the sending end in the first transaction or the last message carrying the SLPP message body.

[0405] In some embodiments, the participants of the first transaction are a UE group, the sending end is the initiator of the first transaction, and the sending module 110 is configured to:

[0406] In response to determining to end the first transaction, sending an SLPP message carrying third indication information; wherein the third indication information is used to end the first transaction.

[0407] In some embodiments, the participants in the first transaction are a UE group, the sender is any UE involved in the first transaction, and the sending module 110 is configured to send an SLPP message carrying fourth indication information, where the fourth indication information is used to indicate that the SLPP message carrying the fourth indication information is the last message sent by the sender within the first transaction or the last message carrying an SLPP message body. Regarding the information processing apparatus in the above embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments of the information processing method performed by the sender and will not be elaborated upon here.

[0408] FIG14 is a schematic diagram showing the structure of an information processing device according to an exemplary embodiment. As shown in FIG14 , the information processing device 200 includes:

[0409] The receiving module 210 is configured to receive an SLPP message; wherein the SLPP message includes a transaction identification ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

[0410] In some embodiments, the transaction ID includes:

[0411] The first ID is used to indicate the initiator of the first transaction.

[0412] In some embodiments, the first ID includes at least one of the following:

[0413] The source end layer 2 ID of the initiator;

[0414] The destination layer 2 ID of the initiator;

[0415] The application layer ID of the initiator;

[0416] The SLPP UE ID of the initiator.

[0417] In some embodiments, the transaction ID further includes:

[0418] The second ID is used to indicate the participant of the first transaction.

[0419] In some embodiments, the participant is a UE, and the second ID includes at least one of the following:

[0420] The source layer 2 ID of the participant;

[0421] The destination layer 2 ID of the participant;

[0422] The application layer ID of the participant;

[0423] The SLPP user equipment UE ID of the participant.

[0424] In some embodiments, the participant is a UE group, and the second ID includes at least one of the following:

[0425] The group ID of the UE group;

[0426] The source layer 2 multicast ID of the UE group;

[0427] Destination layer 2 multicast ID of the UE group;

[0428] The application layer group ID of the UE group;

[0429] The SLPP UE group ID of the UE group.

[0430] In some embodiments, the participant is a UE group, and the second ID includes at least one of the following:

[0431] List of source layer 2 IDs of the participants;

[0432] The destination layer 2 ID list of the participants;

[0433] A list of application layer IDs of the participants;

[0434] List of SLPP UE IDs of the participants.

[0435] In some embodiments, the first transaction is created in broadcast mode, and the second ID includes: at least one of a source end layer 2 broadcast ID, a destination end layer 2 broadcast ID, and an SLPP broadcast ID of the participant;

[0436] Alternatively, the participant in the first transaction is a UE or a UE group, and the transaction ID includes the second ID;

[0437] Alternatively, the first transaction is created in a broadcast mode, and the transaction ID does not include the second ID.

[0438] 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.

[0439] In some embodiments, the initiator of the first transaction is different from the initiator of the second transaction;

[0440] and / or, the parties involved in the first transaction are different from the parties involved in the second transaction;

[0441] 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.

[0442] In some embodiments, the number of UEs involved in the first transaction is less than or equal to two, and the receiving module 210 is configured to:

[0443] receiving an SLPP message carrying first indication information, wherein the first indication information is used to end the first transaction;

[0444] The SLPP message carrying the first indication information includes one of the following:

[0445] The last SLPP message involved in the first transaction;

[0446] The first transaction involves the last SLPP message carrying the SLPP message body.

[0447] In some embodiments, the participants in the first transaction are a UE group, the receiving end is the initiator of the first transaction, and the receiving module 210 is configured to:

[0448] Receive an SLPP message carrying second indication information sent by a sending end; wherein the second indication information is used to indicate that the SLPP message carrying the second indication information is: the last message of the sending end in the first transaction or the last message carrying an SLPP message body.

[0449] In some embodiments, the participants in the first transaction are a UE group, the receiving end is a UE in the UE group, and the apparatus further includes:

[0450] The first determining module is configured to, in response to receiving the SLPP message carrying the third indication information, determine to end the first transaction or determine that the SLPP message carrying the third indication information is the last message carrying the SLPP message body of the first transaction.

[0451] In some embodiments, the participants in the first transaction are a UE group, and the apparatus further comprises:

[0452] The first determination module is configured to determine to end the first transaction in response to receiving an SLPP message carrying fourth indication information; wherein the SLPP message carrying the fourth indication information is sent by all other UEs involved in the first transaction except the receiving end.

[0453] Regarding the information processing apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the information processing method executed by the receiving end, and will not be elaborated here.

[0454] An embodiment of the present disclosure provides a communication device, including:

[0455] a memory for storing processor-executable instructions;

[0456] Processor, respectively memory connected;

[0457] The processor is configured to execute the information processing method provided by any of the aforementioned technical solutions.

[0458] The processor may include various types of storage media, which are non-transitory computer storage media that can continue to store information after the communication device loses power.

[0459] Here, the communication device includes: UE.

[0460] The processor can be connected to the memory via a bus, etc., and is used to read the executable program stored in the memory, for example, to implement the information processing method provided by any of the aforementioned embodiments.

[0461] An embodiment of the present disclosure provides a computer storage medium storing an executable program. After the executable program is executed by a processor, the information processing method provided by any of the aforementioned technical solutions can be implemented.

[0462] Figure 15 is a block diagram of a terminal 800 according to an exemplary embodiment. For example, the terminal 800 may be a mobile phone, a computer, a digital broadcast user device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

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

[0464] The processing component 802 generally controls the overall operation of the terminal 800, such as operations associated with display, phone calls, data communications, camera operation, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the above-described method. In addition, the processing component 802 may 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.

[0465] The memory 804 is configured to store various types of data to support operations on the terminal 800. Examples of such data include instructions for any application or method operating on the terminal 800, contact data, phone book data, messages, pictures, videos, etc. The 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.

[0466] Power supply component 806 provides power to various components of terminal 800. Power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to terminal 800.

[0467] 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 touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the terminal 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.

[0468] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), which is configured to receive external audio signals when the terminal 800 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0469] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as 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.

[0470] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the terminal 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the terminal 800. The sensor assembly 814 can also detect changes in the position of the terminal 800 or a component of the terminal 800, the presence or absence of user contact with the terminal 800, the orientation or acceleration / deceleration of the terminal 800, and temperature changes of the terminal 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0471] 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 also 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) technology and other technologies.

[0472] In an exemplary embodiment, the terminal 800 may 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 perform the above methods.

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

[0474] In the absence of contradiction, each step in a certain embodiment or example can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment or example can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment or example can be arbitrarily exchanged. In addition, the optional methods or optional examples in a certain embodiment or example can be arbitrarily combined; in addition, the various embodiments or examples can be arbitrarily combined. For example, some or all steps of different embodiments or examples can be arbitrarily combined, and a certain embodiment or example can be arbitrarily combined with the optional methods or optional examples of other embodiments or examples.

[0475] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0476] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. An information processing method, wherein: Executed by the sending end, the method includes: Send a Side Link Positioning Protocol (SLPP) message; wherein the SLPP message includes a transaction identifier (ID) of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

2. The method according to claim 1, wherein: The transaction ID includes: The first ID is used to indicate the initiator of the first transaction.

3. The method according to claim 2, wherein: The first ID includes at least one of the following: The source layer 2 ID of the initiator; The destination layer 2 ID of the initiator; The application layer ID of the initiator; The SLPP UE ID of the initiator.

4. The method according to any one of claims 1 to 3, wherein: The transaction ID also includes: The second ID is used to indicate a participant of the first transaction.

5. The method according to claim 4, wherein: The participant is a UE, and the second ID includes at least one of the following: The source layer 2 ID of the participant; The destination layer 2 ID of the participant; The application layer ID of the participant; SLPP user equipment UE ID of the participant.

6. The method according to claim 4, wherein: 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 multicast ID of the UE group; The destination layer 2 multicast ID of the UE group; The application layer group ID of the UE group; The SLPP UE group ID of the UE group.

7. The method according to claim 4, wherein: The participant is a UE group, and the second ID includes at least one of the following: A list of source layer 2 IDs of the participants; The destination layer 2 ID list of the participants; A list of application layer IDs of the participants; List of SLPP UE IDs of the participants.

8. The method according to claim 4, wherein: The first transaction is created in broadcast mode, and the second ID includes: at least one of the source end layer 2 broadcast ID, the destination end layer 2 broadcast ID and the SLPP broadcast ID of the participant; or, The participant of the first transaction is a UE or a UE group, 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.

9. The method according to any one of claims 1 to 8, wherein: 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.

10. The method according to claim 9, wherein: The initiator of the first transaction is different from the initiator of the second transaction; and / or, The parties involved in the first transaction are different from the parties involved 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.

11. The method according to any one of claims 1 to 10, wherein: The number of UEs involved in the first transaction is less than or equal to two, and the method further includes: Sending a SLPP message carrying first indication information; wherein the first indication information is used to end the first transaction; The SLPP message carrying the first indication information includes one of the following: the last SLPP message involved in the first transaction; The first transaction involves the last SLPP message carrying the SLPP message body.

12. The method according to any one of claims 1 to 10, wherein: The participants of the first transaction are a UE group, the sending end is a UE in the UE group, and the method further includes: Sending a SLPP message carrying second indication information; wherein the second indication information is used to indicate that the SLPP message carrying the second indication information is: the last message of the sending end in the first transaction or the last message carrying the SLPP message body.

13. The method according to any one of claims 1 to 10, wherein: The participants of the first transaction are a UE group, the sending end is an initiator of the first transaction, and the method further includes: In response to determining to end the first transaction, sending a SLPP message carrying third indication information; wherein the third indication information is used to end the first transaction.

14. The method according to any one of claims 1 to 10, wherein: The participants of the first transaction are a UE group, the sender is any UE involved in the first transaction, and the method further includes: sending a SLPP message carrying fourth indication information, wherein the fourth indication information is used to indicate that the SLPP message carrying the fourth indication information is: the last message of the sender in the first transaction or the last message carrying the SLPP message body.

15. An information processing method, wherein: Executed by the receiving end, the method includes: A Sidelink Positioning Protocol (SLPP) message is received; wherein the SLPP message includes a transaction identification ID of a first transaction, and the transaction ID is used to determine an initiator of the first transaction.

16. The method according to claim 15, wherein: The transaction ID includes: The first ID is used to indicate the initiator of the first transaction.

17. The method according to claim 16, wherein: The first ID includes at least one of the following: The source layer 2 ID of the initiator; The destination layer 2 ID of the initiator; The application layer ID of the initiator; The SLPP UE ID of the initiator.

18. The method according to any one of claims 15 to 17, wherein: The transaction ID also includes: The second ID is used to indicate a participant of the first transaction.

19. The method according to claim 18, wherein: The participant is a UE, and the second ID includes at least one of the following: The source layer 2 ID of the participant; The destination layer 2 ID of the participant; The application layer ID of the participant; SLPP user equipment UE ID of the participant.

20. The method according to claim 18, wherein: 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 multicast ID of the UE group; The destination layer 2 multicast ID of the UE group; The application layer group ID of the UE group; The SLPP UE group ID of the UE group.

21. The method according to claim 18, wherein: The participant is a UE group, and the second ID includes at least one of the following: A list of source layer 2 IDs of the participants; The destination layer 2 ID list of the participants; A list of application layer IDs of the participants; List of SLPP UE IDs of the participants.

22. The method according to claim 18, wherein: The first transaction is created in broadcast mode, and the second ID includes: at least one of the source end layer 2 broadcast ID, the destination end layer 2 broadcast ID and the SLPP broadcast ID of the participant; or, The participant of the first transaction is a UE or a UE group, 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.

23. The method according to any one of claims 15 to 22, wherein: 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.

24. The method according to claim 23, wherein: The initiator of the first transaction is different from the initiator of the second transaction; and / or, The parties involved in the first transaction are different from the parties involved 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.

25. The method according to any one of claims 15 to 24, wherein: The number of UEs involved in the first transaction is less than or equal to two, and the method further includes: Receiving an SLPP message carrying first indication information; wherein the first indication information is used to end the first transaction; The SLPP message carrying the first indication information includes one of the following: the last SLPP message involved in the first transaction; The first transaction involves the last SLPP message carrying the SLPP message body.

26. The method according to any one of claims 15 to 24, wherein: The participants of the first transaction are a UE group, the receiving end is an initiator of the first transaction, and the method further includes: Receive an SLPP message carrying second indication information sent by a sending end; wherein the second indication information is used to indicate that the SLPP message carrying the second indication information is: the last message of the sending end in the first transaction or the last message carrying an SLPP message body.

27. The method according to any one of claims 15 to 24, wherein: The participants of the first transaction are a UE group, the receiving end is a UE in the UE group, and the method further includes: In response to receiving the SLPP message carrying the third indication information, it is determined that the first transaction is ended or it is determined that the SLPP message carrying the third indication information is the last message carrying the SLPP message body of the first transaction.

28. The method according to any one of claims 15 to 24, wherein: The participants of the first transaction are a UE group, and the method further includes: In response to receiving an SLPP message carrying fourth indication information, determining to end the first transaction; wherein the SLPP message carrying the fourth indication information is sent by all other UEs involved in the first transaction except the receiving end.

29. An information processing device, wherein: The device comprises: The sending module is configured to send a Side Link Positioning Protocol (SLPP) message; wherein the SLPP message includes a transaction identification ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

30. An information processing device, wherein: The device comprises: The receiving module is configured to receive a sidelink positioning protocol SLPP message; wherein the SLPP message includes a transaction identification ID of the first transaction, and the transaction ID is used to determine the initiator of the first transaction.

31. A communication device comprising a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being run by the processor, wherein: When the processor runs the executable program, the information processing method provided in any one of claims 1 to 14 or 15 to 28 is executed.

32. A computer storage medium storing an executable program; after the executable program is executed by a processor, it can implement the information processing method provided in any one of claims 1 to 14 or 15 to 28.

Citation Information

Patent Citations

  • Service security verifying method and apparatus

    CN104426846A

  • Sending method, receiving method and device of sidelink positioning message

    CN115997392A

  • Session distinguishing method and device

    CN115997470A

  • Group positioning method and device, equipment and storage medium

    CN116076122A

  • Message transmission method and device, equipment and storage medium

    CN116097666A