Session identifier receiving, sending and generating method and device, equipment and medium

Abstract

The invention discloses a session identifier receiving, sending and generating method and device, equipment and a medium, and relates to the field of communication. The method comprises the following steps: receiving a first sidewalk positioning protocol message, wherein the first sidewalk positioning protocol message carries a first session identifier; under the condition that the first session identifier is the same as any stored session identifier, first information is sent, and the first information is used for requesting or indicating to change the first session identifier; wherein the first session identifier is used for identifying a first positioning session to which the first sidewalk positioning protocol message belongs. The method provided by the invention is used for solving the problem that the terminal equipment has the same session identifier in the sidewalk positioning session.

Description

Method, device, equipment and medium for receiving, sending and generating session identifiers Technical Field

[0001] The present application relates to the field of communications, and in particular to a method, apparatus, device, and medium for receiving, sending, and generating a session identifier. Background Art

[0002] Terminal devices can communicate with each other via a side link (SL), so that the terminal device can perform positioning interaction with other terminal devices based on the side link communication to determine the positioning information of the terminal device.

[0003] In related technologies, a terminal device receives a location service request from another terminal device or an application layer, and upon receiving the location service request, the terminal device initiates a side-by-side location session. When outside the coverage of a wireless access network, location operations can be performed between terminal devices.

[0004] However, when positioning operations are performed between terminal devices, there is a problem that the session identifiers of the initiating devices are the same in different sideline positioning sessions.

[0005] Summary of the Invention

[0006] The present invention provides a method, apparatus, device, and medium for receiving, sending, and generating a session identifier. The technical solution is as follows:

[0007] According to one aspect of an embodiment of the present application, a method for receiving a session identifier of a sideline positioning session is provided, the method being executed by a receiving node, the method comprising:

[0008] receiving a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier;

[0009] When the first session identifier is the same as any stored session identifier, sending first information, where the first information is used to request or instruct to change the first session identifier;

[0010] The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

[0011] According to one aspect of an embodiment of the present application, a method for sending a session identifier of a sideline positioning session is provided, the method being performed by an initial node, the method comprising:

[0012] Sending a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier;

[0013] receiving first information, where the first information is used to request or instruct a change of the first session identifier;

[0014] The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

[0015] According to one aspect of an embodiment of the present application, a method for generating a session identifier for a sideline positioning session is provided, the method being executed by an initial node, the method comprising:

[0016] generating a third session identifier of the sideline positioning session, where the third session identifier is related to at least one of the first information and the second information;

[0017] The first information is a unique identifier of the initial node, and the second information is distinctive information of the initial node when initializing different sideline positioning sessions.

[0018] According to one aspect of an embodiment of the present application, a method for receiving a session identifier of a sideline positioning session is provided, the method being executed by a receiving node, the method comprising:

[0019] receiving a third sideline positioning protocol message, where the third sideline positioning protocol message carries a session identifier of a second positioning session;

[0020] After the second timer times out, releasing, invalidating, or making the session identifier of the second positioning session idle;

[0021] The start time of the second timer is determined by the end time of the second positioning session, or the start time or reset time of the second timer is determined based on the reception time of the third sideline positioning protocol message. According to one aspect of an embodiment of the present application, a session identifier receiving device for a sideline positioning session is provided, the device comprising:

[0022] A first receiving module is configured to receive a first sideline positioning protocol message, where the first sideline positioning protocol message carries a first session identifier;

[0023] A first sending module is configured to send first information when the first session identifier is the same as any stored session identifier, wherein the first information is used to request or instruct to change the first session identifier;

[0024] The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

[0025] According to one aspect of an embodiment of the present application, a device for sending a session identifier of a sideline positioning session is provided, the device comprising:

[0026] A second sending module is configured to send a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier;

[0027] A second receiving module is configured to receive first information, where the first information is used to request or instruct a change of the first session identifier;

[0028] The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

[0029] According to one aspect of an embodiment of the present application, a device for generating a session identifier for a sideline positioning session is provided, the device comprising:

[0030] a generating module, configured to generate a third session identifier of the sideline positioning session, wherein the third session identifier is related to at least one of the first information and the second information;

[0031] The first information is a unique identifier of the initial node, and the second information is distinctive information of the initial node when initializing different sideline positioning sessions.

[0032] According to one aspect of an embodiment of the present application, a device for receiving a session identifier of a sideline positioning session is provided, the device comprising:

[0033] A third receiving module is configured to receive a third sideline positioning protocol message, where the third sideline positioning protocol message carries a session identifier of a second positioning session;

[0034] An execution module, configured to release, invalidate or idle the session identifier of the second positioning session after the second timer times out;

[0035] The start time of the second timer is determined by the end time of the second positioning session, or the start time or reset time of the second timer is determined based on the reception time of the third sidelink positioning protocol message.

[0036] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which executable instructions are stored. The executable instructions are loaded and executed by a processor to implement the above-mentioned method for receiving a session identifier for a side positioning session, or the method for sending a session identifier for a side positioning session, or the method for generating a session identifier for a side positioning session, or the method for receiving a session identifier for a side positioning session.

[0037] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the above-mentioned method for receiving a session identifier for a side positioning session, or the method for sending a session identifier for a side positioning session, or the method for generating a session identifier for a side positioning session, or the method for receiving a session identifier for a side positioning session.

[0038] According to one aspect of an embodiment of the present application, a computer program product is provided, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned method for receiving a session identifier for a side positioning session, or the method for sending a session identifier for a side positioning session, or the method for generating a session identifier for a side positioning session, or the method for receiving a session identifier for a side positioning session.

[0039] According to one aspect of an embodiment of the present application, a computer program is provided, which includes computer instructions. The processor of a computer device executes the computer instructions, so that the computer device executes the above-mentioned method for receiving a session identifier for a side positioning session, or the method for sending a session identifier for a side positioning session, or the method for generating a session identifier for a side positioning session, or the method for receiving a session identifier for a side positioning session.

[0040] The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

[0041] The initiating node sends a first sideways positioning protocol message carrying a first session identifier to the receiving node. The receiving node checks whether the first session identifier is the same as any stored session identifier. If they are the same, the receiving node replies to the initiating node to update the first session identifier. This interaction between the initiating node and the receiving node can resolve the issue of duplicate session identifiers in sideways positioning sessions.

[0042] The initial node generates a session identifier for the side positioning session. The session identifier is related to the unique identifier of the initial node and the distinguishing information of the initial node when initializing different side positioning sessions. By setting the session identifier uniquely, the problem of identical session identifiers in side positioning sessions can be avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0044] FIG1 shows a schematic diagram of the architecture of a communication system provided by an exemplary embodiment of the present application;

[0045] FIG2 is a schematic flow chart showing a method for receiving a session identifier of a sideline positioning session provided by an exemplary embodiment of the present application;

[0046] FIG3 is a schematic diagram showing a flow chart of a method for sending a session identifier of a sideline positioning session provided by an exemplary embodiment of the present application;

[0047] FIG4 shows an interactive diagram of a method for changing a sideline positioning session identifier provided by an exemplary embodiment of the present application;

[0048] FIG5 shows an interactive diagram of a method for changing a sideline positioning session identifier provided by an exemplary embodiment of the present application;

[0049] FIG6 shows an interactive diagram of a method for changing a sideline positioning session identifier provided by an exemplary embodiment of the present application;

[0050] FIG7 is a schematic diagram showing a flow chart of a method for generating a session identifier for a sideline positioning session provided by an exemplary embodiment of the present application;

[0051] FIG8 is a schematic diagram showing a flow chart of a method for generating a session identifier for a sideline positioning session provided by an exemplary embodiment of the present application;

[0052] FIG9 is a schematic diagram showing a flow chart of a method for generating a session identifier for a sideline positioning session provided by an exemplary embodiment of the present application;

[0053] FIG10 is a schematic flow chart showing a method for receiving a session identifier of a sideline positioning session provided by an exemplary embodiment of the present application;

[0054] FIG11 shows an interactive diagram of a method for changing a sideline positioning session identifier provided by an exemplary embodiment of the present application;

[0055] FIG12 shows a structural block diagram of a session identifier receiving device for a sideline positioning session provided by an exemplary embodiment of the present application;

[0056] FIG13 shows a structural block diagram of a device for sending a session identifier for a sideline positioning session provided by an exemplary embodiment of the present application;

[0057] FIG14 shows a structural block diagram of a device for generating a session identifier for a side-by-side positioning session provided by an exemplary embodiment of the present application;

[0058] FIG15 shows a structural block diagram of a session identifier receiving device for a sideline positioning session provided by an exemplary embodiment of the present application;

[0059] FIG16 shows a structural block diagram of a terminal device provided by an exemplary embodiment of the present application. Specific embodiments

[0060] To make the objectives, technical solutions, and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail herein, with examples shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are merely examples of devices and methods consistent with certain aspects of the present application, as detailed in the appended claims.

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

[0062] It should be understood that although the terms first, second, third, etc. may be used in this application to describe various information, 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 this application, first information may also be referred to as second information, and similarly, second information may also be referred to as 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".

[0063] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0064] Before introducing the technical solutions of this application, we first introduce and explain some of the background technologies involved in this application. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0065] UE: User Equipment (UE), also known as terminal equipment.

[0066] Initiating terminal: that is, initiating UE, refers to the terminal device that initiates the sideline positioning service.

