A session management method

Abstract

An embodiment of the present application discloses a session management method, including: a terminal device establishes a first session and a second session, and the second session is a redundant session with respect to the first session; after the terminal device releases the second session, the terminal device establishes a third session that is a redundant session with respect to the first session, and the third identification information of the third session is the same as the second identification information of the second session. By reasonably allocating the identification information of the sessions, it is possible to avoid frequent updates of the session association information on the access network device due to the session release process or the new session establishment process, and reduce the signaling overhead.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a session management method and related devices. Background Art

[0002] The International Telecommunication Union (ITU) has defined multiple application scenarios for the fifth generation (5G) mobile communication system and future mobile communication systems, such as: enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine type communications (mMTC). Among them, URLLC is characterized by high reliability, low latency, and extremely high availability. It includes the following various scenarios and applications: industrial applications and control, traffic safety and control, remote manufacturing, remote training, remote surgery, etc.

[0003] In the current technology, a method for implementing URLLC through Dual Connectivity (DC) is proposed. The terminal device establishes two sessions (redundant session 1 and redundant session 2), and these two sessions are redundant sessions with each other. However, when one of the redundant sessions is released, the current technology does not stipulate how to perform session management. Summary of the Invention

[0004] In a first aspect, an embodiment of this application proposes a session management method, including:

[0005] The terminal device establishes a first session and a second session, and the second session is a redundant session with the first session. Among them, the user plane path of the first session is: terminal device, Master Radio Access Network (M-RAN), and User Plane Function (UPF) #1; the user plane path of the second session is: UE, Secondary Radio Access Network (S-RAN), and UPF #2; the first session and the second session are Protocol Data Unit (PDU) sessions. The same data packets are transmitted in each of the sessions that are redundant sessions with each other.

[0006] After the terminal device releases the second session, the terminal device establishes a third session that is a redundant session with the first session, and the third identification information of the third session is the same as the second identification information of the second session. For example, the identification information of the first session is, for example, PDU session ID 1, and the identification information of the second session is, for example, PDU session ID 2.

[0007] In the embodiments of the present application, in a scenario where not all of the multiple redundant sessions are released, the terminal device does not use the identification information of the released session among them, that is, does not allocate the identification information of the released redundant session to other sessions for use. In other words, after the terminal device allocates the identification information of the session to the redundant session, the identification information of the redundant session is only used for the redundant session, even in a scenario where the redundant session identified by the identification information has been released. For example: The first session and the second session are redundant sessions, and the second session among them is released. When the first session is not released, the terminal device does not release the identification information of the second session. When establishing a third session that is a redundant session with the first session, the identification information allocated by the terminal device for the third session is the identification information of the second session. That is, the identification information of the third session is the same as the identification information of the second session. By reasonably allocating the identification information of the session, it is possible to avoid frequent updates of the session association information on the M-RAN due to the session release process or the new session establishment process, and reduce the signaling overhead.

[0008] In combination with the first aspect, in a possible implementation manner of the first aspect, after the terminal device releases the first session and the second session, the terminal device establishes a fourth session, and the identification information of the fourth session is the first identification information or the second identification information.

[0009] In this embodiment, when all the redundant sessions are released, the identification information of the session allocated by the terminal device for the redundant session can be released. In other words, it can be used for other sessions. For example: Both the first session and the second session are released. When the terminal device establishes a fourth session, the terminal device can allocate the identification information of the first session or the identification information of the second session for the fourth session. By reasonably allocating the identification information of the session, it is possible to avoid frequent updates of the session association information on the M-RAN due to the session release process or the new session establishment process, and reduce the signaling overhead.

[0010] In combination with the first aspect, in a possible implementation manner of the first aspect, the first session association information corresponding to the first session includes the second identification information; the second session association information corresponding to the second session includes the first identification information of the first session.

[0011] In combination with the first aspect, in a possible implementation manner of the first aspect, the first session association information further includes first identification information; and / or, the second session association information further includes second identification information. There are various implementation manners for the session association information, which improves the implementation flexibility of this solution.

[0012] In combination with the first aspect, in a possible implementation manner of the first aspect, the terminal device sends a first message to the Access and Mobility Management Function (AMF), and the first message includes: a first Routing Selection Descriptor (RSD) and first session association information;

[0013] The terminal device sends a second message to the Access and Mobility Management Function (AMF), and the second message includes: a second Routing Selection Descriptor (RSD) and second session association information.

[0014] In a second aspect, an embodiment of the present application proposes a session management method, including:

[0015] The access network device receives the first session association information corresponding to the first session, where the first session association information is used to indicate that the first session is associated with the second session, and the second session and the first session are redundant sessions with each other; where the user plane path of the first session is: the terminal device, the Master Radio Access Network (M-RAN), and the User Plane Function (UPF) #1; the user plane path of the second session is: the UE, the Secondary Radio Access Network (S-RAN), and UPF #2; the first session and the second session are Protocol Data Unit (PDU) sessions. The same data packets are transmitted in each of the redundant sessions with each other.

[0016] The access network device determines that the second session is released;

[0017] The access network device updates or deletes the first session association information.

[0018] In the embodiment of the present application, in the scenario where some of the multiple redundant sessions are released, the RAN updates the session association information of the remaining unreleased sessions. For example: the first session and the second session are redundant sessions with each other. When the second session is released, the RAN updates or deletes the first session association information corresponding to the first session. By timely updating or deleting the session association information, the occupation of communication resources is reduced, and the signaling overhead caused by the failure to update the session association information in a timely manner is avoided.

[0019] In combination with the second aspect, in a possible implementation manner of the second aspect, the first session association information includes the identification information of the second session.

[0020] In combination with the second aspect, in a possible implementation manner of the second aspect, the access network device receives a request message from the Session Management Function (SMF). The request message is used to request the release of a second session, and the request message carries the identification information of a first session. The access network device updates the first session association information based on the identification information of the first session carried in the request message.

[0021] In the release process of the second session, the SMF sends a request message to the RAN through the AMF. The request message is used to request the release of the second session. Optionally, the request message carries the identification information of the first session, and this information is used to instruct the RAN to update the session association information of the first session. The identification information of the first session is included in the N2 session management information element (N2 SM information) of the request message. Exemplarily, the specific process is as follows: The SMF sends a PDU session update session management context response message (Nsmf_PDUSession_UpdateSMContext Response) to the AMF. The PDU session update session management context response message carries the identification information of the first session and the identification information of the second session. The AMF sends an N2 PDU session request message (N2 PDU session request) to the RAN. The N2 PDU session request message carries the identification information of the first session and the identification information of the second session.

[0022] For example, the identification information of the second session is, for example, PDU session ID 2, and the identification information of the first session is, for example, PDU session ID 1.

[0023] After the RAN determines that the second session is released or the RAN receives the request message from the SMF, the RAN updates or deletes the first session association information corresponding to the first session. The first session association information corresponds to the first session. The first session association information is also referred to as the PDU session pair information of the first session. The first session association information is used to indicate the association between the first session and the second session. It should be noted that the association between the first session and the second session means that the first session and the second session are redundant sessions to each other, that is, the first session and the second session transmit the same data packets. The first session association information includes the identification information of the second session. Optionally, the first session association information includes the identification information of the first session and the identification information of the second session. The SMF triggering the RAN to update the session association information improves the implementation flexibility of the method.

[0024] In combination with the second aspect, in a possible implementation manner of the second aspect, after the access network device updates the first session association information, it further includes:

[0025] The access network device receives the third session association information corresponding to the third session and the identification information of the third session sent by the session management function (SMF). The third session association information includes the identification information of the first session. The access network device determines, based on the third session association information, that the third session and the first session are redundant sessions with each other. The access network device updates the first session association information, and the updated first session association information includes the identification information of the third session.

[0026] For example, the radio access network (RAN) receives the third session association information corresponding to the third session and the identification information of the third session from the SMF. The third session association information includes the identification information of the first session, and the third session association information is used to indicate that the first session and the third session are redundant sessions with each other. Optionally, the third session association information further includes indication information of the third session.

[0027] Optionally, the RAN further receives the identification information of the first session from the SMF, and the identification information of the first session is used to indicate that the RAN updates the session association information of the first session.

[0028] After the RAN determines that the third session and the first session are redundant sessions with each other, the RAN updates the first session association information. The updated first session association information indicates that the first session and the third session are redundant sessions with each other. For example, the updated first session association information includes the indication information of the third session.

[0029] Combined with the second aspect, in a possible implementation manner of the second aspect, the first session association information further includes the identification information of the first session.

[0030] In combination with the second aspect, in a possible implementation of the second aspect, the access network device receives second session association information corresponding to the second session, and the second session association information is used to indicate that the second session is associated with the first session; the access network device updates or deletes the first session association information, including: the access network device determines that the first session and the second session are redundant sessions with each other according to the received second session association information; in response to the first session and the second session being redundant sessions with each other, the access network device updates or deletes the first session association information. In one implementation, the RAN updates the first session association information, and the updated first session association information does not include the identification information of the second session. For example: The first session association information before update includes: the identification information of the first session and the identification information of the second session. The first session association information after update includes: the identification information of the first session. In another implementation, the way for the RAN to update the first session association information includes: retaining the cell where the identification information of the second session is located in the first session association information, and setting the value of this cell to be empty. In another implementation, the RAN deletes the first session association information. By updating or deleting the first session association information in multiple ways, the implementation flexibility of the solution is improved.

[0031] In a third aspect, an embodiment of the present application provides a session management method, including:

[0032] The terminal device establishes a first session and a second session, and the second session and the first session are redundant sessions with each other; wherein, the user plane path of the first session is: the terminal device, the Master RAN (M-RAN), and the user plane function (UPF) #1; the user plane path of the second session is: the UE, the Secondary RAN (S-RAN), and the UPF #2; the first session and the second session are protocol data unit (PDU) sessions. The same data packets are transmitted in each of the redundant sessions.

[0033] The terminal device determines that the second session is released;

[0034] The terminal device sends first indication information to the access network device or the session management function, and the first indication information is used to indicate the access network device to update or delete the first session association information corresponding to the first session.

