Information processing method and device, communication equipment and storage medium

Abstract

The embodiment of the invention provides an information processing method and device, communication equipment and a storage medium. The method executed by a sender comprises the following steps: sending an SLPP (Lateral Location Protocol) message, wherein the SLPP message comprises a first session identifier; wherein the first session identifier is used for identifying a session and determining an initiator of the session.

Description

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

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

[0002] Positioning between user equipment (UE) and UE can be achieved through the sidelink (SL). Positioning includes absolute positioning, relative positioning, and ranging. 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. The UE needs to request positioning based on a session.

[0003] 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 the present disclosure, an information processing method is provided, wherein the method is performed by a sender and includes:

[0006] A Sidelink Positioning Protocol (SLPP) message is sent, where the SLPP message includes a first session identifier, wherein the first session identifier is used to identify a session and determine an initiator of the session.

[0007] A second aspect of the present disclosure provides an information processing method, which is performed by a receiving party. The method includes:

[0008] A Sideline Positioning Protocol (SLPP) message is received, where the SLPP message includes a first session identifier, wherein the first session identifier is used to identify a session and determine an initiator of the session.

[0009] A third aspect of the present disclosure provides an information processing device, wherein the device includes:

[0010] The sending module is configured to send a Sideline Positioning Protocol (SLPP) message, where the SLPP message includes a first session identifier, wherein the first session identifier is used to identify a session and determine an initiator of the session.

[0011] A fourth aspect of the present disclosure provides an information processing device, wherein the device includes:

[0012] The receiving module is configured to receive a Sidelink Positioning Protocol (SLPP) message, where the SLPP message includes a first session identifier, wherein the first session identifier is used to identify a session and determine an initiator of the session.

[0013] A fifth aspect of an embodiment of the present disclosure provides 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 the processor executes the information processing method provided in the first or second aspect above when running the executable program.

[0014] A sixth aspect of the embodiments of the present disclosure provides a computer storage medium storing an executable program; after the executable program is executed by a processor, the information processing method provided in the first or second aspect can be implemented.

[0015] The technical solution provided by the embodiments of the present disclosure can determine the session identifier and the session initiator of a session based on an SLPP message carrying a first session identifier. This can reduce situations where multiple participants are unable to distinguish the session initiator when participating in a session, or where different participants in the same session determine different initiators, thereby improving the accuracy of information exchange during the session. Because the first session identifier can more accurately distinguish the session initiator, positioning using SLPP messages carrying the first session identifier can also improve positioning accuracy.

[0016] The technical solutions provided by the embodiments of the present disclosure should be understood that the above general description and the following detailed description are merely exemplary and explanatory and cannot limit the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0020] FIG2A is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0021] FIG2B is a schematic flow chart of an information processing method according to an exemplary embodiment;

[0022] FIG2C is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0023] FIG3A is a schematic flow chart showing an information processing method according to an exemplary embodiment;

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

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

[0026] FIG3D is a schematic flow chart of an information processing method according to an exemplary embodiment;

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

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

[0029] FIG5A is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0030] Fig. 5B is a schematic structural diagram showing a network device according to an exemplary embodiment. DETAILED DESCRIPTION

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

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

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

[0034] Please refer to Figure 1A, which shows a schematic diagram of the structure of a wireless communication system provided by an embodiment of the present disclosure. As shown in Figure 1A, the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: several UEs 11, one or more access devices 12, and one or more core network devices 13.

[0035] UE 11 may refer to a device that provides voice and / or data connectivity to a user. UE 11 may communicate with one or more core networks via a Radio Access Network (RAN). UE 11 may be an IoT UE, such as a sensor device, a mobile phone (or "cellular" phone), and a computer with an IoT UE. For example, it may 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 terminal, an access terminal, a user terminal, a user agent, a user device, or user equipment (UE). Alternatively, UE 11 may be a device of an unmanned aerial vehicle. Alternatively, UE 11 may be an in-vehicle device, such as a driving computer with wireless communication capabilities, or a wireless communication device connected to an external driving computer. Alternatively, the UE 11 may also be a roadside device, for example, a street lamp, a traffic light, or other roadside device with a wireless communication function.

[0036] The access device 12 may be a network-side device in a wireless communication system. The wireless communication system may be a fourth generation mobile communication technology (4G) system, also known as a long term evolution (LTE) system; or, the wireless communication system may be a 5G system, also known as a new radio (NR) system or a 5G NR system. Alternatively, the wireless communication system may be a next generation system of the 5G system. The access network in the 5G system may be referred to as NG-RAN (New Generation-Radio Access Network). Alternatively, an MTC system.

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

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

[0039] The core network device 13 can be connected to the access device 12. Typical core network devices may include but are not limited to: Access Management Function (AMF), Session Management Function (SMF), User Data Management (UDM), and Policy Control Function (PCF).

[0040] Please refer to FIG. 1B , which shows a schematic structural diagram of a downlink time difference of arrival (DL-TDOA) based positioning framework provided by an embodiment of the present disclosure.

[0041] As shown in Figure 1B, the UE can determine the specific position of the UE relative to the RSU by measuring multiple road side units (RSU, RSU is greater than or equal to 3) and the positioning signal (sidelink Positioning Reference Signal, SL PRS) sent by the sidelink link. In addition to DL-TDOA, positioning solutions also include 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. 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, it is absolute positioning. The UE being positioned is the target UE (target UE), and other UEs that support positioning the target UE (target UE) are anchor UEs (anchor UE).

[0042] If positioning involves only two UEs, the two UEs are each other's anchor UEs.

[0043] There are different types of anchor UEs, such as RSU-type anchor UEs. RSU-type anchor UEs are a type of infrastructure that can provide positioning services by collaborating with other RSUs. For example, ordinary UEs can also serve as anchor UEs, but ordinary UEs are unlikely 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 GPS or other location information.

[0044] The protocols for exchanging positioning messages between two UEs include the Sidelink Positioning Protocol (also known as the Sidelink Positioning Protocol or Sidelink LPP, SLPP) or the Ranging and Sidelink Positioning Protocol (RSPP). Currently, the 3GPP (3rd Generation Partnership Project) has not yet determined whether the SLPP or RSPP protocols will be located above the PC5-S (PC5-Signalling), PC5-U (PC5 user plane), PC5-RRC (PC5 Radio Resource Control), or the PDCP (Packet Data Convergence Protocol) layer.

[0045] When a UE requests positioning, it needs to be done through a session, for example, creating an LTE (Long Term Evolution) positioning protocol LPP session (LTE positioning protocol, LPP session). An LPP session generally involves two nodes, for example, a UE and a location management function (LMF). The LPP session distinguishes the session initiator by the node type in the session ID. For example, the session ID indicates that the initiator is a server-type node, or the session ID indicates that the initiator is a client-type node. This session mode supports the case where the number of nodes is two. If the number of nodes exceeds two, the initiator cannot be distinguished by the node type. For example, if a session includes two UEs and an LMF. If the node whose node type is client indicated by the session ID is the initiator of the session, then this initiator may refer to either of the two UEs.

[0046] For a session with more than two nodes, in addition to the session initiator, there will be two or more participants in the session.

[0047] When there are more than two participants, the session ID in the LPP session cannot simply use the server or client to distinguish the initiator. In addition, in some scenarios, other participants besides the initiator must also be considered.

[0048] Furthermore, LPP sessions support multiple transactions within a session. However, because an LPP session involves only two nodes, the session is considered terminated when the last transaction completes. However, with SLPP, more than three parties may participate in a session, and transactions may be established between different parties in the same session. In this case, a participant cannot determine whether the last transaction has completed. Therefore, it is necessary to consider how to terminate a multi-party session.

[0049] As shown in FIG2A , an embodiment of the present disclosure provides an information processing method, which is performed by a sender and includes:

[0050] S1110: Send a Sidelink Positioning Protocol (SLPP) message, where the SLPP message includes a first session identifier, wherein the first session identifier is used to identify a session and determine an initiator of the session.

[0051] Exemplarily, the sender may be the initiator of the session and / or a participant in the session other than the initiator.

[0052] Exemplarily, the participants include user equipment UE, road side unit RSU, etc.

[0053] In some embodiments, the initiator of the session may be a target UE (target UE) that needs to be positioned, and the participants other than the initiator may be anchor UEs (anchor UEs) that provide positioning services.

