Message transmission method and apparatus, and storage medium

Abstract

The present disclosure provides a message transmission method and apparatus, and a storage medium. The method comprises: sending a first sidelink positioning protocol (SLPP) message to a forwarding terminal, the first SLPP message comprising at least one of the following: one or two transaction identifier fields; and a session identifier field. According to the present disclosure, when an SLPP message is forwarded, an SLPP transaction and / or an SLPP session is clarified, thereby improving the reliability of SL positioning, and achieving high availability.

Description

Message transmission method and device, and storage medium Technical Field

[0001] The present disclosure relates to the field of communications, and in particular to a message transmission method and device, and a storage medium. Background Art

[0002] Positioning based on the sidelink (SL) between terminals includes absolute positioning, relative positioning, and ranging.

[0003] Summary of the Invention

[0004] In order to improve the reliability of SL positioning, the embodiments of the present disclosure provide a message transmission method and device, and a storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a message transmission method is provided, the method being performed by a first node and including:

[0006] Send a first Sidelink Positioning Protocol (SLPP) message to the forwarding terminal, where the first SLPP message includes at least one of the following:

[0007] One or two transaction identification fields;

[0008] A session identification field.

[0009] According to a second aspect of an embodiment of the present disclosure, a message transmission method is provided, the method being executed by a forwarding terminal, including:

[0010] Receive a first Sidelink Positioning Protocol (SLPP) message sent by the first node, where the first SLPP message includes at least one of the following:

[0011] One or two transaction identification fields;

[0012] A session identification field;

[0013] Based on the first SLPP message, a second SLPP message is sent to the second node, where the second SLPP message includes at least one of the following:

[0014] One or two transaction identification fields;

[0015] A session identification field.

[0016] According to a third aspect of an embodiment of the present disclosure, a message transmission method is provided, the method being performed by a second node and including:

[0017] Receive a second Sidelink Positioning Protocol (SLPP) message sent by the forwarding terminal, where the second SLPP message includes at least one of the following:

[0018] One or two transaction identification fields;

[0019] A session identification field.

[0020] According to a fourth aspect of an embodiment of the present disclosure, there is provided a first node, including:

[0021] The transceiver module is configured to send a first Sidelink Positioning Protocol (SLPP) message to the forwarding terminal, where the first SLPP message includes at least one of the following:

[0022] One or two transaction identification fields;

[0023] A session identification field.

[0024] According to a fifth aspect of an embodiment of the present disclosure, a forwarding terminal is provided, including:

[0025] The transceiver module is configured to receive a first Sidelink Positioning Protocol (SLPP) message sent by the first node, where the first SLPP message includes at least one of the following:

[0026] One or two transaction identification fields;

[0027] A session identification field;

[0028] The transceiver module is further configured to send a second SLPP message to the second node based on the first SLPP message, where the second SLPP message includes at least one of the following:

[0029] One or two transaction identification fields;

[0030] A session identification field.

[0031] According to a sixth aspect of an embodiment of the present disclosure, a second node is provided, including:

[0032] The transceiver module is configured to receive a second Sidelink Positioning Protocol (SLPP) message sent by the forwarding terminal, where the second SLPP message includes at least one of the following:

[0033] One or two transaction identification fields;

[0034] A session identification field.

[0035] According to a seventh aspect of an embodiment of the present disclosure, there is provided a first node, including:

[0036] one or more processors;

[0037] The processor is used to execute any message transmission method of the first aspect.

[0038] According to an eighth aspect of an embodiment of the present disclosure, a forwarding terminal is provided, including:

[0039] one or more processors;

[0040] The processor is used to execute any message transmission method of the second aspect.

[0041] According to a ninth aspect of an embodiment of the present disclosure, a second node is provided, including:

[0042] one or more processors;

[0043] The processor is used to execute any message transmission method of the third aspect.

[0044] According to a tenth aspect of an embodiment of the present disclosure, there is provided a communication system, including:

[0045] A first node, the first node being configured to implement the message transmission method according to any one of the first aspects;

[0046] The forwarding terminal is configured to implement the message transmission method of any one of the second aspects

[0047] The second node is configured to implement the message transmission method of any one of the third aspects.

[0048] According to an eleventh aspect of an embodiment of the present disclosure, a storage medium is provided, which stores instructions. When the instructions are executed on a communication device, the communication device executes a message transmission method as described in any one of the first, second or third aspects.

[0049] According to a twelfth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising a computer program, which, when executed by a processor, is used to implement the message transmission method of any one of the first aspect, the second aspect or the third aspect.

[0050] In an embodiment of the present disclosure, a first node may send a first SLPP message to a forwarding terminal, including one or two transaction identification fields and / or a session identification field. Based on the first SLPP message, the forwarding terminal may send a second SLPP message to a second node, also including one or two transaction identification fields and / or a session identification field. When forwarding an SLPP message, the SLPP transaction and / or SLPP session is clearly identified, thereby improving the reliability of SL positioning and enhancing availability.

[0051] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0053] FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0054] FIG1B is a schematic diagram of an exemplary scenario of a DL-TDOA positioning process provided according to an embodiment of the present disclosure.

[0055] FIG1C is an exemplary schematic diagram of an SLPP message forwarding scenario between an LMF and a terminal according to an embodiment of the present disclosure.

[0056] FIG1D is an exemplary schematic diagram of an SLPP message forwarding scenario between a server terminal and a terminal according to an embodiment of the present disclosure.

[0057] FIG2A is an exemplary interaction diagram of a message transmission method provided according to an embodiment of the present disclosure.

[0058] FIG2B is an exemplary interaction diagram of a message transmission method provided according to an embodiment of the present disclosure.

[0059] FIG3A is an exemplary interaction diagram of a message transmission method provided according to an embodiment of the present disclosure.

[0060] FIG3B is an exemplary interaction diagram of a message transmission method provided according to an embodiment of the present disclosure.

[0061] FIG3C is an exemplary interaction diagram of a message transmission method provided according to an embodiment of the present disclosure.

[0062] FIG4A is an exemplary block diagram of a first node provided according to an embodiment of the present disclosure.

[0063] FIG4B is an exemplary block diagram of a forwarding terminal provided according to an embodiment of the present disclosure.

[0064] FIG4C is an exemplary block diagram of a second node provided according to an embodiment of the present disclosure.

[0065] FIG5A is a schematic diagram of an exemplary interaction of a communication device according to an embodiment of the present disclosure.

[0066] FIG5B is an exemplary interaction diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0067] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent like or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.

[0068] The embodiments of the present disclosure provide a message transmission method, device, and storage medium.

[0069] In a first aspect, an embodiment of the present disclosure provides a message transmission method, which is executed by a first node and includes:

[0070] Send a first Sidelink Positioning Protocol (SLPP) message to the forwarding terminal, where the first SLPP message includes at least one of the following:

[0071] One or two transaction identification fields;

[0072] A session identification field.

[0073] In the above embodiment, the first node can send a first SLPP message to the forwarding terminal, which may include one or two transaction identification fields and / or a session identification field, so that in the SLPP message forwarding scenario, the second node can clearly identify the SLPP transaction and / or SLPP session, thereby improving the reliability of SL positioning and high availability.

[0074] In conjunction with some embodiments of the first aspect, in some embodiments, when the first SLPP message includes two transaction identification fields, the two transaction identification fields are used to identify:

[0075] a first transaction, where the first transaction is an SLPP transaction between the first node and the second node; and

[0076] The second transaction is an SLPP transaction between the forwarding terminal and the target terminal, and the target terminal is one of the first node and the second node.

[0077] In the above embodiment, the two transaction identification fields in the first SLPP message can be used to identify the first transaction and the second transaction respectively, clearly distinguishing different SLPP transactions, and having high availability.

[0078] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0079] Based on the first transaction identifier, a first transaction identifier field of the two transaction identifier fields is set.

[0080] In the above embodiment, the first node may set the first transaction identifier field of the two transaction identifier fields based on the first transaction identifier, so that the first transaction identifier field clearly indicates the first transaction, thereby improving the reliability of SLPP message transmission.

[0081] In conjunction with some embodiments of the first aspect, in some embodiments, the first node is a core network function node or a server terminal, and the method further includes any one of the following:

[0082] Setting the second transaction identification field of the two transaction identification fields to the first value;

[0083] The second transaction identification field of the two transaction identification fields is not set.

[0084] In the above embodiment, when the first node is a core network function node or a server terminal, since the second transaction identifier cannot be determined, the first node may set the second transaction identifier field to the first value. Alternatively, the second transaction identifier field may not be set. The forwarding terminal subsequently sets the second transaction identifier field, thereby improving the efficiency of SLPP message transmission.

