Communication method and apparatus

Abstract

The present disclosure provides a communication method and apparatus. The method executed by a terminal comprises: receiving a first message sent by a first network device, wherein the first message is used for instructing to update a first user plane connection between the terminal and a source second network device to be a second user plane connection between the terminal and a target second network device, and the first message is used for instructing the terminal to establish the second user plane connection with the target second network device. In this way, the terminal can determine, on the basis of the first message for instructing the terminal to establish the second user plane connection with the target second network device, to update the first user plane connection between the terminal and the source second network device to be the second user plane connection between the terminal and the target second network device, and then update a session executed in the first user plane connection to be executed in the second user plane connection, thereby ensuring the accurate execution of the session, and improving communication performance.

Description

Communication methods and devices Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] With the continuous development of information technology, the use of terminals is becoming increasingly widespread. Terminals are mobile, and their location changes when they are in motion. In order to obtain location services, terminals can establish user plane connections with second network devices.

[0003] Summary of the Invention

[0004] This disclosure provides a communication method and apparatus for a terminal to determine whether to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, establish a second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, thereby ensuring the accurate execution of the session and improving communication performance.

[0005] This disclosure presents a communication method and apparatus.

[0006] According to a first aspect of the present disclosure, a communication method is proposed, executed by a terminal, comprising: receiving a first message sent by a first network device, wherein the first message is used to instruct the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message is used to instruct the terminal to establish a second user plane connection with the target second network device.

[0007] In the above embodiments, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, establish the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0008] According to a second aspect of the present disclosure, a communication method is provided, executed by a first network device, comprising: sending a first message to a terminal, wherein the first message is used to instruct the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message is used to instruct the terminal to establish a second user plane connection with the target second network device.

[0009] In the above embodiments, the first network device can instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, thereby establishing the second user plane connection between the terminal and the target second network device. This enables the session update executed by the terminal in the first user plane connection to be executed in the second user plane connection, ensuring the accurate execution of the session and improving communication performance.

[0010] According to a third aspect of the present disclosure, a communication method is provided, executed by a target second network device, comprising: sending a fourth message to a first network device, wherein the fourth message is used to instruct the first network device to send a first message to a terminal, the first message is used to instruct the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and the target second network device, the first message is used to instruct the terminal to establish a second user plane connection with the target second network device, and the fourth message includes a first identifier and a second identifier, the first identifier being an identifier of the target second network device, and the second identifier being an identifier of the source second network device.

[0011] In the above embodiments, the target second network device can instruct the first network device to send a first message to the terminal, instructing the terminal to update the first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device, thereby establishing a second user plane connection between the terminal and the target second network device. This enables the session update executed by the terminal in the first user plane connection to be executed in the second user plane connection, ensuring accurate execution of the session and improving communication performance.

[0012] According to a fourth aspect of the present disclosure, a communication method is provided, executed by a source second network device, comprising: receiving a seventh message sent by a first network device, wherein the seventh message is sent by the first network device after sending a first message to a terminal, the first message being used to indicate updating a first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and a target second network device, the first message being used to indicate that the terminal establishes a second user plane connection with the target second network device, and the seventh message being used to indicate that the source second network device releases the first user plane connection.

[0013] In the above embodiments, the source second network device can receive the seventh message sent by the first network device and release the first user plane connection with the terminal, so that the terminal can update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, establish the second user plane connection between the terminal and the target second network device, and then execute the first session update in the first user plane connection between the terminal and the source second network device in the second user plane connection between the terminal and the target second network device, which can ensure the accurate execution of the first session and improve communication performance.

[0014] According to a fifth aspect of the present disclosure, a communication method is proposed, comprising: a target second network device sending a fourth message to a first network device, wherein the fourth message is used to instruct the first network device to send a first message to a terminal, the first message being used to instruct the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and the target second network device, the first message being used to instruct the terminal to establish a second user plane connection with the target second network device, the fourth message including a first identifier and a second identifier, the second identifier being an identifier of the source second network device, and the first identifier being an identifier of the target second network device; the first network device sending the first message to the terminal; the terminal receiving the first message sent by the first network device; the first network device sending a seventh message to the source second network device, the seventh message being used to instruct the source second network device to release the first user plane connection; and the source second network device receiving the seventh message sent by the first network device.

[0015] In the above embodiments, the first session update in the first user plane connection between the terminal and the source second network device can be executed in the second user plane connection between the terminal and the target second network device, which can ensure the accurate execution of the first session and improve communication performance.

[0016] According to a sixth aspect of the present disclosure, a terminal is provided, comprising: a transceiver module, configured to receive a first message sent by a first network device, wherein the first message is configured to indicate updating a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message is configured to indicate that the terminal establishes a second user plane connection with the target second network device.

[0017] According to a seventh aspect of the present disclosure, a first network device is provided, comprising: a transceiver module configured to send a first message to a terminal, wherein the first message is configured to instruct the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message is configured to instruct the terminal to establish a second user plane connection with the target second network device.

[0018] According to an eighth aspect of the present disclosure, a target second network device is provided, comprising: a transceiver module configured to send a fourth message to a first network device, wherein the fourth message is configured to instruct the first network device to send a first message to a terminal, the first message is configured to instruct the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and the target second network device, the first message is configured to instruct the terminal to establish a second user plane connection with the target second network device, and the fourth message includes a first identifier and a second identifier, the first identifier being an identifier of the target second network device, and the second identifier being an identifier of the source second network device.

[0019] According to a ninth aspect of the present disclosure, a source second network device is provided, comprising: a transceiver module, configured to receive a seventh message sent by a first network device, wherein the seventh message is sent by the first network device after sending a first message to a terminal, the first message being configured to indicate updating a first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and a target second network device, the first message being configured to indicate that the terminal establishes a second user plane connection with the target second network device, and the seventh message being configured to indicate that the source second network device releases the first user plane connection.

[0020] According to a tenth aspect of the present disclosure, a terminal is provided, comprising: one or more processors, wherein the terminal is configured to perform the method described in the first aspect.

[0021] According to an eleventh aspect of the present disclosure, a first network device is provided, comprising: one or more processors, wherein the first network device is configured to perform the method described in the second aspect.

[0022] According to a twelfth aspect of the present disclosure, a target second network device is provided, comprising: one or more processors, wherein the target second network device is configured to perform the method described in the third aspect.

[0023] According to a thirteenth aspect of the present disclosure, a source second network device is provided, comprising: one or more processors, wherein the source second network device is configured to perform the method described in the fourth aspect.

[0024] According to a fourteenth aspect of the present disclosure, a communication device is provided, comprising: one or more processors; and a memory coupled to the processors, the memory storing instructions which, when executed by the processors, cause the communication device to perform the method as described in at least one of the first, second, third, and fourth aspects.

[0025] According to a fifteenth aspect of the present disclosure, a communication system is provided, comprising: a terminal, a first network device, a target second network device, and a source second network device; the terminal performs the method as described in the first aspect, the first network device performs the method as described in the second aspect embodiment, the target second network device performs the method as described in the third aspect embodiment, and the source second network device performs the method as described in the fourth aspect embodiment.

[0026] According to a sixteenth aspect of the present disclosure, a computer storage medium is provided, wherein the computer storage medium stores computer-executable instructions; when executed by a processor, the computer-executable instructions are capable of implementing the method described in at least one of the first, second, third, and fourth aspects.

[0027] According to a seventeenth aspect of the present disclosure, a computer program product is provided, wherein the computer program product stores a computer program; after being executed by a processor, the computer program is capable of implementing the method described in at least one of the first, second, third, and fourth aspects.

[0028] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0030] Figure 1A is an architecture diagram of a communication system provided in an embodiment of this disclosure;

[0031] Figure 1B is a schematic diagram of control plane message transmission between a terminal and a second network device according to an embodiment of this disclosure;

[0032] Figure 1C is a schematic diagram of user plane message transmission between a terminal and a second network device according to an embodiment of this disclosure;

[0033] Figure 2A is a flowchart of a communication method provided in an embodiment of this disclosure;

[0034] Figure 2B is a flowchart of a communication method provided in an embodiment of this disclosure;

[0035] Figure 3A is a flowchart of another communication method provided in an embodiment of this disclosure;

[0036] Figure 3B is a flowchart of another communication method provided in an embodiment of this disclosure;

[0037] Figure 3C is a flowchart of another communication method provided in an embodiment of this disclosure;

[0038] Figure 3D is a flowchart of another communication method provided in an embodiment of this disclosure;

[0039] Figure 3E is a flowchart of another communication method provided in an embodiment of this disclosure;

[0040] Figure 4A is a flowchart of a control plane connection update method between a terminal and a second network device provided in an embodiment of this disclosure;

[0041] Figure 4B is a flowchart of a user plane connection update method between a terminal and a second network device provided in an embodiment of this disclosure;

[0042] Figure 4C is a flowchart of another user plane connection update method between a terminal and a second network device provided in an embodiment of this disclosure;

[0043] Figure 4D is a flowchart of another communication method provided in an embodiment of this disclosure;

[0044] Figure 5A is a structural diagram of a terminal provided in an embodiment of this disclosure;

[0045] Figure 5B is a structural diagram of a first network device provided in an embodiment of this disclosure;

[0046] Figure 5C is a structural diagram of a target second network device provided in an embodiment of this disclosure;

[0047] Figure 5D is a structural diagram of a source second network device provided in an embodiment of this disclosure;

[0048] Figure 6A is a structural diagram of a communication device provided in an embodiment of this disclosure;

[0049] Figure 6B is a structural diagram of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0050] This disclosure presents a communication method and apparatus.

[0051] In a first aspect, embodiments of this disclosure propose a communication method executed by a terminal, comprising: receiving a first message sent by a first network device, wherein the first message is used to instruct the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message is used to instruct the terminal to establish a second user plane connection with the target second network device.

[0052] In the above embodiments, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, establish the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes a first identifier, wherein the above method further includes: the terminal updating the second identifier to the first identifier according to the first message, wherein the first identifier is the identifier of the target second network device, and the second identifier is the identifier of the source second network device.

[0054] In the above embodiments, when a terminal receives a first message, it can determine the target second network device based on the first identifier, update the second identifier (which is the identifier of the source second network device) to the first identifier (which is the identifier of the target second network device), and then update the session executed in the first user plane connection to be executed in the second user plane connection. This can ensure the accurate execution of the session and improve communication performance.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: the terminal receiving a second message sent by the first network device, wherein the second message is used to instruct the terminal to release the first user plane connection.

[0056] In the above embodiments, the terminal receives a second message sent by the first network device and releases the first user plane connection, thereby updating the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device. In turn, the session executed in the first user plane connection is updated to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the second message includes a second session identifier, wherein the above method further includes: the terminal updating the first session identifier to the second session identifier according to the second message, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection, and the second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0058] In the above embodiments, when the terminal receives the second message, it can determine the second session identifier of the first session in the first user plane connection, update the first session identifier of the first session to the second session identifier, and then update the first session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the first message is further used to indicate that the first session in the first user plane connection will be updated to be executed in the second user plane connection. The method further includes: the terminal sending first information to the target second network device through the second user plane connection according to the first message, wherein the first information is information that the terminal needs to send to the target second network device when executing the first session in the second user plane connection.

[0060] In the above embodiments, the terminal can update the first session in the first user plane connection to be executed in the second user plane connection according to the first message, and send the first information of the first session to the target second network device through the second user plane connection, which can ensure the accurate execution of the first session and improve communication performance.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes a first identifier, wherein the terminal sends first information to a target second network device via a second user plane connection based on the first message, including: determining the target second network device based on the first identifier, and sending the first information to the target second network device via the second user plane connection.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal sends first information to the target second network device through the second user plane connection according to the first message, including: determining that the first session is executed in the second user plane connection according to the second session identifier, and sending the first information to the target second network device through the second user plane connection, wherein the second session identifier is included in the second message sent by the first network device received by the terminal, and the second session identifier is the identifier corresponding to the execution of the first session in the second user plane connection.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: the terminal receiving a third message sent by the target second network device, wherein the third message is used to indicate that the first information has been successfully received.

[0064] In the above embodiments, the terminal can receive a third message sent by the target second network device to determine that the first information of the first session has been successfully sent.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following: a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection; a second session identifier, which is an identifier corresponding to the first session when it is executed in the second user plane connection; and second session identifier allocation indication information, which is used to instruct the target second network device to allocate a second session identifier for the first session.

[0066] In the above embodiments, the first information sent by the terminal to the target second network device includes a first session identifier and / or a second session identifier, which can be used by the target second network device to identify the first session in order to ensure the accurate execution of the first session.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the third message includes a second session identifier, wherein the above method further includes: the terminal updating the first session identifier to the second session identifier, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0068] In the above embodiments, the terminal can update the identifier of the first session to the identifier of the second session, and use the identifier of the second session to identify the first session when sending the first session to the target second network device in the future, so that the target second network device can identify the first session.

[0069] In conjunction with some embodiments of the first aspect, in some embodiments, the first identifier is at least one of a first association identifier, a target second network device identifier, and a first routing identifier; and / or the second identifier is at least one of a second association identifier, a source second network device identifier, and a second routing identifier.

[0070] In conjunction with some embodiments of the first aspect, in some embodiments, the first session identifier and the second identifier have the same value; and / or the second session identifier has the same value as the first identifier.

[0071] In the above embodiments, when the terminal determines the value of the first session identifier, it can determine it based on the second identifier, which is the identifier of the source second network device. When determining the second session identifier, it can determine it based on the first identifier, which is the identifier of the target second network device, so that the terminal and the target second network device can accurately identify the first session and ensure the accurate execution of the first session.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the first session includes at least one of the following: a session in a location service; a session in a ranging / lateral walkway location service; a session in a sensing service.

[0073] Secondly, embodiments of this disclosure propose a communication method executed by a first network device, comprising: sending a first message to a terminal, wherein the first message is used to instruct the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message is used to instruct the terminal to establish a second user plane connection with the target second network device.

[0074] In the above embodiments, the first network device can instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, thereby establishing the second user plane connection between the terminal and the target second network device. This enables the session update executed by the terminal in the first user plane connection to be executed in the second user plane connection, ensuring the accurate execution of the session and improving communication performance.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes a first identifier, the first identifier being the identifier of the target second network device, the first message being used to instruct the terminal to update the second identifier to the first identifier, the first identifier being the identifier of the target second network device, and the second identifier being the identifier of the source second network device.

[0076] In the above embodiments, the first network device can instruct the terminal to update the second identifier, which is the identifier of the source second network device, to the first identifier, so that the terminal and the target second network device can successfully execute a session after the user plane connection is updated.

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the first message is also used to instruct the terminal to update the first session in the first user plane connection to be performed in the second user plane connection.

[0078] In the above embodiments, the first network device can instruct the terminal to update the first session in the first user plane connection to be executed in the second user plane connection, which can ensure the smooth execution of the first session and improve communication quality.

[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: a first network device receiving a fourth message sent by a target second network device, wherein the fourth message is used to instruct the first network device to send a first message to a terminal, and the fourth message includes a first identifier and a second identifier, wherein the first identifier is the identifier of the target second network device, and the second identifier is the identifier of the source second network device.

[0080] In the above embodiments, the first network device can determine to send a first message to the terminal based on the fourth message sent by the target second network device, so as to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, establish the second user plane connection between the terminal and the target second network device, and thus realize that the session update executed by the terminal in the first user plane connection is executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0081] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: a first network device determining that a source second network device cannot provide services to a terminal, and a target second network device providing services to a terminal; sending a fifth message to the target second network device, wherein the fifth message is used to instruct the target second network device to send a fourth message to the first network device, the fifth message is used to instruct the target second network device to establish a second user plane connection with the terminal, and the fifth message includes a second identifier and an identifier of the terminal, wherein the second identifier is the identifier of the source second network device.

[0082] In the above embodiments, when the source second network device cannot provide services to the terminal and the target second network device can provide services to the terminal, the first network device can send a fifth message to the target second network device, instructing the target second network device to establish a second user plane connection with the terminal, so that the session update executed by the terminal in the first user plane connection can be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0083] In conjunction with some embodiments of the second aspect, in some embodiments, the first network device determines that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal, including: receiving a sixth message sent by the source second network device, wherein the sixth message is used to indicate that the source second network device cannot provide services to the terminal, the sixth message includes a first identifier, the first identifier being an identifier of the target second network device; and determining, based on the sixth message, that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal.

[0084] In the above embodiments, the first network device can determine, based on the sixth message sent by the source second network device, that the source second network device cannot provide services to the terminal, and that the target second network device provides services to the terminal.

[0085] In conjunction with some embodiments of the second aspect, in some embodiments, the first network device determines that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal, including: receiving a sixth message sent by the source second network device, wherein the sixth message is used to indicate that the source second network device cannot provide services to the terminal; and determining from one or more candidate second network devices that the target second network device provides services to the terminal.

[0086] In the above embodiments, the first network device can determine that the source second network device cannot provide services to the terminal based on the sixth message sent by the source second network device, and determine the target second network device to provide services to the terminal from one or more candidate second network devices.

[0087] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: a first network device sending a seventh message to a source second network device, wherein the seventh message is used to instruct the source second network device to release the first user plane connection.

