Method, device, core network element and storage medium for restoring bearer
The core network element receives and processes the initial messages of the UE, determines the connection status and session type of the UE, and executes the bearer recovery process, solving the problem of downlink service interruption caused by wireless link exceptions, ensuring the continuity of data transmission.
Patent Information
- Application Number
- CN202110315006.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-03-24
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2041-03-24
AI Technical Summary
In the case of abnormal release of wireless links or automatic link breakage of NAS layer, when the UE re-initiates the registration process, the user-plane link between the UE and the core network may not be restored, resulting in downlink service interruption and data loss.
The core network element receives the initial UE message sent by the base station and determines the UE context according to the NAS message. If the UE's connection state is an abnormal access state, the UE context release process is initiated; when the NAS message indicates that the UE's session type is not the first type When performing a bearer recovery process to ensure the recovery of the bearer between the UE and the core network.
It effectively solves the problem of downlink service interruption caused by the unrecovered bearer during network abnormalities, ensures that the uplink service between the UE and the base station can be restored in time, and avoids data loss.
Smart Images

Figure CN115134948B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a method, device, core network element and storage medium for restoring a bearer. Background Art
[0002] In the event of network anomalies such as abnormal release of the radio link or automatic disconnection of the NAS layer, the UE will re-initiate the registration process to restore the radio link.
[0003] However, during the above-mentioned wireless link recovery process, there may be a situation where only the signaling plane link between the UE and the core network is restored, but the user plane link between the UE and the core network is not restored. Correspondingly, the bearer is not restored. If there is a downlink service at this time, it will cause the downlink service to be interrupted, resulting in partial data loss, and ultimately leading to poor user perception. Summary of the invention
[0004] The embodiments of the present application provide a method, device, core network element and storage medium for restoring a bearer, which can solve the problem of downlink service interruption due to failure to restore the bearer when a network abnormality exists in the related art. The technical solution is as follows:
[0005] According to one aspect of an embodiment of the present application, a method for restoring a bearer is performed by a core network network element, the method comprising: receiving an initial user equipment UE message sent by a base station, and determining a UE context based on a non-access layer NAS message in the initial UE message; if the UE context indicates that the UE's connection state is an abnormal access state, initiating a UE context release process to the base station; when the NAS message indicates that the UE's session type is not a first type, executing a bearer recovery process, the first type being used to indicate that the UE does not have an uplink service in a requested state and no bearer is established between the UE and the core network.
[0006] According to one aspect of an embodiment of the present application, a core network network element includes: a memory, a transceiver, and a processor; wherein the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following steps: receiving an initial user equipment UE message sent by a base station, and determining the UE context according to a non-access layer NAS message in the initial UE message; if the UE context indicates that the UE's connection state is an abnormal access state, initiating a UE context release process to the base station; when the NAS message indicates that the UE's session type is not a first type, executing a bearer recovery process, the first type is used to indicate that the UE does not have an uplink service in a requested state and no bearer is established between the UE and the core network.
[0007] In a possible implementation manner, the NAS message includes a registration message.
[0008] In a possible implementation manner, the processor is further configured to perform the following steps: extracting a registration message from an initial UE message; if the registration message indicates that the UE is an initial registration, creating a UE context; otherwise, obtaining the UE context.
[0009] In a possible implementation manner, the NAS message includes a service request message.
[0010] In a possible implementation manner, the processor is further configured to perform the following steps: extracting a service request message from an initial UE message; and acquiring a UE context in response to the service request message.
[0011] In a possible implementation manner, the processor is further configured to perform the following steps: initiating an authentication security process to the UE; when the UE authentication succeeds, determining whether the connection state of the UE is an abnormal access state according to the UE context.
[0012] In a possible implementation, the processor is further used to perform the following steps: obtaining a local context; if the UE context indicates that the connection state of the UE is an abnormal access state, and the local context indicates that the connection state of the UE is a normal access state, determining that the connection state of the UE is an abnormal access state.
[0013] In a possible implementation manner, the processor is further configured to perform the following steps: sending a UE release message to the base station, where the UE release message is used to instruct the base station to release local resources but does not notify the UE to release the resources.
[0014] In a possible implementation manner, the processor is further configured to perform the following steps: receiving a release completion message sent by the base station, where the release completion message is used to indicate that the base station has completed the release of local resources according to the UE release message.
[0015] In a possible implementation manner, the processor is further configured to perform the following steps: determining a session type of the UE according to an uplink service state and a bearer state of the UE indicated by the NAS message.
[0016] In a possible implementation, the processor is further used to perform the following steps: determining whether the NAS message carries a first message, the first message being used to indicate that the uplink service state of the UE is a request state; if not, determining whether the NAS message carries a second message, the second message being used to indicate that the bearer state of the UE is an establishment state; if not, determining that the session type of the UE is the first type.
[0017] In a possible implementation manner, the processor is further configured to perform the following steps: if the NAS message carries the first message, determining that the session type of the UE is a second type, where the second type is used to indicate that the UE has an uplink service in a request state.
[0018] In one possible implementation, the processor is also used to perform the following steps: if the NAS message does not carry the first message but carries the second message, determine that the UE's session type is a third type, and the third type is used to indicate that the UE does not have an uplink service in a requested state but has established a bearer with the core network.
[0019] In a possible implementation, the processor is further used to perform the following steps: obtaining a local context, and determining a local bearer state according to the local context; if the local bearer state indicates that a bearer is established between the UE and the core network, determining that the session type of the UE is the third type.
[0020] In a possible implementation manner, the first message includes an uplink data status Uplink Data Status message.
[0021] In a possible implementation manner, the second message includes a protocol data unit session status PDU SessionStatus message.
[0022] In one possible implementation, the core network element includes an access and mobility management function AMF.
[0023] In a possible implementation, the processor is further used to execute the following steps: AMF initiates a bearer update request to the session management function SMF, so that SMF performs session management on the restored session bearer.
[0024] According to one aspect of an embodiment of the present application, a device for restoring a bearer is applied to a core network network element, and the device includes: a message receiving module, used to receive an initial user equipment UE message sent by a base station, and determine the UE context according to a non-access layer NAS message in the initial UE message; a release initiating module, used to initiate a UE context release process to the base station if the UE context indicates that the UE's connection state is an abnormal access state; a bearer recovery module, used to execute a bearer recovery process when the NAS message indicates that the UE's session type is not a first type, and the first type is used to indicate that the UE does not have an uplink service in a requested state and no bearer is established between the UE and the core network.
[0025] According to one aspect of an embodiment of the present application, a storage medium stores a computer program thereon, and when the computer program is executed by a processor, the method for restoring the bearer as described above is implemented.
[0026] The beneficial effects of the technical solution provided by this application are:
[0027] In the above technical solution, after receiving the initial UE message sent by the base station, the core network element determines the UE context according to the NAS message in the initial UE message, and when the UE context indicates that the connection state of the UE is an abnormal access state, the UE context release process is initiated to the base station, and when the NAS message indicates that the session type of the UE is not the first type, the bearer recovery process is executed, that is, the connection state and session type of the UE are combined to comprehensively judge whether it is necessary to restore the bearer between the UE and the core network, so as to ensure that when there is an uplink service and / or downlink service in the requested state between the UE and the base station, the bearer can be restored in time to continue to transmit the uplink and downlink services, thereby effectively solving the problem of downlink service interruption due to failure to restore the bearer when the network is abnormal in the related technology. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.
[0029] Figure 1 It is a schematic diagram of the implementation environment involved in this application;
[0030] Figure 2 is a flow chart showing a method for restoring a bearer according to an exemplary embodiment;
[0031] Figure 3 yes Figure 2 A flowchart of an embodiment corresponding to step 21 in the embodiment;
[0032] Figure 4 yes Figure 2 A flowchart of another embodiment corresponding to step 21 in the embodiment;
[0033] Figure 5 yes Figure 2 A flowchart of an embodiment corresponding to step 22 in the embodiment;
[0034] Figure 6 is a flow chart showing another method for restoring a bearer according to an exemplary embodiment;
[0035] Figure 7 yes Figure 6 A flowchart of an embodiment corresponding to step 24 in an embodiment;
[0036] Figure 8 is a flow chart showing another method for restoring a bearer according to an exemplary embodiment;
[0037] Fig. 9 is a flow chart showing another method for restoring a bearer according to an exemplary embodiment;
[0038] Fig.10 is a flow chart showing another method for restoring a bearer according to an exemplary embodiment;
[0039] Fig.11 is a structural block diagram of a device for restoring a bearer according to an exemplary embodiment;
[0040] Fig.12 The present invention is a structural block diagram of a core network element according to an exemplary embodiment. DETAILED DESCRIPTION
[0041] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout identify the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present application.
[0042] It will be understood by those skilled in the art that, unless specifically stated, the singular forms "one", "said", and "the" used herein may also include plural forms, and "multiple" refers to two or more, and other quantifiers are similar. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the 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 their groups. It should be understood that when we say that an element is "connected" or "coupled" to another element, it can be directly connected or coupled to other elements, or there may be intermediate elements. In addition, the "connection" or "coupling" used here may include wireless connection or wireless coupling. The term "and / or" used here describes the association relationship of associated objects, indicating that there may be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0043] The following is an introduction and explanation of several terms involved in this application:
[0044] RAN, which stands for Radio Access Network in English, means wireless access network in Chinese. For example, the wireless access network used in the 5G New Radio (NR) system.
[0045] NAS, the full spelling of which is Non-Access Stratum in English, means non-access layer in Chinese. In contrast, AS (AccessStratum) refers to the access layer.
[0046] AMF, which stands for Access and Mobility Management Function in English, means access and mobility management function in Chinese. It is responsible for terminal equipment access to the core network and mobility management.
[0047] SMF, the full spelling of which is Session Management Function in English, means session management function in Chinese. It is responsible for interacting with the separated data plane to create, update and delete PDU sessions.
[0048] PDU, the full spelling of English is Protocol Data Unit, and its Chinese meaning is Protocol Data Unit.
[0049] PDU Session Status, which means protocol data unit session status in Chinese, is used to indicate that a bearer has been established between the UE and the core network, and is optionally included in a registration message or a service request message.
[0050] Uplink Data Status, which means uplink data status in Chinese, is used to indicate that there is uplink service that needs to be transmitted and can be optionally included in a registration message or a service request message.
[0051] UDM, which stands for Unified Data Management in English, means unified data management in Chinese. It is responsible for the management of user identification, contract data, authentication data, and user service network element registration management. For example, if AMF, SMF, etc. are currently providing services for terminal devices, when the user switches the currently accessed AMF, UDM will initiate a deregistration message to the old AMF, requiring the old AMF to delete user-related information.
[0052] NEF, which stands for Network Exposure Function, is responsible for the collection, analysis and reorganization of network capabilities, as well as the opening of network capabilities.
[0053] NRF, which stands for NF Repository Function, is responsible for business discovery, receives NF discovery requests from NF instances, and provides information about discovered NF instances to NF instances.
[0054] UPF, the full spelling of which is User Plane Function, means user plane function in Chinese.
[0055] AUSF, which stands for Authentication Server Function in English, means authentication service function in Chinese. It is used to receive requests from AMF to authenticate the identity of the terminal device, request a key from UDM, and then forward the key issued by UDM to AMF for authentication processing.
[0056] PCF, which stands for Policy Control function in English, means policy control function in Chinese. It is used to support a unified policy framework to manage network behavior, provide policy rules to network entities for implementation, and access subscription information of the unified data warehouse (UDR).
[0057] UDR, which stands for Unified Data Repository in English, means unified data warehouse function in Chinese. It is used by UDM to store subscription data or read subscription data, and PCF to store policy data or read policy data.
[0058] NG interface refers to the interface between the radio access network and the core network. Among them, N1 interface refers to the signaling plane interface between the terminal device and AMF. N2 interface refers to the signaling plane interface between RAN and AMF. N3 interface refers to the signaling plane interface between RAN and UPF. N4 interface refers to the signaling plane interface between SMF and UPF.
[0059] In the related technology, when the network is normal, the normal release of the wireless link will not cause the problem of uplink and downlink service interruption. After the old uplink and downlink services are completed, the wireless link can be released. After the wireless link is released normally, if there is a new uplink and downlink service, the wireless link can be re-established. Specifically, on the one hand, if there is a new uplink service, the uplink service is initiated by the UE side, that is, the UE will re-initiate the registration process to restore the signaling plane link or the user plane link; on the other hand, if there is a new downlink service, the downlink service is initiated by the network side, that is, the core network will initiate a paging process to request the UE to restore the signaling plane link or the user plane link.
[0060] However, when the network is abnormal, for example, when the UE detects a network abnormality, the wireless link between the UE and the core network is abnormally released, or when the NAS layer between the UE and the core network is automatically disconnected due to the self-detection protection being enabled when the network is abnormal, at this time, if the old downlink service is not completed, the downlink service may be interrupted.
[0061] Specifically, in order to restore the radio link, the UE re-initiates the registration process through registration or service request, and the signaling plane link is restored. Furthermore, the radio link recovery process also includes restoring the user plane link:
[0062] On the one hand, if there is an old uplink service that has not been completed, the UE will initiate an uplink service, that is, restore the user plane link by carrying an Uplink Data Status message in a registration message or a service request message.
[0063] On the other hand, if there is no unfinished old uplink service, the UE only restores the signaling plane link. At this time, since the UE cannot know whether there is a downlink service and will not initiate the downlink service, the user plane link is not restored, that is, the bearer is not restored. Then, when there is an unfinished old downlink service, the old downlink service cannot be transmitted normally, and an interruption occurs, which causes partial data loss and ultimately leads to poor user perception.
[0064] As can be seen from the above, the related technology still has the defect that the downlink service is interrupted because the bearer is not restored when the network is abnormal.
[0065] In view of this, the present application provides a method, device, core network element and storage medium for restoring bearer, aiming to solve the above-mentioned technical problems of related technologies.
[0066] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0067] Figure 1The present invention is a schematic diagram of an implementation environment involved in a method for restoring a bearer. The implementation environment includes a wireless communication system 100, which may be a global system of mobilecommunication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) system, or a 5G new radio (NR) system, etc., which are not limited here.
[0068] The wireless communication system 100 includes a user device 110 and a network device, which may include an access network device 130 (such as a base station) and may also include various core network elements 150, such as an evolved packet system (EPS), AMF, SMF, UDM, NEF, NRF, UPF, AUSF, PCF, UDR, etc.
[0069] Specifically, the user equipment 110, abbreviated as UE (User Equipment), is also considered as a terminal or terminal device, and refers to an electronic device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem, etc. For example, the user equipment 110 can be a mobile terminal device, such as a mobile phone (or "cellular" phone), or a computer with a mobile terminal device, such as a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device. In different systems, the name of the user equipment 110 may also be different, and it may be a personal communication service (Personal Communication Service, PCS) phone, a cordless phone, a session initiation protocol (Session Initiated Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) and other devices. The user equipment 110 may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, or a user device, without limitation herein.
[0070] The access network device 130, taking a base station as an example, may be called an access point, or may be an electronic device in the access network that communicates with the user equipment 110 over the air interface through one or more sectors, or may be another name, depending on the specific application scenario. The base station 130 may be used to exchange received air frames with Internet Protocol (IP) packets, and act as a router between the user equipment 110 and the rest of the access network, which may include an Internet Protocol network. The base station 130 may also coordinate the attribute management of the air interface. For example, the base station 130 may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB) in Wide-band Code Division Multiple Access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., but is not limited here.
[0071] After an RRC (Radio Resource Control) connection is established between the user equipment 110 and the base station 130, the base station 130 can send a wireless bearer establishment message to the user equipment 110 based on the RRC connection, so that the user equipment 110 completes the wireless bearer establishment between the user equipment 110 and the base station 130 according to the wireless bearer establishment message. As a result, the user equipment 110 can transmit uplink and downlink services with the base station 130 based on the currently established wireless bearer.
[0072] See also Figure 2 The embodiment of the present application provides a method for restoring a bearer, which is executed by a core network element. For example, the core network element is an AMF.
[0073] like Figure 2 As shown, the method may include the following steps:
[0074] Step 21: Receive an initial UE message sent by a base station, and determine a UE context according to a NAS message in the initial UE message.
[0075] First of all, it should be noted that the initial UE message is used to notify the core network that the UE requests registration.
[0076] For a UE, when it attaches to a base station for the first time, or reattaches to another base station as the UE moves, or when the wireless link between the UE and the core network needs to be restored, a registration process will be initiated to the core network.
[0077] In order to initiate a registration process with the core network, the UE first initiates a registration request or a service request to the base station, specifically: sending a registration message or a service request message to the base station.
[0078] Correspondingly, after receiving the registration message or service request message sent by the UE, the base station will send an initial UE message carrying the registration message or service request message to the core network, so that the core network knows that the UE requests registration based on the received initial UE message.
[0079] Based on this, in a possible implementation manner, the NAS message in the initial UE message includes a registration message. In a possible implementation manner, the NAS message in the initial UE message includes a service request message.
[0080] As mentioned above, when the network is normal, the normal release of the radio link will not cause the problem of uplink and downlink service interruption, but when the network is abnormal, the problem of downlink service interruption may occur. Therefore, in this embodiment, after determining the NAS message according to the initial UE message, the UE context will be further determined according to the NAS message to determine the connection state of the UE.
[0081] The connection state of the UE includes at least: normal access state, abnormal access state, and non-access state. For example, when the radio link between the UE and the core network is abnormally released, or when the NAS layer automatically disconnects due to the activation of self-detection protection, the connection state of the UE can be regarded as an abnormal access state.
[0082] If the connection state of the UE is a normal access state or a non-access state, indicating that there is no need to recover the radio link, the core network executes the relevant processing flow according to the processing flow described in the specified protocol specification.
[0083] On the contrary, if the connection state of the UE is an abnormal access state, indicating that the radio link between the UE and the core network needs to be restored, the core network element executes steps 22 to 23 to avoid downlink service interruption during the radio link recovery process.
[0084] It is worth mentioning that the UE context in each embodiment of the present application refers to the wireless link established between the UE and the core network. Therefore, the connection status of the UE can be reflected through the UE context.
[0085] The following describes the process of determining the UE context in combination with different NAS messages:
[0086] Figure 3 The flowchart of determining the UE context based on the registration message is shown as an example. In a possible implementation manner, when the NAS message is a registration message, such as Figure 3 As shown, the process of determining the UE context may include the following steps:
[0087] Step 211: extract a registration message from the initial UE message.
[0088] Step 212: If the registration message indicates that the UE is registering for the first time, a UE context is created.
[0089] Step 213: If the registration message indicates that the UE is re-registering, the UE context is obtained.
[0090] That is to say, the UE initiates a registration process through a registration message. If the registration process is considered to be an initial registration process of the UE, at this time, since the core network does not store the UE context about the UE, the core network will create a UE context for the UE.
[0091] On the contrary, if the registration process considers that the UE is re-registering, for example, the UE reattaches to another base station as it moves, then the core network stores the UE context corresponding to the UE. At this time, the core network can directly obtain the UE context.
[0092] Figure 4 The flowchart of determining the UE context based on the service request message is shown as an example. In a possible implementation manner, when the NAS message is a service request message, such as Figure 4 As shown, the process of determining the UE context may include the following steps:
[0093] Step 214: extract the service request message from the initial UE message.
[0094] Step 215: Acquire UE context in response to the service request message.
[0095] That is to say, the UE initiates the registration process through the service request message. At this time, the registration process is not the initial registration process of the UE. Then, the core network stores the UE context corresponding to the UE, and can directly obtain the UE context.
[0096] Step 22: If the UE context indicates that the connection state of the UE is an abnormal access state, a UE context release process is initiated to the base station.
[0097] As mentioned above, when the UE's connection state is abnormal access state, it may be caused by abnormal release of the radio link between the UE and the core network, or it may be caused by automatic disconnection of the NAS layer due to the activation of self-detection protection. At this time, the core network will initiate the UE context release process to the base station.
[0098] Figure 5 The flowchart of the UE context release process is exemplarily shown. In a possible implementation manner, as Figure 5 As shown, step 22 may include the following steps:
[0099] Step 221: Send a UE release message to the base station.
[0100] The UE release message is used to instruct the base station to release local resources but does not notify the UE to release the resources. The local resources include but are not limited to: wireless resources and storage resources related to the UE in the base station.
[0101] In the above process, only the base station notifies the release of resources, while the UE does not notify the release of resources, which greatly facilitates the recovery of the user plane link during the wireless link recovery process, thereby further fully ensuring that the bearer can be restored in time, thereby avoiding the problem of downlink service interruption due to failure to restore the bearer in time.
[0102] Further, see Figure 5 In a possible implementation manner, step 22 may further include the following steps:
[0103] Step 222: Receive a release completion message sent by the base station.
[0104] The release completion message is used to indicate that the base station has completed the release of local resources according to the UE release message.
[0105] Therefore, the completeness of the bearer recovery process is fully guaranteed.
[0106] Step 23: When the NAS message indicates that the session type of the UE is not the first type, a bearer recovery process is performed.
[0107] Among them, the session type is used to indicate the session status of the session established between the UE and the core network.
[0108] As mentioned above, when the network is abnormal, if only the signaling plane link is restored but not the user plane link, assuming that there is an old downlink service between the UE and the base station, the old downlink service cannot be completed because the user plane is blocked. Here, the inventor realizes that the related technology only considers whether there is an old uplink service between the UE and the base station, which has a technical loophole. Therefore, the inventor designs to introduce whether a bearer is established between the UE and the core network as the basis for whether to restore the bearer between the UE and the core network. That is to say, if a bearer is established between the UE and the core network, it means that there may be an old downlink service between the UE and the base station, and the bearer between the UE and the core network needs to be restored. In view of this, in one possible implementation, the session state includes at least: uplink service state and bearer state.
[0109] In a possible implementation, the uplink service state includes at least: a request state and an idle state. The request state means that the UE has an uplink service in the request state; the idle state means that the UE does not have an uplink service in the request state. It should be noted that the uplink service / downlink service in the request state involved in each embodiment of the present application may refer to the uplink service / downlink service being transmitted between the UE and the base station, and may also be the uplink service to be transmitted in the UE or the downlink service to be transmitted in the base station.
[0110] In one possible implementation, the bearer status includes at least: an established status and an unestablished status. The established status means that a bearer has been established between the UE and the core network, indicating that there may be a downlink service in a requested state between the UE and the base station; the unestablished status means that a bearer has not been established between the UE and the core network, indicating that there is no downlink service in a requested state between the UE and the base station. It is explained here that a bearer has been established between the UE and the core network, which means that before the abnormal release of the wireless link, a bearer was established between the UE and the core network, and then it was interrupted due to the abnormal release of the wireless link. It can also be understood that an abnormally interrupted bearer is established between the UE and the core network.
[0111] It is still necessary to add that the service includes uplink service and downlink service. Of course, in other embodiments, uplink service / downlink service can be further divided into uplink / downlink voice service and uplink / downlink data service, which is not limited here.
[0112] Based on this, in a possible implementation, the session type includes at least a first type, a second type, and a third type. The first type is used to indicate that the UE does not have an uplink service in a requested state and no bearer is established between the UE and the core network; the second type is used to indicate that the UE has an uplink service in a requested state; and the third type is used to indicate that the UE does not have an uplink service in a requested state but a bearer has been established between the UE and the core network.
[0113] Then, after determining that the UE's session type is not the first type, the core network will learn that the UE has an uplink service in a requested state or that a bearer has been established between the UE and the core network (at this time, there may be a downlink service in a requested state between the UE and the base station). In order to avoid interruption of uplink and downlink services, the core network network element will execute the bearer recovery process to ensure that the uplink and downlink services in the requested state can continue to be transmitted relying on the restored bearer.
[0114] Compared with the related technology, on the one hand, if the UE has an uplink service in the requested state, the wireless link recovery process is similar to that when the network is normal, that is, when the UE re-initiates the registration process to restore the signaling plane link, the user plane link will be restored by carrying the Uplink Data Status message in the registration message or service request message, thereby restoring the bearer.
[0115] On the other hand, if the UE does not have any uplink service in the requested state, but a bearer has been established between it and the core network, at this time, there may be a downlink service in the requested state between the UE and the base station. Different from the wireless link recovery process during network abnormalities, the UE will continue to recover the user plane link and then restore the bearer, avoiding downlink service interruption caused by the UE only restoring the signaling plane link when there is no uplink service.
[0116] Through the above process, combined with the UE's connection status and session type, it is comprehensively judged whether it is necessary to restore the bearer between the UE and the core network, so as to ensure that when there is uplink service and / or downlink service in the requested state between the UE and the base station, the bearer can be restored in time to continue transmitting the uplink and downlink services, thereby effectively solving the problem of downlink service interruption due to failure to restore the bearer when the network is abnormal in the related technology.
[0117] See also Figure 6 The embodiment of the present application provides a method for restoring a bearer, which is executed by a core network element. For example, the core network element is an AMF.
[0118] like Figure 6 As shown, the method may include the following steps:
[0119] Step 21: Receive an initial UE message sent by a base station, and determine a UE context according to a NAS message in the initial UE message.
[0120] Step 22: If the UE context indicates that the connection state of the UE is an abnormal access state, a UE context release process is initiated to the base station.
[0121] Step 24: Determine the session type of the UE according to the uplink service state and bearer state of the UE indicated by the NAS message.
[0122] Among them, the uplink service status is used to indicate whether the UE has an uplink service in a requested state. The bearer status is used to indicate whether a bearer is established between the UE and the core network. It can also be considered to indicate whether there may be a downlink service in a requested state between the UE and the base station. In one possible implementation, the uplink service status includes at least: a request state and an idle state. In one possible implementation, the bearer status includes at least: an established state and an unestablished state.
[0123] Now, in combination with the uplink service state and bearer state of the UE, the process of determining the session type of the UE is described as follows:
[0124] like Figure 7 As shown, in a possible implementation, step 24 may include the following steps:
[0125] Step 241: Determine whether the NAS message carries the first message.
[0126] The first message is used to indicate that the uplink service state of the UE is a request state.
[0127] In a possible implementation manner, the first message includes an Uplink Data Status message or any other suitable message.
[0128] If the NAS message carries the first message, it indicates that the uplink service state of the UE is in the request state, and it can also be considered that the UE has an uplink service in the request state, and step 242 is executed.
[0129] Otherwise, if the NAS message does not carry the first message, it indicates that the uplink service state of the UE is idle. It can also be considered that the UE does not have an uplink service in the requested state. Then, it is further determined whether a bearer is established between the UE and the core network, that is, step 243 is executed.
[0130] Step 242: determine that the session type of the UE is the second type.
[0131] The second type is used to indicate that the UE has an uplink service in a request state.
[0132] Step 243: Determine whether the NAS message carries the second message.
[0133] The second message is used to indicate that the bearer state of the UE is an established state.
[0134] In a possible implementation manner, the second message includes a PDU Session Status message or any other suitable message.
[0135] If the NAS message carries the second message, it indicates that the bearer status of the UE is in the established status. It can also be considered that a bearer has been established between the UE and the core network, which also indicates that there may be a downlink service in the requested status between the UE and the base station, then step 244 is executed.
[0136] Otherwise, if the NAS message does not carry the second message, it means that the bearer status of the UE is not established. It can also be considered that no bearer is established between the UE and the core network, which also means that there is no downlink service in the requested state between the UE and the base station, then execute step 245.
[0137] It is worth mentioning that the NAS message is not limited to optionally carrying the first message / second message to indicate the uplink service status / bearer status of the UE. In other embodiments, the NAS message may also optionally carry the first message / second message to indicate the uplink service status / bearer status of the UE, which does not constitute a specific limitation here.
[0138] Step 244: determine that the session type of the UE is the third type.
[0139] Among them, the third type is used to indicate that the UE does not have any uplink service in the requested state but a bearer has been established between the UE and the core network.
[0140] In order to ensure the necessity of executing the bearer recovery process, in a possible implementation manner, step 244 may further include the following steps:
[0141] Get the local context and determine the local bearer state based on the local context.
[0142] Among them, the local context is the UE context stored in the core network. Correspondingly, the local bearer state refers to the bearer state of the UE stored in the core network. The local bearer state includes at least an established state and an unestablished state. The established state is used to indicate that a bearer has been established between the UE and the core network, and the unestablished state indicates that a bearer has not been established between the UE and the core network.
[0143] In step 243, the second message is carried in the NAS message, indicating that a bearer has been established between the UE and the core network. Based on this, if the local bearer status also indicates that a bearer has been established between the UE and the core network, indicating that both the UE and the core network have determined that a bearer has been established between the two before the abnormal release of the wireless link, then the UE's session type is determined to be the third type. In this way, it is avoided to misjudge whether a bearer has been established between the UE and the core network before the abnormal release of the wireless link, thereby effectively ensuring the necessity of executing the bearer recovery process.
[0144] Step 245: determine that the session type of the UE is the first type.
[0145] From the above, it can be seen that when it is determined that the UE's session type is the first type, it means that the UE has neither an uplink service in a requested state nor a bearer established between the UE and the core network (there is no possibility of a downlink service in a requested state). At this time, there is no need for the core network element to execute the bearer recovery process, and the relevant processing process can be executed in accordance with the processing process described in the specified protocol specification.
[0146] Correspondingly, when it is determined that the UE's session type is the second type or the third type, that is, the UE has an uplink service in a requested state, or a bearer has been established between the UE and the core network (there may be a downlink service in a requested state between the UE and the base station), then the core network element needs to execute the bearer recovery process, that is, execute step 23.
[0147] Step 23: When the NAS message indicates that the session type of the UE is not the first type, a bearer recovery process is performed.
[0148] In the above process, the UE's uplink service status and bearer status are combined to determine the UE's session type, which is used as one of the bases for judging whether it is necessary to restore the bearer between the UE and the core network, thereby avoiding the technical loophole in the related technology of only restoring the wireless link through the Uplink Data Status message.
[0149] Figure 8 The following is a flowchart of a method for restoring a bearer executed by AMF. Figure 8 A method for restoring a bearer provided in an embodiment of the present application is described as follows:
[0150] like Figure 8 As shown, the method may include the following steps:
[0151] Step 401: After receiving the initial UE message, the AMF determines the NAS message in the initial UE message.
[0152] The NAS message includes at least a registration message and a service request message.
[0153] Step 402: Determine the UE context according to the NAS message.
[0154] Specifically, on one hand, when the NAS message is a registration message, if the registration message indicates that the UE is initially registering, a UE context is created; otherwise, when the registration message indicates that the UE is re-registering, the UE context is acquired.
[0155] On the other hand, when the NAS message is a service request message, the UE context is acquired in response to the service request message.
[0156] Step 403: AMF determines whether the connection state of the UE is an abnormal access state.
[0157] Specifically, if the connection state of the UE is a normal access state or a non-access state, the AMF executes the relevant processing flow according to the processing flow described in the specified protocol specification.
[0158] On the contrary, if the connection state of the UE is an abnormal access state, step 404 is executed.
[0159] Step 404: Initiate a UE context release process to the base station.
[0160] Specifically, the AMF sends the UE release message to the base station. Correspondingly, after receiving the UE release message, the base station only releases local resources according to the instructions of the UE release message and does not notify the UE to release the resources.
[0161] After the base station completes the release of local resources, step 405 is executed.
[0162] Step 405: AMF determines whether the NAS message carries the Uplink Data Status message.
[0163] Specifically, if the NAS message carries an Uplink Data Status message, indicating that the UE has an uplink service in a request state, it is determined that the bearer needs to be restored, ie, step 407 is executed.
[0164] On the contrary, if the NAS message does not carry the Uplink Data Status message, it means that the UE does not have an uplink service in the requested state, and step 406 is executed.
[0165] Step 406: AMF determines whether the NAS message carries a PDU Session Status message.
[0166] Specifically, if the NAS message carries a PDU Session Status message, it indicates that a bearer has been established between the UE and the core network. It can also be understood that there may be a downlink service in a requested state between the UE and the base station. In this case, it is determined that the bearer needs to be restored, that is, step 407 is executed.
[0167] On the contrary, if the NAS message does not carry the PDU Session Status message, it means that no bearer is established between the UE and the core network, that is, there is no downlink service in the requested state between the UE and the base station, and it is determined that the bearer does not need to be restored. At this time, the AMF follows the processing flow described in the specified protocol specification to execute the relevant processing flow.
[0168] Step 407, execute the bearer recovery process.
[0169] Therefore, the bearer recovery between the UE and the core network is achieved through AMF when the network is abnormal, which fully guarantees that the uplink service and / or downlink service in the requested state between the UE and the base station can continue to be transmitted relying on the restored bearer, thereby effectively solving the problem of downlink service interruption due to failure to restore the bearer when the network is abnormal in the related technology.
[0170] See also Fig. 9 The present application embodiment provides a method for restoring a bearer, which is applicable to Figure 1 A wireless communication system 100 is shown in an implementation environment.
[0171] In this embodiment, the wireless communication system includes at least: user equipment UE (ie, terminal), access network equipment RAN (ie, base station), core network elements AMF and SMF.
[0172] like Fig. 9 As shown, the method may include the following steps:
[0173] Step 501: UE sends a registration message to RAN.
[0174] Step 502: After receiving the registration message, the RAN sends an initial UE message carrying the registration message to the AMF.
[0175] Step 503: After receiving the initial UE message, the AMF initiates an authentication security process to the UE.
[0176] It is explained here that the purpose of the authentication security process is to verify whether the UE has the right to use the relevant resources of the core network.
[0177] Step 504: When the UE is successfully authenticated, the AMF determines whether the UE's connection state is an abnormal access state.
[0178] Specifically, if the registration message indicates that the UE is initially registering, a UE context is created; if the registration message indicates that the UE is re-registering, the UE context is acquired, and the UE context is determined in this way, and then the connection state of the UE is determined according to the UE context.
[0179] If the UE's connection state is a normal access state or a non-access state, the AMF executes the relevant processing flow according to the processing flow described in the specified protocol specification.
[0180] On the contrary, if the connection state of the UE is an abnormal access state, step 505 is executed.
[0181] Further, in order to ensure the necessity of executing the bearer recovery process, the process of determining the connection state of the UE may include the following steps:
[0182] Obtain the local context and determine the local connection status of the UE according to the local context.
[0183] The local context is the UE context stored in the AMF. Correspondingly, the local connection state of the UE refers to the connection state of the UE stored in the AMF. The local connection state of the UE includes at least: normal access state, abnormal access state and non-access state.
[0184] Based on this, if the local connection status of the UE indicates that the UE's connection status is a normal access status, and the UE's connection status determined by the UE context is an abnormal access status, that is, the wireless link between the UE and the core network is abnormally released, then the UE's connection status is determined to be an abnormal access status, and then step 505 is executed. In this way, the misjudgment of whether the UE's connection status is an abnormal access status is avoided, thereby effectively ensuring the necessity of executing the bearer recovery process.
[0185] Step 505: Initiate a UE context release process to the RAN.
[0186] Specifically, the AMF sends the UE release message to the RAN. Correspondingly, after receiving the UE release message, the RAN only releases local resources according to the instructions of the UE release message and does not notify the UE to release the resources.
[0187] After the RAN completes the release of local resources, step 506 is executed.
[0188] Step 506: Send a release completion message to AMF to notify AMF that RAN has completed the release of local resources.
[0189] Step 507: AMF determines whether to restore the bearer based on the Uplink Data Status message and the PDU Session Status message.
[0190] Specifically, if the registration message carries an Uplink Data Status message, indicating that the UE has an uplink service in a request state, it is determined that the bearer needs to be restored, ie, step 508 is executed.
[0191] If the registration message does not carry the Uplink Data Status message but carries the PDU Session Status message, it means that the UE does not have an uplink service in the requested state but has established a bearer with the core network, and it is determined that the bearer needs to be restored, that is, step 508 is executed.
[0192] Here, in order to ensure the accuracy of the bearer recovery determination process, after determining that the registration message carries the PDUSession Status message, it can be further combined with the local bearer status indicated by the local context to jointly determine whether the bearer needs to be restored. In this way, it is possible to avoid misjudgment of whether a bearer is established between the UE and the core network before the abnormal release of the wireless link, thereby effectively ensuring the necessity of executing the bearer recovery process.
[0193] If the registration message carries neither the Uplink Data Status message nor the PDU Session Status message, it means that the UE does not have an uplink service in the requested state and no bearer is established with the core network, then it is determined that no bearer recovery is required. At this time, the AMF executes the relevant processing flow according to the processing flow described in the specified protocol specification.
[0194] Step 508: Execute the bearer recovery process.
[0195] Specifically, the following steps are included: Step 5081, AMF initiates a bearer update request to SMF so that SMF can perform session management on the subsequently restored session bearer; Step 5082, SMF returns a bearer update response message to AMF; Step 5083, executes relevant processing procedures in accordance with the bearer recovery process described in the specified protocol specification.
[0196] In this way, the bearer is restored, so that the uplink service and / or downlink service in the request state between the UE and the RAN can continue to be transmitted by relying on the restored bearer.
[0197] In the above process, the wireless link is restored through registration messages when the network is abnormal, and then the bearer is restored, thereby fully ensuring that the uplink and downlink services in the requested state between the UE and the base station can continue to be transmitted, thereby effectively solving the problem of downlink service interruption due to failure to restore the bearer when the network is abnormal in the related technology.
[0198] See also Fig.10 The present application embodiment provides a method for restoring a bearer, which is applicable to Figure 1 A wireless communication system 100 is shown in an implementation environment.
[0199] In this embodiment, the wireless communication system includes at least: user equipment UE (ie, terminal), access network equipment RAN (ie, base station), core network elements AMF and SMF.
[0200] like Fig.10 As shown, the method may include the following steps:
[0201] Step 601: UE sends a service request message to RAN.
[0202] Step 602: After receiving the service request message, the RAN sends an initial UE message carrying the service request message to the AMF.
[0203] Step 603: After receiving the initial UE message, the AMF initiates an authentication security process to the UE.
[0204] It is explained here that the purpose of the authentication security process is to verify whether the UE has the right to use the wireless resources related to the core network.
[0205] Step 604: When the UE is successfully authenticated, the AMF determines whether the UE's connection state is an abnormal access state.
[0206] Specifically, the UE context is acquired in response to the service request message, and the UE context is determined in this way, and then the connection state of the UE is determined according to the UE context.
[0207] If the UE's connection state is a normal access state or a non-access state, the AMF executes the relevant processing flow according to the processing flow described in the specified protocol specification.
[0208] On the contrary, if the connection state of the UE is an abnormal access state, step 605 is executed.
[0209] Further, in order to ensure the necessity of executing the bearer recovery process, the process of determining the connection state of the UE may include the following steps:
[0210] Obtain the local context and determine the local connection status of the UE according to the local context.
[0211] The local context is the UE context stored in the AMF. Correspondingly, the local connection state of the UE refers to the connection state of the UE stored in the AMF.
[0212] Based on this, if the UE's local connection status indicates that the UE's connection status is a normal access status, and the UE's connection status determined by the UE context is an abnormal access status, that is, the wireless link between the UE and the core network is abnormally released, then the UE's connection status is determined to be an abnormal access status, and step 605 is executed.
[0213] Step 605: Initiate a UE context release process to the RAN.
[0214] Specifically, the AMF sends the UE release message to the RAN. Correspondingly, after receiving the UE release message, the RAN only releases local resources according to the instructions of the UE release message and does not notify the UE to release the resources.
[0215] After the RAN completes the release of local resources, step 606 is executed.
[0216] Step 606: Send a release completion message to AMF to notify AMF that RAN has completed the release of local resources.
[0217] Step 607: AMF determines whether to restore the bearer based on the Uplink Data Status message and the PDU Session Status message.
[0218] If the service request message carries an Uplink Data Status message, indicating that the UE has an uplink service in the requested state, it is determined that the bearer needs to be restored, ie, step 508 is executed.
[0219] If the service request message does not carry the Uplink Data Status message but carries the PDU Session Status message, it means that the UE does not have an uplink service in the requested state but has established a bearer with the core network, and it is determined that the bearer needs to be restored, that is, step 508 is executed.
[0220] Here, in order to ensure the accuracy of the bearer recovery determination process, after determining that the service request message carries the PDUSession Status message, it can be further combined with the local bearer status indicated by the local context to jointly determine whether the bearer needs to be restored. In this way, it is possible to avoid misjudgment of whether a bearer was established between the UE and the core network before the abnormal release of the wireless link, thereby effectively ensuring the necessity of executing the bearer recovery process.
[0221] If the service request message carries neither the Uplink Data Status message nor the PDU Session Status message, it means that the UE does not have an uplink service in the requested state and no bearer is established with the core network, then it is determined that no bearer recovery is required. At this time, the AMF executes the relevant processing flow according to the processing flow described in the specified protocol specification.
[0222] Step 608, execute the bearer recovery process.
[0223] Specifically, the following steps are included: Step 6081, AMF initiates a bearer update request to SMF so that SMF can perform session management on the subsequently restored session bearer; Step 6082, SMF returns a bearer update response message to AMF; Step 6083, executes relevant processing procedures in accordance with the bearer recovery process described in the specified protocol specification.
[0224] In this way, the bearer is restored, so that the uplink service and / or downlink service in the request state between the UE and the RAN can continue to be transmitted by relying on the restored bearer.
[0225] In the above process, the wireless link is restored through the service request message when the network is abnormal, and then the bearer is restored, thereby fully ensuring that the uplink and downlink services in the requested state between the UE and the base station can continue to be transmitted, thereby effectively solving the problem of downlink service interruption due to failure to restore the bearer when the network is abnormal in the related technology.
[0226] The following is an embodiment of the device of the present application, which can be used to execute the method for restoring the bearer involved in the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method for restoring the bearer involved in the present application.
[0227] See also Fig.11 In an embodiment of the present application, a device 900 for restoring bearer is provided, which is applied to a core network element.
[0228] The bearer recovery device 900 includes, but is not limited to: a message receiving module 901 , a release initiating module 902 , and a bearer recovery module 903 .
[0229] The message receiving module 901 is used to receive an initial user equipment UE message sent by a base station, and determine a UE context according to a non-access layer NAS message in the initial UE message.
[0230] The release initiating module 902 is configured to initiate a UE context release process to the base station if the UE context indicates that the connection state of the UE is an abnormal access state.
[0231] The bearer recovery module 903 is used to execute the bearer recovery process when the NAS message indicates that the session type of the UE is not the first type. The first type is used to indicate that the UE does not have an uplink service in the requested state and no bearer is established between the UE and the core network.
[0232] It should be noted that the division of units and / or modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit and / or module in each embodiment of the present application may be integrated into a processing unit and / or module, or each unit and / or module may exist physically separately, or two or more units and / or modules may be integrated into one unit and / or module. The above-mentioned integrated units and / or modules may be implemented in the form of hardware or in the form of software functional units and / or modules.
[0233] If the integrated units and / or modules are implemented in the form of software functional units and / or modules and sold or used as independent products, they can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.
[0234] In addition, the device for restoring the bearer and the method for restoring the bearer provided in the above embodiments are based on the same application concept. Since the principles of solving the problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.
[0235] Therefore, combined with the UE's connection status and session type, a comprehensive judgment is made as to whether the bearer between the UE and the core network needs to be restored, so as to ensure that when there is uplink service and / or downlink service in the requested state between the UE and the base station, the bearer can be restored in time to continue transmitting the uplink and downlink services, thereby effectively solving the problem of downlink service interruption due to failure to restore the bearer when the network is abnormal in the related technology.
[0236] Fig.12 A structural block diagram of a core network element is shown according to an exemplary embodiment. For example, the core network element is an AMF.
[0237] like Fig.12 As shown, the core network element 1100 includes at least: a processor 1110 , a memory 1120 and a transceiver 1130 .
[0238] The transceiver 1130 is used to receive and send data under the control of the processor 1110 .
[0239] exist Fig.12In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1110 and memory represented by memory 1120. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1130 may be a plurality of components, namely, a transmitter and a receiver, providing units and / or modules for communicating with various other devices on a transmission medium, which may include a wireless channel, a wired channel, an optical cable, and other transmission media.
[0240] The processor 1110 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1110 when performing operations.
[0241] Optionally, the processor 1110 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor 1110 may also adopt a multi-core architecture. The processor 1110 and the memory 1120 may also be physically arranged separately.
[0242] The processor 1110 calls the computer program stored in the memory 1120 to execute any one of the bearer recovery methods provided in the above embodiments of the present application according to the obtained executable instructions.
[0243] Specifically, the processor 1110 is used to perform the following steps: receive an initial user equipment UE message sent by the base station, and determine the UE context based on the non-access layer NAS message in the initial UE message; if the UE context indicates that the UE's connection state is an abnormal access state, initiate a UE context release process to the base station; when the NAS message indicates that the UE's session type is not the first type, execute a bearer recovery process, and the first type is used to indicate that the UE does not have an uplink service in a requested state and no bearer is established between the UE and the core network.
[0244] In a possible implementation manner, the NAS message includes a registration message.
[0245] In a possible implementation manner, the processor is further configured to perform the following steps: extracting a registration message from an initial UE message; if the registration message indicates that the UE is an initial registration, creating a UE context; otherwise, obtaining the UE context.
[0246] In a possible implementation manner, the NAS message includes a service request message.
[0247] In a possible implementation manner, the processor is further configured to perform the following steps: extracting a service request message from an initial UE message; and acquiring a UE context in response to the service request message.
[0248] In a possible implementation manner, the processor is further configured to perform the following steps: initiating an authentication security process to the UE; when the UE authentication succeeds, determining whether the connection state of the UE is an abnormal access state according to the UE context.
[0249] In a possible implementation, the processor is further used to perform the following steps: obtaining a local context; if the UE context indicates that the connection state of the UE is an abnormal access state, and the local context indicates that the connection state of the UE is a normal access state, determining that the connection state of the UE is an abnormal access state.
[0250] In a possible implementation manner, the processor is further configured to perform the following steps: sending a UE release message to the base station, where the UE release message is used to instruct the base station to release local resources but does not notify the UE to release the resources.
[0251] In a possible implementation manner, the processor is further configured to perform the following steps: receiving a release completion message sent by the base station, where the release completion message is used to indicate that the base station has completed the release of local resources according to the UE release message.
[0252] In a possible implementation manner, the processor is further configured to perform the following steps: determining a session type of the UE according to an uplink service state and a bearer state of the UE indicated by the NAS message.
[0253] In a possible implementation, the processor is further used to perform the following steps: determining whether the NAS message carries a first message, the first message being used to indicate that the uplink service state of the UE is a request state; if not, determining whether the NAS message carries a second message, the second message being used to indicate that the bearer state of the UE is an establishment state; if not, determining that the session type of the UE is the first type.
[0254] In a possible implementation manner, the processor is further configured to perform the following steps: if the NAS message carries the first message, determining that the session type of the UE is a second type, where the second type is used to indicate that the UE has an uplink service in a request state.
[0255] In one possible implementation, the processor is also used to perform the following steps: if the NAS message does not carry the first message but carries the second message, determine that the UE's session type is a third type, and the third type is used to indicate that the UE does not have an uplink service in a requested state but has established a bearer with the core network.
[0256] In a possible implementation, the processor is further used to perform the following steps: obtaining a local context, and determining a local bearer state according to the local context; if the local bearer state indicates that a bearer is established between the UE and the core network, determining that the session type of the UE is the third type.
[0257] In a possible implementation manner, the first message includes an uplink data status Uplink Data Status message.
[0258] In a possible implementation manner, the second message includes a protocol data unit session status PDU SessionStatus message.
[0259] In one possible implementation, the core network element includes an access and mobility management function AMF.
[0260] In a possible implementation, the processor is further used to execute the following steps: AMF initiates a bearer update request to the session management function SMF, so that SMF performs session management on the restored session bearer.
[0261] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
[0262] In addition, a storage medium is provided in an embodiment of the present application, on which a computer program is stored, and when the computer program is executed by the processor, the method for recovering the load in the above-mentioned embodiments is implemented. The storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.
[0263] In an embodiment of the present application, a program product is provided, for example, the program product is an FPGA chip or a DSP chip, and the program product includes executable instructions, and the executable instructions are stored in a storage medium. The processor reads the executable instructions from the storage medium, so that when the executable instructions are executed by the processor, the method for restoring the load in the above embodiments is implemented.
[0264] Compared with the related technologies, the recovery of the bearer in the event of network anomalies is realized. On the one hand, if the UE has an uplink service in the requested state, the wireless link recovery process is similar to that when the network is normal, that is, when the UE re-initiates the registration process to restore the signaling plane link, the user plane link will be restored by carrying the Uplink Data Status message in the registration message or service request message, thereby restoring the bearer. On the other hand, if the UE does not have an uplink service in the requested state, but a bearer has been established with the core network, at this time, there may be a downlink service in the requested state between the UE and the base station. Different from the wireless link recovery process when the network is abnormal, the UE will continue to restore the user plane link, thereby restoring the bearer, avoiding the downlink service interruption caused by the UE only restoring the signaling plane link when there is no uplink service, thereby avoiding partial data loss and effectively improving user perception.
[0265] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.
[0266] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0267] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0268] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0269] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.
[0270] The above description is only a partial implementation method of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.
Claims
1. A method for restoring a bearer, characterized in that: Executed by a core network element, the method includes: Receiving an initial user equipment UE message sent by a base station, and determining a UE context according to a non-access stratum NAS message in the initial UE message; If the UE context indicates that the connection state of the UE is an abnormal access state, initiating a UE context release process to the base station; When the NAS message indicates that the session type of the UE is not the first type, a bearer recovery process is performed, where the first type is used to indicate that the UE does not have an uplink service in a requested state and no bearer is established between the UE and the core network.
2. The method according to claim 1, characterized in that The NAS message includes a registration message; The determining the UE context according to the NAS message in the initial UE message includes: Extracting the registration message from the initial UE message; If the registration message indicates that the UE is initially registering, the UE context is created; otherwise, the UE context is acquired.
3. The method according to claim 1, characterized in that The NAS message includes a service request message; The determining the UE context according to the NAS message in the initial UE message includes: Extracting the service request message from the initial UE message; In response to the service request message, the UE context is acquired.
4. The method according to claim 1, characterized in that If the UE context indicates that the connection state of the UE is an abnormal access state, before initiating a UE context release process to the base station, the method further includes: Initiate authentication security process to UE; When the UE authentication succeeds, it is determined whether the connection state of the UE is an abnormal access state according to the UE context.
5. The method according to claim 4, characterized in that The determining, according to the UE context, whether the connection state of the UE is an abnormal access state includes: Get the local context; If the UE context indicates that the connection state of the UE is an abnormal access state, and the local context indicates that the connection state of the UE is a normal access state, it is determined that the connection state of the UE is an abnormal access state.
6. The method according to claim 1, characterized in that The initiating a UE context release process to the base station includes: A UE release message is sent to the base station, where the UE release message is used to instruct the base station to release local resources but does not notify the UE to release the resources.
7. The method according to claim 6, characterized in that The initiating a UE context release process to the base station also includes: A release completion message sent by a base station is received, where the release completion message is used to indicate that the base station has completed the release of the local resources according to the UE release message.
8. The method according to claim 1, characterized in that When the NAS message indicates that the session type of the UE is not the first type, before executing the bearer recovery process, the method further includes: The session type of the UE is determined according to the uplink service state and the bearer state of the UE indicated by the NAS message.
9. The method according to claim 8, characterized in that The determining the session type of the UE according to the uplink service state and the bearer state of the UE indicated by the NAS message includes: Determine whether the NAS message carries a first message, where the first message is used to indicate that the uplink service state of the UE is a request state; If not, determining whether the NAS message carries a second message, where the second message is used to indicate that the bearer state of the UE is an established state; If not, it is determined that the session type of the UE is the first type.
10. The method according to claim 9, characterized in that The determining the session type of the UE according to the uplink service state and the bearer state of the UE indicated by the NAS message further includes: If the NAS message carries the first message, it is determined that the session type of the UE is a second type, where the second type is used to indicate that the UE has an uplink service in a request state.
11. The method according to claim 9, characterized in that The determining the session type of the UE according to the uplink service state and the bearer state of the UE indicated by the NAS message further includes: If the NAS message does not carry the first message but carries the second message, it is determined that the session type of the UE is a third type, and the third type is used to indicate that the UE does not have an uplink service in a requested state but has established a bearer with the core network.
12. The method according to claim 11, characterized in that The determining that the session type of the UE is the third type includes: Acquire a local context, and determine a local bearer state according to the local context; If the local bearer status indicates that a bearer is established between the UE and the core network, it is determined that the session type of the UE is the third type.
13. The method according to claim 9, characterized in that The first message includes an uplink data status UplinkData Status message.
14. The method according to claim 9, characterized in that The second message includes a protocol data unit session status PDU Session Status message.
15. The method according to any one of claims 1 to 14, characterized in that: The core network element includes an access and mobility management function AMF; When the NAS message indicates that the session type of the UE is not the first type, after executing the bearer recovery process, the method further includes: AMF initiates a bearer update request to the session management function SMF, so that SMF performs session management on the restored session bearer.
16. A core network element, characterized in that: include: Memory, transceiver, and processor; The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; and the processor is used to read the computer program in the memory to implement the method for restoring the bearer as described in any one of claims 1 to 15.
17. A device for restoring load, characterized in that: Applied to a core network element, the device comprises: A message receiving module, configured to receive an initial user equipment UE message sent by a base station, and determine a UE context according to a non-access layer NAS message in the initial UE message; A release initiating module, configured to initiate a UE context release process to a base station if the UE context indicates that the connection state of the UE is an abnormal access state; The bearer recovery module is used to execute the bearer recovery process when the NAS message indicates that the session type of the UE is not the first type, wherein the first type is used to indicate that the UE does not have an uplink service in a requested state and no bearer is established between the UE and the core network.
18. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for restoring a bearer according to any one of claims 1 to 15 is implemented.
