Communication method and device

Abstract

This application provides a communication method and apparatus. The method includes: a session management function network element initiates a procedure of a first operation for a first session; in the process of the session management function network element performing the first operation, the session management function network element receives a request from an access and mobility management function network element to establish user plane resources for the first session; and the session management function network element determines a subsequent procedure based on the first operation. Thus, the session management function network element determines a subsequent operation procedure based on the first operation, thereby effectively ensuring the smoothness of user experience and service process.

Description

[Technical field]

[0002] TECHNICAL FIELD Embodiments of the present application relate to the field of wireless communication, and in particular to a communication method and apparatus. [Background technology]

[0003] In a communication system, a user equipment (UE) and a network side device may perform different operations for the same session. For example, in 5G, when a UE needs to transmit uplink data, the UE may trigger a request to establish user plane resources. When a network side device determines that a protocol data unit (PDU) session needs to be modified or released, the network side device may initiate a procedure to modify or release the PDU session. Thus, there may be a scenario in which a procedure to request to establish user plane resources initiated by a UE for the same PDU session conflicts with a procedure to modify or release the PDU session initiated by a network side device. In the above conflict scenario, each of the terminal device and the session management function network element may wait for a response message of a request operation initiated by itself until their respective timers expire. This affects the service process and the user experience. Summary of the Invention

[0004] The embodiments of this application provide a communication method and apparatus to solve the problem of conflicting operations initiated by a UE and a network side device for the same PDU session.

[0005] According to a first aspect, the application provides a communication method, the method including: a session management function network element initiating a procedure of a first operation for a first session, the session management function network element receiving a request from an access and mobility management function network element to establish user plane resources for the first session in the process of performing the first operation, the session management function network element determining a subsequent procedure based on a type of the first operation.

[0006] According to the above method, the session management function network element can determine a subsequent operation procedure based on the type of the first operation, thereby effectively ensuring the smoothness of user experience and service process.

[0007] In a possible design, the first operation is to modify the first session, and when the session management function network element determines a subsequent procedure based on the type of the first operation, the session management function network element aborts the procedure to modify the first session and performs a procedure to establish user plane resources for the first session.

[0008] According to the above design, the session management function network element aborts the procedure of modifying the first session and executes the procedure of establishing user plane resources for the first session. In this way, it is possible to avoid the case where the terminal device and the session management function network element each wait for a response message for a request operation initiated by itself, which causes their respective timers to expire.

[0009] In a possible design, the session management function network element stops a first timer, where the first timer includes a timer waiting for a response message to modify the first session.

[0010] In a possible design, after the session management function network element completes the procedure for establishing user plane resources for the first session, the session management function network element resumes the procedure for modifying the first session.

[0011] According to the above design, after completing the procedure of establishing user plane resources for the first session, the session management function network element may resume the procedure of modifying the first session.

[0012] In a possible design, when a session management function network element performs a procedure to establish user plane resources for a first session, the session management function network element sends a first message to an access and mobility management function network element, where the first message indicates successful establishment of user plane resources for the first session.

[0013] In a possible design, the first message is a session management context update response message, and the session management context update response message includes one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that user plane resources for the first session are enabled, and the session management information includes relevant parameters for establishing user plane resources for the first session.

[0014] In a possible design, the first operation is to release the first session, and when the session management function network element determines a subsequent procedure based on the type of the first operation, the session management function network element rejects the request to establish user plane resources for the first session and continues to execute the procedure to release the first session.

[0015] According to the above design, the session management function network element rejects the request to establish user plane resources for the first session and continues to execute the procedure to release the first session. In this way, it is possible to avoid the case where the terminal device and the session management function network element each wait for a response message for a request operation initiated by itself, which causes their respective timers to expire.

[0016] In a possible design, the session management function network element receives a response message to release the first session.

[0017] In a possible design, when the session management function network element rejects the request to establish user plane resources for the first session, the session management function network element sends a second message to the access and mobility management function network element, the second message indicating a failure to establish user plane resources for the first session.

[0018] In a possible design, the second message is a session management context update response message, where the session management context update response message includes user plane context status information, where the user plane context status information indicates that user plane resources for the first session are disabled.

[0019] In a possible design, the second message includes a first cause value, the first cause value indicating a cause for failure to establish user plane resources for the first session.

[0020] In a possible design, it is shown that the cause of the failure to establish user plane resources for the first session is that the first session is performing a procedure to release the first session.

[0021] In a possible design, before the session management function network element receives a response message for the first operation, the session management function network element receives a request to establish user plane resources for the first session from the access and mobility management function network element.

[0022] In a possible design, the request to establish user plane resources for the first session is a session management context update request message, and the session management context update request message includes one or more of the following: an operation type or a valid session identifier, where the operation type indicates user plane enablement and the valid session identifier includes the first session identifier.

[0023] In a possible design, the type of the first operation is to modify the first session, and when the session management function network element determines a subsequent procedure based on the type of the first operation, the session management function network element rejects the request to establish user plane resources for the first session and continues to perform the procedure to modify the first session.

[0024] According to the above design, the session management function network element rejects the request to establish user plane resources for the first session and continues to execute the procedure to modify the first session. In this way, it is possible to avoid the case where the terminal device and the session management function network element each wait for a response message for a request operation initiated by itself, which causes their respective timers to expire.

[0025] In a possible design, the type of the first operation is to modify the first session, and when the session management function network element determines a subsequent procedure based on the type of the first operation, the session management function network element continues to perform the procedure of modifying the first session and the procedure of establishing user plane resources for the first session.

[0026] According to the above design, the session management function network element executes two procedures at the same time, thus avoiding the case where the terminal device and the session management function network element each wait for a response message for a request operation initiated by itself, which causes their respective timers to expire.

[0027] According to a second aspect, the application provides a communications device, the device including: a transceiver unit and a processing unit. The transceiver unit is configured to initiate a procedure of a first operation for a first session and to receive a request from an access and mobility management function network element to establish user plane resources for the first session in the process of performing the first operation. The processing unit is configured to determine a subsequent procedure based on a type of the first operation.

[0028] In a possible design, the first operation is to modify the first session, and the processing unit is particularly configured to abort the procedure of modifying the first session and to perform a procedure of establishing user plane resources for the first session.

[0029] In a possible design, the processing unit is configured to stop a first timer, where the first timer includes a timer waiting for a response message for modifying the first session.

[0030] In a possible design, the transceiver unit is configured to resume a procedure for modifying the first session after completing a procedure for establishing user plane resources for the first session.

[0031] In a possible design, the transceiver unit is configured to send a first message to the access and mobility management function network element when performing a procedure to establish user plane resources for the first session, the first message indicating successful establishment of the user plane resources for the first session.

[0032] In a possible design, the first message is a session management context update response message, and the session management context update response message includes one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that user plane resources for the first session are enabled, and the session management information includes relevant parameters for establishing user plane resources for the first session.

[0033] In a possible design, the first operation is to release the first session, and the processing unit is particularly configured to reject the request to establish user plane resources for the first session and continue executing the procedure to release the first session.

[0034] In a possible design, the transceiver unit is configured to receive a response message to release the first session.

[0035] In a possible design, the transceiver unit is configured to send a second message to the access and mobility management function network element when rejecting the request to establish user plane resources for the first session, the second message indicating a failure to establish the user plane resources for the first session.

[0036] In a possible design, the second message is a session management context update response message, where the session management context update response message includes user plane context status information, where the user plane context status information indicates that user plane resources for the first session are disabled.

[0037] In a possible design, the second message includes a first cause value, the first cause value indicating a cause for failure to establish user plane resources for the first session.

[0038] In a possible design, it is shown that the cause of the failure to establish user plane resources for the first session is that the first session is performing a procedure to release the first session.

[0039] In a possible design, the transceiver unit is configured to receive a request to establish user plane resources for the first session from the access and mobility management function network element before receiving a response message for the first operation.

[0040] In a possible design, the request to establish user plane resources for the first session is a session management context update request message, and the session management context update request message includes one or more of the following: an operation type or a valid session identifier, where the operation type indicates user plane enablement and the valid session identifier includes the first session identifier.

[0041] In a possible design, the type of the first operation is to modify the first session, and the processing unit is configured, when determining a subsequent procedure based on the type of the first operation, to reject the request to establish user plane resources for the first session and to continue performing the procedure to modify the first session.

[0042] In a possible design, the type of the first operation is to modify the first session, and the processing unit is configured to continue executing the procedure of modifying the first session and the procedure of establishing user plane resources for the first session when determining a subsequent procedure based on the type of the first operation.

[0043] It should be noted that the technical effects of the second aspect and any possible designs of the second aspect refer to the corresponding technical effects of the first aspect and any possible designs of the first aspect, and the details will not be described again.

[0044] According to a third aspect, the present application provides a method of communication, the method including:

[0045] The session management function network element sends a first message to the access and mobility management function network element, the first message being used to request a first operation, the first operation including modifying the first session or releasing the first session. After the session management function network element sends the first message, the session management function network element receives a second message from the access and mobility management function network element, the second message being used to request establishing user plane resources for the first session. When the session management function network element determines that a response message to the first message is not received and a second message is received, the session management function network element aborts the procedure of the first operation, and the session management function network element performs a procedure to establish user plane resources for the first session.

[0046] According to the above method, when the procedure of the first operation collides with the procedure of establishing user plane resources for a PDU session initiated by a terminal device, i.e., when the operation initiated by the network side device collides with the operation initiated by the terminal device for the same PDU session, the session management function network element aborts the current procedure of the first operation and executes the procedure of establishing user plane resources for the first session. In this way, the case that the terminal device and the session management function network element each wait for a response message for a request operation initiated by themselves, which causes their respective timers to expire, can be avoided, thereby effectively ensuring the smoothness of user experience and service process.

[0047] In a possible design, the first operation is to modify the first session, and when the session management function network element determines that no response message to the first message is received, a second message is received, and establishing user plane resources for the first session is not requested, the session management function network element aborts the procedure of the first operation, and the session management function network element performs a procedure to establish user plane resources for the first session.

[0048] According to the above design, when the session management function network element has not received a response message to the first message, has received a second message, and requests not to establish user plane resources for the first session, the session management function network element aborts the procedure of the first operation and performs a procedure to establish user plane resources for the first session.

[0049] In a possible design, the method further includes the session management function network element stopping a first timer, the first timer including a timer waiting for a response message to the first message.

[0050] According to the above design, when the session management function network element aborts the procedure of the first operation, the session management function network element stops the first timer.

[0051] In a possible design, the method further includes the session management function network element sending first indication information to the access and mobility management function network element, the first indication information indicating the first operation.

[0052] According to the above design, the first indication information is utilized to enable the terminal device to discard the first message based on the first indication information.

[0053] In a possible design, if the first operation is to modify the first session, the first message includes a PDU session modify command, where the PDU session modify command includes an identifier of the first session, or if the first operation is to release the first session, the first message includes a PDU session release command, where the PDU session release command includes an identifier of the first session.

[0054] In a possible design, the second message is a session management context update request message, where the session management context update request message includes one or more of the following: an operation type or a valid session identifier, where the operation type indicates user plane enablement and the valid session identifier includes the first session identifier.

[0055] In a possible design, a procedure for establishing user plane resources for a first session by a session management function network element may include, but is not limited to, the following steps: The method may particularly include one or more of: the session management function network element sending a session modification request message to a user plane function network element, where the session modification request message is utilized to configure downlink tunnel information for the user plane function network element; the session management function network element receiving a session modification response message from the user plane function network element, where the session modification response message is utilized to respond to the session modification request message; and the session management function network element sending a third message to the access and mobility management function network element in response to the second message, where the third message indicates successful establishment of user plane resources for the first session.

[0056] In a possible design, the third message is a session management context update response message, where the session management context update response message includes one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that user plane resources for the first session are enabled, and the session management information includes relevant parameters for establishing user plane resources for the first session.

[0057] In a possible design, after the session management function network element performs a procedure to establish user plane resources for the first session, the session management function network element sends a first message to the access and mobility management function network element.

[0058] According to a fourth aspect, the application provides a communication method, the method including: a session management function network element sending a first message to an access and mobility management function network element, the first message being used to request a first operation, the first operation including modifying a first session or releasing the first session; after the session management function network element sends the first message, the session management function network element receives a second message from the access and mobility management function network element, the second message being used to request establishing user plane resources for the first session; when a response message to the first message is not received and the session management function network element determines that a second message is received, the session management function network element sends a third message to the access and mobility management function network element in response to the second message, the third message indicating a failure to establish the user plane resources for the first session or a success to establish the user plane resources for the first session.

[0059] According to the above method, when the procedure of the first operation collides with the procedure of establishing user plane resources for a PDU session initiated by a terminal device, i.e., when the operation initiated by the network side device collides with the operation initiated by the terminal device for the same PDU session, the session management function network element sends a third message to the access and mobility management function network element, and the third message indicates the failure or success of establishing user plane resources for the first session. In this way, the case that the terminal device and the session management function network element each wait for a response message for a request operation initiated by themselves, which causes their respective timers to expire, can be avoided, thereby effectively ensuring the smoothness of user experience and service process.

[0060] In a possible design, the first operation is to modify the first session, and when the session management function network element determines that no response message to the first message is received, a second message is received, and establishment of user plane resources for the first session is not requested, the session management function network element sends a third message to the access and mobility management function network element in response to the second message.