[0067] Target terminal: also known as target UE, which refers to the target user equipment that requires sideways positioning. In a sideways positioning session, the location information of the target UE needs to be determined.

[0068] Anchor terminal: An anchor UE is a reference device used for measurements in a sideline positioning session. It can be a terminal device with a known location, used to provide reference information to calculate the location of the target UE.

[0069] Server terminal: also known as server UE, which is the user equipment on the server used to provide sideline positioning services. It can be in multiple sideline positioning sessions simultaneously and receive measurement results from anchor UEs via the Sideline Positioning Service Protocol (SLPP) to provide location information.

[0070] The initial node refers to the terminal device that initiates the sidewalk positioning session and is responsible for sending sidewalk positioning related messages or requests to other terminal devices. In some embodiments, the initial node can be equivalent to the initiating terminal.

[0071] The receiving node refers to a terminal device that receives a side positioning-related message or request sent by the initial node and is responsible for receiving and processing the side positioning-related message or request from the initial node. In some embodiments, the receiving node can be at least one of an anchor terminal, a target terminal, and a server terminal.

[0072] In the related art, terminal devices can communicate with each other through SL, so that the terminal devices can interact with other terminal devices for side positioning based on side link communication to determine the side positioning information of the terminal device. When a group of UEs communicate based on the side link, there is an opportunity to use the side link signal (Sidelink Positioning Reference Signal, SL PRS) to estimate the position of the UE, whether it is the absolute position relative to each other (such as latitude / longitude position estimation) or the relative position (for example, the range or displacement relative to one or more other UEs). However, a group of UEs communicating through the side link may be within the coverage of the cellular network or outside the coverage of the cellular network. In the out-of-coverage scenario, the existing side positioning method based on server communication in the cellular network may not be feasible. Therefore, the position of the target UE can be detected by using the position of each other's UEs.

[0073] The method for detecting the location of the target UE by using the locations of each UE is as follows:

[0074] In step 1, the target UE may receive a ranging / SL positioning service request from the following locations.

[0075] a. Ranging / SL positioning service request via the Proximity Communication (PC5) interface: For absolute location, the service request includes the user information of the target UE and the required Quality of Service for Positioning (QoS); for relative location or ranging information, the service request includes the user information of the target UE, the anchor UE, and ranging / SL positioning QoS information.

[0076] b. Ranging / SL positioning service request from the application layer: The service request includes the result type (ie, absolute position, relative position, or range information) and the required QoS.

[0077] Step 2: The target UE discovers the anchor UE (ie, SL reference UE / positioning UE).

[0078] Step 3: Determine UE-only operation.

[0079] If the Next Generation Radio Access Network (NG-RAN) does not provide target UE and anchor UE services, or the serving network does not support ranging / SL positioning, UE-only operation is applied, that is, the position of the target UE is detected by using the positions of each other's UEs.

[0080] Step 4: The target UE and the anchor UE perform capability exchange.

[0081] Step 4 may be performed in coordination with the server UE during steps 5 and 6.

[0082] Step 5: The server UE discovers and selects.

[0083] If the target UE does not support the SL positioning server function, it will discover a server UE (co-located with the anchor UE or operated by a separate UE) (if not already discovered in step 2). If the server UE is co-located with the anchor UE or operated by a separate UE, the target will discover and select the server UE and request the server UE to participate in ranging / SL positioning.

[0084] Step 6: SLPP assisted data transmission.

[0085] Transmitted between target UE, anchor UE and server UE.

[0086] In step 7, SL-PRS measurement is performed between the target UE and the anchor UE, and may also be performed between the anchor UE and the server UE.

[0087] Step 8: SL-PRS measurement data transmission and result calculation.

[0088] The SL-PRS measurement data is transmitted to the server UE, or to the target UE if the target UE supports the server function, so that the result calculation can be performed. Depending on the type of result received in step 1, the absolute position, relative position or ranging information is calculated on the UE.

[0089] Step 9: Distance measurement / SL positioning is transmitted via the PC5 interface.

[0090] The above steps show that:

[0091] 1) Upon receiving a Location Services (LCS) request, the UE initiates a positioning session.

[0092] 2) A positioning session is applicable to a specific LCS request corresponding to the positioning QoS requirements.

[0093] 3) A UE, whether it is an anchor UE, a target UE, or a server UE, can be in multiple positioning sessions at the same time.

[0094] 4) The UE should have a way to distinguish between messages from different ongoing positioning sessions. For example, a server UE receives SL-PRS measurements from an anchor UE via an SLPP Provide Location Information message. If the anchor UE is tasked with performing SL-PRS measurements for two positioning sessions of the server UE, the server UE needs to know which LCS service request / SL positioning session / target UE this Provide Location Information message corresponds to.

[0095] Figure 1 shows a schematic diagram of the architecture of a communication system provided by some exemplary embodiments of the present application. The number and configuration of terminal devices shown in Figure 1 are for illustrative purposes only and do not constitute a limitation on the embodiments of the present application. In practical applications, two or more terminal devices and two or more lateral positioning assistance devices may be included. The communication system shown in Figure 1 uses one target terminal, three anchor terminals, and one server terminal as an example.

[0096] It should be noted that the technical solutions of the embodiments of the present application can be applied to various communication systems. For example, long term evolution (LTE) systems, fifth generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0097] In the embodiments of the present application, the target terminal, anchor terminal, and server terminal are all terminal devices, which are entities on the user side for receiving or transmitting signals. The terminal device may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, a wireless terminal device in smart home, etc. The embodiments of the present application do not limit the specific technology and specific terminal device form adopted by the terminal device.

[0098] In some embodiments, the initiating terminal is the receiving terminal requesting positioning, and the target terminal is the receiving terminal being positioned, but the initiating terminal and the target terminal can be the same terminal device. The terminal device that assists the target terminal in positioning, that is, the terminal that sends the SL PRS, is called the sending terminal, and the sending terminal can be an anchor terminal or a server terminal. Optionally, the target terminal can also be an anchor terminal or a server terminal. The anchor terminal and the server terminal are only for the convenience of distinguishing terminal devices, and do not serve as a restriction on the terminal device itself. Any terminal device can serve as at least one of the anchor terminal and the server terminal in different communication scenarios, and this application does not impose any restrictions on this.

[0099] In some embodiments, the target terminal will start a side positioning session after receiving a location service request, and the initiating terminal, target terminal, anchor terminal and server terminal can be in multiple side positioning sessions at the same time. In the side positioning session, the location information of the target terminal needs to be determined; the anchor terminal refers to a reference device used for measurement in the side positioning session, which can be a terminal device with a known location, used to provide reference information to calculate the location of the target terminal; the server terminal refers to a user device on a server used to provide positioning services, which can be in multiple side positioning sessions at the same time and receive measurement results from the anchor terminal through SLPP to provide location information messages. In one possible implementation method, the initiating terminal, target terminal, anchor terminal and server terminal communicate with each other through the PC5 interface.

[0100] FIG2 is a flow chart of a method for receiving a session identifier of a sideline positioning session provided by an exemplary embodiment of the present application. Taking the method executed by a receiving node as an example, the method includes at least some of the following steps:

[0101] Step 210: Receive a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier;

[0102] The first sideways positioning protocol message refers to a message sent by an initial node to a receiving node in the sideways positioning protocol for transmitting and exchanging information to support the execution of the sideways positioning process.

[0103] Optionally, the first sideways positioning protocol message is the first message in the sideways positioning session.

[0104] The first session identifier is an identifier carried in the first sidelink positioning protocol message, and is used to identify the positioning session to which the message belongs.

[0105] A positioning session refers to a series of interactions and communications between different nodes during the side positioning process.

[0106] In some embodiments, the initiating node sends a first sidelink positioning protocol message carrying a first session identifier to the receiving node. The receiving node compares the received first session identifier with any stored session identifiers to detect a collision. A collision refers to a situation where the first session identifier overlaps with any stored session identifier.

[0107] In some embodiments, any stored session identifier refers to a session identifier of a side positioning session that has been stored in the receiving node. In a side positioning session, each side positioning session is assigned a unique session identifier to distinguish different side positioning sessions. Each time the initiating node sends a side positioning protocol message to the receiving node, the receiving node stores the session identifier of the side positioning protocol message to identify the side positioning session.

[0108] Step 220: When the first session identifier is identical to any stored session identifier, first information is sent, where the first information is used to request or instruct to change the first session identifier.

[0109] The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

[0110] In an optional example, the first message is sent when the first session identifier is the same as any session identifier stored by the receiving node.

[0111] In some embodiments, the first information is used to request or instruct to change the first session identifier when the first session identifier is the same as any stored session identifier, so as to avoid conflict with any stored session identifier.

[0112] Optionally, the first information indicates a change in the first session identifier, and the receiving node may indicate this by sending at least one of a session control message (Session Control Information, SCI) or an SLPP message to the initial node. Exemplarily, SCI is a message format for controlling and managing communication services, and is used to exchange side positioning session control information between a terminal device and a network. Through the SCI, the receiving node may send a request indicating a change in the session identifier. Exemplarily, SLPP is a protocol for transmitting side positioning session control information between a terminal device and a network. Through the SLPP message, the receiving node may send information containing an indication of a change in the session identifier, for requesting or instructing the initial node to change the first session identifier.

[0113] It should be noted that the embodiment of the present application does not limit the manner in which the first information indicates the change of the first session identifier.