[0085] In conjunction with some embodiments of the first aspect, in some embodiments, the first node is a target terminal, and the method further includes:

[0086] Based on the second transaction identifier, the second transaction identifier field of the two transaction identifier fields is set.

[0087] In the above embodiment, when the first node is the target node, the second transaction identifier field of the two transaction identifier fields can be directly set based on the second transaction identifier. The forwarding terminal does not need to set the second transaction identifier field, thereby improving the efficiency of forwarding SLPP messages.

[0088] In combination with some embodiments of the first aspect, in some embodiments, when the first SLPP message includes a transaction identification field, the transaction identification field is used to identify the first transaction, and the first transaction is an SLPP transaction between the first node and the second node.

[0089] In the above embodiment, the first SLPP message may include only one transaction identification field. In this case, the transaction identification field is used to identify the first transaction, which is an SLPP transaction between the first node and the second node. Reducing the number of transaction identification fields in the SLPP message saves signaling resources.

[0090] In combination with some embodiments of the first aspect, in some embodiments, the first node is a target terminal, the first transaction identifier is not occupied by an existing first transaction and is not occupied by an existing second transaction, and the second transaction is an SLPP transaction between the target terminal and the forwarding terminal.

[0091] In the above embodiment, when the target terminal serves as the first node, the first transaction identifier can be configured and the uniqueness of the first transaction identifier can be ensured, thereby improving the SLPP message transmission efficiency and increasing the availability.

[0092] In conjunction with some embodiments of the first aspect, in some embodiments, the first node is a core network function node, and the method further includes:

[0093] The session identification field is set to the second value.

[0094] In the above embodiment, when the core network function node serves as the first node, since other identifiers can be used to distinguish parallel sessions between the core network function node and the terminal, the session identifier field in the first SLPP message can be set to the second value, which is simple to implement and has high availability.

[0095] In conjunction with some embodiments of the first aspect, in some embodiments, the first node is a target terminal or a server terminal, and the method further includes:

[0096] Based on the session identifier, the session identifier field is set, and the session is an SLPP session between terminals associated with the positioning service.

[0097] In the above embodiment, when the first node is a target terminal or a server terminal, it can set a session identifier field based on the session identifier. The session is an SLPP session between terminals associated with the positioning service, which is simple to implement and has high availability.

[0098] In a second aspect, an embodiment of the present disclosure provides a message transmission method, which is executed by a forwarding terminal and includes:

[0099] Receive a first Sidelink Positioning Protocol (SLPP) message sent by the first node, where the first SLPP message includes at least one of the following:

[0100] One or two transaction identification fields;

[0101] A session identification field;

[0102] Based on the first SLPP message, a second SLPP message is sent to the second node, where the second SLPP message includes at least one of the following:

[0103] One or two transaction identification fields;

[0104] A session identification field.

[0105] In the above embodiment, the forwarding terminal may send a second SLPP message to the second node after receiving the first SLPP message, which may include one or two transaction identification fields and / or a session identification field, so that in the SLPP message forwarding scenario, the second node can clearly understand the SLPP transaction and / or SLPP session, thereby improving the reliability of SL positioning and high availability.

[0106] In combination with some embodiments of the second aspect, in some embodiments, when the first SLPP message includes two transaction identification fields, the second SLPP message includes two transaction identification fields.

[0107] In the above embodiment, both the first SLPP message and the second SLPP message may include two transaction identification fields, so that in the SLPP message forwarding scenario, the second node can clearly identify the SLPP transaction and / or SLPP session, thereby improving the reliability of SL positioning and high availability.

[0108] In conjunction with some embodiments of the second aspect, in some embodiments, the two transaction identification fields are respectively used to identify:

[0109] A first transaction, where the first transaction is an SLPP transaction between the first node and the second node;

[0110] The second transaction is an SLPP transaction between the forwarding terminal and the target terminal, and the target terminal is one of the first node and the second node.

[0111] In conjunction with some embodiments of the second aspect, in some embodiments, the first node is a core network function node or a server terminal, and the method further includes:

[0112] Based on the second transaction identifier, the second transaction identifier field included in the first SLPP message is set to obtain a second SLPP message.

[0113] In the above embodiment, the second transaction field in the first SLPP message is set to the first value by the first node or is not set by the first node. At this time, the forwarding terminal can set the second transaction identifier field included in the first SLPP message based on the second transaction identifier to obtain the second SLPP message, thereby ensuring the reliability of the second SLPP message.

[0114] In combination with some embodiments of the second aspect, in some embodiments, when the first SLPP message includes one transaction identification field, the second SLPP message includes two transaction identification fields.

[0115] In the above embodiment, when the first SLPP message carries only one transaction identification field, the forwarding terminal can add a second transaction identification field thereto, so that the second SLPP message includes two transaction identification fields. In the SLPP message forwarding scenario, the second node is allowed to clearly identify the SLPP transaction and / or SLPP session, thereby improving the reliability of SL positioning and enhancing availability.

[0116] In conjunction with some embodiments of the second aspect, in some embodiments, the transaction identification field in the first SLPP message is used to identify the first transaction, where the first transaction is an SLPP transaction between the first node and the second node;

[0117] The two transaction identification fields included in the second SLPP message are used to identify:

[0118] First Affairs;

[0119] The second transaction is a second SLPP transaction between the forwarding terminal and the target terminal, and the target terminal is one of the first node and the second node.

[0120] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0121] A second transaction identifier field is added to the first SLPP message to obtain a second SLPP message.

[0122] In combination with some embodiments of the second aspect, in some embodiments, when the first SLPP message includes a transaction identification field, the second SLPP message includes a transaction identification field.

[0123] In the above embodiment, the first SLPP message and the second SLPP message may include only one transaction identifier field, thereby saving signaling resources of the SLPP messages.

[0124] In conjunction with some embodiments of the second aspect, in some embodiments, the transaction identification field in the first SLPP message is used to identify the first transaction, where the first transaction is an SLPP transaction between the first node and the second node;

[0125] The transaction identification field in the second SLPP message is used to identify a second transaction. The second transaction is an SLPP transaction between the forwarding terminal and the target terminal. The target terminal is one of the first node and the second node.

[0126] In the above embodiment, the transaction identification field in the second SLPP message sent by the forwarding terminal to the second node can be used to identify the second transaction, allowing the second node to clearly identify the SLPP transaction and / or SLPP session, thereby improving the reliability of SL positioning and high availability.

[0127] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0128] Maintaining a mapping relationship between the first transaction identifier and the second transaction identifier, and determining the second transaction identifier based on the mapping relationship;

[0129] Based on the determined second transaction identifier, the transaction identifier field in the first SLPP message is reset to obtain a second SLPP message.

[0130] In the above embodiment, if the forwarding terminal maintains the above mapping relationship, it can directly determine the second transaction identifier based on the mapping relationship and then reset the transaction identifier field in the first SLPP message to obtain the second SLPP message. This is simple to implement and has high availability.

[0131] In conjunction with some embodiments of the second aspect, in some embodiments, the first node is a core network function node or a server terminal, and the method further includes:

[0132] The mapping relationship between the first transaction identifier and the second transaction identifier is not maintained, and the second transaction identifier is created;

[0133] Create a mapping relationship;

[0134] Based on the created second transaction identifier, the transaction identifier field in the first SLPP message is reset to obtain a second SLPP message.

[0135] In the above embodiment, if the forwarding terminal does not maintain the above mapping relationship, a second transaction identifier and mapping relationship can be created, and the transaction identifier field in the first SLPP message can be reset to obtain the second SLPP message. This is simple to implement and has high availability.

[0136] In conjunction with some embodiments of the second aspect, in some embodiments, the first node is a target terminal, the first transaction identifier is not occupied by an existing first transaction and is not occupied by an existing second transaction, and the second transaction is an SLPP transaction between the target terminal and the forwarding terminal;

[0137] Sending a second SLPP message to the second node based on the first SLPP message includes:

[0138] A first SLPP message is sent to the second node.

[0139] In the above embodiment, when the target terminal determines the first transaction identifier and ensures its uniqueness, the forwarding terminal may directly forward the first SLPP message to the second node, thereby improving the efficiency of forwarding the SLPP message.

[0140] In conjunction with some embodiments of the second aspect, in some embodiments, the first node is a core network function node, and the method further includes:

[0141] Based on the session identifier, the session identifier field in the second SLPP message is set, where the session is an SLPP session between terminals associated with the positioning service.

[0142] In the above embodiment, if the first node is a core network function node, the forwarding terminal can set the session identifier field in the second SLPP message based on the session identifier, and the session is an SLPP session between terminals associated with the positioning service, to ensure the reliability of the second SLPP message.

[0143] In a third aspect, an embodiment of the present disclosure provides a message transmission method, which is executed by a second node and includes:

