Information processing method, device, communication equipment and storage medium

By using transaction ID to identify the SLPP message of the transaction initiator in the wireless communication system, the problem of difficulty in distinguishing between transaction initiators in inter-UE positioning is solved, the accuracy of information interaction and positioning is improved, and the positioning accuracy of the wireless communication system is improved.

CN116868642BActive Publication Date: 2024-11-22BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380009405.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-22
Estimated Expiration
2043-05-12

AI Technical Summary

Technical Problem

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

Method used

By sending and receiving SLPP messages containing transaction IDs, the transaction ID is used to determine the initiator of the transaction, thereby avoiding distinction difficulties when multiple participants participate in the same transaction, and improving the accuracy of information interaction and positioning accuracy.

Benefits of technology

It effectively solves the problem of the transaction initiator's difficulty in distinguishing, improves the accuracy of information interaction and positioning accuracy, and enhances the reliability of the positioning process in wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116868642B_ABST
    Figure CN116868642B_ABST
Patent Text Reader

Abstract

The embodiments of the present disclosure provide an information processing method, apparatus, communication device and storage medium. The information processing method executed by a transmitting end includes: sending a side link positioning protocol (SLPP) message; wherein the SLPP message includes a transaction identification ID of a first transaction, and the transaction ID is used to determine the initiator of the first transaction.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] In a communication system, positioning based on a user equipment (UE) and a sidelink (SL) between 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. Summary of the invention

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

[0005] 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:

[0006] Send a Sidelink Positioning Protocol (Sidelink Positioning Protocol or Sidelink LTEpositioning protocol, SLPP) message; wherein the SLPP message includes a transaction identification (Identification, ID) of a first transaction (transaction), and the transaction ID is used to determine the initiator of the first transaction.

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

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

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

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

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

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

[0013] 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 the processor executes the information processing method provided in the first or second aspect above when running the executable program.

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

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

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

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

[0018] The technical solution provided by the embodiment of the present disclosure includes a transaction ID of a first transaction by sending an SLPP message, and the transaction ID is used to determine the initiator of the first transaction. In this way, the transaction ID included in the SLPP message can be used to determine the initiator of the transaction, thereby reducing the situation where multiple participants cannot distinguish the initiator of the transaction when participating in the same transaction, or different participants in the same transaction determine different initiators, thereby improving the accuracy of information exchange during the transaction. Since the transaction initiator can be more accurately distinguished according to the transaction ID, positioning using the SLPP message carrying the transaction ID can improve the accuracy of positioning.

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

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

[0021] Figure 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment;

[0022] Figure 2 is a structural schematic diagram of a positioning framework according to an exemplary embodiment;

[0023] Figure 3 is a flowchart of an information processing method according to an exemplary embodiment;

[0024] Figure 4 is a flowchart of an information processing method according to an exemplary embodiment;

[0025] Figure 5 is a flowchart of an information processing method according to an exemplary embodiment;

[0026] Figure 6 is a flowchart of an information processing method according to an exemplary embodiment;

[0027] Figure 7 is a flowchart of an information processing method according to an exemplary embodiment;

[0028] Figure 8 is a flowchart of an information processing method according to an exemplary embodiment;

[0029] Fig. 9 is a flowchart of an information processing method according to an exemplary embodiment;

[0030] Fig.10 is a flowchart of an information processing method according to an exemplary embodiment;

[0031] Fig.11 is a flowchart of an information processing method according to an exemplary embodiment;

[0032] Fig.12 is a flowchart of an information processing method according to an exemplary embodiment;

[0033] Fig.13 is a schematic diagram of the structure of an information processing device according to an exemplary embodiment;

[0034] Fig.14 is a schematic diagram of the structure of an information processing device according to an exemplary embodiment;

[0035] Fig.15 The diagram is a schematic diagram of the structure of a terminal according to an exemplary embodiment. DETAILED DESCRIPTION

[0036] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the embodiments of the present invention. Instead, they are only examples of devices and methods consistent with some aspects of the embodiments of the present invention.