[0035] In the embodiments of the present application, when some of multiple mutually redundant sessions are released, the RAN updates or deletes the session association information of the remaining unreleased sessions. For example: The first session and the second session are mutually redundant sessions. When the second session is released, the UE, the RAN, and the SMF update the first session association information corresponding to the first session. By updating or deleting the session association information in a timely manner, the occupation of communication resources is reduced, and the signaling overhead caused by the failure to update the session association information in a timely manner is avoided.

[0036] In combination with the third aspect, in a possible implementation manner of the third aspect, the first session association information includes the identification information of the second session.

[0037] In combination with the third aspect, in a possible implementation manner of the third aspect, the first indication information includes the identification information of the first session. In combination with the third aspect, in a possible implementation manner of the third aspect, the first indication information includes the updated first session association information. There are various implementation manners of the first indication information, which improves the implementation flexibility of the solution.

[0038] In combination with the third aspect, in a possible implementation manner of the third aspect, after the terminal device determines that the second session is released, it further includes: The terminal device updates or deletes the first session association information. In one implementation manner, the terminal device updates the first session association information, and the updated first session association information does not include the identification information of the second session. For example: The first session association information before update includes: the identification information of the first session and the identification information of the second session. The first session association information after update includes: the identification information of the first session. In another implementation manner, the manner in which the terminal device updates the first session association information includes: retaining the cell where the identification information of the second session in the first session association information is located, and setting the value of this cell to be empty. In another implementation manner, the terminal device deletes the first session association information. By updating or deleting the first session association information in multiple ways, the implementation flexibility of the solution is improved.

[0039] In combination with the third aspect, in a possible implementation manner of the third aspect, the terminal device sends the third session association information of the third session and the identification information of the third session to the session management function SMF. The third session association information includes the identification information of the first session, and the third session and the first session are mutually redundant sessions.

[0040] In combination with the third aspect, in a possible implementation manner of the third aspect, the first session association information further includes the identification information of the first session.

[0041] Fourth aspect, embodiments of the present application propose a session management method, including:

[0042] The access network device receives first session association information corresponding to a first session from a session management function (SMF); wherein, the first session association information is used to indicate that the first session is associated with a second session, and the first session and the second session are redundant sessions with respect to each other.

[0043] The access network device receives first indication information from a terminal device.

[0044] The access network device updates or deletes the first session association information based on the first indication information. In one implementation, the radio access network (RAN) updates the first session association information, and the updated first session association information does not include the identification information of the second session. For example: The first session association information before the update includes: the identification information of the first session and the identification information of the second session. The first session association information after the update includes: the identification information of the first session. In another implementation, the manner in which the RAN updates the first session association information includes: retaining the cell where the identification information of the second session in the first session association information is located, and setting the value of this cell to null. In another implementation, the RAN deletes the first session association information. By updating or deleting the first session association information in multiple ways, the implementation flexibility of the solution is improved.

[0045] In the embodiments of the present application, in the scenario where some sessions among multiple redundant sessions are released, the RAN updates the session association information of the remaining unreleased sessions. For example: The first session and the second session are redundant sessions with respect to each other. When the second session among them is released, the UE, the RAN, and the SMF update the first session association information corresponding to the first session. By updating the session association information in a timely manner, the occupation of communication resources is reduced, and the signaling overhead caused by the failure to update the session association information in a timely manner is avoided.

[0046] In combination with the fourth aspect, in a possible implementation manner of the fourth aspect, the first session association information includes the identification information of the second session, and the second session association information includes the identification information of the first session.

[0047] In combination with the fourth aspect, in a possible implementation manner of the fourth aspect, the access network device sends the first indication information to the session management function (SMF) through the access and mobility management function (AMF). Exemplarily, the specific process is as follows: The RAN sends an N2 message to the AMF, and the first indication information is carried in the N2 message. The AMF sends a PDU session update session management context request message (Nsmf_PDUSession_UpdateSMContext Request) to the SMF, and the first indication information is carried in the PDU session update session management context request message.

[0048] After the SMF receives the first indication information from the UE, the SMF updates or deletes the local first session association information.

[0049] In combination with the fourth aspect, in a possible implementation of the fourth aspect, the network device receives first indication information from the terminal device, including:

[0050] The access network device receives the first indication information from the terminal device from the Session Management Function (SMF).

[0051] Exemplarily, the specific process is as follows: The SMF sends a PDU session update session management context response message (Nsmf_PDUSession_UpdateSMContext Response) to the AMF, and the first indication information is carried in the PDU session update session management context response message. The AMF sends an N2 PDU session request message (N2 PDU session request) to the RAN, and the first indication information is carried in the N2 PDU session request message.

[0052] Optionally, after the SMF receives the first indication information from the UE, the SMF updates or deletes the local first session association information.

[0053] In combination with the fourth aspect, in a possible implementation of the fourth aspect, the first indication information includes first identification information. In combination with the fourth aspect, in a possible implementation of the fourth aspect, the first indication information includes the updated first session association information, and the updated first session association information does not include the identification information of the second session.

[0054] In combination with the fourth aspect, in a possible implementation of the fourth aspect, after the network device updates the first session association information, it further includes: The access network device receives the third session association information of the third session and the third identification information of the third session sent by the Session Management Function (SMF), and the third session association information includes the identification information of the first session; The access network device determines that the third session and the first session are redundant sessions with each other based on the third session association information; The access network device updates the first session association information, and the updated first session association information includes the identification information of the third session. In a possible implementation, if the identification information of the second session is: "PDU session ID2", then the identification information of the third session is "PDU sessionID2".

[0055] In another possible implementation, the first session association information corresponding to the first session includes "ID-A", and the second session association information corresponding to the second session includes "ID-A". "ID-A" indicates that the first session and the second session are redundant sessions to each other. When the second session is released and other sessions are established, the "ID-A" is not allocated as the session association information corresponding to the other sessions, and the other sessions do not have a redundant session relationship with the first session. Only when a third session that is a redundant session to the first session is established, the third session association information corresponding to the third session created by the UE for the third session includes the "ID-A". Optionally, the "ID-A" is the unified identification information of the entire network.

[0056] In combination with the fourth aspect, in a possible implementation of the fourth aspect, the first session association information further includes the identification information of the first session.

[0057] In a fifth aspect, an embodiment of the present application provides a communication device, including:

[0058] A processing module, configured to establish a first session and a second session, where the second session is a redundant session to the first session;

[0059] The processing module is further configured to, after releasing the second session, the terminal device establishes a third session that is a redundant session to the first session, and the third identification information of the third session is the same as the second identification information of the second session.

[0060] In combination with the fifth aspect, in a possible implementation of the fifth aspect, the first session association information corresponding to the first session includes the second identification information; the second session association information corresponding to the second session includes the first identification information of the first session.

[0061] In combination with the fifth aspect, in a possible implementation of the fifth aspect, the processing module is further configured to, after releasing the first session and the second session, establish a fourth session, and the identification information of the fourth session is the first identification information or the second identification information.

[0062] In combination with the fifth aspect, in a possible implementation of the fifth aspect, the first session association information further includes the first identification information; and / or, the second session association information further includes the second identification information.

[0063] In combination with the fifth aspect, in a possible implementation of the fifth aspect,

[0064] A transceiver module, configured to send a first message to an access and mobility management function AMF, where the first message includes: a first routing selection description RSD and first session association information;

[0065] The transceiver module is further configured to send a second message to the Access and Mobility Management Function (AMF), where the second message includes: a second Routing Selection Descriptor (RSD) and second session association information.

[0066] In a sixth aspect, an embodiment of the present application provides a communication device, including:

[0067] A transceiver module, configured to receive first session association information corresponding to a first session, where the first session association information is used to indicate that the first session is associated with a second session, and the second session and the first session are redundant sessions with respect to each other;

[0068] A processing module, configured to determine that the second session is released;

[0069] The processing module is further configured to update or delete the first session association information.

[0070] In combination with the sixth aspect, in a possible implementation manner of the sixth aspect, the first session association information includes identification information of the second session.

[0071] In combination with the sixth aspect, in a possible implementation manner of the sixth aspect,

[0072] The transceiver module is further configured to receive a request message from a Session Management Function (SMF), where the request message is used to request the release of the second session, and the request message carries the identification information of the first session;

[0073] The processing module is further configured to update the first session association information based on the identification information of the first session carried in the request message.

[0074] In combination with the sixth aspect, in a possible implementation manner of the sixth aspect,

[0075] The transceiver module is further configured to receive third session association information corresponding to a third session and the identification information of the third session sent by a Session Management Function (SMF), where the third session association information includes the identification information of the first session;

[0076] The processing module is further configured to determine that the third session and the first session are redundant sessions with respect to each other based on the third session association information;

[0077] The processing module is further configured to update the first session association information, and the updated first session association information includes the identification information of the third session.

[0078] In combination with the sixth aspect, in a possible implementation manner of the sixth aspect, the first session association information further includes the identification information of the first session.

[0079] In combination with the sixth aspect, in a possible implementation manner of the sixth aspect,

[0080] The transceiver module is further configured to receive second session - associated information corresponding to a second session, where the second session - associated information is used to indicate that the second session is associated with the first session;

[0081] The processing module is further configured to update or delete the first session - associated information, including:

[0082] The processing module is further configured to determine, according to the received second session - associated information, that the first session and the second session are redundant sessions with each other;

[0083] The processing module is further configured to update or delete the first session - associated information in response to the first session and the second session being redundant sessions with each other.

[0084] In a seventh aspect, an embodiment of the present application provides a communication device, including:

[0085] The processing module is configured to establish a first session and a second session, where the second session and the first session are redundant sessions with each other;

[0086] The processing module is further configured to determine that the second session is released;

[0087] The transceiver module is further configured to send first indication information to an access network device or a session management function, where the first indication information is used to instruct the access network device to update or delete the first session - associated information corresponding to the first session.

[0088] In combination with the seventh aspect, in a possible implementation manner of the seventh aspect, the first session - associated information includes the identification information of the second session.