[0144] Receive a second Sidelink Positioning Protocol (SLPP) message sent by the forwarding terminal, where the second SLPP message includes at least one of the following:

[0145] One or two transaction identification fields;

[0146] A session identification field.

[0147] In the above embodiment, the second node can receive a second SLPP message sent by the forwarding terminal, which may include one or two transaction identification fields and / or a session identification field, so that in the SLPP message forwarding scenario, the second node can clearly identify the SLPP transaction and / or SLPP session, thereby improving the reliability of SL positioning and high availability.

[0148] In conjunction with some embodiments of the third aspect, in some embodiments, the second SLPP message includes two transaction identification fields, which are respectively used to identify:

[0149] A first transaction, where the first transaction is an SLPP transaction between the first node and the second node;

[0150] The second transaction is an SLPP transaction between the forwarding terminal and the target terminal, and the target terminal is one of the first node and the second node.

[0151] In combination with some embodiments of the third aspect, in some embodiments, the second SLPP message includes a transaction identification field, and the transaction identification field in the second SLPP message is used to identify the second transaction. The second transaction is an SLPP transaction between the forwarding terminal and the target terminal, and the target terminal is one of the first node and the second node.

[0152] In a fourth aspect, an embodiment of the present disclosure provides a first node, including:

[0153] The transceiver module is configured to send a first Sidelink Positioning Protocol (SLPP) message to the forwarding terminal, where the first SLPP message includes at least one of the following:

[0154] One or two transaction identification fields;

[0155] A session identification field.

[0156] In a fifth aspect, an embodiment of the present disclosure provides a forwarding terminal, including:

[0157] The transceiver module is configured to receive a first Sidelink Positioning Protocol (SLPP) message sent by the first node, where the first SLPP message includes at least one of the following:

[0158] One or two transaction identification fields;

[0159] A session identification field;

[0160] The transceiver module is further configured to send a second SLPP message to the second node based on the first SLPP message, where the second SLPP message includes at least one of the following:

[0161] One or two transaction identification fields;

[0162] A session identification field.

[0163] In a sixth aspect, an embodiment of the present disclosure provides a second node, including:

[0164] The transceiver module is configured to receive a second Sidelink Positioning Protocol (SLPP) message sent by the forwarding terminal, where the second SLPP message includes at least one of the following:

[0165] One or two transaction identification fields;

[0166] A session identification field.

[0167] In a seventh aspect, an embodiment of the present disclosure provides a first node, including:

[0168] one or more processors;

[0169] The processor is used to execute any message transmission method of the first aspect.

[0170] In an eighth aspect, an embodiment of the present disclosure provides a forwarding terminal, including:

[0171] one or more processors;

[0172] The processor is used to execute any message transmission method of the second aspect.

[0173] In a ninth aspect, an embodiment of the present disclosure provides a second node, including:

[0174] one or more processors;

[0175] The processor is used to execute any message transmission method of the third aspect.

[0176] In a tenth aspect, an embodiment of the present disclosure provides a communication system, including:

[0177] A first node, the first node being configured to implement the message transmission method according to any one of the first aspects;

[0178] The forwarding terminal is configured to implement the message transmission method of any one of the second aspects

[0179] The second node is configured to implement the message transmission method of any one of the third aspects.

[0180] In the eleventh aspect, an embodiment of the present disclosure proposes a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes a message transmission method as described in any one of the first aspect, the second aspect, or the third aspect.

[0181] In a twelfth aspect, an embodiment of the present disclosure proposes a computer program product, comprising a computer program, which, when executed by a processor, is used to implement the message transmission method of any one of the first aspect, the second aspect, or the third aspect.

[0182] It is understandable that the first node, forwarding terminal, second node, storage medium, and computer program are all used to execute the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0183] The embodiments of the present disclosure provide a message transmission method, device, and storage medium. In some embodiments, the terms "message transmission method" and "message sending method," "message forwarding method," and "communication method" are interchangeable; the terms "message transmission device" and "message sending device," "message forwarding device," and "communication device" are interchangeable; and the terms "message transmission system," "message sending system," "message forwarding system," and "communication system" are interchangeable.

[0184] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

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

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

[0187] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when articles such as "a", "an", "the" in English are used in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0188] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0189] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0190] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0191] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0192] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0193] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0194] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "entity", "subject", etc.

[0195] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0196] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0197] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0198] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0199] As shown in FIG1A , a communication system 100 includes a first node 101 , a forwarding terminal 102 , and a second node 103 .

[0200] In some embodiments, the first node 101 may be a node or device that initiates a Sidelink Positioning Protocol (SLPP) message.

[0201] In one example, the first node 101 may be a core network function node. A core network function node may be a device including one or more network elements, or may be multiple devices or a group of devices. A network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0202] In the embodiment of the present disclosure, the core network function node may be a location management function (LMF) node.

[0203] In an example, the first node 101 may be a server terminal, and the server terminal may be a terminal device that supports providing server functions.

[0204] In one example, the first node 101 can be a target terminal, where the target terminal refers to the object to which the SLPP message from the core network function node (e.g., LMF) or the server terminal needs to be forwarded, or the SLPP message from the target terminal needs to be sent to the core network function node (e.g., LMF) or the server terminal through the forwarding terminal.

[0205] In some embodiments, the forwarding terminal 102 can be located between the first node 101 and the second node 102, and is used to forward SLPP messages. The terminal device includes, for example, a mobile phone, a wearable device, a road side unit (RSU), an Internet of Things device, a car with communication functions, a smart car, 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 a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0206] In some embodiments, the second node 103 may be a destination device of the SLPP message.

[0207] In one example, when the first node 101 is a core network function node (eg, LMF) or a server terminal, the second node 103 may be a destination terminal.

[0208] In one example, when the first node 101 is a destination terminal, the second node 103 may be a core network function node (eg, LMF) or a server terminal.

[0209] In some embodiments, when the second node 103 is a server terminal or a target terminal, it may include at least one of a mobile phone, a wearable device, an RSU, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, 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 a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home, but is not limited thereto.

[0210] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0211] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0212] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, systems utilizing other communication methods, and next-generation systems based on these. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be used.

[0213] In the embodiment of the present disclosure, taking the downlink time difference of arrival (DL-TDOA) positioning method as an example, as shown in Figure 1B, the terminal can measure the positioning signals sent by multiple road side units (RSUs) through the side link, thereby determining the position of the terminal relative to the RSU.

[0214] In addition to the above-mentioned DL-TDOA, positioning methods can also include but are not limited to uplink time difference of arrival (UL-TDOA), multiple round-trip time (RTT), angle of arrival (AOA) / angle of departure (AOD), carrier phase positioning, etc.

[0215] It should be noted that if the final positioning result does not convert the absolute position information of the terminal based on the Global Positioning System (GPS) of the RSU into absolute position coordinates, the positioning result is a relative positioning result; otherwise, the positioning result is an absolute positioning result.

[0216] The terminal being located may be referred to as a target terminal (target User Equipment, target UE), and other terminals that support positioning the target UE may be referred to as anchor terminals (anchor User Equipment, anchor UE).

[0217] If positioning involves only two terminals, the two terminals serve as anchor terminals for each other.

[0218] There are different types of anchor UEs. For example, the RSU type anchor UE is an infrastructure that can provide positioning services by collaborating with other RSUs. For example, an ordinary terminal can also serve as an anchor UE, but it is difficult for it to assist in providing positioning services with other terminals. In addition, some anchor UEs have location information such as GPS, which can assist other terminals in absolute positioning. Other anchor UEs may not have location information such as GPS.

[0219] The protocol for exchanging sidelink positioning messages between the two terminals is SLPP and / or Ranging and Sidelink Positioning Protocol Transport QoS (RSPP transport QoS).

[0220] In some embodiments, the SLPP message forwarding process is shown in FIG1C , for example. Here, the LMF can serve as the first node 101, and accordingly, terminal #2 can serve as the second node 103. Alternatively, terminal #2 can serve as the first node 101, and accordingly, the LMF can serve as the second node 103. Terminal #1 always serves as the forwarding terminal.

[0221] For an SLPP message sent from the LMF to Terminal #2, the LMF first places the SLPP message as the payload in a supplementary RSPP message between the LMF and Terminal #1 and sends it to Terminal #1. Terminal #1 then extracts the SLPP message from the supplementary RSPP message and sends it to Terminal #2. Conversely, for an SLPP message sent from Terminal #2 to the LMF, Terminal #2 first sends the SLPP message to Terminal #1. Terminal #1 then places the SLPP message as the payload in a supplementary RSPP message between the LMF and Terminal #1 and sends it to the LMF.

[0222] The SLPP forwarding between the server terminal and terminal #2 is shown in FIG1D . The forwarding process is similar to the forwarding between the LMF and terminal #2 in FIG1C , and will not be described in detail.

