User equipment and method for data service context state synchronization

Abstract

The present application provides a user equipment and method for synchronizing the data service context state, including: a receiver unit receives a rejection message sent by a core network; a processing unit checks whether the user plane resources of the data unit are released or checks whether there are duplicate data units locally or whether the existing data units have reached the upper limit, and if it is determined that the user plane resources of the data unit are not released or there are no duplicate data units or the existing data units have not reached the upper limit, then actively trigger the synchronization data service context state process; a transmitter unit sends a synchronization message to the core network to synchronize the data service context state, and the access network sends a message to release the user plane resources of the data unit; a receiver unit receives a message to release the user plane resources of the data unit sent by the access network; and a processing unit releases the user plane resources of the data unit. The user plane resources are judged by the user equipment, and the data service context states of the network side and the user equipment are synchronized.

Description

Technical Field

[0001] The present application relates to the field of wireless network technology, and in particular to a user equipment and method for synchronizing data service context status. Background Art

[0002] According to the existing communication protocol or in the existing technology, after the UE is rejected for deactivation, there may be redundant user resources. The UE can only release the redundant user plane resources when it enters the idle state. However, if the UE continuously uses data services, the UE will always be in the connected state and will not release the redundant user plane resources. However, at this time, the data service context of the UE and the network side is not synchronized. In addition, for scenarios where the same APN does not allow the activation of multiple PDNs, it is necessary to wait for the user device to re-register or shut down to synchronize the data service status with the network side, which will cause the user device to be unable to use data services for a long time. Summary of the invention

[0003] The present application provides a user equipment and method for synchronizing data service context status, so as to solve the problem of data service context status being out of synchronization between the user equipment and the network side.

[0004] In a first aspect, a user equipment for synchronizing a data service context state is provided, including:

[0005] A receiver unit, configured to receive a rejection message sent by the core network;

[0006] A processing unit, configured to locally check whether the user plane resources of the data unit are released or whether there are duplicate data units locally or whether the existing data units have reached an upper limit, and if it is determined that the access network has not released the user plane resources of the data unit or there are no duplicate data units or the existing data units have not reached the upper limit, actively triggering a synchronous data service context state process;

[0007] A transmitter unit, configured to send a synchronization data service context state message to the core network, so that the core network synchronizes the data service context state, thereby causing the access network to issue a message for releasing user plane resources of the data unit;

[0008] The receiver unit is further configured to receive a message sent by the access network to release user plane resources of the data unit;

[0009] The processing unit is further configured to release the user plane resources of the data unit based on a message for releasing the user plane resources of the data unit.

[0010] In one implementation, the core network includes a 4G core network and a 5G core network.

[0011] In one implementation, when the core network is a 4G core network, the data unit is a PDN; when the core network is a 5G core network, the data unit is a PDU session.

[0012] In one implementation, it further includes:

[0013] The receiver unit is configured to receive a deactivation rejection message sent by the core network;

[0014] The processing unit is used to locally deactivate the data unit, check whether the user plane resources of the data are released, and actively trigger the synchronization data service context state process if it is determined that the access network has not released the user plane resources of the data unit;

[0015] The transmitter unit is used to send a synchronization data service context state request message to the core network, wherein the synchronization data service context state request message includes the data service context state of the data unit, so that the core network synchronizes the data service context state of the data unit, and then the access network sends a message to release the user plane resources of the data unit;

[0016] The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the data unit, and a synchronous data service context state acceptance message from the core network, wherein the synchronous data service context state acceptance message includes a data service context state of the data unit after the user plane resources of the data unit are released;

[0017] The processing unit is further configured to release the user plane resources of the data unit based on a message for releasing the user plane resources of the data unit;

[0018] The transmitter unit is also used to send a data unit synchronization completion message to the core network.

[0019] In one implementation, it further includes:

[0020] The receiver unit is used to receive a data service connection or establishment message sent by the core network; the data service connection or establishment message includes a data service connection or establishment cause value;

[0021] The processing unit is used to actively trigger a synchronization data service context state process based on the data service connection or establishment reason value and the data service context state of the data unit;

[0022] The transmitter unit is used to send a synchronization data service context state request message to the core network, wherein the synchronization data service context state request message includes the data service context state of the data unit, so that the core network synchronizes the data service context state of the data unit, and then the access network sends a message to release the user plane resources of the data unit;

[0023] The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the data unit, and a synchronous data service context state acceptance message from the core network, wherein the synchronous data service context state acceptance message includes a data service context state of the data unit after the user plane resources of the data unit are released;

[0024] The processing unit is further configured to release the user plane resources of the data based on a message for releasing the user plane resources of the data unit;

[0025] The transmitter unit is further configured to send a synchronous data service context status completion message to the core network and re-initiate an activation request.

[0026] In one implementation, it further includes:

[0027] The receiver unit is used to receive a PDN disconnection data service connection message sent by the 4G core network;

[0028] The processing unit is configured to locally deactivate the PDN, check whether the user plane resources of the PDN are released, and actively trigger the TAU process if it is determined that the access network has not released the user plane resources of the PDN;

[0029] The transmitter unit is configured to send a TAU request message to the 4G core network, wherein the TAU request message includes the EPS bearer state of the PDN, so that the 4G core network synchronizes the EPS bearer state of the PDN, thereby causing the access network to issue a message for releasing user plane resources of the PDN;

[0030] The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the PDN, and a TAU acceptance message from the 4G core network, wherein the TAU acceptance message includes an EPS bearer status of the PDN after the user plane resources of the PDN are released;