[0088] In the above embodiments, the first network device can instruct the source second network device to release the first user plane connection with the terminal, so that the session update executed by the terminal in the first user plane connection can be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0089] In conjunction with some embodiments of the second aspect, in some embodiments, the seventh message includes a first identifier, which is an identifier of the target second network device, and the seventh message is also used to indicate that the source second network device sends the context of the terminal to the target second network device.

[0090] In the above embodiments, the first network device can instruct the source second network device to send the terminal's context to the target second network device. In the case of user plane connection update, the target second network device can identify the information sent by the terminal and ensure communication quality.

[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: a first network device receiving an eighth message sent by a source second network device, wherein the eighth message is used to instruct the first network device to instruct the terminal to release the first user plane connection.

[0092] In the above embodiments, the first network device may instruct the terminal to release the first user plane connection with the source second network device based on the eighth message sent by the source second network device.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, the eighth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0094] In the above embodiments, the first network device can obtain the second session identifier of the first session from the source second network device.

[0095] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: a first network device sending a second message to a terminal, wherein the second message is used to instruct the terminal to release the first user plane connection.

[0096] In the above embodiments, the first network device may instruct the terminal to release the first user plane connection with the source second network device in order to complete the update of the user plane connection.

[0097] In conjunction with some embodiments of the second aspect, in some embodiments, the second message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection. The second message is also used to instruct the terminal to update the first session identifier to the second session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0098] In the above embodiments, the first network device can instruct the terminal to update the first session identifier of the first session to the second session identifier, so that the terminal and the target second network device can successfully execute the first session after the user plane connection is updated.

[0099] Thirdly, this disclosure proposes a communication method executed by a target second network device, comprising: sending a fourth message to a first network device, wherein the fourth message is used to instruct the first network device to send a first message to a terminal, the first message is used to instruct the terminal to update a first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device, the first message is used to instruct the terminal to establish a second user plane connection with the target second network device, and the fourth message includes a first identifier and a second identifier, the first identifier being the identifier of the target second network device, and the second identifier being the identifier of the source second network device.

[0100] In the above embodiments, the target second network device can instruct the first network device to send a first message to the terminal, instructing the terminal to update the first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device, thereby establishing a second user plane connection between the terminal and the target second network device. This enables the session update executed by the terminal in the first user plane connection to be executed in the second user plane connection, ensuring accurate execution of the session and improving communication performance.

[0101] In conjunction with some embodiments of the third aspect, in some embodiments, the above method further includes: the target second network device receiving a fifth message sent by the first network device, wherein the fifth message is used to instruct the target second network device to send a fourth message to the first network device, the fifth message is used to instruct the target second network device to establish a second user plane connection with the terminal, and the fifth message includes a second identifier and an identifier of the terminal, wherein the second identifier is an identifier of the source second network device.

[0102] In the above embodiments, the target second network device can receive the fifth message sent by the first network device, establish a second user plane connection with the terminal, and send a fourth message to the terminal.

[0103] In conjunction with some embodiments of the third aspect, in some embodiments, the above method further includes: the target second network device receiving a ninth message sent by the source second network device, wherein the ninth message is used to indicate the context of the terminal; and sending a tenth message to the source second network device, wherein the tenth message is used to indicate that the context of the terminal has been successfully received.

[0104] In the above embodiments, the target second network device can receive the terminal context sent by the source second network device to ensure that after the user plane connection is updated, the target second network device and the terminal can successfully execute the first session in the original first user plane connection between the terminal and the source second network device.

[0105] In conjunction with some embodiments of the third aspect, in some embodiments, the ninth message includes a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection.

[0106] In the above embodiment, the target second network device receives a ninth message sent by the source second network device, which includes a first session identifier of the first session. In subsequent communications with the terminal, the first session can be identified based on the first session identifier to ensure the accurate execution of the first session.

[0107] In conjunction with some embodiments of the third aspect, in some embodiments, the tenth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0108] In the above embodiments, the target second network device can update the first session identifier to the second session identifier and send it to the source second network device, so that the source second network device can instruct the terminal to update the first session identifier of the first session to the second session identifier. In subsequent communications with the terminal, the second session identifier is used to identify the first session, ensuring the accurate execution of the first session.

[0109] In conjunction with some embodiments of the third aspect, in some embodiments, the first message is also used to indicate that the first session in the first user plane connection will be updated to be performed in the second user plane connection, and the above method further includes: the target second network device receiving first information of the first session sent by the terminal through the second user plane connection.

[0110] In conjunction with some embodiments of the third aspect, in some embodiments, the above method further includes: the target second network device sending a third message to the terminal, wherein the third message is used to indicate that the first information has been successfully received.

[0111] In conjunction with some embodiments of the third aspect, in some embodiments, the first information includes at least one of the following: a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection; a second session identifier, which is an identifier corresponding to the first session when it is executed in the second user plane connection; and second session identifier allocation indication information, which is used to instruct the target second network device to allocate a second session identifier to the first session.

[0112] In conjunction with some embodiments of the third aspect, in some embodiments, the third message includes a second session identifier, and the third message is also used to indicate that the first session identifier is updated to the second session identifier, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection, and the second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0113] Fourthly, embodiments of this disclosure propose a communication method executed by a source second network device, comprising: receiving a seventh message sent by a first network device, wherein the seventh message is sent by the first network device after sending a first message to a terminal, the first message being used to indicate updating the first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device, the first message being used to indicate that the terminal establishes a second user plane connection with the target second network device, and the seventh message being used to indicate that the source second network device releases the first user plane connection.

[0114] In the above embodiments, the source second network device can receive the seventh message sent by the first network device and release the first user plane connection with the terminal, so that the terminal can update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, establish the second user plane connection between the terminal and the target second network device, and then execute the first session update in the first user plane connection between the terminal and the source second network device in the second user plane connection between the terminal and the target second network device, which can ensure the accurate execution of the first session and improve communication performance.

[0115] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method further includes: the source second network device sending a ninth message to the target second network device, wherein the ninth message is used to indicate the context of the terminal; and receiving a tenth message sent by the target second network device, wherein the tenth message is used to indicate that the context of the terminal has been successfully received.

[0116] In conjunction with some embodiments of the fourth aspect, in some embodiments, the ninth message includes a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection.

[0117] In conjunction with some embodiments of the fourth aspect, in some embodiments, the tenth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0118] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method further includes: the source second network device sending an eighth message to the first network device, wherein the eighth message is used to instruct the first network device to instruct the terminal to release the first user plane connection.

[0119] In conjunction with some embodiments of the fourth aspect, in some embodiments, the eighth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0120] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method further includes: the source second network device sending a sixth message to the first network device, wherein the sixth message is used to indicate that the source second network device is unable to provide services to the terminal.

[0121] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sixth message includes a first identifier, the first identifier being an identifier of the target second network device, and the sixth message being used by the first network device to determine that the source second network device cannot provide services to the terminal, and the target second network device to provide services to the terminal.

[0122] Fifthly, embodiments of this disclosure propose a communication method, comprising: a target second network device sending a fourth message to a first network device, wherein the fourth message instructs the first network device to send a first message to a terminal, the first message instructing the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and the target second network device, the fourth message instructing the terminal to establish a second user plane connection with the target second network device, the fourth message including a first identifier and a second identifier, the second identifier being an identifier of the source second network device, and the first identifier being an identifier of the target second network device; the first network device sending the first message to the terminal; the terminal receiving the first message sent by the first network device; the first network device sending a seventh message to the source second network device, the seventh message instructing the source second network device to release the first user plane connection; and the source second network device receiving the seventh message sent by the first network device.

[0123] In the above embodiments, the first session update in the first user plane connection between the terminal and the source second network device can be executed in the second user plane connection between the terminal and the target second network device, which can ensure the accurate execution of the first session and improve communication performance.

[0124] In a sixth aspect, embodiments of this disclosure provide a terminal, including: a transceiver module, configured to receive a first message sent by a first network device, wherein the first message is configured to indicate updating a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message is configured to indicate that the terminal establishes a second user plane connection with the target second network device.

[0125] In a seventh aspect, embodiments of this disclosure provide a first network device, including: a transceiver module, configured to send a first message to a terminal, wherein the first message is configured to indicate updating a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message is configured to indicate that the terminal establishes a second user plane connection with the target second network device.

[0126] Eighthly, this disclosure provides a target second network device, including: a transceiver module, configured to send a fourth message to a first network device, wherein the fourth message is configured to instruct the first network device to send a first message to a terminal, the first message is configured to instruct the terminal to update a first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device, the first message is configured to instruct the terminal to establish a second user plane connection with the target second network device, and the fourth message includes a first identifier and a second identifier, the first identifier being the identifier of the target second network device, and the second identifier being the identifier of the source second network device.

[0127] In a ninth aspect, embodiments of this disclosure provide a source second network device, comprising: a transceiver module, configured to receive a seventh message sent by a first network device, wherein the seventh message is sent by the first network device after sending a first message to a terminal, the first message being configured to indicate updating the first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device, the first message being configured to indicate that the terminal establishes a second user plane connection with the target second network device, and the seventh message being configured to indicate that the source second network device releases the first user plane connection.

[0128] In a tenth aspect, a terminal is proposed, comprising: one or more processors, wherein the terminal is used to execute the method described in the first aspect.

[0129] In the eleventh aspect, a first network device is proposed, comprising: one or more processors, wherein the first network device is configured to perform the method described in the second aspect.

[0130] In a twelfth aspect, a target second network device is proposed, comprising: one or more processors, wherein the target second network device is configured to perform the method described in the third aspect.

[0131] In a thirteenth aspect, a second source network device is proposed, comprising: one or more processors, wherein the second source network device is configured to perform the method described in the fourth aspect.

[0132] In a fourteenth aspect, embodiments of this disclosure provide a communication device comprising: one or more processors; and a memory coupled to the processors, the memory storing instructions which, when executed by the processors, cause the communication device to perform the method described in at least one of the first, second, third, and fourth aspects.

[0133] In a fifteenth aspect, embodiments of this disclosure provide a communication system comprising: a terminal, a first network device, a target second network device, and a source second network device; wherein the terminal is configured to perform the method as described in the first aspect, the first network device is configured to perform the method as described in the second aspect, the target second network device is configured to perform the method as described in the third aspect, and the source second network device is configured to perform the method as described in the fourth aspect.

[0134] In a tenth aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in at least one of the first, second, third, and fourth aspects.

[0135] In one aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method described in at least one of the first, second, third, and fourth aspects.

[0136] In a twelfth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in at least one of the first, second, third, and fourth aspects.

[0137] In a thirteenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described in at least one of the first, second, third, and fourth aspects described above.

[0138] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0139] This disclosure provides a communication method and apparatus. In some embodiments, the terms "communication method" and "information processing method" can be used interchangeably.

[0140] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0141] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0142] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0143] In the embodiments disclosed herein, "multiple" refers to two or more.

[0144] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0145] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0146] In some embodiments, the notation "A or B" may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0147] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0148] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0149] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0150] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0151] In some embodiments, the terms “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 lower than,” and “above” can be used interchangeably, as can the terms “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”.

[0152] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0153] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0154] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0155] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0156] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0157] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0158] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0160] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0161] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0162] Figure 1A is an architecture diagram of a communication system provided in an embodiment of this disclosure.

[0163] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102.

[0164] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, and wireless terminal in smart home.

[0165] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0166] In some embodiments, 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, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0167] In some embodiments, the access network device may be a satellite.

[0168] In some embodiments, the core network equipment may be a single device, multiple devices, or a group of devices, including all or part of a first network element, a second network element, a third network element, a fourth network element, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0169] In some embodiments, the first network element is, for example, an access and mobility management function (AMF) network element.

[0170] In some embodiments, the second network element is, for example, a Location Management Function (LMF) network element.

[0171] In some embodiments, the third network element is, for example, a sensing function (SF) network element.

[0172] In some embodiments, the fourth network element is, for example, a network repository function (NRF) network element.

[0173] In some embodiments, the first network element is used to implement terminal access management and mobility management. It is responsible for terminal state maintenance, terminal reachability management, mobility management (MM), forwarding of non-access stratum (NAS) messages, and forwarding of session management (SM) N2 messages.

[0174] In some embodiments, the second network element is used to coordinate and schedule the resources required for the location of the terminal.

[0175] In some embodiments, the third network element is used to perform wireless sensing using access network equipment or terminals to realize sensing services.

[0176] In some embodiments, the fourth network element is used for dynamic registration of network function service capabilities and network function discovery.

[0177] In some embodiments, at least one of the first network element, the second network element, and the third network element can be independent of the core network equipment.

[0178] In some embodiments, at least one of the first network element, the second network element, and the third network element may be part of the core network equipment.

[0179] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0180] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0181] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), Super 3G, IMT-Advanced, 4th Generation Mobile Communication System (4G), 5th Generation Mobile Communication System (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Ultra-Wideband. The technologies used include UWB (Ultra-Wideband), Bluetooth (a registered trademark), public land mobile network (PLMN) networks, device-to-device (D2D) systems, machine-to-machine (M2M) systems, Internet of Things (IoT) systems, vehicle-to-everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0182] In some embodiments, the association identifier (ID), the route identifier (ID), and the location services (LCS) session identifier (ID) are used.

[0183] As shown in Figure 1B, in the control plane, the association ID (or LCS association ID) and route ID are used. The association ID and route ID are used by the AMF to identify the LMF and optionally, the LCS session. The association ID is used between the AMF and the LMF, and the route ID is used between the UE and the AMF. The AMF maps the route ID to the association ID and vice versa. The values ​​of the association ID and the route ID can be the same or have a specific mapping relationship.

[0184] The association ID and routing ID are transmitted together with LCS messages (LCS supplementary service messages), long term evolution positioning protocol (LPP) messages, and user plane positioning connection management (UPP-CM) messages.

[0185] For example, during user plane connection establishment / release, the association ID and route ID are transmitted along with the user plane connection establishment / release request / command / completion message. In the control plane, the association ID and route ID are also transmitted along with event reporting messages.

[0186] As shown in Figure 1C, in the user plane, the LCS session identifier (ID) is used. The user plane connection is an end-to-end connection between the UE and the LMF. Messages are not transmitted through the AMF, and the LCS session ID is used to identify the LCS session. In order to associate LCS messages and LPP messages transmitted in the control plane and user plane, the value of the LCS session ID is the same as the association ID and / or routing ID used in the control plane.

[0187] For example, in the user plane, the LCS session ID is transmitted along with the event reporting message.

[0188] In related technologies, in the user plane, report messages are transmitted between the second network device and the terminal via a user plane connection. If the terminal moves outside the service area of ​​the source second network device and enters the service area of ​​the target second network device, the first network device performs an update for the second network device. However, during the update of the second network device, the terminal is unaware of the association between the source and target second network devices, and the terminal cannot use the second user plane connection established with the target second network device to transmit the first session. This is a problem that urgently needs to be solved.

[0189] Based on this, embodiments of this disclosure provide a communication method and apparatus. The method, executed by a terminal, includes: receiving a first message sent by a first network device, wherein the first message instructs the terminal to update a first user plane connection between the terminal and a source second network device to a second user plane connection between the terminal and a target second network device, and the first message instructs the terminal to establish a second user plane connection with the target second network device. Therefore, the terminal can determine, based on the first message instructing the terminal to establish a second user plane connection with the target second network device, to update the first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device. This allows the session executed in the first user plane connection to be updated and executed in the second user plane connection, ensuring accurate session execution and improving communication performance.

[0190] Figure 2A is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiments of the present disclosure relate to a communication method, which includes:

[0191] S201A, the second network device sends the sixth message to the first network device.

[0192] In some embodiments, the first network device receives a sixth message sent by the source second network device, but is not limited thereto. The first network device may also receive a sixth message sent by a subject other than the source second network device, in which case S201A can be omitted.

[0193] In some embodiments, the first network device obtains the sixth message defined by the protocol, in which case S201A can be omitted.

[0194] In some embodiments, the first network device obtains the sixth message from the upper layer(s), in which case S201A can be omitted.

[0195] In some embodiments, the first network device processes the data to obtain the sixth message, in which case S201A can be omitted.

[0196] In some embodiments, the first network device autonomously implements the function indicated by the sixth message, or the above function is a default or default setting, in which case S201A can be omitted.

[0197] In some embodiments, the source second network device determines to send a sixth message to the first network device on its own, or determines to send a sixth message to the first network device based on the instruction of the target second network device, or determines to send a sixth message to the first network device based on the instruction of the terminal, or determines to send a sixth message to the first network device based on the protocol agreement.

[0198] For example, if the second source network device does not receive feedback from the terminal for a long time after sending information to the terminal, it determines that the second source network device cannot provide services to the terminal, and then determines to send a sixth message to the first network device.

[0199] For example, when the source second network device receives an instruction from the target first network device indicating that it has received information sent by the terminal that was originally intended to be sent to the source second network device, the source second network device can determine that it will be unable to provide services to the terminal, and thus determines to send a sixth message to the first network device.

[0200] For example, the source second network device receives an indication message sent by the terminal, indicating the location information of the terminal. Based on the location information of the terminal, the source second network device determines that it will be unable to provide services to the terminal, and then determines to send a sixth message to the first network device.