[0223] If the LMF and the terminal exchange SLPP messages directly, that is, if there is no need for another terminal to forward, the SLPP message does not need to carry a session identifier (Session ID). The routing ID (or correlation ID) in the non-access stratum (NAS) message that encapsulates the SLPP message can be used to distinguish the parallel sessions between the LMF and the terminal. However, for the forwarding scenario, taking the SLPP message sent by the LMF to terminal #2 as an example, the forwarded SLPP message from the LMF to terminal #1 is piggybacked as a payload in the supplementary RSPP message, and the SLPP message is directly transmitted from terminal #1 to terminal #2. This process may involve the following situations:

[0224] Case 1: About Session ID.

[0225] The SLPP messages exchanged between the LMF and Terminal #2 do not need to carry a session ID, so the LMF does not allocate a session ID for SLPP message exchanges with Terminal #2. Therefore, the SLPP messages sent by the LMF to Terminal #2 do not contain a session ID. However, when Terminal #1 forwards the received SLPP packets to Terminal #2, since Terminal #1 and Terminal #2 exchange SLPP messages directly, the SLPP messages must carry a session ID so that Terminal #1 and Terminal #2 can distinguish their parallel sessions.

[0226] Case 2: Regarding transaction ID.

[0227] SLPP messages exchanged between LMF and Terminal #2 must carry a transaction ID to distinguish between transactions within the same session. SLPP messages between Terminal #1 and Terminal #2 also need to distinguish between transactions within the same session, and SLPP messages must also carry a transaction ID. However, the transaction ID used in SLPP messages between LMF and Terminal #2 is different from the transaction ID used between Terminal #1 and Terminal #2. When Terminal #1 forwards a received SLPP packet to Terminal #2, it cannot forward the packet intact.

[0228] In the SLPP forwarding scenario between the server and terminal #2, Case 1 does not exist. This is because the SLPP interaction between the server and terminal #2 also requires a session ID. Therefore, when forwarding the SLPP message, terminal #1 can directly use the session ID in the message without modifying it. However, Case 2 mentioned above does exist in this scenario.

[0229] In order to clarify SLPP transactions and / or SLPP sessions when forwarding SLPP messages and improve the reliability of SL positioning, the present disclosure provides a message transmission method, apparatus, and storage medium.

[0230] FIG2A is an interactive diagram of a message transmission method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to a message transmission method, which includes:

[0231] Step S2101 : The first node 101 (core network function node or server terminal) sends a first SLPP message to the forwarding terminal 102 .

[0232] In some embodiments, the first node 101 is a core network function node such as a LMF or a server terminal. In this case, the first node 101 may place the first SLPP message as a payload in a supplementary RSPP message and send it to the forwarding terminal 102 .

[0233] In some embodiments, the first SLPP message may include but is not limited to at least one of the following:

[0234] One or two transaction identification fields;

[0235] A session identification field.

[0236] In some embodiments, if the first SLPP message includes two transaction identification fields, the two transaction identification fields may be a first transaction identification field and a second transaction identification field, respectively used to identify the first transaction and the second transaction. The first transaction may be an SLPP transaction between the first node 101 and the second node 103. In the embodiments of the present disclosure, the first transaction is an SLPP transaction between an LMF or a server terminal and a target terminal. The second transaction may be an SLPP transaction between a forwarding terminal and a target terminal, wherein the target terminal is the second node 103. That is, in the embodiments of the present disclosure, the second transaction is an SLPP transaction between the forwarding terminal 102 and the second node 103.

[0237] In some embodiments, the first node 101 may set the first transaction identifier field of the two transaction identifier fields for identifying the first transaction based on the first transaction identifier. For example, the bit value of the first transaction identifier field may be set equal to the first transaction identifier. Assuming that the first transaction identifier is 2 and the first transaction identifier field occupies 3 bits, the bit value of the first transaction identifier field may be set to 010.

[0238] The above is merely an exemplary description, and the present disclosure does not limit the number of bits occupied by the first transaction identifier field. For example, the number of bits occupied by the first transaction identifier field may be determined based on the maximum value of the first transaction identifier, or based on the maximum number of bits allowed for the transaction identifier field in the SLPP message.

[0239] In some embodiments, if the first node 101 is an LMF or a server terminal, it cannot determine the second transaction identifier and therefore cannot set the second transaction identifier field in the two transaction identifier fields based on the second transaction identifier. Therefore, the first node 101 may set the second transaction identifier field to a first value, where the first value may be any value or a specific value agreed upon by the protocol, such as directly setting it to 0 or 1.

[0240] In some embodiments, if first node 101 is an LMF or server terminal, it cannot determine the second transaction identifier and cannot set the second transaction identifier field of the two transaction identifier fields based on the second transaction identifier. Therefore, first node 101 may not set the second transaction identifier field. For example, the second transaction identifier field may be left blank, and forwarding terminal 102 may set the second transaction identifier field.

[0241] In some embodiments, if the first SLPP message includes only one transaction identification field, the transaction identification field can be used to identify the first transaction, where the first transaction is an SLPP transaction between the first node 101 and the second node 103. That is, the first transaction is an SLPP transaction between a core network function node or a server terminal and a target terminal.

[0242] It can be understood that the first node 101 does not carry the second transaction identification field in the first SLPP message, but only carries the first transaction identification field.

[0243] The first node 101 may set the first transaction identifier field in the two transaction identifier fields for identifying the first transaction based on the first transaction identifier. The specific process will not be described in detail.

[0244] In some embodiments, the first SLPP message may include a session identifier field. When the first node 101 is a core network function node, considering that parallel sessions between the core network function node, such as the LMF, and the second node 103 can be distinguished by a routing identifier (or an association identifier), the first node 101 may set the session identifier field to a second value. The second value may be set based on the implementation of the core network function node, or may be set to a protocol agreed value, which is not limited in this disclosure.

[0245] In some embodiments, the first SLPP message may include a session identifier field. When the first node 101 is a server terminal, the first node 101 may set a bit value of the session identifier field based on the session identifier. The session is an SLPP session between terminals associated with the positioning service.

[0246] In some embodiments, the first SLPP message may include a transaction identification field and a session identification field, or may include two transaction identification fields and a session identification field, which is not limited in this disclosure. The specific field setting method has been introduced in the previous embodiment and will not be repeated here.

[0247] Step S2102 : The forwarding terminal 102 sends a second SLPP message to the second node 103 (target terminal).

[0248] In some embodiments, the second node 103 is a target terminal.

[0249] In some embodiments, the second SLPP message includes at least one of the following:

[0250] One or two transaction identification fields;

[0251] A session identification field.

[0252] It should be noted that the number of transaction identification fields included in the second SLPP message may be greater than or equal to the number of transaction identification fields included in the first SLPP message.

[0253] In some embodiments, the first SLPP message includes two transaction identification fields, and the second SLPP message also includes two transaction identification fields, where the two transaction identification fields are used to identify the first transaction and the second transaction, respectively.

[0254] In some embodiments, if the first node 101 sets the second transaction identifier field in the first SLPP message to the first value or does not set the second transaction identifier field, then the forwarding terminal 102, after extracting the first SLPP message from the supplementary RSPP message, may set the second transaction identifier field included in the first SLPP message based on the second transaction identifier, thereby obtaining the second SLPP message. For example, the bit value of the second transaction identifier field may be set equal to the second transaction identifier. Assuming the first transaction identifier is 3 and the second transaction identifier field occupies 3 bits, the bit value of the second transaction identifier field may be set to 011.

[0255] The above is merely an exemplary description, and the present disclosure does not limit the number of bits occupied by the second transaction identifier field. For example, the number of bits occupied by the second transaction identifier field may be determined based on the maximum value of the second transaction identifier, or based on the maximum number of bits allowed for the transaction identifier field in the SLPP message.

[0256] In some embodiments, the first SLPP message includes a transaction identification field, and the transaction identification field is used to identify the first transaction. The second SLPP message includes two transaction identification fields, and the two transaction identification fields are used to identify the first transaction and the second transaction respectively.

[0257] After extracting the first SLPP message from the supplementary RSPP message, the forwarding terminal 102 may add a second transaction identifier field to the first SLPP message and set a bit value of the second transaction identifier field based on the second transaction identifier, thereby obtaining a second SLPP message.

[0258] In some embodiments, the first SLPP message includes a transaction identification field, and the transaction identification field is used to identify the first transaction. The second SLPP message also includes a transaction identification field, and the transaction identification field in the second SLPP message is used to identify the second transaction.

[0259] After extracting the first SLPP message from the supplementary RSPP message, the forwarding terminal 102 may reset the bit value of the transaction identification field so that the field is used to identify the second transaction.