[0089] In combination with the seventh aspect, in a possible implementation manner of the seventh aspect, the first indication information includes the identification information of the first session.

[0090] In combination with the seventh aspect, in a possible implementation manner of the seventh aspect,

[0091] The processing module is further configured to update or delete the first session - associated information.

[0092] In combination with the seventh aspect, in a possible implementation manner of the seventh aspect, the first indication information includes the updated first session - associated information.

[0093] In combination with the seventh aspect, in a possible implementation manner of the seventh aspect,

[0094] The transceiver module is further configured to send the third session - associated information of a third session and the identification information of the third session to a session management function SMF, where the third session - associated information includes the identification information of the first session, and the third session and the first session are redundant sessions with each other.

[0095] In combination with the seventh aspect, in a possible implementation manner of the seventh aspect, the first session association information further includes the identification information of the first session.

[0096] In an eighth aspect, an embodiment of the present application provides a communication device, including:

[0097] a transceiver module, configured to receive first session association information corresponding to a first session from a session management function (SMF);

[0098] wherein the first session association information is used to indicate that the first session is associated with a second session, and the first session and the second session are redundant sessions with each other;

[0099] the transceiver module is further configured to receive first indication information from a terminal device;

[0100] a processing module, configured to update or delete the first session association information based on the first indication information.

[0101] In combination with the eighth aspect, in a possible implementation manner of the eighth aspect, the first session association information includes the identification information of the second session, and the second session association information includes the identification information of the first session;

[0102] In combination with the eighth aspect, in a possible implementation manner of the eighth aspect,

[0103] the transceiver module is further configured to send the first indication information to the session management function (SMF) through an access and mobility management function (AMF).

[0104] In combination with the eighth aspect, in a possible implementation manner of the eighth aspect,

[0105] the transceiver module is further configured to receive the first indication information from the terminal device from the session management function (SMF).

[0106] In combination with the eighth aspect, in a possible implementation manner of the eighth aspect, the first indication information includes first identification information.

[0107] In combination with the eighth aspect, in a possible implementation manner of the eighth aspect, the first indication information includes updated first session association information, and the updated first session association information does not include the identification information of the second session.

[0108] In combination with the eighth aspect, in a possible implementation manner of the eighth aspect,

[0109] the transceiver module is further configured to receive third session association information of a third session and a third identification information of the third session sent by the session management function (SMF), and the third session association information includes the identification information of the first session;

[0110] The processing module is further configured to determine, based on the third session association information, that the third session and the first session are redundant sessions with respect to each other.

[0111] The processing module is further configured to update the first session association information, and the updated first session association information includes the identification information of the third session.

[0112] Combined with the eighth aspect, in a possible implementation manner of the eighth aspect, the first session association information further includes the identification information of the first session.

[0113] In a ninth aspect, a communication device is provided for implementing the above various methods. The communication device may be the network device or the terminal device in the first aspect to the fourth aspect above, or a device including the above network device or terminal device, or a device included in the above network device or terminal device, such as a system chip. The communication device includes corresponding modules, units, or means for implementing the above methods, and the modules, units, or means may be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0114] In a tenth aspect, a communication device is provided, including: a processor and a memory; the memory is configured to store computer instructions, and when the processor executes the instructions, the communication device is caused to execute the methods in any of the above aspects. The communication device may be the network device or the terminal device in the first aspect to the fourth aspect above, or a device including the above network device or terminal device, or a device included in the above network device or terminal device, such as a system chip.

[0115] In an eleventh aspect, a communication device is provided, including: a processor; the processor is configured to be coupled to the memory and, after reading the instructions in the memory, execute the methods in any of the above aspects according to the instructions, and the memory is independent of the communication device. The communication device may be the network device or the terminal device in the first aspect to the fourth aspect above, or a device including the above network device or terminal device, or a device included in the above network device or terminal device, such as a system chip.

[0116] In a twelfth aspect, a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium. When the instructions are run on a communication device, the communication device can execute the methods in any of the above aspects. The communication device may be the network device or the terminal device in the first aspect to the fourth aspect above, or a device including the above network device or terminal device, or a device included in the above network device or terminal device, such as a system chip.

[0117] In a thirteenth aspect, a computer program product including instructions is provided. When the instructions run on a communication device, the communication device can execute the method of any of the above aspects. The communication device may be a network device or a terminal device in the first to fourth aspects above, or a device including the above network device or terminal device, or a device included in the above network device or terminal device, such as a system chip.

[0118] In a fourteenth aspect, a communication device (for example, the communication device may be a chip or a chip system) is provided. The communication device includes a processor for implementing the functions involved in any of the above aspects. In a possible design, the communication device further includes a memory for storing necessary program instructions and data. When the communication device is a chip system, it may be composed of chips or include chips and other discrete devices.

[0119] In a fifteenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is used to communicate with modules outside the chip, and the processor is used to run a computer program or instructions so that a device installed with the chip can execute the method of any of the above aspects.

[0120] Among them, for the technical effects brought by any one of the design manners in the fifth to fifteenth aspects, reference may be made to the technical effects brought by different design manners in the first, second, third, or fourth aspect above, which will not be elaborated here.

[0121] In a sixteenth aspect, a communication system is provided. The communication system includes the terminal device of the above aspect, and / or a network device. Description of the Drawings

[0122] Figure 1 It is a schematic diagram of the network architecture of a communication system;

[0123] Figure 2 It is a schematic diagram of the hardware structure of the communication device in the embodiment of the present application;

[0124] Figure 3 It is a schematic diagram of implementing URLLC in a dual-link manner in the embodiment of the present application;

[0125] Figure 4 It is a schematic diagram of the process of establishing a redundant session in the embodiment of the present application;

[0126] Figure 5 It is a schematic diagram of the process of the PDU session release process;

[0127] Figure 6 It is a schematic diagram of the process of a session management method in the embodiment of the present application;

[0128] Figure 7 It is a schematic flowchart of another session management method in the embodiment of the present application;

[0129] Figure 8 It is a schematic flowchart of another session management method in the embodiment of the present application;

[0130] Figure 9 It is a schematic diagram of an embodiment of a communication device in the embodiment of the present application;

[0131] Figure 10 It is a schematic diagram of an embodiment of a communication device in the embodiment of the present application;

[0132] Figure 11 It is a schematic diagram of an embodiment of a communication device in the embodiment of the present application;

[0133] Figure 12 It is a schematic diagram of an embodiment of a communication device in the embodiment of the present application. Detailed implementation manners

[0134] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the scope of protection of the present application.

[0135] Terms such as "first" and "second" and their corresponding term numbers in the specification, claims and the above-mentioned drawings of the present application are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, which is only a way of distinction adopted when describing objects with the same attributes in the embodiments of the present application. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, so that a process, method, system, product or device including a series of units does not have to be limited to those units, but may include other units not clearly listed or inherent to these processes, methods, products or devices.

[0136] In the description of this application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B. The "and / or" in this application is merely an association relationship describing associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of this application, "at least one item" means one or more items, and "multiple items" means two or more items. "At least one of the following (items)" or similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0137] The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th generation (5G) systems or NR, and future 6th generation communication systems, etc.

[0138] The part operated by an operator in various communication systems can be referred to as the operator network. The operator network can also be called a public land mobile network (PLMN) network, which is a network established and operated by a government or an operator approved by the government for the purpose of providing land mobile communication services to the public. It is mainly a public network where a mobile network operator (MNO) provides mobile broadband access services to users. The operator network or PLMN network described in the embodiments of the present application can be a network that meets the requirements of the 3rd generation partnership project (3GPP) standard, abbreviated as the 3GPP network. Usually, the 3GPP network is operated by an operator, including but not limited to the 5th-generation (5G) network (abbreviated as the 5G network), the 4th-generation (4G) network (abbreviated as the 4G network), or the 3rd-generation (3G) mobile communication technology network (abbreviated as the 3G network). It also includes the future 6G network. For the convenience of description, the embodiments of the present application will be described by taking the operator network (such as the mobile network operator (MNO) network) as an example.

[0139] For the convenience of understanding the embodiments of the present application, Figure 1 taking the 5G network architecture shown as an example to illustrate the application scenarios used in the present application. It can be understood that other communication networks are similar to the 5G network architecture, so they will not be elaborated. Please refer to Figure 1 , Figure 1 which is a schematic diagram of the network architecture of a communication system. The network architecture may include: a terminal device (which can also be referred to as the user equipment part), an operator network part, and a data network 104 (data network, DN) part.

[0140] The terminal device part includes the terminal device 101, which can also be referred to as a user equipment (UE). In the embodiments of the present application, the terminal device 101, as a device with wireless transceiver functions, can communicate with one or more core networks (CN) via an access network device in the (radio) access network 102 ((R)AN). The terminal device 101 can also be called an access terminal, terminal, user unit, user station, mobile station, mobile device, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent or user device, etc. The terminal device 101 can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as a ship, etc.); it can also be deployed in the air (such as an airplane, balloon, satellite, etc.). The terminal device 101 can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, smart phone, mobile phone, wireless local loop (WLL) station, personal digital assistant (PDA), a handheld device with wireless communication functions, a computing device or other devices connected to a wireless modem, vehicle-mounted device, wearable device, drone device or a terminal in the Internet of Things, vehicle-to-everything network, any form of terminal in the fifth generation (5G) network and future networks, a relay user equipment or a terminal in a future evolved public land mobile network (PLMN), etc., where the relay user equipment can be, for example, a 5G residential gateway (RG). For example, the terminal device 101 can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of the present application are not limited thereto.For ease of explanation, in the embodiments of the present application, it is described by taking the terminal device 101 including a drone and a drone remote controller as an example.

[0141] It should be noted that the drones involved in the embodiments of the present application may also include: vehicles that can autonomously travel, or vehicles that travel based on control instructions of a remote controller; ships that can autonomously navigate, or ships that navigate based on control instructions of a remote controller, etc.

