Connection establishment method, first device, first entity, and second entity

Abstract

The present disclosure relates to a connection establishment method, a first device, a first entity, and a second entity. The method comprises: a first device sends a first message to a first entity, and then receives a second message sent by the first entity. Thus, a positioning reference unit (PRU) triggers the establishment of a user plane connection while a PRU association process is executed, so that the flexibility of user plane connection establishment is improved, and communication efficiency is improved.

Description

Connection establishment method, first device, first entity and second entity Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a connection establishment method, a first device, a first entity, and a second entity. Background Art

[0002] In the field of communications technology, a Location Management Function (LMF) network element or User Equipment (UE) may trigger the establishment of a user plane connection and maintain, modify, or terminate the established user plane.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a connection establishment method, a first device, a first entity and a second entity, which to a certain extent solve the problem of how to add a new trigger in the user plane positioning initiated by the LMF network element when executing the positioning reference unit (PRU) association process.

[0005] According to a first aspect of an embodiment of the present disclosure, a connection establishment method is provided, which is performed by a first device. The method includes:

[0006] Sending a first message to the first entity, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with the second entity;

[0007] A second message sent by the first entity is received, where the second message includes an identifier of the second entity and first indication information, where the first indication information is used to indicate whether establishment of the PRU association is allowed.

[0008] According to a second aspect of an embodiment of the present disclosure, a connection establishment method is provided, which is performed by a first entity. The method includes:

[0009] receiving a first message sent by a first device, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with a second entity;

[0010] Sending a third message to the second entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0011] receiving a fourth message sent by the second entity, wherein the fourth message includes an identifier of the second entity and first indication information, where the first indication information is used to indicate whether establishment of the PRU association is allowed;

[0012] Send a second message to the first device, where the second message includes an identifier of the second entity and the first indication information.

[0013] According to a third aspect of an embodiment of the present disclosure, a connection establishment method is provided, which is performed by a second entity. The method includes:

[0014] receiving a third message sent by the first entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0015] A fourth message is sent to the first entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether establishment of the PRU association is allowed.

[0016] According to a fourth aspect of an embodiment of the present disclosure, a connection establishment method is proposed, which is applied to a communication system. The method includes:

[0017] The first entity receives a first message sent by the first device, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with the second entity;

[0018] The first entity sends a third message to the second entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0019] The second entity sends a fourth message to the first entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow establishment of the PRU association;

[0020] The first entity sends a second message to the first device, wherein the second message includes an identifier of the second entity and the first indication information.

[0021] According to a fifth aspect of the embodiments of the present disclosure, a first device is provided, including:

[0022] a transceiver module, configured to send a first message to the first entity, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with the second entity;

[0023] The transceiver module is further used to receive a second message sent by the first entity, where the second message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow the PRU association to be established.

[0024] According to a sixth aspect of an embodiment of the present disclosure, a first entity is provided, including:

[0025] a transceiver module, configured to receive a first message sent by a first device, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with a second entity;

[0026] The transceiver module is further configured to send a third message to the second entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0027] The transceiver module is further configured to receive a fourth message sent by the second entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow establishment of the PRU association;

[0028] The transceiver module is further configured to send a second message to the first device, wherein the second message includes an identifier of the second entity and the first indication information.

[0029] According to a seventh aspect of an embodiment of the present disclosure, a second entity is provided, including:

[0030] a transceiver module, configured to receive a third message sent by the first entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0031] The transceiver module is further used to send a fourth message to the first entity, wherein the fourth message includes the identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow the PRU association to be established.

[0032] According to an eighth aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0033] one or more processors;

[0034] The processor is used to call instructions to enable the communication device to execute the processing method described in any one of the first aspect, the second aspect, and the third aspect.

[0035] According to the ninth aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a first entity and a second entity, wherein the first entity is configured to implement the connection establishment method described in the second aspect, and the second entity is configured to implement the connection establishment method described in the third aspect.

[0036] According to the tenth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes the connection establishment method as described in any one of the first aspect, the second aspect, and the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0038] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0039] FIG2 is an interactive schematic diagram of a connection establishment method according to an embodiment of the present disclosure;

[0040] 3A-3B are flowcharts of a connection establishment method according to an embodiment of the present disclosure;

[0041] 4A-4B are flowcharts of a connection establishment method according to an embodiment of the present disclosure;

[0042] 5A-5B are flowcharts of a connection establishment method according to an embodiment of the present disclosure;

[0043] FIG6 is an interactive schematic diagram illustrating a connection establishment method according to an embodiment of the present disclosure;

[0044] FIG7 is an interactive schematic diagram of a connection establishment method according to an embodiment of the present disclosure;

[0045] FIG8A is a schematic structural diagram of a first device proposed in an embodiment of the present disclosure;

[0046] FIG8B is a schematic structural diagram of the first entity proposed in an embodiment of the present disclosure;

[0047] FIG8C is a schematic structural diagram of a second entity proposed in an embodiment of the present disclosure;

[0048] FIG9A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0049] FIG9B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0050] The embodiments of the present disclosure provide a connection establishment method, a first device, a first entity, and a second entity.

[0051] In a first aspect, an embodiment of the present disclosure provides a connection establishment method, which is performed by a first device. The method includes:

[0052] Sending a first message to the first entity, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with the second entity;

[0053] A second message sent by the first entity is received, where the second message includes an identifier of the second entity, first indication information, and user plane information, where the first indication information is used to indicate whether establishment of the PRU association is allowed.

[0054] In the above embodiment, the first device simultaneously requests to establish a user plane connection with the second entity during the PRU association process, thereby improving the flexibility of establishing the user plane connection and improving the efficiency of information interaction.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, sending the first message to the first entity includes:

[0056] Determine to use user plane positioning, and send the first message to the first entity.

[0057] In the above embodiment, when it is determined to use user plane positioning, the first device sends the first message to the first entity, thereby improving the efficiency of establishing the user plane connection.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, determining to use user plane positioning includes:

[0059] Determining to use user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, a first policy, a state of the first entity, and a type of a last used positioning plane.

[0060] In the above embodiment, whether to use user plane positioning is determined based on information such as capability information of the first device and capability information of the second entity, thereby ensuring the accuracy and reliability of establishing the user plane connection.

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

[0062] Determine a second protocol based on current user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, a second policy, and a first protocol based on which the last user plane positioning was performed.

[0063] In the above embodiment, the protocol based on the user plane is determined based on the capability information of the first device, geothermal strategy and other information, thereby ensuring the reliability of data transmission.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device;

[0065] The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

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

[0067] Based on the user plane information, a user plane connection is established with the second entity, wherein the first indication information indicates that establishment of the PRU association is allowed, and the second message further includes the user plane information.

[0068] In the above embodiment, a user plane connection is established between the first device and the second entity based on the user plane information, thereby improving the accuracy and security of establishing the user plane connection.

[0069] In combination with some embodiments of the first aspect, in some embodiments, the first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, an identifier of the second entity, the reason for PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier on which the user plane positioning is based.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the user plane information includes at least one of the following: an address of the second entity, and a fifth protocol identifier on which user plane positioning is based.

[0071] In the above embodiment, based on the user plane information, the efficiency of establishing the user plane connection between the first device and the second entity is improved.

[0072] In a second aspect, an embodiment of the present disclosure provides a connection establishment method, which is performed by a first entity. The method includes:

[0073] receiving a first message sent by a first device, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with a second entity;

[0074] Sending a third message to the second entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0075] receiving a fourth message sent by the second entity, wherein the fourth message includes an identifier of the second entity and first indication information, where the first indication information is used to indicate whether establishment of the PRU association is allowed;

[0076] Send a second message to the first device, where the second message includes an identifier of the second entity and the first indication information.

[0077] In the above embodiment, the first entity selects a suitable second entity for the first device based on the association request sent by the first device, and sends the association request to the target second entity, thereby improving the stability of the user plane connection between the first device and the second entity.

[0078] With reference to some embodiments of the second aspect, in some embodiments, sending the third message to the second entity includes:

[0079] Verifying whether the first device is a PRU;

[0080] Determine that the first device is a PRU, and send the third message to the second entity.

[0081] In the above embodiment, based on the case where the first device is a PRU, the third message is sent to the second entity, thereby ensuring the security of data transmission.

[0082] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, an identifier of the second entity, a reason for associating the PRU, positioning capability of the first device, location information of the first device, a switch state of the first device, and a second protocol identifier on which user plane positioning is based;

[0083] The third message includes at least one of the following: the second indication information, the third indication information, the first capability information of the first device, the reason for the PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier.

[0084] In combination with some embodiments of the second aspect, in some embodiments, the first capability information includes at least one of the following items: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device.

[0085] In combination with some embodiments of the second aspect, in some embodiments, the first indication information indicates that the PRU association is allowed to be established, and the fourth message and the second message also include user plane information, and the user plane information includes at least one of the following: the address of the second entity, and the fifth protocol identifier on which the user plane positioning is based.