[0201] In some embodiments, the source second network device may reuse existing signaling or messages to send a sixth message to the first network device, or send a sixth message to the first network device using new signaling or messages.

[0202] In some embodiments, the sixth message is an Nlmf_Location_UPNotify message.

[0203] In some embodiments, the sixth message is used to indicate that the source second network device is unable to provide services to the terminal.

[0204] In some embodiments, the sixth message is used to indicate that the terminal has left the network coverage area of ​​the source second network device.

[0205] In some embodiments, the sixth message is used to indicate the terminal's mobility information and the range of network services that the source second network device can provide, wherein the terminal's mobility information is used to indicate that the terminal will leave the range of network services that the source second network device can provide.

[0206] In some embodiments, the sixth message includes an identifier of the terminal, indicating that the source second network device is unable to provide services to the terminal corresponding to the identifier of the terminal.

[0207] In some embodiments, the sixth message includes a first identifier, which is an identifier of the target second network device. The sixth message is used by the first network device to determine that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal.

[0208] In this embodiment of the disclosure, the sixth message includes a first identifier, which is an identifier of the target second network device. The sixth message is also used to indicate that the target second network device can provide services to the terminal.

[0209] In some embodiments, the sixth message includes a first identifier and an identifier of the terminal. The first identifier is the identifier of the target second network device, used to instruct the first network device to instruct the terminal to establish a user plane connection with the target second network device, or to instruct the first network device to instruct the terminal to release the user plane connection with the source second network device.

[0210] In some embodiments, the first network device is an AMF, the source second network device is a first LMF, and the target second network device is a second LMF.

[0211] In some embodiments, the first network device is an AMF, the source second network device is a first SF, and the target second network device is a second SF.

[0212] In some embodiments, the first identifier is at least one of a first association identifier, a target second network device identifier, and a first routing identifier.

[0213] In this embodiment of the disclosure, the first identifier is the identifier of the target second network device, which may be the first association identifier of the target second network device, or the target second network device identifier of the target second network device, or the first routing identifier of the target second network device.

[0214] S202A, the first network device determines that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal.

[0215] In some embodiments, S201A may be omitted, and the first network device may determine on its own that the source second network device cannot provide services to the terminal, and determine that the target second network device provides services to the terminal.

[0216] For example, the first network device determines, based on the location of the terminal, that the terminal has left the service range of the source second network device and entered the service range of the target second network device, thereby determining that the source second network device cannot provide services to the terminal and that the target second network device provides services to the terminal.

[0217] In some embodiments, a first network device receives a sixth message sent by a source second network device, wherein the sixth message indicates that the source second network device is unable to provide services to the terminal, and the sixth message includes a first identifier, which is an identifier of a target second network device; based on the sixth message, it is determined that the source second network device is unable to provide services to the terminal, and that the target second network device provides services to the terminal.

[0218] In some embodiments, the first network device receives a sixth message sent by the source second network device, wherein the sixth message is used to indicate that the source second network device cannot provide services to the terminal; and determines a target second network device from one or more candidate second network devices to provide services to the terminal.

[0219] In this embodiment of the disclosure, the first network device determines, based on the sixth message sent by the source second network device, that the source second network device cannot provide services to the terminal. It then determines the target second network device from one or more candidate second network devices to provide services to the terminal. This determination can be made based on information from the one or more candidate second network devices. Optionally, the information from the one or more candidate second network devices may include the service area of ​​the one or more candidate second network devices, user plane positioning capability information of the one or more candidate second network devices, etc.

[0220] S203A, the first network device sends a fifth message to the target second network device.

[0221] In some embodiments, the target second network device receives a fifth message sent by the first network device, but is not limited thereto. The target second network device may also receive a fifth message sent by a subject other than the first network device, in which case S203A can be omitted.

[0222] In some embodiments, the target second network device obtains the fifth message defined by the protocol, in which case S203A can be omitted.

[0223] In some embodiments, the target second network device obtains the fifth message from the upper layer(s), in which case S203A can be omitted.

[0224] In some embodiments, the target second network device processes the data to obtain the fifth message, in which case S203A can be omitted.

[0225] In some embodiments, the target second network device autonomously implements the function indicated by the fifth message, or the above function is a default or default value, in which case S203A can be omitted.

[0226] In some embodiments, the first network device sends a fifth message to the target second network device on its own, or sends a fifth message to the target second network device based on an instruction from the source second network device, or sends a fifth message to the target second network device based on an instruction from the target second network device, or sends a fifth message to the target second network device based on a protocol agreement.

[0227] For example, if the first network device determines that the source second network device is unable to provide services to the terminal and the target second network device is providing services to the terminal, it sends a fifth message to the target second network device.

[0228] For example, when a first network device receives a fifth message from a source second network device and determines that the source second network device cannot provide services to the terminal, and that the target second network device is providing services to the terminal, the first network device sends a fifth message to the target second network device.

[0229] For example, if the first network device receives an instruction message sent by the target second network device, indicating that the target second network device is providing services to the terminal, and if it is determined that the target second network device is providing services to the terminal, then the first network device sends a fifth message to the target second network device.

[0230] In some embodiments, the first network device may reuse existing signaling or messages to send a fifth message to the target second network device, or send a fifth message to the target second network device using new signaling or messages.

[0231] In some embodiments, the fifth message is an Nlmf_Location_UPConfig Request message.

[0232] In some embodiments, the fifth message is used to instruct the target second network device to establish a second user plane connection with the terminal.

[0233] In some embodiments, the fifth message is used to instruct the target second network device to re-establish the second user plane connection with the terminal.

[0234] In some embodiments, the fifth message includes a second identifier and an identifier of the terminal, wherein the second identifier is an identifier of the source second network device. Optionally, the fifth message is used to instruct the user plane connection between the terminal and the source second network device to be updated to a user plane connection between the terminal and the target second network device.

[0235] In some embodiments, the second identifier is at least one of a second association identifier, a source second network device identifier, and a second routing identifier.

[0236] In some embodiments, the fifth message is used to instruct the target second network device to send a fourth message to the first network device.

[0237] S204A, the target second network device sends a fourth message to the first network device.

[0238] In some embodiments, the first network device receives a fourth message sent by the target second network device, but is not limited thereto. The first network device may also receive a fourth message sent by a subject other than the target second network device, in which case S204A can be omitted.

[0239] In some embodiments, the first network device obtains the fourth message defined by the protocol, in which case S204A can be omitted.

[0240] In some embodiments, the first network device obtains the fourth message from the upper layer(s), in which case S204A can be omitted.

[0241] In some embodiments, the first network device processes the data to obtain the fourth message, in which case S204A can be omitted.

[0242] In some embodiments, the first network device autonomously implements the function indicated by the fourth message, or the above function is a default or default setting, in which case S204A can be omitted.

[0243] In some embodiments, the target second network device sends a fourth message to the first network device on its own, or sends a fourth message to the first network device based on an instruction from the source second network device, or sends a fourth message to the first network device based on an instruction from the first network device, or sends a fourth message to the first network device based on a protocol agreement.

[0244] For example, when the target second network device determines that it needs to establish a second user plane connection with the terminal, it sends a fourth message to the first network device.

[0245] For example, when the target second network device receives the indication information sent by the source second network device and determines that it needs to establish a second user plane connection with the terminal, it sends a fourth message to the first network device.

[0246] For example, when the target second network device receives the fifth message sent by the first network device and determines that a second user plane connection with the terminal has been established, it sends a fourth message to the first network device.

[0247] In some embodiments, the target second network device may reuse existing signaling or messages to send a fourth message to the first network device, or send a fourth message to the first network device using new signaling or messages.

[0248] In some embodiments, the fourth message is the Namf_Communication_N1N2MessageTransfer message.

[0249] In some embodiments, the fourth message includes at least one of a second identifier, which is an identifier of a source second network device and a first identifier, where the first identifier is an identifier of a target second network device. Optionally, the fourth message is used to instruct the first network device to indicate to the terminal that the first user plane connection between the terminal and the source second network device be updated to a second user plane connection between the terminal and the target second network device. Optionally, the fourth message is used to instruct the first network device to instruct the terminal to establish / rebuild a second user plane connection with the target second network device.

[0250] In some embodiments, the fourth message is used to instruct the first network device to send the first message to the terminal.

[0251] In some embodiments, the fourth message includes a user plane connection establishment command message.

[0252] In some embodiments, the user plane connection establishment command message includes a second identifier, which is an identifier of the source second network device and a first identifier, wherein the first identifier is at least one of the identifiers of the target second network device.

[0253] In some embodiments, a user plane connection establishment command message is used to instruct a first network device to instruct a terminal to update the first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device.

[0254] In some embodiments, the first identifier is at least one of a first correlation identifier, a target second network device identifier, and a first routing identifier; and / or the second identifier is at least one of a second correlation identifier, a source second network device identifier, and a second routing identifier.

[0255] S205A, the first network device sends the first message to the terminal.

[0256] In some embodiments, the terminal receives a first message sent by the first network device, but is not limited thereto. The terminal may also receive a first message sent by a subject other than the first network device, in which case S205A can be omitted.

[0257] In some embodiments, the terminal obtains the first message defined by the protocol, in which case S205A can be omitted.

[0258] In some embodiments, the terminal obtains the first message from the upper layer(s), in which case S205A can be omitted.

[0259] In some embodiments, the terminal processes the data to obtain the first message, in which case S205A can be omitted.

[0260] In some embodiments, the terminal autonomously implements the function indicated by the first message, or the above function is a default or default setting, in which case S205A can be omitted.

[0261] In some embodiments, the first network device sends a first message to the terminal on its own, or sends a first message to the terminal based on an instruction from the source second network device, or sends a first message to the terminal based on an instruction from the target second network device, or sends a first message to the terminal based on an instruction from the terminal, or sends a first message to the terminal based on a protocol agreement.

[0262] For example, the first network device sends a first message to the terminal when it determines that the source second network device cannot provide services to the terminal, and / or determines that the target second network device can provide services to the terminal.

[0263] For example, the first network device receives the fourth message sent by the target second network device and sends the first message to the terminal.

[0264] For example, when the first network device receives the indication information sent by the source second network device, determines that the source second network device cannot provide services to the terminal, and determines that the target second network device can provide services to the terminal, it sends a first message to the terminal.

[0265] For example, when the first network device receives the indication information sent by the terminal, determines that the source second network device cannot provide services to the terminal, and determines that the target second network device can provide services to the terminal, it sends a first message to the terminal.

[0266] In some embodiments, the first network device may reuse existing signaling or messages to send a first message to the terminal, or send a first message to the terminal using new signaling or messages.

[0267] In some embodiments, the first message is a downlink NAS transfer (DL NAS TRANSPORT) message.

[0268] In some embodiments, the first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device.

[0269] In some embodiments, the first message is also used to instruct the terminal to update the first session in the first user plane connection to be executed in the second user plane connection.

[0270] In some embodiments, the first message includes a first identifier, which is the identifier of the target second network device. The first message is also used to instruct the terminal to update a second identifier, which is the identifier of the source second network device, to the first identifier, which is the identifier of the target second network device.

[0271] In some embodiments, the first message is used to instruct the terminal to establish a second user plane connection with the target second network device.

[0272] It is understandable that the terminal receives the first message sent by the first network device and obtains the first identifier. The first message is also used to instruct the terminal to update the second identifier, which is the identifier of the source second network device, to the first identifier. The terminal can determine the session between itself and the source second network device, and will subsequently update the target second network device corresponding to the first identifier for execution.

[0273] In some embodiments, the first message includes a user plane connection establishment command message.

[0274] In some embodiments, the user plane connection establishment command message includes a first identifier, which is an identifier of the target second network device.

[0275] In some embodiments, the user plane connection establishment command message is also used to instruct the first session in the first user plane connection to be updated to be executed in the second user plane connection.

[0276] In some embodiments, the first identifier is at least one of a first association identifier, a target second network device identifier, and a first routing identifier; and / or the second identifier is at least one of a second association identifier, a source second network device identifier, and a second routing identifier.

[0277] In this embodiment of the disclosure, the first identifier is at least one of a first correlation identifier, a target second network device identifier, and a first routing identifier.

[0278] In this embodiment of the disclosure, the second identifier is at least one of a second correlation identifier, a source second network device identifier, and a second routing identifier.

[0279] In some embodiments, the first session identifier and the second identifier have the same value; and / or the second session identifier has the same value as the first identifier.

[0280] In some embodiments, the first session includes at least one of the following: a session in a location service; a session in a ranging / lateral link location service; or a session in a sensing service.

[0281] In some embodiments, the source second network device is a first LMF, the target second network device is a second LMF, and the first session includes at least one of a session in the location service and a session in the ranging / sidelink location service.

[0282] In some embodiments, the source second network device is the first SF, the target second network device is the second SF, and the first session includes a session in the awareness service.

[0283] S206A, the terminal updates the second identifier, which is the identifier of the source second network device, to the first identifier, which is the identifier of the target second network device.

[0284] In this embodiment of the present disclosure, the terminal receives a first message sent by a first network device. If the first message includes a first identifier, and the first identifier is the identifier of the target second network device, the terminal updates the second identifier, and the second identifier is the identifier of the source second network device, to the first identifier, and the first identifier is the identifier of the target second network device. Then, the first user plane connection with the source second network device is updated to the second user plane connection with the target second network device.

[0285] S207A, the first network device sends the seventh message to the source second network device.

[0286] Specifically, S207A can be executed simultaneously with S203A or in a different order; S207A can be executed simultaneously with S204A or in a different order; S207A can be executed simultaneously with S205A or in a different order; and S207A can be executed simultaneously with S206A or in a different order.

[0287] In some embodiments, the source second network device receives a seventh message sent by the first network device, but is not limited thereto. The source second network device may also receive a seventh message sent by a subject other than the first network device, in which case S207A can be omitted.

[0288] In some embodiments, the source second network device obtains the seventh message as defined by the protocol, in which case S207A can be omitted.

[0289] In some embodiments, the source second network device obtains the seventh message from the upper layer(s), in which case S207A can be omitted.

[0290] In some embodiments, the source second network device processes the data to obtain the seventh message, in which case S207A can be omitted.

[0291] In some embodiments, the source second network device autonomously implements the function indicated by the seventh message, or the above function is a default or default value, in which case S207A can be omitted.

[0292] In some embodiments, the first network device sends a seventh message to the source second network device on its own, or sends a seventh message to the source second network device based on the instruction of the source second network device, or sends a seventh message to the source second network device based on the instruction of the target second network device, or sends a seventh message to the source second network device based on the instruction of the terminal, or sends a seventh message to the source second network device based on the protocol agreement.

[0293] For example, if the first network device determines that the source second network device cannot provide services to the terminal, and / or determines that the target second network device can provide services to the terminal, the first network device sends a seventh message to the source second network device.

[0294] For example, the first network device receives the fourth message sent by the target second network device and sends the seventh message to the source second network device.

[0295] For example, if the first network device receives a sixth message from the source second network device, determines that the source second network device cannot provide services to the terminal, and determines that the target second network device can provide services to the terminal, then sends a seventh message to the source second network device.

[0296] For example, if the first network device receives the indication information sent by the terminal, determines that the source second network device cannot provide services to the terminal, and determines that the target second network device can provide services to the terminal, then sends a seventh message to the source second network device.

[0297] In some embodiments, the first network device may reuse existing signaling or messages to send a seventh message to the source second network device, or send a fourth message to the source second network device using new signaling or messages.

[0298] In some embodiments, before the first network device sends the seventh message, the first network device has instructed the target second network device to establish a second user plane connection with the terminal.

[0299] In some embodiments, before the first network device sends the seventh message, the first network device has determined that the second user plane connection between the target second network device and the terminal has been established. For example, the first network device has received an indication from the target second network device that the second user plane connection has been established; or, for example, the first network device has received an indication from the terminal that the second user plane connection has been established.

[0300] In some embodiments, the seventh message is the Nlmf_Location_UPConfig Request message.

[0301] In some embodiments, the seventh message includes a first identifier, which is an identifier of the target second network device. The seventh message is also used to indicate that the source second network device sends the context of the terminal to the target second network device.

[0302] In some embodiments, the seventh message includes at least one of a first identifier and an identifier of the terminal, wherein the first identifier is an identifier of the target second network device. Optionally, the seventh message is used to instruct the source second network device to send the context of the terminal to the target second network device.

[0303] In some embodiments, the seventh message is used to instruct the source second network device to release the first user plane connection.

[0304] Optionally, the number of first sessions can be one or more.

[0305] S208A, the source second network device sends the ninth message to the target second network device.

[0306] In some embodiments, the target second network device receives a ninth message sent by the source second network device, but is not limited thereto. The target second network device may also receive a ninth message sent by a subject other than the source second network device, in which case S208A may be omitted.

[0307] In some embodiments, the target second network device obtains the ninth message defined by the protocol, in which case S208A can be omitted.

[0308] In some embodiments, the target second network device obtains the ninth message from the upper layer(s), in which case S208A can be omitted.

[0309] In some embodiments, the target second network device processes the data to obtain the ninth message, in which case S208A can be omitted.