[0260] In one example, if the forwarding terminal 102 maintains a mapping relationship between the first transaction identifier and the second transaction identifier, the forwarding terminal 102 can determine the second transaction identifier mapped to the first transaction identifier in the first SLPP message based on the mapping relationship, and reset the transaction identifier field in the first SLPP message based on the determined second transaction identifier to obtain the second SLPP message.

[0261] In one example, if the forwarding terminal 102 does not maintain a mapping relationship between the first transaction identifier and the second transaction identifier, the forwarding terminal 102 may create a second transaction identifier. The second transaction identifier created by the forwarding terminal 102 should not conflict with the transaction identifier used between the forwarding terminal 102 and the second node 103 (i.e., the destination terminal). Furthermore, the forwarding terminal 102 may create the mapping relationship, for example, the mapping relationship between the first transaction identifier and the second transaction identifier. Based on the created second transaction identifier, the forwarding terminal 102 may reset the transaction identifier field in the first SLPP message to obtain a second SLPP message.

[0262] In some embodiments, the first SLPP message includes a session identification field.

[0263] In some embodiments, the first node 101 is a core network function node, which sets the session identifier field to the second value. The forwarding terminal 102 may ignore the session identifier field in the first SLPP message. Exemplarily, the forwarding terminal 102 may set the bit value of the session identifier field in the second SLPP message based on the session identifier, where the session is an inter-terminal SLPP session associated with the positioning service.

[0264] In some embodiments, the second SLPP message may include a transaction identification field and a session identification field, or may include two transaction identification fields and one session identification field. The specific setting method will not be repeated here.

[0265] In some embodiments, the forwarding terminal 102 sends a second SLPP message to the second node 103 , and the second node 103 receives the second SLPP message.

[0266] In some embodiments, the second node 103 determines a corresponding transaction identifier and / or session identifier based on the second SLPP message.

[0267] Exemplarily, the second SLPP message includes two transaction identification fields, and the second node 103 directly determines the second transaction based on the second transaction identification field, wherein the second transaction is an SLPP transaction between the forwarding terminal 102 and the target terminal 103 .

[0268] Exemplarily, the second SLPP message includes a transaction identification field, and the second node 103 directly determines the second transaction based on the transaction identification field, wherein the second transaction is an SLPP transaction between the forwarding terminal 102 and the target terminal 103 .

[0269] Exemplarily, the second SLPP message includes a session identification field. The second node 103 determines a corresponding session based on the session identification field. The session is an SLPP session between terminals associated with the positioning service.

[0270] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0271] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0272] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0273] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0274] In some embodiments, the priority determination method according to the embodiments of the present disclosure may include at least one of steps S2101 and S2102. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, and steps S2101+S2102 may be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0275] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first node 101 directly sends the SLPP message to the second node 103, step S2101 may not be performed.

[0276] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second terminal 103 receives the second SLPP message forwarded by another execution entity, step S2102 may not be executed.

[0277] In some embodiments, steps S2101 to S2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0278] In the above embodiment, when the first node is a core network function node or a server terminal and the second node is a target terminal, when forwarding the SLPP message through the forwarding terminal, the second node can clarify the SLPP transaction and / or SLPP session, thereby improving the reliability of SL positioning and high availability.

[0279] FIG2B is an interactive diagram of a message transmission method according to an embodiment of the present disclosure. As shown in FIG2B , the present disclosure embodiment relates to a message transmission method, which includes:

[0280] Step S2201 : The first node 101 (target terminal) sends a first SLPP message to the forwarding terminal 102 .

[0281] In some embodiments, the first node 101 is a target terminal. In this case, the first node 101 may directly send the first SLPP message to the forwarding terminal 102 .

[0282] In some embodiments, the first SLPP message may include but is not limited to at least one of the following:

[0283] One or two transaction identification fields;

[0284] A session identification field.

[0285] In some embodiments, if the first SLPP message includes two transaction identification fields, the two transaction identification fields may be a first transaction identification field and a second transaction identification field, respectively used to identify the first transaction and the second transaction. The first transaction may be an SLPP transaction between the first node 101 and the second node 103. In the embodiments of the present disclosure, the first transaction is an SLPP transaction between an LMF or a server terminal and a target terminal. The second transaction may be an SLPP transaction between a forwarding terminal and a target terminal, wherein the target terminal is the first node 101. That is, in the embodiments of the present disclosure, the second transaction is an SLPP transaction between the forwarding terminal 102 and the first node 101.

[0286] In some embodiments, the first node 101 may set the first transaction identification field in the two transaction identification fields for identifying the first transaction based on the first transaction identification.

[0287] In addition, since the first node 101 is the target terminal, it can determine the second transaction identifier. Therefore, based on the second transaction identifier, the second transaction identifier field of the two transaction identifier fields can be set to identify the second transaction. The method for setting the second transaction identifier field is similar to the method for setting the first transaction identifier field and is not further described here.

[0288] In some embodiments, if the first SLPP message includes a transaction identification field, the field can be used to identify the first transaction, which is an SLPP transaction between the first node 101 (i.e., the target terminal) and the second node 103 (core network function node or server terminal).

[0289] In some embodiments, the first transaction identifier can be set by the first node 101. That is, when a transaction between a target terminal and a core network function node or a server terminal is initiated by the target terminal, and the first SLPP is the first message of the first transaction, the target terminal can determine the first transaction identifier and ensure that it is not occupied by an existing first transaction and an existing second transaction, where the second transaction is an SLPP transaction between the target terminal and the forwarding terminal. In other words, the uniqueness of the first transaction identifier can be ensured by the target terminal.

[0290] In some embodiments, the first node 101 may set a bit value of a session identifier field in the first SLPP message based on a known session identifier, and the session is an SLPP session between terminals associated with the positioning service.

[0291] In some embodiments, the first SLPP message may include a transaction identification field and a session identification field, or two transaction identification fields and a session identification field. The specific setting method is not repeated here.

[0292] Step S2202: The forwarding terminal 102 sends a second SLPP message to the second node 103 (core network function node or server terminal).

[0293] In some embodiments, the second node 103 may be a core network function node or a server terminal.

[0294] In some embodiments, the forwarding terminal 102 may send the second SLPP message as a payload of a supplementary RSPP message to the second node 103 (core network function node or server terminal).

[0295] In some embodiments, the second SLPP message includes at least one of the following:

[0296] One or two transaction identification fields;

[0297] A session identification field.

[0298] It should be noted that the number of transaction identification fields included in the second SLPP message may be greater than or equal to the number of transaction identification fields included in the first SLPP message.

[0299] In some embodiments, the first SLPP message includes two transaction identification fields, and the second SLPP message also includes two transaction identification fields, where the two transaction identification fields are used to identify the first transaction and the second transaction, respectively.

[0300] In some embodiments, the first node 101 is the target terminal, which has set the first transaction identifier field and the second transaction identifier field according to the first transaction identifier and the second transaction identifier respectively. The content of the first SLPP message is the same as the content of the second SLPP message. The forwarding terminal 101 directly uses the first SLPP message as the payload of the supplementary RSPP message and sends it to the second node 103 (core network function node or server terminal).

[0301] In some embodiments, the first SLPP message includes two transaction identification fields, and the second SLPP message also includes two transaction identification fields, where the two transaction identification fields are used to identify the first transaction and the second transaction, respectively.

[0302] In some embodiments, the first SLPP message includes a transaction identification field, and the transaction identification field is used to identify the first transaction. The second SLPP message includes two transaction identification fields, and the two transaction identification fields are used to identify the first transaction and the second transaction respectively.

[0303] The forwarding terminal 102 may add a second transaction identifier field to the first SLPP message and set the bit value of the second transaction identifier field based on the second transaction identifier to obtain a second SLPP message. The second SLPP message is sent to the second node 103 (core network function node or server terminal) as the payload of the supplementary RSPP message.

[0304] In some embodiments, the first SLPP message includes a transaction identification field, and the transaction identification field is used to identify the first transaction. The second SLPP message also includes a transaction identification field, and the transaction identification field in the second SLPP message is used to identify the second transaction.

[0305] In an example, the first transaction identifier is not occupied by an existing first transaction and is not occupied by an existing second transaction. The second transaction is an SLPP transaction between the target terminal and the forwarding terminal. That is, the target terminal has ensured the uniqueness of the first transaction identifier.

[0306] After receiving the first SLPP message, the forwarding terminal 102 can directly send the first SLPP message as the payload of a supplementary RSPP message to the second node 103 (core network function node or server terminal) without modifying the bit value of the transaction identifier field. This reduces the forwarding delay of the SLPP message and improves availability.