[0114] In summary, the method provided in this embodiment involves an initiating node sending a first sideways positioning protocol message carrying a first session identifier to a receiving node. The receiving node then checks whether the first session identifier matches any stored session identifier. If so, it replies to the initiating node, updating the first session identifier. This interaction between the initiating node and the receiving node can resolve collision issues in sideways positioning sessions.

[0115] FIG3 is a flow chart showing a method for sending a session identifier for a sideline positioning session provided by an exemplary embodiment of the present application. Taking the method executed by a sending node as an example, the method includes at least some of the following steps:

[0116] Step 310: Send a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier;

[0117] Step 320: Receive first information, where the first information is used to request or instruct to change the first session identifier.

[0118] The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

[0119] The first information is an instruction for the receiving node to request or instruct to change the first session identifier when the first session identifier sent by the initial node is identical to any session identifier stored by the receiving node.

[0120] In some embodiments, when the first session identifier of the initiating node is identical to any stored session identifier of the receiving node, the initiating node receives first information for requesting or instructing a change in the first session identifier.

[0121] There are two implementation methods for the initial node to solve the problem of identical positioning session identifiers. In different embodiments, the initial node can adopt at least one of the two selection methods.

[0122] The first implementation method:

[0123] FIG4 shows an interactive diagram of a method for changing a sideline positioning session identifier provided by an exemplary embodiment of the present application. The method includes all or part of the following steps:

[0124] Step 401: The initial node sends a first sideways positioning protocol message;

[0125] In an optional example, the first sidelink positioning protocol message carries indication information, where the indication information is used to indicate that the first sidelink positioning protocol message is the first message or initial message of the first positioning session.

[0126] In some embodiments, during the sideways positioning process, in order to ensure the order and correctness of communications between different nodes, the first sideways positioning protocol message carries indication information, which can be used to identify the order of the sideways positioning protocol messages.

[0127] Optionally, the indication information may be expressed as at least one of a bit or a sequence number. Exemplarily, when the indication information is a bit, the bit may be set to 1 or 0. When the bit is 1, it indicates that the first sideline positioning protocol message is the first message or initial message of the first positioning session; when the bit is 0, it indicates that the first sideline positioning protocol message is not the first message or initial message of the first positioning session. In one possible implementation, when the indication information is a bit, the bit may be set to 1 or 0. When the bit is 0, it indicates that the first sideline positioning protocol message is the first message or initial message of the first positioning session; when the bit is 1, it indicates that the first sideline positioning protocol message is not the first message or initial message of the first positioning session.

[0128] Optionally, when the indication information is a sequence number, the first sidelink positioning protocol message may include a sequence number field for indicating the order of the first sidelink positioning protocol message in the positioning session.

[0129] It should be noted that the embodiments of the present application do not limit the manner in which the indication information is presented.

[0130] Step 402: The receiving node sends a first message to the initial node;

[0131] In some embodiments, when the receiving node detects that the first session identifier is the same as any stored session identifier, the receiving node sends first information to the initial node, where the first information is used to request or instruct to change the first session identifier.

[0132] Step 403: The initial node updates the first session identifier.

[0133] In some embodiments, after receiving the first information, the initial node updates the first session identifier in the first sidelink positioning protocol message, and the updated session identifier is different from the session identifier before the update.

[0134] In an optional example, the initial node sends a second sideways positioning protocol message to the receiving node. The second sideways positioning protocol message carries a second session identifier, and the second session identifier is a session identifier after being changed from the first positioning session.

[0135] Optionally, the initial node can be updated by feedback update. Exemplarily, when the initial node is updated by feedback update, the initial node can update the first session identifier to the second session identifier according to the instruction of the received first information. If the first information contains a new second session identifier, the initial node can update the first session identifier to the second session identifier according to the new identifier in the feedback information. It should be noted that the above is only an example of the method of updating the initial node, and the embodiments of the present application do not limit the method of updating the initial node.

[0136] In an optional example, the second sideline positioning protocol message carries indication information, where the indication information is used to indicate that the second sideline positioning protocol message is the first message or initial message of the first positioning session.

[0137] The manner of displaying the indication information is detailed in step 401 and will not be described again here.

[0138] Second implementation method:

[0139] FIG5 shows an interactive diagram of a method for changing a sideline positioning session identifier provided by an exemplary embodiment of the present application. The method includes all or part of the following steps:

[0140] Step 501: The initial node sends a first sideways positioning protocol message;

[0141] Step 502: The receiving node sends a first message to the initial node;

[0142] Step 503: The initial node removes the receiving node from the first session.

[0143] In one optional example, after receiving the first information, the initiating node removes the receiving node from the first positioning session; wherein the receiving node is the node that receives the first sidelink positioning protocol message and / or the receiving node is the node that sends the first information. Optionally, the receiving node is an anchor terminal.

[0144] Exemplarily, the initial node may remove the receiving node from the first session by terminating the connection. Optionally, when the removal method is to terminate the connection, the initial node may proactively terminate the communication link with the receiving node to ensure that the receiving node can no longer participate in the current first positioning session. Optionally, the initial node may not terminate the communication link with the receiving node, and the communication link remains, but the initial node no longer sends side positioning messages related to the first session to the receiving node. In some embodiments, after the initial node removes the receiving node from the first session, the initial node no longer sends other messages in the first session to the receiving node.

[0145] It should be noted that the above is only an exemplary description of the manner in which the initial node removes the receiving node from the first positioning session, and the embodiment of the present application does not limit the manner of removal.

[0146] In summary, in the method provided in this embodiment, when the initiating node receives the first message from the receiving node requesting a change in the first session identifier, the initiating node has two options: updating the first session identifier or removing the receiving node from the first session to prevent it from being identical to any of the receiving node's stored session identifiers. Using these two options, the initiating node can manage and control the sideline positioning session, effectively resolving the issue of duplicate session identifiers.

[0147] It should be noted that the steps shown in FIG. 4 can be combined with the first implementation to form an embodiment, and the steps shown in FIG. 4 can be combined with the second implementation to form an embodiment.

[0148] FIG6 shows an interactive diagram of a method for changing a sideline positioning session identifier provided by an exemplary embodiment of the present application. Taking the method executed by an initiating UE, an anchor UE, and a server UE as an example, the method includes at least some of the following steps:

[0149] Step 601: The initiating UE initiates a first positioning session;

[0150] The initiating UE refers to the terminal device that initiates the positioning request, which sends sideline positioning-related messages or requests to other terminal devices.

[0151] In some embodiments, the initiating UE sends a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier.

[0152] Step 602: The server UE detects the positioning session identifier;

[0153] In some embodiments, the server UE is a terminal device that receives and processes sidewalk positioning requests and is capable of receiving messages from the initiating UE. In some embodiments, the anchor UE compares the first session identifier of the initiating UE with any of its stored session identifiers to determine whether the first session identifier is the same as any of the stored session identifiers of the server UE.

[0154] Step 603: The anchor UE performs collision detection notification;

[0155] A collision refers to a situation where the first session identifier is the same as any session identifier stored by the receiving node.

[0156] In some embodiments, the anchor UE participates in a collision detection notification in a sidewalk positioning session during the sidewalk positioning process, supporting the conduct of the sidewalk positioning session. If the first session identifier is identical to any session identifier stored by the server UE, the anchor UE sends a first message to the initiating UE, where the first message is sent when the first session identifier is identical to any session identifier stored by the server UE.

[0157] Step 604: The initiating UE removes the anchor UE from the positioning session;

[0158] In some embodiments, the initiating UE removes the anchor UE from the first positioning session, which means that the initiating UE no longer regards the anchor UE as a part of the first positioning session, and the anchor UE no longer participates in the sidewalk positioning session.

[0159] Step 605: The initiating UE initiates a second positioning session and updates the first positioning session identifier to a second session identifier.

[0160] In some embodiments, the initiating UE initiates a new sidewalk positioning session and sends a second sidewalk positioning protocol message to the anchor UE. The second sidewalk positioning protocol message carries a second session identifier, which is a session identifier obtained by changing the first session identifier.

[0161] To sum up, the method provided in this embodiment is that the initiating UE initiates a first session request to the anchor UE. If the first session identifier of the initiating UE conflicts with any stored session identifier of the server UE, the anchor UE will send a collision detection notification to the initiating UE. The initiating UE can choose to remove the anchor UE from the first session, or the initiating UE re-initiates the side positioning session and updates the first positioning session identifier to the second session identifier.

[0162] FIG7 shows a flow chart of a method for generating a session identifier for a sideline positioning session provided by an exemplary embodiment of the present application. The method includes all or part of the following steps:

[0163] Step 710: Generate a third session identifier of the sidewalk positioning session, where the third session identifier is related to at least one of the first information and the second information.

[0164] The first information is a unique identifier of the initial node, and the second information is distinctive information of the initial node when initializing different sideline positioning sessions.

[0165] The third session identifier is used to identify the sideline positioning session to which the sideline positioning protocol message belongs. The generation of the third session identifier requires combining or calculating at least one of the first information and the second information.

[0166] In some embodiments, the first information refers to a unique identifier of the initiating node, used to generate a portion of the session identifier. Alternatively, the first information may be a unique identifier of a terminal device. Alternatively, the first information may be a unique identifier used among multiple terminal devices. The multiple terminal devices may include all terminal devices, all terminal devices within a certain area, or all terminal devices within a certain range of the initiating node.