[0310] In some embodiments, the target second network device autonomously implements the function indicated by the ninth message, or the above function is a default or default value, in which case S208A can be omitted.

[0311] In some embodiments, the source second network device sends a ninth message to the target second network device on its own, or sends a ninth message to the target second network device based on a request from the target second network device, or sends a ninth message to the target second network device based on an instruction from the first network device, or sends a ninth message to the target second network device based on a protocol agreement, or sends a ninth message to the target second network device based on an instruction from the terminal.

[0312] For example, when the source second network device determines that it can no longer provide services to the terminal and determines that the target second network device can provide services to the terminal, it sends a ninth message to the target second network device.

[0313] For example, if the source second network device receives a request from the target second network device requesting the source second network device to send the terminal context to the target second network device, the source second network device may send a ninth message to the target second network device.

[0314] For example, the source second network device sends a ninth message to the target second network device after determining that the first user plane connection with the terminal has been released and that the target second network device can provide services to the terminal.

[0315] For example, upon receiving a seventh message from a first network device, the source second network device sends a ninth message to the target second network device.

[0316] For example, when the source second network device receives an instruction from the terminal indicating a switch to the target second network device for service, the source second network device sends a ninth message to the target second network device.

[0317] In some embodiments, the source second network device may reuse existing signaling or messages to send a ninth message to the target second network device, or send a ninth message to the target second network device using new signaling or messages.

[0318] In some embodiments, the ninth message is an Nlmf_Location_LocationContexTransfer Request message.

[0319] In some embodiments, the ninth message is used to indicate the context of the transmitting terminal.

[0320] In some embodiments, the ninth message includes the context of the terminal. Optionally, the context of the terminal includes the context of the terminal's first session.

[0321] In some embodiments, the ninth message includes a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection. Optionally, the ninth message is used to instruct the target second network device to identify the first session based on the first session identifier.

[0322] In some embodiments, the target second network device assigns one or more corresponding second session identifiers for the first session identifier update of one or more first sessions.

[0323] In some embodiments, the tenth message includes a mapping relationship between the first session identifier and the second session identifier.

[0324] In some embodiments, the tenth message includes a second session identifier and a mapping relationship between the first session identifier and the second session identifier.

[0325] S209A, the target second network device sends the tenth message to the source second network device.

[0326] In some embodiments, the source second network device receives a tenth message sent by the target second network device, but is not limited thereto. The source second network device may also receive a tenth message sent by a subject other than the target second network device, in which case S209A can be omitted.

[0327] In some embodiments, the source second network device obtains the tenth message as specified by the protocol, in which case S209A can be omitted.

[0328] In some embodiments, the source second network device obtains the tenth message from the upper layer(s), in which case S209A can be omitted.

[0329] In some embodiments, the source second network device processes the data to obtain the tenth message, in which case S209A can be omitted.

[0330] In some embodiments, the source second network device autonomously implements the function indicated by the tenth message, or the above function is a default or default value, in which case S209A can be omitted.

[0331] In some embodiments, the target second network device determines, based on the ninth message sent by the source second network device, if the ninth message includes a first session identifier, that the identifier corresponding to the session in the second user plane connection between the terminal and the target second network device is determined as the first session identifier, and the session in the second user plane connection of the terminal can be identified based on the first session identifier.

[0332] In some embodiments, the target second network device determines, based on the ninth message sent by the source second network device, the identifier corresponding to the session in the second user plane connection between the terminal and the target second network device is determined as the first session identifier, and the session in the second user plane connection of the terminal can be identified based on the first session identifier.

[0333] In some embodiments, the target second network device determines, based on the ninth message sent by the source second network device, if the ninth message includes the first session identifier, the identifier corresponding to the session in the second user plane connection between the terminal and the target second network device is identified as the second session identifier, and instructs it to the source second network device. Then, the source second network device can instruct the terminal through the first network device to identify the session in the second user plane connection of the terminal based on the second session identifier.

[0334] In some embodiments, the target second network device sends a tenth message to the source second network device on its own, or sends a tenth message to the source second network device based on an instruction from the terminal, or sends a tenth message to the source second network device based on a message sent by the source second network device, or sends a tenth message to the source second network device based on a protocol agreement.

[0335] For example, the target second network device, having obtained the context of the terminal, may send a tenth message to the source second network device. Optionally, the target second network device obtains the context of the terminal from the terminal itself, or from another network device.

[0336] For example, after receiving the ninth message sent by the source second network device, the target second network device sends a tenth message to the source second network device.

[0337] For example, after receiving the terminal's context sent by the terminal, the target second network device sends a tenth message to the source second network device. Optionally, the target second network device sends a context request message to the terminal, requesting the terminal to send its context to the target second network device.

[0338] In some embodiments, the target second network device may reuse existing signaling or messages to send a tenth message to the source second network device, or send a tenth message to the source second network device using new signaling or messages.

[0339] In some embodiments, the tenth message is an Nlmf_Location_LocationContexTransfer Response message.

[0340] In some embodiments, the tenth message is used to indicate the context of a terminal that has been successfully received.

[0341] In some embodiments, the tenth message is used to indicate the context of the first session that the terminal has successfully received.

[0342] In some embodiments, the tenth message includes a first identifier, which is an identifier of the target second network device.

[0343] In some embodiments, the tenth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection. Optionally, the tenth message is used to instruct the source second network device to update the identifier of the session in the user plane connection between the terminal and the source second network device to the second session identifier. Optionally, the tenth message is used to instruct the source second network device to send the second session identifier to the terminal. Optionally, the tenth message is used to instruct the source second network device to instruct the terminal to update the identifier of the session in the user plane connection between the terminal and the source second network device to the second session identifier.

[0344] S210A, the second network device sends the eighth message to the first network device.

[0345] In some embodiments, the first network device receives an eighth message sent by the source second network device, but is not limited thereto. The first network device may also receive an eighth message sent by a subject other than the source second network device, in which case S210A may be omitted.

[0346] In some embodiments, the first network device obtains the eighth message defined by the protocol, in which case S210A can be omitted.

[0347] In some embodiments, the first network device obtains the eighth message from the upper layer(s), in which case S210A can be omitted.

[0348] In some embodiments, the first network device processes the data to obtain the eighth message, in which case S210A can be omitted.

[0349] In some embodiments, the first network device autonomously implements the function indicated by the eighth message, or the above function is a default or default setting, in which case S210A can be omitted.

[0350] In some embodiments, the source second network device sends the eighth message to the first network device on its own, or sends the eighth message to the first network device based on an instruction sent by the first network device, or sends the eighth message to the first network device based on an instruction sent by the target second network device, or sends the eighth message to the first network device based on an instruction sent by the terminal, or sends the eighth message to the first network device based on a protocol agreement.

[0351] For example, when the source second network device determines that it needs to update the user plane connection with the terminal to the user plane connection between the terminal and the target second network device, it sends an eighth message to the first network device.

[0352] For example, upon receiving a seventh message from a first network device, the second source network device sends an eighth message to the first network device.

[0353] For example, upon receiving the tenth message from the target second network device, the source second network device sends an eighth message to the first network device.

[0354] For example, when the source second network device receives an instruction from the terminal indicating that the first user plane connection between the terminal and the source second network device needs to be updated to a second user plane connection between the terminal and the target second network device, the source second network device sends an eighth message to the first network device.

[0355] In some embodiments, the source second network device may reuse existing signaling or messages to send an eighth message to the first network device, or send an eighth message to the first network device using new signaling or messages.

[0356] In some embodiments, the eighth message is the Namf_communication_N1N2MassageTransfer message.

[0357] In some embodiments, the eighth message is used to instruct the first network device to send a second message to the terminal.

[0358] In some embodiments, the eighth message includes the identifier of the terminal.

[0359] In some embodiments, the eighth message is used to instruct the first network device to indicate to the terminal that the first user plane connection with the source second network device will be updated to a second user plane connection with the target second network device.

[0360] In some embodiments, the eighth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0361] In some embodiments, the eighth message includes a mapping relationship between the first session identifier and the second session identifier.

[0362] In some embodiments, the eighth message includes a second session identifier and a mapping relationship between the first session identifier and the second session identifier.

[0363] S211A, the first network device sends a second message to the terminal.

[0364] In some embodiments, the terminal receives a second message sent by the first network device, but is not limited thereto. The terminal may also receive a second message sent by a subject other than the first network device, in which case S211A can be omitted.

[0365] In some embodiments, the terminal obtains a second message defined by the protocol, in which case S211A can be omitted.

[0366] In some embodiments, the terminal obtains the second message from the upper layer(s), in which case S211A can be omitted.

[0367] In some embodiments, the terminal processes the data to obtain a second message, in which case S211A can be omitted.

[0368] In some embodiments, the terminal autonomously implements the function indicated by the second message, or the above function is a default or default setting, in which case S211A can be omitted.

[0369] In some embodiments, the first network device sends a second message to the terminal on its own, or sends a second message to the terminal based on an instruction from the source second network device, or sends a second message to the terminal based on an instruction from the target second network device, or sends a first message to the terminal based on an instruction from the terminal, or sends a second message to the terminal based on a protocol agreement.

[0370] For example, if the first network device determines that the source second network device cannot provide services to the terminal, and / or determines that the target second network device can provide services to the terminal, the first network device sends a second message to the terminal.

[0371] For example, the first network device receives the eighth message sent by the source second network device and sends the second message to the terminal.

[0372] For example, if the first network device receives an indication message sent by the source second network device, determines that the source second network device cannot provide services to the terminal, and / or determines that the target second network device can provide services to the terminal, then the first network device sends a second message to the terminal.

[0373] For example, if the first network device receives an indication message sent by the target second network device, determines that the source second network device cannot provide services to the terminal, and / or determines that the target second network device can provide services to the terminal, it sends a second message to the terminal.

[0374] For example, if the first network device receives the indication information sent by the terminal and determines that the source second network device cannot provide services to the terminal, and / or determines that the target second network device can provide services to the terminal, it sends a second message to the terminal.

[0375] In some embodiments, the first network device may reuse existing signaling or messages to send a second message to the terminal, or send a second message to the terminal using new signaling or messages.

[0376] In some embodiments, the second message is a downlink NAS transfer (DL NAS TRANSPORT) message.

[0377] In some embodiments, the second message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection. The second message is also used to instruct the terminal to update the first session identifier to the second session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0378] In some embodiments, the second message is used to instruct the terminal to release the first user plane connection.

[0379] In some embodiments, the second message includes a user plane connection release command message.

[0380] In some embodiments, the user plane connection release command message includes a second session identifier of the first session in the first user plane connection.

[0381] In some embodiments, the user plane connection release command message is also used to instruct the terminal to update the second identifier, which is the identifier of the source second network device, to the first identifier.

[0382] In some embodiments, the second message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection, and a mapping relationship between the second session identifier and the first session identifier. The second message is used to instruct the terminal to update the first session identifier of the first session to the second session identifier.

[0383] Optionally, there can be one or more first sessions. The terminal updates the first session identifier of one or more first sessions to the second session identifier.

[0384] In some embodiments, when there are multiple first sessions, the second message includes a mapping relationship between the first session identifier and the second session identifier.

[0385] In some embodiments, when there are multiple first sessions, the user plane connection release command message includes a mapping relationship between the first session identifier and the second session identifier.

[0386] S212A, the terminal updates the first session identifier to the second session identifier.

[0387] In this embodiment, the terminal receives a second message sent by the first network device. If the second message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection, the terminal updates the first session identifier to the second session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection. Thus, the terminal can send information about the first session, including the second session identifier, to the target second network device through the second user plane connection between the terminal and the target second network device. The target second network device can then identify the first session based on the second session identifier, ensuring the accurate execution of the first session and improving communication performance.

[0388] Optionally, there can be one or more first sessions. The terminal updates the first session identifier of one or more first sessions to the second session identifier.

[0389] In some embodiments, when there are multiple first sessions, the first message includes a mapping relationship between the first session identifier and the second session identifier.

[0390] For example, the first session is LCS session a and LCS session b, the first session identifier is LCS session ID1a, LCS session ID1b, and the second session identifier is LCS session ID2a, LCS session ID2b. The first session identifier is updated to the second session identifier, which is LCS session ID1a, and LCS session ID2b is updated to LCS session ID2a, LCS session ID2b.

[0391] S213A, the terminal sends the first information to the target second network device.

[0392] In some embodiments, the target second network device receives the first information of the first session sent by the terminal, but is not limited thereto. The target second network device may also receive the first information of the first session sent by other subjects other than the terminal, in which case S213A can be omitted.

[0393] In some embodiments, the target second network device obtains the first information of the first session as defined by the protocol, in which case S213A can be omitted.

[0394] In some embodiments, the target second network device obtains the first information of the first session from the upper layer(s), in which case S213A can be omitted.

[0395] In some embodiments, the target second network device processes the information to obtain the first information of the first session, in which case S213A can be omitted.

[0396] In some embodiments, the target second network device autonomously implements the function indicated by the first information of the first session, or the above function is a default or default value, in which case S213A can be omitted.

[0397] In this embodiment of the disclosure, when the terminal determines that the first user plane connection with the source target second network device has been updated to the second user plane connection between the terminal and the target second network device, it can send the first information of the first session to the target second network device.

[0398] In some embodiments, the terminal may reuse existing signaling or messages to send the first information of the first session to the target second network device, or use new signaling or messages to send the first information of the first session to the target second network device.

[0399] In some embodiments, the terminal uses an uplink LCS-UP TRANSPORT message to send the first information of the first session to the target second network device.

[0400] In some embodiments, the first information is used to instruct the terminal to report events.

[0401] In some embodiments, the first information is used to indicate periodic or triggered event reports of the terminal.

[0402] In some embodiments, the first information includes at least one of the following: a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection; a second session identifier, which is an identifier corresponding to the first session when it is executed in the second user plane connection; and second session identifier allocation indication information, which is used to instruct the target second network device to allocate a second session identifier to the first session.

[0403] In this embodiment of the disclosure, the terminal receives a first message sent by a first network device. If the first message includes a second session identifier of a first session in a first user plane connection, the first information of the first session sent to the target second network device includes at least one of the first session identifier and the second session identifier.

[0404] In some embodiments, the first information does not include a session identifier.

[0405] In some embodiments, the first information includes second session identifier allocation indication information.

[0406] In some embodiments, the value of the first session identifier is a specific value that is pre-agreed or pre-configured, which is used to instruct the target second device to assign a second session identifier to the first session.

[0407] In some embodiments, the first information includes second session identifier allocation indication information, which is used to instruct the target second device to allocate a second session identifier for the first session.

[0408] In some embodiments, the terminal connects to the second user plane of the target second network device and sends the first information of the first session to the target second network device.

[0409] S214A, the target second network device sends a third message to the terminal.

[0410] In some embodiments, the terminal receives a third message sent by the target second network device, but is not limited thereto. The terminal may also receive a third message sent by other entities other than the target second network device, in which case S214A may be omitted.

[0411] In some embodiments, the terminal obtains a third message defined by the protocol, in which case S214A can be omitted.

[0412] In some embodiments, the terminal obtains a third message from the upper layer(s), in which case S214A can be omitted.

[0413] In some embodiments, the terminal processes the data to obtain a third message, in which case S214A can be omitted.

[0414] In some embodiments, the terminal autonomously implements the function indicated by the third message, or the above function is a default or default setting, in which case S214A can be omitted.

[0415] In some embodiments, the target second network device sends a third message to the terminal on its own, or sends a third message to the terminal based on the terminal's instruction, or sends a third message to the terminal based on the protocol agreement.

[0416] For example, when the target second network device receives the first information of the first session sent by the terminal, it sends a third message to the terminal.

[0417] In some embodiments, the target second network device may reuse existing signaling or messages to send a third message to the terminal, or send a third message to the terminal using new signaling or messages.

[0418] In some embodiments, the third message is a downlink LCS user plane connection transport (DL LCS-UP TRANSPORT) message.

[0419] In some embodiments, the third message is used to indicate that the first message has been successfully received.

[0420] In some embodiments, the third message is used to indicate the terminal's event report confirmation.

[0421] In some embodiments, the third message is used to indicate periodic or triggered event report confirmation from the terminal.

[0422] In some embodiments, the first information does not include a session identifier.

[0423] In some embodiments, the first information does not include a session identifier, and the target second network device identifies the first session based on the context of the terminal in the fifth message.

[0424] In some embodiments, the first information does not include a session identifier, and the target second network device identifies the first session based on the context of the first session in the fifth message.

[0425] In some embodiments, the first information does not include a session identifier, and the third message sent by the target second network device to the terminal includes a second session identifier.

[0426] In some embodiments, the first information does not include a session identifier, the target second network device assigns a second session identifier to the first session, and the third message sent by the target second network device to the terminal includes the second session identifier.

[0427] In some embodiments, the first information includes a first session identifier, and the target second network device identifies the first session based on the first session identifier in the fifth message and the context of the terminal.

[0428] In some embodiments, the first information includes a first session identifier, the target second network device assigns a second session identifier to the first session, and the third message sent by the target second network device to the terminal includes the second session identifier.