[0031] The processing unit is further configured to release the user plane resources of the PDN based on a message for releasing the user plane resources of the PDN;

[0032] The transmitter unit is also used to send a TAU completion message to the 4G core network.

[0033] In one implementation, it further includes:

[0034] The receiver unit is used to receive a PDU session release rejection message sent by the 5G core network;

[0035] The processing unit is configured to locally deactivate the PDU, check whether the user plane resources of the PDU session are released, and actively trigger the mobility registration process if it is determined that the access network has not released the user plane resources of the PDU session;

[0036] The transmitter unit is configured to send a mobility registration request message to the 5G core network, wherein the mobility registration request message includes the state of the PDU session, so that the 5G core network synchronizes the state of the PDU session, thereby causing the access network to issue a message for releasing user plane resources of the PDU session;

[0037] The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the PDU session, and a mobility registration acceptance message from the 5G core network, wherein the mobility registration acceptance message includes a state of the PDU session after the user plane resources of the PDU session are released;

[0038] The processing unit is further configured to release the user plane resources of the PDU session based on a message for releasing the user plane resources of the PDU session;

[0039] The transmitter unit is also used to send a mobility registration completion message to the 5G core network.

[0040] In one implementation, it further includes:

[0041] The receiver unit is configured to receive a PDN data service connection rejection message sent by the 4G core network; the PDN data service connection rejection message includes a PDN data service connection rejection reason value;

[0042] The processing unit is configured to, when the PDN data service connection rejection reason value is that multiple PDN connections of a given APN are not allowed, check whether the user plane resources of the PDN are released, and if it is determined that the APN used for the PDN activation is not used, actively trigger the TAU process;

[0043] The transmitter unit is configured to send a TAU request message to the 4G core network, wherein the TAU request message includes the EPS bearer state of the PDN, so that the 4G core network synchronizes the EPS bearer state of the PDN, thereby causing the access network to issue a message for releasing user plane resources of the PDN;

[0044] The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the PDN, and a TAU acceptance message from the 4G core network, wherein the TAU acceptance message includes an EPS bearer status of the PDN after the user plane resources of the PDN are released;

[0045] The processing unit is further configured to release the user plane resources of the PDN based on a message for releasing the user plane resources of the PDN;

[0046] The transmitter unit is also used to send a TAU completion message to the 4G core network and reuse the APN to initiate a PDN activation request.

[0047] In one implementation, it further includes:

[0048] The receiver unit is used to receive a PDU session establishment rejection message sent by the 5G core network; the PDU session establishment rejection message includes a PDU session establishment rejection reason value;

[0049] The processing unit is configured to check the number of PDU sessions locally when the PDU session establishment rejection reason value is that the maximum number of PDU sessions has been reached, and if it is determined that the number of current PDU sessions has not reached the maximum number of PDU sessions, actively trigger the mobility registration process;

[0050] The transmitter unit is configured to send a mobility registration request message to the 5G core network, wherein the mobility registration request message includes the state of the PDU session, so that the 5G core network synchronizes the state of the PDU session, thereby causing the access network to issue a message for releasing user plane resources of the PDU session;

[0051] The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the PDU session, and a mobility registration acceptance message from the 5G core network, wherein the mobility registration acceptance message includes a state of the PDU session after the user plane resources of the PDU session are released;

[0052] The processing unit is further configured to release the user plane resources of the PDU session based on a message for releasing the user plane resources of the PDU session;

[0053] The transmitter unit is also used to send a mobility registration completion message to the 5G core network.

[0054] In a second aspect, the present application further provides a method for synchronizing a data service context state, applying the user equipment for synchronizing a data service context state, including:

[0055] When the user equipment receives the rejection message sent by the core network, the user equipment checks locally whether the user plane resources of the data unit are released or whether there are duplicate data units locally or whether the existing data units have reached the upper limit. If it is determined that the access network has not released the user plane resources of the data unit or there are no duplicate data units or the existing data units have not reached the upper limit, the synchronous data service context state process is actively triggered;

[0056] Sending a synchronization data service context state message to the core network through the user equipment, so that the core network synchronizes the data service context state, and then the access network sends a message to release the user plane resources of the data unit;

[0057] The user equipment is used to receive a message for releasing the user plane resources of the data unit sent by the access network, and the user plane resources of the data unit are released based on the message for releasing the user plane resources of the data unit.

[0058] This application determines whether it is necessary to synchronize data services with the network side based on the internally stored parameter information. If necessary, the TAU process is used in 4G, or the mobile registration process is used in 5G to carry the data service context state of the UE side and synchronize the data service context state with the network side. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The preferred implementation scheme will be described below in a clear and understandable manner with reference to the accompanying drawings to further illustrate the above-mentioned characteristics, technical features, advantages and implementation methods of the present application.

[0060] Figure 1 It is a working framework diagram of a user equipment for data service context state synchronization in this application;

[0061] Figure 2 It is a schematic diagram of synchronizing the PDN state with the network after the PDN deactivation in this application is rejected;

[0062] Figure 3 It is a schematic diagram of synchronizing the PDU session state with the network after the PDU session deactivation in this application is rejected;

[0063] Figure 4 It is a schematic diagram of synchronizing the PDN state with the network after the PDN activation in this application is rejected;

[0064] Figure 5 It is a schematic diagram of synchronizing the PDU session state with the network after the PDU session establishment in this application is rejected. DETAILED DESCRIPTION

[0065] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0066] It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections.

[0067] In order to simplify the drawings, only the parts related to the present invention are schematically shown in each figure, and they do not represent the actual structure of the product. In addition, in order to simplify the drawings and facilitate understanding, in some figures, only one of the parts with the same structure or function is schematically drawn or marked. In this article, "one" not only means "only one", but also means "more than one".