[0167] Exemplarily, the initial node is a terminal device, and the first information may be the International Mobile Equipment Identity (IMEI) of the terminal device. The IMEI is a unique identifier for identifying the terminal device.

[0168] In some embodiments, the second information refers to distinctive information used by the initial node when initializing different side positioning.

[0169] Optionally, the second information is the number of sideline positioning sessions used in the initial node.

[0170] Optionally, the second information may be a timestamp. Each time a side positioning session is initialized, the timestamp will be different, and thus the session identifier will also be different, thereby distinguishing different side positioning sessions.

[0171] Optionally, the second information is the maximum value of the session identifiers of the side positioning sessions used in the initial node. In some embodiments, when the session identifier of the side positioning session is the maximum value of the session identifiers of the side positioning sessions used in the initial node, the third session identifier is determined based on the maximum value of the session identifier and a second value, and the second value is a positive integer. In some embodiments, the third session identifier is the sum of the maximum value of the session identifier and the second value. In some embodiments, the maximum value of the session identifier of the side positioning session used in the initial node includes the first information and the second information; in some embodiments, the maximum value of the session identifier of the side positioning session used in the initial node is the maximum value of the session identifier accumulated successively from the initial value, and the initial value can be 1 or other possible values.

[0172] In summary, in the method provided in this embodiment, the session identifier of a side positioning session consists of at least one of the unique identifier of the initiating node and information that distinguishes the initiating node when initiating different side positioning sessions. By making the session identifier of a side positioning session unique, the problem of duplicate session identifiers in other side positioning sessions can be avoided.

[0173] FIG8 is a flow chart showing a method for generating a session identifier for a sideline positioning session provided by an exemplary embodiment of the present application. The method includes all or part of the following steps:

[0174] Step 810: Obtain second information, where the second information is the number of sideline positioning sessions used in the initial node;

[0175] In an optional example, the second information is the number of side positioning sessions that have been used in the initial node. In some embodiments, each time a side positioning session is initialized, the number of side positioning sessions will increase. Exemplarily, the initial node is a terminal device, and a counter can be used in the terminal device to record the second information through a timer. Initially, the counter is 0, when the side positioning session is initialized for the first time, the timer is 1, when the side positioning session is initialized for the second time, the timer is again incremented to 2, and so on. Each time a side positioning session is initialized, the timer increments. It should be noted that after performing the above steps, the second information needs to be updated.

[0176] Step 820: Generate a session identifier for the sideline positioning session, where the session identifier is associated with the first information and the second information.

[0177] The first information is the unique identifier of the initial node.

[0178] In some embodiments, the first information refers to a unique identifier of the initiating node, used to generate a portion of the session identifier. Alternatively, the first information may be a unique identifier of a terminal device. Alternatively, the first information may be a unique identifier used among multiple terminal devices. The multiple terminal devices may include all terminal devices, all terminal devices within a certain area, or all terminal devices within a certain range of the initiating node.

[0179] Exemplarily, the initial node is a terminal device, and the first information may be the IMEI of the terminal device, where the IMEI is a unique identifier for identifying the terminal device.

[0180] In an optional example, the third session identifier is obtained by concatenating the first information and the second information.

[0181] Concatenation refers to the process or operation of connecting two or more objects or information together to form a whole. In some embodiments, concatenation refers to connecting the first information and the second information together to form a session identifier.

[0182] For example, the first information and the second information can be concatenated together using a string to form a new string that serves as a session identifier for the sideline positioning session. In some embodiments, the third session identifier can be at least one of the two cascade methods: the first information + the second information, or the second information + the first information.

[0183] In an optional example, the third session identifier is obtained by concatenating the first information and the third information, the third information is determined based on the second information and the first value, and the first value is a positive integer. In some embodiments, the third information is equal to the sum of the second information and the first value.

[0184] In some embodiments, the second information is added to the first value to obtain the third information, and the third information is cascaded with the first information to obtain the session identifier. The first value can be any positive integer. For example, the first value is 2; for another example, the first value is 1. Exemplarily, the first information is 111, the first value is 1, the starting value of the second information is 1, and the session identifiers of the 6 side positioning sessions that have been used are 1111, 1112, 1113, 1114, 1115, and 1116. Even when one or more side positioning sessions end (for example, the side session corresponding to 1115 ends), the session identifier of the next side positioning session is 1117. That is, the session identifier of the ended side positioning session is no longer used.

[0185] In some embodiments, the third session identifier may be at least one of the two cascade modes of the first information + the third information or the third information + the first information.

[0186] In some other embodiments, the session identifier of the ended sideline positioning session may also be reused, as shown in the following steps:

[0187] Step 830: When the second positioning session in the initialized lateral positioning session ends, the session identifier corresponding to the second positioning session is generated as the session identifier of the next lateral positioning session;

[0188] In some embodiments, in a sidewalk positioning session, the second information is the number of used sidewalk positioning sessions. The communication system assigns a session identifier to the initial node based on the number of used sidewalk positioning sessions. When an initialized second positioning session ends, the session identifier of the second positioning session becomes idle. Optionally, the idle session identifier can be allocated for use in subsequent sidewalk positioning sessions.

[0189] In order for the receiving node to clearly know that the session identifier of the second positioning session has become idle, there are two ways to determine (at least one of which can be used):

[0190] Method 1:

[0191] When the second positioning session in the initialized sidewalk positioning session ends, the initiating node sends a notification message to the receiving node, which is used to notify the session release of the second positioning session or that the session identifier of the second positioning session has been released, invalidated or idle.

[0192] Method 2:

[0193] In some embodiments, a first timer is set within the initial node. The start time of the first timer is determined based on the end time of the second positioning session, or the start time or reset time of the first timer is determined based on the time when the last message of the second positioning session is sent. After the first timer expires, the session identifier of the second positioning session is used to generate the session identifier of the next sideways positioning session. In some embodiments, the duration of the timer can be predefined by the communication protocol, preconfigured by the network device, or negotiated between terminal devices. For example, the timer is 0.5ms.

[0194] It should be noted that, in order for the receiving node to clearly know that the session identifier of the second positioning session has become idle, in one possible implementation, method 1 and method 2 may be executed simultaneously, or method 1 may be executed alone, or method 2 may be executed alone.

[0195] In some embodiments, when the session identifier corresponding to the second positioning session is generated as the session identifier of the next sideline positioning session, the number of used sideline positioning sessions is temporarily increased.

[0196] In some embodiments, when the time for the session identifier of the second positioning session to become idle reaches a first duration, the session identifier corresponding to the second positioning session is generated as the session identifier of the next parallel positioning session, and the first duration is the timing duration of the above timer.

[0197] Step 840: After the second information grows to a maximum value corresponding to N bits, reset the second information, where N is a positive integer.

[0198] The second information is the number of used sideline positioning sessions.

[0199] In some embodiments, the second information is represented by N bits. When the second information reaches the maximum value represented by N bits, the second information can be reset and accumulation can be restarted. This approach can keep the second information within a reasonable range. In some embodiments, after the second information is reset, the session identifier in the sideline positioning session needs to be reset at the same time.

[0200] For example, an 8-bit binary number is used to represent the second information. Initially, the value of the second information is 0. Each time the initial node initiates a new side positioning session, the second information is incremented by 1. When the second information reaches 11111111, it reaches the maximum value of 255 that can be represented by 8 bits. At this time, the second information is reset to 0 and accumulation begins again. The same 8 bits can be used cyclically to represent the number of side positioning sessions, ensuring that the range of the second information is within a controllable range and maintaining data accuracy.

[0201] To summarize, the method provided in this embodiment, when the second information is the number of side positioning sessions used in the initial node, can set a timer in the receiving node to indicate the end of the side positioning session; or, after the second information is increased to the maximum value corresponding to N bits, the second information is reset. This method maintains the second information within a reasonable range.

[0202] It should be noted that the above steps 810 and 820 can be implemented as a new embodiment. The above steps 810, 820, and 830 can be implemented as a new embodiment. The above steps 810, 820, and 840 can be implemented as a new embodiment.

[0203] FIG9 shows a flow chart of a method for generating a session identifier for a sideline positioning session provided by an exemplary embodiment of the present application. The method includes all or part of the following steps:

[0204] Step 910: Acquire second information, where the second information is a timestamp based on absolute time;

[0205] In an optional example, the second information is a timestamp based on absolute time. The granularity of the timestamp can be predefined by the communication protocol or preconfigured by the network device or negotiated between terminals. For example, the timestamp is a timestamp at the second level or a timestamp at the microsecond level.

[0206] For example, the initial node is a terminal device. Each time a side positioning session is initialized, a timestamp of the absolute time of the current time can be obtained as the second information. In different side positioning sessions, the timestamp of the absolute time each time a side positioning session is initialized will be different, and therefore the session identifier of the side positioning session will be different.

[0207] Step 920: Generate a session identifier for the sideline positioning session, where the session identifier is associated with the first information and the second information.

[0208] The first information is the unique identifier of the initial node.

[0209] In some embodiments, the first information refers to a unique identifier of the initiating node, used to generate a portion of the session identifier. Alternatively, the first information may be a unique identifier of a terminal device. Alternatively, the first information may be a unique identifier used among multiple terminal devices. The multiple terminal devices may include all terminal devices, all terminal devices within a certain area, or all terminal devices within a certain range of the initiating node.