[0061] According to the above design, when the session management function network element has not received a response message to the first message, has received a second message, and has not requested to establish user plane resources for the first session, the session management function network element sends a third message to the access and mobility management function network element in response to the second message.

[0062] In a possible design, when the third message indicates a failure to establish user plane resources for the first session, the third message includes a first cause value, the first cause value indicating a cause for the failure to establish user plane resources for the first session.

[0063] In a possible design, it is shown that the cause of the failure to establish user plane resources for the first session is that the first session is performing a procedure of a first operation.

[0064] In a possible design, when the third message indicates a failure to establish user plane resources for the first session, the third message includes a session management context update response message and a first cause value, the session management context update response message includes user plane context status information, and the user plane context status information indicates that the user plane resources for the first session are disabled.

[0065] In a possible design, when the third message indicates successful establishment of user plane resources for the first session, the third message is a session management context update response message, and the session management context update response message includes one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that the user plane resources for the first session are enabled, and the session management information includes relevant parameters for establishing the user plane resources for the first session.

[0066] In a possible design, the method further includes the session management function network element sending first indication information to the access and mobility management function network element, the first indication information indicating the first operation.

[0067] According to the above design, the first indication information is utilized to enable the terminal device to cache the first message or a response message to the first message based on the first indication information.

[0068] In a possible design, if the first operation is to modify the first session, the first message includes a PDU session change command, the PDU session change command includes an identifier of the first session, and the response message to the first message is a PDU session change complete command, the PDU session change complete command includes the identifier of the first session; or If the first operation is to release a first session, the first message includes a PDU session release command, where the PDU session release command includes an identifier of the first session, and the response message to the first message is a PDU session release complete command, where the PDU session release complete command includes the identifier of the first session.

[0069] In a possible design, the second message is a session management context update request message, where the session management context update request message includes one or more of the following: an operation type or a valid session identifier, where the operation type indicates user plane enablement and the valid session identifier includes the first session identifier.

[0070] In a possible design, after the session management function network element sends a third message to the access and mobility management function network element, the session management function network element receives a response message to the first message from the access and mobility management function network element.

[0071] According to a fifth aspect, the application provides a communication method, the method including: a terminal device sending a service request message to an access and mobility management function network element, the service request message being used to request establishing user plane resources for a first session; the terminal device receiving a first message from the access and mobility management function network element, the first message being used to request a first operation, the first operation including modifying the first session or releasing the first session; and the terminal device caching the first message or a response message to the first message until receiving a service grant message from the access and mobility management function network element, and sending the response message to the first message to the access and mobility management function network element.

[0072] According to the above method, when a procedure of a first operation initiated by a session management function network element conflicts with a procedure of establishing user plane resources for a PDU session initiated by a terminal device, i.e., for the same PDU session, when an operation initiated by the network side device conflicts with an operation initiated by the terminal device, the terminal device caches the first message or a response message to the first message until it receives a service authorization message from the access and mobility management function network element, and sends the response message to the first message to the access and mobility management function network element, thereby effectively ensuring the smoothness of user experience and service processes.

[0073] In a possible design, the terminal device includes a session management layer and a mobility management layer, and before the terminal device caches a response message to the first message, the mobility management layer sends a first message to the session management layer, and the mobility management layer receives the response message to the first message from the session management layer.

[0074] According to the above design, the mobility management layer first sends a first message to the session management layer, and then caches a response message which is of the first message and is fed back by the session management layer.

[0075] In a possible design, the terminal device includes a session management layer and a mobility management layer, and when the terminal device caches the first message until it receives a service authorization message from the access and mobility management function network element, and sends a response message to the first message to the access and mobility management function network element, The mobility management layer caches the first message until a service authorization message is received, the mobility management layer sends the first message to the session management layer, the mobility management layer receives a response message to the first message from the session management layer, and the mobility management layer sends the response message to the first message to the access and mobility management function network element.

[0076] According to the above design, the mobility management layer first caches the first message, and sends the first message to the session management layer after receiving the service authorization message.

[0077] In a possible design, the terminal device receives first indication information from the access and mobility management function network element, the first indication information indicating a first operation, in which case the terminal device caches the first message or a response message to the first message based on the first indication information.

[0078] According to the above design, the terminal device may cache the first message or a response message to the first message based on the first indication information.

[0079] In a possible design, if the first operation is to modify a first session, the first message includes a PDU session modification command, the PDU session modification command includes an identifier of the first session, and the response message to the first message is a PDU session modification complete command, the PDU session modification complete command includes the identifier of the first session; or If the first operation is to release a first session, the first message includes a PDU session release command, where the PDU session release command includes an identifier of the first session, and the response message for the first session is a PDU session release complete command, where the PDU session release complete command includes the identifier of the first session.

[0080] In a possible design, the service request message includes uplink data status information, where the uplink data status information indicates an identifier of the first session.

[0081] In a possible design, the service grant message includes an information element indicating a PDU session validation result, where the information element indicating the PDU session validation result indicates that establishment of user plane resources for the first session is successful.

[0082] In a possible design, the service grant message includes an information element indicating a PDU session activation result, and the information element indicating the PDU session activation result indicates a failure to establish user plane resources for the first session; or The service authorization message includes an information element indicating a PDU session activation result and / or an information element indicating an error cause of the PDU session activation result, where the information element indicating the PDU session activation result indicates a failure to establish user plane resources for the first session, and the information element indicating the error cause of the PDU session activation result indicates the cause of the failure to establish user plane resources for the first session.

[0083] In a possible design, a cause of failure to establish user plane resources for the first session includes the first session being performing a procedure of a first operation.

[0084] In a possible design, the first operation is to modify the first session, and after the terminal device sends a response message to the access and mobility management function network element to the first message, the method further includes the terminal device resending a service request message to the access and mobility management function network element.

[0085] According to the above design, the terminal device may resume procedures to request establishing user plane resources for the first session.

[0086] According to a sixth aspect, the application provides a communication method, the method including: a terminal device sending a service request message to an access and mobility management function network element, the service request message being used to request establishing user plane resources for a first session; the terminal device receiving a first message from the access and mobility management function network element, the first message being used to request a first operation, the first operation including modifying the first session or releasing the first session; and when the terminal device determines that the service request message has been sent and a response message to the service request message is not received, the terminal device discarding the first message.

[0087] According to the above design, when a procedure of a first operation initiated by a session management function network element conflicts with a procedure of establishing user plane resources for a PDU session initiated by a terminal device, the terminal device may discard the first message.

[0088] In a possible design, the terminal device receives first indication information from an access and mobility management function network element, the first indication information indicating a first operation, and the terminal device discarding the first message includes the terminal device discarding the first message based on the first indication information.

[0089] According to the above design, the terminal device may discard the first message based on the first indication information.

[0090] In a possible design, the service request message includes uplink data status information, where the uplink data status information indicates an identifier of the first session.

[0091] In a possible design, if the first operation is to modify the first session, the first message includes a PDU session modify command, where the PDU session modify command includes an identifier of the first session, or if the first operation is to release the first session, the first message includes a PDU session release command, where the PDU session release command includes an identifier of the first session.

[0092] According to a seventh aspect, the application provides a communication device. The device includes a transceiver unit and a processing unit. The transceiver unit is configured to: send a first message to an access and mobility management function network element, the first message being used to request a first operation, the first operation including modifying a first session or releasing the first session; and receive a second message from the access and mobility management function network element after sending the first message, the second message being used to request establishing user plane resources for the first session. The processing unit is configured to abort a procedure of the first operation and perform a procedure of establishing user plane resources for the first session when it determines that a response message to the first message is not received and that a second message is received.

[0093] In a possible design, the first operation is to modify the first session, and the processing unit is configured to abort a procedure of the first operation and perform a procedure of establishing user plane resources for the first session when it determines that no response message to the first message is received, a second message has been received, and establishing user plane resources for the first session is not requested.

[0094] In a possible design, the processing unit is configured to stop a first timer, the first timer including a timer waiting for a response message to the first message.

[0095] In a possible design, the transceiver unit is configured to send first indication information to the access and mobility management function network element, the first indication information indicating the first operation.

[0096] In a possible design, if the first operation is to modify the first session, the first message includes a PDU session modify command, where the PDU session modify command includes an identifier of the first session, or if the first operation is to release the first session, the first message includes a PDU session release command, where the PDU session release command includes an identifier of the first session.

[0097] In a possible design, the second message is a session management context update request message, where the session management context update request message includes one or more of the following: an operation type or a valid session identifier, where the operation type indicates user plane enablement and the valid session identifier includes the first session identifier.

[0098] In a possible design, the processing unit causing the transceiver unit to perform a procedure for establishing user plane resources for the first session may specifically include the following steps: sending a session modification request message to a user plane function network element, where the session modification request message is used to configure downlink tunnel information for the user plane function network element; receiving a session modification response message from the user plane function network element, where the session modification response message is used to respond to the session modification request message; and sending a third message to the access and mobility management function network element in response to the second message, where the third message indicates successful establishment of the user plane resources for the first session.

[0099] In a possible design, the third message is a session management context update response message, where the session management context update response message includes one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that user plane resources for the first session are enabled, and the session management information includes relevant parameters for establishing user plane resources for the first session.

[0100] In a possible design, the transceiver unit is configured to send a first message to the access and mobility management function network element after performing a procedure to establish user plane resources for the first session.

[0101] According to an eighth aspect, the application provides a communication device, the device including: a transceiver unit; and a processing unit. The transceiver unit is configured to: send a first message to an access and mobility management function network element, the first message being used to request a first operation, the first operation including modifying a first session or releasing the first session; and after sending the first message, the transceiver unit is configured to receive a second message from the access and mobility management function network element, the second message being used to request establishing user plane resources for the first session. When the processing unit determines that a response message to the first message is not received and a second message is received, the transceiver unit is configured to: send a third message to the access and mobility management function network element in response to the second message, the third message indicating a failure to establish user plane resources for the first session or a success to establish user plane resources for the first session.

[0102] In a possible design, the first operation is to modify the first session, and when the session management function network element determines that no response message to the first message is received, a second message is received, and establishment of user plane resources for the first session is not requested, the session management function network element sends a third message to the access and mobility management function network element in response to the second message.

[0103] In a possible design, when the third message indicates a failure to establish user plane resources for the first session, the third message includes a first cause value, the first cause value indicating a cause for the failure to establish user plane resources for the first session.

[0104] In a possible design, it is shown that the cause of the failure to establish user plane resources for the first session is that the first session is performing a procedure of a first operation.

[0105] In a possible design, when the third message indicates a failure to establish user plane resources for the first session, the third message includes a session management context update response message and a first cause value, the session management context update response message includes user plane context status information, and the user plane context status information indicates that the user plane resources for the first session are disabled.

[0106] In a possible design, when the third message indicates successful establishment of user plane resources for the first session, the third message is a session management context update response message, and the session management context update response message includes one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that the user plane resources for the first session are enabled, and the session management information includes relevant parameters for establishing the user plane resources for the first session.

[0107] In a possible design, the transceiver unit is configured to send first indication information to the access and mobility management function network element, the first indication information indicating the first operation.

[0108] In a possible design, if the first operation is to modify the first session, the first message includes a PDU session change command, the PDU session change command includes an identifier of the first session, and the response message to the first message is a PDU session change complete command, the PDU session change complete command includes the identifier of the first session; or If the first operation is to release a first session, the first message includes a PDU session release command, where the PDU session release command includes an identifier of the first session, and the response message to the first message is a PDU session release complete command, where the PDU session release complete command includes the identifier of the first session.

[0109] In a possible design, the second message is a session management context update request message, where the session management context update request message includes one or more of the following: an operation type or a valid session identifier, where the operation type indicates user plane enablement and the valid session identifier includes the first session identifier.

[0110] In a possible design, the transceiver unit is configured to receive a response message to the first message from the access and mobility management function network element after sending the third message to the access and mobility management function network element.

[0111] According to a ninth aspect, the application provides a communication device, the device including a transceiver unit and a processing unit. The transceiver unit is configured to: send a service request message to an access and mobility management function network element, the service request message being used to request establishing user plane resources for a first session; and receive a first message from the access and mobility management function network element, the first message being used to request a first operation, the first operation including modifying the first session or releasing the first session. The processing unit is configured to cache the first message or a response message to the first message until the transceiver unit receives a service grant message from the access and mobility management function network element, and cause the transceiver unit to send the response message to the first message to the access and mobility management function network element.

[0112] In a possible design, the device includes a session management layer and a mobility management layer, where the mobility management layer sends a first message to the session management layer before caching a response message to the first message, and the mobility management layer receives the response message to the first message from the session management layer.

[0113] In a possible design, the device includes a session management layer and a mobility management layer, and caches the first message until receiving a service authorization message from the access and mobility management function network element, and when sending a response message to the first message to the access and mobility management function network element, the mobility management layer caches the first message until receiving the service authorization message, the mobility management layer sends the first message to the session management layer, the mobility management layer receives the response message to the first message from the session management layer, and the mobility management layer sends the response message to the first message to the access and mobility management function network element.

[0114] In a possible design, the transceiver unit is configured to receive first indication information from an access and mobility management function network element, the first indication information indicating a first operation, and the processing unit is configured to cache the first message or a response message to the first message based on the first indication information.