[0086] In a third aspect, an embodiment of the present disclosure provides a connection establishment method, which is performed by a second entity. The method includes:

[0087] receiving a third message sent by the first entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0088] A fourth message is sent to the first entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether establishment of the PRU association is allowed.

[0089] In conjunction with some embodiments of the third aspect, in some embodiments, before sending the fourth message to the first entity, the method further includes:

[0090] Determine to use user plane positioning.

[0091] In conjunction with some embodiments of the third aspect, in some embodiments, determining to use user plane positioning includes:

[0092] Determine to use user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, a third policy, a state of the first entity, and a type of positioning plane last used by the first device.

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

[0094] Refuse to perform positioning based on the second protocol on which the user plane positioning contained in the third message is based, and determine the fifth protocol on which the current user plane positioning is based based on one or more of the first capability information of the first device, the second capability information of the second entity, the second protocol identifier, the fourth strategy, and the first protocol on which the first device last used user plane positioning.

[0095] In conjunction with some embodiments of the third aspect, in some embodiments, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device;

[0096] The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

[0097] In combination with some embodiments of the third aspect, in some embodiments, the third message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, the reason for the PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier on which the user plane positioning is based.

[0098] In combination with some embodiments of the third aspect, in some embodiments, the first indication information indicates that the PRU association is allowed to be established, and the fourth message also includes user plane information, and the user plane information includes at least one of the following: the address of the second entity, and the fifth protocol identifier on which the user plane positioning is based.

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

[0100] Based on the fifth protocol identifier, a user plane connection is established with the first device.

[0101] In the above embodiment, a user plane connection with the first device is established based on the fifth protocol identifier, thereby ensuring the stability of establishing the user plane connection and the reliability of data transmission.

[0102] In a fourth aspect, an embodiment of the present disclosure provides a connection establishment method, which is applied to a communication system. The method includes:

[0103] The first entity receives a first message sent by the first device, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with the second entity;

[0104] The first entity sends a third message to the second entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0105] The second entity sends a fourth message to the first entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow establishment of the PRU association;

[0106] The first entity sends a second message to the first device, wherein the second message includes an identifier of the second entity and the first indication information.

[0107] In a fifth aspect, an embodiment of the present disclosure provides a first device, the first device including:

[0108] a transceiver module, configured to send a first message to the first entity, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with the second entity;

[0109] The transceiver module is further used to receive a second message sent by the first entity, where the second message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow the PRU association to be established.

[0110] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further configured to:

[0111] Determine to use user plane positioning, and send the first message to the first entity.

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

[0113] The processing module is configured to determine to use user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, a first policy, a state of the first entity, and a type of a last used positioning plane.

[0114] In conjunction with some embodiments of the fifth aspect, in some embodiments, the processing module is further configured to:

[0115] Determine a second protocol based on current user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, a second policy, and a first protocol based on which the last user plane positioning was performed.

[0116] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device;

[0117] The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

[0118] In conjunction with some embodiments of the fifth aspect, in some embodiments, the processing module is further configured to:

[0119] Based on the user plane information, a user plane connection is established with the second entity.

[0120] In combination with some embodiments of the fifth aspect, in some embodiments, the first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, an identifier of the second entity, the reason for PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier on which the user plane positioning is based.

[0121] In combination with some embodiments of the fifth aspect, in some embodiments, the first indication information indicates that the PRU association is allowed to be established, and the second message also includes user plane information, and the user plane information includes at least one of the following: the address of the second entity, and the fifth protocol identifier on which the user plane positioning is based.

[0122] In a sixth aspect, an embodiment of the present disclosure provides a first entity, wherein the first entity includes:

[0123] a transceiver module, configured to receive a first message sent by a first device, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with a second entity;

[0124] The transceiver module is further configured to send a third message to the second entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0125] The transceiver module is further configured to receive a fourth message sent by the second entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow establishment of the PRU association;

[0126] The transceiver module is further configured to send a second message to the first device, wherein the second message includes an identifier of the second entity and the first indication information.

[0127] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module further includes:

[0128] a processing module, configured to verify whether the first device is a PRU;

[0129] The transceiver module is configured to determine that the first device is a PRU and send the third message to the second entity.

[0130] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, an identifier of the second entity, a reason for associating the PRU, positioning capability of the first device, location information of the first device, a switch state of the first device, and a second protocol identifier on which user plane positioning is based;

[0131] The third message includes at least one of the following: the second indication information, the third indication information, the first capability information of the first device, the reason for the PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier.

[0132] In combination with some embodiments of the sixth aspect, in some embodiments, the first capability information includes at least one of the following items: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device.

[0133] In combination with some embodiments of the sixth aspect, in some embodiments, the first indication information indicates that the establishment of a PRU association is allowed, and the fourth message and the second message also include user plane information, and the user plane information includes at least one of the following: the address of the second entity, and the fifth protocol identifier on which the user plane positioning is based.

[0134] In a seventh aspect, the present disclosure provides a second entity, including:

[0135] a transceiver module, configured to receive a third message sent by the first entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0136] The transceiver module is further used to send a fourth message to the first entity, wherein the fourth message includes the identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow the PRU association to be established.

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

[0138] The processing module is used to determine the use of user plane positioning.

[0139] In conjunction with some embodiments of the seventh aspect, in some embodiments, the processing module is further configured to:

[0140] Determine to use user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, a third policy, a state of the first entity, and a type of positioning plane last used by the first device.

[0141] In conjunction with some embodiments of the seventh aspect, in some embodiments, the processing module is further configured to:

[0142] Refuse to perform positioning based on the second protocol on which the user plane positioning contained in the third message is based, and determine the fifth protocol on which the current user plane positioning is based based on one or more of the first capability information of the first device, the second capability information of the second entity, the second protocol identifier, the fourth strategy, and the first protocol on which the first device last used user plane positioning.

[0143] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device;

[0144] The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

[0145] In combination with some embodiments of the seventh aspect, in some embodiments, it is characterized in that the third message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, the reason for the PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier on which the user plane positioning is based.

[0146] In combination with some embodiments of the seventh aspect, in some embodiments, the first indication information indicates that the PRU association is allowed to be established, and the fourth message also includes user plane information, and the user plane information includes at least one of the following: the address of the second entity, and the fifth protocol identifier on which the user plane positioning is based.

[0147] In conjunction with some embodiments of the seventh aspect, in some embodiments, the method and the processing module are further used to:

[0148] Based on the fifth protocol identifier, a user plane connection is established with the first device.

[0149] In an eighth aspect, an embodiment of the present disclosure proposes a first device, which includes: one or more processors; wherein the processors are used to execute an optional implementation of the connection establishment method proposed in the first aspect.

[0150] In a ninth aspect, an embodiment of the present disclosure proposes a first entity, which includes: one or more processors; wherein the processors are used to execute an optional implementation of the connection establishment method proposed in the second aspect.

[0151] In a tenth aspect, an embodiment of the present disclosure proposes a second entity, and the second entity includes: one or more processors; wherein the processor is used to execute an optional implementation of the connection establishment method proposed in the third aspect.

[0152] In the eleventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a first entity and a second entity; wherein the first entity is configured to execute the method described in the optional implementation manner of the second aspect, and the second entity is configured to execute the method described in the optional implementation manner of the third aspect.

[0153] In the twelfth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect or the third aspect.

[0154] In a thirteenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect or the third aspect.

[0155] In a fourteenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0156] In a fifteenth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0157] It is understandable that the first device, first entity, second entity, communication system, storage medium, program product, computer program, chip, or chip system described above are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0158] The embodiments of the present disclosure provide a connection establishment method. In some embodiments, the terms connection establishment method, measurement report reporting configuration method, configuration method, and connection establishment method are interchangeable; the terms information processing device, information configuration device, and communication device are interchangeable; and the terms information transmission system, information configuration system, and communication system are interchangeable.

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

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

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

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

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

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

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

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

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

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

[0169] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0170] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0171] 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", "chip", "chip system", "entity", "subject", etc.

[0172] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0173] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macrocell", "smallcell", "femtocell", "picocell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0174] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station (subscriber station), mobile unit (mobile unit), subscriber unit (subscribe runit), wireless unit (wireless unit), remote unit (remote unit), mobile device (mobile device), wireless device (wireless device), wireless communication device (wireless communication device), remote device (remoted device), mobile subscriber station (mobile subscriber station), access terminal (access terminal), mobile terminal (mobile terminal), wireless terminal (wireless terminal), remote terminal (remote terminal), handset (handset), user agent (user agent), mobile client (mobile client), client (client), etc.

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

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

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

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

[0179] As shown in FIG1 , a communication system 100 includes a first device 101 , a first entity 102 , and a second entity 103 .

[0180] In some embodiments, the first device 101 may be a terminal. The terminal includes, for example, at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, 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.