[0054] In some embodiments, the initiator of the session may be an anchor UE (anchor UE), and other participants except the initiator may be target UEs (target UEs) that need to be located.

[0055] In some embodiments, all participants in the session are UEs. In other embodiments, some participants in the session may include but are not limited to RSUs.

[0056] In some embodiments, step S1110 includes: UE A sends a Sidelink Positioning Protocol (SLPP) message to UE B. UE B may include one or more UEs.

[0057] In some embodiments, the SLPP message may be a message in a session creation process. Exemplarily, the SLPP message may include a session creation request message for a session corresponding to the first session identifier. Exemplarily, the session is an SLPP session based on the SLPP protocol.

[0058] For example, an SLPP message may include at least one of an SLPP session creation request message, an SLPP session creation completion message, and an SLPP message carrying session content. After a session is established, the participants in the session can communicate based on the established session. During communication, SLPP messages may be sent based on SLPP. The SLPP message may include session content.

[0059] If the SLPP message is a session creation request message, the sender is the initiator of the session.

[0060] The SLPP message carrying the first session identifier can be used to determine the session identifier and the session initiator. This can reduce situations where multiple participants are unable to distinguish the session initiator, or where different participants in the same session determine different initiators, thereby improving the accuracy of information exchange during the session. Because the first session identifier can more accurately distinguish the session initiator, positioning using the SLPP message carrying the first session identifier can also improve positioning accuracy.

[0061] In some embodiments, the number of participants in the session indicated by the first session identifier is equal to or greater than three.

[0062] In some embodiments, the first session identifier includes: a first ID indicating an initiator of the session.

[0063] In the embodiment of the present disclosure, the ID in the first ID may be represented as a UE ID. The first ID is the UE ID of the initiator.

[0064] The UE ID is used to distinguish different participants in a conversation. For example, the UE ID can be a unique identifier for each participant in the conversation. Therefore, different participants can determine the unique initiator based on the UE ID, thereby improving the accuracy of information exchange in the conversation.

[0065] The first session identifier includes the first ID, so the receiver of the SLPP message can know the initiator of the session identified by the first session identifier according to the first session identifier carried in the SLPP message.

[0066] In some embodiments, the portion corresponding to the specified position of the first session identifier is the first ID. Exemplarily, the first ID can be a string consisting of a plurality of characters distributed continuously from the start position of the first session identifier. In another exemplary embodiment, the first ID can be a string consisting of a plurality of characters distributed continuously from the end position of the first session identifier forward. Furthermore, in another exemplary embodiment, the first ID can be a string consisting of a plurality of characters distributed continuously from any intermediate position in the first session identifier.

[0067] In summary, in the embodiment of the present disclosure, the character string formed by the first ID is used as a substring formed by multiple consecutively distributed characters in the first session identifier, which facilitates rapid decoding by subsequent recipients.

[0068] In the same session, different participants have different UE IDs.

[0069] The UE ID of the same participant can be the same in different sessions.

[0070] In some embodiments, the first session identifier further includes:

[0071] The second ID indicates the participant of the conversation.

[0072] Exemplarily, the second ID indicates the UE ID of the participant.

[0073] Using the second ID, the recipient of the SLPP message can determine whether it is a session participant indicated by the first session identifier carried in the SLPP message. This SLPP message that specifies session participants allows the sender of the SLPP message to select session participants based on session needs. For example, when using SLPP messages for positioning: some UEs have absolute location information, while others do not. If a session participant that needs to be located needs absolute location positioning, the second ID can be used to specify the UE with absolute location information as a participant.

[0074] In some embodiments, the portion of the first session identifier corresponding to a specified position is the second ID. Exemplarily, the second ID can be a string consisting of a plurality of characters distributed continuously from the start position of the first session identifier. In another exemplary embodiment, the second ID can be a string consisting of a plurality of characters distributed continuously from the end position of the first session identifier forward. Furthermore, in another exemplary embodiment, the second ID can be a string consisting of a plurality of characters distributed continuously from any intermediate position in the first session identifier.

[0075] In summary, in the embodiment of the present disclosure, the character string formed by the second ID is used as a substring formed by multiple consecutively distributed characters in the first session identifier, which facilitates rapid decoding by subsequent recipients.

[0076] For example, if the first session identifier includes a first ID and a second ID, the first ID may be arranged before the second ID so that the recipient can more quickly unlock the first ID to determine the initiator.

[0077] The first session identification may or may not include the second ID.

[0078] In some embodiments, the session is created in a broadcast mode, and the first session identifier includes the second ID.

[0079] If a session is created in broadcast mode, there will be many SLPP message recipients. These recipients can determine whether they are a participant in the session identified by the SLPP message based on the second ID. If a recipient determines that it is a participant in the session, it joins the session identified by the SLPP message. If a recipient determines that it is not a participant in the session, it ignores the SLPP message.

[0080] For example, if one or more nodes around the target UE have their own location information, these nodes can serve as anchor UEs. Therefore, carrying the second ID in the first session identifier indicates that the anchor UE is included as a participant, which can improve the efficiency and accuracy of positioning the target UE.

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

[0082] Exemplarily, if the first session identifier does not carry the second ID, the receiver of the SLPP message can determine whether it is a participant in the session indicated by the first session identifier through the broadcast identifier.

[0083] This method of distinguishing participants by broadcast identification rather than second ID is more suitable for scenarios with fewer participants.

[0084] In some embodiments, the broadcast identifier includes at least one of the following:

[0085] The participant's source layer 2 broadcast ID (source 2 broadcast ID);

[0086] The destination Layer 2 broadcast ID of the participant;

[0087] SLPP user equipment broadcast ID of the participant.

[0088] In some embodiments, the number of participants in the session is less than a specified threshold, and the first session identifier includes the second ID.

[0089] Exemplarily, the specified threshold is a small number such as three or four.

[0090] When the number of participants in a session is less than a specified threshold, the first session identifier, including the second ID, can select an appropriate UE as a participant for positioning, which can reduce the complexity of positioning and improve the efficiency and accuracy of positioning. For example, if there are two participants in a session, the target UE-1, as the sender, indicates the target UE-1 as the initiator of the session through the first ID, and indicates the anchor UE-2, whose own location information is known, as a participant through the second ID. At this time, by determining the distance between the anchor UE-2 and the target UE-1 (ranging) and the location information of the anchor UE-2, the absolute position of the target UE-1 can be determined.

[0091] In some embodiments, the participants in the session other than the initiator are a UE group, and the first session identifier includes a second ID, where the second ID is a group ID of the UE group.

[0092] Compared to a single UE, a UE group includes one or more UEs. A UE group-based conversation can enable multi-party conversations and / or positioning when the UE group includes multiple UEs. Using a UE group to locate the initiator can improve positioning accuracy, while having the initiator locate the UE group can improve positioning efficiency.

[0093] In some embodiments, the session is created in a broadcast mode and the session creation request message includes a broadcast identifier, and the first session identifier does not include the second ID; the broadcast identifier is an identifier of the broadcast creation request message known to all participants.

[0094] Exemplarily, if the first session identifier does not carry the second ID, the receiver of the SLPP message can determine whether it is a participant in the session indicated by the first session identifier through the broadcast identifier.

[0095] This method of distinguishing participants by broadcast identification rather than a second ID is more suitable for scenarios with fewer participants.

[0096] In some embodiments, the broadcast identifier includes at least one of the following:

[0097] The source layer 2 broadcast ID of the initiator;

[0098] Destination Layer 2 broadcast ID of the initiator;

[0099] The initiator's SLPP user equipment broadcast ID;

[0100] The serial number of the message broadcast by the initiator;

[0101] The participant's source layer 2 broadcast ID (source 2 broadcast ID);

[0102] The destination Layer 2 broadcast ID of the participant;

[0103] SLPP user equipment broadcast ID of the participant.

[0104] In some embodiments, the first session identifier further includes: a session number;

[0105] Different sessions initiated by the same initiator have different session numbers, and / or different sessions participated in by the same participant have different session numbers.

[0106] For example, the session number may be the serial number of all sessions created by the initiator, or the serial number of the SLPP session created by the initiator. Therefore, different sessions may have different session numbers.

[0107] In some embodiments, different SLPP messages within the same session use the same session number.