[0115] In a possible design, if the first operation is to modify a first session, the first message includes a PDU session modification command, the PDU session modification command includes an identifier of the first session, and the response message to the first message is a PDU session modification complete command, the PDU session modification complete command includes the identifier of the first session; or If the first operation is to release a first session, the first message includes a PDU session release command, where the PDU session release command includes an identifier of the first session, and the response message to the first message is a PDU session release complete command, where the PDU session release complete command includes the identifier of the first session.

[0116] In a possible design, the service request message includes uplink data status information, where the uplink data status information indicates an identifier of the first session.

[0117] In a possible design, the service grant message includes an information element indicating a PDU session validation result, where the information element indicating the PDU session validation result indicates that establishment of user plane resources for the first session is successful.

[0118] In a possible design, the service grant message includes an information element indicating a PDU session activation result, and the information element indicating the PDU session activation result indicates a failure to establish user plane resources for the first session; or The service authorization message includes an information element indicating a PDU session activation result and an information element indicating an error cause of the PDU session activation result, where the information element indicating the PDU session activation result indicates a failure to establish user plane resources for the first session, and the information element indicating the error cause of the PDU session activation result indicates the cause of the failure to establish user plane resources for the first session.

[0119] In a possible design, a cause of failure to establish user plane resources for the first session includes the first session being performing a procedure of a first operation.

[0120] In a possible design, the first operation is to modify the first session, and after sending a response message to the access and mobility management function network element for the first message, the transceiver unit is configured to resend the service request message to the access and mobility management function network element.

[0121] According to the above design, the terminal device may resume procedures to request establishing user plane resources for the first session.

[0122] According to a tenth aspect, the application provides a communication device. The device includes a transceiver unit and a processing unit. The transceiver unit is configured to: send a service request message to an access and mobility management function network element, where the service request message is used to request to establish user plane resources for a first session; and receive a first message from the access and mobility management function network element, where the first message is used to request a first operation, where the first operation includes modifying the first session or releasing the first session. The processing unit is configured to discard the first message when it determines that the service request message has been sent and a response message to the service request message is not received.

[0123] In one possible design, the transceiver unit is configured to receive first indication information from an access and mobility management function network element, the first indication information indicating a first operation, and the processing unit is configured to discard the first message based on the first indication information.

[0124] In a possible design, the service request message includes uplink data status information, where the uplink data status information indicates an identifier of the first session.

[0125] In a possible design, if the first operation is to modify the first session, the first message includes a PDU session modify command, where the PDU session modify command includes an identifier of the first session, or if the first operation is to release the first session, the first message includes a PDU session release command, where the PDU session release command includes an identifier of the first session.

[0126] According to an eleventh aspect, the present application further provides an apparatus, which can execute the above method design. The apparatus may be a chip or circuit capable of executing the function corresponding to the above method, or a device including the chip or circuit.

[0127] In a possible implementation, the apparatus includes a memory configured to store computer executable program code and a processor, the processor coupled to the memory. The program code stored in the memory includes instructions. When the processor executes the instructions, the apparatus, or a device to which the apparatus is attached, is enabled to perform the method in any one of the possible designs above.

[0128] The device may further include a communication interface. The communication interface may be a transceiver. Alternatively, if the device is a chip or a circuit, the communication interface may be an input / output interface of the chip, such as an input / output pin.

[0129] In a possible design, the apparatus includes corresponding functional units configured to implement the steps of the above methods, respectively. The functions may be implemented by hardware or by the hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0130] According to a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium storing a computer program, the computer program being operable, when executed on an apparatus, to perform a method in any one of the above possible designs.

[0131] According to a thirteenth aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program, which, when executed on an apparatus, performs a method in any one of the above possible designs. [Brief description of the drawings]

[0132] [Figure 1A] 1 is a schematic diagram of the architecture of a mobile communication system to which an embodiment of this application is applied; [Figure 1B] 2 is a schematic diagram of the architecture of a mobile communication system to which an embodiment of this application is applied; [Diagram 2] A schematic diagram of a UE initiating a specific procedure for establishing user plane resources for a PDU session according to an embodiment of this application. [Diagram 3] A schematic diagram of a network side device initiating a procedure for modifying a PDU session according to an embodiment of this application. [Figure 4] A schematic diagram of a scenario in which a procedure for modifying a PDU session initiated by a network side device conflicts with a procedure for establishing user plane resources for a PDU session initiated by a UE according to an embodiment of this application. [Diagram 5] 1 is an overview flowchart 1 of a communication method according to an embodiment of the present application. [Figure 6] 2 is an overview flowchart 2 of a communication method according to an embodiment of the present application. [Figure 7] FIG. 1 is a schematic diagram of a terminal device sending a response message to a first message to an access and mobility management function network element according to an embodiment of this application; [Figure 8] FIG. 2 is a schematic diagram of a terminal device sending a response message to a first message to an access and mobility management function network element according to an embodiment of this application; [Figure 9]1 is a schematic diagram of a process for handling a collision between a procedure for modifying a PDU session initiated by a network side device and a procedure for establishing user plane resources initiated by a UE according to an embodiment of this application; [Figure 10] Schematic diagram 2 of a process for handling a collision between a procedure for modifying a PDU session initiated by a network side device and a procedure for establishing user plane resources initiated by a UE according to an embodiment of this application. [Figure 11] Schematic diagram 3 of a process for handling a collision between a procedure for modifying a PDU session initiated by a network side device and a procedure for establishing user plane resources initiated by a UE according to an embodiment of this application. [Figure 12] 1 is a schematic diagram of the structure of an apparatus according to an embodiment of the present application; [Figure 13] 2 is a schematic diagram of the structure of the device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0133] Hereinafter, the technical solutions in the embodiments of this application will be described with reference to the accompanying drawings in the embodiments of this application. TheoryIt is clear that the described embodiments are merely some but not all of the embodiments of this application. In the specification, claims, and accompanying drawings of this application, the terms "first", "second" and corresponding terms such as reference numbers are intended to distinguish similar objects and do not necessarily indicate a specific order or sequence. Terms used in such a manner are interchangeable in appropriate circumstances, and it should be understood that it is merely a manner of distinction used when objects having the same attributes are described in the embodiments of this application. In addition, the terms "include", "comprise", and other variations are meant to cover non-exclusive inclusion, whereby a process, method, system, product, or device that includes a set of units is not necessarily limited to those units and may include other units that are not expressly listed or inherent to such process, method, system, product, or device.

[0134] In the description of this application, " / " means "or" unless otherwise specified. For example, A / B can mean A or B. In this application, "and / or" describes only the association relationship to describe related objects, and indicates that three relationships may exist. For example, A and / or B can represent the following three cases: A exists, both A and B exist, and only B exists. 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 (parts)" or its analogous origin means any combination of these items, including any combination of singular items (parts) or multiple items (parts). For example, at least one of a, b, or c can refer to a, b, c, a and b, a and c, b and c, or a, b, and c, and a, b, and c can be singular or plural.

[0135] The technical solutions in the embodiments of this application may be applied to various communication systems, such as a Wideband Code Division Multiple Access (WCDMA) system, a general packet radio service (GPRS) system, a Long Term Evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunications system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) system, or a future 6th generation communication system.

[0136] 1A and 1B are respectively schematic diagrams of the architecture of a mobile communication system to which an embodiment of this application is applied. A terminal device is connected to a radio access network device in a wireless manner, and the radio access network device is connected to a core network device in a wireless or wired manner. The core network device and the radio access network device may be independent and different physical devices, or the functions of the core network device and the logical functions of the radio access network device are integrated into the same physical device, or part of the functions of the core network device and part of the functions of the radio access network device are integrated into one physical device. The terminal device may be located at a fixed location or may be mobile. FIG. 1A and FIG. 1B are merely schematic diagrams. The communication system may further include other network devices.

[0137] The core network devices include session management network elements, access management network elements, user plane function network elements, etc.

[0138] The session management network element is mainly configured to manage sessions, allocate and manage internet protocol (IP) addresses of terminal devices, select endpoints that can manage user equipment plane function interfaces and policy control or charging function interfaces, and perform downlink data notification, etc. In 5G communication, the session management network element may be a session management function (SMF) network element. In future communication, such as 6G communication, the session management function network element may still be an SMF network element or may have other names. This is not limited in this application. Nsmf is a service-based interface provided by SMF. SMF may communicate with other network functions through Nsmf.

[0139] The access management network element is mainly configured to perform mobility management and access management, etc. The access management network element may be configured to implement functions, such as lawful interception or access authorization (or authentication), in a mobility management entity (MME) function other than session management. In 5G communication, the access management network element may be an access and mobility management function (AMF) network element. In future communication, such as 6G communication, the access management network element may still be an AMF network element or may have other names. This is not limited in this application. Namf is a service-based interface provided by AMF. AMF may communicate with other network functions through Namf.

[0140] A user plane function (UPF) network element is configured to perform packet routing and forwarding, and perform quality of service (QoS) processing on user plane data, etc. In 5G communication, the user plane network element may be a user plane function (UPF) network element. In future communication, such as 6G communication, the user plane network element may still be a UPF network element or may have another name. This is not limited in this application.

[0141] The radio access device is a radio access network (RAN) and is configured to implement functions related to radio access. The radio access network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a Wi-Fi system. Alternatively, the radio network device may be a module or unit that implements part of the functions of a base station, for example, a central unit (CU) or a distributed unit (DU). The specific technology and the specific device form used by the radio access network device are not limited in the embodiments of this application.

[0142] The terminal device may also be referred to as a terminal, user equipment (UE), mobile station, or mobile terminal, etc. The terminal device may be a mobile phone, a tablet computer, a computer with a wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in remote surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home, etc. The specific technology and the specific device form used by the terminal device are not limited in the embodiments of this application.

[0143] In addition, the terminal device may be divided into a 5GS session management (5GSM) layer and a 5GS mobility management (5GMM) layer, among others. The 5GSM layer is responsible for session management of the terminal device. The 5GMM layer is responsible for mobility management of the terminal device, requests higher layer services to establish service connections, and requests user plane resources for uplink data transmission.

[0144] The following describes a procedure for establishing user plane resources for a PDU session initiated by a UE. It should be noted that the procedure shown in FIG. 2 is a non-collision scenario. For example, the UE is registered in a 5G network and the UE is in a connected mode. There is currently a valid PDU session context. For example, the identifier of the PDU session is PDU session ID=5. The following takes an example where the identifier of the PDU session is PDU session ID=5, and describes a specific procedure for establishing user plane resources for a PDU session initiated by a UE for the PDU session, as shown in FIG. 2.

[0145] Step 201: The UE sends a service request message to the RAN.

[0146] The service request message includes uplink data status information, and the uplink data status information indicates a PDU session ID (eg, PDU session ID=5).

[0147] For example, if the uplink data status information indicates that PDU session ID=5, it indicates that the UE is requesting to establish user plane resources for the PDU session with PDU session ID=5.

[0148] Step 202: The RAN sends an N2 message to the AMF, where the N2 message includes the service request message in step 201.

[0149] Step 203: The AMF sends a session management context update request (Nsmf_PDUSession_UpdateSMConext Request) message to the SMF.

[0150] The AMF determines, based on the service request message in step 202, that the UE is requesting to establish user plane resources for a PDU session with PDU session ID = 5. The session management context update request message may, for example, include one or more of the following: an operation type or an identifier of an active PDU session (the PDU session to be reactivated) (e.g., PDU session ID = 5), where the operation type indicates user plane activation (UP activate).

[0151] Step 204: The SMF sends a session modification request (N4 session modification request) message to the UPF.

[0152] The session modification request message is used to configure downlink tunnel information for the UPF.

[0153] Step 205: The UPF sends a session modification response (N4 session modification response) message to the SMF.

[0154] The session modify response message is utilized to respond to the session modify request message in step 204 .

[0155] Step 206: The SMF sends a session management context update response (Nsmf_PDUSession_UpdateSMConext Response) message to the AMF. The session management context update response message is used to respond to the session management context update request message in step 203.

[0156] The SMF determines that the UE requests to establish user plane resources for the PDU session with PDU Session ID=5 based on the operation type and the identifier of the valid PDU session in the Session Management Context Update Request message. The SMF sends a Session Management Context Update Response message to the AMF. The Session Management Context Update Response message includes, for example, one or more of the following: user plane context status information (UpCnxState) or session management information (for example, N2 SM information). The user plane context status information (upConxState) indicates that the user plane resources for the PDU session with PDU Session ID=5 are activated. The session management information includes related parameters for establishing user plane resources for the PDU session with PDU Session ID=5. For example, here, the related parameters for establishing user plane resources may include, but are not limited to, one or more of the following: PDU Session ID (for example, PDU Session ID=5), QoS flow identifier, and QoS configuration.

[0157] Step 207: The AMF sends an N2 request message to the RAN. The N2 request message includes the service accept message and the session management information in step 206.

[0158] The AMF determines a service grant message based on the session management context update response message in step 206. For example, the service grant message includes a PDU session reactivation result, and the PDU session reactivation result indicates that the user plane resources for the PDU session are successfully established. For example, if the bit position corresponding to PDU session ID=5 is 0, it indicates that the user plane resources for the PDU session with PDU session ID=5 are successfully established. The service grant message is used to respond to the service request message in step 201.