[0037] 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 embodiments of the present disclosure. The singular forms of "a", "said", and "the" used in the present disclosure are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in this article refers to and includes any or all possible combinations of one or more associated listed items.

[0038] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the disclosed embodiments, 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".

[0039] 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. Figure 1 As shown, 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 equipments 11 and a plurality of access network equipments 12 .

[0040] 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 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 a 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 device 11 may be a device of an unmanned aerial vehicle. Alternatively, the user device 11 may be a vehicle-mounted device, for example, a driving computer with a wireless communication function, or a wireless user device connected to an external driving computer. Alternatively, the user device 11 may be a roadside device, for example, a street lamp, a signal lamp, or other roadside device with a wireless communication function.

[0041] The access network device 12 may be a device for communicating with the user equipment 11 in a wireless communication system, may be a base station, or 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 and IP packets to each other, as a router between the wireless terminal and the rest of the access network, wherein 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. Among them, the wireless communication system may be the 4th generation mobile communication technology (4G) system, also known as the Long Term Evolution (LTE) system; or, the wireless communication system may also be a 5G system, also known as a new radio (NR) system or a 5G NR system. Alternatively, the wireless communication system may also be the next generation system of the 5G system. Among them, the access network in the 5G system may be called NG-RAN (New Generation-Radio Access Network, a new generation of wireless access network).

[0042] 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 (Physical, PHY) layer protocol stack. The specific implementation method of the access network device 12 is not limited in the embodiment of the present disclosure.

[0043] A wireless connection can be established between the access network device 12 and the user equipment 11 through 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.

[0044] In some embodiments, an E2E (End to End) or D2D (device to device) connection may also be established between user devices 11, such as V2V (vehicle to vehicle) communication, V2I (vehicle to Infrastructure) communication and V2P (vehicle to pedestrian) communication in vehicle to everything (V2X) communication.

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

[0046] 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 also be a Serving GateWay (SGW), a Public Data Network Gateway (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS).

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

[0048] The PCF, SMF, UPF, etc. in the embodiments of the present disclosure can be implemented by one physical device or by multiple physical devices. It is understandable that the PCF, SMF, etc. in the embodiments of the present disclosure can be a logical function module in a physical device or a logical function module composed of multiple physical devices, which is not limited in the embodiments of the present disclosure.

[0049] In order to facilitate the understanding of 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 can understand that the multiple embodiments provided by the embodiments of the present disclosure can be executed separately, or can be executed together with the methods of other embodiments of the embodiments of the present disclosure, or can be executed together with some methods in other related technologies separately or in combination; the embodiments of the present disclosure do not limit this.

[0050] In each embodiment of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment based on their internal logical relationships.

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

[0052] Positioning based on the sidelink (SL) between UEs includes absolute positioning, relative positioning and ranging, where the sidelink can also be called a straight 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.

[0053] In the present disclosure, Figure 2 As shown in the figure, taking the positioning based on the downlink time difference of arrival (DL-TDOA) as an example, the UE can determine the specific position of the UE relative to the RSU by measuring multiple road side units (RSU) and sidelink positioning reference signals (SL PRS).

[0054] In addition to DL-TDOA-based positioning, the positioning scheme 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.

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

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

[0057] Anchor UEs have different types, for example, they may include: RSU type anchor UEs. RSU type anchor UEs belong to a type of infrastructure, and can provide positioning services by collaborating with other RSUs. For example, ordinary UEs can also serve as anchor UEs, but ordinary UEs are difficult to assist in providing positioning services with other UEs. In addition, some anchor UEs have location information such as GPS, which can assist other UEs in absolute positioning; other anchor UEs may not have location information such as GPS.

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

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

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

[0061] In addition, for LPP transactions, since only two UEs are involved, the transaction can be determined to be completed when one of the UEs sends an end transaction indication. However, when multiple UEs may participate in a transaction in SLPP, it is also necessary to consider how to determine the transaction completion.