[0307] In one example, the forwarding terminal 102 maintains a mapping relationship between the first transaction identifier and the second transaction identifier. Based on the mapping relationship, the forwarding terminal 102 determines the second transaction identifier to which the first transaction identifier in the first SLPP message is mapped. Based on the determined second transaction identifier, the forwarding terminal 102 resets the transaction identifier field in the first SLPP message to obtain a second SLPP message. The second SLPP message is sent to the second node 103 (core network function node or server terminal) as the payload of a supplementary RSPP message.

[0308] In one example, the forwarding terminal 102 does not maintain a mapping relationship between the first transaction identifier and the second transaction identifier. At this time, the forwarding terminal 102 can determine that the uniqueness of the first transaction identifier is ensured by the first node 101 (target terminal). At this time, the forwarding terminal 102 can send the first SLPP message as the payload of the supplementary RSPP message to the second node 103 (core network function node or server terminal).

[0309] In some embodiments, the first SLPP message includes a session identification field. In this case, the forwarding terminal 102 may send the first SLPP message as a payload of a supplementary RSPP message to the second node 103 (core network function node or server terminal).

[0310] In some embodiments, the first SLPP message may include one transaction identification field and one session identification field, or may include two transaction identification fields and one session identification field, which is not limited in the present disclosure.

[0311] The above description is merely an exemplary description, and the present disclosure does not limit the processing method of the forwarding terminal 102 .

[0312] In some embodiments, the second node 103 (core network function node or server terminal) receives the supplementary RSPP message, thereby obtaining the second SLPP message therein.

[0313] In some embodiments, the second node 10 (core network function node or server terminal) 3 determines the corresponding transaction identifier and / or session identifier based on the second SLPP message.

[0314] Exemplarily, the second SLPP message includes two transaction identification fields, and the second node 103 can determine the second transaction based on the second transaction identification field. The second transaction is an SLPP transaction between the forwarding terminal 102 and the second node 103 (core network function node or server terminal).

[0315] Exemplarily, the second SLPP message includes a transaction identification field, and the second node 103 may determine the second transaction based on the transaction identification field.

[0316] Exemplarily, the second SLPP message includes a session identifier field. When the second node 103 is a core network function node, such as LMF, the second node 103 can determine the parallel session between the second node 103 (LMF) and the target terminal 101 based on the routing identifier or other association identifier.

[0317] Exemplarily, the second SLPP message includes a session identifier field. When the second node 103 is a server terminal, the second node 103 may determine the parallel session between the second node 103 (server terminal) and the target terminal 101 based on the session identifier.

[0318] In some embodiments, the priority determination method according to the embodiments of the present disclosure may include at least one of steps S2201 and S2202. For example, step S2201 may be implemented as an independent embodiment, step S2202 may be implemented as an independent embodiment, and steps S2201+S2202 may be implemented as independent embodiments, but are not limited thereto.

[0319] In some embodiments, step S2201 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first node 101 directly sends the SLPP message to the second node 103, step S2201 may not be performed.

[0320] In some embodiments, step S2202 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second terminal 103 receives the second SLPP message forwarded by another execution entity, step S2202 may not be performed.

[0321] In some embodiments, steps S2201 to S2202 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0322] In the above embodiment, the first node is the target terminal, the second node is the core network function node or the server terminal, and when the SLPP message is forwarded through the forwarding terminal, the second node can clearly identify the SLPP transaction and / or SLPP session, thereby improving the reliability of SL positioning and high availability.

[0323] FIG3A is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to a message transmission method, which can be executed by the first node 101, and the method includes:

[0324] Step S3101: Send a first SLPP message.

[0325] In some embodiments, the first SLPP message may include at least one of the following:

[0326] One or two transaction identification fields;

[0327] A session identification field.

[0328] In some embodiments, the first node 101 may be a core network function node or a server terminal. The first node 101 may send the first SILL message as a payload to the forwarding terminal 102 via a supplementary RSPP message.

[0329] In some embodiments, the first node 101 may be a target terminal. The first node 101 may send a first SILL message to the forwarding terminal 102.

[0330] In some embodiments, the forwarding terminal 102 receives a first SLPP message.

[0331] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, or refer to the optional implementation of step S2201 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0332] In the above embodiment, the first node may send a first SLPP message to the forwarding terminal, which may include one or two transaction identification fields and / or a session identification field, thereby improving the reliability of SL positioning and increasing availability.

[0333] FIG3B is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to a message transmission method, which can be executed by a forwarding terminal 102, and the method includes:

[0334] Step S3201: Obtain a first SLPP message.

[0335] In some embodiments, the forwarding terminal 102 may obtain the first SLPP message from the first node 101 , but is not limited thereto. The forwarding terminal 102 may also receive the first SLPP message sent by other entities.

[0336] In an example, the first node 101 is a core network function node or a server terminal, and the forwarding terminal 102 receives a supplementary RSPP message sent by the core network function node or the server terminal, and determines the first SLPP message based on a payload in the supplementary RSPP message.

[0337] In an example, the first node 101 is a target terminal, and the forwarding terminal 102 receives a first SLPP message sent by the target terminal.

[0338] In some embodiments, the forwarding terminal 102 obtains a first SLPP message determined according to a predefined rule.

[0339] In some embodiments, the forwarding terminal 102 performs processing to obtain the first SLPP message.

[0340] In some embodiments, step S3201 is omitted, the forwarding terminal 102 independently implements the function indicated by the first SLPP message, or the forwarding terminal 102 obtains the first SLPP message based on predefined rules or protocol agreements, or the above function is default or default.

[0341] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, or refer to the optional implementation of step S2201 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0342] Step S3202: Send a second SLPP message.

[0343] In some embodiments, the second SLPP message may include at least one of the following:

[0344] One or two transaction identification fields;

[0345] A session identification field.

[0346] In an example, the first node 101 is a core network function node or a server terminal. The forwarding terminal 102 determines the second SLPP message based on the first SLPP message and sends the second SLPP message to the second node 103 (target terminal).

[0347] In one example, the first node 101 is the target terminal. After the forwarding terminal 102 receives the first SLPP message sent by the target terminal, it determines the second SLPP message and sends the second SLPP message as the payload to the second node 103 (core network function node or server terminal) through a supplementary RSPP message.

[0348] In some embodiments, the second node 103 receives the second SLPP message.

[0349] In some embodiments, the optional implementation of step S3202 can refer to the optional implementation of step S2102 in Figure 2A and other related parts of the embodiment involved in Figure 2A, or refer to the optional implementation of step S2202 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0350] In some embodiments, steps S3201 to S3202 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0351] In the above embodiment, the first node can send a first SLPP message to the forwarding terminal, which may include one or two transaction identification fields and / or a session identification field, and the forwarding terminal sends a second SLPP message to the second node, which may include one or two transaction identification fields and / or a session identification field, thereby improving the reliability of SL positioning and high availability.

[0352] FIG3C is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to a message transmission method, which can be executed by the second node 103. The method includes:

[0353] Step S3301: Obtain a second SLPP message.

[0354] In some embodiments, the second node 103 may obtain the second SLPP message from the forwarding terminal 102 , but is not limited thereto. The second node 103 may also receive the second SLPP message sent by other entities.

[0355] In one example, the second node 103 is a core network function node or a server terminal.

[0356] In one example, the second node 103 is a target terminal.

[0357] In some embodiments, the second node 103 obtains a second SLPP message determined according to a predefined rule.

[0358] In some embodiments, the second node 103 performs processing to obtain the second SLPP message.

[0359] In some embodiments, step S3301 is omitted, the second node 103 autonomously implements the function indicated by the first SLPP message, or the second node 103 obtains the second SLPP message based on predefined rules or protocol agreements, or the above functions are default or default.

[0360] In some embodiments, the optional implementation of step S3301 can refer to the optional implementation of step S2102 in Figure 2A and other related parts of the embodiment involved in Figure 2A, or refer to the optional implementation of step S2202 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0361] In the above embodiment, the second node can receive a second SLPP message sent by the forwarding terminal, which may include one or two transaction identification fields and / or a session identification field, and clarify the SLPP transaction and / or SLPP session based on the second SLPP message, thereby improving the reliability of SL positioning and high availability.

[0362] The above scheme is further illustrated below with examples.

[0363] Example 1, for transaction ID:

[0364] In some embodiments, the SLPP message includes two transaction IDs, one transaction ID corresponding to the SLPP transaction between the forwarding terminal and the target terminal, and the other transaction ID corresponding to the SLPP transaction between the LMF / server terminal and the target terminal.

[0365] Description: The target terminal refers to the object to which the SLPP message from the LMF or server terminal is forwarded, or the SLPP message from the target terminal is sent to the LMF or server terminal through the forwarding terminal.