[0159] Step 208: The RAN sends an RRC connection reconfiguration message to the UE.

[0160] The RAN determines the DRB configuration information based on the session management information in the N2 request message. The DRB configuration information includes a PDU session ID (eg, PDU session ID=5).

[0161] The RRC connection reconfiguration message includes the service grant message in step 207 and the DRB configuration information.

[0162] Step 209: The UE sends an RRC connection reconfiguration complete message to the RAN.

[0163] The RRC connection reconfiguration complete message is used to respond to the RRC connection reconfiguration message in step 208 .

[0164] Step 210: The RAN sends an N2 request acknowledgment (N2 request ACK) message to the AMF.

[0165] The N2 request acknowledgement message includes session management information, which includes a list of user plane resources for the successfully established PDU sessions. In this case, the list of user plane resources for the successfully established PDU sessions indicates that the user plane resources for the PDU session with PDU session ID=5 are successfully established.

[0166] Step 211: The AMF sends a session management context update request message to the SMF.

[0167] The session management context update request message includes the session management information in step 210 .

[0168] Step 212: The SMF sends a session management context update response message to the AMF.

[0169] The session management context update response message is used to respond to the session management context update request message in step 211 .

[0170] Based on the session management information in the session management context update request message, the SMF determines that the user plane resources for the PDU session with PDU session ID=5 are successfully established.

[0171] It may be understood that if the UE is in idle mode, the UE needs to first enter connected mode from idle mode and then perform the above procedure.

[0172] The following describes a procedure for modifying a PDU session initiated by a network side device. It should be noted that the procedure shown in FIG. 3 is a non-collision scenario. For example, a UE is registered in a 5G network, and the UE is in a connected mode. There is currently a valid PDU session context. For example, the identifier of the PDU session is PDU session ID=5. The following takes an example where the identifier of the PDU session is PDU session ID=5, and describes a procedure for modifying a PDU session initiated by a network side device for the PDU session, as shown in FIG. 3.

[0173] Step 301: The SMF sends an N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) message to the AMF.

[0174] For example, when deciding to initiate a PDU session modification procedure, the SMF sends an N1N2 message transfer message to the AMF.

[0175] The N1N2 message transfer message may, for example, include one or more of the following: a UE identifier, a PDU session ID (e.g., PDU session ID=5), or a session management container (e.g., N1 SM container). The session management container includes a PDU session modification command, which includes a PDU session ID (e.g., PDU session ID=5). It is assumed here that the N1N2 transfer message does not include session management information (N2 SM information). The N1 interface is the interface between the UE and the AMF, i.e., the non-access stratum (NAS) interface. The N2 interface is the interface between the RAN and the AMF. The PDU session modification command is a message sent to the UE, and the session management information is a message sent to the RAN.

[0176] Step 302: In response to the N1N2 message transfer message, the AMF sends an N1N2 message transfer response message to the SMF.

[0177] Step 303: The AMF sends an N2 request message to the RAN, where the N2 request message includes a downlink non-access stratum transport (DL NAS TRANSPORT) message, and the downlink non-access stratum transport message includes the session management container (N1 SM container) in step 301.

[0178] Step 304: The RAN sends a downlink non-access stratum forwarding message to the UE.

[0179] Step 305: The UE sends a PDU Session Modification complete command to the RAN.

[0180] Step 306: The RAN sends an N2 message to the AMF, where the N2 message includes the PDU session modification complete command in step 305.

[0181] Step 307: The AMF sends a session management context update request message to the SMF, where the session management context update request message includes a PDU session modification complete command.

[0182] Step 308: The SMF sends a session management context update response message to the AMF, where the session management context update response message is used to respond to the session management context update request message.

[0183] Similarly, the PDU session change command in the above procedure may alternatively be replaced by a PDU session release command, and the PDU session change complete command may alternatively be replaced by a PDU session release complete command.

[0184] The following describes a specific scenario in which operations initiated by the UE and the network side device for the same PDU session collide.

[0185] The UE is registered in a 5G network, and the UE is in a connected mode. There is currently a valid PDU session context. For example, the identifier of the PDU session is PDU session ID=5. In the following, using an example where the identifier of the PDU session is PDU session ID=5, as shown in FIG. 4, a scenario and a collision handling process are described in which the procedure of modifying the PDU session initiated by the network side device for the PDU session and the procedure of establishing user plane resources for the PDU session initiated by the UE collide.

[0186] Step 401: The SMF sends an N1N2 message transfer message to the AMF.

[0187] For example, when deciding to initiate a procedure to modify a PDU session (PDU session modification), the SMF sends an N1N2 message transfer message to the AMF.

[0188] The N1N2 message forwarding message may, for example, include one or more of the following: a UE identifier, a PDU Session ID (e.g., PDU Session ID=5), or a session management container (N1 SM container). The session management container includes a PDU Session Change command, which includes a PDU Session ID (e.g., PDU Session ID=5). It is assumed here that the N1N2 forwarding message does not include session management information (N2 SM information).

[0189] Step 402: In response to the N1N2 message transfer message, the AMF sends an N1N2 message transfer response message to the SMF.

[0190] Step 403: The AMF sends an N2 request message to the RAN, where the N2 request message includes a downlink non-access stratum transport message, and the downlink non-access stratum transport message includes the session management container (N1 SM container) in step 401.

[0191] Step 404: The UE sends a service request message to the RAN. The service request message includes uplink data status information, and the uplink data status information indicates a PDU session ID (for example, PDU session ID=5). If the uplink data status information indicates PDU session ID=5, it indicates that the UE requests to establish user plane resources for the PDU session with PDU session ID=5.

[0192] Step 405: The RAN sends a downlink non-access stratum forwarding message to the UE.

[0193] Step 406: The RAN sends an N2 message to the AMF. The N2 message includes the service request message in step 404.

[0194] Step 407: The AMF sends a session management context update request message to the SMF.

[0195] The AMF determines, based on the service request message in step 406, that the UE is requesting to establish user plane resources for a PDU session with PDU session ID = 5. The session management context update request message may, for example, include one or more of the following: an operation type or an identifier of a valid PDU session (e.g., PDU session ID = 5), where the operation type indicates user-plane activation.

[0196] Step 408: The SMF triggers an abnormal procedure when it determines that the timer expires.

[0197] The SMF determines that the UE requests to establish user plane resources for the PDU session with PDU session ID=5 based on the session management context update request message in step 407. Since the SMF is performing a procedure to modify the PDU session with PDU session ID=5, the SMF does not respond to the session management context update request message in step 407. Since the collision scenario is not described in the protocol, it can be understood that the SMF generally handles collision scenarios that are explicitly described in the protocol and does not handle collision scenarios that are not described. When the SMF receives a response message to the PDU session modification command (i.e., a PDU Session Modification complete message) from the UE, the SMF responds to the session management context update request message in step 407. However, if the SMF has not received a PDU session modification complete command, the SMF does not respond to the session management context update request message in step 407. The SMF waits for the PDU session modification complete command until the first timer expires. The SMF resends the PDU session modification complete message and restarts the first timer. When the first timer expires K times, the SMF aborts the procedure to modify the PDU session with PDU session ID = 5, where K is a preset value. The first timer includes a timer to wait for a PDU session modification complete command.

[0198] Similarly, the UE determines that the SMF requests to modify the PDU session with PDU session ID=5 based on the PDU session modification command in step 405. Since the UE is performing a procedure requesting to establish user plane resources for the PDU session with PDU session ID=5, the UE does not respond to the PDU session modification command, and the UE suspends the transmission of the PDU session modification command. The UE responds to the PDU session modification command in step 405 only after receiving a response message to the service request message (i.e., a service grant message) from the AMF. However, if the UE has not received the service grant message, the UE does not respond to the PDU session modification command in step 405, and the UE waits for the service grant message until the second timer expires. If the UE in the connected mode initiates a procedure requesting to establish user plane resources for the PDU session with PDU session ID=5, the UE aborts the procedure and returns to the connected mode. If a UE in idle mode initiates a procedure requesting to establish user plane resources for a PDU session with PDU Session ID=5, the UE aborts the procedure, releases any resources related to the procedure, and enters idle mode, where the second timer includes a timer waiting for a service grant message.

[0199] Thus, the UE and the SMF each wait for a response message to the request operation initiated by them, and as a result, their respective timers expire and an abnormal procedure is triggered.

[0200] In addition, a similar case may occur in a scenario where a network-initiated procedure for releasing a PDU session and a UE-initiated procedure for establishing user plane resources collide. For example, when the UE is in connected mode, a PDU session modification command may alternatively be replaced by a PDU session release command. Alternatively, a similar case may occur in a scenario where a network-initiated procedure for modifying (releasing) a PDU session and a UE-initiated procedure for establishing user plane resources collide when the UE is in idle mode.

[0201] Based on the collision scenarios illustrated in FIG. 4, the following collisions may occur during the network-requested PDU session modification procedure:

[0202] 1. The UE initiates a service request procedure, where the service request procedure includes uplink data status information, which is used to activate user plane resources for PDU session #1. In addition, the SMF initiates a PDU session modification procedure requested by the network, where the PDU session modification procedure is used to modify PDU session #1.

[0203] 2. According to the existing processing logic, during the 5GMM procedure, the UE and AMF suspend the transmission of 5GSM messages. Therefore, the PDU session change command may be suspended at the AMF or the UE.

[0204] 3. After the SMF sends the PDU session modification command, the SMF receives a session management context update request message (e.g., Nsmf_PDUSession_UpdateSMConext Request) from the AMF, which is used to activate user plane resources for the session that is requested to be modified.

[0205] In the above collision cases, it is unclear how the SMF handles collisions.

[0206] Two subcases need to be considered. Sub-case 1: A PDU session modification requested by the network is to modify parameters (such as QoS profile) of both the UE NAS and the NG-RAN node for that PDU session.

[0207] Sub-case 2: The PDU session modification requested by the network is to change UE NAS only parameters for that PDU session (e.g. serving PLMN rate control).

[0208] In the above two sub-cases, to make the SMF's processing simpler and to prevent possible unnecessary 5GSM retries (e.g., some abnormal cases occur during an ongoing service request procedure, which delays the contention of the service request procedure), the SMF may abort the ongoing network-requested PDU session modification procedure and only perform user plane resource setup for the PDU session. For the above sub-case 1, the parameters of the NG-RAN node may be updated during the user plane resource setup procedure triggered by the service request procedure. After the user plane resources for the PDU session are fully established, the SMF may further resume the network-requested PDU session modification procedure for that PDU session.

[0209] Similarly, the following collision scenarios may occur in a network-requested PDU session release procedure:

[0210] 1. The UE initiates a service request procedure, where the service request procedure includes uplink data status information, where the uplink data status information is used to activate user plane resources for PDU session #1. In addition, the SMF initiates a PDU session release procedure requested by the network, where the PDU session release procedure is used to release PDU session #1.

[0211] 2. As specified in Section 4.2, during the 5GMM procedure, the UE and AMF suspend the transmission of 5GSM messages. Therefore, the PDU session release command may be suspended at the AMF or the UE.

[0212] 3. After the SMF sends the PDU session release command, the SMF receives a session management context update request message from the AMF, which is used to activate the user plane resources that are requested to be released.

[0213] In the research process, the inventors have discovered the above collision scenarios and found that it is unclear how the SMF will handle the collision scenarios in the above collision cases.

[0214] Since the PDU session is to be released, it does not make sense to establish user plane resources for the PDU session in this case, so the SMF does not have to establish user plane resources for the PDU session, but continues to perform the network requested PDU session release procedure for that session.

[0215] As a consequence, when a user plane resource establishment procedure conflicts with a network requested PDU session modification (or release) procedure for the same PDU session, this is currently undetermined, making the SMF's implementation actions unclear.

[0216] Based on the above two types of collision scenarios, this application provides the following solutions: 1. When a user plane resource establishment procedure conflicts with a network requested PDU session modification procedure of the same PDU session, the SMF aborts the ongoing network requested PDU session modification procedure and continues to execute only the user plane resource setup procedure of that PDU session.

[0217] 2. When a user plane resource establishment procedure conflicts with a network-requested PDU session modification procedure for the same PDU session, the SMF does not establish user plane resources for the PDU session and continues to execute the network-requested PDU session release procedure for that PDU session.

[0218] In some embodiments, the session management function network element initiates a procedure of a first operation for the first session. The session management function network element receives a request to establish user plane resources for the first session from the access and mobility management function network element when, in the process of performing the first operation, for example, the procedure of establishing user plane resources conflicts with a procedure of modifying (releasing) the PDU session, initiated by the network, for the same PDU session. The session management function network element may determine the subsequent procedure based on the type of the first operation.

[0219] For example, when the first operation is to modify the first session (i.e., a procedure of modifying the first session initiated by the network side device), the session management function network element aborts the procedure of modifying the first session and executes a procedure of establishing user plane resources for the first session. For details, see, for example, the related content of the embodiments shown in FIG. 5 and other accompanying figures.

[0220] When the first operation is to release the first session (i.e., a procedure of releasing the first session initiated by the network), the session management function network element rejects the request to establish user plane resources for the first session and continues to execute the procedure of releasing the first session. For details, see, for example, the related content of the embodiments shown in FIG. 6 and other accompanying figures.