[0062] Figure 3 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Figure 3 As shown, the method is executed by the sending end, and the method may include the following steps:

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

[0064] In some examples, the first transaction may be any transaction among all transactions in a session.

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

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

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

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

[0069] In some examples, the participant different from the initiator in the first transaction may be a UE or a UE group. The UE group includes multiple UEs.

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

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

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

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

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

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

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

[0077] 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, where the UE type is used to indicate the UE ID of the initiator of the first transaction.

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

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

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

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

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

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

[0084] In some examples, the SLPP message includes at least one of the following: a SLPP transaction creation request message, a SLPP transaction creation completion message, and a SLPP message carrying transaction content.

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

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

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

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

[0089] The information processing method provided by the embodiment of the present disclosure sends an SLPP message, and 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. In this way, the transaction ID included in the SLPP message can be used to determine the initiator of the transaction, thereby reducing the situation where multiple participants cannot distinguish the transaction initiator when participating in the same transaction, or different participants in the same transaction determine different initiators, thereby improving the accuracy of information exchange during the transaction. Since the transaction initiator can be more accurately distinguished according to the transaction ID, positioning using the SLPP message carrying the transaction ID can improve the accuracy of positioning.

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

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

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

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

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

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

[0096] Exemplarily, the substring may include one character, or the substring may include a plurality of consecutively distributed characters.

[0097] For example, the string of the transaction ID 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 is a string consisting of the last N characters of the M characters, or the first ID includes 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.

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

[0099] 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 beneficial to improve the accuracy of information exchange in the same transaction.

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

[0101] Source Layer 2ID of the initiator;

[0102] Destination Layer 2ID of the initiator;

[0103] The application layer ID of the initiator;

[0104] SLPP UE ID of the initiator.

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

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

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

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

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

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

[0111] Exemplarily, the substring may include one character, or the substring may include a plurality of consecutively distributed characters.

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

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

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

[0115] In this embodiment, since the transaction ID includes the second ID, the second ID is used to indicate the participant of the first transaction, so that when the receiving end of the SLPP message receives the SLPP message carrying the transaction ID of the first transaction, it can determine whether it is a participant of the first transaction according to the second ID included in the transaction ID of the first transaction. For example, in the process of positioning using SLPP messages, some UEs have absolute location information, while some UEs do not have absolute location information. If the transaction participant that needs to be located needs to perform absolute location positioning, the UE with absolute location information can be specified as a participant through the second ID.

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

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

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

[0119] The application layer ID of the participant;

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

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

[0122] The group ID of the UE group;

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

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

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

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

[0127] 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 may be provided by the application layer of the session initiator and provided to the session participants via a message for session establishment.

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

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

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

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

[0132] List of application layer IDs of the participants;

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

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

[0135] In this embodiment, the first transaction is created in broadcast mode, and there will be multiple receiving ends of the SLPP message. When these receiving ends receive the SLPP message carrying the transaction ID of the first transaction, if the transaction ID of the first transaction carries the second ID, they can determine whether they are participants of the first transaction based on the second ID. If a receiving end determines that it is a participant of the first transaction, it participates in the first transaction. If a receiving end determines that it is not a participant of the first transaction, it can ignore the SLPP message.

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

[0137] 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 layer 2 broadcast ID, the destination layer 2 broadcast ID and the SLPP broadcast ID of the participant.

[0138] 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 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 for session establishment.

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

[0140] Compared with a single UE, a UE group may include one or more UEs. Based on transactions of a UE group, transactions and / or positioning involving multiple parties may be implemented when the UE group has multiple UEs. Positioning the initiator using the UE group may improve the accuracy of positioning, or positioning the UE group by the initiator may improve the efficiency of positioning.

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

[0142] 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, so that when the receiving end is not the initiator of the first transaction, it can determine that it is a participant of the first transaction.

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

[0144] 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 a transaction that is not parallel to the first transaction.

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

[0146] 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:

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

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

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

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

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

[0152] Sending an SLPP message carrying indication information;

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

[0154] Ending the first transaction;