[0429] In some embodiments, the first information includes a first session identifier, the value of which is a pre-agreed or pre-configured specific value. The target second network device assigns a second session identifier to the first session based on the specific value of the first session identifier. The second message sent by the target second network device to the terminal includes the second session identifier.

[0430] In some embodiments, the first information includes a second session identifier allocation indication, the target second network device allocates a second session identifier to the first session based on the second session identifier allocation indication, and the second message sent by the target second network device to the terminal includes the second session identifier.

[0431] In some embodiments, the first information includes a second session identifier, and the third message sent by the target second network device to the terminal includes the second session identifier, so that the terminal can identify the first session upon receiving the third message.

[0432] It should be noted that, in this embodiment of the disclosure, the first session identifier and the second session identifier of the first session respectively mean that the first session identifier is the identifier corresponding to the execution of the first session in the first user plane connection, and the second session identifier is the identifier corresponding to the execution of the first session in the second user plane connection.

[0433] It should be noted that when the terminal sends the first information of the first session, it means that the terminal sends the first information when executing the first session; when the target second network device receives the first information of the first session, it means that the target second network device receives the first information when executing the first session.

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

[0435] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0436] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0437] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from upper layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0438] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0439] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0440] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0441] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc., from one subject to another passes through other subjects, it can be interpreted as the message being forwarded from one subject to another via other subjects, or it can be interpreted as the message being sent from one subject to another without passing through other subjects. For example, the terminal sends the first information of the first session directly to the target second network device without passing through other subjects, and the target second network device sends the second message directly to the terminal without passing through other subjects.

[0442] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, establish the second user plane connection between the terminal and the target second network device, and then execute the session update in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0443] The communication method involved in the embodiments of this disclosure may include at least one of S201A to S214A. For example, S201A, S202A, S203A, S204A, S205A, S206A, S207A, S208A, S209A, S210A, S211A, S212A, S213A, and S214A may be implemented as independent embodiments, but are not limited thereto.

[0444] In some embodiments, S207A and S203A can be executed in different orders or simultaneously, S207A and S204A can be executed in different orders or simultaneously, S207A and S205A can be executed in different orders or simultaneously, and S207A and S206A can be executed in different orders or simultaneously.

[0445] In some embodiments, S201A, S202A, S203A, S204A, S206A, S207A, S208A, S209A, S210A, S211A, S212A, S213A, and S214A are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0446] In some embodiments, S201A, S202A, S203A, S209A, S210A, S211A, S212A, S213A, and S214A are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0447] In some embodiments, S201A, S209A, S210A, S211A, S212A, S213A, and S214A are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0448] In some embodiments, S201A, S212A, S213A, and S214A are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0449] In some embodiments, S201A and S214A are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0450] In some embodiments, S201A is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0451] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0452] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, the present disclosure relates to a communication method, which includes:

[0453] S201B, the second network device sends the sixth message to the first network device.

[0454] The optional implementations of S201B can be found in the optional implementations of S201A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0455] In some embodiments, the sixth message is used to indicate that the source second network device is unable to provide services to the terminal.

[0456] In some embodiments, the sixth message includes a first identifier, which is an identifier of the target second network device. The sixth message is used by the first network device to determine that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal.

[0457] S202B, the first network device determines that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal.

[0458] The optional implementations of S202B can be found in the optional implementations of S202A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0459] In some embodiments, a first network device receives a sixth message sent by a source second network device, wherein the sixth message indicates that the source second network device is unable to provide services to the terminal, and the sixth message includes a first identifier, which is an identifier of a target second network device; based on the sixth message, it is determined that the source second network device is unable to provide services to the terminal, and that the target second network device provides services to the terminal.

[0460] In some embodiments, the first network device receives a sixth message sent by the source second network device, wherein the sixth message is used to indicate that the source second network device cannot provide services to the terminal; and determines a target second network device from one or more candidate second network devices to provide services to the terminal.

[0461] S203B, the first network device sends a fifth message to the target second network device.

[0462] The optional implementations of S203B can be found in the optional implementations of S203A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0463] In some embodiments, the fifth message is used to instruct the target second network device to send a fourth message to the first network device.

[0464] S204B, the target second network device sends a fourth message to the first network device.

[0465] The optional implementations of S204B can be found in the optional implementations of S204A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0466] In some embodiments, the fourth message includes a second identifier, which is an identifier of the source second network device, and a first identifier, which is an identifier of the target second network device. Optionally, the fourth message is used to instruct the first network device to indicate to the terminal that the first user plane connection between the terminal and the source second network device be updated to a second user plane connection between the terminal and the target second network device. Optionally, the fourth message is used to instruct the first network device to instruct the terminal to establish / rebuild a second user plane connection with the target second network device.

[0467] In some embodiments, the fourth message is used to instruct the first network device to send the first message to the terminal.

[0468] S205B, the first network device sends the first message to the terminal.

[0469] The optional implementations of S205B can be found in the optional implementations of S205A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0470] In some embodiments, the first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device.

[0471] In some embodiments, the first message is also used to indicate that the first session in the first user plane connection will be updated to be executed in the second user plane connection.

[0472] In some embodiments, the first message includes a first identifier, which is the identifier of the target second network device. The first message is also used to instruct the terminal to update a second identifier, which is the identifier of the source second network device, to the first identifier.

[0473] In some embodiments, the first identifier is at least one of a first association identifier, a target second network device identifier, and a first routing identifier; and / or the second identifier is at least one of a second association identifier, a source second network device identifier, and a second routing identifier.

[0474] In some embodiments, the first session identifier and the second identifier have the same value.

[0475] In some embodiments, the first message is also used to instruct the terminal to release the first user plane connection with the source second network device.

[0476] S206B, the terminal updates the second identifier to the first identifier.

[0477] In some embodiments, the first identifier is the identifier of the target second network device, and the second identifier is the identifier of the source second network device.

[0478] The optional implementations of S206B can be found in the optional implementations of S206A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0479] S207B, the first network device sends the seventh message to the source second network device.

[0480] The optional implementations of S207B can be found in the optional implementations of S207A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0481] In some embodiments, the seventh message includes at least one of a first identifier and an identifier of the terminal, wherein the first identifier is an identifier of the target second network device. Optionally, the seventh message is used to instruct the source second network device to send the context of the terminal to the target second network device.

[0482] In some embodiments, the seventh message is used to instruct the source second network device to release the first user plane connection.

[0483] S208B, the source second network device sends the ninth message to the target second network device.

[0484] The optional implementations of S208B can be found in the optional implementations of S208A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0485] In some embodiments, the ninth message is used to indicate the context of the terminal.

[0486] In some embodiments, the ninth message includes a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection. Optionally, the ninth message is used to instruct the target second network device to identify the first session based on the first session identifier.

[0487] S209B, the target second network device sends the tenth message to the source second network device.

[0488] The optional implementations of S209B can be found in the optional implementations of S209A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0489] In some embodiments, the tenth message is used to indicate the context of a terminal that has been successfully received.

[0490] In some embodiments, the tenth message includes a first identifier, which is an identifier of the target second network device. Optionally, the tenth message is used to instruct the source second network device to identify the tenth message sent by the target second network device.

[0491] In some embodiments, the tenth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection. Optionally, the tenth message is used to instruct the source second network device to update the identifier of the session in the user plane connection between the terminal and the source second network device to the second session identifier. Optionally, the tenth message is used to instruct the source second network device to send the second session identifier to the terminal. Optionally, the tenth message is used to instruct the source second network device to instruct the terminal to update the identifier of the session in the user plane connection between the terminal and the source second network device to the second session identifier.

[0492] S210B, the second network device sends the eighth message to the first network device.

[0493] The optional implementations of S210B can be found in the optional implementations of S210A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0494] In some embodiments, the eighth message is used to instruct the first network device to send a second message to the terminal.

[0495] In some embodiments, the eighth message includes the identifier of the terminal.

[0496] In some embodiments, the eighth message is used to instruct the first network device to indicate to the terminal that the first user plane connection with the source second network device will be updated to a second user plane connection with the target second network device.

[0497] In some embodiments, the eighth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0498] S211A, the first network device sends a second message to the terminal.

[0499] The optional implementations of S211B can be found in the optional implementations of S211A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0500] In some embodiments, the second message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection. The second message is also used to instruct the terminal to update the first session identifier to the second session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0501] In some embodiments, the second message is used to instruct the terminal to release the first user plane connection.

[0502] S212B, the terminal sends the first information to the target second network device.

[0503] The optional implementation of S212B can be found in the optional implementation of S213A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0504] In some embodiments, the first information is used to instruct the terminal to report events.

[0505] In some embodiments, the first information is used to indicate periodic or triggered event reports of the terminal.

[0506] In some embodiments, the first information includes at least one of the following: a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection; a second session identifier, which is an identifier corresponding to the first session when it is executed in the second user plane connection; and second session identifier allocation indication information, which is used to instruct the target second network device to allocate a second session identifier to the first session.

[0507] In some embodiments, the first information includes a first session identifier for the first session.

[0508] In some embodiments, the first information includes a second identifier, which is an identifier of the target second network device.

[0509] In some embodiments, the first information does not include a session identifier.

[0510] In some embodiments, the terminal connects to the second user plane of the target second network device and sends the first information of the first session to the target second network device.

[0511] S213B, the target second network device sends a third message to the terminal.

[0512] The optional implementation of S213B can be found in the optional implementation of S214A in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0513] In some embodiments, the third message is used to indicate that the first message has been successfully received.

[0514] In some embodiments, the third message includes a second session identifier, which is used to instruct the terminal to update the first session identifier of the first session to the second session identifier.

[0515] In some embodiments, the third message includes a second session identifier and a mapping relationship between the second session identifier and the first session identifier. The third message is used to instruct the terminal to update the first session identifier of the first session to the second session identifier.

[0516] In some embodiments, the target second network device sends a third message to the terminal via a second user plane connection between the terminal and the target second network device.

[0517] In this embodiment of the disclosure, the target second network device can identify the first session based on the terminal context obtained in S208B and the first information of the first session. Optionally, the terminal context includes a delay location type, and the first information of the first session also includes a delay location type, allowing the target second network device to identify the first session. Optionally, the first information of the first session sent by the terminal includes a first identifier, which is an identifier of the target second network device, allowing the target second network device to identify the first session, thereby ensuring the accurate execution of the first session and improving communication performance.

[0518] In some embodiments, the third message is used to indicate the terminal's event report confirmation.

[0519] In some embodiments, the third message is used to indicate periodic or triggered event report confirmation from the terminal.

[0520] In some embodiments, the first information does not include a session identifier.

[0521] In some embodiments, the first information does not include a session identifier, and the target second network device identifies the first session based on the context of the terminal in the fifth message.

[0522] In some embodiments, the first information does not include a session identifier, and the target second network device identifies the first session based on the context of the first session in the fifth message.

[0523] In some embodiments, the first information does not include a session identifier, and the third message sent by the target second network device to the terminal includes a second session identifier.

[0524] In some embodiments, the first information does not include a session identifier, the target second network device assigns a second session identifier to the first session, and the third message sent by the target second network device to the terminal includes the second session identifier.

[0525] In some embodiments, the first information includes a first session identifier, and the target second network device identifies the first session based on the first session identifier in the fifth message and the context of the terminal.

[0526] In some embodiments, the first information includes a first session identifier, the target second network device assigns a second session identifier to the first session, and the third message sent by the target second network device to the terminal includes the second session identifier.

[0527] In some embodiments, the first information includes a second session identifier, and the third message sent by the target second network device to the terminal includes the second session identifier, so that the terminal can identify the first session upon receiving the third message.

[0528] S214B, the terminal updates the first session identifier to the second session identifier.

[0529] In this embodiment, the terminal receives a third message sent by the target second network device. If the third message includes a second session identifier, the terminal updates the first session identifier of the first session to the second session identifier. Thus, the terminal can send information about the first session, including the second session identifier, to the target second network device through the second user plane connection between the terminal and the target second network device. The target second network device can then identify the first session based on the second session identifier, ensuring the accurate execution of the first session and improving communication performance.

[0530] Optionally, there can be one or more first sessions. The terminal updates the first session identifier of one or more first sessions to the second session identifier.

[0531] In some embodiments, when there are multiple first sessions, the first message includes a mapping relationship between the first session identifier and the second session identifier.

[0532] For example, the first session is LCS session a and LCS session b, the first session identifier is LCS session ID1a, LCS session ID1b, and the second session identifier is LCS session ID2a, LCS session ID2b. The first session identifier is updated to the second session identifier, which is LCS session ID1a, and LCS session ID2b is updated to LCS session ID2a, LCS session ID2b.

[0533] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, establish the second user plane connection between the terminal and the target second network device, and then execute the session update in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0534] The communication method involved in the embodiments of this disclosure may include at least one of S201B to S214B. For example, S201B, S202B, S203B, S204B, S205B, S206B, S207B, S208B, S209B, S210B, S211B, S212B, S213B, and S214B may be implemented as independent embodiments, but are not limited thereto.

[0535] In some embodiments, S207B and S203B can be executed in different orders or simultaneously, S207B and S204B can be executed in different orders or simultaneously, S207B and S205B can be executed in different orders or simultaneously, and S207B and S206B can be executed in different orders or simultaneously.

[0536] In some embodiments, S201B, S202B, S203B, S204B, S206B, S207B, S208B, S209B, S210B, S211B, S212B, S213B, and S214B are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0537] In some embodiments, S201B, S202B, S203B, S209B, S210B, S211B, S212B, S213B, and S214B are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0538] In some embodiments, S201B, S209B, S210B, S211B, S212B, S213B, and S214B are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0539] In some embodiments, S201B, S212B, S213B, and S214B are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0540] In some embodiments, S201B and S214B are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0541] In some embodiments, S201B is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0542] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0543] Figure 3A is a schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the present disclosure relates to a communication method, which includes:

[0544] S301A, the target second network device sends a fourth message to the first network device.

[0545] The optional implementation of S301A can be found in the optional implementation of S204A in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0546] In some embodiments, the method further includes: a first network device receiving a fourth message sent by a target second network device, wherein the fourth message is used to instruct the first network device to send a first message to a terminal, and the fourth message includes a first identifier and a second identifier, wherein the first identifier is the identifier of the target second network device, and the second identifier is the identifier of the source second network device.

[0547] In some embodiments, the method further includes: a first network device determining that a source second network device cannot provide services to a terminal, and a target second network device providing services to a terminal; sending a fifth message to the target second network device, wherein the fifth message is used to instruct the target second network device to send a fourth message to the first network device, the fifth message is used to instruct the target second network device to establish a second user plane connection with the terminal, and the fifth message includes a second identifier and an identifier of the terminal, wherein the second identifier is the identifier of the source second network device.

[0548] In some embodiments, determining that a source second network device cannot provide services to a terminal and a target second network device can provide services to the terminal includes: receiving a sixth message sent by the source second network device, wherein the sixth message indicates that the source second network device cannot provide services to the terminal, the sixth message includes a first identifier, the first identifier being an identifier of the target second network device; and determining, based on the sixth message, that the source second network device cannot provide services to the terminal and the target second network device can provide services to the terminal.

[0549] In some embodiments, determining that a source second network device cannot provide services to a terminal and a target second network device can provide services to a terminal includes: receiving a sixth message sent by the source second network device, wherein the sixth message is used to indicate that the source second network device cannot provide services to the terminal; and determining that the target second network device can provide services to the terminal from one or more candidate second network devices.

[0550] In some embodiments, the method further includes: a first network device sending a seventh message to a source second network device, wherein the seventh message is used to instruct the source second network device to release the first user plane connection.

[0551] In some embodiments, the seventh message includes a first identifier of the target second network device, and the seventh message is also used to indicate that the source second network device sends the context of the terminal to the target second network device.

[0552] In some embodiments, the method further includes: a first network device receiving an eighth message sent by a source second network device, wherein the eighth message is used to instruct the first network device to instruct the terminal to release the first user plane connection.

[0553] In some embodiments, the eighth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0554] In some embodiments, the method further includes: a first network device sending a second message to a terminal, wherein the second message is used to instruct the terminal to release the first user plane connection.

[0555] In some embodiments, the second message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection. The second message is also used to instruct the terminal to update the first session identifier to the second session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0556] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0557] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0558] In an exemplary embodiment, a communication method is proposed, wherein the method includes:

[0559] S1, the first network device sends the first message to the terminal.

[0560] The optional implementation of S1 can be found in the optional implementation of S205A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0561] The first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and the first message is used to instruct the terminal to establish a second user plane connection with the target second network device.

[0562] In some embodiments, the first message includes a first identifier, wherein the method further includes: the terminal updating the second identifier to the first identifier according to the first message, wherein the first identifier is the identifier of the target second network device, and the second identifier is the identifier of the source second network device.

[0563] In some embodiments, the method further includes: the terminal receiving a second message sent by the first network device, wherein the second message is used to instruct the terminal to release the first user plane connection.

[0564] In some embodiments, the second message includes a second session identifier, wherein the method further includes: the terminal updating the first session identifier to the second session identifier according to the second message, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection, and the second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0565] In some embodiments, the first message is further used to indicate that the first session in the first user plane connection will be updated to be executed in the second user plane connection. The method further includes: the terminal sending first information to the target second network device through the second user plane connection according to the first message, wherein the first information is information that the terminal needs to send to the target second network device when executing the first session in the second user plane connection.