[0221] Based on the above collision scenario, an embodiment of this application provides a communication method. When it is determined that a procedure of a first operation (e.g., a procedure of modifying a PDU session) conflicts with a procedure of establishing user plane resources for a PDU session initiated by a terminal device, a session management function network element aborts a current procedure of the first operation and executes a procedure of establishing user plane resources. The following takes the embodiment shown in Figure 5 as an example for illustration.

[0222] Step 501: A session management function network element sends a first message to an access and mobility management function network element, where the first message is used to request a first operation, and the first operation includes modifying a first session or releasing the first session.

[0223] For example, if the first operation is to modify the first session, the first message is a PDU session modify command, and the PDU session modify command includes an identifier of the first session, or if the first operation is to release the first session, the first message is a PDU session release command, and the PDU session release command includes an identifier of the first session.

[0224] For example, the session management function network element sends an N1N2 message forwarding message to the access and mobility management function network element, where the N1N2 message forwarding message includes a session management container, where the session management container includes a first message, where the first message includes an identifier of the first session. The access and mobility management function network element sends a downlink non-access stratum forwarding message to the terminal device using the wireless access device, where the downlink non-access stratum forwarding message includes the session management container.

[0225] For details, see steps 301 to 304 shown in FIG.

[0226] Step 502: The access and mobility management function network element sends a second message to a session management function network element, where the second message is used to request establishing user plane resources for the first session.

[0227] It can be understood from steps 201 to 203 in the procedure shown in FIG. 2 that the terminal device sends a service request message to the wireless access device before the access and mobility management function network element sends the second message to the session management function network element. The service request message includes uplink data status information, and the uplink data status information indicates an identifier of the first session. The wireless access device sends an N2 message to the access and mobility management function network element. The N2 message includes a service request message. The access and mobility management function network element determines the second message based on the service request message. For example, the second message is a session management context update request message, and the session management context update request message includes, for example, one or more of the following: an operation type or an identifier of a valid session, where the operation type indicates user plane activation, and the identifier of the valid session includes an identifier of the first session.

[0228] Step 503: The session management function network element aborts the procedure of the first operation, and the session management function network element performs a procedure to establish user plane resources for the first session when the session management function network element determines that no response message to the first message is received and a second message is received.

[0229] When the session management function network element receives the second message, the session management function network element determines whether a response message to the first message is received. If the session management function network element receives the response message to the first message, the session management function network element executes a procedure to establish user plane resources for the first session. Please refer to the procedure shown in Figure 2. If the session management function network element does not receive a response message to the first message and receives a second message, i.e., the first operation conflicts with the establishment of user plane resources for the first session, the session management function network element may first abort the procedure of the first operation, and the session management function network element executes a procedure to establish user plane resources for the first session.

[0230] If the first operation is to modify the first session, the response message to the first message includes a PDU session modification complete command, where the PDU session modification complete command includes an identifier of the first session, or if the first operation is to release the first session, the response message to the first message includes a PDU session release complete command, where the PDU session release complete command includes an identifier of the first session.

[0231] The session management function network element aborting the procedure of the first operation may include the session management function network element not waiting for a response message to the first message. For example, the session management function network element stops a first timer, and the first timer includes a timer waiting for a response message to the first message. For example, assume that the first operation is to modify a first session, the SMF aborts the procedure of the first operation, and the SMF does not wait for a PDU session modification complete command.

[0232] For example, a procedure in which the session management function network element establishes user plane resources for the first session may include, but is not limited to, one or more of the following steps: the session management function network element sending a session modification request message to the user plane function network element, where the session modification request message is utilized to configure downlink tunnel information for the user plane function network element; the session management function network element receiving a session modification response message from the user plane function network element, where the session modification response message is utilized to respond to the session modification request message; and the session management function network element sending a third message to the access and mobility management function network element in response to the second message, where the third message indicates successful establishment of the user plane resources for the first session. The third message is a session management context update response message, which may, for example, include one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that user plane resources for the first session are enabled, and the session management information includes related parameters for establishing user plane resources for the first session. For example, referring to FIG. 2, the session management function network element performs a procedure for establishing user plane resources for the first session, as shown in steps 204 to 206.

[0233] Additionally, in some embodiments, if the first operation is to modify the first session, when a response message to the first message is not received, a second message is received, and the session management function network element determines that establishing user plane resources for the first session is not requested, the session management function network element aborts the procedure of the first operation, and the session management function network element performs a procedure of establishing user plane resources for the first session. For example, the session management function network element sends an N1N2 message transfer message to the access and mobility management function network element, where the N1N2 message transfer message includes a session management container, where the session management container includes a PDU session modification command, and where the N1N2 message transfer message does not include session management information.

[0234] Furthermore, in some embodiments, after the session management function network element executes the procedure of establishing user plane resources for the first session, the session management function network element may resend the first message to the terminal device, i.e., resume the procedure of requesting the first operation. For example, the SMF resumes the procedure of requesting to modify the first session. For details, see the procedure illustrated in FIG. 3.

[0235] Additionally, in some embodiments, the session management function network element sends a first indication information to the access and mobility management function network element, where the first indication information indicates the first operation. For example, the session management function network element sends an N1N2 message forwarding message to the access and mobility management function network element. The N1N2 message forwarding message includes, for example, one or more of the following: an identifier of the terminal device, an identifier of the first session, a session management container, or the first indication information. The session management container includes a PDU session modification command, where the PDU session modification command includes an identifier of the first session. The access and mobility management function network element sends an N2 request message to the wireless access device, where the N2 request message includes a downlink non-access stratum forwarding message, where the downlink non-access stratum forwarding message includes, for example, one or more of the following: a session management container or the first indication information. The wireless access device sends a downlink non-access stratum forwarding message to the terminal device. When the terminal device decides to send a service request message to an access and mobility management function network element and does not receive a response message (i.e., a service grant message) to the service request message, if the first indication information indicates that the first operation is to modify the first session, the terminal device may discard the first message based on the first indication information. Similarly, if the first indication information indicates that the first operation is to release the first session, the terminal device may discard the first message based on the first indication information.

[0236] According to the method provided in the embodiment shown in Figure 5, when the session management function network element determines that the procedure for modifying (or releasing) a PDU session conflicts with the procedure for establishing user plane resources initiated by the terminal device for that PDU session, i.e., the operation initiated by the network side device conflicts with the operation initiated by the terminal device for the same PDU session, the session management function network element aborts the current procedure for modifying (or releasing) a PDU session and responds to the procedure for establishing user plane resources for the first session. In this way, it is possible to avoid the case where the terminal device and the session management function network element each wait for a response message for a request operation initiated by itself, which causes their respective timers to expire, thereby effectively ensuring the smoothness of the user experience and the service process.

[0237] Based on the above collision scenario, an embodiment of this application provides a communication method.

[0238] When the session management function network element determines that the procedure of the first operation (e.g., a procedure for releasing a PDU session) conflicts with a procedure for establishing user plane resources for a PDU session initiated by the terminal device, the session management function network element responds to the procedure for establishing user plane resources by sending a third message to the access and mobility management function network element, the third message indicating a failure to establish user plane resources for the first session (i.e., a refusal to establish user plane resources). In this case, the session management function network element denies the request to establish user plane resources for the first session and continues to execute the procedure for releasing the first session.

[0239] When the session management function network element determines that the procedure of the first operation (e.g., a procedure for modifying a PDU session) conflicts with the procedure for establishing user plane resources for the PDU session initiated by the terminal device, the session management function network element responds to the procedure for establishing user plane resources by sending a third message to the access and mobility management function network element, the third message indicating successful establishment of user plane resources for the first session (i.e., establishing user plane resources). In this case, the session management function network element continues to execute the procedure for requesting establishment of user plane resources for the first session and the procedure for releasing the first session.

[0240] In the following, the embodiment shown in FIG. 6 is used as an example for explanation.

[0241] Step 601: A session management function network element sends a first message to an access and mobility management function network element, where the first message is used to request a first operation, and the first operation includes modifying a first session or releasing the first session.

[0242] For example, if the first operation is to modify the first session, the first message is a PDU session modify command, and the PDU session modify command includes an identifier of the first session, or if the first operation is to release the first session, the first message is a PDU session release command, and the PDU session release command includes an identifier of the first session.

[0243] For example, the session management function network element sends an N1N2 message forwarding message to the access and mobility management function network element, where the N1N2 message forwarding message includes a session management container, where the session management container includes a first message, where the first message includes an identifier of the first session.

[0244] Step 602: The access and mobility management function network element sends a first message to the terminal device.

[0245] For example, the access and mobility management function network element utilizes the wireless access device to send a downlink non-access stratum transport message to the terminal device, where the downlink non-access stratum transport message includes a session management container.

[0246] It should be noted that the "first message" in step 601 and the "first message" in step 602 may be the same or different. For steps 601 and 602, see steps 301 to 304 shown in FIG.

[0247] Step 603: The terminal device sends a service request message to an access and mobility management function network element, where the service request message is used to request to establish user plane resources for a first session.

[0248] The service request message includes uplink data status information, where the uplink data status information indicates an identifier of the first session.

[0249] For example, the terminal device sends a service request message to the wireless access device. The wireless access device sends an N2 message to the access and mobility management function network element, where the N2 message includes the service request message. For details, see step 201 and step 202 shown in FIG. 2.

[0250] Step 604: The access and mobility management function network element sends a second message to the session management function network element based on the service request message, where the second message is utilized to request establishing user plane resources for the first session.

[0251] For example, the access and mobility management function network element determines the second message based on the service request message in step 603. The second message is a session management context update request message, and the session management context update request message includes, for example, one or more of the following: an operation type, or an identifier of a valid session, where the operation type indicates user plane activation and the identifier of the valid session includes an identifier of the first session. For details, see step 3 illustrated in FIG. 2.

[0252] Step 605: When the session management function network element determines that a response message to the first message is not received and a second message is received, the session management function network element sends a third message to the access and mobility management function network element in response to the second message, where the third message indicates failure to establish user plane resources for the first session, or the third message indicates success in establishing user plane resources for the first session.

[0253] In some embodiments, when the third message indicates successful establishment of user plane resources for the first session, the third message is a session management context update response message, and the session management context update response message includes, for example, one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that the user plane resources for the first session are enabled. The session management information includes related parameters for establishing user plane resources for the first session. For example, here, the related parameters for establishing user plane resources may include, but are not limited to, one or more of the following: PDU Session ID (e.g., PDU Session ID=5), QoS flow identifier, and QoS configuration.

[0254] For example, when the session management function network element determines that, for the same PDU session, a procedure for modifying the PDU session conflicts with a procedure for establishing user plane resources for the PDU session initiated by the terminal device, the session management function network element sends a third message to the access and mobility management function network element, the third message indicating successful establishment of user plane resources for the first session.

[0255] In some other embodiments, when the third message indicates a failure to establish user plane resources for the first session, the third message is a session management context update response message, the session management context update response message includes user plane context status information, and the user plane context status information indicates that the user plane resources for the first session are disabled. In addition, the third message may further include a first cause value, the first cause value indicating a cause for the failure to establish the user plane resources for the first session. For example, the first cause value indicates that the first session is performing a procedure of a first operation.

[0256] For example, when the session management function network element determines that, for the same PDU session, a procedure for releasing the PDU session conflicts with a procedure for establishing user plane resources for the PDU session initiated by the terminal device, the session management function network element sends a third message to the access and mobility management function network element, the third message indicating a failure to establish user plane resources for the first session.

[0257] Additionally, in some embodiments, if the first operation is to modify a first session, when a response message to the first message is not received, a second message is received, and the session management function network element determines for the first session that establishing user plane resources for the first session is not required, the session management function network element sends a third message to the access and mobility management function network element in response to the second message. For example, the session management function network element sends an N1N2 message transfer message to the access and mobility management function network element, where the N1N2 message transfer message includes a session management container, where the session management container includes a PDU session modification command, and where the N1N2 message transfer message does not include session management information.

[0258] Step 606: The access and mobility management function network element sends a service authorization message to the terminal device based on the third message.

[0259] In some embodiments, the third message is a session management context update response message, where the session management context update response message includes, for example, one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that user plane resources for the first session are enabled. The access and mobility management function network element determines a service grant message based on the third message, where the service grant message includes an information element indicating a PDU session validation result, where the information element indicating the PDU session validation result indicates that the establishment of the user plane resources for the first session is successful.

[0260] For example, the access and mobility management function network element further sends an N2 request message to the wireless access device. The N2 request message includes, for example, one or more of the following: a service grant message or session management information in a session management context update response message. The wireless access device sends a service grant message to the terminal device, and the wireless access device interacts with the terminal device based on the session management information to complete the RRC connection reconfiguration. For details, please refer to steps 207 to 212 in the embodiment shown in Figure 2.

[0261] In some embodiments, the third message is a session management context update response message, the session management context update response message including user plane context status information, the user plane context status information indicating that user plane resources for the first session are disabled. The access and mobility management function network element determines a service grant message based on the third message, the service grant message including an information element indicating a PDU session activation result, the information element indicating the PDU session activation result indicating a failure to establish user plane resources for the first session.