[0155] The SLPP message is the last message of the sender in the first transaction or the last message carrying the SLPP message body.

[0156] 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 a 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 a SLPP message carrying indication information for indicating the end of the first transaction.

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

[0158] In this example, after receiving the SLPP message carrying the indication information, 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 message related to the first transaction, or any SLPP message carrying the SLPP message body related to the first transaction. In other words, when the receiving end receives any SLPP message of a transaction with the same transaction ID as the first transaction, or any SLPP message carrying the SLPP message body of a transaction with the same transaction ID as the first transaction, it will treat the SLPP as a SLPP message of a new transaction.

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

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

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

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

[0163] the last SLPP message involved in the first transaction;

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

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

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

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

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

[0169] In some embodiments, 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:

[0170] 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 sending end in the first transaction or the last message carrying the SLPP message body.

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

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

[0173] Figure 4 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Figure 4 As shown, the method is performed by a receiving end, and the method may include the following steps:

[0174] Step 401: Receive a 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.

[0175] In some examples, the first transaction may be any transaction among all transactions in a session.

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

[0177] 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 first transaction party is different from the sending end.

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

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

[0180] In some examples, the transaction ID and other related descriptions can be found in Figure 3 The description of the transaction ID and other contents in step 301 will not be repeated here.

[0181] The information processing method provided by the embodiment of the present disclosure receives 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, so that the receiving end can use the transaction ID included in the SLPP message to determine the initiator of the transaction, thereby reducing the situation where multiple participants cannot distinguish the transaction initiator when participating in the same transaction, or different participants in the same transaction determine different initiators, thereby improving the accuracy of information interaction during the transaction. Since the transaction initiator can be more accurately distinguished according to the transaction ID, positioning using the SLPP message carrying the transaction ID can improve the accuracy of positioning.

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

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

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

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

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

[0187] The application layer ID of the initiator;

[0188] The SLPP UE ID of the initiator.

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

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

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

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

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

[0194] The application layer ID of the participant;

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

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

[0197] The group ID of the UE group;

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

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

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

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

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

[0203] A list of source layer 2 IDs of the participants;

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

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

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

[0207] In some embodiments, 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;

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

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

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

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

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

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

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

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

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

[0217] the last SLPP message involved in the first transaction;

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

[0219] In some embodiments, 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:

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

[0221] In some embodiments, 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:

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

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

[0224] In response to receiving a 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.

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

[0226] Figure 5 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Figure 5 As shown, the method is executed by the sending end, and the method may include the following steps:

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

[0228] 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 carrying the SLPP message body involved in the first transaction.

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

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

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

[0232] 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 also includes a distinguishing mark, and the distinguishing mark is used to distinguish the first indication information and the transaction content in the message body.

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

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

[0235] 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, thereby multiplexing the SLPP messages and simplifying the implementation.

[0236] In some examples, the transaction end indication may be carried in a SLPP message that does not include a 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.

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

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

[0239] Figure 6 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Figure 6 As shown, the method is executed by the sending end, and the method may include the following steps:

[0240] 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 sender in the first transaction or the last message carrying the SLPP message body; the participants of the first transaction are a UE group, and the sender is a UE in the UE group.

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

[0242] 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 also includes a distinguishing mark, and the distinguishing mark is used to distinguish the second indication information and the transaction content in the message body.

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

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

[0245] 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 the implementation is simple.

[0246] In some examples, the transaction end indication may be carried in a SLPP message that does not include a 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.

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

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

[0249] In this embodiment, the sending end sends an SLPP message carrying the second indication information. When the receiving end is the initiator of the first transaction, the receiving end can confirm that the SLPP message is: the last message of the sending end in the first transaction or the last message carrying the SLPP message body according to the second indication information carried by the SLPP message. This helps to improve the accuracy of determining the end of the transaction by the initiator and multiple participants of the same transaction.

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

[0251] Receive a 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 a SLPP message sent by the initiator of the first transaction.

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