[0181] In some embodiments, the first device 101 may also be an access network device. The access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home nodeB (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.

[0182] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0183] In some embodiments, the first entity 102 and the second entity 103 may be core network devices. The first entity 102 and the second entity 103 may be a single device, multiple devices, or a group of devices. The first entity 102 and the second entity 103 may be virtual or physical. The core network, for example, includes at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0184] In some embodiments, the first entity 102 may be, for example, an Access and Mobility Management Function (AMF) network element.

[0185] In some embodiments, the second entity 103 may be, for example, a location management function (LMF) network element.

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

[0187] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are 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.

[0188] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER3G, 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 (Ultra Mobile Broadband), and other technologies. Broadband (UMB), IEEE802.11 (Wi-Fi (registered trademark)), IEEE802.16 (WiMAX (registered trademark)), IEEE802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine-to-Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other connection establishment methods, next-generation systems based on them, etc. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A with 5G, etc.) for application.

[0189] The location management function (LMF) or the UE may trigger the establishment of a user plane connection. The UE and LMF may maintain the established user plane connection. The LMF may modify or terminate the user plane connection established between the UE and the LMF.

[0190] The UE can support the functions of the Positioning Reference Unit (PRU): support service level association, association update and disassociation with the serving LMF, PRU sends service level association, association update or disassociation to the LMF through the Location Services (LCS) supplementary service message, and supports association with multiple LMFs. For example, for the case where the PRU is in the service area where multiple LMFs overlap, the PRU information included in the PRU association or PRU association update includes one or more of the following aspects: PRU positioning capability, location information (if known), and PRU ON / OFF status indication of the temporary availability of the UE's PRU function at the serving LMF.

[0191] Among them, UE accessing the 5G network via NR satellite shall not operate as a PRU

[0192] FIG2 is an interactive diagram of a connection establishment method according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a connection establishment method, the method comprising:

[0193] Step S2101: When the first device 101 is determined to be a PRU, it determines whether to use user plane positioning.

[0194] In some embodiments, the first device 101 may be a user equipment (UE) or an access network device, such as a gNB, which is not limited in this disclosure.

[0195] In some embodiments, in some embodiments, the terms "positioning reference unit PRU", "Positioning Reference Unit", "PRU" and the like can be used interchangeably.

[0196] In some embodiments, the first device 101 may determine to use user plane positioning based on one or more of the first capability information of the first device 101, the second capability information of the second entity 103, the first policy, the status of the first entity 102, and the type of positioning plane last used.

[0197] In some embodiments, the first capability information of the first device 101 includes at least one of the following: whether the first device 101 supports user plane positioning, whether the first device 101 supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device 101.

[0198] In some embodiments, the third protocol identifier is used to indicate the protocol supported by the first device 101. The third protocol identifier may be any implementation form to indicate the third protocol. For example, the third protocol identifier may be the name of the third protocol, which is not limited in this disclosure.

[0199] In some embodiments, the third protocol may include at least one of the SUPL protocol and the LCS-UPP protocol, which is not limited in the present disclosure.

[0200] In some embodiments, the terms "SUPL protocol", "Secure User Plane Location protocol", "Secure User Plane Location protocol", etc. can be used interchangeably.

[0201] In some embodiments, terms such as “LCS-UPP protocol”, “Location Services-Universal Parallel Port Protocol”, and “Location Services-Universal Parallel Port Protocol” may be used interchangeably.

[0202] In some embodiments, the first device 101 needs to register with the network before initiating an association request and a user plane connection establishment request. After the registration authorization authentication is passed, the network can send the second capability information of the second entity 103 to the first device 101. At this time, the first device 101 can obtain the capability information of the second entity 103.

[0203] In some embodiments, the second capability information of the second entity 103 includes at least one of the following: whether the second entity 103 supports user plane positioning, whether the second entity 103 supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity 103.

[0204] Among them, the identifier of the fourth protocol and the specific implementation method of the fourth protocol refer to the relevant description of the optional implementation method of step S2101, which will not be repeated here.

[0205] In some embodiments, the first policy may be a locally preset policy, or may be a policy configured by a PCF network element, etc., which is not limited in this disclosure.

[0206] In some embodiments, terms such as "PCF network element" and "Policy Control Function (PCF) network element" can be used interchangeably.

[0207] In some embodiments, the state of the first entity 102 is used to represent the current load state of the first entity 102. For example, the state of the first entity 102 may be a congestion state, etc., which is not limited in the present disclosure.

[0208] In some embodiments, the first entity 102 is, for example, an Access and Mobility Management Function (AMF) network element.

[0209] In some embodiments, terms such as "first entity", "mobile access management function network element", "AMF network element", etc. can be used interchangeably.

[0210] In some embodiments, the second entity 103 is, for example, a location management function (LMF) network element.

[0211] In some embodiments, terms such as "second entity", "location management function network element", "LMF network element" and the like can be used interchangeably.

[0212] In some embodiments, the type of the positioning plane may be a user plane or a control plane, which is not limited in this disclosure.

[0213] In some embodiments, the name of the positioning surface is not limited, and it can also be "positioning plane", "surface based on positioning", "plane used for positioning data transmission", etc., which is not limited in this disclosure.

[0214] In some embodiments, if the first capability information of the first device 101 includes that the first device 101 only supports user plane positioning, or the second capability information of the second entity 103 includes that the second entity 103 only supports user plane positioning, or the first entity 102 is in a congested state, or the priority of supporting the user plane in the first policy of the second entity 103 is higher, or the type of positioning plane last used by the first device 101 is the user plane type, then the first device 101 can determine to use user plane positioning.

[0215] In some embodiments, the first device 101 can determine whether to use user plane positioning based on multiple items of the first capability information of the first device 101, the second capability information of the second entity 103, the first policy, the status of the first entity 102, and the type of positioning plane last used by the first device 101.

[0216] Step S2102: When determining to use user plane positioning, the first device 101 determines a second protocol based on which the current user plane positioning is based.

[0217] In some embodiments, the first device may determine the second protocol on which the current user plane positioning is based based on one or more of the first capability information of the first device, the second capability information of the second entity, the second policy, and the first protocol on which the last user plane positioning was based.

[0218] In some embodiments, the second policy may be a locally preset policy, or may be a policy configured by a PCF network element, etc. It may be the same as the first policy or different from the first policy, and this disclosure does not limit this.

[0219] In some embodiments, the second protocol may include at least one of the SUPL protocol and the LCS-UPP protocol. The specific implementation of the second protocol refers to the description of the optional implementation of step S2101, which will not be repeated here.

[0220] In some embodiments, in some embodiments, when the first device 101 determines to use user plane positioning, it can further determine the protocol based on which the user plane positioning is based. The first device 101 can select the protocol based on the capabilities of the first device 101 and the second entity 103, for example, the protocol can be selected based on the capabilities of the first device 101 and the second entity 103 to support the SUPL protocol or the LCS-UPP protocol.

[0221] In some embodiments, the first device 101 may also determine the protocol based on which the user plane positioning is based based on a local policy or a policy configured by a PCF network element.

[0222] Step S2103 : The first device 101 sends a first message to the first entity 102 .

[0223] In some embodiments, the first message is used to request establishment of a PRU association and to request establishment of a user plane connection with the second entity 103 .

[0224] In some embodiments, the name of the first message is not limited, and may be, for example, "ULNAS TRANSPORT".

[0225] In some embodiments, after determining to use user plane positioning, the first device 101 sends a first message to the first entity 102 .

[0226] In some embodiments, the first message may include at least one of the following: second indication information for indicating that the first device 101 is a PRU, third indication information for indicating establishment of a user plane connection with the second entity 103, first capability information of the first device 101, an identifier of the second entity 103, a reason for PRU association, positioning capability of the first device 101, location information of the first device 101, a switch status of the first device 101, and a second protocol identifier on which user plane positioning is based.

[0227] In some embodiments, the number of bits occupied by the second indication information may be one or more. For example, the second indication information occupies one bit, and indicates whether the first device 101 is a PRU through different values. For example, "1" indicates that the first device 101 is a PRU, and "0" indicates that the first device 101 is not a PRU; or, "0" indicates that the first device 101 is a PRU, and "1" indicates that the first device 101 is not a PRU. Alternatively, if the first message contains the second indication information, it indicates that the first device 101 is a PRU; if the first message does not contain the second indication information, it indicates that the first device 101 is not a PRU, and so on. This disclosure is not limited to this.

[0228] In some embodiments, the number of bits occupied by the third indication information may be one or more. For example, the third indication information occupies one bit and indicates whether the first device 101 establishes a user plane connection with the second entity 103 through different values. For example, "1" indicates that the first device 101 establishes a user plane connection with the second entity 103, and "0" indicates that the first device 101 does not establish a user plane connection with the second entity 103; or, "0" indicates that the first device 101 establishes a user plane connection with the second entity 103, and "1" indicates that the first device 101 does not establish a user plane connection with the second entity 103. Alternatively, if the first message includes the third indication information, it indicates that the first device 101 establishes a user plane connection with the second entity 103; if the third indication information is not included, it indicates that the first device 101 does not establish a user plane connection with the second entity 103, and so on. This disclosure is not limited to this.