[0108] In some embodiments, the first session identifier may include other components in addition to the first ID and the session number. For example, the first session identifier may include one or more of the following related information: the number of participants in the session identified by the first session identifier, the device types of the participants, the protocol version number of the SLPP protocol, and so on.

[0109] In some embodiments, the participants relate to a UE group, and the same participants include the same UE group ID and / or Layer 2 group ID of the participants.

[0110] Exemplarily, the layer 2 group ID includes a source layer 2 group ID and / or a destination layer 2 group ID.

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

[0112] The source Layer 2 ID of the initiator;

[0113] Destination Layer 2 ID of the initiator;

[0114] The application layer ID of the initiator;

[0115] SLPP User Equipment UE ID (SLPP UE ID) of the initiator.

[0116] In some embodiments, the second ID includes 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 participants other than the initiator are a UE group of the session, and the second ID includes at least one of the following:

[0122] 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 the embodiment of the present disclosure, the UE group whose participants are the session includes: the UE group whose participants other than the initiator are the session.

[0128] In some embodiments, the participants other than the initiator are a UE group of the session, and the second ID further includes at least one of the following:

[0129] The source layer 2 ID in the UE group's source layer 2 ID list;

[0130] Destination layer 2 ID in the destination layer 2 ID list of the UE group;

[0131] Application layer ID in the application layer ID list of the UE group;

[0132] SLPP user equipment UE ID in the SLPP user equipment UE ID list of the UE group; wherein the participant is a participant in the session.

[0133] In some embodiments, the number of participants involved in the session is greater than two, and the session has a first session identifier.

[0134] If the session involves different UEs, that is, all participants are UEs, then the number of UEs involved in the session is greater than two, and the session has a first session identifier.

[0135] Based on the SLPP message carrying the first session identifier, it is possible to determine which of three or more participants is the session initiator. This reduces the situation where multiple participants cannot distinguish the session initiator, or different participants in the same session identify different initiators, thereby improving the accuracy of information exchange during the session. Because the first session identifier can more accurately distinguish the session initiator, positioning using the SLPP message carrying the first session identifier can also improve positioning accuracy.

[0136] In some embodiments, the number of parties involved in the session is less than or equal to two, and the session has a second session identifier;

[0137] A second session identifier, used to identify the second session;

[0138] The type information and the second session identifier carried in the SLPP message are used to determine the initiator of the session.

[0139] If the session involves different UEs, that is, all participants are UEs, then the number of UEs involved in the session is less than or equal to two, and the session has a second session identifier.

[0140] The type information includes the type of UE.

[0141] Exemplarily, the type information includes client and server.

[0142] If a session involves two UEs and the number of participants is small, the type information can be used to distinguish the two different UEs. For example, the server can be used to indicate that the server UE is the initiator, or the client can be used to indicate that the client UE is the initiator.

[0143] When there are two participants in a conversation, the initiator of the conversation can be distinguished by type information, which can improve compatibility with related technologies.

[0144] In some embodiments, in response to the session initiator being a participant with set type information, the type information and the second session identifier carried in the SLPP message are used to determine the session initiator.

[0145] For sessions with two or more participants, there may be only one participant of a specific type. If this participant of a specific type serves as the session initiator, using specific type information to distinguish the initiator can improve compatibility with related technologies. Exemplarily, participants with type information include participants of client type. For example, if the session initiator is a client UE, the SLPP message carries client type information to indicate that the client UE is the initiator of the session.

[0146] As shown in FIG2B , an embodiment of the present disclosure provides an information processing method, which is performed by a sender and includes:

[0147] S1210: In response to determining to end the session, send indication information; the indication information is used to end the session (end session).

[0148] Exemplarily, the sender may be the initiator of the session and / or a participant in the session other than the initiator.

[0149] Exemplarily, the participants include user equipment UE or road side unit RSU, etc.

[0150] In some embodiments, the initiator of the session may be a target UE (target UE) that needs to be positioned, and the participants other than the initiator may be anchor UEs (anchor UEs) that provide positioning services.

[0151] In some embodiments, the initiator of the session may be an anchor UE (anchor UE), and other participants except the initiator may be target UEs (target UEs) that need to be located.

[0152] In some embodiments, all participants in the session are UEs. In other embodiments, some participants in the session may include but are not limited to RSUs.

[0153] In some embodiments, the sender is the initiator of the session, and step S1210 includes: the initiator of the session sends indication information to participants other than the initiator.

[0154] In some embodiments, the number of participants in a session is two. Even if multiple transactions are supported within a session, these transactions all involve these two participants, so any participant can know that the end of the last transaction of the session means the end of the session.

[0155] In some embodiments, if the participants in the session other than the initiator are a group of UEs (i.e., a UE group), and all transactions in the session involve this group of UEs, the initiator can determine that the session is over after determining that the last transaction in the session is completed.

[0156] All participants in a session, except the initiator, are a UE group, and all transactions within the session involve the initiator and this UE group. Even if a session supports multiple transactions, these transactions all involve the initiator and the UE group, so any participant can know that the end of the session means the end of the last transaction.

[0157] In other embodiments, the session is terminated based on the session result. For example, if the session result indicates that the initiator has obtained a location estimate, it indicates that the session can be terminated.

[0158] In some embodiments, the participants in the session other than the initiator are a UE group, and the initiator sends indication information to the UE group.

[0159] In the embodiment of the present disclosure, the session may be ended using an indication message, or the session may be ended automatically without sending an indication message.

[0160] If a session involves more than two participants, since a session involves multiple transactions and different transactions involve different session participants, the participants cannot determine which transaction is the last transaction. Therefore, it is necessary to end the session through an indication message.

[0161] Exemplarily, the indication information is broadcast or multicast to the participants of the session.

[0162] As another example, after a participant receives the instruction information, it forwards the instruction information to other participants according to the transaction in which it participates, until all participants receive the instruction information.

[0163] If a session involves two parties, even if the session involves multiple transactions, the two parties involved in these transactions are the same. Therefore, any party knows which transaction is the last transaction, so there is no need to end the session using indication information.

[0164] If a session involves more than two participants, and all but the initiator belong to a single UE group, and all transactions in the session involve this single UE group, the sender or UE group can know which transaction is the last and can terminate the session after the last transaction. There is no need to use an indication message to terminate the session.

[0165] A transaction may be established between different participants in the same conversation. Through an indication message, any participant in the conversation can be informed that the conversation can be ended, thus achieving accurate determination of the end of the conversation when three or more participants are involved.

[0166] In some embodiments, the SLPP message carrying the session content carries indication information.

[0167] Exemplarily, the last SLPP message of the session carries the indication information, and the SLPP message is originally intended to be used for transmitting the session content. By carrying the indication message, after the transmission of the SLPP message is completed, all participants will end the session.

[0168] Exemplarily, the session content is carried in the SLPP message body, and the indication information is carried in the message header or message body of the SLPP message. If the indication information and the session content are both carried in the message body, the message body also includes a distinguishing mark, which is used to distinguish the marking area indication information from the session content.

[0169] Exemplarily, the indication information may be an end marker, for example, the end marker is “end session”; or, the indication information may be a bit sequence indicating the end.

[0170] The SLPP message carries both session content and indication information. There is no need to construct a special message to carry indication information in addition to the SLPP message that carries the session content. The SLPP message is reused, which is easy to implement.

[0171] In some embodiments, the SLPP message that does not carry session content carries indication information.

[0172] Here, carrying the indication information through an SLPP message that does not carry session content can be understood as indicating the end of the session through a dedicated SLPP message.

[0173] For example, after the last SLPP message carrying the session content is transmitted, the SLPP message carrying the indication information is sent.

[0174] Exemplarily, the indication information may be an end marker, or the indication information may be a bit sequence indicating the end.

[0175] Exemplarily, the indication information may be carried in a message header of the SLPP message or in a message body of the SLPP message.

[0176] In some embodiments, the indication information may be carried in a unicast, multicast, or broadcast manner through an SLPP message carrying session content, or the indication information may be carried in an SLPP message not carrying session content.

[0177] In some embodiments, the SLPP message carrying the indication information does not have an SLPP message body; the SLPP message body is used to carry the session content.

[0178] The message header of the SLPP message may be used to carry the indication information.

[0179] Such an SLPP message without an SLPP message body can shorten the length of the SLPP message and simplify decoding.

[0180] In some embodiments, the SLPP message carrying the indication information has an SLPP message body; the content of the SLPP message body is empty, or the SLPP message body carries specified content. Exemplarily, the SLPP message body carries session content.