[0262] In some embodiments, the third message is a session management context update response message, the session management context update response message includes user plane context status information and a first cause value, the user plane context status information indicates that user plane resources for the first session are disabled, and the first cause value indicates a cause for failure to establish the user plane resources for the first session. The access and mobility management function network element determines a service grant message based on the third message, the service grant message includes an information element indicating a PDU session activation result and an information element indicating an error cause of the PDU session activation result, the information element indicating the PDU session activation result indicates a failure to establish the user plane resources for the first session, and the information element indicating the error cause of the PDU session activation result indicates a cause for failure to establish the user plane resources for the first session. For example, the reason for failure to establish the user plane resources for the first session indicates that the first session is performing a procedure of a first operation.

[0263] Step 607: The terminal device sends a response message to the first message to the access and mobility management function network element.

[0264] The terminal device may cache the first message or the response message to the first message, and after receiving the service authorization message in step 606, send the response message to the first message to the access and mobility management function network element.

[0265] A mobility management layer in the terminal device receives a first message from an access and mobility management function network element.

[0266] After the mobility management layer receives the first message from the access and mobility management function network element, since the procedure initiated by the terminal device requesting to establish user plane resources for the first session conflicts with the procedure initiated by the session management function network element requesting the first operation, in this scenario, the terminal device may send a response message to the first message to the session management function network element by using, but not limited to, the following solution 1 (shown in FIG. 7) and solution 2 (shown in FIG. 8).

[0267] Solution 1: Step 701: The mobility management layer receives a first message from an access and mobility management function network element. (This step may correspond to step 602.)

[0268] Step 702: The mobility management layer sends a first message to the session management layer.

[0269] For example, the session management function network element further sends first indication information to the access and mobility management function network element, where the first indication information indicates the first operation. Specifically, the session management function network element sends an N1N2 message transfer message to the access and mobility management function network element. The N1N2 message transfer message includes, for example, one or more of the following: an identifier of the terminal device, an identifier of the first session, a session management container, or the first indication information. The session management container includes a PDU session release command (or a PDU session modification command), where the PDU session release command includes an identifier of the first session. The access and mobility management function network element sends an N2 request message to the wireless access device, where the N2 request message includes a downlink non-access stratum transfer message, where the downlink non-access stratum transfer message includes the session management container and the first indication information. The wireless access device sends the downlink non-access stratum transfer message to the terminal device. When the first indication information indicates that the first operation is to release the first session (or to modify the first session), the mobility management layer sends a first message to the session management layer based on the first indication information.

[0270] It should be noted that the "first message" in step 701 and the "first message" in step 702 may be the same or different. Step 703: The session management layer sends a response message to the first message to the mobility management layer.

[0271] For example, a response message to a first message may indicate completing the first operation.

[0272] Step 704: The mobility management layer caches the response message to the first message.

[0273] Step 705: The access and mobility management function network element sends the service authorization message in step 606 to the mobility management layer.

[0274] Step 706: The mobility management layer sends a response message to the first message to the access and mobility management function network element (ie, step 607).

[0275] Refer to Figure 7. According to the above solution 1, when a procedure for modifying (or releasing) a PDU session conflicts with a procedure for establishing user plane resources for the PDU session initiated by a terminal device, the mobility management layer sends a first message to the session management layer, and caches a response message to the first message from the session management layer until receiving a service grant message in step 606. The mobility management layer sends the cached response message to the first message to the access and mobility management function network element, thereby effectively ensuring the smoothness of user experience and service process.

[0276] Solution 2: Step 801: The mobility management layer receives a first message from a session management function network element. (This step may correspond to step 602.)

[0277] Step 802: The mobility management layer caches the first message.

[0278] For example, the session management function network element further sends first indication information to the access and mobility management function network element, where the first indication information indicates the first operation. Specifically, the session management function network element sends an N1N2 message transfer message to the access and mobility management function network element. The N1N2 message transfer message includes, for example, one or more of the following: an identifier of the terminal device, an identifier of the first session, a session management container, or the first indication information. The session management container includes a PDU session release command (or a PDU session modification command), where the PDU session release command includes an identifier of the first session. The access and mobility management function network element sends an N2 request message to the wireless access device, where the N2 request message includes a downlink non-access stratum transfer message, where the downlink non-access stratum transfer message includes the session management container and the first indication information. The wireless access device sends the downlink non-access stratum transfer message to the terminal device. When the first indication information indicates that the first operation is to release the first session (or to modify the first session), the mobility management layer caches the first message based on the first indication information.

[0279] Step 803: The access and mobility management function network element sends the service authorization message in step 606 to the mobility management layer.

[0280] Step 804: The mobility management layer sends a first message to the session management layer.

[0281] It should be noted that the "first message" in step 801 and the "first message" in step 804 may be the same or different.

[0282] Step 805: The session management layer sends a response message to the first message to the mobility management layer.

[0283] Step 806: The mobility management layer sends a response message to the first message to the access and mobility management function network element (ie, step 607).

[0284] Refer to Figure 8. According to the above solution 2, when the procedure of modifying (or releasing) a PDU session conflicts with the procedure of establishing user plane resources for the PDU session initiated by the terminal device, the mobility management layer caches the first message until receiving a service authorization message in step 606. The mobility management layer sends the first message to the session management layer and receives a response message for the first message from the mobility management layer. The mobility management layer sends the response message for the first message to the access and mobility management function network element, thereby effectively ensuring the smoothness of the user experience and service process. Comparing solution 2 with the above solution 1, the message cached in solution 1 is the response message for the first message, and the message cached in solution 2 is the first message.

[0285] Step 608: The access and mobility management function network element sends a response message to the first message to the session management network element.

[0286] According to the method provided in the embodiment shown in Figure 6, when the session management function network element determines that the procedure for modifying (or releasing) a PDU session conflicts with the procedure for establishing user plane resources for a PDU session initiated by a terminal device, i.e., the operation initiated by the network side device conflicts with the operation initiated by the terminal device for the same PDU session, the session management function network element sends a third message to the access and mobility management function network element, where the third message indicates that the establishment of user plane resources for the first session fails, or the third message indicates that the establishment of user plane resources for the first session succeeds. In this way, the case that the terminal device and the session management function network element each wait for a response message for a request operation initiated by themselves, which causes their respective timers to expire, can be effectively guaranteed, thereby ensuring the smoothness of user experience and service process.

[0287] In the following, the specific embodiment will be described with reference to the embodiment shown in FIG. 5 and FIG.

[0288] Embodiment 1: A UE is registered in a 5G network, and the UE is in a connected mode. There is currently a valid PDU session context. For example, the identifier of the PDU session is PDU session ID=5, and no user plane resources for the PDU session are established. The following uses an example where the identifier of the PDU session is PDU session ID=5, and describes a scenario in which the procedure of modifying the PDU session initiated by the network side device conflicts with the procedure of establishing user plane resources initiated by the UE for the PDU session, as shown in FIG. 9, and a collision handling process.

[0289] For steps 901 to 907, please refer to steps 401 to 407 in Fig. 4. The details will not be described again.

[0290] Step 908: The SMF determines that the UE is requesting to establish user plane resources for the PDU session with PDU session ID = 5 based on the operation type and the identifier of the valid PDU session in the Session Management Context Update Request message. In addition, the SMF is requesting to modify the PDU session with PDU session ID = 5 and has not received a PDU Session Modify Complete command. The SMF aborts the procedure to modify the PDU session with PDU session ID = 5.

[0291] For example, the SMF stops the timer waiting for the PDU session change complete command.

[0292] For steps 909 to 917, please refer to steps 204 to 212 in Fig. 2. The details will not be described again.

[0293] In some embodiments, the UE discards the PDU session change command.

[0294] In some embodiments, if the N1N2 message transfer message further includes the first indication information, when the AMF sends the N2 request message to the RAN, the downlink non-access stratum transfer message in the N2 request message also includes the first indication information. The RAN sends the downlink non-access stratum transfer message to the UE. When the service request message is sent to the AMF and the UE determines that a response message (i.e., a service grant message) to the service request message is not received, if the first indication information indicates that the first operation is to modify the PDU session with PDU session ID=5, the UE may discard the PDU session modification command based on the first indication information.

[0295] After the procedure for establishing user plane resources for the PDU session with PDU session ID=5 is completed (i.e., after step 917), the SMF may resume the procedure for modifying the PDU session with PDU session ID=5.

[0296] According to the above method, for a PDU session with PDU session ID=5, when a procedure for modifying a PDU session initiated by a network side device conflicts with a procedure for establishing user plane resources initiated by a UE, the SMF aborts the procedure for modifying a PDU session with PDU session ID=5, and performs a procedure for establishing user plane resources for the PDU session with PDU session ID=5, thereby effectively ensuring the smoothness of user experience and service processes.

[0297] Similarly, the above embodiments are also applicable to scenarios and collision handling processes in which a procedure for releasing a PDU session initiated by a network side device conflicts with a procedure for establishing user plane resources initiated by a UE.

[0298] Embodiment 2: The UE is registered with a 5G network, and the UE is in a connected mode. There is currently a valid PDU session context. For example, the identifier of the PDU session is PDU session ID=5, and no user plane resources for the PDU session are established. The following takes an example where the identifier of the PDU session is PDU session ID=5, and describes a scenario and a collision handling process for the PDU session in which the procedure of releasing the PDU session initiated by the network side device conflicts with the procedure of establishing user plane resources initiated by the UE, as shown in FIG. 10.

[0299] Step 1001: The SMF sends an N1N2 message transfer message to the AMF.

[0300] For example, when deciding to initiate a procedure to release a PDU session, the SMF sends an N1N2 message transfer message to the AMF.

[0301] The N1N2 message transfer message may, for example, include one or more of the following: an identifier of the UE, a PDU Session ID (e.g., PDU Session ID=5), or a Session Management Container, where the Session Management Container includes a PDU Session Release Command, which includes a PDU Session ID (e.g., PDU Session ID=5).

[0302] Step 1002: In response to the N1N2 message transfer message, the AMF sends an N1N2 message transfer response message to the SMF.

[0303] Step 1003: The AMF sends an N2 request message to the RAN, where the N2 request message includes a downlink non-access stratum transport message, and the downlink non-access stratum transport message includes the session management container in step 1001.

[0304] Step 1004: The UE sends a service request message to the RAN. The service request message includes uplink data status information, and the uplink data status information indicates a PDU session ID (for example, PDU session ID=5). If the uplink data status information indicates that the PDU session ID=5, it indicates that the UE requests to establish user plane resources for the PDU session with PDU session ID=5.

[0305] Step 1005: The RAN sends a downlink non-access stratum forwarding message to the UE.

[0306] Step 1006: The RAN sends an N2 message to the AMF. The N2 message includes the service request message in step 1004.

[0307] Step 1007: The AMF sends a session management context update request message to the SMF.

[0308] The AMF determines, based on the service request message in step 1006, that the UE is requesting to establish user plane resources for a PDU session with PDU session ID = 5. The session management context update request message may, for example, include one or more of the following: an operation type or an identifier of a valid PDU session (e.g., PDU session ID = 5), where the operation type indicates user plane activation.

[0309] Step 1008: The SMF determines that the UE requests to establish user plane resources for the PDU session with PDU session ID=5 based on the operation type and the identifier of the valid PDU session in the Session Management Context Update Request message. In addition, the SMF requests to release the PDU session with PDU session ID=5 and has not received a PDU Session Release Complete command. The SMF sends a Session Management Context Update Response message to the AMF. The Session Management Context Update Response message indicates a failure to establish user plane resources for the PDU session with PDU session ID=5. The Session Management Context Update Response message includes user plane context status information or the Session Management Context Update Response message includes user plane context status information and a cause value (cause). The user plane context status information indicates that the user plane resources for the PDU session with PDU session ID=5 are disabled, and the cause value indicates that a procedure to release the PDU session is performed for the PDU session with PDU session ID=5.

[0310] Step 1009: The AMF sends an N2 message to the RAN, where the N2 message includes a service authorization message.

[0311] The AMF determines a service authorization message based on the session management context update response message. The service authorization message includes a PDU session activation result. Alternatively, the service authorization message includes a PDU session activation result and an error cause of the PDU session activation result. The PDU session activation result indicates that the establishment of user plane resources for the PDU session with PDU session ID=5 fails. For example, if the bit position corresponding to the PDU session ID=5 is 1, it indicates that the establishment of user plane resources for the PDU session with PDU session ID=5 fails. The error cause of the PDU session activation result indicates that a procedure is performed to release the PDU session with PDU session ID=5. In addition, the error cause of the PDU session activation result may indicate other contents. This is not limited here.

[0312] Step 1010: The RAN sends a service grant message to the UE.

[0313] Step 1011: The UE determines based on the service grant message in step 1009 that the establishment of user plane resources for the PDU session with PDU session ID=5 fails, and the UE sends a PDU session release complete command to the RAN.

[0314] Specifically, in a possible implementation, after receiving the PDU session release command, the 5GMM layer of the UE may cache the PDU session release command, and after receiving a service grant message in step 1010, the 5GMM layer sends the PDU session release command to the 5GSM layer, the 5GSM layer sends a PDU session release complete command to the 5GMM layer, and the 5GMM layer sends the PDU session release complete command to the RAN.