[0142] The operator network may include a unified data management 108 (UDM), an access and mobility management function 105 (AMF), a session management function 106 (SMF), a policy control function 107 (PCF), a user plane function 103 (UPF), and a (R)AN 102, etc. In the above operator network, the parts other than the (R)AN part can be referred to as the core network (CN) part or the core network part. For ease of explanation, in the embodiments of the present application, the (R)AN is taken as the RAN for example.

[0143] The data network DN104, which can also be referred to as a protocol data network (PDN), is usually a network located outside the operator network, such as a third-party network. The operator network can access multiple data networks DN104. Multiple services can be deployed on the data network DN104, which can provide data and / or voice services for the terminal device. For example, the data network DN104 can be a private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminal devices. A control server for the sensors is deployed in the data network DN104, and the control server can provide services for the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server based on the instructions. Another example is that the data network DN104 can be an internal office network of a company. The mobile phones or computers of the company's employees can be terminal devices. The mobile phones or computers of the employees can access information, data resources, etc. on the company's internal office network.

[0144] The terminal device can establish a connection with the operator network through an interface provided by the operator network (such as N1, etc.), and use services such as data and / or voice provided by the operator network. The terminal device can also access the data network DN104 through the operator network, use operator services deployed on the data network DN104, and / or services provided by a third party. Among them, the above-mentioned third party can be a service provider other than the operator network and the terminal device, and can provide other data and / or voice and other services for the terminal device. Among them, the specific manifestation form of the above-mentioned third party can be specifically determined based on the actual application scenario, and is not limited here.

[0145] The following briefly introduces the network functions in the operator network.

[0146] (R)AN102 can be regarded as a sub-network of the operator network, and is an implementation system between service nodes and terminal devices in the operator network. For a terminal device to access the operator network, it first passes through (R)AN102, and then can be connected to the service nodes of the operator network through (R)AN102. The access network device 102 (RAN device) in the embodiments of the present application is a device that provides wireless communication functions for terminal devices, and can also be called a network device. The RAN device includes but is not limited to: the next generation base station node (gNB) in the 5G system, the evolved node B (eNB) in the long term evolution (LTE), the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home base station (for example, home evolved node B, or home node B, HNB), the baseband unit (BBU), the transmitting and receiving point (TRP), the transmitting point (TP), the pico base station device, the mobile switching center, or network devices in future networks, etc. In systems using different radio access technologies, the names of devices with access network device functions may be different. For ease of description, in all embodiments of the present application, the above-mentioned device that provides wireless communication functions for terminal devices is collectively referred to as an access network device or simply referred to as RAN102 or AN102. It should be understood that the specific types of access network devices are not limited herein.

[0147] The Access and Mobility Management Function AMF 105 (which can also be referred to as the AMF network element, AMF network function, or AMF network function entity) is a control plane network function provided by the operator network, responsible for access control and mobility management of the terminal device accessing the operator network, such as functions including mobile status management, allocation of user temporary identity identifiers, authentication and authorization of users, etc.

[0148] The Session Management Function SMF 106 (which can also be referred to as the SMF network element, SMF network function, or SMF network function entity) is a control plane network function provided by the operator network, responsible for managing the protocol data unit (PDU) sessions of the terminal device. A PDU session is a channel for transmitting PDUs, and the terminal device needs to transmit PDUs with the data network DN 104 through the PDU session. The establishment, maintenance, and deletion of the PDU session are the responsibilities of the SMF 106 network function. The SMF 106 network function includes session management (such as session establishment, modification, and release, including the maintenance of the tunnel between the user plane function UPF 103 and the (R)AN 102), selection and control of the UPF 103 network function, service and session continuity (SSC) mode selection, roaming, and other session-related functions.

[0149] The User Plane Function UPF 103 (which can also be referred to as the UPF network element, UPF network function, or UPF network function entity) is a gateway provided by the operator and is the gateway for communication between the operator network and the data network DN 104. The UPF 103 network function includes user plane-related functions such as packet routing and transmission, packet detection, service usage reporting, quality of service (QoS) processing, lawful interception, uplink packet detection, and downlink packet storage.

[0150] The Unified Data Management network element UDM108 (which can also be referred to as the UDM network element, UDM network function, or UDM network function entity) is a control plane function provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI), the generic public subscription identifier (GPSI) of the subscribed users in the operator's network, and credentials. Among them, the SUPI will be encrypted first during the transmission process, and the encrypted SUPI is called the subscription concealed identifier (SUCI). The information stored by UDM108 can be used for the authentication and authorization of the terminal device to access the operator's network. Among them, the subscribed users of the above operator network can specifically be users who use the services provided by the operator network. For example, users who use the mobile phone SIM card of "China Telecom", or users who use the mobile phone SIM card of "China Mobile", etc. The credentials of the above subscribed users can be: the long-term key stored in the mobile phone SIM card, or the small file stored with the information related to the encryption of the mobile phone SIM card, etc., for authentication and / or authorization. It should be noted that permanent identifiers, credentials, security contexts, authentication data (cookies), and tokens, etc., information related to authentication / verification and authorization are not distinguished and restricted for the sake of convenient description in the embodiments of this application.

[0151] The Policy Control Entity (PCF), PCF107 interacts with the AF to obtain Quality of Service (QoS) parameters, or provides QoS parameters to the AF, thereby achieving a function that can affect the application data transmission.

[0152] The Application Function AF interacts with the core network of the 3rd Generation Partnership Project (3GPP) to provide application layer services. For example: providing application layer data routing and providing access network capabilities. AF can interact with PCF107. The location of AF can be inside the 5G core network or outside the 5G core network. If AF is inside the 5G core network, then it can directly interact with PCF107. If AF is outside the 5G core network, then the Network Exposure Function (NEF) acts as an intermediate node to forward the interaction content between AF and PCF107. For example, forwarding through NEF.

[0153] Figure 1Among them, N1, N2, N3, N5, N6, N7, N8, N10, and N11 are interface serial numbers. The meanings of these interface serial numbers can be found in the meanings defined in the 3GPP standard protocol and will not be elaborated here. It should be noted that Figure 1 only an exemplary illustration is made for the terminal device as UE101 in Figure 1 and the interface names between the various network functions in

[0154] are only an example. In specific implementations, the interface names of this system architecture may also be other names, and the embodiments of this application do not make specific limitations on this.

[0155] A session management method provided in this application can be applied to various communication systems. For example, it can be the Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Long Term Evolution (LTE), or the fifth-generation (5G) communication system. It can also be an LTE-5G hybrid architecture, a 5G New Radio (NR) system, or new communication systems emerging in the future development of communications. The 5G communication system of this application can include at least one of a non-standalone (NSA) 5G communication system and a standalone (SA) 5G communication system. The communication system can also be a Public Land Mobile Network (PLMN) network, a device-to-device (D2D) network, a machine-to-machine (M2M) network, or other networks.

[0156] In addition, the embodiments of the present application can also be applicable to other future communication technologies, such as 6G, etc. The network architecture and service scenarios described in the present application are to more clearly illustrate the technical solutions of the present application, and do not constitute a limitation on the technical solutions provided by the present application. Those of ordinary skill in the art can know that with the evolution of the network architecture and the emergence of new service scenarios, various network functions involved in the present application may change, and the technical solutions provided by the present application are equally applicable to similar technical problems.

[0157] Figure 2 It is a schematic diagram of the hardware structure of the communication device in the embodiment of the present application. This communication device can be a possible implementation of the network device or the terminal device in the embodiment of the present application. As Figure 2 shown, the communication device at least includes a processor 204, a memory 203, and a transceiver 202. The memory 203 is further used to store instructions 2031 and data 2032. Optionally, the communication device may further include an antenna 206, an I / O (Input / Output) interface 210, and a bus 212. The transceiver 202 further includes a transmitter 2021 and a receiver 2022. In addition, the processor 204, the transceiver 202, the memory 203, and the I / O interface 210 are communicatively connected to each other through the bus 212, and the antenna 206 is connected to the transceiver 202.

[0158] The processor 204 can be a general-purpose processor, such as, but not limited to, a Central Processing Unit (CPU), or a dedicated processor, such as, but not limited to, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), and a Field Programmable Gate Array (FPGA), etc. The processor 204 can also be a neural processing unit (NPU). In addition, the processor 204 can also be a combination of multiple processors. In particular, in the technical solution provided by the embodiment of the present application, the processor 204 can be used to execute the relevant steps of the method for generating the key identifier in the subsequent method embodiments. The processor 204 can be a processor specifically designed to execute the above steps and / or operations, or a processor that executes the above steps and / or operations by reading and executing the instructions 2031 stored in the memory 203. The processor 204 may need to use the data 2032 during the execution of the above steps and / or operations.

[0159] The transceiver 202 includes a transmitter 2021 and a receiver 2022. In an alternative implementation, the transmitter 2021 is used to send signals via the antenna 206. The receiver 2022 is used to receive signals via at least one of the antennas 206. Specifically, in the technical solution provided in the embodiments of the present application, the transmitter 2021 can be specifically used to perform, via at least one of the antennas 206, for example, the operations performed by the receiving module or the transmitting module in a network device or a terminal device when the session management method in the low-latency and high-reliability connection scenario in the subsequent method embodiments is applied to the network device or the terminal device.

[0160] In the embodiments of the present application, the transceiver 202 is used to support the communication device to perform the aforementioned receiving and transmitting functions. The processor with processing functions is regarded as the processor 204. The receiver 2022 can also be referred to as an input port, a receiving circuit, etc., and the transmitter 2021 can be referred to as a transmitter or a transmitting circuit, etc.

[0161] The processor 204 can be used to execute the instructions stored in the memory 203 to control the transceiver 202 to receive messages and / or send messages, and complete the functions of the communication device in the method embodiments of the present application. As an implementation, the functions of the transceiver 202 can be considered to be implemented by a transceiver circuit or a dedicated chip for transceiver. In the embodiments of the present application, the transceiver 202 receiving a message can be understood as the transceiver 202 inputting a message, and the transceiver 202 sending a message can be understood as the transceiver 202 outputting a message.