[0181] As shown in FIG2C , an embodiment of the present disclosure provides an information processing method, which is performed by a sender and includes:

[0182] S1310: In response to obtaining a session result of the session, determining that the session is ended.

[0183] Exemplarily, the session result may be the purpose of establishing the session. Exemplarily, if the purpose of establishing the session is to obtain location information, obtaining the location information may be considered as obtaining the session result. Furthermore, exemplarily, if the purpose of establishing the session is to deliver message content, the recipient may determine that the session has ended after the message content is delivered to the recipient.

[0184] For example, for absolute and / or relative ranging scenarios, the session result may include whether the participant requiring positioning has obtained a position estimate. For example, the session result may include whether the initiator requiring positioning has obtained a position estimate.

[0185] The technical solutions provided by the embodiments of the present disclosure can be implemented in conjunction with the methods shown in FIG. 2A and / or FIG. 2B . Specifically, the session identifier of the session can be a first session identifier that includes the first ID of the initiator. Alternatively, the session identifier of the session can be a component of the session identifier determined based on the number of participants in the session.

[0186] In some embodiments, the method shown in FIG. 2C can be implemented independently, that is, without relying on any of the aforementioned embodiments.

[0187] In some embodiments, the session is determined to be ended in response to the participant requiring positioning obtaining a position estimate.

[0188] In some embodiments, the session is determined not to have ended in response to a participant requiring positioning not obtaining a position estimate.

[0189] In some embodiments, after determining that the session is ended, the method further includes: sending indication information; the indication information is used to end the session (end session).

[0190] A transaction may be established between different participants in the same conversation. Through an indication message, any participant in the conversation can be informed that the conversation can be ended, thus achieving accurate determination of the end of the conversation when three or more participants are involved.

[0191] In some embodiments, the SLPP message carrying the session content carries indication information.

[0192] Exemplarily, the last SLPP message of the session carries the indication information, and the SLPP message is originally intended to be used for transmitting the session content. By carrying the indication message, after the transmission of the SLPP message is completed, all participants will end the session.

[0193] Exemplarily, the session content is carried in the SLPP message body, and the indication information is carried in the message header or message body of the SLPP message. If the indication information and the session content are carried in the message body at the same time, the message body also includes a distinguishing mark, which is used to distinguish the marking area indication information from the session content.

[0194] Exemplarily, the indication information may be an end marker, for example, the end marker is “end session”; or, the indication information may be a bit sequence indicating the end.

[0195] The SLPP message carries both session content and indication information. There is no need to construct a special message to carry indication information in addition to the SLPP message that carries the session content. The SLPP message is reused, which is easy to implement.

[0196] In some embodiments, the SLPP message that does not carry session content carries indication information.

[0197] Here, carrying the indication information through an SLPP message that does not carry session content can be understood as indicating the end of the session through a dedicated SLPP message.

[0198] For example, after the last SLPP message carrying the session content is transmitted, the SLPP message carrying the indication information is sent.

[0199] Exemplarily, the indication information may be an end marker, or the indication information may be a bit sequence indicating the end.

[0200] Exemplarily, the indication information may be carried in a message header of the SLPP message or in a message body of the SLPP message.

[0201] Exemplarily, the sender may be the initiator of the session, and / or a participant in the session other than the sender.

[0202] Exemplarily, the participants include user equipment UE or road side unit RSU, etc.

[0203] In some embodiments, the initiator of the session may be a target UE (target UE) that needs to be positioned, and the participant may be an anchor UE (anchor UE) that provides positioning services.

[0204] In some embodiments, the initiator of the session may be an anchor UE (anchor UE), and other participants except the initiator may be target UEs ((target UE)) that need to be located.

[0205] In some embodiments, all participants in the session are UEs.

[0206] In some embodiments, if the number of participants in the session exceeds two, or the participants in the session include a UE group, in response to obtaining a session result of the session, it is determined that the session is ended.

[0207] In other embodiments, the session is determined to be ended in response to the last transaction involved in the session ending.

[0208] For example, if there are two participants in a session, even if multiple transactions are supported within a session, these transactions all involve these two participants, so any participant can know that the end of the last transaction of the session means the end of the session.

[0209] For example, if there are multiple participants in a session, all of them belong to the same UE group, and all transactions of the session involve this UE group, in this case, any participant can also know that the end of the last transaction of the session means the end of the session.

[0210] As shown in FIG3A , an embodiment of the present disclosure provides an information processing method, which is executed by a receiving party and includes:

[0211] S2110: Receive a Sidelink Positioning Protocol (SLPP) message, where the SLPP message includes a first session identifier, wherein the first session identifier is used to identify a session and determine an initiator of the session.

[0212] Exemplarily, the recipient may be the initiator of the session and / or a participant in the session other than the initiator.

[0213] Exemplarily, the participants include user equipment UE or road side unit RSU, etc.

[0214] In some embodiments, the initiator of the session may be a target UE (target UE) that needs to be positioned, and the participant may be an anchor UE (anchor UE) that provides positioning services.

[0215] In some embodiments, all participants in the session are UEs. In other embodiments, some participants in the session may include but are not limited to RSUs.

[0216] In some embodiments, step S2110 includes: UE B receiving a Sidelink Positioning Protocol (SLPP) message sent by UE A. UE B may include one or more UEs.

[0217] In some embodiments, the SLPP message may be a message in a session creation process. Exemplarily, the SLPP message may include a session creation request message for a session corresponding to the first session identifier. Exemplarily, the session is an SLPP session based on the SLPP protocol.

[0218] For example, an SLPP message may include at least one of an SLPP session creation request message, an SLPP session creation completion message, and an SLPP message carrying session content. After a session is established, the participants in the session can communicate based on the established session. During communication, SLPP messages may be sent based on SLPP. The SLPP message may include session content.

[0219] If the SLPP message is a session creation request message, the sender is the initiator of the session.

[0220] The SLPP message carrying the first session identifier can be used to determine the session identifier and the session initiator. This can reduce situations where multiple participants are unable to distinguish the session initiator, or where different participants in the same session determine different initiators, thereby improving the accuracy of information exchange during the session. Because the first session identifier can more accurately distinguish the session initiator, positioning using the SLPP message carrying the first session identifier can also improve positioning accuracy.

[0221] In some embodiments, the number of participants in the session indicated by the first session identifier is equal to or greater than three.

[0222] In some embodiments, the first session identifier includes: a first ID indicating an initiator of the session.

[0223] In the embodiment of the present disclosure, the ID in the first ID may be represented as a UE ID. The first ID is the UE ID of the initiator.

[0224] The UE ID is used to distinguish different participants in a session. In other words, the UE ID can distinguish different participants.

[0225] For example, the UE ID can be a unique identifier for a participant in a session. Therefore, different participants can determine the unique initiator based on the UE ID, thereby improving the accuracy of information exchange in the session.

[0226] The first session identifier includes the first ID, so the receiver of the SLPP message can know the initiator of the session identified by the first session identifier according to the first session identifier carried in the SLPP message.

[0227] In some embodiments, the portion corresponding to the specified position of the first session identifier is the first ID. Exemplarily, the first ID can be a string consisting of a plurality of characters distributed continuously from the start position of the first session identifier. In another exemplary embodiment, the first ID can be a string consisting of a plurality of characters distributed continuously from the end position of the first session identifier forward. Furthermore, in another exemplary embodiment, the first ID can be a string consisting of a plurality of characters distributed continuously from any intermediate position in the first session identifier.

[0228] In summary, in the embodiment of the present disclosure, the character string formed by the first ID is used as a substring formed by multiple consecutively distributed characters in the first session identifier, which facilitates rapid decoding by subsequent recipients.

[0229] In the same session, different participants have different UE IDs.

[0230] The UE ID of the same participant can be the same in different sessions.

[0231] In some embodiments, the first session identifier further includes:

[0232] The second ID indicates the participant of the conversation.

[0233] Exemplarily, the second ID indicates the UE ID of the participant.

[0234] Using the second ID, the recipient of the SLPP message can determine whether it is a session participant indicated by the first session identifier carried in the SLPP message. This SLPP message that specifies a session participant allows the sender of the SLPP message to select a session participant based on positioning needs, facilitating positioning. For example, some UEs have absolute location information, while others do not. If a session participant that needs to be located requires absolute positioning, the second ID can be used to specify the UE with absolute location information as a participant.