[0210] Exemplarily, the initial node is a terminal device, and the first information may be the IMEI of the terminal device, where the IMEI is a unique identifier for identifying a mobile phone device.

[0211] In an optional example, the session identifier is obtained by concatenating the first information and the second information.

[0212] Concatenation refers to the process or operation of connecting two or more objects or information together to form a whole. In some embodiments, concatenation refers to connecting the first information and the second information together to form a session identifier.

[0213] For example, the first information and the second information can be concatenated together through a string to form a new string as a session identifier for the sideline positioning session. In some embodiments, the session identifier can be at least one of the two cascade methods: the first information + the second information, or the second information + the first information.

[0214] In an optional example, the third session identifier is obtained by concatenating the first information and the third information, the third information is determined based on the second information and the first value, and the first value is a positive integer. In some embodiments, the third information is equal to the sum of the second information and the first value.

[0215] In some embodiments, the second information is added to the first value to obtain the third information, and the third information is concatenated with the first information to obtain a session identifier. The first value can be any positive integer. For example, the first value is 2; for another example, the first value is 1. In some embodiments, the third session identifier can be at least one of the concatenation of the first information plus the third information or the third information plus the first information.

[0216] FIG10 shows a flow chart of a method for receiving a session identifier of a sideline positioning session provided by an exemplary embodiment of the present application. The method includes all or part of the following steps:

[0217] Step 1010: Receive a third sideline positioning protocol message, where the third sideline positioning protocol message carries a session identifier of a second positioning session;

[0218] The third sideways positioning protocol message refers to a message sent by an initial node to a receiving node in the sideways positioning protocol for transmitting and exchanging information to support the execution of the sideways positioning process.

[0219] Optionally, the third sideline positioning protocol message is the latest or last message in the sideline positioning session.

[0220] In some embodiments, when the second positioning session in the initialized sideline positioning session ends, the session identifier corresponding to the second positioning session is generated as the session identifier of the next sideline positioning session, and the initial node sends a third sideline positioning protocol message to the receiving node. The third sideline positioning protocol includes a session identifier that is released, invalid, or idle in the second positioning session.

[0221] Step 1020: After the second timer expires, the session identifier of the second positioning session is released, invalidated, or idled.

[0222] The start time of the second timer is determined by the end time of the second positioning session, or the start time or reset time of the second timer is determined based on the reception time of the third sidelink positioning protocol message.

[0223] In an optional example, the session identifier of the second positioning session is related to at least one of the first information and the second information, wherein the first information is the unique identifier of the initial node, and the second information is distinctive information of the initial node when initializing different sideline positioning sessions.

[0224] In some embodiments, a second timer associated with the second positioning session is set in the receiving node. The receiving node receives a notification message sent by the initial node, and the notification message is used to indicate the end of the second positioning session. The start time of the second timer can be determined based on the end time of the second positioning session; or, the start time or reset time of the second timer is determined based on the reception time of the third side positioning protocol message. The second timer is reset when a message related to the second positioning session is received. After receiving the notification message or timing out, the receiving node is triggered to regard the session identifier of the second positioning session as invalid or idle. In some embodiments, the timing duration of the timer can be predefined by the communication protocol, preconfigured by the network device, or negotiated between terminal devices. For example, the timer is 0.5ms.

[0225] To sum up, the method provided in this embodiment is that the initial node sends a third side positioning protocol message carrying the session identifier of the second positioning session to the receiving node, and after the second timer times out, the session identifier of the second positioning session is released or invalidated or idle. This method can ensure that the receiving node can promptly know the release or idle status of the session identifier, thereby improving the efficiency and accuracy of the communication system.

[0226] FIG11 shows an interactive diagram of a method for changing a sidewalk positioning session identifier provided by an exemplary embodiment of the present application. Taking the method performed by the initiating UE and the anchor UE as an example, the method includes at least some of the following steps:

[0227] Step 1101: The initiating UE initiates a sidewalk positioning session;

[0228] The initiating UE refers to the terminal device that initiates the positioning request, which sends a sideline positioning-related message or request to the anchor UE.

[0229] An anchor UE refers to a terminal device that serves as a reference device and is used to provide reference information to the initiating UE.

[0230] In some embodiments, the initiating UE initiates a sidewalk positioning session by sending a sidewalk positioning protocol message to the anchor UE. The sidewalk positioning protocol message carries a session identifier, which is used to identify the sidewalk positioning session to which the sidewalk positioning protocol message belongs.

[0231] Step 1102: The anchor UE concatenates the first information and the second information to obtain a session identifier;

[0232] The first information is a unique identifier of the initial node, and the second information is distinguishing information used by the initial node when initiating different sideline positioning sessions. Optionally, the first information may be a unique identifier of the terminal device, and the second information may be the number of sideline positioning sessions used within the initial node, or the second information may be a timestamp based on absolute time.

[0233] In some embodiments, the anchor UE obtains a session identifier by concatenating the first information and the second information, and the session identifier is unique.

[0234] Step 1103: The anchor UE sends the session identifier to the initiating UE.

[0235] In some embodiments, the anchor UE sends the session identifier to the initiating UE, and the initiating UE may associate the session identifier with its own sidewalk positioning request to ensure that the initiating UE can correctly identify and process the sidewalk positioning session related to itself.

[0236] In summary, the method provided in this embodiment is that after the initiating UE initiates a side positioning session, the anchor UE cascades the first information and the second information to obtain a session identifier. The session identifier is unique and can effectively avoid the problem of identical positioning identifiers in the side positioning session.

[0237] It should be noted that, in one possible implementation, the steps shown in FIG4 can be combined with the steps shown in FIG9 to form a new embodiment, or the steps shown in FIG5 can be combined with the steps shown in FIG9 to form a new embodiment, or the steps shown in FIG6 can be combined with the steps shown in FIG9 to form a new embodiment, which will not be repeated here.

[0238] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0239] FIG12 shows a block diagram of a device for receiving a session identifier for a side-by-side positioning session provided by an exemplary embodiment of the present application. The device has the function of implementing the method for receiving a session identifier for a side-by-side positioning session described above. The device may include: a first receiving module 1210 and a first sending module 1220;

[0240] The first receiving module 1210 is configured to receive a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier;

[0241] The first sideways positioning protocol message refers to a message sent by an initial node and received by the first receiving module 1210 in the sideways positioning protocol for transmitting and exchanging information to support the execution of the sideways positioning process.

[0242] Optionally, the first sideways positioning protocol message is the first message in the sideways positioning session.

[0243] The first session identifier is an identifier carried in the first sidelink positioning protocol message, and is used to identify the positioning session to which the message belongs.

[0244] A positioning session refers to a series of interactions and communications between different nodes during the side positioning process.

[0245] In some embodiments, the first receiving module 1210 receives a first sidelink positioning protocol message sent by the initial node and carrying a first session identifier. The first receiving module 1210 compares the received first session identifier with any stored session identifiers to detect whether there is a collision. A collision refers to a situation where the first session identifier overlaps with any stored session identifier.

[0246] In some embodiments, any stored session identifier refers to a session identifier of a side positioning session that has been stored in the first receiving module 1210. In a side positioning session, each side positioning session is assigned a unique session identifier to distinguish different side positioning sessions. Each time the initial node sends a side positioning protocol message to the first receiving module 1210, the first receiving module 1210 stores the session identifier of the side positioning protocol message to identify the side positioning session.

[0247] The first sending module 1220 is configured to send first information when the first session identifier is the same as any stored session identifier, where the first information is used to request or instruct to change the first session identifier.

[0248] The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

[0249] In an optional example, the first message is sent when the first session identifier is the same as any session identifier stored in the first receiving module 1210 .

[0250] In some embodiments, the first information is used to request or instruct to change the first session identifier when the first session identifier is the same as any stored session identifier, so as to avoid conflict with any stored session identifier.

[0251] Optionally, the first information indicates a change in the first session identifier, and the first sending module 1220 may indicate this by sending at least one of a session control message (Session Control Information, SCI) or an SLPP message to the initial node. Exemplarily, SCI is a message format for controlling and managing communication services, and is used to exchange side positioning session control information between a terminal device and a network. Through SCI, the first sending module 1220 may send a request indicating a change in the session identifier. Exemplarily, SLPP is a protocol for transmitting side positioning session control information between a terminal device and a network. Through the SLPP message, the first sending module 1220 may send information containing an indication of a change in the session identifier, for requesting or instructing the initial node to change the first session identifier.

[0252] It should be noted that the embodiment of the present application does not limit the manner in which the first information indicates the change of the first session identifier.

[0253] In summary, in the apparatus provided in this embodiment, the first receiving module 1210 receives a first sideways positioning protocol message sent by an initial node and carrying a first session identifier. The first receiving module 1210 detects whether the first session identifier is identical to any stored session identifier. If so, the module replies to the initial node to update the first session identifier. This interaction between the initial node and the apparatus can resolve collision issues in sideways positioning sessions.

[0254] FIG13 shows a block diagram of a device for sending a session identifier for a side-by-side positioning session according to an exemplary embodiment of the present application. The device has the function of implementing the method for sending a session identifier for a side-by-side positioning session. The device may include: a second receiving module 1310, a second sending module 1320, an updating module 1330, and a removing module 1340;

[0255] The second sending module 1320 is configured to send a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier;

[0256] The second receiving module 1310 is configured to receive first information, where the first information is used to request or instruct to change the first session identifier.