[0068] It should be further understood that the term “and / or” used in the specification and appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0069] In addition, in the description of the present application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0070] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings and other implementation methods can be obtained based on these drawings without creative work.

[0071] Unless otherwise defined, all technical and scientific terms used in the embodiments of the present application have the same meanings as those commonly understood by those skilled in the art. The terms used in the embodiments of the present application are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0072] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0073] 3GPP's 24.301 protocol is a specification document for the non-access stratum (NAS) protocol of the evolved Packet System (EPS) used by the core network and terminals of the technical specification group. It defines the interface and protocol for controlling the connection and communication of radio resources and mobile terminals in the LTE (Long Term Evolution) network. The specification covers many aspects, including mobility management, service management, bearer management, handshake and identity authentication. It describes in detail the communication process and message format between network elements, and specifies the exchange process of control information.

[0074] LTE (Long Term Evolution) is the long-term evolution of the UMTS (Universal Mobile Telecommunications System) technical standard developed by 3GPP (The 3rd Generaion ParnershipProiec, Third Generation Partnership Project) organization.

[0075] User equipment: In 3G / 4G standards such as LTE, the terminal is called UE (User Equipment). User equipment can be a mobile phone, tablet computer, laptop or other device.

[0076] PDN Connection is the logical data path between UE and PDN, which we call EPS end-to-end service tunnel (End-to-End Service), and EPS Bearer is a smaller tunnel contained in PDN Connection. Because UE can create multiple PDN Connections and have multiple EPS Bearers, these Bearers need to be identified by EBI (EPS Bearer Identity). EBI is assigned to EPS Bearer by MME, based on UE, and is used to distinguish multiple EPS Bearers in the same UE. EBI between different UEs can be repeated.

[0077] PDU session (Protocol Data Unit session) refers to the communication path established between the user terminal (UE) and the data network (DN) in the 5G network.

[0078] In the 4G core network, EPS Bearer is the minimum granularity for distinguishing QoS; in the 5G core network, QoS Flow is the minimum granularity for distinguishing QoS. 5G PDU Session (similar to PDN Connection in 4G) replaces EPSSession in 4G. One Session can establish multiple QoS Flows, and each Session requires a user plane tunnel established by a UE, gNB, and UPF for the Session.

[0079] TAU (Tracking Area Update) is a process performed by a mobile device to maintain network connection and update its location information when entering a new tracking area.

[0080] Among them, the 4G core network is EPC and the access network is eNodeB.

[0081] eNodeB (Evolved Node B), or eNB for short. Compared with the existing Node B in 3G, eNodeB integrates some RNC functions and reduces the protocol layers during communication. eNodeB is a wireless base station in the LTE network and a network element of the LTE wireless access network. It is responsible for all functions related to the air interface: (1) wireless link maintenance function, maintaining the wireless link with the terminal, and responsible for the protocol conversion between wireless link data and IP data; (2) wireless resource management function, including the establishment and release of wireless links, scheduling and allocation of wireless resources, etc.; (3) some mobility management functions, including configuring terminals for measurement, evaluating the quality of terminal wireless links, and deciding on terminal switching between cells. 2G / 3G base stations are only responsible for connecting to the wireless link with the terminal, while the specific maintenance of the link (wireless resource management, mobility management without passing through the core network, etc.) is completed by the upper-level management entity of the base station (BSC in 2G and RNC in 3G). In addition, the bridge function between the wireless access network and the core network is also implemented in BSC or RNC.

[0082] Evolved Packet Core (EPC) is a packet core network that supports multiple access methods including 3GPP and non-3GPP (such as Wi-Fi, WiMAX, etc.), and is a converged architecture that supports heterogeneous networks.

[0083] 5GC (5G core, 5G core network), the corresponding access network is (R)AN.

[0084] Public Land Mobile Network (PLMN) is a network established and operated by the government or an operator approved by it to provide land mobile communication services to the public. This network is usually interconnected with the public switched telephone network (PSTN) to form a communication network on a regional or national scale.

[0085] According to the current 3GPP protocol, after the UE receives the rejection message, the UE should immediately release the PDN or PDU session to be deactivated locally, and there is no need to synchronize the data service status with the network side. However, this will cause the data service context of the UE and the network side to be inconsistent, resulting in a waste of user plane resources, or causing subsequent PDN activation requests to be rejected, or PDU session establishment to be rejected.

[0086] Based on the above analysis of related technologies, it can be seen that the embodiment of the present application is important for data service context synchronization. Therefore, after the UE is rejected for PDN deactivation or the release of the PDU session is rejected, the present application determines whether it is necessary to synchronize data services with the network side according to the internally stored parameter information. If necessary, the TAU process is used in the 4G core network, or the mobile registration process is used in the 5G core network to carry the data service context state of the UE side and synchronize the data service context state with the network side.

[0087] The present application provides a method for synchronizing a data service context state, and applies the user equipment 100 for synchronizing a data service context state, including:

[0088] After the user equipment 100 receives the rejection message sent by the core network 200, the user equipment 100 locally checks whether the user plane resources of the data unit are released or checks whether there are duplicate data units locally or whether the existing data units have reached the upper limit. If it is determined that the access network has not released the user plane resources of the data unit or there are no duplicate data units or the existing data units have not reached the upper limit, the synchronization data service context state process is actively triggered; the user equipment 100 sends a synchronization data service context state message to the core network 200, so that the core network 200 synchronizes the data service context state, and then the access network 300 sends a message to release the user plane resources of the data unit; the user equipment 100 receives the message of releasing the user plane resources of the data unit sent by the access network 300, and based on the message of releasing the user plane resources of the data unit, the user plane resources of the data unit are released.