[0162] The memory 203 can be various types of storage media, such as Random Access Memory (RAM), Read Only Memory (ROM), Non-Volatile RAM (NVRAM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), flash memory, optical memory, and registers, etc. The memory 203 is specifically used to store instructions 2031 and data 2032. The processor 204 can execute the steps and / or operations described in the method embodiments of the present application by reading and executing the instructions 2031 stored in the memory 203, and the data 2032 may be required during the execution of the operations and / or steps in the method embodiments of the present application.

[0163] Optionally, the communication device may further include an I / O interface 210, and the I / O interface 210 is used to receive instructions and / or data from peripheral devices, and output instructions and / or data to peripheral devices.

[0164] Next, some background technologies related to the embodiments of the present application will be introduced.

[0165] 1. Method for implementing URLLC through Dual Connectivity (DC).

[0166] Currently, a method for implementing URLLC through the DC method has been proposed. Please refer to Figure 3 , Figure 3 which is a schematic diagram of implementing URLLC through a dual-connectivity method in the embodiments of the present application. The communication system includes: UE, Master RAN (M-RAN), UPF#1, SMF#1, Secondary RAN (S-RAN), UPF#2, SMF#2, DN, and AMF. The UE accesses the data network by establishing a PDU session between the UE, RAN, UPF, and DN.

[0167] As Figure 3 shown, the UE establishes a first session and a second session, and the first session and the second session are redundant sessions with each other. Among them, the user plane path of the first session is: UE, M-RAN, and UPF#1; the user plane path of the second session is: UE, S-RAN, and UPF#2. In terms of the signaling connection, there is only one N1 connection between the UE and the AMF, and the signaling message is sent to the AMF through the M-RAN.

[0168] Next, taking the first session and the second session as examples, the establishment process of the redundant session will be introduced.

[0169] The UE determines the route selection descriptor (RSD) corresponding to the application according to the UE route selection policy (URSP). In the URLLC service scenario, this application is also called a URLLC application and is represented by the traffic descriptor (TD). The URSP can be provided by the policy control function (PCF) of the home public land mobile network (HPLMN), or can be pre-configured on the UE. For example, when there are both pre-configured URSP and URSP provided by the PCF on the UE, the UE can only use the URSP provided by the PCF.

[0170] The URSP includes a set of URSP rules. The URSP rules consist of traffic description information (TD) and routing selection description information (RSD), etc. The UE determines to initiate the establishment of a redundant session according to the URSP rules or local configuration information. In the embodiments of this application, the first session and the second session are taken as examples for illustration, and the first session and the second session are redundant sessions with respect to each other.

[0171] Please refer to Figure 4 , Figure 4 which is a schematic flowchart of establishing a redundant session in the embodiments of this application.

[0172] 401. A session establishment request message, carrying the identification information of the session.

[0173] In step 401, when the UE starts a URLLC application, or when the traffic to be transmitted by the UE has high reliability requirements, the UE initiates the establishment processes of the first session and the second session according to the URSP or local configuration information (such as the USRP rules), and the first session and the second session are PDU sessions. For example, the UE sends a session establishment request message to the SMF. For the first session, the UE sends a session establishment request message of the first session to SMF#1 through the AMF; for the second session, the UE sends a session establishment request message of the second session to SMF#2 through the AMF. SMF#1 and SMF#2 may be the same SMF or different SMFs, which is not limited herein.

[0174] The session establishment request message of the first session is included in the first message sent by the UE to the AMF. Among them, the first message carries the routing selection description first RSD and the first session association information. Among them, the routing selection description first RSD includes: data network name (DNN) #1 and single network slice selection assistance information (S-NSSAI) #1. This session association information is also called PDU session pair information. For example, this first session association information may carry the second identification information of the second session. Optionally, this first session association information further includes the first identification information of the first session. It should be noted that the first session association information may be included in the session establishment request message, and the AMF sends the first RSD to SMF#1.

[0175] The session establishment request message of the second session is included in the second message sent by the UE to the AMF. Among them, the second message carries a routing selection description, the second RSD, and the second session association information. Among them, the routing selection description, the second RSD, includes: a data network name DNN#2 and a single network slice selection assistance information S-NSSAI#2. For example, the second session association information may carry the first identification information of the first session. Optionally, the second session association information further includes the second identification information of the second session. It should be noted that the second session association information may be included in the session establishment request message, and the AMF sends the second RSD to the SMF#2. The first session association information and the second session association information may be the same or different.

[0176] The routing selection descriptions of the first session and the second session are different. For example, the above DNN#1 is different from DNN#2, or the above S-NSSAI#1 is different from S-NSSAI#2, or the above DNN#1 is different from DNN#2 and the above S-NSSAI#1 is different from S-NSSAI#2.

[0177] The identification information (such as the identification information of the first session and the identification information of the second session) includes but is not limited to a PDU session identifier (PDU session ID), and may also be a fixed value, that is, the first and second sessions correspond to the same fixed value.

[0178] It should be noted that according to step 401, it can be known that the first session and the second session are redundant sessions to each other. In this application, only the first session is taken as an example to illustrate the establishment process of the first session.

[0179] 402. Determine whether the PDU session is redundantly processed.