[0257] The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

[0258] In some embodiments, when the first session identifier is identical to any session identifier stored by the receiving node, the receiving node requests or instructs an instruction to change the first session identifier, and the second receiving module 1310 receives the first information.

[0259] The first information is used to request or instruct to change the first session identifier.

[0260] In some embodiments, the apparatus further includes an update module 1330 .

[0261] The updating module 1330 is configured to update the first session identifier.

[0262] In some embodiments, after the second receiving module 1310 receives the first information, the updating module 1330 updates the first session identifier in the first sidelink positioning protocol message, and the updated session identifier is different from the session identifier before the update.

[0263] In an optional example, the second sending module 1320 is further configured to send a second sideline positioning protocol message to the receiving node, where the second sideline positioning protocol message carries a second session identifier, which is a session identifier after the first positioning session is changed.

[0264] Optionally, the update module 1330 can be updated via feedback. For example, when the device is updated via feedback, the second receiving module 1310 can update the first session identifier to the second session identifier based on the instructions of the received first information. If the first information includes a new second session identifier, the update module 1330 can update the first session identifier to the second session identifier based on the new identifier in the feedback information. It should be noted that the above is merely an example of the update method of the update module 1330, and the embodiments of the present application do not limit the update method of the update module 1330.

[0265] In an optional example, the second sideline positioning protocol message carries indication information, where the indication information is used to indicate that the second sideline positioning protocol message is the first message or initial message of the first positioning session.

[0266] In some embodiments, the apparatus further includes a rejection module 1340 .

[0267] The removing module 1340 is configured to remove the receiving node from the first session.

[0268] In one optional example, after receiving the first information, the second receiving module 1310 removes the receiving node from the first positioning session; wherein the receiving node is a node that receives the first sidelink positioning protocol message and / or the receiving node is a node that sends the first information. Optionally, the receiving node is an anchor terminal.

[0269] Exemplarily, the removal module 1340 may remove the receiving node from the first session by terminating the connection. Optionally, when the removal method is to terminate the connection, the device may actively terminate the communication link with the receiving node to ensure that the receiving node can no longer participate in the current first positioning session. Optionally, the device may not terminate the communication link with the receiving node, and the communication link is still maintained, but the device no longer sends side positioning messages related to the first session to the receiving node. In some embodiments, after the removal module 1340 removes the receiving node from the first session, the device no longer sends other messages in the first session to the receiving node.

[0270] It should be noted that the above is only an exemplary description of the manner in which the removal module 1340 removes the receiving node from the first positioning session, and the embodiment of the present application does not limit the removal manner.

[0271] In summary, in the apparatus provided by this embodiment, when the second receiving module 1310 receives the first information requesting a change in the first session identifier from the receiving node, the apparatus has two options: the updating module 1330 can choose to update the first session identifier, or the removal module 1340 can remove the receiving node from the first session to prevent the receiving node from having the same session identifier as any other session identifier already stored by the receiving node. Through these two methods, the apparatus can manage and control the sideline positioning session, effectively resolving the issue of duplicate session identifiers.

[0272] It should be noted that the second sending module 1320, the second receiving module 1310 and the update module 1330 can be implemented as an embodiment, the second sending module 1320, the second receiving module 1310 and the elimination module 1340 can be implemented as an embodiment, and the second sending module 1320, the second receiving module 1310, the update module 1330 and the elimination module 1340 can be implemented as an embodiment, which will not be repeated here.

[0273] Figure 14 shows a block diagram of a device for generating a session identifier for a side-by-side positioning session, provided by an exemplary embodiment of the present application. The device has the function of implementing the method for generating a session identifier for a side-by-side positioning session. The device may include: a generating module 1410, an acquiring module 1420, a resetting module 1430, and a sending module 1440;

[0274] The generating module 1410 is configured to generate a third session identifier of the sideline positioning session, where the third session identifier is related to at least one of the first information and the second information.

[0275] The first information is a unique identifier of the device, and the second information is distinctive information used by the device when initializing different sideline positioning sessions.

[0276] The session identifier is used to identify the sideline positioning session to which the sideline positioning protocol message belongs. The generation of the session identifier requires combining or calculating at least one of the first information and the second information.

[0277] In some embodiments, the first information is a unique identifier of the device, used to generate a portion of the session identifier. Alternatively, the first information may be a unique identifier of a terminal device. Alternatively, the first information may be a unique identifier used among multiple terminal devices. The multiple terminal devices may include all terminal devices, all terminal devices within a certain area, or all terminal devices within a certain range of the device.

[0278] Exemplarily, the apparatus is a terminal device, and the first information may be the IMEI of the terminal device, where the IMEI is a unique identifier for identifying the terminal device.

[0279] In some embodiments, the second information refers to information that is distinguishable when the device initiates different lateral positioning.

[0280] Optionally, the second information is the number of sideline positioning sessions used in the device.

[0281] Optionally, the second session identifier may be a timestamp. Each time a side positioning session is initialized, the timestamp will be different, and thus the session identifier will also be different, thereby distinguishing different side positioning sessions.

[0282] Optionally, the second information is the maximum value of the session identifiers of the side positioning sessions already used within the device. In some embodiments, when the session identifier of the side positioning session is the maximum value of the session identifiers of the side positioning sessions already used within the device, the third session identifier is determined based on the maximum value of the session identifier and a second value, where the second value is a positive integer. In some embodiments, the third session identifier is the sum of the maximum value of the session identifier and the second value. In some embodiments, the maximum value of the session identifiers of the side positioning sessions already used within the initial node includes the first information and the second information; in some embodiments, the maximum value of the session identifiers of the side positioning sessions already used within the initial node is the maximum value of the session identifiers accumulated from an initial value, where the initial value can be 1 or other possible values. In summary, in the method provided in this embodiment, the session identifier of the side positioning session is composed of at least one of the unique identifier of the device and information that distinguishes the device when initializing different side positioning sessions. By making the session identifier of the side positioning session unique, the problem of identical session identifiers in side positioning sessions can be avoided.

[0283] In some embodiments, the apparatus further includes an acquisition module 1420 .

[0284] An acquiring module 1420 is configured to acquire second information, the second information including the number of used sideline positioning sessions;

[0285] In an optional example, the second information is the number of sideline positioning sessions used in the device.

[0286] In some embodiments, the number of side positioning sessions increments each time a side positioning session is initialized. Exemplarily, the apparatus is a terminal device, and a counter can be used in the terminal device to record the second information via a timer. Initially, the counter is 0. When a side positioning session is initialized for the first time, the timer is 1. When a side positioning session is initialized for the second time, the timer increments again to 2, and so on. Each time a side positioning session is initialized, the timer increments.

[0287] It should be noted that after executing the above steps, the second information needs to be updated.

[0288] A generating module 1410 is configured to generate a session identifier for a sideline positioning session, where the session identifier is associated with the first information and the second information;

[0289] The first information is a unique identifier of the device.

[0290] In some embodiments, the first information is a unique identifier of the device, used to generate a portion of the session identifier. Alternatively, the first information may be a unique identifier of a terminal device. Alternatively, the first information may be a unique identifier used among multiple terminal devices. The multiple terminal devices may include all terminal devices, all terminal devices within a certain area, or all terminal devices within a certain range of the device.

[0291] Exemplarily, the apparatus is a terminal device, and the first information may be the IMEI of the terminal device, where the IMEI is a unique identifier for identifying the terminal device.

[0292] In an optional example, the third session identifier is obtained by concatenating the first information and the second information.

[0293] Concatenation refers to the process or operation of connecting two or more objects or information together to form a whole. In some embodiments, concatenation refers to connecting the first information and the second information together to form a session identifier.

[0294] Exemplarily, the first information and the second information may be connected together through a character string to form a new character string, which serves as a session identifier of the sideline positioning session.

[0295] In some embodiments, the third session identifier may be at least one of the two cascade modes of the first information + the second information or the second information + the first information.

[0296] In an optional example, the third session identifier is obtained by concatenating the first information and the third information, the third information is determined based on the second information and the first value, and the first value is a positive integer. In some embodiments, the third information is equal to the sum of the second information and the first value.

[0297] In some embodiments, the second information is added to the first value to obtain the third information, and the third information is cascaded with the first information to obtain a session identifier. The first value can be any positive integer. For example, the first value is 2; for another example, the first value is 1. Exemplarily, the first information is 111, the first value is 1, the starting value of the second information is 1, and the session identifiers of the 6 side positioning sessions that have been used are 1111, 1112, 1113, 1114, 1115, and 1116. Even when one or more side positioning sessions end (for example, the side positioning session corresponding to 1115 ends), the session identifier of the next side positioning session is 1117. That is, the session identifier of the ended side positioning session is no longer used. In some embodiments, the third session identifier can be at least one of the two cascade methods of the first information + the third information or the third information + the first information.

[0298] The generating module 1410 is configured to generate a session identifier corresponding to the second positioning session as a session identifier of a next sideways positioning session when the second positioning session in the initialized sideways positioning session ends;

[0299] In some embodiments, in a sideline positioning session, the second information is the number of used sideline positioning sessions. The communication system assigns a session identifier to the device based on the number of used sideline positioning sessions. When an initialized second positioning session ends, the session identifier of the second positioning session becomes idle. Optionally, the idle session identifier can be allocated for use in subsequent sideline positioning sessions.