[0089] Reference Figure 1As shown, the present application provides a user equipment 100 for synchronizing a data service context state, including:

[0090] The receiver unit 101 is configured to receive a rejection message sent by the core network 200 .

[0091] Processing unit 102 is used to locally check whether the user plane resources of the data unit are released or check whether there are duplicate data units locally or whether the existing data units have reached an upper limit. If it is determined that the access network has not released the user plane resources of the data unit or there are no duplicate data units or the existing data units have not reached the upper limit, the synchronous data service context state process is actively triggered.

[0092] The transmitter unit 103 is used to send a synchronization data service context state message to the core network 200, so that the core network 200 synchronizes the data service context state, and then the access network 300 sends a message to release the user plane resources of the data unit.

[0093] The receiver unit 101 is further configured to receive a message sent by the access network 300 to release user plane resources of the data unit.

[0094] The processing unit 102 is further configured to release the user plane resources of the data unit based on a message for releasing the user plane resources of the data unit.

[0095] In the present application, in order to avoid the rejection of PDN deactivation caused by abnormalities on the network side, or the rejection of PDU session release by the network, after the UE locally releases the PDN / PDU session, it is inconsistent with the data service context on the network side, resulting in a series of problems such as waste of user plane resources, rejection of subsequent PDN activation requests, and rejection of PDU session establishment. It is proposed to screen the user plane resources and synchronize the data service context status to the network side, so as to release the unused user plane resources through the network side through the user equipment 100, thereby avoiding waste of user plane resources.

[0096] In one implementation, the core network 200 includes a 4G core network and a 5G core network.

[0097] When the core network 200 is a 4G core network, the data unit is a PDN; when the core network 200 is a 5G core network, the data unit is a PDU session.

[0098] In addition, when the core network 200 is a 4G core network, the rejection message is a PDN rejection message; when the core network 200 is a 5G core network, the rejection message is a PDU session rejection message.

[0099] In the 24.301 protocol of 3GPP, after the user equipment 100 receives the PDN disconnection rejection message, it should immediately release the PDN to be deactivated locally, and will not synchronize the PDN status with the network side. This will cause the data service context status of the user equipment 100 and the network side to be out of sync, resulting in problems such as waste of user plane resources.

[0100] After the network side receives the UE's active PDN deactivation request, in some scenarios, if the network side does not accept the UE's PDN deactivation request, it will use the PDN DISCONNECT REJECT message to reject the UE's request, and carry reason values ​​such as #35 "PTI has been used", or #43 "Invalid EPS bearer identifier", or #49 "The last PDN link cannot be deactivated", or #95-111 "Protocol error". According to the current protocol, after the UE receives the PDN DISCONNECT REJECT message, it should immediately release the PDN to be deactivated locally, and there is no need to synchronize the PDN status with the network. This will cause many problems in actual use.

[0101] In order to solve the problems that may exist during actual use, this application provides a variety of solutions. Solution 1: When the UE is registered in the 4G network, when the UE receives the PDN DISCONNECT REJECT message, the UE first deactivates the PDN locally, but the user plane resources corresponding to the EPS bearer contained in the PDN still exist. In this case, a TAU request can be actively triggered to synchronize the EPS bearer status with the network.

[0102] Wherein, the rejection message includes a deactivation rejection message. When the rejection message is a deactivation rejection message, the receiver unit 101 is used to receive the deactivation rejection message sent by the core network 200. The processing unit 102 is used to locally deactivate the data unit, check whether the user plane resources of the data are released, and actively trigger the synchronization data service context state process if it is determined that the access network 300 has not released the user plane resources of the data unit. The transmitter unit 103 is used to send a synchronization data service context state request message to the core network 200, and the synchronization data service context state request message includes the data service context state of the data unit, so that the core network 200 synchronizes the data service context state of the data unit, and then the access network 300 sends a message to release the user plane resources of the data unit. The receiver unit 101 is also used to receive a message to release the user plane resources of the data unit sent by the access network 300, and a synchronization data service context state acceptance message sent by the core network 200, and the synchronization data service context state acceptance message includes the data service context state of the data unit after the user plane resources of the data unit are released. The processing unit 102 is further configured to release the user plane resource of the data unit based on the message for releasing the user plane resource of the data unit. The transmitter unit 103 is further configured to send a data unit synchronization completion message to the core network 200 .

[0103] The following problem scenarios may occur during actual use: Problem 1: The UE establishes two PDNs, but when the UE deactivates one of the PDNs, due to an abnormality on the network side, the network uses #49 "The last PDN link cannot be deactivated" to reject the user's PDN deactivation request. Since the network will not reallocate user plane resources at this time, the network will not release user plane resources, resulting in waste of user plane resources and asynchronous data service status.

[0104] For problem 1, this application provides a specific solution. When the UE is registered in the 4G network, when the UE receives the PDNDISCONNECT REJECT message, the UE first deactivates the PDN locally according to the protocol, and then checks the locally stored user plane configuration information. If it is found that the user plane resources corresponding to the EPS bearer contained in the PDN still exist, it can actively trigger a TAU request, and send only other activated EPS bearers in the EPS bearer context status IE to the network side to synchronize the EPS bearer status with the network.