[0229] In some embodiments, the identifier of the second entity 103 may be, for example, a “Routing ID”.

[0230] In some embodiments, the identifier of the second entity 103 is used to uniquely identify a second entity 103 , and the second entity 103 may be, for example, a location management function (LMF) network element.

[0231] In some embodiments, the reason for PRU association may be initial PRU association, or may be PRU association update, etc., which is not limited in the present disclosure.

[0232] The specific implementation of the second protocol identifier refers to the description of the optional implementation of step S2101 and will not be repeated here.

[0233] In some embodiments, the first entity 102 receives a first message sent by the first device 101 .

[0234] Step S2104 , the first entity 102 verifies whether the first device 101 is a PRU.

[0235] In some embodiments, the first entity 102 may verify whether the sender of the first device association request is a PRU based on the subscription information of the first device 101 from the UDM network element.

[0236] In some embodiments, the first entity 102 may also verify whether the first device 101 can operate as a fixed PRU based on subscription information or local policies.

[0237] In step S2105 , when the first entity 102 determines that the first device 101 is a PRU, the first entity 102 sends a third message to the second entity 103 .

[0238] In some embodiments, the first entity 102 may first determine the second entity 103 associated with the first device 101 , and then send the third message to the associated second entity 103 .

[0239] In some embodiments, if the first message includes an identifier of the second entity 103, the first entity 102 may determine the second entity 103 associated with the first device 101 based on the identifier of the second entity 103, and then further determine whether to associate the first device 101 with the second entity 103 indicated by the identifier of the second entity 103 in the first message. If the determination is to associate with the second entity 103 indicated by the identifier of the second entity 103, the first entity 102 will send an association request for the first device 101 to the second entity 103 indicated in the first message. If the determination is not to associate with the second entity 103 indicated by the identifier of the second entity 103, or if the first message does not include the identifier of the second entity 103, the first entity 102 will select a second entity for the first device 101 and send an association request for the first device 101 to the selected second entity 103.

[0240] For example, if the first message includes the identifier of the second entity, LMF#1, the first entity 102 may determine whether to select LMF#1 based on whether the first device 101 is within the service range of the second entity, LMF#1, and whether the second entity, LMF#1, meets the positioning requirements of the first device 101, such as Quality of Service (QoS) requirements. If LMF#1 is not selected, a second entity that meets the requirements may be reselected.

[0241] In some embodiments, if the first message does not include an identifier of the second entity 103 , the first entity 102 may select a suitable second entity 103 for the first device 101 by querying a network repository function (NRF) or according to local configuration.

[0242] In some embodiments, the name of the third message is not limited, and may be, for example, "Namf_Communication_N1MessageNotify" or the like.

[0243] In some embodiments, the third message is used to indicate that the first device requests to establish a PRU association and a user plane connection.

[0244] In some embodiments, the third message may include at least one of the following: the second indication information, the third indication information, the first capability information of the first device 101, the reason for PRU association, the positioning capability of the first device 101, the location information of the first device 101, the power state of the first device 101, and the second protocol identifier. The specific implementation of the third message refers to the description of the optional implementation of step S2103 and is not repeated here.

[0245] In some embodiments, the second entity 103 receives the third message sent by the first entity 102 .

[0246] In some embodiments, the first entity 102 sends a third message to the second entity 103 .

[0247] Optionally, the second entity 103 may send a response message to the third message to the first entity 102 to indicate that the second entity 103 has received the third message.

[0248] In some embodiments, the second entity 103 does not send a response message to the third message to the first entity 102 , which implicitly indicates that the second entity 103 agrees to the association request and user plane connection establishment request of the first device 101 .

[0249] In some embodiments, the second entity 103 does not send a response message to the third message to the first entity 102 , which implicitly indicates that the second entity 103 rejects the association request and user plane connection establishment request of the first device 101 .

[0250] Step S2106 : The second entity 103 determines whether to use user plane positioning.

[0251] In some embodiments, the second entity 103 can determine whether to use user plane positioning and / or whether the user plane positioning requested by the PRU is reasonable based on one or more of the third indication information, the first capability information of the first device 101, the second capability information of the second entity 103, the third policy, the status of the first entity 102, the type of positioning plane last used by the first device 101, and the second protocol identifier.

[0252] Among them, the specific implementation methods of the second indication information, the third indication information, the first capability information of the first device 101, and the second capability information of the second entity 103 can refer to the relevant description of the optional implementation method of step S2101, and will not be repeated here.

[0253] In some embodiments, the third policy may be a locally preset policy, or may be a policy configured by a PCF network element, etc., which is not limited in this disclosure.

[0254] In some embodiments, if the first device 101 only supports user plane positioning in the first capability information of the first device 101, or the second entity 103 only supports user plane positioning in the second capability information of the second entity 103, or the first entity 102 is in a congested state, or the priority of supporting the user plane in the third strategy of the second entity 103 is higher, or the type of the positioning plane last used by the first device 101 is the user plane type, then the second entity 103 can determine to use user plane positioning.

[0255] In some embodiments, the second entity 103 may also determine whether to use user plane positioning based on multiple items including the first capability information of the first device 101, the second capability information of the second entity 103, the third policy, the status of the first entity 102, and the type of positioning plane last used by the first device 101.

[0256] In some embodiments, if the second entity 103 determines to use user plane positioning, the subsequent association process and user plane connection establishment process may be performed. If it is determined to use control plane positioning, the subsequent positioning of the PRU and LMF needs to use control plane positioning.

[0257] Step S2107 : When determining to use user plane positioning, the second entity 103 determines the fifth protocol on which the current user plane positioning is based.

[0258] In some embodiments, the second entity 103 can determine whether to use the user plane protocol indicated by the second protocol identifier as the fifth protocol on which the current user plane positioning is based based on the second protocol identifier, and one or more of the first capability information of the first device 101, the second capability information of the second entity 103, the second protocol identifier, the fourth policy, and the first protocol on which the first device 101 last used user plane positioning.

[0259] In some embodiments, when the second entity 103 refuses to perform positioning based on the second protocol, the second entity 103 may re-determine the fifth protocol on which the current user plane positioning is based based on one or more of the first capability information of the first device 101, the second capability information of the second entity 103, the second protocol identifier, the fourth policy, and the first protocol on which the first device 101 last used user plane positioning.

[0260] In some embodiments, the fourth policy may be a locally preset policy, or may be a policy configured by a PCF network element, etc., which is not limited in this disclosure.

[0261] In some embodiments, the fifth protocol may include at least one of the SUPL protocol and the LCS-UPP protocol. The specific implementation of the fifth protocol refers to the description of the optional implementation of step S2101, which will not be repeated here.

[0262] In some embodiments, when determining the fifth protocol based on which user plane positioning is performed based on the first protocol based on which the first device 101 last used user plane positioning, the fifth protocol is the same as the first protocol. For example, if the first protocol based on which the first device 101 last used user plane positioning was the SUPL protocol, it may be determined that the fifth protocol based on which the current user plane positioning is performed is also the SUPL protocol.

[0263] Step S2108 : The second entity 103 sends a fourth message to the first entity 102 .

[0264] In some embodiments, the name of the fourth message is not limited, and may be, for example, "Namf_Communication_N1N2MessageTransfer" or the like.

[0265] In some embodiments, the fourth message includes the identifier of the second entity 103 and the first indication information.

[0266] In some embodiments, the first indication information is used to indicate whether to allow establishment of PRU association.

[0267] In some embodiments, the first indication information indicates that establishment of the PRU association is allowed, and the fourth message further includes user plane information, which may include at least one of the following: an address of the second entity 103, and a fifth protocol identifier based on user plane positioning.

[0268] In some embodiments, the identifier of the second entity 103 may be, for example, a “Correlation ID”.

[0269] In some embodiments, the address of the second entity 103 may be an Internet Protocol (IP) address of the second entity 103 , or may be a Fully Qualified Domain Name (FQDN) of the second entity 103 , etc., which is not limited in the present disclosure.

[0270] In some embodiments, the fifth protocol identifier is used to indicate the protocol selected by the second entity 103 . The fifth protocol may be identified in any implementation form, which is not limited in this disclosure.

[0271] In some embodiments, when the fourth message does not include the fifth protocol identifier, it may implicitly indicate that the fifth protocol identifier based on which the user plane positioning determined by the second entity 103 is based is the same as the second protocol identifier based on which the user plane positioning determined by the first device 101 is based.

[0272] In some embodiments, the first entity 102 receives a fourth message sent by the second entity 103 .

[0273] Step S2109 : The first entity 102 sends a second message to the first device 101 .

[0274] In some embodiments, the name of the second message is not limited, and it can be, for example, "DL NAS TRANSPORT message" or the like.

[0275] In some embodiments, the second message includes an identifier of the second entity 103 and the first indication information.

[0276] In some embodiments, the identifier of the second entity 103 may be, for example, a “Routing ID”.