[0366] In one example, when the LMF / server terminal needs to send an SLPP message to the target terminal by forwarding, the LMF or server terminal sets the transaction ID field between the LMF / server terminal and the target terminal in the SLPP message to be forwarded to the transaction ID between the LMF / server terminal and the target terminal.

[0367] In one example, when the LMF / server terminal needs to send an SLPP message to the target terminal by forwarding, the LMF or server terminal can set the transaction ID between the forwarding terminal and the target terminal in the SLPP message to any value, such as 0, or a specific value agreed upon by the system, or not set the field, or not carry the field.

[0368] In one example, when the target terminal needs to send an SLPP message to the LMF / server terminal by forwarding, the target terminal sets the transaction ID field between the forwarding terminal and the target terminal in the SLPP message that needs to be forwarded to the transaction ID between the forwarding terminal and the target terminal, and sets the transaction ID field between the LMF / server terminal and the target terminal in the SLPP message to the transaction ID between the LMF / server terminal and the target terminal.

[0369] In one example, when the forwarding terminal receives the SLPP message with forwarding from the LMF / server terminal, the forwarding terminal sets the transaction ID field between the forwarding terminal and the target terminal in the SLPP message to be forwarded to the transaction ID between the forwarding terminal and the target terminal.

[0370] Example 2, about Session ID:

[0371] In some embodiments, the SLPP message includes a SLPP Session ID, where the Session ID is the inter-terminal SLPP Session ID associated with the current positioning request.

[0372] In one example, when the LMF needs to send an SLPP message to the target terminal by forwarding, the Session ID is carried in the SLPP message, but the LMF sets the value of the Session ID based on implementation, or sets it to a system agreed value.

[0373] For example, the forwarding terminal ignores the Session ID field sent by the LMF to the forwarding terminal.

[0374] In one example, the forwarding terminal sets the Session ID field in the SLPP message received from the LMF to the inter-UE SLPP Session ID associated with the positioning request.

[0375] In one example, when the target terminal needs to send an SLPP message to the LMF / server terminal by forwarding, the target terminal sets the Session ID field in the SLPP message to be forwarded to the inter-UE SLPP Session ID associated with the positioning request.

[0376] In an example, when the server terminal needs to send an SLPP message to the target by forwarding, the server terminal sets the Session ID field in the SLPP message to be forwarded to the inter-UE SLPP Session ID associated with the positioning request.

[0377] Example 3, regarding transaction ID enhancement mode 2 (wherein the SLPP message includes a transaction identification field):

[0378] In some embodiments, after receiving the SLPP message to be forwarded, the forwarding terminal of the SLPP message sets the transaction ID field in the SLPP message and then forwards the SLPP message to the target terminal.

[0379] For example, when the LMF / server terminal sends the SLPP message to be forwarded to the forwarding terminal, the transaction ID in the SLPP message is set to the transaction ID between the LMF / server terminal and the target terminal.

[0380] For another example, when the target terminal sends the SLPP message to be forwarded to the forwarding terminal, the transaction ID in the SLPP message is set to the transaction ID between the LMF / server terminal and the target terminal.

[0381] In one example, when the forwarding terminal forwards the SLPP message from the LMF / server terminal to the target terminal, if a transaction ID between the target terminal and the forwarding terminal is currently maintained, which maps the transaction ID between the LMF / server terminal and the target terminal, the transaction ID field in the SLPP message is set to the mapped transaction ID between the target terminal and the forwarding terminal.

[0382] In one example, when the forwarding terminal forwards the SLPP message from the LMF / server terminal to the target terminal, if the transaction ID between the target terminal and the forwarding terminal is not currently maintained, the forwarding terminal determines the transaction ID used to send the forwarded SLPP message, creates a mapping relationship between the transaction ID and the transaction ID between the LMF / server terminal and the target terminal, and sets the transaction ID field in the SLPP message to the determined transaction ID between the forwarding terminal and the target terminal.

[0383] For example, when the forwarding terminal determines the transaction ID used to send the forwarded SLPP message, it should ensure that it does not conflict with the transaction ID currently in use.

[0384] In one example, when the target terminal sends an SLPP message to be forwarded to the forwarding terminal, if the transaction between the target terminal and the LMF / server terminal is initiated by the target terminal and the SLPP message is the first message of the transaction, the target terminal determines the transaction ID of the transaction and ensures that the transaction ID is not occupied by other transactions between the target terminal and the forwarding terminal, and the transaction ID is not occupied by other transactions between the target terminal and the LMF / server terminal.

[0385] For example, after receiving the SLPP message from the target terminal, the forwarding terminal directly forwards it to the LMF / server terminal without modifying the transaction ID therein.

[0386] In one example, when the forwarding terminal forwards the SLPP message from the target terminal to the LMF / server terminal, if a transaction ID between the LMF / server terminal and the target terminal that maps the transaction ID between the target terminal and the forwarding terminal is currently maintained, the transaction ID field in the SLPP message is set to the mapped transaction ID between the LMF / server terminal and the target terminal.

[0387] The embodiments of the present disclosure also propose an apparatus for implementing any of the above methods. For example, an apparatus is proposed, which includes units or modules for implementing each step performed by each node (such as the first node, forwarding terminal, second node) in any of the above methods.

[0388] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0389] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0390] FIG4A is a schematic diagram of the structure of a first node proposed in an embodiment of the present disclosure. As shown in FIG4A , the first node 4100 may include: a transceiver module 4101 .

[0391] In some embodiments, the transceiver module 4101 is configured to send a first Sidelink Positioning Protocol (SLPP) message to the forwarding terminal, where the first SLPP message includes at least one of the following:

[0392] One or two transaction identification fields;

[0393] A session identification field.

[0394] In some embodiments, the above-mentioned transceiver module 4101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first node 4100 in any of the above methods (for example, step S2101, step S2201, but not limited to this), which will not be repeated here.

[0395] FIG4B is a schematic diagram of the structure of a forwarding terminal proposed in an embodiment of the present disclosure. As shown in FIG4B , a forwarding terminal 4200 may include: a transceiver module 4201 .

[0396] In some embodiments, the transceiver module 4201 is configured to receive a first Sidelink Positioning Protocol (SLPP) message sent by the first node, where the first SLPP message includes at least one of the following:

[0397] One or two transaction identification fields;

[0398] A session identification field.

[0399] The transceiver module 4201 is further configured to send a second SLPP message to the second node based on the first SLPP message, where the second SLPP message includes at least one of the following:

[0400] One or two transaction identification fields;

[0401] A session identification field.

[0402] In some embodiments, the above-mentioned transceiver module 4201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the forwarding terminal 4200 in any of the above methods (for example, step S2101, step S2102, step S2201, step S2202, but not limited to this), which will not be repeated here.

[0403] FIG4C is a schematic diagram of the structure of a second node proposed in an embodiment of the present disclosure. As shown in FIG4C , the second node 4300 may include: a transceiver module 4301 .

[0404] In some embodiments, the transceiver module 4301 is configured to receive a second Sidelink Positioning Protocol (SLPP) message sent by the forwarding terminal, where the second SLPP message includes at least one of the following:

[0405] One or two transaction identification fields;

[0406] A session identification field.

[0407] In some embodiments, the above-mentioned transceiver module 4301 is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2102, step S2202, but not limited to this) performed by the second node 4300 in any of the above methods, which will not be repeated here.

[0408] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0409] Figure 5A is a schematic diagram of the structure of a communication device 5100 proposed in an embodiment of the present disclosure. Communication device 5100 can be a first node, a forwarding terminal, a second node, or a chip, a chip system, or a processor that supports the first node, forwarding terminal, or second node in implementing any of the above methods. Communication device 5100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0410] As shown in Figure 5A, the communication device 5100 includes one or more processors 5101. The processor 5101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as terminal devices, terminal device chips, core network function nodes, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to perform any of the above methods. Optionally, one or more processors 5101 are used to call instructions to cause the communication device 5100 to perform any of the above methods.

[0411] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2102, step S2201, step S2202, but not limited thereto), and the processor 5101 performs at least one of the other steps. In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

[0412] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data. Alternatively, all or part of the memories 5103 may be located outside the communication device 5100. In alternative embodiments, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuits 5104 are connected to the memory 5102 and may be configured to receive data from the memory 5102 or other devices, or to send data to the memory 5102 or other devices. For example, the interface circuits 5104 may read data stored in the memory 5102 and send the data to the processor 5101.

[0413] The communication device 5100 described in the above embodiment may be a network device, but the scope of the communication device 5100 described in the present disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0414] 5B is a schematic diagram of the structure of a chip 5200 according to an embodiment of the present disclosure. If the communication device 5100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 5200 shown in FIG5B , but the present disclosure is not limited thereto.