[0105] Reference Figure 2As shown, the specific process is as follows: in the 4G network, when the UE no longer uses a certain PDN, it actively sends a PDNdisconnect request message to the network side; if the current network does not accept the UE's PDN deactivation request, it will send a PDNdisconnect reject message, carrying a reason value (including #35, #43, #49 or #95-111, etc.); after receiving the PDN disconnect reject message, the UE first locally deactivates the PDN, and then checks the user plane information. If the network has not released the user plane resources corresponding to the PDN at this time, it actively triggers the TAU process; in the TAU request message sent by the UE, the EPS bearer context status IE contains only other activated EPS bearers; after receiving the TAUrequest message, the 4G core network synchronizes the EPS bearer context status, and then may notify the access network to release the user plane resources, and the access network notifies the UE to release the user plane resources corresponding to the PDN; the network side replies to the UE with a TAU Accept message, carrying the EPSbearercontextstatusIE containing other activated EPS bearers, and synchronizes the EPS bearer status with the UE; after receiving the TAU Accept message, the UE replies to the network side with a TAU Complete message.

[0106] In this implementation, in the 4G core network, the deactivation rejection message includes a PDN disconnection rejection message, and the receiver unit 101 is used to receive the PDN disconnection rejection message sent by the 4G core network; the processing unit 102 is used to locally deactivate the PDN, check whether the user plane resources of the PDN are released, and actively trigger the TAU process if it is determined that the access network 300 has not released the user plane resources of the PDN; the transmitter unit 103 is used to send a TAU request message to the 4G core network, and the TAU request message includes the EPS bearer status of the PDN, so that the 4G core network synchronizes the EPS bearer status of the PDN, and then the access network 300 sends a message to release the user plane resources of the PDN; the receiver unit 101 is also used to receive a message sent by the access network 300 to release the user plane resources of the PDN, and a TAU acceptance message sent by the 4G core network, and the TAU acceptance message includes the EPS of the PDN after the user plane resources of the PDN are released. bearer state; the processing unit 102 is also used to release the user plane resources of the PDN based on the message of releasing the user plane resources of the PDN; the transmitter unit 103 is also used to send a TAU completion message to the 4G core network.

[0107] When the UE is registered in the 4G network, during the previous PDN deactivation, if the UE is rejected by the network, the UE only releases the PDN locally, and does not synchronize the data service context status with the network. When the UE receives the PDN connectivity reject message, if it carries the reason value #55 "Multiple PDN connections for agiven APN not allowed", and then checks other local PDNs, if no other PDNs are found to use the APN used for this PDN activation, it can actively trigger a TAU request, and only include other activated EPS bearers in the EPS bearer context status IE, and synchronize the EPS bearer status with the network. After the UE receives the TAU accept message, it re-initiates the PDN connectivity request message.

[0108] Similar problem scenarios also exist in the 24.501 protocol. After the network side receives the UE's active request to release the PDU session, in some scenarios, if the network side does not accept the UE's PDU session release request, it will use the PDUSESSION RELEASE REJECT message (PDU session release reject message) to reject the UE's request, and carry reason values ​​such as #35 "PTI has been used", or #43 "Invalid PDU session identifier", or #95-111 "Protocol error". According to the current protocol, after the UE receives the PDU SESSION RELEASE REJECT message, it should immediately release the PDUsession locally, and there is no need to synchronize the PDU session status with the network, but this may cause the UE to be out of sync with the network side PDUsession status. For example, there are the following problem scenarios:

[0109] Question 3: When the UE releases one of the PDU sessions, due to an unknown abnormality of the network-side device, the network uses #111 "reason value not defined by the protocol" to reject the user's PDU session release request. Since the network will not reallocate user plane resources at this time, the network will not release user plane resources, resulting in waste of user plane resources and asynchronous data service status.

[0110] For question 3, this application provides a specific solution. When the UE is registered in the 5G network, when the UE receives the PDUSESSION RELEASE REJECT message, the UE first deactivates the PDU session locally according to the protocol, and then checks the locally stored user plane configuration information. If it is found that the user plane resources corresponding to the QoS flow included in the PDU session still exist, it can actively trigger a mobility registration request, and only include other activated PDU sessions in the PDU sessionstatus IE to synchronize the PDU session status with the network.

[0111] Solution 2: When the UE is registered in the 5G network, after receiving the PDU SESSION RELEASE REJECT message, the UE first locally deactivates the PDU session. However, if the user plane resources corresponding to the QoS flows contained in the PDU session still exist, the UE can actively trigger a mobility registration request to synchronize the PDU session status with the network. Figure 3As shown, the specific process is as follows: Under the 5G network, when the UE no longer uses a certain PDU session, it actively sends a PDUsession release request message to the network side; if the current network does not accept the UE's PDU session release request, it will send a PDU session release reject message, and carry a reason value (including #35, #43 or #95-111, etc.); After receiving the PDU session release reject message, the UE first releases the PDU session locally, and then checks the user plane information. If the network has not released the user plane resources corresponding to the PDU at this time, it actively triggers the mobility registration process; In the Registration request message sent by the UE, the PDU session status IE contains only other activated PDU sessions; After receiving the Registration request message, the 5G core network synchronizes the PDU session status, and then may notify the access network 300 to release the user plane resources. The access network 300 notifies the UE to release the user plane resources corresponding to the PDU session; The network side replies to the UE with a Registration Accept message, carrying the PDU session status IE containing other activated PDU sessions, and synchronizes the PDU session status with the UE; The UE receives the Registration After receiving the Accept message, the network side will reply with a Registration Complete message.