[0277] In some embodiments, the first indication information indicates that establishment of the PRU association is permitted, and the second message further includes user plane information, where the user plane information includes at least one of the following: an address of the second entity 103, and a fifth protocol identifier based on user plane positioning. A specific implementation of the user plane information is described with reference to the description of the optional implementation of step S2106 and is not repeated here.

[0278] In some embodiments, the first device 101 receives the second message sent by the first entity 102 .

[0279] In some embodiments, after receiving the second message, the first device 101 may store the identifier (Routing ID) of the second entity 103 for subsequent association updates with the second entity 103. The Routing ID may overwrite the identifier of the second entity 103 used in the previous association update.

[0280] Step S2110 : The first device 101 establishes a user plane connection with the second entity 103 based on the user plane information.

[0281] In some embodiments, after receiving the second message sent by the first entity 102 , the first device 101 may establish a user plane connection with the second entity 103 based on the user plane information.

[0282] In some embodiments, when the first device 101 establishes a user plane connection with the second entity 103 based on the user plane information, if the protocol selected by the second entity 103 for the user plane connection is different from the protocol selected by the first device 101, the second entity 103 has a higher priority than the first device 101. In this case, the first device 101 will establish the user plane connection based on the protocol selected by the second entity 103. If an error occurs during the user plane connection establishment process, the first device 101 can report the error information to the second entity 103, and the second entity 103 will then reselect the protocol based on the user plane connection.

[0283] In step S2111 , the first device 101 and the second entity 103 complete PRU association.

[0284] The connection establishment method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2111. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, and steps S2101+S2103 may be implemented as independent embodiments, but are not limited thereto.

[0285] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0286] In the embodiment of the present disclosure, after the first device determines that it is a PRU and determines to use user plane positioning, it initiates a PRU association request and a user plane connection establishment request to the second entity through the first entity. After the second entity determines that the PRU association can be established; and when it determines to use user plane positioning, it returns a PRU association response and user plane information to the first device through the first entity to establish a PRU association and user plane connection with the first device. As a result, the first device requests a user plane connection with the second entity at the same time during the process of initiating the PRU association request, thereby improving the flexibility of establishing the user plane connection and improving the efficiency of information exchange.

[0287] FIG3A is a flow chart of a connection establishment method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a connection establishment method for a first device 101, the method comprising:

[0288] Step S3101: When the PRU is determined to be a PRU, determine whether to use user plane positioning.

[0289] Step S3102: When it is determined that user plane positioning is used, a second protocol based on which the current user plane positioning is based is determined.

[0290] Step S3103: Send a first message to the first entity 102.

[0291] In some embodiments, the first message is used to request establishment of a PRU association and to request establishment of a user plane connection with the second entity 103 .

[0292] In some embodiments, the first device 101 sends a first message to the first entity 102 .

[0293] Step S3104: Receive the second message sent by the first entity 102.

[0294] In some embodiments, the second message includes an identifier of the second entity 103 and first indication information, where the first indication information is used to indicate whether to allow establishment of the PRU association.

[0295] In some embodiments, the first indication information indicates that establishment of the PRU association is allowed, and the second message further includes user plane information.

[0296] In some embodiments, the first device 101 receives the second message sent by the first entity 102 .

[0297] Step S3105: Establish a user plane connection with the second entity 103 based on the user plane information.

[0298] For a detailed description of steps S3101-S3105, please refer to the detailed description in the embodiment shown in FIG2, which will not be repeated here.

[0299] The connection establishment method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3105. For example, steps S3101+S3102 may be implemented as independent embodiments, and step S3103 may be implemented as an independent embodiment, etc., but the present invention is not limited thereto.

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

[0301] In an embodiment of the present disclosure, when the first device acts as a PRU and initiates a PRU association request, when it determines to use user plane positioning, after sending an association request and a user plane connection establishment request to the second entity through the first entity, if the first device receives user plane information returned by the first entity, the first device can establish a user plane connection with the second entity based on the user plane information, thereby improving the efficiency of information interaction.

[0302] FIG3B is a flow chart of a connection establishment method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a connection establishment method for a first device 101, the method comprising:

[0303] Step S3201: Send a first message to the first entity 102.

[0304] In some embodiments, the first device 101 sends a first message to the first entity 102 .

[0305] In some embodiments, the first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, an identifier of the second entity, a reason for PRU association, positioning capability of the first device, location information of the first device, a switch status of the first device, and a second protocol identifier on which user plane positioning is based.

[0306] In some embodiments, sending a first message to a first entity includes:

[0307] Determine to use user plane positioning, and send a first message to the first entity.

[0308] In some embodiments, determining to use user plane positioning includes:

[0309] Determining to use user plane positioning based on one or more of first capability information of the first device, second capability information of the second entity, a first policy, a state of the first entity, and a type of a last used positioning plane.

[0310] In some embodiments, after determining to use the user plane for positioning, the method further includes:

[0311] The second protocol based on the current user plane positioning is determined based on one or more of the first capability information of the first device, the second capability information of the second entity, the second policy, and the first protocol based on which the last user plane positioning was performed.

[0312] In some embodiments, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device;

[0313] The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

[0314] Step S3202: Receive a second message sent by the first entity 102.

[0315] In some embodiments, the second message includes an identifier of the second entity 103 and first indication information, where the first indication information is used to indicate whether to allow establishment of the PRU association.

[0316] In some embodiments, the first indication information indicates that establishment of the PRU association is allowed, and the second message further includes user plane information, which includes at least one of the following: an address of the second entity, and a fifth protocol identifier based on user plane positioning.

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

[0318] A user plane connection is established with the second entity based on the user plane information.

[0319] For a detailed description of steps S3201 - S3202 , please refer to the above embodiment description.

[0320] The connection establishment method involved in the embodiments of the present disclosure may include at least one of steps S3201 and S3202. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, and steps S3201+S3202 may be implemented as independent embodiments, but are not limited thereto.

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

[0322] In the embodiment of the present disclosure, when the first device initiates a PRU association request, it initiates a user plane connection establishment request to the second entity when determining to use user plane positioning, thereby enriching the triggering conditions for user plane connection establishment and improving the efficiency of user plane connection establishment.

[0323] FIG4A is a flow chart of a connection establishment method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a connection establishment method for a first entity 102, the method comprising:

[0324] Step S4101: Receive a first message sent by the first device 101.

[0325] Step S4102: Check whether the first device 101 is a PRU.

[0326] Step S4103 : Determine the second entity 103 associated with the first device 101 .

[0327] Step S4104: When it is determined that the first device 101 is a PRU, a third message is sent to the second entity 103.

[0328] Step S4105: Receive the fourth message sent by the second entity 103.

[0329] Step S4106: Send a second message to the first device 101.

[0330] For a detailed description of steps S4101-S4106, please refer to the detailed description of the above embodiments, which will not be repeated here.

[0331] The connection establishment method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4106. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, and steps S4101+S4102 may be implemented as independent embodiments, but are not limited thereto.

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

[0333] In an embodiment of the present disclosure, after receiving the PRU association request and user plane connection establishment request of the first device, the first entity forwards the PRU association request and user plane connection establishment request of the first device to the second entity when determining that the first device is a PRU and determining the second entity associated with the first device. Then, after receiving the PRU association response and user plane information sent by the second entity, it forwards them to the first device, thereby ensuring the security and stability of the user plane connection establishment.

[0334] FIG4B is a flow chart of a connection establishment method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a connection establishment method for a first entity 102, the method comprising:

[0335] Step S4201: Receive a first message sent by the first device 101.

[0336] In some embodiments, the first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with the second entity, first capability information of the first device, an identifier of the second entity, a reason for PRU association, positioning capability of the first device, location information of the first device, a switch state of the first device, and a second protocol identifier on which user plane positioning is based;

[0337] In some embodiments, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device.

[0338] Step S4202: Send a third message to the second entity 103.

[0339] In some embodiments, the third message includes at least one of the following: second indication information, third indication information, first capability information of the first device, reason for PRU association, positioning capability of the first device, first device location information, switch status of the first device, and second protocol identifier.

[0340] In some embodiments, sending a third message to the second entity includes:

[0341] Verifying whether the first device is a PRU;

[0342] It is determined that the first device is a PRU, and the second entity sends a third message.

[0343] Step S4203: Receive a fourth message sent by the second entity 103.

[0344] The fourth message includes the identifier of the second entity and the first indication information.

[0345] In some embodiments, the first indication information indicates that establishment of the PRU association is allowed, and the fourth message further includes user plane information, which includes at least one of the following: an address of the second entity, and a fifth protocol identifier on which user plane positioning is based.

[0346] Step S4204: Send a second message to the first device 101.

[0347] For a detailed description of steps S4201-S4204, please refer to the detailed description of the above embodiments, which will not be repeated here.

[0348] The connection establishment method involved in the embodiment of the present disclosure may include at least one of steps S4201 to S4204. For example, steps S4201+S4202 may be implemented as independent embodiments, and steps S4201+S4202+S4203+S4204 may be implemented as independent embodiments, but are not limited thereto.

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