[0180] In step 402, the SMF determines whether the session needs to be redundantly processed according to the session establishment request message. For example, the SMF determines whether the session is redundantly processed according to the DNN (including DNN#1 and DNN#2), S-NSSAI (including S-NSSAI#1 and S-NSSAI#2), local policy, control rules (policy and charging control rule, PCC), and subscription data (the subscription data indicates whether the UE is allowed to establish a redundant session), etc.

[0181] If the session needs to be redundantly processed, the SMF determines the corresponding redundancy sequence number (RSN), and the RSN is used to indicate to the M-RAN that the session needs to be redundantly processed. Different RSNs are used to indicate that the corresponding sessions use different user plane connections.

[0182] The SMF determines the corresponding UPF based on the UPF selection strategy configured for different RSNs and operators. For example, it determines UPF#1 for the first session and UPF#2 for the second session, so as to achieve independent user plane connections between different sessions.

[0183] 403. Send the RSN, session association information, and session identification information to the RAN.

[0184] In step 403, correspondingly, the RAN saves the RSN, session association information, and session identification.

[0185] The SMF sends the RSN, the session association information received in step 401, and the session identification to the M-RAN. For example, for the first session, SMF#1 sends RSN#1, the first session association information, and the identification information of the first session to the M-RAN; for the second session, SMF#2 sends RSN#2, the second session association information, and the identification information of the second session to the M-RAN.

[0186] 404. The RAN determines the user plane connection corresponding to the session according to the session association information.

[0187] In step 404, the M-RAN determines whether the RAN resources can meet the user plane requirements of the PDU session based on the local configuration information. The M-RAN determines the corresponding user plane resources based on the received user plane connection corresponding to the session determined by the RAN according to the session association information. For example, it selects the S-RAN to establish a dual link. The session association information indicates that the first session and the second session are redundant sessions to each other, and these two sessions correspond to different user plane resources.

[0188] Exemplarily, for the first session, the M-RAN returns the M-RAN tunnel information to establish a user plane connection between the M-RAN and UPF#1. For the second session, the M-RAN returns the S-RAN tunnel information to establish a user plane connection between the S-RAN and UPF#2.

[0189] Through the above method, the UE can establish the first session and the second session that are redundant sessions to each other, as Figure 3 shown.

[0190] 2. PDU session release process.

[0191] The PDU session release procedures requested by the UE side and the network side are introduced separately below. This PDU session release procedure allows the UE to request the release of a PDU session. This procedure also allows the AMF, SMF, or PCF to initiate the PDU session release procedure. In the local breakout (LBO) roaming scenario, this procedure is the same as that in the non-roaming scenario, except that the AMF, SMF, UPF, and PCF are located in the visited network.

[0192] For ease of understanding, please refer to Figure 5 , Figure 5 the process schematic diagram of the PDU session release procedure. It should be noted that Figure 5 the messages indicated in the diagram can be related services that call the target network function.

[0193] 2.1. PDU session release procedure initiated by the UE side:

[0194] Step 1a. When the UE no longer needs the services related to this PDU session, the UE sends a PDU session release request message (PDU Session Release Request) to the RAN. The RAN forwards this PDU session release request message to the AMF, and the AMF forwards this PDU session release request message to the SMF through the PDU session update session management context message (Nsmf_PDUSession_UpdateSMContext).

[0195] 2.2. PDU session release procedure initiated by the network side:

[0196] Step 1b. The PCF initiates a session modification policy negotiation procedure (SM Policy AssociationTermination). According to the local configured policy, the PCF notifies the SMF of the information that the PDU session needs to be released through the "Npcf_SMPolicyControl_UpdateNotifyRequest". After the SMF sends a response, it then requests the PCF to delete the associated session management (SM) policy through the "Npcf_SMPolicyControl_Delete" message to release the PDU session. For the relevant definitions of this procedure, please refer to the standard TS 23.502, which will not be elaborated here.

[0197] Step 1c: When the session state between the UE and the AMF does not match, or the network slice of the UE is unavailable, the AMF sends a PDU session release session management context message (Nsmf_PDUSession_ReleaseSMContext Request) to the SMF to request the release of the PDU session.

[0198] Step 1d: The RAN sends an N2 message to the AMF. The N2 message carries the PDU session identifier (PDUsession ID) and session management information (SM information). The AMF forwards this N2 message from the RAN through a PDU session update session management context message (Nsmf_PDUSession_UpdateSMContext Request).

[0199] The RAN notifies the SMF that the materials related to this PDU session have been released. For example, all Quality of Service flows (QoS flows) of the PDU session have been released.

[0200] Step 1e: The SMF triggers a PDU session release process (PDU Session Release Trigger). For example, including but not limited to: the UDM subscription data changes; the DN requests the SMF to initiate a PDU session release process, such as when the DN needs to cancel the UE's access permission to the DN; the UE is not in the local area data network (LADN) service area; the SMF initiates a PDU session release process under the local configuration release policy scenario.

[0201] Step 1f: Before releasing the SM context, if N1 and N2 signaling information is required, the AMF can send a PDU session release session management context message with a release indication (Nsmf_PDUSession_ReleaseSMContextRequest) to the SMF to request the release of the PDU session.

[0202] After triggering the above Steps 1a - 1f, the SMF releases the Internet Protocol Address (IP address), prefix, and corresponding user plane resources of this PDU session.

[0203] According to the above Figure 4 and Figure 5From the description, it can be known that during the establishment of a redundant session, the RAN stores the identification information of the first session and the first session association information, as well as the identification information of the second session and the second session association information. However, when a redundant session (PDU session) is released, there is no agreement on how to update the session association relationship of the other redundant session. When the session association relationship of the other redundant session is not updated, it will cause unnecessary waste of communication resources. For example, the UE establishes sessions #1 and #2 that are redundant to each other, and the RAN stores session #1 and session association information #1, as well as session #2 and session association information #2. Session #2 is released. For session #1, since the session association information #1 stored by the RAN is not updated, that is, the RAN still stores session #1 and session association information #1. Suppose the UE initiates a new session establishment, and the session identifier of this new session is #2. Since the RAN stores the session association information #1, that is, the RAN considers session #1 and session #2 to be redundant sessions to each other. Then the RAN can only return the S-RAN tunnel information to ensure that session #1 and session #2 correspond to different user plane connections. This brings additional overhead to the S-RAN resources, causing unnecessary resource waste, and when the dual connection cannot be maintained (such as deleting the S-RAN), it also involves migrating session #2 to the M-RAN, resulting in additional signaling overhead. Based on this, the embodiments of this application propose a session management method, which updates the session association information corresponding to the redundant session in various ways in the scenario where the redundant session is released. In the embodiments of this application, the first session and the second session are used as examples for illustration, where the first session and the second session are redundant to each other. The first redundant session to be released is the second session. It should be noted that the sessions that are redundant to each other can also include multiple sessions. For example, sessions #1, #2, and #3 are redundant to each other. The same data packets are transmitted in each of the sessions that are redundant to each other.

[0204] First, an embodiment for the UE to implement this solution is introduced. Please refer to Figure 6 , Figure 6 is a schematic flow diagram of a session management method in an embodiment of this application. A session management method proposed in an embodiment of this application includes:

[0205] 601. Establish a first session and a second session.

[0206] In this embodiment, the UE and the network function on the network side participate in establishing the first session and the second session. The specific process of establishing the first session and the second session is the same as that of the foregoing Figure 4 shown embodiment, and will not be elaborated here.

[0207] 602. Release the second session.

[0208] In this embodiment, the UE and the network function on the network side perform the release process of the second session. The specific scenarios and processes for releasing the second session are similar to those of the foregoing Figure 5 embodiment shown, and will not be elaborated here.

[0209] 603. The terminal device allocates the identification information of the second session for the third session.

[0210] In this embodiment, after the UE determines that the second session is released, the UE and the network function on the network side establish a third session. The third session and the first session may be PDU sessions. The third session and the first session are redundant sessions to each other.

[0211] During the process of establishing the third session, the UE allocates the identification information of the third session for the third session. The identification information of the third session is the same as the identification information of the second session.

[0212] In a possible implementation manner, if the identification information of the second session is: "ID2", then the identification information of the third session is "ID2".

[0213] In another possible implementation manner, the first session association information corresponding to the first session includes "ID-A", the second session association information corresponding to the second session includes "ID-A", and "ID-A" indicates that the first session and the second session are redundant sessions to each other. When the second session is released and other sessions are established, the "ID-A" is not allocated as the session association information corresponding to other sessions, and there is no redundant session relationship between these other sessions and the first session. Only when a new third session that is a redundant session to the first session is established, the third session association information corresponding to the third session created by the UE for the third session includes the "ID-A". Optionally, the "ID-A" is the unified identification information for the entire network.

[0214] 604. Establish the third session.

[0215] In this embodiment, the UE and the network function on the network side participate in the establishment of the third session. The specific process for establishing the third session is the same as that of the foregoing Figure 4 embodiment shown, and will not be elaborated here.

[0216] 605. Release the first session.

[0217] In this embodiment, after step 601, the UE and the network function on the network side perform the release process of the first session. The specific scenarios and processes for releasing the first session are similar to those of the foregoing Figure 5 embodiment shown, and will not be elaborated here.

[0218] 606. The terminal device allocates the identification information of the first session or the identification information of the second session for the fourth session.

[0219] In this embodiment, after step 605, a fourth session is established. The specific process of establishing the fourth session is the same as that of the foregoing Figure 4 embodiment shown and will not be elaborated here.

[0220] Since both the first session and the second session, which are redundant sessions to each other, are released, the identification information of the first session and the identification information of the second session are in an available state. The UE allocates session identification information for the newly established fourth session. Among them, the session identification information of the fourth session is the identification information of the first session, or the identification information of the second session. Of course, the session identification information of the fourth session can also be other identification information other than the identification information of the first session and the identification information of the second session. That is: the identification information of the fourth session is the identification information of the first session, or the identification information of the fourth session is the identification information of the second session, or others.

[0221] It should be noted that step 606 is an optional step.

[0222] In the embodiments of the present application, in the scenario where not all of the multiple sessions that are redundant sessions to each other are released, the terminal device does not use the identification information of the released session, that is, does not allocate the identification information of the released redundant session to other sessions for use. In other words, after the terminal device allocates the identification information of the session for the redundant session, the identification information of the redundant session will not be used by other sessions that are not redundant sessions. Even in the scenario where the redundant session has been released, the identification information will be reserved for a new redundant session. For example: the first session and the second session are redundant sessions to each other. When the second session is released. Then the terminal device does not release the identification information of the second session. When establishing a third session that is redundant to the first session, the identification information allocated by the terminal device for the third session is the identification information of the second session. That is, the identification information of the third session is the same as the identification information of the second session. When all the redundant sessions are released, the identification information of the session allocated by the terminal device for the redundant session can be released. In other words, it can be used by other sessions. For example: both the first session and the second session are released. When the terminal device establishes a fourth session, the terminal device can allocate the identification information of the first session or the identification information of the second session for the fourth session. By reasonably allocating the identification information of the session, it is avoided that the session association information on the M-RAN is frequently updated due to the session release process or the new session establishment process, reducing the signaling overhead.

[0223] Please refer to Figure 7 , Figure 7 which is a schematic flowchart of another session management method in the embodiments of the present application. A session management method proposed in the embodiments of the present application includes:

[0224] 701. Establish a first session and a second session.

[0225] In this embodiment, it is the same as the aforementioned step 601 and will not be elaborated here.

[0226] 702. Release the second session.

[0227] In this embodiment, it is the same as the aforementioned step 602 and will not be elaborated here.

[0228] 703. The RAN determines that the second session is released.

[0229] In this embodiment, after entering the release process of the second session in step 702, if the RAN determines that the second session is released, then step 705 is entered.

[0230] 704. The RAN receives a request message from the SMF.

[0231] In this embodiment, in the release process of the second session in step 702, the SMF sends a request message to the RAN through the AMF. This request message is used to request the release of the second session. Optionally, the request message carries the identification information of the first session, which is used to instruct the RAN to update the session association information of the first session. The identification information of the first session is included in the N2 session management cell (N2 SM information) of the request message. Exemplarily, the specific process is as follows: The SMF sends a PDU session update session management context response message (Nsmf_PDUSession_UpdateSMContextResponse) to the AMF. The PDU session update session management context response message carries the identification information of the first session and the identification information of the second session. The AMF sends an N2 PDU session request message (N2 PDU session request) to the RAN. The N2 PDU session request message carries the identification information of the first session and the identification information of the second session.

[0232] For example, the identification information of the second session is, for example, PDU session ID 2, and the identification information of the first session is, for example, PDU session ID 1.

[0233] After the RAN receives the request message from the SMF, step 705 is entered.

[0234] It should be noted that step 704 is an optional step.

[0235] 705. The RAN updates or deletes the first session association information.

[0236] In this embodiment, the RAN receives the second session association information corresponding to the second session, and the second session association information can be sent by the SMF through the AMF. The RAN determines that the first session and the second session are redundant sessions with each other according to the second session association information.

[0237] After the RAN determines that the second session is released or the RAN receives a request message from the SMF, the RAN updates or deletes the first session association information corresponding to the first session. The first session association information corresponds to the first session. The first session association information is also referred to as the PDU session pair information of the first session. The first session association information is used to indicate the association between the first session and the second session. It should be noted that the association between the first session and the second session means that the first session and the second session are redundant sessions with each other, that is, the first session and the second session transmit the same data packets. The first session association information includes the identification information of the second session. Optionally, the first session association information includes the identification information of the first session and the identification information of the second session.

[0238] In one implementation manner, the RAN updates the first session association information, and the updated first session association information does not include the identification information of the second session. For example: the first session association information before update includes: the identification information of the first session and the identification information of the second session. The updated first session association information includes: the identification information of the first session.

[0239] In another implementation manner, the way for the RAN to update the first session association information includes: retaining the cell where the identification information of the second session in the first session association information is located, and setting the value of the cell to be empty.

[0240] In another implementation manner, the RAN deletes the first session association information.

[0241] 706. The RAN receives the third session association information corresponding to the third session and the identification information of the third session from the SMF.

[0242] In this embodiment, after step 701, the RAN receives the third session association information corresponding to the third session and the identification information of the third session from the SMF. The third session association information includes the identification information of the first session, and the third session association information is used to indicate that the first session and the third session are redundant sessions with each other. Optionally, the third session association information further includes the indication information of the third session.

[0243] Optionally, the RAN also receives the identification information of the first session from the SMF, and the identification information of the first session is used to indicate that the RAN updates the session association information of the first session.

[0244] It should be noted that step 706 is an optional step.

[0245] After the RAN determines that the third session and the first session are redundant sessions to each other in step 707, it updates the first session association information.

[0246] In this embodiment, after step 706, when the RAN determines that the third session and the first session are redundant sessions to each other, the RAN updates the first session association information. The updated first session association information indicates that the first session and the third session are redundant sessions to each other. For example, the updated first session association information includes the indication information of the third session.

[0247] It should be noted that step 707 is an optional step.

[0248] In the embodiments of the present application, in the scenario where some sessions among multiple sessions that are redundant sessions to each other are released, the RAN updates the session association information of the remaining unreleased sessions. For example: The first session and the second session are redundant sessions to each other. When the second session is released, the RAN updates the first session association information corresponding to the first session. By updating the session association information in a timely manner, the occupation of communication resources is reduced, and the signaling overhead caused by the failure to update the session association information in a timely manner is avoided.

[0249] Please refer to Figure 8 , Figure 8 which is a schematic flow diagram of another session management method in the embodiments of the present application. A session management method proposed in the embodiments of the present application includes:

[0250] 801. Establish a first session and a second session.

[0251] Step 801 is the same as the foregoing step 601 and will not be elaborated here.

[0252] 802. Release the second session.

[0253] Step 802 is the same as the foregoing step 602 and will not be elaborated here.

[0254] 803. The UE determines that the second session is released.

[0255] In this embodiment, in the process of entering the release process of the second session in step 802, the UE determines that the second session is released.

[0256] It should be noted that this step can also be described as: The UE initiates a session release request, or the UE receives a session release command.

[0257] After step 803, there are two implementation solutions respectively: that is, step 804-805 are executed after step 803, or step 806-807 are executed after step 803. It should be noted that whether step 804-805 are executed or step 806-807 are executed, the UE will execute step 808. The time sequence of executing step 808 after step 803 is not restricted here.

[0258] 804. The UE sends a first indication message to the SMF.

[0259] In this embodiment, after step 803, the UE sends a first indication message to the SMF, and the first indication message is used to indicate the RAN to update or delete the first session association information corresponding to the first session. For example, for the first session, the UE initiates a session modification process, and in this process, the UE sends a first indication message to the SMF. This first indication message may be included in the session modification request.

[0260] In one implementation, the first indication message includes the identification information of the first session.

[0261] In another implementation, after step 803, step 808 (the UE updates or deletes the first session association information) is executed. After step 808 is executed, step 804 is executed. The first indication message includes the updated first session association information. This updated first session association information does not include the identification information of the second session.

[0262] Optionally, the UE sends this first indication message to the SMF through a session modification request message.

[0263] 805. The SMF sends the first indication message to the RAN through the AMF.

[0264] In this embodiment, after step 804, when the SMF receives the first indication message, the SMF sends the first indication message to the RAN through the AMF.

[0265] Exemplarily, the specific process is as follows: The SMF sends a PDU session update session management context response message (Nsmf_PDUSession_UpdateSMContext Response) to the AMF, and the first indication message is carried in this PDU session update session management context response message. The AMF sends an N2 PDU session request message (N2 PDU session request) to the RAN, and the first indication message is carried in this N2 PDU session request message.

[0266] Optionally, after receiving the first indication information from the UE, the SMF updates or deletes the first session association information locally. For example, the manner of updating or deleting the first session association information is similar to that in step 705 described above and will not be elaborated here.

[0267] 806. The UE sends the first indication information to the RAN.

[0268] In this embodiment, after step 803, the UE sends the first indication information to the SMF. The first indication information is used to indicate the RAN to update or delete the first session association information corresponding to the first session.

[0269] For example, the first indication information is sent to the RAN through an air interface message. The air interface message may be a radio resource control (RRC) message, etc., which is not limited here.

[0270] In one implementation manner, the first indication information includes the identification information of the first session and is used to indicate the RAN to update the session association information of the first session.

[0271] In another implementation manner, after step 803, step 808 (the UE updates or deletes the first session association information) is executed. After step 808 is executed, step 806 is executed. The first indication information includes the updated first session association information. The updated first session association information does not include the identification information of the second session.

[0272] 807. The RAN sends the first indication information to the SMF through the AMF.

[0273] In this embodiment, after step 806, the RAN may also send the first indication information to the SMF through the AMF.

[0274] Exemplarily, the specific process is as follows: The RAN sends an N2 message to the AMF, and the first indication information is carried in the N2 message. The AMF sends a PDU session update session management context request message (Nsmf_PDUSession_UpdateSMContext Request) to the SMF, and the first indication information is carried in the PDU session update session management context request message.

[0275] After receiving the first indication information from the UE, the SMF updates or deletes the first session association information locally. For example, the manner of updating or deleting the first session association information is similar to that in step 705 described above and will not be elaborated here.

[0276] It should be noted that step 807 is an optional step.

[0277] 808. The UE updates or deletes the first session association information.

[0278] In this embodiment, the UE updates or deletes the first session association information locally. For example, the manner of updating or deleting the first session association information is similar to that in step 705 described above, and will not be elaborated here.

[0279] It should be noted that this step 808 is an optional step.

[0280] 809. The RAN updates or deletes the first session association information.

[0281] In this embodiment, after step 805 or after step 806, the RAN updates or deletes the first session association information locally. For example, the manner of updating or deleting the first session association information is similar to that in step 705 described above, and will not be elaborated here.

[0282] 810. The UE sends the third association information of the third session and the identification information of the third session to the SMF.

[0283] In this embodiment, after step 803, the UE sends the third session association information corresponding to the third session and the identification information of the third session to the SMF. The third session association information includes the identification information of the first session, and the third session association information is used to indicate that the first session and the third session are redundant sessions to each other. Optionally, the third session association information further includes the indication information of the third session.

[0284] 811. The RAN receives the third session association information corresponding to the third session and the identification information of the third session from the SMF.

[0285] In this embodiment, the SMF sends the third session association information corresponding to the third session and the identification information of the third session to the RAN through the AMF.

[0286] 812. The RAN updates the first session association information, and the updated first session association information includes the identification information of the third session.

[0287] In this embodiment, after the RAN determines that the third session and the first session are redundant sessions to each other, the RAN updates the first session association information. The updated first session association information indicates that the first session and the third session are redundant sessions to each other. For example, the updated first session association information includes the indication information of the third session.

[0288] It should be noted that steps 810 - 812 are optional steps.

[0289] In the embodiments of the present application, when some of multiple mutually redundant sessions are released, the RAN updates the session association information of the remaining unreleased sessions. For example, the first session and the second session are mutually redundant sessions. When the second session is released, the UE, the RAN, and the SMF update the first session association information corresponding to the first session. By updating the session association information in a timely manner, the occupancy of communication resources is reduced, and the signaling overhead caused by the failure to update the session association information in a timely manner is avoided.

[0290] The above mainly introduces the solution provided by the embodiments of the present application from the perspective of methods. It can be understood that in order for a communication device (network device or terminal device) to implement the above functions, it includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, in combination with the modules and algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0291] The embodiments of the present application can divide the communication device into function modules according to the above method examples. For example, each function module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software function module. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there may be other division methods in actual implementation.