[0112] Among them, in the 5G core network, the deactivation rejection message is a PDU session release rejection message, and the receiver unit 101 is used to receive the PDU session release rejection message sent by the 5G core network; the processing unit 102 is used to locally deactivate the PDU, check whether the user plane resources of the PDU session are released, and if it is determined that the access network 300 has not released the user plane resources of the PDU session, actively trigger the mobility registration process; the transmitter unit 103 is used to send a mobility registration request message to the 5G core network, and the mobility registration request message includes the status of the PDU session, so that the 5G core network synchronizes the PDU session status, thereby causing the access network 300 to issue a message for releasing the user plane resources of the PDU session; the receiver unit 101 is also used to receive the message for releasing the user plane resources of the PDU session issued by the access network 300, and the mobility registration acceptance message sent by the 5G core network, the mobility registration acceptance message including the status of the PDU session after the user plane resources of the PDU session are released; the processing unit 102 is also used to release the user plane resources of the PDU session based on the message for releasing the user plane resources of the PDU session; the transmitter unit 103 is also used to send a mobility registration completion message to the 5G core network.

[0113] In this implementation, by checking the locally stored user plane configuration information, if it is found that the user plane resources corresponding to the QoS flow contained in the PDU session still exist, the mobility registration request can be actively triggered, and a message containing only other activated PDU sessions in the PDUsession status IE is sent to the network side, and the PDU session status is synchronized with the network side to avoid waste of user plane resources.

[0114] In one implementation, the rejection message includes an activation rejection message. When the rejection message is an activation rejection message, the receiver unit 101 is used to receive the activation rejection message sent by the core network 200. The activation rejection message includes a data service connection rejection message or an establishment rejection message. The processing unit 102 is used to actively trigger the synchronization data service context state process based on the activation rejection reason value and the data service context state of the data unit; the transmitter unit 103 is used to send a synchronization data service context state request message to the core network 200, the synchronization data service context state request message includes the data service context state of the data unit, so that the core network 200 synchronizes the data service context state of the data unit, and then the access network 300 sends a message to release the user plane resources of the data unit; the receiver unit 101 is also used to receive the message of releasing the user plane resources of the data unit sent by the access network 300, and the synchronization data service context state acceptance message sent by the core network 200, the synchronization data service context state acceptance message includes the data service context state of the data unit after releasing the user plane resources of the data unit; the processing unit 102 is also used to release the user plane resources of the data based on the message of releasing the user plane resources of the data unit; the transmitter unit 103 is also used to send a synchronization data service context state completion message to the core network 200, and re-initiate the activation request.

[0115] In the actual use of the 4G core network, the following problems may exist: Problem 2: Due to an abnormality on the network side, the PDN deactivation initiated by the UE last time was rejected by the network. If the network uses the reason value #35 "PTI is already in use", the UE locally deactivates the PDN according to the protocol, but the network side does not release the PDN, resulting in the UE subsequently using the APN in the deactivated PDN to initiate a new PDN activation request to the network. Since many operators currently do not support the use of the same APN to activate multiple PDNs, the activation request for this PDN will be rejected by the network, resulting in the UE being unable to use the data service corresponding to this APN.

[0116] For problem 2, this application provides a specific solution, please refer to the attached Figure 4As shown in scheme three, when the UE is registered in the 4G network, if the UE is rejected by the network during the previous PDN deactivation, the UE only releases the PDN locally and does not synchronize the data service context status with the network. When the UE receives the PDN connectivity reject message, if it carries the reason value #55 "Multiple PDN connections for a given APN not allowed", it checks other local PDNs. If no other PDNs are found to use the APN used for this PDN activation, it can actively trigger a TAU request and include only other activated EPS bearers in the EPS bearer context status IE to synchronize the EPS bearer status with the network. After the UE receives the TAU accept message, it re-initiates the PDN connectivity request message. Refer to the attached Figure 4 As shown in the figure, the specific process is as follows: in the 4G network, when the UE needs to use a certain APN for data services, it sends a PDN Connectivity request message to the network side; if the current network does not accept the UE's PDN activation request, it will send a PDN Connectivity reject message with a reason value; after receiving the PDN Connectivity reject message, if it carries the ESM reason value #55 "Multiple PDN connections for a given APN not allowed" reason value, then the UE checks other local PDNs. If no other PDNs are found to use the APN used for this PDN activation, the TAU process is actively triggered; in the TAU request message sent by the UE, the EPS bearercontext status IE carried contains only other activated EPS bearers; after receiving the TAU request message, the 4G core network synchronizes the EPS bearer context status, and then may notify the access network to release the user plane resources, and the access network notifies the UE to release the user plane resources corresponding to the PDN; the network side replies to the UE with a TAU Accept message, carrying the EPS bearer contextstatus IE containing other activated EPS bearers, and synchronizes the EPS bearer status with the UE; the UE receives the TAU After receiving the Accept message, the network side replies with a TAU Complete message, and then the UE uses the APN to re-initiate the PDN activation request.

[0117] Among them, in the 4G core network, the activation rejection message is a PDN data service connection rejection message, and the receiver unit 101 is used to receive the PDN data service connection rejection message sent by the 4G core network; the PDN data service connection rejection message includes a PDN data service connection rejection reason value; the processing unit 102 is used to check whether the user plane resources of the PDN are released when the PDN data service connection rejection reason value is that multiple PDN connections for a given APN are not allowed, and if it is determined that the APN used for the PDN activation is not used, actively trigger the TAU process; the transmitter unit 103 is used to send a TAU request message to the 4G core network, and the TAU request message includes the EPS bearer status of the PDN, so that the 4G core network synchronizes the EPS of the PDN bearer state, thereby causing the access network 300 to send a message for releasing the user plane resources of the PDN; the receiver unit 101 is also used to receive the message for releasing the user plane resources of the PDN sent by the access network 300, and the TAU acceptance message sent by the 4G core network, the TAU acceptance message including the EPS bearer state of the PDN after the user plane resources of the PDN are released; the processing unit 102 is also used to release the user plane resources of the PDN based on the message for releasing the user plane resources of the PDN; the transmitter unit 103 is also used to send a TAU completion message to the 4G core network, and reuse the APN to initiate a PDN activation request.