[0566] In some embodiments, the first message includes a first identifier, wherein sending first information to a target second network device via a second user plane connection based on the first message includes: determining the target second network device based on the first identifier, and sending the first information to the target second network device via the second user plane connection.

[0567] In some embodiments, the terminal sends first information to a target second network device through a second user plane connection based on a first message, including: determining that a first session is executed in the second user plane connection based on a second session identifier, and sending the first information to the target second network device through the second user plane connection, wherein the second session identifier is included in the second message sent by the first network device received by the terminal, and the second session identifier is the identifier corresponding to the execution of the first session in the second user plane connection.

[0568] In some embodiments, the method further includes: the terminal receiving a third message sent by the target second network device, wherein the third message is used to indicate that the first information has been successfully received.

[0569] In some embodiments, the first information includes at least one of the following: a first session identifier, which is an identifier corresponding to the first session when it is executed in the first user plane connection; a second session identifier, which is an identifier corresponding to the first session when it is executed in the second user plane connection; and second session identifier allocation indication information, which is used to instruct the target second network device to allocate a second session identifier to the first session.

[0570] In some embodiments, the third message includes a second session identifier, wherein the above method further includes: updating the terminal's first session identifier to the second session identifier, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0571] In some embodiments, the first session identifier and the second identifier have the same value; and / or the second session identifier has the same value as the first identifier.

[0572] In some embodiments, the first session includes at least one of the following: a session in a location service; a session in a ranging / lateral link location service; or a session in a sensing service.

[0573] In some embodiments, the first message includes a first identifier, which is the identifier of the target second network device. The first message is used to instruct the terminal to update the second identifier to the first identifier of the target second network device, where the second identifier is the identifier of the source second network device.

[0574] In some embodiments, the first message is also used to instruct the terminal to update the first session in the first user plane connection to be executed in the second user plane connection.

[0575] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0576] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0577] In an exemplary embodiment, a communication method is proposed, wherein the method includes:

[0578] S10, the first network device sends the seventh message to the source second network device.

[0579] The optional implementation of S10 can be found in the optional implementation of S207A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0580] In some embodiments, the method further includes: the target second network device receiving a fifth message sent by the first network device, wherein the fifth message is used to instruct the target second network device to send a fourth message to the first network device, the fifth message is used to instruct the target second network device to establish a second user plane connection with the terminal, and the fifth message includes a second identifier and an identifier of the terminal, wherein the second identifier is the identifier of the source second network device.

[0581] In some embodiments, the method further includes: the target second network device receiving a ninth message sent by the source second network device, wherein the ninth message is used to indicate the context of the terminal; and sending a tenth message to the source second network device, wherein the tenth message is used to indicate that the context of the terminal has been successfully received.

[0582] In some embodiments, the ninth message includes a first session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0583] In some embodiments, the tenth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0584] In some embodiments, the first message is further used to indicate that the first session in the first user plane connection will be updated to be performed in the second user plane connection, and the above method further includes: the target second network device receiving first information of the first session sent by the terminal through the second user plane connection.

[0585] In some embodiments, the method further includes: the target second network device sending a third message to the terminal, wherein the third message is used to indicate that the first information has been successfully received.

[0586] In some embodiments, the first information includes at least one of the following:

[0587] The first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0588] The second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0589] In some embodiments, the third message includes a second session identifier, and the third message is further used to indicate that the first session identifier is updated to the second session identifier, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection, and the second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0590] In some embodiments, the above method further includes: the source second network device sending a ninth message to the target second network device, wherein the ninth message is used to indicate the context of the terminal;

[0591] Receive the tenth message sent by the target second network device, wherein the tenth message is used to indicate the context of the terminal that has successfully received the message.

[0592] In some embodiments, the ninth message includes a first session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

[0593] In some embodiments, the tenth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0594] In some embodiments, the method further includes: the source second network device sending an eighth message to the first network device, wherein the eighth message is used to instruct the first network device to instruct the terminal to release the first user plane connection.

[0595] In some embodiments, the second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

[0596] In some embodiments, the method further includes: the source second network device sending a sixth message to the first network device, wherein the sixth message is used to indicate that the source second network device is unable to provide services to the terminal.

[0597] In some embodiments, the sixth message includes a first identifier of the target second network device, and the sixth message is used by the first network device to determine that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal.

[0598] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0599] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0600] Figure 3B is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the embodiments of the present disclosure relate to a communication method, which includes:

[0601] S301B, the first network device sends a fifth message to the target second network device, the fifth message including the second identifier.

[0602] The optional implementation of S301B can be found in the optional implementation of S203A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0603] S302B, the target second network device sends a fourth message to the first network device, the fourth message including the first identifier.

[0604] The optional implementation of S302B can be found in the optional implementation of S204A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0605] S303B, the first network device sends a first message to the terminal, the first message including a first identifier and a second identifier.

[0606] The optional implementation of S303B can be found in the optional implementation of S205A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0607] S304B, the terminal updates the second identifier to the first identifier.

[0608] The optional implementation of S304B can be found in the optional implementation of S206A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0609] S305B, the first network device sends a seventh message to the source second network device, the seventh message including the first identifier.

[0610] The optional implementation of S305B can be found in the optional implementation of S207A in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0611] S306B, the source second network device sends a ninth message to the target second network device, the ninth message including the first identifier.

[0612] The optional implementation of S306B can be found in the optional implementation of S208A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0613] S307B, the target second network device sends a tenth message to the source second network device, the tenth message including the second session identifier.

[0614] The optional implementation of S307B can be found in the optional implementation of S209A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0615] S308B, the source second network device sends an eighth message to the first network device, the eighth message including the second session identifier.

[0616] The optional implementation of S308B can be found in the optional implementation of S210A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0617] S309B, the first network device sends a second message to the terminal, the second message including a second session identifier.

[0618] The optional implementation of S309B can be found in the optional implementation of S211A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0619] S310B, the terminal updates the first session identifier of the first session to the second session identifier.

[0620] The optional implementation of S310B can be found in the optional implementation of S212A in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0621] S311B, the terminal sends first information to the target second network device, the first information including a second session identifier.

[0622] The optional implementation of S311B can be found in the optional implementation of S213A in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0623] S312B, the target second network device sends a third message to the terminal, the third message including the second session identifier.

[0624] The optional implementation of S312B can be found in the optional implementation of S214A in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0625] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0626] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0627] Figure 3C is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3C, the embodiments of the present disclosure relate to a communication method, which includes:

[0628] S301C, the first network device sends a fifth message to the target second network device, the fifth message including the second identifier.

[0629] The optional implementation of S301C can be found in the optional implementation of S203B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0630] S302C, the target second network device sends a fourth message to the first network device, the fourth message including the first identifier.

[0631] The optional implementation of S302C can be found in the optional implementation of S204B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0632] S303C, the first network device sends a first message to the terminal, the first message including a first identifier and a second identifier.

[0633] The optional implementation of S303C can be found in the optional implementation of S205B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0634] S304C, the terminal updates the second identifier to the first identifier.

[0635] The optional implementation of S304C can be found in the optional implementation of S206B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0636] S305C, the first network device sends a seventh message to the source second network device, the seventh message including the first identifier.

[0637] The optional implementation of S305C can be found in the optional implementation of S207B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0638] S306C, the source second network device sends a ninth message to the target second network device, the ninth message including the first session identifier.

[0639] The optional implementation of S306C can be found in the optional implementation of S208B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0640] S307C, the target second network device sends the tenth message to the source second network device.

[0641] The optional implementation of S307C can be found in the optional implementation of S209B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0642] S308C, the second network device sends the eighth message to the first network device.

[0643] The optional implementation of S308C can be found in the optional implementation of S210B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0644] S309C, the first network device sends a second message to the terminal.

[0645] The optional implementation of S309C can be found in the optional implementation of S211B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0646] S310C, the terminal sends first information to the target second network device, the first information including a first session identifier.

[0647] The optional implementation of S310C can be found in the optional implementation of S212B in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0648] S311C, the target second network device sends a third message to the terminal, the third message including the second session identifier.

[0649] The optional implementation of S311C can be found in the optional implementation of S213B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0650] S312C, the terminal updates the first session identifier of the first session to the second session identifier.

[0651] The optional implementation of S312C can be found in the optional implementation of S214B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0652] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0653] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0654] Figure 3D is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3D, the embodiments of the present disclosure relate to a communication method, which includes:

[0655] S301D, the first network device sends a fifth message to the target second network device, the fifth message including the second identifier.

[0656] The optional implementation of S301D can be found in the optional implementation of S203B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0657] S302D, the target second network device sends a fourth message to the first network device, the fourth message including the first identifier.

[0658] The optional implementation of S302D can be found in the optional implementation of S204B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0659] S303D, the first network device sends a first message to the terminal, the first message including a first identifier and a second identifier.

[0660] The optional implementation of S303D can be found in the optional implementation of S205B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0661] S304D, the terminal updates the second identifier to the first identifier.

[0662] The optional implementation of S304D can be found in the optional implementation of S206B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0663] S305D, the first network device sends a seventh message to the source second network device, the seventh message including the first identifier.

[0664] The optional implementation of S305D can be found in the optional implementation of S207B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0665] S306D, the source second network device sends a ninth message to the target second network device, the ninth message including the first identifier.

[0666] The optional implementation of S306D can be found in the optional implementation of S208B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0667] S307D, the target second network device sends the tenth message to the source second network device.

[0668] The optional implementation of S307D can be found in the optional implementation of S209B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0669] S308D, the second network device sends the eighth message to the first network device.

[0670] The optional implementation of S308D can be found in the optional implementation of S210B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0671] S309D, the first network device sends a second message to the terminal.

[0672] The optional implementation of S309D can be found in the optional implementation of S211B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0673] S310D, the terminal sends the first information to the target second network device.

[0674] The optional implementation of S310D can be found in the optional implementation of S212B in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0675] S311D, the target second network device sends a third message to the terminal, the third message including the second session identifier.

[0676] The optional implementation of S311D can be found in the optional implementation of S213B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0677] S312D, the terminal updates the first session identifier of the first session to the second session identifier.

[0678] The optional implementation of S312D can be found in the optional implementation of S214B in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0679] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0680] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0681] Figure 3E is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3E, the present disclosure relates to a communication method, which includes:

[0682] S301E, the first network device sends a fifth message to the target second network device, the fifth message including the second identifier.

[0683] The optional implementation of S301E can be found in the optional implementation of S203B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0684] S302E, the target second network device sends a fourth message to the first network device, the fourth message including the first identifier.

[0685] The optional implementation of S302E can be found in the optional implementation of S204B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0686] S303E, the first network device sends a first message to the terminal, the first message including a first identifier and a second identifier.

[0687] The optional implementation of S303E can be found in the optional implementation of S205B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0688] S304E, the terminal updates the second identifier to the first identifier.

[0689] The optional implementation of S304E can be found in the optional implementation of S206B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0690] S305E, the first network device sends a seventh message to the source second network device, the seventh message including the first identifier.

[0691] The optional implementation of S305E can be found in the optional implementation of S207B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0692] S306E, the source second network device sends a ninth message to the target second network device, the ninth message including a second identifier.

[0693] The optional implementation of S306E can be found in the optional implementation of S208B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0694] S307E, the target second network device sends a tenth message to the source second network device, the tenth message including the first identifier.

[0695] The optional implementation of S307E can be found in the optional implementation of S209B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0696] S308E, the second network device sends an eighth message to the first network device, the eighth message including the first identifier.

[0697] The optional implementation of S308E can be found in the optional implementation of S210B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0698] S309E, the first network device sends a second message to the terminal, the second message including the first identifier.

[0699] The optional implementation of S309E can be found in the optional implementation of S211B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0700] S310E: The terminal sends first information to the target second network device, the first information including a first identifier.

[0701] The optional implementation of S310E can be found in the optional implementation of S212B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0702] S311E, the target second network device sends a third message to the terminal, the third message including the second session identifier.

[0703] The optional implementation of S311E can be found in the optional implementation of S213B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0704] In some embodiments, the target second network device sets the value of the second session identifier to be equal to that of the first identifier.

[0705] S312E, the terminal updates the first session identifier of the first session to the second session identifier.

[0706] The optional implementation of S312E can be found in the optional implementation of S214B in Figure 2B and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0707] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0708] By implementing the embodiments of this disclosure, the terminal can determine to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and then update the session executed in the first user plane connection to be executed in the second user plane connection, which can ensure the accurate execution of the session and improve communication performance.

[0709] To facilitate understanding of the embodiments of this disclosure, an exemplary embodiment is provided.

[0710] In an exemplary embodiment, the "LMF Change" procedure supports changing the serving LMF based on periodic or triggered location events during a delayed 5G core network mobile terminated location request (5GC-MT-LR) process. The mobility of the target UE may cause the serving AMF to change, making the original serving LMF unsuitable. For example, the serving LMF may be very far from the new serving AMF, resulting in higher resource utilization for AMF-to-LMF signaling, or the LMF may not be configured with information about the current access network (e.g., a cell database) to enable location for the terminal. In such cases, the serving LMF may need to be changed.

[0711] Figure 4A illustrates the process of enabling service LMF change based on the event report sent by the UE. The service LMF is LMF1.

[0712] 1. The UE executes service requests as needed.

[0713] 2. The UE sends a NAS transport message containing a supplemental service event report message to the serving AMF. The NAS transport message includes a delayed route identifier indicating LMF1.

[0714] 3. Based on operator configuration and policies, the AMF can assess and determine that LMF1 is unsuitable or unable to support network or serving cell access for the current UE's location, and determine that LMF2 is a more suitable LMF. The AMF may already have LMF2 information, for example, from previous Network Repository Function (NRF) discovery or local configuration; otherwise, the AMF will query the NRF and obtain a set of LMF profiles in response. The AMF selects a new LMF (i.e., LMF2 in this case) for the current UE's location based on the LMF serving area (consisting of one or more tracking areas (TAs)) and other relevant information.

[0715] 4. The AMF invokes the Namf_Communication_N1MessageNotify service operation to LMF1. This service operation includes the event report received in step 2. If the AMF determines in step 3 that a new LMF2 should be used, it also indicates this to LMF1.

[0716] 5. If the AMF does not indicate a new LMF in step 4, LMF1 can assess and determine, based on operator configuration and policies, that it is unsuitable or unable to support network or serving cell access for the current UE's location, and determine that LMF2 is a more suitable LMF. LMF1 may already have LMF2 information, such as from previous NRF discovery or local configuration; otherwise, LMF1 will query the NRF and obtain a set of LMF profiles in response. LMF1 selects a new LMF (i.e., LMF2 in this case) for the current UE's location based on the LMF serving area (consisting of one or more TAs) and other information listed in Section 5.1.

[0717] 6. LMF1 invokes the Nlmf_Location_LocationContextTransfer Request service operation to LMF2 to provide the UE's current location context, including the event report message received in step 4. The service operation includes the AMF identifier and all information regarding periodic or triggered location requests initially received by LMF1 from the AMF or an earlier serving LMF. The service operation may also include the current status of event reports (e.g., the number of event reports received from the UE so far and / or the duration of event reports so far), and may include location-related information for the UE, such as previous location estimates and timestamps of location estimates (if available) or location measurements.

[0718] 7. LMF2 notifies LMF1 of the result of the location context transfer operation. Then, LMF1 releases all resources of the process.

[0719] 8. LMF2 invokes the Namf_Communication_N1N2MessageTransfer service operation to the AMF to request the transmission of a supplementary service event report acknowledgment message to the UE. The event report acknowledgment indicates the change in LMF and includes a delayed route identifier indicating LMF2.

[0720] 9. The AMF forwards the event report confirmation to the UE in the NAS transmission message. The AMF also notifies LMF2 of the delivery result of the event report confirmation.

[0721] 10. If the event report requires location estimation, the LMF2 can perform the UE location and determine the UE's location. Afterward, the LMF2 retains the status information to support the UE's subsequent event reporting.

[0722] During the control plane event reporting process, the AMF or LMF1 can trigger the LMF1 change procedure. When the AMF receives an event report message from the UE, the AMF triggers the LMF change procedure, and the event report message is transmitted to LMF2 via LMF1. The AMF or LMF1 indicates the new LMF2 using the delayed routing ID of LMF2 included in the event report acknowledgment message.

[0723] In some embodiments, the UE is modified to connect to the LMF user plane.

[0724] Figure 4B shows a flowchart of modifying the secure user plane connection between the UE and the LMF. This flowchart describes the change of the LMF, but it also applies to situations where the source and target LMFs are the same. This procedure can also be used to terminate the user plane connection with the source LMF without selecting any target LMF.

[0725] 1a. [Conditional] The LMF discovers the need to change the LMF, re-establish the user plane connection between the UE and the LMF, or terminate the user plane connection, for example, after receiving an event report from the UE via the user plane, or after receiving AMF relocation information from the target AMF (the target AMF obtains the UE LCS-user plane (UP) context from the source AMF, which indicates that the UE has maintained an LCS-UP connection with the source LMF; the target AMF can use the Nlmf_Location_UPConfig request to notify the source LMF of the AMF change). The source LMF sends an Nlmf_Location_UPNotify message, which includes the connection move (termination and establishment) or the need for termination; if the connection move is requested, the message may include the target LMF identifier. The AMF's address is provided to the source LMF as the "notification target address" in the latest Nlmf_Location_UPConfig message or Nlmf_Location_UP Subscribe message.