[0235] In some embodiments, the portion of the first session identifier corresponding to a specified position is the second ID. Exemplarily, the second ID can be a string consisting of a plurality of characters distributed continuously from the start position of the first session identifier. In another exemplary embodiment, the second ID can be a string consisting of a plurality of characters distributed continuously from the end position of the first session identifier forward. Furthermore, in another exemplary embodiment, the second ID can be a string consisting of a plurality of characters distributed continuously from any intermediate position in the first session identifier.

[0236] In summary, in the embodiment of the present disclosure, the character string formed by the second ID is used as a substring formed by multiple consecutively distributed characters in the first session identifier, which facilitates rapid decoding by subsequent recipients.

[0237] For example, if the first session identifier includes a first ID and a second ID, the first ID is arranged before the second ID, so that the recipient can more quickly unlock the first ID to determine the initiator.

[0238] The first session identification may or may not include the second ID.

[0239] In some embodiments, the session is created in a broadcast mode, and the first session identifier includes the second ID.

[0240] If a session is created in broadcast mode, there will be many SLPP message recipients. These recipients can determine whether they are a participant in the session identified by the SLPP message based on the second ID. If a recipient determines that it is a participant in the session, it joins the session identified by the SLPP message. If a recipient determines that it is not a participant in the session, it ignores the SLPP message.

[0241] For example, if one or more nodes around the target UE have their own location information, these nodes can serve as anchor UEs. Therefore, using the first session identifier to carry the second ID, indicating that the anchor UE is included as a participant, can improve the efficiency and accuracy of positioning the target UE.

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

[0243] Exemplarily, if the first session identifier does not carry the second ID, the receiver of the SLPP message can determine whether it is a participant in the session indicated by the first session identifier through the broadcast identifier.

[0244] This method of distinguishing participants by broadcast identification rather than second ID is more suitable for scenarios with fewer participants.

[0245] In some embodiments, the broadcast identifier includes at least one of the following:

[0246] The participant's source layer 2 broadcast ID (source 2 broadcast ID);

[0247] The destination Layer 2 broadcast ID of the participant;

[0248] SLPP user equipment broadcast ID of the participant.

[0249] In some embodiments, the number of participants in the session is less than a specified threshold, and the first session identifier includes the second ID.

[0250] Exemplarily, the specified threshold is a small number such as three or four.

[0251] When the number of participants in a session is less than a specified threshold, the first session identifier, including the second ID, can select an appropriate UE as a participant for positioning, which can reduce the complexity of positioning and improve the efficiency and accuracy of positioning. For example, if there are two participants in a session, the target UE-1, as the sender, indicates the target UE-1 as the initiator of the session through the first ID, and indicates the anchor UE-2, whose own location information is known, as a participant through the second ID. At this time, by determining the distance between the anchor UE-2 and the target UE-1 (ranging) and the location information of the anchor UE-2, the absolute position of the target UE-1 can be determined.

[0252] In some embodiments, the participants in the session other than the initiator are a UE group, and the first session identifier includes a second ID, where the second ID is a group ID of the UE group.

[0253] Compared to a single UE, a UE group includes two or more UEs, and thus contains richer location information. Using a UE group to locate the initiator can improve positioning accuracy, or using the initiator to locate the UE group can improve positioning efficiency.

[0254] In some embodiments, the session is created in broadcast mode and the session creation request message includes a broadcast identifier, and the first session identifier does not include the second ID; wherein the broadcast identifier is an identifier of the broadcast creation request message known to both the initiator and the participants.

[0255] Exemplarily, if the first session identifier does not carry the second ID, the receiver of the SLPP message can determine whether it is a participant in the session indicated by the first session identifier through the broadcast identifier.

[0256] This method of distinguishing participants by broadcast identification rather than a second ID is more suitable for scenarios with fewer participants.

[0257] In some embodiments, the broadcast identifier includes at least one of the following:

[0258] The participant's source layer 2 broadcast ID (source 2 broadcast ID);

[0259] The destination Layer 2 broadcast ID of the participant;

[0260] SLPP user equipment broadcast ID of the participant.

[0261] In some embodiments, the first session identifier further includes: a session number;

[0262] Different sessions initiated by the same initiator have different session numbers, and / or different sessions participated in by the same participant have different session numbers.

[0263] For example, the session number may be the serial number of all sessions created by the initiator, or the serial number of the SLPP session created by the initiator. Therefore, different sessions may have different session numbers.

[0264] In some embodiments, different SLPP messages within the same session use the same session number.

[0265] In some embodiments, the first session identifier may include other components in addition to the first ID and the session number. For example, the first session identifier may also include: the number of participants in the session identified by the first session identifier, the device types of the participants, the protocol version number of the SLPP protocol, and other related information.

[0266] In some embodiments, the participants are UE groups of a session, and the same participants include the same UE group ID and / or Layer 2 group ID of the participants.

[0267] The Layer 2 group ID includes a source Layer 2 group ID and / or a destination Layer 2 group ID.

[0268] The first session identifier identifies the session by a session number.

[0269] In some embodiments, different SLPP messages within the same session use the same session number.

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

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

[0272] Destination Layer 2 ID of the initiator;

[0273] The application layer ID of the initiator;

[0274] SLPP UE ID of the initiator.

[0275] In some embodiments, the second ID includes at least one of the following:

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

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

[0278] The application layer ID of the participant;

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

[0280] In some embodiments, the participants other than the initiator are a UE group of the session, and the second ID includes at least one of the following:

[0281] Group ID of the UE group, where participants are the participants of the session;

[0282] Source Layer 2 group ID of the UE group, where participants are the participants in the session;

[0283] Destination Layer 2 group ID of the UE group, where participants are the participants of the session;

[0284] Application layer group ID of the UE group, where participants are the participants of the session;

[0285] SLPP UE group ID of the UE group, where participants are the participants of the session.

[0286] In some embodiments, the participants other than the initiator are a UE group of the session, and the second ID further includes at least one of the following:

[0287] The source layer 2 ID in the UE group's source layer 2 ID list;

[0288] Destination layer 2 ID in the destination layer 2 ID list of the UE group;

[0289] Application layer ID in the application layer ID list of the UE group;

[0290] SLPP user equipment UE ID in the SLPP user equipment UE ID list of the UE group; wherein the participant is a participant in the session.

[0291] In some embodiments, the number of participants involved in the session is greater than two, and the session has a first session identifier.

[0292] If the session involves different UEs, that is, all participants are UEs, then the number of UEs involved in the session is greater than two, and the session has a first session identifier.

[0293] Based on the SLPP message carrying the first session identifier, it is possible to determine which of three or more participants is the session initiator. This reduces the situation where multiple participants cannot distinguish the session initiator, or different participants in the same session identify different initiators, thereby improving the accuracy of information exchange during the session. Because the first session identifier can more accurately distinguish the session initiator, positioning using the SLPP message carrying the first session identifier can also improve positioning accuracy.

[0294] In some embodiments, the number of parties involved in the session is less than or equal to two, and the session has a second session identifier;

[0295] A second session identifier, used to identify the second session;

[0296] The type information and the second session identifier carried in the SLPP message are used to determine the initiator of the session.

[0297] The type information includes the type of UE.

[0298] Exemplarily, the type information includes client and server.

[0299] If a session involves two UEs and the number of participants is small, the type information can be used to distinguish the two different UEs. For example, the server can be used to indicate that the server UE is the initiator, or the client can be used to indicate that the client UE is the initiator.

[0300] When there are two participants in a conversation, the initiator of the conversation can be distinguished by type information, which can improve compatibility with related technologies.

[0301] As shown in FIG3B , an embodiment of the present disclosure provides an information processing method, which is performed by a receiving party and includes:

[0302] S2210: Receive indication information, where the indication information is used to end a session (end session).

[0303] Exemplarily, the recipient may be the initiator of the session and / or a participant in the session other than the initiator.

[0304] Exemplarily, the participants include user equipment UE or road side unit RSU, etc.

[0305] In some embodiments, the initiator of the session may be a target UE (target UE) that needs to be positioned, and the participant may be an anchor UE (anchor UE) that provides positioning services.

[0306] In some embodiments, all participants in the session are UEs. In other embodiments, some participants in the session may include but are not limited to RSUs.