[0315] In a possible implementation, the N1N2 message transfer message may further include first indication information, where the first indication information indicates that the first operation is to release the first session. When the AMF sends the N2 request message to the RAN, the downlink non-access stratum transfer message in the N2 request message also includes the first indication information. The RAN sends the downlink non-access stratum transfer message to the UE. After receiving the PDU session release complete command and the first indication information, the 5GMM layer of the UE may cache the PDU session release command based on the first indication information, and after receiving the service grant message in step 1010, the 5GMM layer sends the PDU session release command to the 5GSM layer, and the 5GSM layer sends the PDU session release complete command to the 5GMM layer, and the 5GMM layer sends the PDU session release complete command to the RAN.

[0316] In a possible implementation, after receiving the PDU session release command, the 5GMM layer of the UE may send a PDU session release command to the 5GSM layer, and the 5GSM layer sends a PDU session release complete command to the 5GMM layer. The 5GMM layer may cache the PDU session release complete command, and after receiving the service grant message in step 1010, the 5GMM layer sends the PDU session release complete command to the RAN.

[0317] In a possible implementation, the N1N2 message transfer message may further include first indication information, where the first indication information indicates that the first operation is to release the first session. When the AMF sends the N2 request message to the RAN, the downlink non-access stratum transfer message in the N2 request message also includes the first indication information. The RAN sends the downlink non-access stratum transfer message to the UE. After receiving the PDU session release command and the first indication information, the 5GMM layer of the UE may send a PDU session release command to the 5GSM layer based on the first indication information, and the 5GSM layer sends a PDU session release complete command to the 5GMM layer. The 5GMM layer may cache the PDU session release complete command, and after receiving the service grant message in step 1010, the 5GMM layer sends the PDU session release complete command to the RAN.

[0318] Step 1012: The RAN sends an N2 message to the AMF, where the N2 message includes a PDU session release complete command in step 1111.

[0319] Step 1013: The AMF sends a session management context update request message to the SMF, where the session management context update request message includes a PDU session release complete command.

[0320] Step 1014: The SMF sends a session management context update response message to the AMF, where the session management context update response message is used to respond to the session management context update request message.

[0321] In the above method, when a procedure for releasing a PDU session, which is PDU session ID=5, initiated by a network side device collides with a procedure for requesting user plane resources, which is initiated by a UE, the SMF sends an update context response message in response to the update context request message. The update context response message includes, for example, user plane context status information, or the update context response message includes, for example, user plane context status information and a cause value. The AMF sends a service allow message to the UE based on the update context response message, where the service allow message includes a PDU session activation result, or the service allow message includes a PDU session activation result and an error cause of the PDU session activation result. After receiving the service allow message, the UE sends a PDU session release complete command in response to the PDU session release command.

[0322] Similarly, the above embodiments are also applicable to scenarios in which a procedure for modifying a PDU session initiated by a network side device conflicts with a procedure for establishing user plane resources initiated by a UE, and the collision handling process.

[0323] Embodiment 3: The UE is registered in a 5G network, and the UE is in a connected mode. There is currently a valid PDU session context. For example, the identifier of the PDU session is PDU session ID=5, and no user plane resources for the PDU session are established. The following takes an example where the identifier of the PDU session is PDU session ID=5, and describes a scenario and a collision handling process for the PDU session in which the procedure for modifying the PDU session initiated by the network side device conflicts with the procedure for establishing user plane resources initiated by the UE, as shown in FIG. 11.

[0324] For steps 1101 to 1107, please refer to steps 401 to 407 in Fig. 4. The details will not be described again.

[0325] Step 1108: The SMF determines that the UE requests to establish user plane resources for the PDU session with PDU Session ID=5 based on the operation type and the identifier of the valid PDU session in the Session Management Context Update Request message. In addition, the SMF requests to modify the PDU session with PDU Session ID=5 and has not received a PDU Session Modify Complete command. The SMF sends a Session Management Context Update Response message to the AMF. The Session Management Context Update Response message indicates successful establishment of user plane resources for the PDU session with PDU Session ID=5, and the Session Management Context Update Response message includes, for example, one or more of the following: user plane context status information or session management information, where the user plane context status information indicates that the user plane resources for the PDU session with PDU Session ID=5 are enabled. The session management information includes related parameters for establishing user plane resources for the PDU session with PDU Session ID=5. For example, here, relevant parameters for establishing user plane resources may include, but are not limited to, one or more of the following: PDU Session ID (e.g., PDU Session ID=5), QoS flow identifier, and QoS configuration.

[0326] Step 1109: The AMF sends an N2 message to the RAN, where the N2 message includes, for example, one or more of the following: a service authorization message and session management information.

[0327] The AMF determines a service grant message based on the session management context update response message. The service grant message includes a PDU session activation result. The PDU session activation result indicates that the user plane resources for the PDU session with PDU session ID=5 are successfully established. For example, if the bit position corresponding to PDU session ID=5 is 0, it indicates that the user plane resources for the PDU session with PDU session ID=5 are successfully established.

[0328] Step 1110: The RAN sends an RRC connection reconfiguration message to the UE.

[0329] The RAN determines the DRB configuration information based on the session management information in the N2 request message. The DRB configuration information includes a PDU session ID (eg, PDU session ID=5).

[0330] The RRC connection reconfiguration message may, for example, include one or more of the following: a service grant message and DRB configuration information.

[0331] For steps 1111 to 1114, please refer to steps 209 to 212 in Fig. 2. The details will not be described again.

[0332] The UE sends an RRC connection reconfiguration complete message to the RAN.

[0333] Step 1115: The UE determines based on the service grant message in step 1110 that the user plane resources for the PDU session with PDU session ID=5 are successfully established, and the UE sends a PDU session change complete command to the RAN.

[0334] For steps 1116 to 1118, please refer to steps 306 to 308 in Fig. 3. The details will not be described again.

[0335] It can be understood that steps 1111 to 1114 are independent of steps 1115 to 1117 and correspond to different procedures.

[0336] According to the above method, for a PDU session with PDU session ID=5, when a procedure for modifying a PDU session initiated by a network side device conflicts with a procedure for establishing user plane resources initiated by a UE, the SMF responds to the update context request message by sending an update context response message. The update context response message includes, for example, one or more of the following: user plane context status information or session management information. The AMF sends a service allow message to the UE based on the update context response message, where the service allow message includes a PDU session activation result. After receiving the service allow message, the UE responds to the PDU session modify command by sending a PDU session modify complete command, and completes the DRB configuration by interacting with the RAN.

[0337] 12 is a possible exemplary block diagram of an apparatus according to an embodiment of this application. The apparatus 1200 includes a transceiver module 1210 and a processing module 1220. The transceiver module 1210 may include a receiving unit and a transmitting unit. The processing module 1220 is configured to control and manage the actions of the apparatus 1200. The transceiver module 1210 is configured to support the apparatus 1200 in communicating with other network entities. Optionally, the apparatus 1200 may further include a storage unit, which is configured to store program codes and data of the apparatus 1200.

[0338] Optionally, each module of the apparatus 1200 may be implemented using software.

[0339] Optionally, the processing module 1220 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or a combination thereof. The processing module 1220 may implement or execute various exemplary logic blocks, modules, and circuits described in connection with the contents disclosed in the embodiments of this application. The processor may be a combination of processors that implement computing functions, such as a combination of one or more microprocessors, or a combination of a DSP and a microprocessor. The transceiver module 1210 may be a communication interface, a transceiver, a transceiver circuit, or the like. The communication interface is a general term. In a specific implementation, the communication interface may include multiple interfaces, and the storage unit may be a memory.

[0340] When the device 1200 is a session management function network element or a chip within a session management function network element, the processing module 1220 within the device 1200 may support the device 1200 in performing the actions of the session management function network element in the above example methods, for example, may support the device 1200 in performing step 503 of FIG. 5 and step 908 of FIG. 9.

[0341] The transceiver module 1210 may support communication between the device 1200 and an access and mobility management function network element. For example, the transceiver module 1210 may support the device 1200 in performing steps 501 and 503 of Figure 5, steps 601, 604, 605, and 608 of Figure 6, steps 1001, 1002, 1007, 1010, 1011, 1016, and 1017 of Figure 10, and steps 1101, 1102, 1107, 1108, 1113, 1114, 1117, and 1118 of Figure 11.

[0342] For example, details may be as follows: In an implementation, the apparatus 1200 includes a transceiver module 1210 and a processing module 1220.

[0343] The transceiver module 1210 is configured to initiate a procedure of a first operation for a first session and receive a request from an access and mobility management function network element to establish user plane resources for the first session in the process of performing the first operation.

[0344] The processing module 1220 is configured to determine a subsequent procedure based on the type of the first operation.

[0345] In a possible design, the first operation is to modify the first session, and the processing module 1220 is configured to, when determining a subsequent procedure based on the type of the first operation, abort the procedure of modifying the first session and perform a procedure of establishing user plane resources for the first session.

[0346] In a possible design, the first operation is to release the first session, and the processing module 1220, when determining a subsequent procedure based on the type of the first operation, is configured to reject the request to establish user plane resources for the first session and continue to execute the procedure to release the first session.

[0347] In an implementation, the apparatus 1200 includes a transceiver module 1210 and a processing module 1220 .

[0348] The transceiver module 1210 is configured to: send a first message to the access and mobility management function network element, where the first message is utilized to request a first operation, the first operation including modifying the first session or releasing the first session, and receive a second message from the access and mobility management function network element after the session management function network element sends the first message, where the second message is utilized to request establishing user plane resources for the first session.

[0349] The processing module 1220 is configured to abort a procedure of the first operation and perform a procedure of establishing user plane resources for the first session when it determines that a response message to the first message is not received and a second message is received.

[0350] In an implementation, the apparatus 1200 includes a transceiver module 1210 .

[0351] The transceiver module 1210 is configured to: send a first message to the access and mobility management function network element, the first message being used to request a first operation, the first operation including modifying the first session or releasing the first session, and after sending the first message, receive a second message from the access and mobility management function network element, the second message being used to request establishing user plane resources for the first session. When the processing module 1220 determines that no response message to the first message is received and a second message is received, the transceiver module 1210 is configured to send a third message to the access and mobility management function network element in response to the second message, the third message indicating a failure to establish the user plane resources for the first session or a success to establish the user plane resources for the first session.

[0352] It should be understood that the apparatus 1200 in this embodiment of the present application may correspond to the method of the session management function network element in the above method embodiment, for example, the method of Fig. 5. The functions of the operations and / or modules in the apparatus 1200 are respectively utilized to implement the corresponding steps of the method of the session management function network element in the above method embodiment. Thus, the advantageous effects in the above method embodiment can also be realized. For the sake of brevity, the details will not be described again here.

[0353] When the apparatus 1200 is a terminal device or a chip in a terminal device, the processing module 1220 of the apparatus 1200 may support the apparatus 1200 in performing the actions of the session management function network element in the above example methods, for example, supporting the apparatus 1200 in performing step 503 of FIG. 5 and step 908 of FIG. 9.

[0354] The transceiver module 1210 may support communication between the device 1200 and an access and mobility management function network element. For example, the transceiver module 1210 may support the device 1200 in performing steps 602, 603, 606, and 607 of Figure 6, steps 702 and 703 of Figure 7, steps 804 and 805 of Figure 8, steps 904, 905, 913, and 914 of Figure 9, steps 1004, 1005, 1010, and 1011 of Figure 10, and steps 1104, 1105, 1110, 1111, and 1115 of Figure 11.

[0355] For example, details may be as follows: In an implementation, the apparatus 1200 includes a transceiver module 1210 and a processing module 1220.

[0356] The transceiver module 1210 is configured to send a service request message to an access and mobility management function network element, where the service request message is utilized to request establishing user plane resources for a first session, and to receive a first message from the access and mobility management function network element, where the first message is utilized to request a first operation, where the first operation includes modifying the first session or releasing the first session.

[0357] The processing module 1220 is configured to cache the first message or a response message to the first message until the transceiver module 1210 receives a service authorization message from the access and mobility management function network element. The processing module 1220 causes the transceiver module 1210 to transmit the response message to the first message to the access and mobility management function network element.

[0358] In an implementation, the apparatus 1200 includes a transceiver module 1210 and a processing module 1220 .

[0359] The transceiver module 1210 is configured to send a service request message to an access and mobility management function network element, where the service request message is utilized to request establishing user plane resources for a first session, and to receive a first message from the access and mobility management function network element, where the first message is utilized to request a first operation, where the first operation includes modifying the first session or releasing the first session.

[0360] The processing module 1220 is configured to discard the first message when it determines that a service request message has been sent and no response message to the service request message has been received.

[0361] It should be understood that the apparatus 1200 in this embodiment of the present application may correspond to a method of a terminal device, for example, the method of Fig. 5. The functions of the operations and / or modules in the apparatus 1200 are respectively utilized to implement corresponding steps of the method of the terminal device in the above method embodiment. Thus, the advantageous effects in the above method embodiment can also be realized. For the sake of brevity, the details will not be described again here.

[0362] When the processing module 1220 in this embodiment of the application is a processor and the transceiver module 1210 is a transceiver, the apparatus 1200 in this embodiment of the application may be the apparatus 1300 shown in FIG.

[0363] 13 is a schematic diagram of a structure of a communication device 1300 according to an embodiment of the present application. As shown in FIG. 13, the device 1300 includes: a processor 1301.