[0350] In the disclosed embodiment, the first entity first forwards the association request and user plane connection establishment request of the first device to the second entity, and then forwards the PRU association response and user plane information of the second entity to the first device, thereby ensuring the security of information interaction.

[0351] FIG5A is a flow chart of a connection establishment method according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a connection establishment method for a second entity 103, the method comprising:

[0352] Step S5101: Receive a third message sent by the first entity 102.

[0353] In some embodiments, the third message is used to indicate that the first device requests to establish a PRU association and a user plane connection.

[0354] Step S5102: Determine whether to use user plane positioning.

[0355] Step S5103: When it is determined that user plane positioning is used, determine the fifth protocol on which the current user plane positioning is based.

[0356] Step S5104: Send a fourth message to the first entity 102.

[0357] In some embodiments, the fourth message includes an identifier of the second entity and first indication information, where the first indication information is used to indicate whether establishment of the PRU association is allowed.

[0358] In some embodiments, the first indication information indicates that establishment of the PRU association is allowed, and the fourth message further includes user plane information.

[0359] For a detailed description of steps S5101 - S5104 , please refer to the above embodiment description.

[0360] The connection establishment method involved in the embodiments of the present disclosure may include at least one of steps S5101 to S5104. For example, step S5101 may be implemented as an independent embodiment, step S5102 may be implemented as an independent embodiment, and steps S5101+S5104 may be implemented as independent embodiments, but are not limited thereto.

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

[0362] In an embodiment of the present disclosure, after receiving the association request of the first device and the user plane connection establishment request forwarded by the first entity, the second entity determines the protocol and user plane information on which the user plane positioning is based when determining to use user plane positioning, and finally sends a PRU association response and user plane information to the first entity, thereby improving the flexibility of establishing the user plane connection.

[0363] FIG5B is a flow chart of a connection establishment method according to an embodiment of the present disclosure. As shown in FIG5B , the embodiment of the present disclosure relates to a connection establishment method for the second entity 103, the method comprising:

[0364] Step S5201: Receive a third message sent by the first entity 102.

[0365] In some embodiments, the third message is used to indicate that the first device requests to establish a PRU association and a user plane connection.

[0366] In some embodiments, the third message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, the reason for PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier on which the user plane positioning is based.

[0367] Step S5202: Send a fourth message to the first entity 102.

[0368] In some embodiments, the fourth message includes an identifier of the second entity and first indication information, where the first indication information is used to indicate whether establishment of the PRU association is allowed.

[0369] In some embodiments, the identifier of the second entity 103 may be, for example, a “Correlation ID”.

[0370] In some embodiments, the first indication information indicates that establishment of the PRU association is allowed, and the fourth message further includes user plane information, which includes at least one of the following: an address of the second entity, and a fifth protocol identifier on which user plane positioning is based.

[0371] In some embodiments, before sending the fourth message to the first entity, the method further includes:

[0372] Determining to use user plane positioning. In some embodiments, determining to use user plane positioning includes:

[0373] Determine to use user plane positioning based on one or more of the third indication information, the first capability information of the first device, the second capability information of the second entity, the third policy, the status of the first entity, the type of positioning plane last used by the first device, and the second protocol identifier.

[0374] In some embodiments, after determining to use user plane positioning, the method further includes:

[0375] Refuse to perform positioning based on the second protocol on which the user plane positioning contained in the third message is based, and determine the fifth protocol on which the current user plane positioning is based based on one or more of the first capability information of the first device, the second capability information of the second entity, the second protocol identifier, the fourth strategy, and the first protocol on which the first device last used user plane positioning.

[0376] In some embodiments, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device;

[0377] The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

[0378] In some embodiments, after receiving the third message sent by the first entity, the method further includes:

[0379] Based on the fifth protocol identifier, a user plane connection is established with the first device.

[0380] For a detailed description of steps S5201 - S5202 , please refer to the above embodiment description.

[0381] The connection establishment method involved in the embodiments of the present disclosure may include at least one of steps S5201 and S5202. For example, step S5201 may be implemented as an independent embodiment, step S5202 may be implemented as an independent embodiment, and steps S5201+S5202 may be implemented as independent embodiments, but are not limited thereto.

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

[0383] In an embodiment of the present disclosure, the second entity sends an association response and user plane information to the first entity based on the PRU association request and user plane connection establishment request of the first device, when it is determined to use user plane positioning, thereby enriching the triggering conditions for establishing the user plane connection.

[0384] FIG6 is an interactive diagram of a connection establishment method according to an embodiment of the present disclosure. As shown in FIG6 , an embodiment of the present disclosure relates to a connection establishment method for a communication system including a first device, a first entity, and a second entity, the method comprising:

[0385] Step S6101: The first device 101 sends a first message to the first entity 102.

[0386] In some embodiments, the first message is used to request establishment of a PRU association and to request establishment of a user plane connection with the second entity.

[0387] Step S6102 : The first entity 102 sends a third message to the second entity 103 .

[0388] In some embodiments, the third message is used to indicate that the first device 101 requests to establish a PRU association and a user plane connection.

[0389] Step S6103 : The second entity 103 sends a fourth message to the first entity 102 .

[0390] In some embodiments, the fourth message includes an identifier of the second entity and first indication information, where the first indication information is used to indicate whether to allow establishment of the PRU association.

[0391] In some embodiments, the identifier of the second entity may be, for example, a "Correlation ID".

[0392] The first indication information indicates that establishment of the PRU association is allowed, and the fourth message also includes user plane information.

[0393] Step S6104 : The first entity 102 sends a second message to the first device 101 .

[0394] In some embodiments, the second message includes an identifier of the second entity 103 and the first indication information.

[0395] In some embodiments, the identifier of the second entity may be, for example, a "Routing ID".

[0396] In some embodiments, the first indication information indicates that establishment of the PRU association is allowed, and the second message further includes user plane information.

[0397] For a detailed description of steps S6101 - S6104 , please refer to the above embodiment description.

[0398] In an embodiment of the present disclosure, when the first device acts as a PRU and determines to use user plane positioning, after initiating a PRU association request and a user plane connection establishment request to the second entity through the first entity, the second entity, when determining that a PRU association can be established and determining to use user plane positioning, can return a PRU association response and user plane information to the first device through the first entity to establish a PRU association and user plane connection with the first device, thereby ensuring the stability and security of the user plane connection establishment.

[0399] The following is an exemplary introduction to the above method.

[0400] The present disclosure is used to solve the problem of how to initiate the establishment of a user plane connection while executing a Positioning Reference Unit (PRU) association process. The optional implementation solutions are as follows:

[0401] As shown in Figure 7, Figure 7 is an interactive schematic diagram of a connection establishment method according to an embodiment of the present disclosure. The embodiment of the present disclosure involves a connection establishment method taking the UE as a PRU, the first entity as an AMF, and the second entity as an LMF as an example. The method includes:

[0402] It should be noted that in the following steps, Correlation ID and Routing ID are different names (or terms) for the same identifier. "Correlation ID" is the identifier used between the AMF and LMF to identify the LMF, while "Routing ID" is the identifier used to identify the LMF in the Non-Access-Stratum (NAS) message between the PRU and the AMF.

[0403] 1. If the UE as the PRU is in the Connection Management IDLE (CM_IDLE) state, the PRU executes the UE-triggered Service Request. If the UE is in the CM_CONNECTED (CM connected) state, this step is skipped.

[0404] 2. The PRU decides to perform the PRU association procedure and decides whether to use the user plane or control plane for positioning. If the PRU decides to use user plane positioning, it performs subsequent operations. For example, the PRU further determines the protocol to use for user plane positioning. The PRU can also trigger the UE-initiated user plane connection establishment procedure at the same time as the PRU association procedure.

[0405] The PRU decides whether to use the control plane or the user plane based on the capabilities of the PRU and LMF (i.e., whether user plane or control plane positioning is supported, whether the SUPL protocol and LCS-UPP protocol for user plane positioning are supported), local policies or policies provided by the PCF, and the previous plane type used for PRU positioning.

[0406] The PRU further determines a user plane protocol (e.g., SUPL or LCS-UPP) for the user plane. The PRU may also select a protocol for user plane positioning based on the capabilities of the PRU and LMF (e.g., the capability to support SUPL or the capability to support LCS-UPP), local policies or policies provided by the PCF, and one or more of the protocols based on which the previous user plane positioning was performed.

[0407] 3. The PRU executes the user plane connection establishment process initiated by the UE during the PRU association process.

[0408] The PRU can send the LMF identifier (e.g., Routing ID), PRU association request, user plane indication, PRU indication, and protocol indication to the AMF. The user plane indication indicates that the PRU is trying to establish a user plane connection. The PRU indication indicates that the UE is a PRU. The protocol indication is used to indicate the selected user plane positioning protocol, which can be SUPL or LCS-UPP. The user plane indication, PRU indication, and protocol indication can be encapsulated in the user plane information container or additional information information unit (Information Element, IE) of the uplink non-access stratum transport (UpLink Non-Access Stratum TRANSPORT, UL NAS TRANSPORT) message, or can also be transmitted in other messages, such as a service request message. In addition, the PRU can send the PRU association request and Routing ID in the location service (LoCation Services, LCS) container of the UL NAS transport message.