[0307] In some embodiments, the sender is the initiator of the session, and step S2210 includes: the initiator of the session sends indication information to participants other than the initiator.

[0308] In some embodiments, the number of participants in a session is two. Even if multiple transactions are supported within a session, these transactions all involve these two participants, so any participant can know that the end of the last transaction of the session means the end of the session.

[0309] Exemplarily, if a session includes multiple participants, all of the participants belong to the same UE group, and all transactions of the session involve this UE group, the session ends after the UE determines that the last transaction in the session is completed.

[0310] In other embodiments, the session is terminated based on the session result. For example, if the session result indicates that the participant who needs to be located has obtained a position estimate, it indicates that the session can be terminated.

[0311] In some embodiments, the participants in the session other than the initiator are a UE group, and the initiator sends indication information to the UE group.

[0312] In the embodiment of the present disclosure, the session may be ended using an indication message, or the session may be ended automatically without sending an indication message.

[0313] A transaction may be established between different participants in the same conversation. Through an indication message, any participant in the conversation can be informed that the conversation can be ended, thus achieving accurate determination of the end of the conversation when three or more participants are involved.

[0314] In some embodiments, the indication information is carried in an SLPP message containing the session content.

[0315] Exemplarily, the last SLPP message of the session carries the indication information, and the SLPP message is originally intended to be used for transmitting the session content. By carrying the indication message, after the transmission of the SLPP message is completed, all participants will end the session.

[0316] Exemplarily, the session content is carried in the SLPP message body, and the indication information is carried in the message header or message body of the SLPP message. If the indication information and the session content are both carried in the message body, the message body also includes a distinguishing mark, which is used to distinguish the marking area indication information from the session content.

[0317] Exemplarily, the indication information may be an end marker, for example, the end marker is “end session”; or, the indication information may be a bit sequence indicating the end.

[0318] The SLPP message carries both session content and indication information. There is no need to construct a special message to carry indication information in addition to the SLPP message that carries the session content. The SLPP message is reused, which is easy to implement.

[0319] In some embodiments, the indication information is carried in an SLPP message that does not include session content.

[0320] Here, carrying the indication information through an SLPP message that does not carry session content can be understood as indicating the end of the session through a dedicated SLPP message.

[0321] For example, after the last SLPP message carrying the session content is transmitted, the SLPP message carrying the indication information is sent.

[0322] Exemplarily, the indication information may be an end marker, or the indication information may be a bit sequence indicating the end.

[0323] Exemplarily, the indication information may be carried in a message header of the SLPP message or in a message body of the SLPP message.

[0324] In some embodiments, the indication information may be carried in a unicast, multicast, or broadcast manner through an SLPP message carrying session content, or the indication information may be carried in an SLPP message not carrying session content.

[0325] In some embodiments, the SLPP message carrying the indication information does not have an SLPP message body carrying the session content.

[0326] The message header of the SLPP message may be used to carry the indication information.

[0327] Such an SLPP message without an SLPP message body can shorten the length of the SLPP message and simplify decoding.

[0328] In some embodiments, the SLPP message carrying the indication information has an SLPP message body; the content of the SLPP message body is empty, or the SLPP message body carries specified content. Exemplarily, the SLPP message body carries session content.

[0329] As shown in FIG3C , an embodiment of the present disclosure provides an information processing method, which is performed by a receiving party and includes:

[0330] S2310: In response to obtaining a session result of the session, determining that the session is ended.

[0331] Exemplarily, the session result may be the purpose of establishing the session. Exemplarily, if the purpose of establishing the session is to obtain location information, obtaining the location information may be considered as obtaining the session result. Furthermore, exemplarily, if the purpose of establishing the session is to deliver message content, the recipient may determine that the session has ended after the message content is delivered to the recipient.

[0332] For example, for absolute and / or relative ranging scenarios, the session result includes whether the participant requiring positioning has obtained a position estimate. For example, the session result includes whether the initiator requiring positioning has obtained a position estimate.

[0333] In some embodiments, the session is determined to be ended in response to the participant requiring positioning obtaining a position estimate.

[0334] In some embodiments, the session is determined not to have ended in response to a participant requiring positioning not obtaining a position estimate.

[0335] In some embodiments, after determining that the session is ended, the method further includes: receiving indication information; the indication information is used to end the session (end session).

[0336] A transaction may be established between different participants in the same conversation. Through an indication message, any participant in the conversation can be informed that the conversation can be ended, thus achieving accurate determination of the end of the conversation when three or more participants are involved.

[0337] In some embodiments, the SLPP message carrying the session content carries indication information.

[0338] The SLPP message carries both session content and indication information. There is no need to construct a special message to carry indication information in addition to the SLPP message that carries the session content. The SLPP message is reused, which is easy to implement.

[0339] In some embodiments, the SLPP message that does not carry session content carries indication information.

[0340] In the embodiment of the present disclosure, the session may be ended using an indication message, or the session may be ended automatically without sending an indication message.

[0341] Exemplarily, the recipient may be the initiator of the session and / or a participant in the session other than the initiator.

[0342] Exemplarily, the participants include user equipment UE or road side unit RSU, etc.

[0343] In some embodiments, the initiator of the session may be a target UE (target UE) that needs to be positioned, and participants other than the initiator may be anchor UEs (anchor UEs) that provide positioning services.

[0344] In some embodiments, all participants in the session are UEs.

[0345] In some embodiments, if the number of participants in the session exceeds two, or the participants in the session other than the initiator include a UE group, in response to obtaining a session result of the session, it is determined that the session is ended.

[0346] In other embodiments, the session is determined to be ended in response to the last transaction involved in the session ending.

[0347] For example, if there are two participants in a session, even if multiple transactions are supported within a session, these transactions all involve these two participants, so any participant can know that the end of the last transaction of the session means the end of the session.

[0348] For example, if the session includes three or more participants, all of these participants belong to the same UE group, and all transactions of the session involve this UE group, the session ends after the UE determines that the last transaction in the session is completed.

[0349] As shown in FIG3D , an embodiment of the present disclosure provides an information processing method, wherein the method includes:

[0350] S2310: UE A adds a session ID to the SLPP message sent to other UEs, where the session ID includes at least the UE ID of the session initiator and the session number.

[0351] The session number includes the first session identifier of the aforementioned technical solution.

[0352] In some embodiments, SLPP messages within the same session use the same session number.

[0353] In some embodiments, if a session involves only two UEs, the initiator's UE ID may be indicated by a UE type, such as a server UE or a client UE.

[0354] In some embodiments, if the session initiator is a server UE, the UE ID may be indicated by a UE type, ie, a server UE.

[0355] In some embodiments, the first SLPP message received by the UE and carrying a session ID triggers the establishment of the session.

[0356] In some embodiments, the UE ID of the session initiator may be the source / destination Layer 2 ID, or the application layer ID, or the SLPP UE ID of the initiator.

[0357] In some embodiments, the session ID further includes the UE ID of the session participant.

[0358] In some embodiments, when the session participant is a UE, the UE ID of the session participant may be the source / destination Layer 2 ID, application layer ID or SLPP UE ID of the participant.

[0359] In some embodiments, when the session participant is a group of UEs, the UE ID of the session participant may be the source / destination Layer 2 groupcast ID, or the application layer group ID, or the SLPP group ID of the participant.

[0360] In some embodiments, when the session participants are a group of UEs, the UE IDs of the session 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.

[0361] In some embodiments, when the session is created in broadcast mode, the UE ID of the session participant may be a source / destination Layer 2 broadcast ID or an SLPP broadcast ID.

[0362] In some embodiments, only when a session participant is a UE or a group of UEs, the session ID carries the UE ID of the participant.

[0363] In some embodiments, if the session is created in broadcast mode, the session ID does not carry the UE ID of the participant.

[0364] In some embodiments, different session numbers are required for sessions with the same initiator and participants.

[0365] In some embodiments, for a session involving a group of UEs, the having the same participants includes the same group ID or Layer 2 group ID of the participants.

[0366] In some embodiments, if an SLPP session involves only two UEs, the session ends after the last transaction in the session is completed.

[0367] S2320: If the SLPP session involves a group of UEs, the session initiator sends a message for ending the session, such as adding end session indication information in the SLPP message, or sending an SLPP message for ending the session.

[0368] In some embodiments, the SLPP message carrying the end session or the SLPP message that ends the session may be sent by unicast, multicast, or broadcast.