[0415] The chip 5200 includes one or more processors 5201. The chip 5200 is configured to execute any of the above methods.

[0416] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data. Alternatively, all or part of memory 5203 may be located external to chip 5200. Optionally, interface circuit 5202 is connected to memory 5203 and may be used to receive data from memory 5203 or other devices, or may be used to send data to memory 5203 or other devices. For example, interface circuit 5202 may read data stored in memory 5203 and send the data to processor 5201.

[0417] In some embodiments, the interface circuit 5202 performs at least one of the communication steps (e.g., steps S2101, S2102, S2201, and S2202) of the aforementioned method. For example, the interface circuit 5202 performing the communication steps (e.g., steps S2101, S2102, S2201, and S2202) of the aforementioned method means that the interface circuit 5202 performs data exchange between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.

[0418] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0419] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 5100, causes the communication device 5100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0420] The present disclosure also provides a program product, which, when executed by the communication device 5100, enables the communication device 5100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0421] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

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

[0423] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A message transmission method, characterized in that: The method is performed by a first node and includes: Send a first Sidelink Positioning Protocol (SLPP) message to the forwarding terminal, where the first SLPP message includes at least one of the following: One or two transaction identification fields; A session identification field.

2. The method according to claim 1, characterized in that In the case where the first SLPP message includes two transaction identification fields, the two transaction identification fields are respectively used to identify: a first transaction, where the first transaction is an SLPP transaction between the first node and a second node; as well as The second transaction is an SLPP transaction between the forwarding terminal and a target terminal, and the target terminal is one of the first node and the second node.

3. The method according to claim 2, characterized in that The method further comprises: Based on the transaction identifier of the first transaction, a first transaction identifier field of the two transaction identifier fields is set.

4. The method according to claim 2 or 3, characterized in that The first node is a core network function node or a server terminal, and the method further includes any one of the following: Setting the second transaction identification field of the two transaction identification fields to a first value; The second transaction identification field of the two transaction identification fields is not set.

5. The method according to claim 2 or 3, characterized in that The first node is a target terminal, and the method further includes: Based on the transaction identifier of the second transaction, the second transaction identifier field of the two transaction identifier fields is set.

6. The method according to claim 1, characterized in that In a case where the first SLPP message includes one transaction identification field, the one transaction identification field is used to identify a first transaction, where the first transaction is an SLPP transaction between the first node and the second node.

7. The method according to claim 6, characterized in that The first node is a target terminal, the first transaction identifier is not occupied by an existing first transaction, and is not occupied by an existing second transaction, and the second transaction is an SLPP transaction between the target terminal and the forwarding terminal.

8. The method according to any one of claims 1 to 7, characterized in that The first node is a core network function node, and the method further includes: The session identification field is set to a second value.

9. The method according to any one of claims 1 to 7, characterized in that The first node is a target terminal or a server terminal, and the method further includes: The session identifier field is set based on an identifier of a session, where the session is an SLPP session between terminals associated with a positioning service.

10. A message transmission method, characterized in that: The method is executed by a forwarding terminal and includes: Receive a first Sidelink Positioning Protocol (SLPP) message sent by a first node, where the first SLPP message includes at least one of the following: One or two transaction identification fields; A session identification field; Sending a second SLPP message to the second node based on the first SLPP message, where the second SLPP message includes at least one of the following: One or two transaction identification fields; A session identification field.

11. The method according to claim 10, characterized in that When the first SLPP message includes two transaction identification fields, the second SLPP message includes two transaction identification fields.

12. The method according to claim 11, characterized in that The two transaction identification fields are used to identify: a first transaction, where the first transaction is an SLPP transaction between the first node and the second node; The second transaction is an SLPP transaction between the forwarding terminal and a target terminal, and the target terminal is one of the first node and the second node.

13. The method according to claim 12, characterized in that The first node is a core network function node or a server terminal, and the method further includes: Based on the second transaction identifier, the second transaction identifier field included in the first SLPP message is set to obtain the second SLPP message.

14. The method according to claim 10, characterized in that When the first SLPP message includes one transaction identification field, the second SLPP message includes two transaction identification fields.

15. The method according to claim 14, characterized in that The transaction identifier field in the first SLPP message is used to identify a first transaction, where the first transaction is an SLPP transaction between the first node and the second node; The two transaction identification fields included in the second SLPP message are respectively used to identify: the first transaction; The second transaction is a second SLPP transaction between the forwarding terminal and a target terminal, and the target terminal is one of the first node and the second node.

16. The method according to claim 15, characterized in that The method further comprises: A second transaction identifier field is added to the first SLPP message to obtain the second SLPP message.

17. The method according to claim 10, wherein: When the first SLPP message includes one transaction identification field, the second SLPP message includes one transaction identification field.

18. The method according to claim 17, characterized in that The transaction identifier field in the first SLPP message is used to identify a first transaction, where the first transaction is an SLPP transaction between the first node and the second node; The transaction identification field in the second SLPP message is used to identify a second transaction, where the second transaction is an SLPP transaction between the forwarding terminal and a target terminal, and the target terminal is one of the first node and the second node.

19. The method according to claim 18, characterized in that The method further comprises: Maintaining a mapping relationship between the first transaction identifier and the second transaction identifier, and determining the second transaction identifier based on the mapping relationship; Based on the determined second transaction identifier, the transaction identifier field in the first SLPP message is reset to obtain the second SLPP message.

20. The method according to claim 19, wherein The first node is a core network function node or a server terminal, and the method further includes: The mapping relationship between the first transaction identifier and the second transaction identifier is not maintained, and the second transaction identifier is created; Creating the mapping relationship; Based on the created second transaction identifier, the transaction identifier field in the first SLPP message is reset to obtain the second SLPP message.

21. The method according to claim 19, wherein The first node is a target terminal, the first transaction identifier is not occupied by an existing first transaction and is not occupied by an existing second transaction, and the second transaction is an SLPP transaction between the target terminal and the forwarding terminal; The sending a second SLPP message to the second node based on the first SLPP message includes: Send the first SLPP message to the second node.

22. The method according to any one of claims 10 to 21, characterized in that The first node is a core network function node, and the method further includes: The session identifier field in the second SLPP message is set based on the session identifier, where the session is an SLPP session between terminals associated with the positioning service.

23. A message transmission method, characterized in that: The method is performed by the second node and includes: Receive a second Sidelink Positioning Protocol (SLPP) message sent by the forwarding terminal, where the second SLPP message includes at least one of the following: One or two transaction identification fields; A session identification field.

24. The method according to claim 23, wherein The second SLPP message includes two transaction identification fields, which are respectively used to identify: a first transaction, where the first transaction is an SLPP transaction between the first node and the second node; The second transaction is an SLPP transaction between the forwarding terminal and a target terminal, and the target terminal is one of the first node and the second node.

25. The method according to claim 23, characterized in that The second SLPP message includes a transaction identification field, and the transaction identification field in the second SLPP message is used to identify a second transaction. The second transaction is an SLPP transaction between the forwarding terminal and the target terminal, and the target terminal is one of the first node and the second node.

26. A first node, characterized in that: include: The transceiver module is configured to send a first Sidelink Positioning Protocol (SLPP) message to the forwarding terminal, where the first SLPP message includes at least one of the following: One or two transaction identification fields; A session identification field.

27. A forwarding terminal, characterized in that: include: The transceiver module is configured to receive a first Sidelink Positioning Protocol (SLPP) message sent by the first node, where the first SLPP message includes at least one of the following: One or two transaction identification fields; A session identification field; The transceiver module is further configured to send a second SLPP message to the second node based on the first SLPP message, where the second SLPP message includes at least one of the following: One or two transaction identification fields; A session identification field.

28. A second node, characterized in that: include: The transceiver module is configured to receive a second Sidelink Positioning Protocol (SLPP) message sent by the forwarding terminal, where the second SLPP message includes at least one of the following: One or two transaction identification fields; A session identification field.

29. A first node, characterized in that: include: one or more processors; The processor is configured to execute the message transmission method according to any one of claims 1 to 9.

30. A forwarding terminal, characterized in that: include: one or more processors; The processor is configured to execute the message transmission method according to any one of claims 10 to 22.

31. A second node, characterized in that: include: one or more processors; The processor is used to execute the message transmission method according to any one of claims 23 to 25.

32. A communication system, characterized in that: include: A first node, wherein the first node is configured to implement the message transmission method according to any one of claims 1 to 9; A forwarding terminal configured to implement the message transmission method according to any one of claims 10 to 22. The second node is configured to implement the message transmission method according to any one of claims 23 to 25.

33. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the message transmission method according to any one of claims 1-9, 10-22 or 23-25.

34. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, it is used to implement the message transmission method according to any one of claims 1 to 9, 10 to 22 or 23 to 25.

Images