[0292] The following will describe the communication device in the present application in detail. Please refer to Figure 9 , Figure 9 which is a schematic diagram of an embodiment of the communication device in the embodiments of the present application. The communication device can be deployed in a terminal device. The communication device 900 includes:

[0293] A processing module 901, configured to establish a first session and a second session, where the second session is mutually redundant with the first session;

[0294] The processing module 901 is further configured to, after releasing the second session, the terminal device establishes a third session that is mutually redundant with the first session, and the third identification information of the third session is the same as the second identification information of the second session.

[0295] In a possible implementation, the first session association information corresponding to the first session includes second identification information; the second session association information corresponding to the second session includes the first identification information of the first session.

[0296] In a possible implementation, the processing module 901 is further configured to, after releasing the first session and the second session, establish a fourth session, and the identification information of the fourth session is the first identification information or the second identification information.

[0297] In a possible implementation, the first session association information further includes the first identification information; and / or, the second session association information further includes the second identification information.

[0298] In a possible implementation, the transceiver module 902 is configured to send a first message to the Access and Mobility Management Function (AMF), where the first message includes: a first Routing Selection Descriptor (RSD) and the first session association information;

[0299] The transceiver module 902 is further configured to send a second message to the Access and Mobility Management Function (AMF), where the second message includes: a second Routing Selection Descriptor (RSD) and the second session association information.

[0300] Please refer to Figure 10 , Figure 10 for a schematic diagram of an embodiment of the communication device in the embodiments of the present application. The communication device may be deployed in a network device. The communication device 1000 includes:

[0301] The transceiver module 1001 is configured to receive the first session association information corresponding to the first session, where the first session association information is used to indicate that the first session is associated with the second session, and the second session and the first session are redundant sessions with respect to each other;

[0302] The processing module 1002 is configured to determine that the second session is released;

[0303] The processing module 1002 is further configured to update or delete the first session association information.

[0304] In a possible implementation, the first session association information includes the identification information of the second session.

[0305] In a possible implementation, the transceiver module 1001 is further configured to receive a request message from the Session Management Function (SMF), where the request message is used to request the release of the second session, and the request message carries the identification information of the first session;

[0306] The processing module 1002 is further configured to update the first session association information based on the identification information of the first session carried in the request message.

[0307] In a possible implementation,

[0308] The transceiver module 1001 is further configured to receive the third session association information corresponding to the third session and the identification information of the third session sent by the session management function SMF, where the third session association information includes the identification information of the first session;

[0309] The processing module 1002 is further configured to determine, based on the third session association information, that the third session and the first session are redundant sessions to each other;

[0310] The processing module 1002 is further configured to update the first session association information, and the updated first session association information includes the identification information of the third session.

[0311] In a possible implementation manner, the first session association information further includes the identification information of the first session.

[0312] In a possible implementation manner,

[0313] The transceiver module 1001 is further configured to receive the second session association information corresponding to the second session, where the second session association information is used to indicate that the second session is associated with the first session;

[0314] The processing module 1002 is further configured to update or delete the first session association information, including:

[0315] The processing module 1002 is further configured to determine, according to the received second session association information, that the first session and the second session are redundant sessions to each other;

[0316] The processing module 1002 is further configured to update or delete the first session association information in response to the first session and the second session being redundant sessions to each other.

[0317] Please refer to Figure 11 , Figure 11 which is a schematic diagram of an embodiment of the communication device in the embodiments of the present application. The communication device may be deployed in a terminal device. The communication device 1100 includes:

[0318] The processing module 1101 is configured to establish a first session and a second session, where the second session and the first session are redundant sessions to each other;

[0319] The processing module 1101 is further configured to determine that the second session is released;

[0320] The transceiver module 1102 is further configured to send a first indication message to an access network device or a session management function, where the first indication message is used to indicate that the access network device updates or deletes the first session association information corresponding to the first session.

[0321] In a possible implementation manner, the first session association information includes the identification information of the second session.

[0322] In a possible implementation, the first indication information includes the identification information of the first session.

[0323] In a possible implementation,

[0324] The processing module 1101 is further configured to update or delete the first session association information.

[0325] In a possible implementation, the first indication information includes the updated first session association information.

[0326] In a possible implementation,

[0327] The transceiver module 1102 is further configured to send the third session association information of the third session and the identification information of the third session to the session management function SMF, where the third session association information includes the identification information of the first session, and the third session and the first session are redundant sessions to each other.

[0328] In a possible implementation, the first session association information further includes the identification information of the first session.

[0329] Please refer to Figure 12 , Figure 12 which is a schematic diagram of an embodiment of the communication device in the embodiments of the present application. The communication device can be deployed in a network device. The communication device 1200 includes:

[0330] The transceiver module 1201 is configured to receive the first session association information corresponding to the first session from the session management function SMF;

[0331] wherein the first session association information is used to indicate that the first session is associated with the second session, and the first session and the second session are redundant sessions to each other;

[0332] The transceiver module 1201 is further configured to receive the first indication information from the terminal device;

[0333] The processing module 1202 is configured to update or delete the first session association information based on the first indication information.

[0334] In a possible implementation, the first session association information includes the identification information of the second session, and the second session association information includes the identification information of the first session;

[0335] In a possible implementation,

[0336] The transceiver module 1201 is further configured to send the first indication information to the session management function SMF through the access and mobility management function AMF.

[0337] In a possible implementation,

[0338] The transceiver module 1201 is further configured to receive first indication information from a session management function (SMF) that is sent from a terminal device.

[0339] In a possible implementation manner, the first indication information includes first identification information.

[0340] In a possible implementation manner, the first indication information includes updated first session association information, and the updated first session association information does not include the identification information of a second session.

[0341] In a possible implementation manner,

[0342] The transceiver module 1201 is further configured to receive third session association information of a third session and third identification information of the third session that are sent by the session management function (SMF), where the third session association information includes the identification information of a first session;

[0343] The processing module 1202 is further configured to determine, based on the third session association information, that the third session and the first session are redundant sessions to each other;

[0344] The processing module 1202 is further configured to update the first session association information, and the updated first session association information includes the identification information of the third session.

[0345] In a possible implementation manner, the first session association information further includes the identification information of the first session.

[0346] It should be noted that for the information interaction, execution process, etc. between the modules / or components of the communication device, Figures 4 - 8 it is based on the same concept as the corresponding method embodiment in this application. For specific content, reference can be made to the description in the foregoing method embodiments shown in this application, and details are not described herein again.

[0347] It should be noted that for the specific implementation manner of the communication device and the beneficial effects brought, reference can be made to Figures 4 - 8 the description in the corresponding method embodiments, and details are not described herein one by one.

[0348] An embodiment of this application further provides a processing device, where the processing device includes a processor and an interface; the processor is configured to execute the session management method in the low-latency and high-reliability connection scenario of any of the foregoing method embodiments.

[0349] It should be understood that the foregoing processing device may be a chip, and the processor may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor, and is implemented by reading software code stored in a memory. The memory may be integrated in the processor or may exist independently outside the processor.

[0350] Among them, "implemented by hardware" means that the functions of the above-mentioned modules or units are implemented by a hardware processing circuit that does not have the function of processing program instructions. The hardware processing circuit can be composed of discrete hardware components or can be an integrated circuit. To reduce power consumption and size, the form of an integrated circuit is usually adopted for implementation. The hardware processing circuit can include an ASIC (application-specific integrated circuit), or a PLD (programmable logic device); among them, the PLD can further include an FPGA (field programmable gate array), a CPLD (complex programmable logic device), and so on. These hardware processing circuits can be a separately packaged semiconductor chip (such as packaged as an ASIC); they can also be integrated with other circuits (such as a CPU, a DSP) and then packaged into a semiconductor chip. For example, multiple hardware circuits and a CPU can be formed on a silicon substrate and separately packaged into a chip. Such a chip is also called an SoC, or a circuit for implementing the FPGA function and a CPU can be formed on a silicon substrate and separately enclosed into a chip. Such a chip is also called an SoPC (system on a programmable chip).

[0351] This application also provides a communication system, which includes at least one or more of a terminal device and a network device.

[0352] This application embodiment also provides a computer-readable storage medium, including instructions, which when running on a computer, cause the computer to control a network device to execute any implementation manner shown in the foregoing method embodiment.

[0353] This application embodiment also provides a computer program product, which includes computer program code, and when the computer program code runs on a computer, causes the computer to execute any implementation manner shown in the foregoing method embodiment.

[0354] This application embodiment also provides a chip system, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the chip executes any implementation manner shown in the foregoing method embodiment.

[0355] The embodiments of the present application also provide a chip system, including a processor. The processor is used to call and run a computer program, so that the chip executes any implementation manner shown in the foregoing method embodiments.

[0356] In addition, it should be noted that the device embodiments described above are only illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, in the attached drawings of the device embodiments provided in the present application, the connection relationship between the modules indicates that they have a communication connection, which can be specifically implemented as one or more communication buses or signal lines.

[0357] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware. Of course, it can also be implemented by dedicated hardware including application-specific integrated circuits, dedicated CPUs, dedicated memories, dedicated components, etc. Generally, functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structures used to implement the same function can also be various, such as analog circuits, digital circuits or dedicated circuits. However, for the present application, in more cases, software program implementation is a better implementation manner. Based on such an understanding, the technical solution of the present application, in essence, or the part that makes a contribution to the prior art, can be embodied in the form of a software product. The computer software product is stored in a readable storage medium, such as a floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disc of a computer, and includes several instructions for causing a computer device to execute the methods described in the various embodiments of the present application.

[0358] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product.

[0359] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from a website, computer, communication device, computing device, or data center to another website, computer, communication device, computing device, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a communication device or a data center that includes one or more integrated available media. The available medium may be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

[0360] It should be understood that the term "one embodiment" or "an embodiment" mentioned throughout the specification means that a particular feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Therefore, the appearances of the phrases "in one embodiment" or "in an embodiment" throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that in various embodiments of the present application, the order numbers of the above processes do not indicate the order of execution. The order of execution of each process should be determined by its function and internal logic and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0361] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the components and steps of the examples have been generally described according to their functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present application.

[0362] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0363] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of devices or units can be in electrical, mechanical, or other forms.

[0364] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0365] In addition, each functional unit in various embodiments of the present application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0366] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in various embodiments of the present application.

Claims

1. A session management method, characterized in that, including: The terminal device establishes a first session and a second session, and the second session is a redundant session with respect to the first session; After the terminal device releases the second session, the terminal device establishes a third session that is a redundant session with respect to the first session. The third identification information of the third session is the same as the second identification information of the second session. The third identification information and the second identification information are allocated by the terminal device. The second identification information is used to identify the second session, and the third identification information is used to identify the third session.

2. The method according to claim 1, wherein: The first session association information corresponding to the first session includes the second identification information; The second session association information corresponding to the second session includes the first identification information of the first session.

3. The method according to claim 2, wherein The method further includes: After the terminal device releases the first session and the second session, the terminal device establishes a fourth session, and the identification information of the fourth session is the first identification information or the second identification information.

4. The method according to claim 2 or 3, wherein: The first session association information further includes the first identification information; and / or, the second session association information further includes the second identification information.

5. The method according to claim 2 or 3, wherein: The terminal device sends a first message to the Access and Mobility Management Function (AMF). The first message includes: a first Routing Selection Descriptor (RSD) and the first session association information; The terminal device sends a second message to the Access and Mobility Management Function (AMF). The second message includes: a second Routing Selection Descriptor (RSD) and the second session association information.

6. A communication device, characterized in that, including: A processing module, configured to establish a first session and a second session, and the second session is a redundant session with respect to the first session; The processing module is further configured to, after releasing the second session, the communication device establishes a third session that is a redundant session with respect to the first session. The third identification information of the third session is the same as the second identification information of the second session. The third identification information and the second identification information are allocated by the communication device. The second identification information is used to identify the second session, and the third identification information is used to identify the third session.

7. The communication device according to claim 6, wherein: The first session association information corresponding to the first session includes the second identification information; The second session association information corresponding to the second session includes the first identification information of the first session.

8. The communication device according to claim 7, wherein The device further includes: The processing module is further configured to, after releasing the first session and the second session, the communication device establishes a fourth session, and the identification information of the fourth session is the first identification information or the second identification information.

9. The communication device according to claim 7 or 8, wherein: The first session association information further includes the first identification information; and / or, the second session association information further includes the second identification information.

10. The communication device according to claim 7 or 8, characterized in that, The communication device further includes a transceiver module; The transceiver module is configured to send a first message to an Access and Mobility Management Function (AMF), where the first message includes: a first Routing Selection Descriptor (RSD) and the first session association information; The transceiver module is further configured to send a second message to the Access and Mobility Management Function (AMF), where the second message includes: a second Routing Selection Descriptor (RSD) and the second session association information.

11. A communication device, characterized in that, The communication device includes: a processor; The processor is configured to execute computer programs or instructions stored in a memory, so that the communication device executes the method according to any one of claims 1-5.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium has program instructions that, when directly or indirectly executed, cause the method according to any one of claims 1-5 to be implemented.

13. A chip system, characterized in that, The chip system includes at least one processor, and the processor is configured to execute computer programs or instructions stored in a memory. When the computer programs or the instructions are executed in the at least one processor, the method according to any one of claims 1-5 is caused to be implemented.

Images