[0409] 4.AMF uses the subscription information from the UDM to verify whether the sender of the PRU association request is the PRU. If the use of user plane positioning is authorized based on the UE subscription information and the message contains the Routing ID, the AMF further checks whether the PRU is capable of establishing a user plane session. If the message does not contain the Routing ID, or the LMF indicated by the Routing ID cannot establish a user plane session with the PRU, the AMF can reselect an LMF for the PRU. The AMF can query the Network Repository Function (NRF) or discover and select a suitable LMF based on local configuration.

[0410] 5.AMF transmits the PRU association request, user plane indication, PRU indication and protocol indication to LMF. Some or all of the above parameters can be transmitted to LMF using Namf_Communication_N1MessageNotify message or Nlmf_Location_UPConfig request message.

[0411] 6. If the LMF accepts association with the PRU, the LMF returns a PRU Association Accept as a supplementary services message. For example, the LMF returns the PRU Association Accept and the LMF's identifier (e.g., Correlation ID) to the AMF via Namf_Communication_N1N2MessageTransfer. Otherwise, the LMF returns a PRU Association Reject and indicates the reason for the rejection. If the LMF accepts positioning using the user plane and the protocol selected by the PRU, and a secure user plane connection is not established between the UE and the LMF, the LMF sends user plane information to the AMF, indicating that the PRU accepts PRU association and uses the user plane for positioning. If the LMF accepts positioning using the user plane but rejects positioning using the protocol selected by the PRU, the LMF may select another protocol for the PRU and indicate this protocol in the user plane information. The user plane information includes the LMF's address, security-related information, and the protocol based on which the reselected user plane positioning is based. Otherwise, the LMF returns an indication of rejecting the PRU user plane positioning and the reason for the rejection.

[0412] 7. The AMF forwards the PRU Association Response, the Routing ID corresponding to the Correlation ID, and the user plane information to the PRU in a Downlink Non-Access Stratum Transport (DL NAS TRANSPORTL) message. The PRU stores the Routing ID for future PRU association updates with the serving LMF. This Routing ID may overwrite any Routing ID used in a previous association update (if any).

[0413] 8. Execute the steps initiated by the UE to establish a user plane connection and complete the user plane connection between the PRU and the LMF.

[0414] 9. The PRU uses the selected LMF for user plane or control plane positioning.

[0415] 10. The PRU and LMF complete the association operation.

[0416] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a first entity (e.g., a RAN) in any of the above methods.

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

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

[0419] FIG8A is a schematic diagram of the structure of the first device 101 proposed in an embodiment of the present disclosure. As shown in FIG8A , the first device 8100 may include: at least one of a transceiver module 8101 and a processing module 8102. The first device 8100 may include:

[0420] The transceiver module 8101 is configured to send a first message to the first entity, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with the second entity;

[0421] The transceiver module 8102 is further configured to receive a second message sent by the first entity, where the second message includes an identifier of the second entity and first indication information, and the first indication information is configured to indicate whether to allow the PRU association to be established.

[0422] Optionally, the transceiver module 8101 is further configured to:

[0423] Determine to use user plane positioning, and send the first message to the first entity.

[0424] Optionally, it also includes:

[0425] The processing module 8102 is configured to determine to use user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, the first policy, the state of the first entity, and the type of the last used positioning plane.

[0426] Optionally, the processing module 8102 is further configured to:

[0427] The second protocol based on the current user plane positioning is determined based on one or more of the first capability information of the first device, the second capability information of the second entity, the second policy, and the first protocol based on which the last user plane positioning was performed.

[0428] Optionally, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device;

[0429] The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

[0430] Optionally, the processing module 8102 is further configured to:

[0431] Based on the user plane information, a user plane connection is established with the second entity, wherein the first indication information indicates that establishment of the PRU association is allowed, and the second message further includes the user plane information.

[0432] Optionally, the first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, an identifier of the second entity, a reason for PRU association, positioning capability of the first device, location information of the first device, a switch status of the first device, and a second protocol identifier on which user plane positioning is based.

[0433] Optionally, the first indication information indicates that establishment of the PRU association is allowed, and the second message further includes user plane information, and the user plane information includes at least one of the following: an address of the second entity, and a fifth protocol identifier on which user plane positioning is based.

[0434] FIG8B is a schematic diagram of the structure of the first entity 102 proposed in an embodiment of the present disclosure. As shown in FIG8B , the first entity 8200 may include at least one of a transceiver module 8201 and a processing module 8202. The first entity 8200 may include:

[0435] The transceiver module 8201 is configured to receive a first message sent by a first device, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection between a second entity;

[0436] The transceiver module 8201 is further configured to send a third message to the second entity, wherein the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0437] The transceiver module 8201 is further configured to receive a fourth message sent by the second entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow establishment of the PRU association;

[0438] The transceiver module 8201 is further configured to send a second message to the first device, wherein the second message includes an identifier of the second entity and the first indication information.

[0439] Optionally, the transceiver module 8201 further includes:

[0440] The processing module 8202 is configured to verify whether the first device is a PRU;

[0441] The transceiver module 8201 is configured to determine that the first device is a PRU and send a third message to the second entity.

[0442] Optionally, the first message includes at least one of the following: second indication information used to indicate that the first device is a PRU, third indication information used to indicate establishment of a user plane connection with the second entity, first capability information of the first device, an identifier of the second entity, a reason for PRU association, a positioning capability of the first device, location information of the first device, a switch state of the first device, and a second protocol identifier on which user plane positioning is based;

[0443] The third message includes at least one of the following: the second indication information, the third indication information, the first capability information of the first device, the reason for PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier.

[0444] Optionally, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device.

[0445] Optionally, the first indication information indicates that establishment of a PRU association is allowed, and the fourth message and the second message also include user plane information, and the user plane information includes at least one of the following: the address of the second entity, and a fifth protocol identifier on which the user plane positioning is based.

[0446] FIG8C is a schematic diagram of the structure of the second entity 103 proposed in an embodiment of the present disclosure. As shown in FIG8B , the second entity 8300 may include at least one of a transceiver module 8301 and a processing module 8302. The second entity 8300 may include:

[0447] The transceiver module 8301 is configured to receive a third message sent by the first entity, where the third message is used to instruct the first device to request to establish a PRU association and a user plane connection;

[0448] The transceiver module 8301 is further configured to send a fourth message to the first entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is configured to indicate whether establishment of the PRU association is allowed.

[0449] Optionally, it also includes:

[0450] The processing module 8302 is configured to determine whether to use user plane positioning.

[0451] Optionally, the processing module 8302 is further configured to:

[0452] Determine to use user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, the third policy, the state of the first entity, and the type of positioning plane last used by the first device.

[0453] Optionally, the processing module 8302 is further configured to:

[0454] Refuse to perform positioning based on the second protocol on which the user plane positioning contained in the third message is based, and determine the fifth protocol on which the current user plane positioning is based based on one or more of the first capability information of the first device, the second capability information of the second entity, the second protocol identifier, the fourth strategy, and the first protocol on which the first device last used user plane positioning.

[0455] Optionally, the first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device;

[0456] The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

[0457] Optionally, the third message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, the reason for PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier on which the user plane positioning is based.

[0458] Optionally, the first indication information indicates that establishment of the PRU association is allowed, and the fourth message further includes user plane information, and the user plane information includes at least one of the following: the address of the second entity, and a fifth protocol identifier on which the user plane positioning is based.

[0459] Optionally, the processing module 8302 is further configured to:

[0460] Based on the fifth protocol identifier, a user plane connection is established with the first device.

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

[0462] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0463] Figure 9A is a schematic diagram of the structure of a communication device 9100 proposed in an embodiment of the present disclosure. Communication device 9100 can be a first device, a first entity, or a second entity. It can also be a chip, chip system, or processor that supports the first device to implement any of the above methods. It can also be a chip, chip system, or processor that supports the first entity to implement any of the above methods. It can also be a chip, chip system, or processor that supports the second entity to implement any of the above methods. Communication device 9100 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.

[0464] As shown in Figure 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 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 the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 9100 is used to perform any of the above methods.

[0465] In some embodiments, the communication device 9100 further includes one or more memories 9102 for storing instructions. Optionally, all or part of the memories 9102 may be located outside the communication device 9100.

[0466] In some embodiments, the communication device 9100 further includes one or more transceivers 9103. When the communication device 9100 includes one or more transceivers 9103, the transceiver 9103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2103, step S2105, step S2109, step S2110, but not limited thereto), and the processor 9101 performs the other steps (for example, step S2101, step S2102, step S2104, step S2106, step S2107, step S2108, step S2111).