[0253] According to the SLPP message carrying the third indication information sent by the initiator of the first transaction, it is confirmed that the first transaction is ended, or it is confirmed that the SLPP message carrying the third indication information is the last message carrying the SLPP message body of the first transaction.

[0254] In this embodiment, after the participants of the first transaction confirm the completion of the first transaction according to the third indication information, or confirm that the SLPP message carrying the third indication information is the last message carrying the SLPP message body of the first transaction, they no longer expect to receive any SLPP message related to the first transaction, or any SLPP message carrying the SLPP message body related to the first transaction. In other words, when receiving any SLPP message of a transaction having the same transaction ID as the first transaction, or any SLPP message carrying the SLPP message body of a transaction having the same transaction ID as the first transaction, the SLPP will be regarded as an SLPP message of a new transaction.

[0255] In this embodiment, since the same transaction may involve multiple different participants, by receiving the SLPP message carrying 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 and multiple participants of the same transaction in determining the end of the transaction.

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

[0257] Figure 7 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Figure 7 As shown, the method is executed by the sending end, and the method may include the following steps:

[0258] Step 701: 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; the sending end is the initiator of the first transaction; and the participants of the first transaction are the UE group.

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

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

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

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

[0263] In some examples, the initiator of the first transaction autonomously determines to end the first transaction. In this example, the initiator of the first transaction can actively end the first transaction, that is, it can directly determine to receive the first transaction without the SLPP message carrying the second indication information sent by the participants of the first transaction.

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

[0265] 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 also includes a distinguishing mark, and the distinguishing mark is used to distinguish the third indication information and the transaction content in the message body.

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

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

[0268] The SLPP message sent by the sender in the first transaction can carry a transaction end indication when carrying a message body. This eliminates the need to construct a special message to carry a transaction end indication in addition to the SLPP message carrying the message body, thereby allowing the SLPP message to be reused and implemented simply.

[0269] In some examples, the transaction end indication may be carried in a SLPP message that does not include a 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.

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

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

[0272] 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 according to the third indication information carried by the SLPP message. This is conducive to improving the accuracy of the initiator and multiple participants of the same transaction in determining the end of the transaction.

[0273] Figure 8 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Figure 8As shown, the method is executed by the sending end, and the method may include the following steps:

[0274] 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 sender in the first transaction or the last message carrying the SLPP message body; wherein the participants in the first transaction are the UE group, and the sender is any UE involved in the first transaction.

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

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

[0277] 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 also includes a distinguishing mark, and the distinguishing mark is used to distinguish the fourth indication information and the transaction content in the message body.

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

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

[0280] 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 the implementation is simple.

[0281] In some examples, the transaction end indication may be carried in a SLPP message that does not include a 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.

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

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

[0284] In this embodiment, when the participants of the first transaction are a UE group and the sending end is any UE involved in the first transaction, the sending end sends an SLPP carrying the fourth indication information, so that when the receiving end receives the SLPP message carrying the fourth indication information from the sending end, it can confirm that the SLPP message is: the last message sent by the sending end in the first transaction or the last message carrying the SLPP message body. This is conducive to improving the accuracy of determining the end of the transaction by the initiator and multiple participants of the same transaction.

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

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

[0287] Fig. 9 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Fig. 9 As shown, the method is performed by a receiving end, and the method may include the following steps:

[0288] Step 901: Receive a 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.

[0289] 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 carrying the SLPP message body involved in the first transaction.

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

[0291] 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 first indication information, so that the receiving end (here, the receiving end is the participant of the first transaction) can determine that the first transaction is ended when it receives the first SLPP message.

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

[0293] 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 also includes a distinguishing mark, and the distinguishing mark is used to distinguish the first indication information and the transaction content in the message body.

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

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

[0296] The SLPP message of the first transaction can carry a transaction end indication when carrying a message body, and 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.

[0297] In some examples, the transaction end indication may be carried in a SLPP message that does not include a 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.

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

[0299] 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, the first transaction can be terminated directly according to the first indication information.

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

[0301] Fig.10 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Fig.10 As shown, the method is executed by receiving, and the method may include the following steps:

[0302] 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 participants in the first transaction are a UE group, and the sending end is a UE in the UE group.

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

[0304] 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 also includes a distinguishing mark, and the distinguishing mark is used to distinguish the second indication information and the transaction content in the message body.

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

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

[0307] 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 the implementation is simple.

[0308] In some examples, the transaction end indication may be carried in a SLPP message that does not include a 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.

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

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

[0311] In this embodiment, when the receiving end is the initiator of the first transaction, after receiving the SLPP message carrying the second indication information, it can be confirmed that the SLPP message is: the last message sent by the sending end in the first transaction or the last message carrying the SLPP message body. This is conducive to improving the accuracy of the initiator and multiple participants of the same transaction in determining the end of the transaction.

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

[0313] Fig.11 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Fig.11 As shown, the method is performed by a receiving end, and the method may include the following steps:

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

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

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

[0317] In this embodiment, by receiving the SLPP message carrying the third indication information sent by the initiator of the first transaction, the participants of the first transaction no longer expect to receive any SLPP message related to the first transaction or any SLPP message carrying the SLPP message body related to the first transaction after confirming the completion of the first transaction according to the third indication information, or confirming that the SLPP message carrying the third indication information is the last message carrying the SLPP message body of the first transaction. In other words, when the participants of the first transaction receive any SLPP message of a transaction having the same transaction ID as the first transaction or any SLPP message carrying the SLPP message body of a transaction having the same transaction ID as the first transaction, the SLPP will be regarded as an SLPP message of a new transaction.

[0318] 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 and multiple participants of the same transaction in determining the end of the transaction.

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

[0320] Fig.12 FIG. 1 is a flowchart of an information processing method according to an exemplary embodiment. Fig.12 As shown, the method is executed by receiving, and the method may include the following steps:

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

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

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

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

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

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

[0327] In order to further explain any embodiments of the present disclosure, some specific embodiments are provided below.

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

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

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

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

[0332] 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).

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

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

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

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

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

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

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

[0340] 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 message for session establishment. The SLPP group ID is created by the session initiator and provided to the session participants via a message for session establishment.

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

[0342] 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 a SLPP broadcast ID.

[0343] 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 through a message for session establishment. The SLPP broadcast ID is created by the session initiator and provided to the session participants through a message for session establishment.

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

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

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

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

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

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

[0350] 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 a SLPP message body, the UE adds an end transaction indication (eg, end transaction) in the SLPP message.

[0351] 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 SLPP message currently sent is the last message of the transaction for the UE, or the last message carrying the SLPP message body.

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

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

[0354] 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).

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

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

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

[0358] In some examples, after confirming that the transaction is over, or confirming that it is the last message carrying the SLPP body of the transaction, the UE no longer expects to receive any SLPP message of the transaction, or any SLPP message carrying the SLPP body of the transaction. That is, the UE will treat any received SLPP message with the same transaction ID, or any SLPP message carrying the SLPP body with the same transaction ID, as an SLPP message of a new SLPP transaction.

[0359] 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 packet body of the transaction.

[0360] In some examples, after confirming that the transaction is over, or confirming that it is the last message carrying the SLPP body of the transaction, the UE no longer expects to receive any SLPP message of the transaction, or any SLPP message carrying the SLPP body of the transaction. That is, the UE will treat any received SLPP message with the same transaction ID, or any SLPP message carrying the SLPP body with the same transaction ID, as an SLPP message of a new SLPP transaction.

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

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

[0363] Fig.13 FIG. 1 is a schematic diagram showing the structure of an information processing device according to an exemplary embodiment. Fig.13 As shown, the information processing device 100 includes:

[0364] The sending module 110 is configured as a sending module, configured to send a 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.

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

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

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

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

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

[0370] The application layer ID of the initiator;

[0371] The SLPP UE ID of the initiator.

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

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

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

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

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

[0377] The application layer ID of the participant;

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

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

[0380] The group ID of the UE group;

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

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

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

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

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