[0300] In order for the receiving node to clearly know that the session identifier of the second positioning session has become idle, there are two ways to determine (at least one of which can be used):

[0301] Method 1:

[0302] The sending module 1440 is configured to send a notification message to the receiving node when the second positioning session in the initialized sidewalk positioning session ends. The notification message is used to notify the receiving node that the second positioning session is released, or the session identifier of the second positioning session has been released, invalidated, or idle.

[0303] Method 2:

[0304] In some embodiments, a first timer is provided in the device, and the start time of the first timer is determined based on the end time of the second positioning session, or the start time or reset time of the first timer is determined based on the sending time of the last message of the second positioning session.

[0305] The generating module 1410 is configured to generate a session identifier of a next sideways positioning session from the session identifier of the second positioning session after the first timer times out.

[0306] In some embodiments, the timing duration of the timer may be predefined by the communication protocol, preconfigured by the network device, or negotiated between terminal devices. For example, the timer is 0.5 ms.

[0307] It should be noted that, in order for the receiving node to clearly know that the session identifier of the second positioning session has become idle, in one possible implementation, method 1 and method 2 may be executed simultaneously, or method 1 may be executed alone, or method 2 may be executed alone.

[0308] In some embodiments, when the session identifier corresponding to the second positioning session is generated as the session identifier of the next sideline positioning session, the number of used sideline positioning sessions is temporarily increased.

[0309] In some embodiments, when the time for the session identifier of the second positioning session to become idle reaches a first duration, the session identifier corresponding to the second positioning session is generated as the session identifier of the next parallel positioning session, and the first duration is the timing duration of the above timer.

[0310] In some embodiments, the apparatus further includes a reset module 1430 .

[0311] The resetting module 1430 is configured to reset the second information after the second information grows to a maximum value corresponding to N bits, where N is a positive integer.

[0312] The second information is the number of used sideline positioning sessions.

[0313] In some embodiments, the second information is represented by N bits. When the second information reaches the maximum value represented by N bits, the second information can be reset and accumulation can be restarted. This approach can keep the second information within a reasonable range.

[0314] For example, an 8-bit binary number is used to represent the second information. Initially, the value of the second information is 0. Each time the reset module 1430 initiates a new side-track positioning session, the second information is incremented by 1. When the second information reaches 11111111, it reaches the maximum value of 255 that can be represented by 8 bits. At this point, the second information is reset to 0 and accumulation begins again. The same 8 bits can be used cyclically to represent the number of side-track positioning sessions, ensuring that the range of the second information is within a controllable range and maintaining data accuracy.

[0315] To summarize, the method provided in this embodiment, when the second information is the number of side positioning sessions used in the device, can set a timer in the receiving node to indicate the end of the side positioning session; or, after the second information is increased to the maximum value corresponding to N bits, the second information is reset. In this way, the second information is maintained within a reasonable range.

[0316] An acquisition module 1420 is configured to acquire second information, where the second information is a timestamp based on absolute time;

[0317] In an optional example, the second information is a timestamp based on absolute time. The granularity of the timestamp can be predefined by the communication protocol or preconfigured by the network device or negotiated between terminals. For example, the timestamp is a timestamp at the second level or a timestamp at the microsecond level.

[0318] Exemplarily, the apparatus is a terminal device. Each time a side positioning session is initialized, the acquisition module 1420 may acquire a timestamp of the absolute time of the current time as the second information. In different side positioning sessions, the absolute time timestamp will be different each time a side positioning session is initialized, and therefore the session identifier of the side positioning session will be different.

[0319] The generating module 1410 is configured to generate a session identifier of a sideline positioning session, where the session identifier is associated with the first information and the second information.

[0320] The first information is a unique identifier of the device.

[0321] In some embodiments, the first information is a unique identifier of the device, used to generate a portion of the session identifier. Alternatively, the first information may be a unique identifier of a terminal device. Alternatively, the first information may be a unique identifier used among multiple terminal devices. The multiple terminal devices may include all terminal devices, all terminal devices within a certain area, or all terminal devices within a certain range of the device.

[0322] Exemplarily, the apparatus is a terminal device, and the first information may be the IMEI of the terminal device, where the IMEI is a unique identifier for identifying the terminal device.

[0323] In an optional example, the session identifier is obtained by concatenating the first information and the second information.

[0324] Concatenation refers to the process or operation of connecting two or more objects or information together to form a whole. In some embodiments, concatenation refers to connecting the first information and the second information together to form a session identifier.

[0325] Exemplarily, the first information and the second information may be connected together through a character string to form a new character string, which serves as a session identifier of the sideline positioning session.

[0326] In some embodiments, the session identifier may be at least one of the two cascade modes of first information + second information and second information + first information.

[0327] In an optional example, the third session identifier is obtained by concatenating the first information and the third information, the third information is determined based on the second information and the first value, and the first value is a positive integer. In some embodiments, the third information is equal to the sum of the second information and the first value.

[0328] In some embodiments, the second information is added to the first value to obtain the third information, and the third information is cascaded with the first information to obtain a session identifier, and the first value can be any positive integer. For example, the first value is 2; for another example, the first value is 1. In some embodiments, the third session identifier can be the first information + the third information, or at least one of the two cascade methods of the third information + the first information. It should be noted that the generation module 1410 can be implemented as an embodiment alone, the generation module 1410 and the acquisition module 1420 can be implemented as an embodiment, the generation module 1410 and the reset module 1430 can be implemented as an embodiment, and the generation module 1410 and the sending module 1440 can be implemented as an embodiment, which will not be repeated here.

[0329] It should be noted that the apparatus provided in the above embodiments only uses the division of the above functional modules as an example to illustrate the implementation of its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the terminal device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0330] FIG15 shows a block diagram of a device for receiving a session identifier for a side-by-side positioning session provided by an exemplary embodiment of the present application. The device has the function of implementing the method for receiving a session identifier for a side-by-side positioning session described above. The device may include: a third receiving module 1510 and an execution module 1520;

[0331] The third receiving module 1510 is configured to receive a third sideline positioning protocol message, where the third sideline positioning protocol message carries a session identifier of a second positioning session;

[0332] The third sideways positioning protocol message refers to a message sent by the initial node to the third receiving module 1510 in the sideways positioning protocol for transmitting and exchanging information to support the execution of the sideways positioning process.

[0333] Optionally, the third sideline positioning protocol message is the latest or last message in the sideline positioning session.

[0334] In some embodiments, when the second positioning session in the initialized side positioning session ends, the session identifier corresponding to the second positioning session is generated as the session identifier of the next side positioning session, and the initial node sends a third side positioning protocol message to the third receiving module 1510. The third side positioning protocol includes a session identifier that is released, invalid, or idle in the second positioning session.

[0335] The execution module 1520 is configured to release, invalidate, or idle the session identifier of the second positioning session after the second timer times out.

[0336] The start time of the second timer is determined by the end time of the second positioning session, or the start time or reset time of the second timer is determined based on the reception time of the third sidelink positioning protocol message.

[0337] In an optional example, the session identifier of the second positioning session is related to at least one of the first information and the second information, wherein the first information is the unique identifier of the initial node, and the second information is distinctive information of the initial node when initializing different sideline positioning sessions.

[0338] In some embodiments, a second timer associated with the second positioning session is provided in the device, and the third receiving module 1510 receives a notification message sent by the initial node, the notification message is used to indicate the end of the second positioning session, and the start time of the second timer can be determined based on the end time of the second positioning session; or, the start time or reset time of the second timer is determined based on the reception time of the third side positioning protocol message. The second timer is reset when a message related to the second positioning session is received, and after receiving the notification message or timing out, the receiving node is triggered to regard the session identifier of the second positioning session as invalid or idle. In some embodiments, the timing duration of the timer can be predefined by the communication protocol, preconfigured by the network device, or negotiated between terminal devices. For example, the timer is 0.5ms.

[0339] To sum up, in the device provided in this embodiment, the third receiving module 1510 receives a third side positioning protocol message carrying a session identifier of a second positioning session, and after the second timer times out, releases or invalidates or idles the session identifier of the second positioning session. This method can ensure that the device can promptly know the status of the session identifier release or idleness, thereby improving the efficiency and accuracy of the communication system.

[0340] Please refer to Figure 16, which shows a block diagram of the structure of a terminal device provided in one embodiment of the present application. This terminal device can be used to implement the method for sending and generating a sideline positioning session identifier provided in the above embodiment. The terminal device may include: a processor 1301, a receiver 1302, a transmitter 1303, a memory 1304, and a bus 1305.

[0341] The processor 1301 includes one or more processing cores. The processor 1301 executes various functional applications and information processing by running software programs and modules.

[0342] The receiver 1302 and the transmitter 1303 may be implemented as a transceiver, which may be a communication chip.

[0343] The memory 1304 is connected to the processor 1301 via a bus 1305; in some embodiments, the processor 1301 can be implemented as a first IC chip, and the processor 1301 and the memory 1304 can be jointly implemented as a second IC chip; the first chip or the second chip can be an application specific integrated circuit (ASIC) chip.

[0344] The memory 1304 may be used to store at least one computer program, and the processor 1301 may be used to execute the at least one computer program to implement the various steps performed by the communication system in the above method embodiment.

[0345] In addition, the memory 1304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and the volatile or non-volatile storage device includes but is not limited to: random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other solid-state storage technology, compact disc read-only memory (CD-ROM), high-density digital video disc (DVD) or other optical storage, tape cassettes, magnetic tape, disk storage or other magnetic storage devices.