[0726] If the request is to terminate the user plane connection, AMF will release the LCS-UP context.

[0727] Note 1: The LMF modification process is independent of the service and session continuity (SSC) mode of the protocol data unit (PDU) session and uses the dedicated data network name (DNN) for location. For SSC modes 2 / 3, the connection between the PDU session anchor (PSA) user plane function (UPF) and the LMF can be relocated as the UE moves, and the LMF can detect the need to modify the LMF to reduce user plane path delay.

[0728] 1b. [Conditionally] The AMF can perform LMF reselection based on the target LMF identifier received from the source LMF for user plane positioning, or if the UE moves to a new location (potentially outside the source LMF's service area but within the target LMF's operational area), and select a target LMF for the current UE location based on the LMF's service area, LMF user plane positioning capability information, and other relevant information. The source LMF needs to be able to establish a user plane session for positioning with the UE. After AMF relocation, the target AMF can trigger LMF reselection and LCS-UP connection modification procedures, for example, if the source LMF does not perform LMF reselection.

[0729] 2. [Conditionally] Perform a network-initiated user plane connection establishment procedure between the AMF (or target AMF), the UE, and the target LMF. The UE or source LMF may also perform a user plane connection release procedure.

[0730] 3. The message may include a request for the source LMF to terminate its connection with a specific user plane of the UE, and the target LMF identifier. Alternatively, it may include information about AMF reallocation.

[0731] Note 2: AMF relocation does not always lead to LMF reselection. AMF relocation information can be notified to LMF at any time.

[0732] 4-5. [Conditionally] If a periodic and triggered UE location event reporting context based on the user plane exists, the source LMF can invoke the Nlmf_Location_LocationContextTransfer Request service operation to the target LMF to provide the UE's current location context. The target LMF will notify the source LMF of the location context transfer operation result.

[0733] 6. [Conditionally] If the user plane connection to the source LMF is still valid, the source LMF terminates the connection to the UE.

[0734] 7. The source LMF sends an Nlmf_Location_UPConfig response message to the AMF to acknowledge the connection termination or to confirm changes made by the AMF. If this procedure is used for termination, the AMF will release the LCS-UP context upon receiving the response message.

[0735] In the user plane, event reporting messages are transmitted between the LMF and the UE via the user plane. If the UE moves to a new location (possibly outside the service area of ​​the source LMF but within the working area of ​​the target LMF) instead of receiving event reporting messages from the UE in the control plane, the AMF performs an LMF reselection.

[0736] Figure 4C shows the complete process of modifying the user plane connection through the user plane.

[0737] However, when the AMF triggers an LMF reselection, there may be ongoing processes, such as delayed MT-LR for periodically triggered location events for LCS services, or SL-MT-LR for periodically triggered location events for ranging / sidelink positioning services. The target LMF cannot send an event report acknowledgment message to the UE to notify of the LMF change because event report messages from the UE are sent to the source LMF via the user plane.

[0738] Therefore, the UE is unaware of ongoing LMF changes. The UE only knows that the user plane connection between the UE and LMF1 (source LMF) has been released. The UE has no information to associate the ongoing process / LCS session with the newly established user plane connection between the UE and LMF2 (target LMF) for event reporting procedures. The UE cannot decide whether to use the newly established user plane connection between the UE and LMF2 (target LMF) for event reporting procedures, especially when multiple user plane connections exist with one or more LMFs.

[0739] To enable the UE to associate an ongoing LCS session with a newly established user plane connection, embodiments of this disclosure propose a method for the LMF to notify the UE of a new association ID and LCS session ID for the ongoing LCS session during the user plane connection release process. When the LMF is reselected, the UE can use another user plane connection to transfer the ongoing LCS session.

[0740] Note: LMF can be replaced by SF (sensing function).

[0741] An ongoing session (e.g., a periodic, triggered event reporting process) can be an LCS service in an LMF, a ranging / sidechain positioning service in an LMF, or a sensing service in an SF.

[0742] As shown in Figure 4D, 0. The UE conducts an ongoing session (e.g., a periodic, triggered event reporting process) through the user plane connection established between the LMF and the UE.

[0743] 1.1a: The LMF detects a need to change the LMF, for example, after receiving an event report from the UE via the user plane. The LMF sends an Nlmf_Location_UPNotify message to the AMF, which includes a connection mobility indication, termination of the old connection, and establishment of a new connection, and may include the target LMF identifier.

[0744] When LMF performs LMF reselection, it may not be triggered by an event report message received from the UE via the user plane.

[0745] LMF->AMF: Nlmf_Location_UPNotify (Connection Mobility Indicator, LMF2 ID).

[0746] 1b: The AMF performs LMF reselection based on the message received from the LMF in step 1a, or detects that the UE has moved to a new location.

[0747] If a message is received from the LMF in step 1a, the AMF selects a target LMF for the current UE location based on the target LMF identifier (i.e., LMF2 ID) received from the source LMF (i.e., LMF1) for user plane positioning, the LMF service area, LMF user plane positioning capability information (e.g., LCS-UPP capability, ranging / sidelink positioning capability via user plane, sensing capability via user plane), and the LMF that maintains a user plane connection with the UE.

[0748] Alternatively, if the UE moves to a new location (possibly outside the service area of ​​the source LMF and within the service area of ​​the target LMF), the AMF can perform LMF reselection. Step 1a can be skipped.

[0749] AMF triggering LMF reselection is not triggered by receiving event report messages from the UE.

[0750] AMF selects LMF2 as the target LMF.

[0751] 2. The AMF sends an Nlmf_Location_UPConfig request to the target LMF. This message includes an LCS-UP (LCS-User Plane Connection) connection establishment indication / LCS-UP connection reconstruction indication, the source LMF ID and / or LCS association ID1, and the UE ID.

[0752] The LCS-UP connection establishment indication indicates that LMF2 establishes a user plane connection with the UE. The LCS-UP connection establishment indication can also be called the LCS-UP reconstruction indication.

[0753] The AMF also inputs the LMF association ID1 (used during the establishment of the user plane connection between LMF1 and the UE, and can be LMF1ID or other values). The LMF1 ID and / or association ID1 indicate that the source LMF is LMF1.

[0754] AMF->LMF:Nlmf_Location_UPConfig(UE ID, LCS-UP Connection Establishment Indicator / LCS-UP Connection Reconstruction Indicator, LMF1 ID, LCS Association ID1).

[0755] 3. LMF2 initiates the user plane connection establishment process with the UE's LMF. LMF2 calls Namf_Communication_N1N2MessageTransfer to the AMF to transmit the user plane connection establishment command and associated ID1.

[0756] If an LMF is received, the LMF will also include the LCS association ID1 of LMF1 in the user plane connection establishment command message. The value of LCS association ID1 can be a value used during the user plane connection establishment process between LMF1 and the UE, or it can be LMF1ID or other values. LMF1->AMF:Namf_Communication_N1N2MessageTransfer(User plane connection establishment command message (LCS association ID1), LCS association ID2).

[0757] 4. AMF maps Association ID2 to Route ID2. AMF sets the payload container type to "UPP-CMI container" and includes the user plane connection release command in the payload container, and includes Route ID2 (or routing information) in the additional information of the DL NAS TRASPORT message.

[0758] AMF->UE:DL NAS TRANSPORT (User plane connection establishment command message (LCS association ID1), route ID2).

[0759] 5. The UE receives LCS association ID 2 from the user plane connection establishment command and updates the correlation between the ongoing session and LCS association ID 2.

[0760] For example, suppose there are two ongoing sessions between the UE and LMF1 (using LCS session ID1a and LCS session ID1b). The UE updates the correlation between the ongoing session and LCS association ID2:

[0761] LCS Association ID1: LCS Session ID1a, LCS Session ID1b -> LCS Association ID2: LCS Session ID1a, LCS Session ID2b;

[0762] 6. The UE establishes a user plane connection / TLS connection with LMF2 and performs a user plane connection binding process between the UE and LMF2.

[0763] 7. The UE sets the payload container type to "UPP-CMI container" and includes the user plane connection establishment and routing ID (or routing information) completed in the payload container in the additional information of the UL NAS TRASPORT message.

[0764] UE->AMF:UL NAS TRASPORT (User plane connection established successfully message, route ID2).

[0765] 8. The AMF receives the UPP-CMI container with additional information in the UL NAS TRANSPORT message. The AMF maps route ID2 to association ID2 and calls the Namf_Communication_N1MessageNotify message to the LMF indicated by route ID2 (or association ID2). This message includes a user plane connection establishment completion message and the association ID.

[0766] UE->AMF:Namf_Communication_N1MessageNotify (User plane connection established successfully message, route ID2).

[0767] 9. The LMF indicates in the Nlmf_Location_UPNotify message that the user plane connection between the AMF, UE and LMF2 has been established.

[0768] LMF->AMF:Nlmf_Location_UPN notification (LCS-UP connection 2 established)

[0769] 10. The AMF sends an Nlmf_Location_UPConfig request to the source LMF (i.e., LMF1). This message includes an LCS-UP connection release indication, the target LMF ID (i.e., LMF2 ID), and the UE ID.

[0770] AMF->LMF:Nlmf_Location_UPConfig(UE ID, LCS-UP connection release indicator, LMF2 ID, UE ID).

[0771] 11. Due to the existence of an ongoing user plane-based periodic and triggered event reporting session, LMF1 transfers the location context / sensing context related to the ongoing session to LMF2. The source LMF invokes the Nlmf_Location_LocationContextTransfer request message to the target LMF to provide the UE's current location context.

[0772] The current parameters in the Nlmf_Location_LocationContextTransfer request message include AMF ID, delayed location type, delayed location parameters, event report message, etc.

[0773] This event reporting message should not be included in the Nlmf_Location_LocationContextTransfer request message. The presence of the event reporting message IE in the Nlmf_Location_LocationContextTransfer request message should be changed from M (mandatory) to O (optional).

[0774] Scenario a. LMF1 provides LCS session ID1 to LMF2

[0775] Optionally, the message may also include the association ID1 / LCS session ID1 of the ongoing session. If LCS session ID1 in LMF1 is provided to LMF2, then LMF2 can receive an event report message with LCS session ID2 from the UE in step 20.

[0776] In cases b, c, and d, LCS session ID 1 is not provided from LMF1 to LMF2.

[0777] .LMF1->LMF2:Nlmf_Location_LocationContextTransfer request(Location Context Data (LCS Session ID 1)).

[0778] 12. The target LMF notifies the source LMF of the location context transfer operation result.

[0779] There are four possibilities for the LCS session ID:

[0780] Case a. LMF1 provides LCS session ID1 to LMF2

[0781] If LCS session ID 1 and its corresponding location context are provided by LMF1 through LMF2, then LMF2 stores the context along with LCS session ID 1. If LCS session ID 1 is received, LMF2 can identify which session the message belongs to.

[0782] Case b. LMF2 assigns LCS session ID2 when receiving context.

[0783] Location context is received with or without LCS session ID1. LMF2 assigns a new LCS session ID2 to the received location context session. If LCS session ID2 is received, LMF2 can identify which session the message belongs to. The value of LCS session ID2 may vary from session to session, or it may be a generic value, such as the LMF2 ID, or the LCS association ID2 used in step 2. If multiple ongoing sessions exist, LMF2 can also provide LMF1 with a mapping between LCS session ID1 and LCS session ID2.

[0784] Case c. LMF2 assigns LCS session ID2 upon receiving an event report message.

[0785] Location context is received without an LCS session ID1. LMF2 does not assign a new LCS session ID2 for the received location context session. LMF2 identifies which session the message belongs to based on the Deferred location type in the Nlmf_location_LocationContextTransfer request message. LMF assigns an LCS session ID2 upon receiving an event report message.

[0786] Scenario d. The UE uses LCS association ID2 as LCS session ID2. LMF 2 will not assign any new LCS session ID.

[0787] LMF2->LMF1:Nlmf_Location_LocationContextTransfer response (success / failure indication, LCS session ID 2, mapping between LCS session ID1 and ID2).

[0788] 13. LMF1 initiates a user plane connection release procedure with the UE. The LMF calls Namf_Communication_N1N2MessageTransfer to the AMF to transmit the user plane connection release command and association ID1. If the LCS session ID2 and the mapping are received in step 5, the LMF also includes the received LCS session ID2 and the mapping to the UE.

[0789] LMF1->AMF:Namf_Communication_N1N2MessageTransfer(User plane connection release command message (LCS session ID 2, mapping), LCS association ID 1).

[0790] 14. AMF maps Association ID1 to Route ID1. AMF sets the payload container type to "UPP-CMI container" and includes the user plane connection release command in the payload container, and includes Route ID1 (or routing information) in the additional information of the DL NAS TRASPORT message.

[0791] AMF->UE:DL NAS TRANSPORT (User plane connection release command message (LCS session ID 2 + mapping), route ID 1).

[0792] 15. The UE receives the user plane connection release command.

[0793] For example, suppose there are two ongoing sessions between this UE and LMF1 (using LCS session ID1a and LCS session ID1b):

[0794] - If LCS session ID2 is included in the message (case b in step 12), the UE updates the correlation between the ongoing session ID and LCS session ID2.

[0795] LCS Association ID2: LCS Session ID1a, LCS Session ID1b -> LCS Association ID2: LCS Session ID2a, LCS Session ID2b;

[0796] If LCS session ID2 is not included in the message (cases a, c, and d), the UE does not update the correlation.

[0797] Note: Step 15 can be executed after the completion message is sent in step 17.

[0798] 16. The UE releases its user plane connection with LMF1.

[0799] 17. The UE sets the payload container type to "UPP-CMI container" and includes the user plane connection release completion in the payload container. The additional information in the UL NAS TRASPORT message includes the route ID (or route information).

[0800] UE->AMF:UL NAS TRASPORT (User plane connection release complete message, route ID1).

[0801] 18. The AMF receives a UPP-CMI container with additional information from a UL NAS TRANSPORT message. The AMF maps route ID1 to association ID1 and invokes a Namf_Communication_N1MessageNotify message, which includes a user plane connection release complete message and the association ID of the LMF indicated by route ID1 (or association ID1).

[0802] .UE->AMF:Namf_Communication_N1MessageNotify(User plane connection release complete message, route ID1).

[0803] 19. The LMF indicates in the Nlmf_Location_UPNotify message that the user plane connection between the AMF, UE and LMF has been released.

[0804] LMF->AMF:Nlmf_Location_UPN notification (LCS-UP connection 1 has been published)

[0805] 20. The UE detects an event and finds that an event report message needs to be sent. The UE includes the LCS session ID of this event reporting session.

[0806] If LCS session ID2 is received (case b), the UE includes the received LCS session ID2 in the message.

[0807] - If LCS session ID2 is not received, and LCS session ID1 is included in step 11 (case a), then the UE includes the source LCS session ID1 in the message.

[0808] - If LCS session ID2 is not received and LCS session ID1 is not included in step 11 (case d), then the UE will include the LCS association ID2 / routing ID2 received in step 4 as LCS session ID2 in the message.

[0809] - If LCS session ID2 is not received, the UE will not include any LCS session ID in the message.

[0810] The event report message is sent to LMF2 via the established user plane connection.

[0811] UE->LMF2:UL LCS-UP transmission (event report, LCS session ID1 / 2).

[0812] 21. The LMF receives UL LCS-UP transmission messages from the UE via the established user plane.

[0813] - If LCS session ID1 is included, LMF identifies the event reporting session based on LCS session ID1 in the received location context (case a);

[0814] - If LCS session ID2 is included, LMF identifies the event reporting session based on LCS session ID2 (case b).

[0815] - If LCS association ID2 is used as LCS session ID2, LMF identifies the event reporting session based on LCS association ID2 and the delay location type in the event reporting message. LMF2 can also assign a new LCS session ID2 to the event reporting session. (Case d)

[0816] - If the LCS session ID is not included in the message, LMF identifies the event reporting session based on the delay location type in the event reporting message. LMF2 also assigns a new LCS session ID2 to the event reporting session. (Case c)

[0817] 22. The LMF responds to the event reporting message using either the received LCS session ID1 / 2 or the newly assigned LCS session ID2. The LMF then performs the remaining steps of the event reporting procedure as defined.

[0818] LMF->UE:DL LCS-UP transmission (event report confirmation, LCS session ID 1 / 2)

[0819] By implementing embodiments of this disclosure, even if the service LMF changes, at least one of the LCS session, ranging session, edge positioning session, and sensing session in the user plane will not be interrupted or fail.

[0820] In this embodiment, LMF1 can provide the existing LCS session ID1 to LMF2, and LMF2 can identify the session with LCS session ID2. LMF1 can provide the UE with the LCS association ID2 of LMF2. The UE can associate the ongoing session with LCS-UP 2. LMF2 can assign a new LCS session ID2 to the existing LCS session and provide it to LMF1. LMF1 can provide the UE with the received LCS session ID2. The UE can associate the ongoing session with the new LCS session ID2. The UE can use the received LCS session ID2 or LCS association ID2 to send an event reporting message to the new LMF2. Even if the serving LMF changes, the ongoing session will not be interrupted / failed. Therefore, the accurate execution of the session can be guaranteed, and communication performance can be improved.