[0386] A list of source layer 2 IDs of the participants;

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

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

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

[0390] In some embodiments, 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;

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

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

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

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

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

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

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

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

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

[0400] the last SLPP message involved in the first transaction;

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

[0402] 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:

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

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

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

[0406] In some embodiments, the participants of 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, 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. Regarding the information processing device 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 executed by the sender, and will not be elaborated here.

[0407] Fig.14 FIG. 1 is a schematic diagram showing the structure of an information processing device according to an exemplary embodiment. Fig.14 As shown, the information processing device 200 includes:

[0408] The receiving module 210 is configured to receive a 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.

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

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

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

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

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

[0414] The application layer ID of the initiator;

[0415] The SLPP UE ID of the initiator.

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

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

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

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

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

[0421] The application layer ID of the participant;

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

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

[0424] The group ID of the UE group;

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

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

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

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

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

[0430] A list of source layer 2 IDs of the participants;

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

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

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

[0434] In some embodiments, 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;

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

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

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

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

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

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

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

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

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

[0444] the last SLPP message involved in the first transaction;

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

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

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

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

[0449] The first determining module is configured to determine, in response to receiving the SLPP message carrying the third indication information, 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.

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

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

[0452] Regarding the information processing device 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.

[0453] The present disclosure provides a communication device, including:

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

[0455] Processor, respectively memory connection;

[0456] Among them, the processor is configured to execute the information processing method provided by any of the aforementioned technical solutions.

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

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

[0459] The processor may be connected to the memory via a bus or the like, and may be used to read an executable program stored in the memory, for example, to implement the information processing method provided by any of the aforementioned embodiments.

[0460] An embodiment of the present disclosure provides a computer storage medium, which stores an executable program; after the executable program is executed by a processor, the information processing method provided by any of the above-mentioned technical solutions can be implemented.

[0461] Fig.15 800 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.

[0462] Reference Fig.15 The 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 .

[0463] The processing component 802 generally controls the overall operation of the terminal 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to generate all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0464] The memory 804 is configured to store various types of data to support operations at 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 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as a static random access memory (SRAM), an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a programmable read-only memory (PROM), a read-only memory (ROM), a magnetic memory, a flash memory, a magnetic disk, or an optical disk.

[0465] Power component 806 provides power to various components of terminal 800. Power 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.

[0466] 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 touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the 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 may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

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

[0468] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0469] 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 the components, such as the display and keypad of the terminal 800, and the sensor assembly 814 can also detect the position change of the terminal 800 or a component of the terminal 800, the presence or absence of contact between the user and the terminal 800, the orientation or acceleration / deceleration of the terminal 800, and the temperature change 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 acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

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

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

[0472] 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 a processor 820 of the terminal 800 to generate 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.

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

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

[0475] It should be understood that the present invention is not limited to the exact construction that has been 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: Sending a sidelink positioning protocol SLPP message; wherein the SLPP message includes a transaction identifier of the first transaction, and the transaction identifier is used to determine the initiator of the first transaction; Sending an SLPP message carrying indication information; wherein the indication information is used to indicate that the SLPP message carrying the indication information is the last message of the sender in the first transaction or the last message carrying the SLPP message body.

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

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

4. The method according to claim 1, wherein: The transaction identifier also includes: The second identifier 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 identifier includes at least one of the following: The source layer 2 identifier of the participant; The destination layer 2 identifier of the participant; The application layer identifier of the participant; The SLPP user equipment UE identifier of the participant.

6. The method according to claim 4, wherein: The participant is a UE group, and the second identifier includes at least one of the following: A group identifier of the UE group; The source layer 2 multicast identifier of the UE group; The destination layer 2 multicast identifier of the UE group; The application layer group identifier of the UE group; The SLPP UE group identifier of the UE group.

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

8. The method according to claim 4, wherein: The first transaction is created in a broadcast mode, and the second identifier includes: at least one of a source end layer 2 broadcast identifier, a destination end layer 2 broadcast identifier, and an SLPP broadcast identifier of the participant; or, The participant of the first transaction is a UE or a UE group, and the transaction identifier includes the second identifier; or, The first transaction is created in a broadcast mode, and the transaction identifier does not include the second identifier.