[0118] In this implementation, the PDN data service connection rejection reason value is analyzed by the user equipment 100, and the release of the user plane resources is further checked, and the TAU process is actively triggered to synchronize the data service context status of the 4G core network and the user equipment 100.

[0119] The following problem scenarios also exist in the 24.501 protocol: Problem 4: The total number of PDU sessions previously established by the UE has reached the maximum number allowed under the PLMN. Due to an abnormality on the network side, the PDUsession release request previously initiated by the UE was rejected by the network. According to the protocol, the UE released the PDU session locally. However, the network side did not release the PDU session, resulting in the UE initiating a new PDU session establishment request to the network. Since the network limits the maximum number of PDU sessions that can be established under this PLMN, this PDU session establishment request will be rejected by the network with the 5GMM reason value #65 "the maximum number of PDU sessions has been reached", resulting in the UE being unable to use the corresponding data service.

[0120] In view of the problems existing in the above practical scenarios, this application provides a specific solution. Solution 4: After receiving the PDU session establishment reject message, the UE checks the number of currently activated PDU sessions. If it has not reached the previous maximum value; or there is no activated PDU session, it can actively trigger a mobility registration request, and only include other activated PDU sessions in the PDU session status IE, and synchronize the PDU session status with the network. After the UE receives the Registration accept message, it re-initiates the PDU session establishment request.

[0121] Reference Figure 5 As shown, the specific process is as follows: Under the 5G network, when the UE needs to use data services, it sends a PDUsession establishment request message to the network side; if the network side limits the maximum number of PDU sessions that can be established under the PLMN, the current network does not accept the UE's PDU session establishment request, and sends a PDUsession establishment reject message, carrying the 5GMM reason value #65; After receiving the PDUsession establishment reject message, if the UE carries 5GMM's #65 "the maximum number of PDU sessions has been reached", it checks the number of currently activated PDU sessions. If it has not reached the previous maximum value; or there is no activated PDUsession, it actively triggers the mobility registration process; In the Registration request message sent by the UE, the PDUsession status IE is carried, which only contains other activated PDU sessions; After receiving the Registration request message, the 5G core network synchronizes the PDU session status, and then may notify the access network 300 to release the user plane resources. The access network 300 notifies the UE to release the user plane resources corresponding to the PDU session; The network side replies to the UE with a Registration Accept message, carrying the PDU session status The IE contains other PDU sessions in the same active state as the UE, and synchronizes the data service context state with the UE; after receiving the Registration Accept message, the UE replies with a Registration Complete message to the network side; the UE re-initiates the PDU session establishment process.

[0122] Specifically, when the core network 200 is a 5G core network and the rejection message is a PDU session establishment rejection message, the receiver unit 101 is used to receive the PDU session establishment rejection message sent by the 5G core network; the PDU session establishment rejection message includes a PDU session establishment rejection reason value; the processing unit 102 is used to check the number of PDU sessions locally when the PDU session establishment rejection reason value is the maximum number of PDU sessions reached, and if it is determined that the current number of PDU sessions has not reached the maximum number of PDU sessions, the mobility registration process is actively triggered; the transmitter unit 103 is used to send a mobility registration request message to the 5G core network, and the mobility registration request message includes the PDU session status, so that the 5G core network synchronizes the status of the PDU session, and then the access network 300 sends a message to release the user plane resources of the PDU session; the receiver unit 101 is also used to receive the message of releasing the user plane resources of the PDU session sent by the access network 300, and the mobility registration acceptance message sent by the 5G core network, the mobility registration acceptance message including the status of the PDU session after releasing the user plane resources of the PDU session; the processing unit 102 is also used to release the user plane resources of the PDU session based on the message of releasing the user plane resources of the PDU session; the transmitter unit 103 is also used to send a mobility registration completion message to the 5G core network.

[0123] In this implementation, by analyzing the reason value, checking the user plane resource status, and actively triggering the mobility registration process, the network side and the user equipment 100 synchronize the data service context status, thereby avoiding the problem that the network will not release user plane resources due to the network not reallocating user plane resources, resulting in user plane resource waste and data service status asynchrony.

[0124] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned program modules is used as an example for illustration. In actual applications, the above-mentioned functions can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program units or modules to complete all or part of the functions described above. In addition, the specific names of the program modules are only for the convenience of distinguishing each other and are not used to limit the scope of protection of this application.

[0125] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0126] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed with hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0127] It should be noted that the above embodiments can be freely combined as needed. The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered as the protection scope of the present invention.

Claims