[0364] When the apparatus 1300 is a session management function network element or a chip within a session management function network element, in a possible implementation, the processor 1301 is configured to invoke an interface to perform the following actions: initiating a procedure of a first operation for a first session; receiving a request to establish user plane resources for the first session from the access and mobility management function network element in the process of performing the first operation; and determining subsequent procedures based on the type of the first operation.

[0365] When the apparatus 1300 is a session management function network element or a chip in a session management function network element, in a possible implementation, the processor 1301 is configured to invoke the interface to perform the following actions: sending a first message to the access and mobility management function network element, where the first message is used to request a first operation, the first operation including modifying the first session or releasing the first session; receiving a second message from the access and mobility management function network element after the session management function network element sends the first message, where the second message is used to request establishing user plane resources for the first session; and when it is determined that a response message to the first message is not received and a second message is received, aborting the procedure of the first operation and performing a procedure of establishing user plane resources for the first session.

[0366] When the apparatus 1300 is a session management function network element or a chip in a session management function network element, in a possible implementation, the processor 1301 is configured to invoke the interface to perform the following actions: sending a first message to the access and mobility management function network element, where the first message is used to request a first operation, the first operation including modifying the first session or releasing the first session; receiving a second message from the access and mobility management function network element after sending the first message, where the second message is used to request establishing user plane resources for the first session; and when it is determined that a response message to the first message is not received and a second message is received, sending a third message to the access and mobility management function network element in response to the second message, where the third message indicates a failure to establish the user plane resources for the first session or a success to establish the user plane resources for the first session.

[0367] It should be understood that the apparatus 1300 may be further configured to perform other steps and / or operations of the session management function network element side in the above embodiments, and for the sake of brevity, the details will not be described again here.

[0368] When the apparatus 1300 is a terminal device or a chip in a terminal device, in a possible implementation, the processor 1301 is configured to invoke the interface to perform the following actions: sending a service request message to an access and mobility management function network element, where the service request message is used to request establishing user plane resources for a first session; receiving a first message from the access and mobility management function network element, where the first message is used to request a first operation, where the first operation includes modifying the first session or releasing the first session; caching the first message or a response message to the first message until receiving a service authorization message from the access and mobility management function network element, and sending the response message to the first message to the access and mobility management function network element.

[0369] When the apparatus 1300 is a terminal device or a chip in a terminal device, in a possible implementation, the processor 1301 is configured to invoke the interface to perform the following actions: sending a service request message to an access and mobility management function network element, where the service request message is used to request establishing user plane resources for a first session; receiving a first message from the access and mobility management function network element, where the first message is used to request a first operation, where the first operation includes modifying the first session or releasing the first session; and discarding the first message when it is determined that the service request message has been sent and no response message to the service request message has been received.

[0370] It should be understood that the apparatus 1300 may be further configured to perform other steps and / or operations on the terminal device side in the above embodiments, and for the sake of brevity, the details will not be described again here.

[0371] It should be understood that the processor 1301 may invoke an interface to perform the above receiving and transmitting actions. The invoked interface may be a logical interface or a physical interface, without being limited thereto. Optionally, the physical interface may be implemented using a transceiver. Optionally, the apparatus 1300 further includes a transceiver 1303.

[0372] Optionally, the apparatus 1300 further includes a memory 1302, which stores program codes in the above method embodiments, so that the processor 1301 can invoke the program codes.

[0373] Specifically, when the device 1300 includes a processor 1301, a memory 1302, and a transceiver 1303, the processor 1301, the memory 1302, and the transceiver 1303 communicate with each other via an internal connection path to transmit control signals and / or data signals. In a possible design, the processor 1301, the memory 1302, and the transceiver 1303 may be implemented using chips. The processor 1301, the memory 1302, and the transceiver 1303 may be implemented in the same chip or separately in different chips, or any two functions of the following, i.e., the processor 1301, the memory 1302, and the transceiver 1303, are implemented in one chip. The memory 1302 may store program codes, and the processor 1301 calls the program codes stored in the memory 1302 to implement corresponding functions of the device 1300.

[0374] The method disclosed in the embodiments of this application may be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps in the above method embodiments may be implemented using hardware integrated logic circuits in the processor or using instructions in the form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD) or other integrated chip. It may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor, the processor may be any conventional processor, etc. The steps of the methods disclosed in relation to the embodiments of this application may be directly executed and completed using a hardware decoding processor, or may be executed and completed using a combination of hardware and software modules in the decoding processor.The software module may be arranged in a storage medium matured in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register, etc. The storage medium is arranged in the memory, and the processor reads the information in the memory and works in cooperation with the hardware of the processor to complete the steps in the above method.

[0375] It may be understood that the memory in this embodiment of the application may be volatile memory, non-volatile memory, or may include volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM) used as an external cache. By way of example and not limitation, many forms of RAM may be utilized, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus dynamic random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein includes, but is not limited to, these and any other suitable types of memory.

[0376] It should be understood that in the embodiments of this application, the numbers "first", "second", etc. are used merely to distinguish different objects, e.g., to distinguish different parameter information or messages, and do not constitute a limitation on the scope of the embodiments of this application, and this embodiment of this application is not limited thereto.

[0377] It should be further understood that the sequence numbers of the above processes do not mean the execution order in the embodiments of this application. The execution order of the processes should be determined based on the functions and internal logic of the processes. The numbers or sequence numbers in the above processes are merely for distinction and ease of description, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0378] It should also be understood that the term "and / or" in this specification describes only an association relationship to describe related objects and represents that three relationships may exist. For example, A and / or B may represent the following three cases: only A exists, both A and B exist, and only B exists. In addition, the symbol " / " in this specification generally indicates an "or" relationship between related objects.

[0379] Unless otherwise specified, expressions used in this application similar to the expression "the item includes one or more of the following: A, B, and C" usually mean that the item can be any one of the following: A, B, C, A and B, A and C, B and C, A and B and C, A and A, A and A and A, A and A and B, A and A and C, A and B and B, A and C and C, B and B, B and B and B, B and B and C, C and C, C and C and C, and other combinations of A, B, and C. In the above explanation, three elements A, B, and C are used as examples to describe the optional cases of the item. When the expression is "the item includes at least one of the following: A, B, ..., X", in other words, when more elements are included in the expression, the cases in which the item is applicable can also be obtained according to the above rules.

[0380] Those skilled in the art may realize that the units and algorithm steps, in combination with the examples described in the embodiments disclosed in this specification, may be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the design constraints of a specific application and technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but the implementation should not be considered as departing from the scope of this application.

[0381] For the purpose of convenient and concise description, it can be obviously understood by those skilled in the art that the detailed operation processes of the above systems, devices and units should be referred to the corresponding processes in the above method embodiments, and the details will not be described again here.

[0382] In some embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiment described is merely an example. For example, the division into units is merely a logical division of functions, and in actual implementation, there may be other divisions. For example, multiple units or components may be combined or integrated into other systems, and some features may be omitted or not implemented. In addition, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented using some interfaces. Indirect or communication connections between devices or units may be implemented in electrical, mechanical, or other forms.

[0383] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, located in one place or distributed over multiple network units. Some or all of the units may be selected based on the actual requirements to achieve the objectives of the solutions of the embodiments.

[0384] In addition, the functional units in the embodiments of this application may be integrated into a single processing unit, each of the units may exist physically independent, or two or more units may be integrated into a single unit.

[0385] When a function is implemented in the form of a software functional unit and sold or used independently as a product, the function may be stored in a computer-readable storage medium. Based on such understanding, the solution of this application may be essentially implemented in the form of a software product, or a part of the technical solution may be implemented in the form of a software product. The software product is stored in a storage medium and includes some instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of this application. The above storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

[0386] The above description is merely a specific implementation of this application, and is not intended to limit the scope of protection of this application. Any variations or replacements that are immediately understood by those skilled in the art within the technical scope disclosed in this application should fall within the scope of protection of this application. Therefore, the scope of protection of this application should be subject to the scope of protection of the claims.

Claims

1. 1. A method of communication, comprising: initiating, by a Session Management Function network element, a procedure of a first operation for a first session; receiving, by the session management function network element, from an access and mobility management function network element, a request to establish user plane resources for the first session in a process of performing the first operation; determining, by the Session Management Function network element, a subsequent procedure based on a type of the first operation; Including, the first operation is to modify the first session; determining, by the Session Management Function network element, a subsequent procedure based on a type of the first operation, 20. A method of communication comprising: aborting, by the Session Management Function network element, a procedure for modifying the first session; and performing a procedure for establishing the user plane resources for the first session.

2. and after the Session Management Function network element completes the procedure of establishing the user plane resources for the first session, resuming, by the Session Management Function network element, the procedure of modifying the first session. The method of claim 1.

3. The step of performing, by the Session Management Function network element, a procedure for establishing the user plane resources for the first session, further comprising: sending, by the session management function network element, a first message to the access and mobility management function network element, the first message indicating successful establishment of the user plane resources for the first session; The method according to claim 1 or 2.

4. the first message is a session management context update response message, the session management context update response message including one or more of the following: user plane context status information and session management information, the user plane context status information indicating that the user plane resources for the first session are enabled, and the session management information including relevant parameters for establishing the user plane resources for the first session. The method according to claim 3.

5. A communication method, comprising: initiating, by a Session Management Function network element, a procedure of a first operation for a first session; receiving, by the session management function network element, from an access and mobility management function network element, a request to establish user plane resources for the first session in a process of performing the first operation; determining, by the Session Management Function network element, a subsequent procedure based on a type of the first operation; Including, the first operation is to release the first session; determining, by the Session Management Function network element, a subsequent procedure based on a type of the first operation, and continuing to perform, by the Session Management Function network element, a procedure of rejecting the request to establish the user plane resources for the first session and releasing the first session. method.

6. The step of rejecting, by the Session Management Function network element, the request to establish the user plane resources for the first session, further comprising: sending, by the session management function network element, a second message to the access and mobility management function network element, the second message indicating a failure to establish the user plane resources for the first session; The method according to claim 5.

7. the second message is a session management context update response message, the session management context update response message including user plane context status information, the user plane context status information indicating that the user plane resources for the first session are invalid. The method according to claim 6.

8. the second message includes a first cause value, the first cause value indicating a cause for failure to establish the user plane resources for the first session. The method according to claim 6 or 7.

9. indicating that the cause of the failure to establish the user plane resources for the first session is that the first session is performing the procedure to release the first session. The method according to claim 8.

10. 1. A communication device, comprising: A memory for storing instructions; Executing the instructions to cause the device to: initiating a procedure of a first operation for a first session; receiving, from an access and mobility management function network element, a request to establish user plane resources for the first session in the process of performing the first operation; determining a subsequent procedure based on the type of the first operation; A processor configured to: Including, the first operation is to modify the first session; The processor executes the instructions to cause the device to: causing a procedure for modifying the first session to be aborted and a procedure for establishing the user plane resources for the first session to be performed. It is configured as follows: Communications equipment.

11. The processor executes the instructions to cause the device to: resuming the procedure for modifying the first session after completing the procedure for establishing the user plane resources for the first session. further comprising:

11. The apparatus of claim 10.

12. The processor executes the instructions to cause the device to: causing a first message to be sent to the access and mobility management function network element when performing the procedure of establishing the user plane resources for the first session. and wherein the first message indicates successful establishment of the user plane resources for the first session.

11. The apparatus of claim 10.

13. A communication device, comprising: A memory for storing instructions; Executing the instructions to cause the device to: initiating a procedure of a first operation for a first session; receiving, from an access and mobility management function network element, a request to establish user plane resources for the first session in the process of performing the first operation; determining a subsequent procedure based on the type of the first operation; A processor configured to: Including, the first operation is to release the first session; The processor executes the instructions to cause the device to: causing the request to establish the user plane resources for the first session to be rejected and continuing to execute procedures for releasing the first session. further comprising: Device.

14. The processor executes the instructions to cause the device to: causing the access and mobility management function network element to send a second message when rejecting the request to establish the user plane resources for the first session. and wherein the second message indicates a failure to establish the user plane resources for the first session.

14. The apparatus of claim 13.

15. the second message includes a first cause value, the first cause value indicating a cause for failure to establish the user plane resources for the first session.

15. The apparatus of claim 14.

16. indicating that the cause of the failure to establish the user plane resources for the first session is that the first session is performing the procedure to release the first session.

16. The apparatus of claim 15.

17. A computer-readable storage medium, the storage medium storing a computer program or instructions, the computer program or instructions being executed by a communication device to cause the device to: initiating a procedure of a first operation for a first session; receiving, from an access and mobility management function network element, a request to establish user plane resources for the first session in the process of performing the first operation; determining a subsequent procedure based on a type of the first operation; the first operation is modifying the first session, and the computer program or the instructions, when executed by the device, cause the device to abort the procedure for modifying the first session and to perform a procedure for establishing the user plane resources for the first session. A computer-readable storage medium.

18. A computer-readable storage medium, the storage medium storing a computer program or instructions, the computer program or instructions being executed by a communications device to cause the device to: initiating a procedure of a first operation for a first session; receiving, from an access and mobility management function network element, a request to establish user plane resources for the first session in the process of performing the first operation; determining a subsequent procedure based on a type of the first operation; the first operation is to release the first session, and the computer program or the instructions, when executed by the device, cause the device to reject the request to establish the user plane resources for the first session and to continue executing a procedure to release the first session. A computer-readable storage medium.

Images