9. The method according to any one of claims 1 to 8, wherein: The transaction identifier of the first transaction is different from the transaction identifier 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 identifier 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 8, wherein: The number of UEs involved in the first transaction is less than or equal to two.

12. The method according to any one of claims 1 to 8, wherein: The participants of the first transaction are a UE group, and the sending end is a UE in the UE group.

13. The method according to any one of claims 1 to 8, wherein: The participants of the first transaction are a UE group, and the sender is any UE involved in the first transaction.

14. An information processing method, wherein: Executed by the receiving end, the method includes: Receiving a sidelink positioning protocol SLPP message; wherein the SLPP message includes a transaction identifier of a first transaction, and the transaction identifier is used to determine an initiator of the first transaction; Receive an SLPP message carrying indication information; wherein the indication information is used to indicate that the SLPP message carrying the indication information is the last message of the sender in the first transaction or the last message carrying the SLPP message body.

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

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

17. The method according to claim 14, wherein: The transaction identifier also includes: The second identifier is used to indicate a participant of the first transaction.

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

19. The method according to claim 17, wherein: The participant is a UE group, and the second identifier includes at least one of the following: A group identifier of the UE group; The source layer 2 multicast identifier of the UE group; The destination layer 2 multicast identifier of the UE group; The application layer group identifier of the UE group; The SLPP UE group identifier of the UE group.

20. The method according to claim 17, wherein: The participant is a UE group, and the second identifier includes at least one of the following: A list of source layer 2 identifiers of the participants; The destination layer 2 identifier list of the participants; A list of application layer identifiers of the participants; A list of SLPP UE identities of the participants.

21. The method according to claim 17, wherein: The first transaction is created in a broadcast mode, and the second identifier includes: at least one of a source end layer 2 broadcast identifier, a destination end layer 2 broadcast identifier, and an SLPP broadcast identifier of the participant; or, The participant of the first transaction is a UE or a UE group, and the transaction identifier includes the second identifier; or, The first transaction is created in a broadcast mode, and the transaction identifier does not include the second identifier.

22. The method according to any one of claims 14 to 21, wherein: The transaction identifier of the first transaction is different from the transaction identifier of the second transaction, and the first transaction and the second transaction are parallel transactions in the same session.

23. The method according to claim 22, 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 identifier includes a transaction number, and the transaction number of the first transaction is different from the transaction number of the second transaction.

24. The method according to any one of claims 14 to 21, wherein: The number of UEs involved in the first transaction is less than or equal to two.

25. The method according to any one of claims 14 to 21, wherein: The participants of the first transaction are a UE group, and the receiving end is an initiator of the first transaction.

26. The method according to any one of claims 14 to 21, wherein: The participants of the first transaction are a UE group, and the SLPP message carrying the indication information is sent by all other UEs involved in the first transaction except the receiving end.

27. An information processing device, wherein: The device comprises: A sending module is configured to send a Side Link Positioning Protocol (SLPP) message; wherein the SLPP message includes a transaction identifier of a first transaction, and the transaction identifier is used to determine the initiator of the first transaction; and send a SLPP message carrying indication information; wherein the indication information is used to indicate that the SLPP message carrying the indication information is the last message of the sender in the first transaction or the last message carrying the SLPP message body.

28. An information processing device, wherein: The device comprises: A receiving module is configured to receive a Side Link Positioning Protocol (SLPP) message; wherein the SLPP message includes a transaction identifier of a first transaction, and the transaction identifier is used to determine the initiator of the first transaction; receive an SLPP message carrying indication information; wherein the indication information is used to indicate that the SLPP message carrying the indication information is the last message of the sender in the first transaction or the last message carrying the SLPP message body.

29. 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, it executes the information processing method provided by any one of claims 1 to 13 or 14 to 26.

30. 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 13 or 14 to 26.