[0467] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0468] In some embodiments, the communication device 9100 may include one or more interface circuits 9104. Optionally, the interface circuit 9104 is connected to the memory 9102. The interface circuit 9104 may be configured to receive signals from the memory 9102 or other devices, and may be configured to send signals to the memory 9102 or other devices. For example, the interface circuit 9104 may read instructions stored in the memory 9102 and send the instructions to the processor 9101.

[0469] The communication device 9100 described in the above embodiments may be a terminal or a first entity or a second entity, but the scope of the communication device 9100 described in the present disclosure is not limited thereto, and the structure of the communication device 9100 may not be limited by FIG. 9A . 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.

[0470] 9B is a schematic diagram of the structure of a chip 9200 according to an embodiment of the present disclosure. If the communication device 9100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 9200 shown in FIG9B , but the present disclosure is not limited thereto.

[0471] The chip 9200 includes one or more processors 9201 , and the chip 9200 is configured to execute any of the above methods.

[0472] In some embodiments, the chip 9200 further includes one or more interface circuits 9202. Optionally, the interface circuit 9202 is connected to the memory 9203. The interface circuit 9202 can be used to receive signals from the memory 9203 or other devices, and can be used to send signals to the memory 9203 or other devices. For example, the interface circuit 9202 can read instructions stored in the memory 9203 and send the instructions to the processor 9201.

[0473] In some embodiments, the interface circuit 9202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2103, step S2105, step S2109, step S2110, but not limited to this), and the processor 9201 executes other steps (for example, step S2101, step S2102, step S2104, step S2106, step S2107, step S2108, step S2111).

[0474] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0475] In some embodiments, the chip 9200 further includes one or more memories 9203 for storing instructions. Alternatively, all or part of the memories 9203 may be located outside the chip 9200.

[0476] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 9100, causes the communication device 9100 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 temporary storage medium.

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

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

Claims

1. A connection establishment method, characterized in that: The method is performed by a first device, and includes: Sending a first message to the first entity, wherein the first message is used to request establishment of a PRU association and request establishment of a user plane connection with the second entity; A second message sent by the first entity is received, where the second message includes an identifier of the second entity and first indication information, where the first indication information is used to indicate whether establishment of the PRU association is allowed.

2. The method according to claim 1, characterized in that The sending a first message to the first entity includes: Determine to use user plane positioning, and send the first message to the first entity.

3. The method according to claim 2, characterized in that: The determining to use user plane positioning includes: Based on one or more of the first capability information of the first device, the second capability information of the second entity, a first policy, a state of the first entity, and a type of the last used positioning plane, it is determined to use the user plane for positioning.

4. The method according to claim 3, characterized in that The method further comprises: Determine a second protocol based on current user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, a second policy, and a first protocol based on which the last user plane positioning was based.

5. The method according to claim 3 or 4, characterized in that The first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device; The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Based on the user plane information, a user plane connection is established with the second entity, wherein the first indication information indicates that establishment of a PRU association is allowed, and the second message further includes the user plane information.

7. The method according to claim 6, characterized in that The user plane information includes at least one of the following: an address of the second entity, and a fifth protocol identifier based on user plane positioning.

8. The method according to any one of claims 1 to 7, characterized in that: The first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, an identifier of the second entity, a reason for PRU association, a positioning capability of the first device, location information of the first device, a switch state of the first device, and a second protocol identifier on which user plane positioning is based.

9. A connection establishment method, characterized in that: The method is performed by a first entity, and comprises: Receiving a first message sent by a first device, wherein the first message is used to request to establish a PRU association and to request to establish a user plane connection with a second entity; Sending a third message to the second entity, wherein the third message is used to indicate that the first device requests to establish a PRU association and a user plane connection; receiving a fourth message sent by the second entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow establishment of the PRU association; Send a second message to the first device, wherein the second message includes an identifier of a second entity and the first indication information.

10. The method according to claim 9, characterized in that The sending a third message to the second entity includes: Verifying whether the first device is a PRU; Determine that the first device is a PRU, and send the third message to the second entity.

11. The method according to claim 9 or 10, characterized in that The first message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, an identifier of the second entity, a reason for associating the PRU, a positioning capability of the first device, location information of the first device, a switch state of the first device, and a second protocol identifier on which user plane positioning is based; The third message includes at least one of the following: the second indication information, the third indication information, the first capability information of the first device, the reason for the PRU association, the positioning capability of the first device, the location information of the first device, the switch status of the first device, and the second protocol identifier.

12. The method according to claim 11, characterized in that The first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device.

13. The method according to any one of claims 9 to 12, characterized in that: The first indication information indicates that establishment of a PRU association is allowed, and the second message also includes user plane information, and the user plane information includes at least one of the following: an address of the second entity, and a fifth protocol identifier on which user plane positioning is based.

14. A connection establishment method, characterized in that: The method is performed by a second entity, and the method includes: receiving a third message sent by the first entity, wherein the third message is used to indicate that the first device requests to establish a PRU association and a user plane connection; A fourth message is sent to the first entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow establishment of the PRU association.

15. The method according to claim 14, characterized in that The method further comprises: Determine to use user plane positioning.

16. The method according to claim 15, characterized in that The determining to use user plane positioning includes: Determine to use user plane positioning based on one or more of the first capability information of the first device, the second capability information of the second entity, a third policy, the state of the first entity, and the type of positioning plane last used by the first device.

17. The method according to claim 15 or 16, characterized in that The method further comprises: Refuse to perform positioning based on the second protocol on which the user plane positioning contained in the third message is based, and determine the fifth protocol on which the current user plane positioning is based based on one or more of the first capability information of the first device, the second capability information of the second entity, the second protocol identifier, the fourth strategy, and the first protocol on which the first device last used user plane positioning.

18. The method according to claim 16 or 17, characterized in that The first capability information includes at least one of the following: whether the first device supports user plane positioning, whether the first device supports control plane positioning, and a third protocol identifier of user plane positioning supported by the first device; The second capability information includes at least one of the following: whether the second entity supports user plane positioning, whether the second entity supports control plane positioning, and a fourth protocol identifier of user plane positioning supported by the second entity.

19. The method according to any one of claims 14 to 18, characterized in that: The third message includes at least one of the following: second indication information for indicating that the first device is a PRU, third indication information for indicating establishment of a user plane connection with a second entity, first capability information of the first device, the reason for the PRU association, the positioning capability of the first device, the location information of the first device, the switch state of the first device, and the second protocol identifier on which the user plane positioning is based.

20. The method according to any one of claims 14 to 19, characterized in that: The first indication information indicates that establishment of a PRU association is allowed, and the fourth message also includes user plane information, and the user plane information includes at least one of the following: an address of the second entity, and a fifth protocol identifier on which user plane positioning is based.

21. The method of claim 20, wherein: The method further comprises: Based on the fifth protocol identifier, a user plane connection is established with the first device.

22. A connection establishment method, characterized in that: Applied to a communication system, the method comprises: The first entity receives a first message sent by a first device, wherein the first message is used to request to establish a PRU association and request establishing a user plane connection with a second entity; The first entity sends a third message to the second entity, wherein the third message is used to indicate that the first device requests to establish a PRU association and a user plane connection; The second entity sends a fourth message to the first entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow establishment of the PRU association; The first entity sends a second message to the first device, wherein the second message includes an identifier of the second entity and the first indication information.

23. A first device, characterized in that: The first device comprises: A transceiver module, configured to send a first message to a first entity, wherein the first message is used to request to establish a PRU association and to request to establish a user plane connection with a second entity; The transceiver module is further used to receive a second message sent by the first entity, where the second message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow the PRU association to be established.

24. A first entity, characterized in that: The first entity comprises: A transceiver module, configured to receive a first message sent by a first device, wherein the first message is used to request to establish a PRU association and to request to establish a user plane connection with a second entity; The transceiver module is further used to send a third message to the second entity, wherein the third message is used to indicate that the first device requests to establish a PRU association and a user plane connection; The transceiver module is further used to receive a fourth message sent by the second entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow the PRU association to be established; The transceiver module is further used to send a second message to the first device, wherein the second message includes an identifier of the second entity and the first indication information.

25. A second entity, characterized in that: The second entity comprises: A transceiver module, configured to receive a third message sent by the first entity, wherein the third message is used to indicate that the first device requests to establish a PRU association and a user plane connection; The transceiver module is further used to send a fourth message to the first entity, wherein the fourth message includes an identifier of the second entity and first indication information, and the first indication information is used to indicate whether to allow the PRU association to be established.

26. A communication device, characterized in that: include: one or more processors; The processor is used to execute the connection establishment method described in any one of claims 1-21.

27. A communication system, characterized in that: The invention comprises a first entity and a second entity, wherein the first entity is configured to implement the connection establishment method according to any one of claims 9 to 13, and the second entity is configured to implement the connection establishment method according to any one of claims 14 to 21.

28. 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 connection establishment method according to any one of claims 1 to 21.

Images