[0369] In some embodiments, the session initiator sends a message for ending the session when determining that the session can be ended. The determination that the session can be ended may be, for example, that the initiator obtains a location estimate.

[0370] In some embodiments, the SLPP message for indicating the end of the session may carry or not carry an SLPP message body.

[0371] In some embodiments, if an SLPP session involves a group of UEs, and if all transactions in the session involve the group of UEs, the session ends after the UE determines that the last transaction in the session ends.

[0372] As shown in FIG4A , an embodiment of the present disclosure provides an information processing device, wherein the device includes:

[0373] The sending module 110 is configured to send a Sidelink Positioning Protocol (SLPP) message, where the SLPP message includes a first session identifier, wherein the first session identifier is used to identify a session and determine an initiator of the session.

[0374] In some embodiments, the information processing device may include a sender.

[0375] The sender may be the initiator of the session and / or a participant other than the initiator of the session.

[0376] A node becomes a participant after joining a session.

[0377] Exemplarily, the participants include user equipment UE or road side unit RSU, etc.

[0378] In some embodiments, the initiator of the session may be a target UE (target UE) that needs to be positioned, and the participant may be an anchor UE (anchor UE) that provides positioning services.

[0379] In some embodiments, all participants in the session are UEs.

[0380] In some embodiments, the sending module 110 may be a program module, which can implement the above operations after being executed by a processor.

[0381] In other embodiments, the sending module 110 may be a soft-hard combination module; the soft-hard combination module includes but is not limited to a programmable array.

[0382] In some other embodiments, the sending module 110 may be a pure hardware module; the pure hardware module includes but is not limited to a dedicated integrated circuit.

[0383] In some embodiments, the first session identifier includes: a first ID indicating an initiator of the session.

[0384] In some embodiments, the first session identifier further includes:

[0385] The second ID indicates the participant of the conversation.

[0386] The session is created in broadcast mode, and the first session identifier includes the second ID;

[0387] or,

[0388] The number of participants in the session is less than a specified threshold, and the first session identifier includes the second ID;

[0389] or,

[0390] The participants in the session other than the initiator are a UE group, and the first session identifier includes a second ID, wherein the second ID is a group ID of the UE group.

[0391] In some embodiments, the session is created in a broadcast mode and the session creation request message includes a broadcast identifier, and the first session identifier does not include the second ID;

[0392] The broadcast identifier is an identifier of the broadcast creation request message known to all participants.

[0393] In some embodiments, the first session identifier further includes: a session number;

[0394] Different sessions initiated by the same initiator have different session numbers, and / or different sessions participated in by the same participant have different session numbers.

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

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

[0397] Destination Layer 2 ID of the initiator;

[0398] The application layer ID of the initiator;

[0399] SLPP UE ID of the initiator.

[0400] The second ID includes at least one of the following:

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

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

[0403] The application layer ID of the participant;

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

[0405] In some embodiments, the participants other than the initiator are a UE group of the session, and the second ID includes at least one of the following:

[0406] Group ID of the UE group, where participants are the participants of the session;

[0407] Source Layer 2 group ID of the UE group, where participants are the participants in the session;

[0408] Destination Layer 2 group ID of the UE group, where participants are the participants of the session;

[0409] Application layer group ID of the UE group, where participants are the participants of the session;

[0410] SLPP UE group ID of the UE group, where participants are the participants of the session.

[0411] In some embodiments, the number of parties involved in the session is less than or equal to two, and the session has a second session identifier;

[0412] A second session identifier, used to identify the second session;

[0413] The type information and the second session identifier carried in the SLPP message are used to determine the initiator of the session.

[0414] In some embodiments, the sending module is further configured to perform:

[0415] In response to determining to end the session, an indication message is sent; the indication message is used to end the session.

[0416] In some embodiments, the SLPP message carrying the session content carries indication information.

[0417] In some embodiments, the SLPP message that does not carry session content carries indication information.

[0418] In some embodiments, the SLPP message carrying the indication information does not have an SLPP message body; the SLPP message is used to carry session content.

[0419] In some embodiments, the sending module 110 is configured to perform at least one of the following:

[0420] In response to the last transaction involved in the session ending, determining that the session ends;

[0421] In response to acquiring a session result of the session, it is determined that the session is ended.

[0422] As shown in FIG4B , an embodiment of the present disclosure provides an information processing device, wherein the device includes:

[0423] The receiving module 210 is configured to receive a Sidelink Positioning Protocol (SLPP) message, where the SLPP message includes a first session identifier, wherein the first session identifier is used to identify a session and determine an initiator of the session.

[0424] In some embodiments, the information processing device may include a recipient.

[0425] The recipient may be the initiator of the session and / or a participant other than the initiator of the session.

[0426] A node becomes a participant after joining a session.

[0427] Exemplarily, the participants include user equipment UE or road side unit RSU, etc.

[0428] In some embodiments, the initiator of the session may be a target UE (target UE) that needs to be positioned, and the participants other than the initiator may be anchor UEs (anchor UEs) that provide positioning services.

[0429] In some embodiments, all participants in the session are UEs.

[0430] In some embodiments, the receiving module 210 may be a program module, which can implement the above operations after being executed by a processor.

[0431] In other embodiments, the receiving module 210 may be a soft-hard combination module; the soft-hard combination module includes but is not limited to a programmable array.

[0432] In some other embodiments, the receiving module 210 may be a pure hardware module; the pure hardware module includes but is not limited to a dedicated integrated circuit.

[0433] In some embodiments, the first session identifier includes: a first ID indicating an initiator of the session.

[0434] The first session identifier also includes:

[0435] The second ID indicates the participants in the session other than the initiator.

[0436] In some embodiments, the session is created in a broadcast mode, and the first session identifier includes the second ID;

[0437] or,

[0438] The number of participants in the session is less than a first threshold, and the first session identifier includes the second ID;

[0439] or,

[0440] The participants of the session other than the initiator are a UE group, and the first session identifier includes a second ID, where the second ID is a group ID of the UE group.

[0441] In some embodiments, the session is created in broadcast mode and the session creation request message includes a broadcast identifier, and the first session identifier does not include the second ID; wherein the broadcast identifier is an identifier of the broadcast creation request message known to both the initiator and the participants.

[0442] In some embodiments, the first session identifier further includes: a session number;

[0443] Different sessions initiated by the same initiator have different session numbers, and / or different sessions participated in by the same participant have different session numbers.

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

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

[0446] Destination Layer 2 ID of the initiator;

[0447] The application layer ID of the initiator;

[0448] UE ID of the initiator's SLPP user equipment.

[0449] In some embodiments, the second ID includes at least one of the following:

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

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

[0452] The application layer ID of the participant;

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

[0454] In some embodiments, the participants other than the initiator are a UE group of the session, and the second ID includes at least one of the following:

[0455] Group ID of the UE group, where participants are the participants of the session;

[0456] Source Layer 2 group ID of the UE group, where participants are the participants in the session;

[0457] Destination Layer 2 group ID of the UE group, where participants are the participants of the session;

[0458] Application layer group ID of the UE group, where participants are the participants of the session;

[0459] SLPP UE group ID of the UE group, where participants are the participants of the session.

[0460] In some embodiments, the number of UEs involved in the session is greater than two, and the session has a first session identifier.

[0461] In some embodiments, the number of UEs involved in the session is less than or equal to two, and the session has a second session identifier, wherein the second session identifier of the participant is used to identify the second session; the type information and the second session identifier carried in the SLPP message are used to determine the initiator of the session.

[0462] In some embodiments, the method comprises:

[0463] Receive indication information, where the indication information is used to end the session.

[0464] In some embodiments, the indication information is carried in an SLPP message containing the session content.

[0465] In some embodiments, the indication information is carried in an SLPP message that does not include session content.

[0466] In some embodiments, the SLPP message carrying the indication information does not have an SLPP message body carrying the session content.

[0467] In some embodiments, the method further comprises one of the following:

[0468] In response to the last transaction involved in the session ending, determining that the session ends;

[0469] In response to acquiring a session result of the session, it is determined that the session is ended.

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

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

[0472] Processor, respectively memory connected;

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

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

[0475] Here, the communication device includes: UE and / or network equipment.

[0476] The processor may be connected to the memory via a bus or the like, and may be configured to read an executable program stored in the memory, for example, at least one of the methods shown in FIG. 2A to FIG. 3D .

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