1. A user equipment for data service context state synchronization, characterized in that: include: A receiver unit, configured to receive an activation rejection message sent by a core network; The activation rejection message includes a data service connection rejection message or an establishment rejection message; A processing unit, configured to check whether there are duplicate data units locally when a PDN data service connection rejection message is received, and determine that there are no duplicate data units when the PDN data service connection rejection reason value is that multiple PDN connections for a given APN are not allowed; or, when the activation rejection message includes a PDU session establishment rejection message, check whether the existing data units have reached an upper limit, and when the PDU session establishment rejection reason value is that the maximum number of PDU sessions has been reached, check the number of PDU sessions locally, and if it is determined that the number of current PDU sessions has not reached the maximum number of PDU sessions, determine that the existing data units have not reached the upper limit; The processing unit is further configured to actively trigger a synchronous data service context state process if it is determined that no duplicate data units exist in the access network or the existing data units do not reach an upper limit; A transmitter unit, configured to send a synchronization data service context state message to the core network, so that the core network synchronizes the data service context state, thereby causing the access network to issue a message for releasing user plane resources of the data unit; The receiver unit is further configured to receive a message sent by the access network to release user plane resources of the data unit; The processing unit is further configured to release the user plane resources of the data unit based on a message for releasing the user plane resources of the data unit.

2. A user equipment for data service context state synchronization according to claim 1, characterized in that: The core network includes a 4G core network and a 5G core network.

3. A user equipment for data service context state synchronization according to claim 2, characterized in that: When the core network is a 4G core network, the data unit is a PDN; when the core network is a 5G core network, the data unit is a PDU session.

4. The user equipment for data service context state synchronization according to claim 3, characterized in that: Also includes: The receiver unit is configured to receive an activation rejection message sent by the core network; The processing unit is used to actively trigger a synchronization data service context state process based on the activation rejection reason value and the data service context state of the data unit; The transmitter unit is used to send a synchronization data service context state request message to the core network, wherein the synchronization data service context state request message includes the data service context state of the data unit, so that the core network synchronizes the data service context state of the data unit, and then the access network sends a message to release the user plane resources of the data unit; The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the data unit, and a synchronous data service context state acceptance message from the core network, wherein the synchronous data service context state acceptance message includes a data service context state of the data unit after the user plane resources of the data unit are released; The processing unit is further configured to release the user plane resources of the data unit based on a message for releasing the user plane resources of the data unit; The transmitter unit is further configured to send a synchronous data service context status completion message to the core network and re-initiate an activation request.

5. The user equipment for data service context state synchronization according to claim 4, characterized in that: Also includes: The receiver unit is used to receive a PDN data service connection rejection message sent by the 4G core network; The PDN data service connection rejection message includes a PDN data service connection rejection cause value; The processing unit is configured to, when the PDN data service connection rejection reason value is that multiple PDN connections of a given APN are not allowed, check whether the user plane resources of the PDN are released, and if it is determined that the APN used for the PDN activation is not used, actively trigger the TAU process; The transmitter unit is configured to send a TAU request message to the 4G core network, wherein the TAU request message includes the EPS bearer state of the PDN, so that the 4G core network synchronizes the EPS bearer state of the PDN, thereby causing the access network to issue a message for releasing user plane resources of the PDN; The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the PDN, and a TAU acceptance message from the 4G core network, wherein the TAU acceptance message includes an EPS bearer status of the PDN after the user plane resources of the PDN are released; The processing unit is further configured to release the user plane resources of the PDN based on a message for releasing the user plane resources of the PDN; The transmitter unit is also used to send a TAU completion message to the 4G core network and reuse the APN to initiate a PDN activation request.

6. The user equipment for data service context state synchronization according to claim 4, characterized in that: Also includes: The receiver unit is used to receive a PDU session establishment activation rejection message sent by the 5G core network; The PDU session establishment rejection message includes a PDU session establishment rejection cause value; The processing unit is configured to check the number of PDU sessions locally when the PDU session establishment rejection reason value is that the maximum number of PDU sessions has been reached, and if it is determined that the number of current PDU sessions has not reached the maximum number of PDU sessions, actively trigger the mobility registration process; The transmitter unit is configured to send a mobility registration request message to the 5G core network, wherein the mobility registration request message includes the state of the PDU session, so that the 5G core network synchronizes the state of the PDU session, thereby causing the access network to issue a message for releasing user plane resources of the PDU session; The receiver unit is further configured to receive a message from the access network for releasing user plane resources of the PDU session, and a mobility registration acceptance message from the 5G core network, wherein the mobility registration acceptance message includes a state of the PDU session after the user plane resources of the PDU session are released; The processing unit is further configured to release the user plane resources of the PDU session based on a message for releasing the user plane resources of the PDU session; The transmitter unit is also used to send a mobility registration completion message to the 5G core network.

7. A method for synchronizing data service context state, characterized in that: The user equipment for data service context state synchronization according to any one of claims 1 to 6 is applied, wherein the activation rejection message includes a data service connection rejection message or an establishment rejection message; comprising: Receiving, through the user equipment, an activation rejection message sent by the core network; When a PDN data service connection rejection message is received, the user equipment is used to check whether there are duplicate data units locally, and when the PDN data service connection rejection reason value is that multiple PDN connections for a given APN are not allowed, it is determined that there are no duplicate data units; or, when the activation rejection message includes a PDU session establishment rejection message, it is checked whether the existing data units have reached the upper limit, and when the PDU session establishment rejection reason value is the maximum number of PDU sessions reached, the number of PDU sessions is checked locally, and if it is determined that the number of current PDU sessions has not reached the maximum number of PDU sessions, it is determined that the existing data units have not reached the upper limit; if it is determined that there are no duplicate data units in the access network or the existing data units have not reached the upper limit, the synchronous data service context state process is actively triggered; Sending a synchronization data service context state message to the core network through the user equipment, so that the core network synchronizes the data service context state, and then the access network sends a message to release the user plane resources of the data unit; The user equipment is used to receive a message for releasing the user plane resources of the data unit sent by the access network, and the user plane resources of the data unit are released based on the message for releasing the user plane resources of the data unit.

Images