[0346] In an exemplary embodiment, a chip is further provided. The chip includes a programmable logic circuit and / or program instructions. When the chip runs on a multi-link device, it is used to implement the above-mentioned method for receiving, sending, and generating a session identifier.

[0347] In an exemplary embodiment, a computer-readable storage medium is further provided, wherein a computer program is stored in the computer-readable storage medium. When the computer program is executed by a processor, the computer program implements the above-mentioned method for receiving, sending, and generating a session identifier.

[0348] In an exemplary embodiment, a computer program product is further provided. When the computer program product is executed by a processor, it is used to implement the above-mentioned method for receiving, sending, and generating a session identifier.

[0349] It should be understood that the "multiple" mentioned in this article refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship. In addition, the step numbers described in this article only illustrate a possible execution sequence between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order to the diagram. The embodiments of the present application do not limit this.

[0350] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for receiving a session identifier of a sideline positioning session, characterized in that: The method is performed by a receiving node, and the method includes: receiving a first sideline positioning protocol message, wherein the first sideline positioning protocol message carries a first session identifier; When the first session identifier is the same as any stored session identifier, sending first information, where the first information is used to request or instruct to change the first session identifier; The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

2. The method according to claim 1, characterized in that: The first sideline positioning protocol message carries: Indication information, where the indication information is used to indicate that the first sideline positioning protocol message is the first message or the initial message of the first positioning session.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: A second sideways positioning protocol message is received, where the second sideways positioning protocol message carries a second session identifier, where the second session identifier is a session identifier after the first positioning session is changed.

4. The method according to claim 3, characterized in that The second sideline positioning protocol message carries: Indication information, where the indication information is used to indicate that the second sideline positioning protocol message is the first message or the initial message of the first positioning session.

5. A method for sending a session identifier of a sideline positioning session, characterized in that: The method is performed by an initial node, and comprises: Sending a first sideways positioning protocol message, where the first sideways positioning protocol message carries a first session identifier; receiving first information, where the first information is used to request or instruct to change the first session identifier; The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

6. The method according to claim 5, characterized in that The first information is sent when the first session identifier is the same as any session identifier stored in the receiving node.

7. The method according to claim 5 or 6, characterized in that: The first sideline positioning protocol message carries: Indication information, where the indication information is used to indicate that the first sideline positioning protocol message is the first message or the initial message of the first positioning session.

8. The method according to any one of claims 5 to 7, characterized in that: The method further comprises: Remove the receiving node from the first positioning session; The receiving node is a node that receives the first sideline positioning protocol message, and / or the receiving node is a node that sends the first information.

9. The method according to any one of claims 5 to 7, characterized in that: The method further comprises: A second sideways positioning protocol message is sent, where the second sideways positioning protocol message carries a second session identifier, where the second session identifier is a session identifier after the first positioning session is changed.

10. The method according to claim 9, characterized in that The second sideline positioning protocol message carries: Indication information, where the indication information is used to indicate that the second sideline positioning protocol message is the first message or the initial message of the first positioning session.

11. A method for generating a session identifier for a sideline positioning session, characterized in that: The method is performed by an initial node, and comprises: generating a third session identifier of the sideline positioning session, wherein the third session identifier is related to at least one of the first information and the second information; The first information is a unique identifier of the initial node, and the second information is distinguishing information of the initial node when initializing different sideline positioning sessions.

12. The method according to claim 11, characterized in that The second information is the number of sideline positioning sessions used in the initial node.

13. The method according to claim 11, characterized in that The second information is a timestamp based on absolute time.

14. The method according to any one of claims 12 or 13, characterized in that: The third session identifier is obtained by concatenating the first information and the second information; Alternatively, the third session identifier is obtained by concatenating the first information and the third information, the third information is determined based on the second information and a first value, and the first value is a positive integer.

15. The method according to claim 11, characterized in that The method further comprises: The second information is a maximum value of session identifiers of the sideline positioning sessions used in the initial node.

16. The method according to claim 15, characterized in that The third session identifier is determined based on the maximum value of the session identifiers and a second value, where the second value is a positive integer.

17. The method according to claim 12, characterized in that The method further comprises: When the second positioning session in the initialized lateral positioning session ends, the session identifier of the second positioning session is generated as the session identifier of the next lateral positioning session.

18. The method according to claim 17, characterized in that The step of generating, when the second positioning session in the initialized sideline positioning session ends, the session identifier of the second positioning session as the session identifier of the next sideline positioning session comprises: After the first timer times out, generating the session identifier of the second positioning session as the session identifier of the next sideline positioning session; The start time of the first timer is determined based on the end time of the second positioning session, or the start time or reset time of the first timer is determined based on the sending time of the last message of the second positioning session.

19. The method according to claim 18, characterized in that The timing duration of the first timer is agreed upon by the communication protocol or configured by the network device or pre-configured by the terminal device.

20. The method according to claim 12, characterized in that The method further comprises: When the second positioning session in the used sidewalk positioning session ends, a notification message is sent, where the notification message is used to notify the session release of the second positioning session, or the session identifier of the second positioning session is released, invalidated or idle.

21. The method according to claim 12, characterized in that The method further comprises: After the second information is increased to a maximum value corresponding to N bits, the second information is reset, where N is a positive integer.

22. A method for receiving a session identifier of a sideline positioning session, characterized in that: The method is performed by a receiving node, and the method includes: receiving a third sideline positioning protocol message, wherein the third sideline positioning protocol message carries a session identifier of a second positioning session; After the second timer times out, releasing, invalidating or idling the session identifier of the second positioning session; The start time of the second timer is determined by the end time of the second positioning session, or the start time or reset time of the second timer is determined based on the reception time of the third sideline positioning protocol message.

23. The method according to claim 22, characterized in that The timing duration of the second timer is agreed upon by the communication protocol or configured by the network device or pre-configured by the terminal device.

24. The method according to claim 22, characterized in that The method further comprises: A notification message is received, where the notification message is used to indicate that the second positioning session is ended.

25. The method according to claim 22, characterized in that The session identifier of the second positioning session is related to at least one of the first information and the second information, wherein the first information is a unique identifier of the initial node, and the second information is distinguishing information of the initial node when using different sideline positioning sessions.

26. A session identifier receiving device for a side positioning session, characterized in that: The device comprises: A first receiving module, configured to receive a first sideline positioning protocol message, wherein the first sideline positioning protocol message carries a first session identifier; A first sending module, configured to send first information when the first session identifier collides with any stored session identifier, wherein the first information is used to request or instruct to change the first session identifier; The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

27. A device for sending a session identifier of a side positioning session, characterized in that: The device comprises: A second sending module, configured to send a first sideways positioning protocol message, wherein the first sideways positioning protocol message carries a first session identifier; A second receiving module, used for receiving first information, where the first information is used for requesting or instructing to change the first session identifier; The first session identifier is used to identify the first positioning session to which the first sidelink positioning protocol message belongs.

28. A device for generating a session identifier for a side positioning session, characterized in that: The device comprises: A generating module, configured to generate a third session identifier of the sideline positioning session, wherein the third session identifier is related to at least one of the first information and the second information; The first information is the unique identifier of the initial node, and the second information is the unique information of the initial node.

29. A session identifier receiving device for a side positioning session, characterized in that: The device comprises: A third receiving module is used to receive a third sideline positioning protocol message, where the third sideline positioning protocol message carries a session identifier of a second positioning session; An execution module, configured to release, invalidate or idle the session identifier of the second positioning session after the second timer times out; The start time of the second timer is determined by the end time of the second positioning session, or the start time or reset time of the second timer is determined based on the reception time of the third sideline positioning protocol message.

30. A computer-readable storage medium, characterized in that: The readable storage medium stores executable instructions, which are loaded and executed by a processor to implement the method for receiving a session identifier for a side positioning session as described in any one of claims 1 to 4, or the method for sending a session identifier for a side positioning session as described in any one of claims 5 to 10, or the method for generating a session identifier for a side positioning session as described in any one of claims 11 to 21, or the method for receiving a session identifier for a side positioning session as described in any one of claims 22 to 25.

31. A chip, characterized in that: The chip includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the session identifier receiving method for the side positioning session described in any one of claims 1 to 4, or the session identifier sending method for the side positioning session described in any one of claims 5 to 10, or the session identifier generating method for the side positioning session described in any one of claims 11 to 21, or the session identifier receiving method for the side positioning session described in any one of claims 22 to 25.

32. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. The processor reads and executes the computer instructions from the computer-readable storage medium to implement the method for receiving a session identifier for a side positioning session as described in any one of claims 1 to 4, or the method for sending a session identifier for a side positioning session as described in any one of claims 5 to 10, or the method for generating a session identifier for a side positioning session as described in any one of claims 11 to 21, or the method for receiving a session identifier for a side positioning session as described in any one of claims 22 to 25.

33. A computer program, characterized in that The computer program includes computer instructions, and the processor of the computer device executes the computer instructions, so that the computer device executes the method for receiving a session identifier for a side positioning session as described in any one of claims 1 to 4, or the method for sending a session identifier for a side positioning session as described in any one of claims 5 to 10, or the method for generating a session identifier for a side positioning session as described in any one of claims 11 to 21, or the method for receiving a session identifier for a side positioning session as described in any one of claims 22 to 25.

Images