[0478] 5A 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.

[0479] 5A , 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 .

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

[0481] The memory 804 is configured to store various types of data to support operations on the terminal 800. Examples of such data include instructions for any application or method operating on the terminal 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.

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

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

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

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

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

[0487] 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, 2G or 3G, 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.

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

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

[0490] As shown in Figure 5B, an embodiment of the present disclosure illustrates a structure of a network device. For example, the network device 900 may be provided as a network-side device. The communication device may be various network elements such as the aforementioned access network element and / or network function.

[0491] 5B , network device 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by memory 932 for storing instructions executable by processing component 922, such as applications. The applications stored in memory 932 may include one or more modules, each corresponding to a set of instructions. In addition, processing component 922 is configured to execute instructions to perform any of the aforementioned methods applied to the access device, such as the methods shown in any of Figures 2A to 2C and / or Figures 3A to 3D.

[0492] The network device 900 may also include a power supply component 926 configured to perform power management of the network device 900, a wired or wireless network interface 950 configured to connect the network device 900 to a network, and an input / output (I / O) interface 958. The network device 900 may operate based on an operating system stored in the memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like. Unless otherwise specified, each step in a particular embodiment or example may be implemented as an independent embodiment, and the steps may be combined arbitrarily. For example, a solution in which some steps are removed from a particular embodiment or example may also be implemented as an independent embodiment, and the order of the steps in a particular embodiment or example may be interchanged arbitrarily. In addition, the alternatives or alternative examples in a particular embodiment or example may be combined arbitrarily. Furthermore, the various embodiments or examples may be combined arbitrarily. For example, some or all steps of different embodiments or examples may be combined arbitrarily, and a particular embodiment or example may be combined arbitrarily with the alternatives or alternative examples of other embodiments or examples.

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

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

Claims

1. An information processing method, in, Executed by the sender, the method includes: A Sideline Positioning Protocol (SLPP) message is sent, wherein the SLPP message includes: a first session identifier; wherein the first session identifier is used to identify a session and determine an initiator of the session.

2. The method according to claim 1, in, The first session identifier includes: The first ID indicates the initiator of the session.

3. The method according to claim 1 or 2, in, The first session identifier further includes: The second ID indicates the participant of the conversation.

4. The method according to claim 3, in, The session is created in broadcast mode, and the first session identifier includes the second ID; or, The number of participants in the session is less than a specified threshold, and the first session identifier includes the second ID; or, The participants of the session are a UE group, and the first session identifier includes the second ID, wherein the second ID is the group ID of the UE group.

5. The method according to claim 3, in, The session is created in a broadcast mode and the creation request message of the session includes a broadcast identifier, and the first session identifier does not include the second ID; The broadcast identifier is an identifier of the broadcast creation request message known to all the participants.

6. The method according to any one of claims 1 to 5, in, The first session identifier also includes: a session number; The session numbers of different sessions initiated by the same initiator are different, and / or the session numbers of different sessions participated in by the same participant are different.

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

8. The method according to claim 3, in, The second ID includes at least one of the following: The source layer 2 ID of the participant; The destination layer 2 ID of the participant; The application layer ID of the participant; SLPP user equipment UE ID of the participant.

9. The method according to claim 3, in, The participant is a UE group of the session, and the second ID includes at least one of the following: a group ID of the UE group, wherein the participant is a participant of the session; a source layer 2 group ID of the UE group, wherein the participant is a participant of the session; a destination layer 2 group ID of a UE group of the UE group, wherein the participant is a participant of the session; an application layer group ID of the UE group, wherein the participant is a participant of the session; The SLPP UE group ID of the UE group, wherein the participant is a participant of the session.

10. The method according to any one of claims 1 to 8, in, The number of participants involved in the session is greater than two, and the session has the first session identifier.

11. The method according to any one of claims 1 to 8, in, The number of participants involved in the session is less than or equal to two, and the session has a second session identifier; The second session identifier is used to identify the second session; The type information and the second session identifier carried in the SLPP message are used to determine the initiator of the session.

12. The method according to any one of claims 1 to 11, in, The method further comprises: In response to determining to end the session, sending indication information; the indication information is used to end the session.

13. The method according to claim 12, in, The SLPP message carrying the session content carries the indication information.

14. The method according to claim 12, in, The SLPP message that does not carry the session content carries the indication information.

15. The method according to claim 13, in, The SLPP message carrying the indication information does not have a SLPP message body; the SLPP message body is used to carry the session content.

16. The method according to any one of claims 1 to 15, in, The method further comprises one of the following: In response to the last transaction involved in the session ending, determining that the session ends; In response to obtaining a session result of the session, it is determined that the session is ended.

17. An information processing method, in, Executed by a receiving party, the method includes: A Sideline Positioning Protocol (SLPP) message is received, wherein the SLPP message includes: a first session identifier; wherein the first session identifier is used to identify a session and determine an initiator of the session.

18. The method according to claim 17, in, The first session identifier includes: The first ID indicates the initiator of the session.

19. The method according to claim 17 or 18, in, The first session identifier further includes: The second ID indicates the participant of the conversation.

20. The method according to claim 19, in, The session is created in broadcast mode, and the first session identifier includes the second ID; or, The number of participants in the session is less than a first threshold, and the first session identifier includes the second ID; or, The participants of the session are a UE group, and the first session identifier includes the second ID, wherein the second ID is the group ID of the UE group.

21. The method according to claim 19, in, The session is created in broadcast mode and the creation request message of the session includes a broadcast identifier, and the first session identifier does not include the second ID; wherein the broadcast identifier is an identifier of the broadcast creation request message known to both the initiator and the participants.

22. The method according to any one of claims 17 to 21, in, The first session identifier also includes: a session number; The session numbers of different sessions initiated by the same initiator are different, and / or the session numbers of different sessions participated in by the same participant are different.

23. The method according to claim 18, in, The first ID includes at least one of the following: The source layer 2 ID of the initiator; The destination layer 2 ID of the initiator; The application layer ID of the initiator; The SLPP user equipment UE ID of the initiator.

24. The method according to claim 20, in, The second ID includes at least one of the following: The source layer 2 ID of the participant; The destination layer 2 ID of the participant; The application layer ID of the participant; SLPP user equipment UE ID of the participant.

25. The method according to claim 20, in, The participant is a UE group of the session, and the second ID includes at least one of the following: a group ID of the UE group, wherein the participant is a participant of the session; a source layer 2 group ID of the UE group, wherein the participant is a participant of the session; a destination layer 2 group ID of a UE group of the UE group, wherein the participant is a participant of the session; an application layer group ID of the UE group, wherein the participant is a participant of the session; The SLPP UE group ID of the UE group, wherein the participant is a participant of the session.

26. The method according to any one of claims 17 to 24, in, The number of participants involved in the session is greater than two, and the session has the first session identifier.

27. The method according to any one of claims 17 to 24, in, The number of participants involved in the session is less than or equal to two, and the session has a second session identifier, wherein the second session identifier of the participant is used to identify the second session; the type information and the second session identifier carried in the SLPP message are used to determine the initiator of the session.

28. The method according to any one of claims 17 to 27, in, The method comprises: Indication information is received, wherein the indication information is used to end a session.

29. The method according to claim 28, in, The indication information is carried in the SLPP message including the session content.

30. The method according to claim 28, in, The indication information is carried in the SLPP message that does not include the session content.

31. The method according to claim 28, in, The SLPP message carrying the indication information does not have an SLPP message body carrying session content.

32. A method according to any one of claims 17 to 31, in, The method further comprises one of the following: In response to the last transaction involved in the session ending, determining that the session ends; In response to obtaining a session result of the session, it is determined that the session is ended.

33. An information processing device, in, The device comprises: The sending module is configured to send a Side Line Positioning Protocol (SLPP) message, wherein the SLPP message includes: a first session identifier; wherein the first session identifier is used to identify a session and determine an initiator of the session.

34. An information processing device, in, The device comprises: The receiving module is configured to receive a Sideline Positioning Protocol (SLPP) message, wherein the SLPP message includes: a first session identifier; wherein the first session identifier is used to identify a session and determine an initiator of the session.

35. 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, in, When the processor runs the executable program, it executes the information processing method provided in any one of claims 1 to 16 or 17 to 32.

36. 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 16 or 17 to 32.

Images