[0821] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0822] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0823] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute 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 relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using 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 configuring the hardware circuit 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. Furthermore, 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), or a Deep Learning Processing Unit (DPU).

[0824] Figure 5A is a schematic diagram of the structure of a terminal proposed in an embodiment of this disclosure. As shown in Figure 5A, the terminal 101 may include at least one of a transceiver module 1011, a processing module 1012, etc.

[0825] In some embodiments, the transceiver module 1011 is configured to receive a first message sent by a first network device, wherein the first message is configured to instruct the terminal to update the first user plane connection between the terminal and the source second network device to a second user plane connection between the terminal and the target second network device, and the first message is configured to instruct the terminal to establish a second user plane connection with the target second network device.

[0826] Optionally, the transceiver module 1011 is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods (e.g., the communication steps such as sending and / or receiving performed by the terminal in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), which will not be elaborated here. Optionally, the processing module 1012 is used to execute at least one of the other steps executed by the terminal 101 in any of the above methods (e.g., other steps besides the communication steps such as sending and / or receiving executed by the terminal in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), which will not be elaborated here.

[0827] Figure 5B is a schematic diagram of the structure of the first network device proposed in an embodiment of this disclosure. As shown in Figure 5B, the first network device 1021 may include at least one of a transceiver module 11, a processing module 12, etc.

[0828] In some embodiments, the transceiver module 11 is configured to send a first message to the terminal, wherein the first message is configured to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and the first message is configured to instruct the terminal to establish a second user plane connection with the target second network device.

[0829] Optionally, the transceiver module 11 is used to perform at least one of the communication steps such as sending and / or receiving performed by the first network device 1021 in any of the above methods (e.g., the communication steps such as sending and / or receiving performed by the first network device in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), which will not be elaborated here. Optionally, the processing module 12 is used to execute at least one of the other steps executed by the first network device 1021 in any of the above methods (e.g., other steps besides the communication steps such as sending and / or receiving executed by the first network device in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), which will not be elaborated here.

[0830] Figure 5C is a schematic diagram of the structure of the target second network device according to an embodiment of this disclosure. As shown in Figure 5C, the target second network device 1022 may include at least one of a transceiver module 21, a processing module 22, etc.

[0831] In some embodiments, the transceiver module 21 is configured to send a fourth message to the first network device, wherein the fourth message is configured to instruct the first network device to send a first message to the terminal, the first message is configured to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, the first message is configured to instruct the terminal to establish a second user plane connection with the target second network device, and the fourth message includes a second identifier of the source second network device and a first identifier of the target second network device.

[0832] Optionally, the transceiver module 21 is used to perform at least one of the communication steps such as sending and / or receiving performed by the target second network device 1022 in any of the above methods (e.g., the communication steps such as sending and / or receiving performed by the target second network device in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), which will not be elaborated here. Optionally, the processing module 22 is used to perform at least one of the other steps performed by the target second network device 1022 in any of the above methods (e.g., other steps besides the communication steps such as sending and / or receiving performed by the target second network device in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), which will not be elaborated here.

[0833] Figure 5D is a schematic diagram of the structure of the source second network device proposed in an embodiment of this disclosure. As shown in Figure 5D, the source second network device 1023 may include at least one of a transceiver module 31, a processing module 32, etc.

[0834] In some embodiments, the transceiver module 1031 is configured to receive a seventh message sent by the first network device, wherein the seventh message is sent by the first network device after sending a first message to the terminal, the first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, the first message is used to instruct the terminal to establish a second user plane connection with the target second network device, and the seventh message is used to instruct the source second network device to release the first user plane connection.

[0835] Optionally, the transceiver module 31 is used to perform at least one of the communication steps such as sending and / or receiving performed by the source second network device 1024 in any of the above methods (e.g., the communication steps such as sending and / or receiving performed by the source second network device in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), which will not be elaborated here. Optionally, the processing module 32 is used to perform at least one of the other steps performed by the source second network device 1024 in any of the above methods (e.g., other steps besides the communication steps such as sending and / or receiving performed by the source second network device in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), which will not be elaborated here.

[0836] In some embodiments, the transceiver module may include a sending module and / or a receiving module, which may be separate or integrated together.

[0837] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0838] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0839] Figure 6A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0840] As shown in Figure 6A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0841] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceivers 5102 perform at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., the sending and / or receiving steps in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., other steps besides sending and / or receiving in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0842] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

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

[0844] Figure 6B is a schematic diagram of the structure of the chip 5200 proposed in an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of the chip 5200 shown in Figure 6B, but it is not limited thereto.

[0845] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

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

[0847] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., the sending and / or receiving steps in S201A-S214A, S201B-S214B, S301A, S301B-S312B, S301C, S301D-S312D, S301E-S312E, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, chip 5200, memory 5203, or transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps other than sending and / or receiving in S201A to S214A, S201B to S214B, S301A, S301B to S312B, S301C, S301D to S312D, S301E to S312E, but not limited thereto).

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

[0849] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0850] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0851] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0852] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0853] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0854] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. [Corrected according to Rule 91, 05.12.2024] A communication method, characterized in that, The method is executed by a terminal and includes: The terminal receives a first message sent by a first network device, wherein the first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and the first message is used to instruct the terminal to establish the second user plane connection with the target second network device.

2. [Correction 05.12.2024 based on Rule 91] The method as described in claim 1, characterized in that, The first message includes a first identifier, wherein the method further includes: The second identifier is updated to the first identifier according to the first message, wherein the first identifier is the identifier of the target second network device, and the second identifier is the identifier of the source second network device.

3. [Correction 05.12.2024 based on Rule 91] The method as described in claim 1 or 2, characterized in that, The method further includes: The terminal receives a second message sent by the first network device, wherein the second message is used to instruct the terminal to release the first user plane connection.

4. [Correction 05.12.2024 according to Rule 91] The method as described in claim 3, characterized in that, The second message includes a second session identifier, wherein the method further includes: The first session identifier is updated to the second session identifier according to the second message, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection, and the second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

5. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 1 to 4, characterized in that, The first message is further configured to indicate that the first session update in the first user plane connection will be performed in the second user plane connection, wherein the method further includes: Based on at least one of the first message and the second message sent by the first network device, first information is sent to the target second network device through the second user plane connection, wherein the first information is information that the terminal needs to send to the target second network device when executing the first session in the second user plane connection.

6. [Corrected according to Rule 91, 05.12.2024] The method as described in claim 5, characterized in that, The first message includes a first identifier, wherein sending the first information to the target second network device via the second user plane connection according to the first message includes: The target second network device is identified based on the first identifier, and the first information is sent to the target second network device through the second user plane connection.

7. [Correction 05.12.2024 according to Rule 91] The method as described in claim 5 or 6, characterized in that, The second message includes a second session identifier, wherein sending the first information to the target second network device via the second user plane connection according to the second message includes: The first session is executed in the second user plane connection based on the second session identifier, and the first information is sent to the target second network device through the second user plane connection, wherein the second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

8. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 5 to 7, characterized in that, The method further includes: Receive a third message sent by the target second network device, wherein the third message is used to indicate that the first information has been successfully received.

9. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 5 to 8, characterized in that, The first information includes at least one of the following: The first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection; The second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection; Second session identifier allocation indication information, which is used to instruct the target second network device to allocate a second session identifier for the first session.

10. [Correction 05.12.2024 according to Rule 91] The method as described in claim 8, characterized in that, The third message includes a second session identifier, wherein the method further includes: Update the first session identifier to the second session identifier, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection.

11. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 4, 8 to 10, characterized in that, The first session identifier and the second identifier have the same value; and / or the second session identifier has the same value as the first identifier.

12. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 4 to 11, characterized in that, The first session includes at least one of the following: Sessions in location services; Sessions in ranging / lateral walkway positioning services; Sessions within the perceived service.

13. [Corrected according to Rule 91, 05.12.2024] A communication method, characterized in that, The method is executed by a first network device and includes: Send a first message to the terminal, wherein the first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, and the first message is used to instruct the terminal to establish the second user plane connection with the target second network device.

14. [Correction 05.12.2024 according to Rule 91] The method as described in claim 13, characterized in that, The first message includes a first identifier, which is the identifier of the target second network device. The first message is used to instruct the terminal to update the second identifier to the first identifier. The first identifier is the identifier of the target second network device, and the second identifier is the identifier of the source second network device.

15. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 13 or 14, characterized in that, The first message is also used to instruct the terminal to update the first session in the first user plane connection to be executed in the second user plane connection.

16. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 13 to 15, characterized in that, The method further includes: The first network device receives a fourth message sent by the target second network device, wherein the fourth message is used to instruct the first network device to send the first message to the terminal, and the fourth message includes a first identifier and a second identifier, wherein the first identifier is the identifier of the target second network device, and the second identifier is the identifier of the source second network device.

17. [Correction 05.12.2024 according to Rule 91] The method as described in claim 16, characterized in that, The method further includes: It is determined that the source second network device cannot provide services to the terminal, and the target second network device provides services to the terminal; Send a fifth message to the target second network device, wherein the fifth message is used to instruct the target second network device to send the fourth message to the first network device, and the fifth message is used to instruct the target second network device to establish a second user plane connection with the terminal. The fifth message includes a second identifier and the identifier of the terminal, wherein the second identifier is the identifier of the source second network device.

18. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 17, characterized in that, The determination that the source second network device cannot provide services to the terminal, and that the target second network device provides services to the terminal, includes: The system receives a sixth message sent by the source second network device, wherein the sixth message is used to indicate that the source second network device cannot provide services to the terminal, and the sixth message includes a first identifier, which is the identifier of the target second network device; According to the sixth message, it is determined that the source second network device cannot provide services to the terminal, and the target second network device can provide services to the terminal.

19. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 17, characterized in that, The determination that the source second network device cannot provide services to the terminal, and that the target second network device provides services to the terminal, includes: Receive a sixth message sent by the source second network device, wherein the sixth message is used to indicate that the source second network device is unable to provide services to the terminal; The target second network device is determined from one or more candidate second network devices to provide services to the terminal.

20. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 13 to 19, characterized in that, The method further includes: A seventh message is sent to the source second network device, wherein the seventh message is used to instruct the source second network device to release the first user plane connection.

21. [Correction 05.12.2024 according to Rule 91] The method as described in claim 20, characterized in that, The seventh message includes the first identifier, which is the identifier of the target second network device. The seventh message is also used to instruct the source second network device to send the context of the terminal to the target second network device.

22. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 20 or 21, characterized in that, The method further includes: The first network device receives an eighth message sent by the second source network device, wherein the eighth message is used to instruct the first network device to instruct the terminal to release the first user plane connection.

23. [Correction 05.12.2024 according to Rule 91] The method as described in claim 22, characterized in that, The eighth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

24. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 20 to 23, characterized in that, The method further includes: A second message is sent to the terminal, wherein the second message is used to instruct the terminal to release the first user plane connection.

25. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 24, characterized in that, The second message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection. The second message is also used to instruct the terminal to update the first session identifier to the second session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

26. [Corrected according to Rule 91, 05.12.2024] A communication method, characterized in that, The method is performed by the target second network device and includes: A fourth message is sent to the first network device, wherein the fourth message is used to instruct the first network device to send a first message to the terminal, the first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, the first message is used to instruct the terminal to establish the second user plane connection with the target second network device, and the fourth message includes a first identifier and a second identifier, the first identifier being the identifier of the target second network device, and the second identifier being the identifier of the source second network device.

27. [Correction 05.12.2024 according to Rule 91] The method as described in claim 26, characterized in that, The method further includes: The system receives a fifth message sent by the first network device, wherein the fifth message is used to instruct the target second network device to send the fourth message to the first network device, and the fifth message is used to instruct the target second network device to establish a second user plane connection with the terminal. The fifth message includes a second identifier and the identifier of the terminal, wherein the second identifier is the identifier of the source second network device.

28. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 26 or 27, characterized in that, The method further includes: Receive a ninth message sent by the source second network device, wherein the ninth message is used to indicate the context of the terminal; A tenth message is sent to the source second network device, wherein the tenth message is used to indicate that the context of the terminal has been successfully received.

29. [Correction 05.12.2024 according to Rule 91] The method as described in claim 28, characterized in that, The ninth message includes a first session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

30. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 28 or 29, characterized in that, The tenth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

31. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 26 to 30, characterized in that, The first message is also used to indicate that the first session update in the first user plane connection will be performed in the second user plane connection, and the method further includes: Receive the first information of the first session sent by the terminal through the second user plane connection.

32. [Correction 05.12.2024 based on Rule 91] The method as described in claim 31, characterized in that, The method further includes: A third message is sent to the terminal, wherein the third message is used to indicate that the first information has been successfully received.

33. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 31 or 32, characterized in that, The first information includes at least one of the following: The first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection; The second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection; Second session identifier allocation indication information, which is used to instruct the target second network device to allocate a second session identifier for the first session.

34. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 32 or 33, characterized in that, The third message includes a second session identifier, and the third message is also used to indicate that the first session identifier is updated to the second session identifier, wherein the first session identifier is the identifier corresponding to the first session when it is executed in the first user plane connection, and the second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

35. [Corrected according to Rule 91, 05.12.2024] A communication method, characterized in that, The method is performed by the source second network device and includes: The system receives a seventh message sent by a first network device, wherein the seventh message is sent by the first network device after sending a first message to the terminal, the first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, the first message is used to instruct the terminal to establish the second user plane connection with the target second network device, and the seventh message is used to instruct the source second network device to release the first user plane connection.

36. [Correction 05.12.2024 according to Rule 91] The method as described in claim 35, characterized in that, The method further includes: A ninth message is sent to the target second network device, wherein the ninth message is used to indicate the context of the terminal; The tenth message sent by the target second network device is received, wherein the tenth message is used to indicate that the context of the terminal has been successfully received.

37. [Correction 05.12.2024 according to Rule 91] The method as described in claim 36, characterized in that, The ninth message includes a first session identifier, which is the identifier corresponding to the first session when it is executed in the first user plane connection.

38. [Correction 05.12.2024 according to Rule 91] The method as claimed in claim 36 or 37, characterized in that, The tenth message includes a second session identifier, which is the identifier corresponding to the first session when it is executed in the second user plane connection.

39. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 35 to 38, characterized in that, The method further includes: Send an eighth message to the first network device, wherein the eighth message is used to instruct the first network device to instruct the terminal to release the first user plane connection.

40. [Correction 05.12.2024 according to Rule 91] The method as described in claim 39, characterized in that, The second session identifier is the identifier corresponding to the first session when it is executed in the second user plane connection.

41. [Correction 05.12.2024 according to Rule 91] The method as described in any one of claims 35 to 40, characterized in that, The method further includes: A sixth message is sent to the first network device, wherein the sixth message is used to indicate that the source second network device is unable to provide services to the terminal.

42. [Correction 05.12.2024 according to Rule 91] The method as described in claim 41, characterized in that, The sixth message includes the first identifier, which is the identifier of the target second network device. The sixth message is used by the first network device to determine that the source second network device cannot provide services to the terminal, and by the target second network device to provide services to the terminal.

43. [Corrected according to Rule 91, 05.12.2024] A communication method, characterized in that, include: The target second network device sends a fourth message to the first network device, wherein the fourth message is used to instruct the first network device to send a first message to the terminal, the first message is used to instruct the terminal to update the first user plane connection between the terminal and the source second network device to the second user plane connection between the terminal and the target second network device, the first message is used to instruct the terminal to establish the second user plane connection with the target second network device, and the fourth message includes a first identifier and a second identifier, wherein the second identifier is the identifier of the source second network device, and the first identifier is the identifier of the target second network device; The first network device sends a first message to the terminal; The first network device sends a seventh message to the source second network device, the seventh message being used to instruct the source second network device to release the first user plane connection.

44. [Corrected according to Rule 91, 05.12.2024] A communication device, characterized in that, The communication device is used to perform the method according to any one of claims 1 to 12, 13 to 25, 26 to 34, and 35 to 42.

45. [Corrected according to Rule 91, 05.12.2024] A communication system, characterized in that, The method includes a terminal, a first network device, a target second network device, and a source second network device, wherein the terminal is configured to implement the method of any one of claims 1 to 12, the first network device is configured to implement the method of any one of claims 13 to 25, the target second network device is configured to implement the method of any one of claims 26 to 34, and the source second network device is configured to implement the method of any one of claims 35 to 42.

46. ​​[Corrected from Rule 91, 05.12.2024] A storage medium storing instructions, characterized in that, When the instructions are executed on a communication device, the communication device performs the method as described in any one of claims 1 to 12, 13 to 25, 26 to 34, and 35 to 42.

47. [Corrected according to Rule 91, 05.12.2024] A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by a communication device, it implements the method according to any one of claims 1 to 12, 13 to 25, 26 to 34, and 35 to 42.

Images