CN115134948A - Method, device, core network element and storage medium for restoring bearer - Google Patents

Abstract

Embodiments of the present application provide a method, an apparatus, a core network element, and a storage medium for restoring a bearer, which relate to the field of communications technologies. The method for restoring a bearer is performed by a core network element, and the method includes: receiving an initial user equipment UE message sent by the base station, and determining the UE context according to the non-access stratum NAS message in the initial UE message; if the UE context indicates If the connection state of the UE is in the abnormal access state, the UE context release process is initiated to the base station; when the NAS message indicates that the session type of the UE is not the first type, the bearer recovery process is performed, and the first type is used to indicate that the UE does not exist in the requesting state. Status uplink service and bearer is not established between the UE and the core network. The embodiments of the present application solve the problem in the related art that the downlink service is interrupted due to the unrecovery of the bearer when the network is abnormal.

Description

Method, device, core network element and storage medium for restoring bearer

technical field

The present application relates to the field of communication technologies, and in particular, the present application relates to a method, an apparatus, a core network element and a storage medium for restoring bearer.

Background technique

In the case of network abnormalities such as the abnormal release of the radio link or the automatic disconnection of the NAS layer, the UE will re-initiate the registration process in order to restore the radio link.

However, in the above radio link restoration process, there may be a situation that 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 has not been restored. If there is downlink service at this time, it will cause downlink service interruption, resulting in partial data loss, and ultimately poor user perception.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a method, device, core network element and storage medium for restoring bearer, which can solve the problem of downlink service interruption caused by unrestored bearer when the network is abnormal in the related art. The technical solution is as follows:

According to an aspect of the embodiments of the present application, a method for resuming a bearer is performed by a core network element, the method includes: receiving an initial user equipment UE message sent by a base station, and according to a non-access stratum NAS in the initial UE message The message determines the UE context; if 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; when the NAS message indicates that the session type of the UE is not the first type, the bearer recovery process is performed. The type is used to indicate that there is no uplink service in the request state for the UE and no bearer is established between the UE and the core network.

According to an aspect of the embodiments of the present application, a core network element includes: a memory, a transceiver, and a processor; wherein the memory is used to store a computer program; and the transceiver is used to send and receive data under the control of the processor a processor for reading the computer program in the memory and performing the following steps: receiving an initial user equipment UE message sent by the base station, and determining the UE context according to the non-access stratum NAS message in the initial UE message; if the UE context indicates that the UE If the connection state is abnormal access state, the UE context release process is initiated to the base station; when the NAS message indicates that the session type of the UE is not the first type, the bearer recovery process is performed, and the first type is used to indicate that the UE does not exist in the request state and the bearer is not established between the UE and the core network.

In one possible implementation, the NAS message includes a registration message.

In a possible implementation manner, the processor is further configured to perform the following steps: extracting a registration message from the initial UE message; creating a UE context if the registration message indicates that the UE is initially registered; otherwise, acquiring the UE context.

In one possible implementation, the NAS message includes a service request message.

In a possible implementation manner, the processor is further configured to perform the following steps: extracting the service request message from the initial UE message; and acquiring the UE context in response to the service request message.

In a possible implementation manner, the processor is further configured to perform the following steps: initiate an authentication security process to the UE; when the UE authentication succeeds, determine whether the connection state of the UE is an abnormal access state according to the UE context.

In a possible implementation manner, the processor is further configured 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, then It is determined that the connection state of the UE is an abnormal access state.

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 not notify the UE to release resources.

In a possible implementation manner, the processor is further configured to perform the following steps: receiving a release complete message sent by the base station, where the release complete message is used to indicate that the base station has completed the release of local resources according to the UE release message.

In a possible implementation manner, the processor is further configured to perform the following step: determine the session type of the UE according to the uplink service status and bearer status of the UE indicated by the NAS message.

In a possible implementation manner, the processor is further configured to perform the following steps: determine whether the NAS message carries a first message, and the first message is used to indicate that the uplink service state of the UE is a request state; if not, determine whether the NAS message contains a first message. Whether to carry the second message, the second message is used to indicate that the bearer state of the UE is the establishment state; if not, it is determined that the session type of the UE is the first type.

In a possible implementation manner, the processor is further configured to perform the following steps: if the NAS message carries the first message, determine that the session type of the UE is the second type, and the second type is used to indicate that the UE exists in the request state Upstream business.

In a possible implementation manner, the processor is further configured to perform the following steps: if the NAS message does not carry the first message but carries the second message, determine that the session type of the UE is the third type, and the third type is used to indicate The UE has no uplink service in the request state but has established a bearer with the core network.

In a possible implementation manner, the processor is further configured to perform the following steps: obtain a local context, and determine 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, determine the session of the UE Type is the third type.

In a possible implementation manner, the first message includes an Uplink Data Status message.

In a possible implementation, the second message includes a Protocol Data Unit Session Status PDU SessionStatus message.

In a possible implementation, the core network element includes an access and mobility management function AMF.

In a possible implementation manner, the processor is further configured to perform the following step: the AMF initiates a bearer update request to the session management function SMF, so that the SMF performs session management on the restored session bearer.

According to an aspect of the embodiments of the present application, an apparatus for restoring a bearer, applied to a core network element, includes: a message receiving module, configured to receive an initial user equipment UE message sent by a base station, The access stratum NAS message determines the UE context; the release initiation module is used to initiate the 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; the bearer recovery module is used when the NAS message indicates the UE's session. When the type is not the first type, the bearer recovery process is performed, and the first type is used to indicate that the UE does not have an uplink service in a request state and no bearer is established between the UE and the core network.

According to an aspect of the embodiments of the present application, a storage medium stores a computer program thereon, and when the computer program is executed by a processor, the above-mentioned method for restoring a bearer is implemented.

The beneficial effects brought by the technical solution provided by the application are:

In the above technical solution, after receiving the initial UE message sent by the base station, the core network element will determine the UE context according to the NAS message in the initial UE message, when the UE context indicates that the connection state of the UE is abnormal access state , initiate the UE context release process to the base station, and when the NAS message indicates that the UE's session type is not the first type, execute the bearer recovery process, that is, combine the UE's connection status and session type to comprehensively judge whether it is necessary to restore the UE and the core In this way, when there is an uplink service and/or downlink service in the request 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 network problems existing in the related art. In the event of an exception, the downlink service is interrupted because the bearer is not restored.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments of the present application.

1 is a schematic diagram of an implementation environment involved in the present application;

FIG. 2 is a flowchart of a method for restoring a bearer according to an exemplary embodiment;

Fig. 3 is a flowchart of step 21 in an embodiment corresponding to Fig. 2;

Fig. 4 is the flowchart of step 21 in the corresponding embodiment of Fig. 2 in another embodiment;

Fig. 5 is the flow chart of step 22 in one embodiment in the corresponding embodiment of Fig. 2;

FIG. 6 is a flowchart illustrating another method for restoring a bearer according to an exemplary embodiment;

Fig. 7 is the flow chart of step 24 in one embodiment in the corresponding embodiment of Fig. 6;

FIG. 8 is a flowchart of another method for restoring a bearer according to an exemplary embodiment;

FIG. 9 is a flowchart of another method for restoring a bearer according to an exemplary embodiment;

FIG. 10 is a flowchart of another method for restoring a bearer according to an exemplary embodiment;

FIG. 11 is a structural block diagram of an apparatus for restoring a bearer according to an exemplary embodiment;

Fig. 12 is a structural block diagram of a core network element according to an exemplary embodiment.

Detailed ways

The following describes in detail the embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals identify the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, but not to be construed as a limitation on the present application.

It will be understood by those skilled in the art that unless expressly stated otherwise, the singular forms "a", "an", "the" and "the" can also include the plural forms, and "a plurality" refers to two or two more than one, and other quantifiers are similar. It should be further understood that the word "comprising" used in the specification of this application refers to the presence of stated features, integers, steps, operations, elements and/or components, but does not preclude the presence or addition of one or more other features, Integers, steps, operations, elements, components and/or groups thereof. It will be understood that when we refer to an element as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Furthermore, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. The word "and/or" used here describes the relationship of the related objects, and means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist simultaneously, and B exists alone. a situation. The character "/" generally indicates that the associated objects are an "or" relationship.

The following is the introduction and explanation of several terms involved in this application:

RAN, the English spelling is Radio Access Network, and the Chinese meaning is Radio Access Network. For example, a radio access network applied to a 5G New Radio (NR) system.

NAS, the English spelling is Non-Access Stratum, the Chinese meaning is non-access stratum, relatively, AS (AccessStratum) refers to the access stratum.

AMF, English spelling for Access and Mobility Management Function, Chinese meaning for access and mobility management function, is responsible for terminal equipment access to the core network and mobility management.

SMF, spelled Session Management Function in English, and Session Management Function in Chinese, is responsible for interacting with the separated data plane, creating, updating and deleting PDU sessions.

PDU, the English spelling is Protocol Data Unit, and the Chinese meaning is Protocol Data Unit.

PDU Session Status, which means Protocol Data Unit Session Status in Chinese, is used to indicate that a bearer is established between the UE and the core network, and is optionally included in a registration message or a service request message.

Uplink Data Status, which means uplink data status in Chinese, is used to indicate that there is an uplink service that needs to be transmitted, and is optionally included in a registration message or a service request message.

UDM, the English spelling is Unified Data Management, and the Chinese meaning is unified data management function. It is responsible for the management of user identification, contract data, authentication data, and user service network element registration management. For example, assuming that the AMF, SMF, etc. currently provide services for the terminal device, when the user switches the currently accessed AMF, the UDM will send a logout message to the old AMF, requesting the old AMF to delete user-related information.

NEF, which is spelled Network Exposure Function in English, is responsible for the collection, analysis and reorganization of network capabilities, as well as the opening of network capabilities.

NRF, which is spelled NF Repository Function in English, is responsible for service discovery, receives NF discovery requests from NF instances, and provides NF instances with information about discovered NF instances.

UPF, the English spelling is User Plane Function, and the Chinese meaning is User Plane Function.

AUSF, the English spelling is Authentication Server Function, and the Chinese meaning is authentication service function. It is used to receive the request of AMF to authenticate the terminal device. It requests the key from UDM, and then forwards the key issued by UDM to AMF for processing. Authentication processing.

PCF, the English spelling is Policy Control function, and the Chinese meaning is Policy Control Function, which is used to support a unified policy framework to manage network behavior, provide policy rules for network entities to implement and execute, and access subscription information of the Unified Data Warehouse (UDR).

UDR, spelled Unified Data Repository in English, and unified data warehouse function in Chinese, is used for UDM to store subscription data or read subscription data, and PCF to store policy data or read policy data.

The NG interface refers to the interface between the radio access network and the core network. The N1 interface refers to the signaling plane interface between the terminal device and the AMF. The N2 interface refers to the signaling plane interface between the RAN and the AMF. The N3 interface refers to the signaling plane interface between the RAN and the UPF. N4 interface refers to the signaling plane interface between SMF and UPF.

In the related art, when the network is normal, for the normal release of the wireless link, the problem of interruption of uplink and downlink services does not occur. After the old uplink and downlink services are completed, the radio link can be released. After the radio link is normally released, if there is new uplink and downlink services, the radio link can be re-established. Specifically, on the one hand, if there is a new uplink service, the UE side initiates the uplink service, 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 For services, 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.

However, when the network is abnormal, for example, when the UE detects the network abnormality, the radio link between the UE and the core network is abnormally released, or the NAS layer between the UE and the core network is turned on for self-detection protection when the network is abnormal. Automatic disconnection. At this time, if the old downlink service is not completed, the downlink service may be interrupted.

Specifically, in order to restore the radio link, the UE re-initiates the registration process through a registration or service request, and the signaling plane link is restored. Further, the radio link restoration process also includes restoring the user plane link:

On the one hand, if the old uplink service is not completed, the UE will initiate the uplink service, that is, restore the user plane link by carrying the Uplink Data Status message in the registration message or the service request message.

On the other hand, if there is no old uplink service that has not been completed, 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 a downlink service, the user plane link is not restored. , that is, the bearer is not restored, then, when there is an old downlink service that is not completed, the old downlink service cannot be transmitted normally, resulting in interruption, which in turn causes some data loss, and ultimately leads to poor user perception.

As can be seen from the above, the related art still has the defect that the downlink service is interrupted due to the unrecovery of the bearer when the network is abnormal.

In view of this, the present application provides a method, device, core network element and storage medium for restoring bearer, aiming at solving the above-mentioned technical problems of the related art.

In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only Some embodiments of the present application are not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

FIG. 1 is a schematic diagram of an implementation environment involved in a method for restoring bearers. The implementation environment includes a wireless communication system 100, which may be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (Wideband) system Code Division Multiple Access (WCDMA) system, general packet radio service (GPRS) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division Duplex (time division duplex, TDD) system, long term evolution advanced (long term evolution advanced, LTE-A) system, universal mobile telecommunication system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, WiMAX) ) system, may also be a 5G New Radio (New Radio, NR) system, etc., which is not limited here.

The wireless communication system 100 includes a user equipment 110 and a network device. The network device may include an access network device 130 (eg, 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.

Specifically, the user equipment 110, abbreviated as UE (User Equipment), is also considered to be a terminal or terminal equipment, 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 a device connected to Other processing devices, etc. of the wireless modem, for example, the user equipment 110 may 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 devices. In different systems, the user equipment 110 may have different names, and may be a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiated Protocol (SIP) phone, a wireless local loop (Wireless LocalLoop, WLL) station, personal digital assistant (Personal Digital Assistant, PDA) and other devices. The user equipment 110 may also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile, remote station, access point ), a remote terminal, an access terminal, a user terminal, a user agent, and a user device, which are not limited here.

The access network device 130, taking a base station as an example, may be called an access point according to different specific applications, or may be an electronic device in the access network that communicates with the user equipment 110 through one or more sectors on the air interface , or another name. 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 the Internet Protocol network. Base station 130 may also coordinate attribute management for the air interface. For example, the base station 130 may be a base transceiver station (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a bandwidth A base station (NodeB) in a code division multiple access (Wide-band Code Division Multiple Access, WCDMA), may also be an evolved network device (evolutional Node B, eNB or e) in a long term evolution (long term evolution, LTE) system -NodeB), 5G base station (gNB) in 5G network architecture (next generation system), it can also be Home evolved Node B (HeNB), relay node (relay node), home base station (femto), pico The base station (pico) and the like are not limited here.

After an RRC (Radio Resource Control, Radio Resource Control) connection is established between the user equipment 110 and the base station 130, the base station 130 can send a radio bearer establishment message to the user equipment 110 based on the RRC connection, thereby enabling the user equipment 110 to set up a radio bearer based on the RRC connection. The bearer establishment message completes the establishment of the radio bearer with the base station 130 , so that the user equipment 110 can perform uplink and downlink service transmission with the base station 130 based on the currently established radio bearer.

Referring to FIG. 2 , an embodiment of the present application provides a method for restoring a bearer, and the method is executed by a core network element. For example, the core network element is an AMF.

As shown in Figure 2, the method may include the following steps:

Step 21: Receive the initial UE message sent by the base station, and determine the UE context according to the NAS message in the initial UE message.

First of all, the initial UE message is used to notify the core network that the UE requests to register.

For the UE, when attaching to a base station for the first time, or re-attaching to another base station as the UE moves, or the wireless link between the UE and the core network needs to be restored, a registration process will be initiated to the core network.

In order to initiate a registration process to the core network, the UE first initiates a registration request or a service request to the base station, specifically: sends a registration message or a service request message to the base station.

Correspondingly, after receiving the registration message or the service request message sent by the UE, the base station will send the initial UE message carrying the registration message or the service request message to the core network, so that the core network knows the UE according to the received initial UE message. Request to register.

Based on this, in a possible implementation manner, the NAS message in the initial UE message includes a registration message. In a possible implementation, the NAS message in the initial UE message includes a service request message.

As mentioned above, when the network is normal, for the normal release of the wireless link, there is no problem of interruption of uplink and downlink services, but when the network is abnormal, the problem of interruption of downlink services may occur. Therefore, in this embodiment, after the NAS message is determined according to the initial UE message, the UE context is further determined according to the NAS message, so as to determine the connection state of the UE.

The connection state of the UE at least includes: a normal access state, an abnormal access state, and a non-access state. For example, when the wireless link between the UE and the core network is abnormally released, or when the NAS layer automatically disconnects the link due to enabling self-detection protection, the connection state of the UE can be regarded as an abnormal access state.

If the connection state of the UE is the normal access state or the non-connected state, indicating that there is no need to restore the radio link, the core network executes the relevant processing flow according to the processing flow described in the specified protocol specification.

On the contrary, if the connection state of the UE is in the 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, so that the radio link can be restored during the restoration process. Avoid disruption of downlink services.

It is worth mentioning that the UE context in the embodiments of the present application refers to the radio link established between the UE and the core network, so the connection state of the UE can be reflected through the UE context.

Combining different NAS messages, the process of determining the UE context is described as follows:

FIG. 3 exemplarily shows a schematic flowchart of determining the UE context based on the registration message. In a possible implementation manner, when the NAS message is a registration message, as shown in FIG. 3 , the process of determining the UE context may include the following steps:

Step 211, extracting the registration message from the initial UE message.

Step 212, if the registration message indicates that the UE is initially registered, create a UE context.

Step 213, if the registration message indicates that the UE is re-registering, obtain the UE context.

That is to say, the UE initiates the registration process through the registration message. If the registration process is considered to be the initial registration process of the UE, at this time, since the UE context about the UE is not stored in the core network, the core network will create a UE for the UE. context.

Conversely, if the registration process considers that the UE is re-registering, for example, re-attaching to another base station as the UE moves, the core network stores the UE context corresponding to the UE, and at this time, the core network can directly obtain the UE context.

FIG. 4 exemplarily shows a schematic flowchart of determining a UE context based on a service request message. In a possible implementation manner, when the NAS message is a service request message, as shown in FIG. 4 , the process of determining the UE context may include the following steps:

Step 214, extracting the service request message from the initial UE message.

Step 215, in response to the service request message, obtain the UE context.

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 UE context can be directly obtained if the UE context corresponding to the UE is stored in the core network.

Step 22, if the UE context indicates that the connection state of the UE is an abnormal access state, initiate a UE context release process to the base station.

As mentioned above, when the connection state of the UE is abnormal access state, it may be caused by the abnormal release of the radio link between the UE and the core network, or it may be caused by the automatic disconnection of the NAS layer due to the self-detection protection being turned on. . At this time, the core network will initiate the UE context release process to the base station.

FIG. 5 exemplarily shows a flowchart of the UE context release process. In a possible implementation manner, as shown in FIG. 5 , step 22 may include the following steps:

Step 221: Send a UE release message to the base station.

The UE release message is used to instruct the base station to release local resources but not notify the UE to release resources. The local resources include, but are not limited to: radio resources, storage resources and the like related to the UE in the base station.

In the above process, only the base station notifies the release of resources, but the UE does not notify the release of resources, which greatly facilitates the recovery of the user plane link in the process of radio link recovery, which further fully guarantees that the bearer can be recovered in time, thereby avoiding the The downlink service is interrupted because the bearer is not restored in time.

Further, continuing to refer to FIG. 5, in a possible implementation manner, step 22 may further include the following steps:

Step 222: Receive a release complete message sent by the base station.

The release complete message is used to indicate that the base station has completed the release of local resources according to the UE release message.

Thus, the completeness of the bearer recovery process is fully guaranteed.

Step 23, when the NAS message indicates that the session type of the UE is not the first type, execute the bearer recovery process.

The session type is used to indicate the session state of the session established between the UE and the core network.

As mentioned above, when the network is abnormal, if only the signaling plane link is restored but the user plane link is not restored, assuming that there is an old downlink service between the UE and the base station, the old downlink service will be caused due to the unreachable user plane. The service cannot be completed. Here, the inventor realizes that the related art only considers whether there are technical loopholes in the old uplink service between the UE and the base station. Therefore, the inventor designed to introduce whether to establish a bearer between the UE and the core network as whether to restore or not. The basis for the bearer between the UE and the core network, that is, if a bearer is established between the UE and the core network, it means that there may be old downlink services 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 a possible implementation manner, the session state at least includes: an uplink service state and a bearer state.

In a possible implementation manner, the uplink service state at least includes 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 the uplink service in the request state. It should be noted that the uplink service/downlink service in the request state involved in the embodiments of this 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 base station. Downlink traffic to be transmitted.

In a possible implementation manner, the bearer state at least includes an established state and an unestablished state. Among them, the established state means that a bearer has been established between the UE and the core network, indicating that there may be downlink services in the requested state between the UE and the base station; the unestablished state means that no bearer has been established between the UE and the core network, indicating that the UE There is no downlink service in the request state with the base station. It is explained here that a bearer was established between the UE and the core network, which means that a bearer was established between the UE and the core network before the abnormal release of the wireless link, and then interrupted due to the abnormal release of the wireless link, which can also be understood as: An abnormally interrupted bearer is established between the UE and the core network.

It still needs to be added that the services include uplink services and downlink services. Certainly, in other embodiments, the uplink service/downlink service may be further divided into uplink/downlink voice service and uplink/downlink data service, which are not limited here.

Based on this, in a possible implementation manner, the session types include at least a first type, a second type, and a third type. Among them, the first type is used to indicate that the UE does not have an uplink service in a request 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 request state; the third type is used to indicate that the UE has There is no uplink service in the request state but a bearer has been established with the core network.

Then, after determining that the session type of the UE is not the first type, the core network learns that the UE has an uplink service in the request state or that a bearer has been established between the UE and the core network (there may be a request state between the UE and the base station at this time). In order to avoid the interruption of the uplink and downlink services, the core network element performs the bearer recovery process, so as to ensure that the uplink and downlink services in the request state can continue to transmit on the recovered bearer.

Compared with the related art, on the one hand, if the UE has an uplink service in the request state, the same is true for the radio link recovery process when the network is normal, that is, when the UE re-initiates the registration process to restore the signaling plane link, it will pass The Uplink Data Status message is carried in the registration message or service request message to restore the user plane link and then restore the bearer.

On the other hand, if the UE does not have the uplink service in the request state, but has established a bearer with the core network, at this time, there may be downlink services in the request state between the UE and the base station, which is different from the wireless link when the network is abnormal. During the path restoration process, the UE will continue to restore the user plane link, and then restore the bearer, so as to avoid the downlink service interruption caused by the UE only restoring the signaling plane link when there is no uplink service.

Through the above process, combined with the connection state and session type of the UE, it is comprehensively judged whether the bearer between the UE and the core network needs to be restored, so as to ensure that there is an uplink service and/or downlink service in the request state between the UE and the base station, The bearer can be resumed in time to continue to transmit the uplink and downlink services, thereby effectively solving the problem of interruption of downlink services caused by the failure of the bearer to be restored when the network is abnormal in the related art.

Referring to FIG. 6 , an embodiment of the present application provides a method for resuming a bearer, and the method is performed by a core network element. For example, the core network element is an AMF.

As shown in Figure 6, the method may include the following steps:

Step 21: Receive the initial UE message sent by the base station, and determine the UE context according to the NAS message in the initial UE message.

Step 22, if the UE context indicates that the connection state of the UE is an abnormal access state, initiate a UE context release process to the base station.

Step 24: Determine the session type of the UE according to the uplink service status and bearer status of the UE indicated by the NAS message.

Wherein, the uplink service state is used to indicate whether the UE has an uplink service in a request state. The bearer state is used to indicate whether a bearer is established between the UE and the core network, and can also be considered to be used to indicate whether there is a downlink service in a request state between the UE and the base station. In a possible implementation manner, the uplink service state at least includes a request state and an idle state. In a possible implementation manner, the bearer state at least includes an established state and an unestablished state.

Combining the uplink service status and bearer status of the UE, the process of determining the session type of the UE is described as follows:

As shown in FIG. 7, in a possible implementation manner, step 24 may include the following steps:

Step 241: Determine whether the NAS message carries the first message.

The first message is used to indicate that the uplink service state of the UE is a request state.

In one possible implementation, the first message includes an Uplink Data Status message or any other suitable message.

If the NAS message carries the first message, it indicates that the uplink service state of the UE is the request state, and it can also be considered that the UE has the uplink service in the request state, and then step 242 is performed.

Otherwise, if the NAS message does not carry the first message, it means that the uplink service state of the UE is in the idle state, and it can also be considered that the UE does not have the uplink service in the request state, and further judges whether there is a bearer established between the UE and the core network, That is, step 243 is executed.

Step 242, determining that the session type of the UE is the second type.

Among them, the second type is used to indicate that the UE has an uplink service in a request state.

Step 243: Determine whether the NAS message carries the second message.

The second message is used to indicate that the bearer state of the UE is the establishment state.

In a possible implementation, the second message includes a PDU Session Status message or any other suitable message.

If the second message is carried in the NAS message, it means that the bearer state of the UE is in the established state. It can also be considered that the bearer has been established between the UE and the core network, which means that there may be downlink services in the request state between the UE and the base station. Step 244.

Otherwise, if the NAS message does not carry the second message, it means that the bearer state of the UE is in the unestablished state. It can also be considered that the bearer is not established between the UE and the core network, which means that there is no downlink in the request state between the UE and the base station. service, step 245 is executed.

It is worth mentioning that it is not limited to the above-mentioned NAS message optionally carrying the first message/second message to indicate the uplink service status/bearer status of the UE. Carrying the first message/second message to indicate the uplink service state/bearer state of the UE does not constitute a specific limitation here.

Step 244, determining that the session type of the UE is the third type.

The third type is used to indicate that the UE does not have an uplink service in a request state but a bearer has been established between the UE and the core network.

In order to ensure the necessity of carrying out the bearer recovery process, in a possible implementation manner, step 244 may further include the following steps:

Get the local context and determine the local bearer status based on the local context.

The local context is the UE context stored in the core network. Correspondingly, the local bearer status refers to the bearer status of the UE stored in the core network. The local bearer state at least includes 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 no bearer has been established between the UE and the core network.

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, it indicates that both the UE and the core network have established a bearer. Both determine that a bearer is established between the two before the radio link is abnormally released, then determine that the session type of the UE is the third type, in this way, to avoid whether a bearer is established between the UE and the core network before the radio link is abnormally released. Therefore, it effectively guarantees the necessity of carrying out the bearer recovery process.

Step 245, determining that the session type of the UE is the first type.

It can be seen from the above that when it is determined that the session type of the UE is the first type, it means that the UE has neither an uplink service in the request state nor a bearer established with the core network (and there may be no downlink service in the request state) , at this time, the core network element does not need to perform the bearer recovery process, and only needs to execute the related processing flow according to the processing flow described in the specified protocol specification.

Correspondingly, when it is determined that the session type of the UE is the second type or the third type, it means that the UE has an uplink service in the request state, or a bearer has been established between the UE and the core network (there may be a request between the UE and the base station). state downlink service), then, the core network element needs to perform the bearer recovery process, that is, step 23 is performed.

Step 23, when the NAS message indicates that the session type of the UE is not the first type, execute the bearer recovery process.

In the above process, the UE's session type is determined by combining the UE's uplink service status and bearer status, which is used as one of the basis for judging whether the bearer between the UE and the core network needs to be restored, thereby avoiding the need for Technical vulnerability of wireless link recovery through Uplink Data Status message.

FIG. 8 exemplarily shows a flow chart of a method for restoring bearers performed by the AMF. A method for restoring a bearer provided by an embodiment of the present application will now be described as follows with reference to FIG. 8 :

As shown in Figure 8, the method may include the following steps:

Step 401, after receiving the initial UE message, the AMF determines the NAS message in the initial UE message.

Wherein, the NAS message includes at least: a registration message and a service request message.

Step 402: Determine the UE context according to the NAS message.

Specifically, on the one hand, when the NAS message is a registration message, if the registration message indicates that the UE is initially registered, the UE context is created; otherwise, when the registration message indicates that the UE is re-registering, the UE context is obtained.

On the other hand, when the NAS message is a service request message, the UE context is obtained in response to the service request message.

Step 403, the AMF determines whether the connection state of the UE is an abnormal access state.

Specifically, if the connection state of the UE is the normal access state or the non-access state, the AMF executes the relevant processing flow according to the processing flow described in the specified protocol specification.

On the contrary, if the connection state of the UE is an abnormal access state, step 404 is performed.

Step 404, initiate a UE context release process to the base station.

Specifically, the AMF sends the UE release message to the base station. Correspondingly, after receiving the UE release message, the base station releases only local resources and does not notify the UE to release resources according to the instructions of the UE release message.

After the base station completes the release of local resources, step 405 is executed.

Step 405, the AMF determines whether the NAS message carries the Uplink Data Status message.

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, that is, step 407 is performed.

On the contrary, if the NAS message does not carry the Uplink Data Status message, it means that the UE does not have the uplink service in the request state, then step 406 is performed.

Step 406, the AMF determines whether the NAS message carries the PDU Session Status message.

Specifically, if the NAS message carries the PDU Session Status message, indicating that a bearer has been established between the UE and the core network, it can also be understood that there may be downlink services in the request state between the UE and the base station, and it is determined that the bearer needs to be restored, That is, step 407 is executed.

Conversely, if the NAS message does not carry the PDU Session Status message, it means that the bearer is not established between the UE and the core network, that is, there is no downlink service in the request state between the UE and the base station, then it is determined that the bearer does not need to be restored. At this time, the AMF executes the relevant processing flow following the processing flow described in the specified protocol specification.

Step 407, the bearer recovery process is performed.

In this way, the bearer recovery between the UE and the core network when the network is abnormal is realized through AMF, which fully guarantees that the uplink service and/or downlink service in the request state between the UE and the base station can continue to be transmitted depending on the restored bearer , thereby effectively solving the problem of downlink service interruption due to unrecovery of the bearer when the network is abnormal in the related art.

Referring to FIG. 9 , an embodiment of the present application provides a method for restoring a bearer, and the method is applicable to the wireless communication system 100 in the implementation environment shown in FIG. 1 .

In this embodiment, the wireless communication system at least includes: user equipment UE (ie terminal), access network equipment RAN (ie base station), core network network elements AMF and SMF.

As shown in Figure 9, the method may include the following steps:

Step 501, the UE sends a registration message to the RAN.

Step 502, after receiving the registration message, the RAN sends an initial UE message carrying the registration message to the AMF.

Step 503, after receiving the initial UE message, the AMF initiates an authentication security process to the UE.

It is explained here that the purpose of the authentication security process is to check whether the UE has the right to use the relevant resources of the core network.

Step 504, when the authentication of the UE succeeds, the AMF determines whether the connection state of the UE is an abnormal access state.

Specifically, if the registration message indicates that the UE is initially registered, the UE context is created; if the registration message indicates that the UE is re-registering, the UE context is obtained, and the UE context is determined in this way, and then the connection state of the UE is determined according to the UE context.

If the connection state of the UE is the normal access state or the non-access state, the AMF executes the relevant processing flow according to the processing flow described in the specified protocol specification.

On the contrary, if the connection state of the UE is the abnormal access state, step 505 is performed.

Further, in order to ensure the necessity of carrying out the bearer recovery process, the process of determining the connection state of the UE may include the following steps:

Acquire the local context, and determine the local connection state of the UE according to the local context.

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 at least includes: a normal access state, an abnormal access state and a non-access state.

Based on this, if the local connection state of the UE indicates that the connection state of the UE is a normal access state, and the connection state of the UE determined by the UE context is an abnormal access state, it means that the wireless link between the UE and the core network is For abnormal release, it is determined that the connection state of the UE is in the abnormal access state, and then step 505 is performed, in this way, a misjudgment of whether the connection state of the UE is in the abnormal access state is avoided, thereby effectively ensuring the execution of the bearer recovery process. necessity.

Step 505, initiate a UE context release process to the RAN.

Specifically, the AMF sends the UE release message to the RAN. Correspondingly, after receiving the UE release message, the RAN releases only local resources and does not notify the UE to release the resources according to the instructions of the UE release message.

After the RAN completes the local resource release, step 506 is executed.

Step 506: Send a release complete message to the AMF to notify the AMF that the RAN has completed the release of the local resources.

Step 507, the AMF determines whether to resume the bearer by combining the Uplink Data Status message and the PDU Session Status message.

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, that is, step 508 is performed.

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 the 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.

Here, in order to ensure the accuracy of the bearer restoration determination process, after it is determined that the PDUSession Status message is carried in the registration message, the local bearer status indicated by the local context can be further combined to jointly determine whether the bearer needs to be restored. A misjudgment of whether a bearer is established between the UE and the core network before the radio link is abnormally released, thereby effectively ensuring the necessity of carrying out the bearer recovery process.

If the registration message does not carry either the Uplink Data Status message nor the PDU SessionStatus message, it means that the UE does not have the uplink service in the requested state and the bearer has not been established with the core network, and it is determined that the bearer does not need to be restored. At this time, the AMF executes the relevant processing flow following the processing flow described in the specified protocol specification.

Step 508, the bearer recovery process is performed.

Specifically, it includes the following steps: Step 5081, the AMF initiates a bearer update request to the SMF, so that the SMF can perform session management on the subsequently restored session bearer; Step 5082, the SMF returns a bearer update response message to the AMF; Step 5083, follow the specified protocol specification The described bearer recovery procedure executes the relevant processing flow.

Thereby, the recovery of the bearer is realized, so that the uplink service and/or the downlink service in the request state existing between the UE and the RAN can continue to be transmitted depending on the recovered bearer.

In the above process, the wireless link is restored through the registration message when the network is abnormal, and then the bearer is restored, which fully ensures that the uplink and downlink services in the request state between the UE and the base station can continue to be transmitted, thus effectively solving the problem. In the related art, the downlink service is interrupted because the bearer is not restored when the network is abnormal.

Referring to FIG. 10 , an embodiment of the present application provides a method for restoring a bearer, and the method is applicable to the wireless communication system 100 in the implementation environment shown in FIG. 1 .

In this embodiment, the wireless communication system at least includes: user equipment UE (ie terminal), access network equipment RAN (ie base station), core network network elements AMF and SMF.

As shown in Figure 10, the method may include the following steps:

Step 601, the UE sends a service request message to the RAN.

Step 602, after receiving the service request message, the RAN sends an initial UE message carrying the service request message to the AMF.

Step 603, after receiving the initial UE message, the AMF initiates an authentication security process to the UE.

It is explained here that the purpose of the authentication security process is to check whether the UE has the right to use the radio resources related to the core network.

Step 604, when the UE is authenticated successfully, the AMF determines whether the connection state of the UE is an abnormal access state.

Specifically, the UE context is obtained 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.

If the connection state of the UE is the normal access state or the non-access state, the AMF executes the relevant processing flow according to the processing flow described in the specified protocol specification.

On the contrary, if the connection state of the UE is the abnormal access state, step 605 is performed.

Further, in order to ensure the necessity of carrying out the bearer recovery process, the process of determining the connection state of the UE may include the following steps:

Acquire the local context, and determine the local connection state of the UE according to the local context.

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.

Based on this, if the local connection state of the UE indicates that the connection state of the UE is a normal access state, and the connection state of the UE determined by the UE context is an abnormal access state, it means that the wireless link between the UE and the core network is For abnormal release, it is determined that the connection state of the UE is the abnormal access state, and then step 605 is performed.

Step 605, initiate a UE context release process to the RAN.

Specifically, the AMF sends the UE release message to the RAN. Correspondingly, after receiving the UE release message, the RAN releases only local resources and does not notify the UE to release the resources according to the instructions of the UE release message.

After the RAN completes the local resource release, step 606 is executed.

Step 606: Send a release complete message to the AMF to notify the AMF that the RAN has completed the release of the local resources.

Step 607, the AMF combines the Uplink Data Status message and the PDU Session Status message to determine whether to resume the bearer.

If the service request 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, that is, step 508 is performed.

If the service request message does not carry the Uplink Data Status message but carries the PDU SessionStatus message, it means that the UE does not have the uplink service in the requested state but has established a bearer with the core network, it is determined that the bearer needs to be restored, and step 508 is executed.

Here, in order to ensure the accuracy of the bearer restoration determination process, after it is determined that the PDUSession Status message is carried in the service request message, the local bearer status indicated by the local context can be further combined to jointly determine whether the bearer needs to be restored. In this way It avoids a misjudgment as to whether a bearer is established between the UE and the core network before the radio link is abnormally released, thereby effectively ensuring the necessity of carrying out the bearer recovery process.

If neither the Uplink Data Status nor the PDU SessionStatus message is carried in the service request message, it means that the UE does not have the uplink service in the request state and the bearer has not been established with the core network, and it is determined that the bearer does not need to be restored. At this time, the AMF executes the relevant processing flow following the processing flow described in the specified protocol specification.

Step 608, the bearer recovery process is performed.

Specifically, it includes the following steps: Step 6081, the AMF initiates a bearer update request to the SMF, so that the SMF can perform session management on the subsequently restored session bearer; Step 6082, the SMF returns a bearer update response message to the AMF; Step 6083, follow the specified protocol specification The described bearer recovery procedure executes the relevant processing flow.

Thereby, the recovery of the bearer is realized, so that the uplink service and/or the downlink service in the request state existing between the UE and the RAN can continue to be transmitted depending on the recovered bearer.

In the above process, the wireless link is restored through the service request message when the network is abnormal, and the bearer is restored, which fully guarantees that the uplink and downlink services in the request state between the UE and the base station can continue to be transmitted, thereby effectively solving the problem. The problem that the downlink service is interrupted due to the unrecovery of the bearer when the network is abnormal in the related art is solved.

The following are device embodiments of the present application, which can be used to execute the bearer recovery method involved in the present application. For details not disclosed in the device embodiments of the present application, please refer to the embodiments of the bearer restoration method involved in the present application.

Referring to FIG. 11 , an embodiment of the present application provides an apparatus 900 for restoring a bearer, which is applied to a core network element.

The apparatus 900 for restoring a bearer includes but is not limited to: a message receiving module 901 , a release initiating module 902 and a bearer restoring module 903 .

The message receiving module 901 is configured to receive the initial user equipment UE message sent by the base station, and determine the UE context according to the non-access stratum NAS message in the initial UE message.

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.

The bearer recovery module 903 is configured to execute the bearer recovery process when the NAS message indicates that the session type of the UE is not the first type, and the first type is used to indicate that the UE does not have an uplink service in a request state and there is no connection between the UE and the core network. Create a bearer.

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, and other division methods may be used in actual implementation. In addition, each functional unit and/or module in each embodiment of the present application may be integrated into one processing unit and/or module, or each unit and/or module may exist physically alone, or two or more Units and/or modules are integrated in one unit and/or module. The above-mentioned integrated units and/or modules may be implemented in the form of hardware, or may be implemented in the form of software functional units and/or modules.

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 may be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the related technology, or all or part of the technical solution, and the computer software product is stored in a storage medium, Several instructions are included to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments 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), magnetic disk or optical disk and other media that can store program codes.

In addition, the apparatus for restoring a bearer and the method for restoring a bearer provided by the above-mentioned embodiments are conceived based on the same application. Since the principle of solving the problem of the method and the apparatus is similar, the implementation of the apparatus and the method can be referred to each other, and the repetition will not be repeated. .

Therefore, it is comprehensively judged whether the bearer between the UE and the core network needs to be restored in combination with the connection status and session type of the UE, 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 The bearer is restored in a timely manner to continue transmitting the uplink and downlink services, thereby effectively solving the problem in the related art that the downlink service is interrupted because the bearer is not restored when the network is abnormal.

Fig. 12 shows a structural block diagram of a core network network element according to an exemplary embodiment. For example, the core network element is an AMF.

As shown in FIG. 12 , the core network element 1100 at least includes: a processor 1110 , a memory 1120 and a transceiver 1130 .

The transceiver 1130 is used for receiving and transmitting data under the control of the processor 1110 .

In FIG. 12 , the bus architecture may include any number of interconnected buses and bridges, in particular one or more processors represented by processor 1110 and various circuits of memory represented by memory 1120 linked together. 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 therefore will not be described further herein. The bus interface provides the interface. Transceiver 1130 may be a number of elements, including transmitters and receivers, providing units and/or modules for communicating with various other devices over transmission media including wireless channels, wired channels, fiber optic cables, etc. medium.

The processor 1110 is responsible for managing the bus architecture and general processing, and the memory 1120 may store data used by the processor 1110 in performing operations.

Optionally, the processor 1110 may be a central processor (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (Complex Programmable Logic). Device, CPLD), the processor 1110 may also adopt a multi-core architecture. The processor 1110 and the memory 1120 may also be arranged physically separately.

The processor 1110 invokes the computer program stored in the memory 1120 to execute any one of the bearer recovery methods provided by the foregoing embodiments of the present application according to the obtained executable instructions.

Specifically, the processor 1110 is configured to perform the following steps: receive the initial user equipment UE message sent by the base station, and determine the UE context according to the non-access stratum NAS message in the initial UE message; if the UE context indicates that the connection state of the UE is abnormal In the access state, the UE context release process is initiated to the base station; when the NAS message indicates that the session type of the UE is not the first type, the bearer recovery process is performed. The first type is used to indicate that the UE does not have uplink services in the request state and the UE No bearer is established with the core network.

In one possible implementation, the NAS message includes a registration message.

In a possible implementation manner, the processor is further configured to perform the following steps: extracting a registration message from the initial UE message; creating a UE context if the registration message indicates that the UE is initially registered; otherwise, acquiring the UE context.

In one possible implementation, the NAS message includes a service request message.

In a possible implementation manner, the processor is further configured to perform the following steps: extracting the service request message from the initial UE message; and acquiring the UE context in response to the service request message.

In a possible implementation manner, the processor is further configured to perform the following steps: initiate an authentication security process to the UE; when the UE authentication succeeds, determine whether the connection state of the UE is an abnormal access state according to the UE context.

In a possible implementation manner, the processor is further configured 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, then It is determined that the connection state of the UE is an abnormal access state.

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 not notify the UE to release resources.

In a possible implementation manner, the processor is further configured to perform the following steps: receiving a release complete message sent by the base station, where the release complete message is used to indicate that the base station has completed the release of local resources according to the UE release message.

In a possible implementation manner, the processor is further configured to perform the following step: determine the session type of the UE according to the uplink service status and bearer status of the UE indicated by the NAS message.

In a possible implementation manner, the processor is further configured to perform the following steps: determine whether the NAS message carries a first message, and the first message is used to indicate that the uplink service state of the UE is a request state; if not, determine whether the NAS message contains a first message. Whether to carry the second message, the second message is used to indicate that the bearer state of the UE is the establishment state; if not, it is determined that the session type of the UE is the first type.

In a possible implementation manner, the processor is further configured to perform the following steps: if the NAS message carries the first message, determine that the session type of the UE is the second type, and the second type is used to indicate that the UE exists in the request state Upstream business.

In a possible implementation manner, the processor is further configured to perform the following steps: if the NAS message does not carry the first message but carries the second message, determine that the session type of the UE is the third type, and the third type is used to indicate The UE has no uplink service in the request state but has established a bearer with the core network.

In a possible implementation manner, the processor is further configured to perform the following steps: obtain a local context, and determine 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, determine the session of the UE Type is the third type.

In a possible implementation manner, the first message includes an Uplink Data Status message.

In a possible implementation, the second message includes a Protocol Data Unit Session Status PDU SessionStatus message.

In a possible implementation, the core network element includes an access and mobility management function AMF.

In a possible implementation manner, the processor is further configured to perform the following step: the AMF initiates a bearer update request to the session management function SMF, so that the SMF performs session management on the restored session bearer.

It should be noted here that the above-mentioned device provided by the embodiment of the present application can realize all the method steps realized by the above-mentioned method embodiment, and can achieve the same technical effect, and the same as the method embodiment in this embodiment is not repeated here. The parts and beneficial effects will be described in detail.

In addition, an embodiment of the present application provides a storage medium, where a computer program is stored on the storage medium, and when the computer program is executed by a processor, the method for restoring a bearer in each of the foregoing embodiments is implemented. The storage medium can be any available medium or data storage device that can be accessed by the processor, including, but not limited to, magnetic storage (eg, floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (eg, CD, DVD, BD, etc.) , HVD, etc.), and semiconductor memory (eg, ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state disk (SSD)), etc.

An embodiment of the present application provides a program product, 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 instruction from the storage medium, so that when the executable instruction is executed by the processor, the method for restoring a bearer in the foregoing embodiments is implemented.

Compared with the related art, it realizes the recovery of the bearer when the network is abnormal. On the one hand, if the UE has the uplink service in the request state, it is the same as the wireless link recovery process when the network is normal, that is, the UE re-initiates the registration process to recover. When the signaling plane link is used, the user plane link will be restored by carrying the Uplink Data Status message in the registration message or the service request message, and then the bearer will be restored. On the other hand, if the UE does not have the uplink service in the request state, but has established a bearer with the core network, at this time, there may be downlink services in the request state between the UE and the base station, which is different from the wireless link when the network is abnormal. During the path restoration process, the UE will continue to restore the user plane link, and then restore the bearer to avoid the downlink service interruption caused by the UE only recovering the signaling plane link when there is no uplink service, thereby avoiding partial data loss, effectively improving User perception.

As will be appreciated by those skilled in the art, the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media having computer-usable program code embodied therein, including but not limited to disk storage, optical storage, and the like.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowcharts and/or block diagrams, and combinations of flows and/or blocks in the flowcharts and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These processor-executable instructions may also be stored in a processor-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the processor-readable memory result in the manufacture of means including the instructions product, the instruction means implements the functions specified in the flow or flow of the flowchart and/or the block or blocks of the block diagram.

These processor-executable instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process that Execution of the instructions provides steps for implementing the functions specified in the flowchart or blocks and/or the block or blocks of the block diagrams.

It should be understood that although the various steps in the flowchart of the accompanying drawings are sequentially shown in the order indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order and may be performed 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 may be executed at different times, and the execution sequence is also It does not have to be performed sequentially, but may be performed alternately or alternately with other steps or at least a portion of sub-steps or stages of other steps.

The above are only part of the embodiments of the present application. It should be pointed out that for those skilled in the art, without departing from the principles of the present application, several improvements and modifications can also be made. It should be regarded as the protection scope of this application.

Claims (18)

1. A method for bearer recovery, performed by a core network element, the method comprising:

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 a base station;

and when the NAS message indicates that the session type of the UE is not a first type, executing a bearer recovery process, wherein the first type is used for indicating that the UE does not have uplink service in a request state and no bearer is established between the UE and a core network.

2. The method of claim 1, wherein the NAS message comprises a registration message;

the determining a 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 registered, creating the UE context; otherwise, obtaining the UE context.

3. The method of claim 1, wherein the NAS message comprises 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;

and responding to the service request message, and acquiring the UE context.

4. The method of claim 1, wherein before initiating a UE context release procedure to a base station if the UE context indicates that the connection status of the UE is an abnormal access status, the method further comprises:

initiating an authentication security procedure to the UE;

and when the UE authentication is successful, determining whether the connection state of the UE is an abnormal access state according to the UE context.

5. The method of claim 4, wherein the determining whether the connection state of the UE is an abnormal access state according to the UE context comprises:

acquiring a local context;

and 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 the abnormal access state.

6. The method of claim 1, wherein the initiating a UE context release procedure to a base station comprises:

and sending a UE release message to the base station, wherein the UE release message is used for indicating the base station to release the local resources but not informing the UE of releasing the resources.

7. The method of claim 6, wherein the initiating the UE context release procedure to the base station further comprises:

and receiving a release completion message sent by the base station, wherein the release completion message is used for indicating that the base station has completed the release of the local resources according to the UE release message.

8. The method of claim 1, wherein before performing the bearer recovery procedure when the NAS message indicates that the session type of the UE is not the first type, the method further comprises:

and determining the session type of the UE according to the uplink service state and the bearing state of the UE indicated by the NAS message.

9. The method of claim 8, wherein the determining the session type of the UE according to the uplink traffic state and the bearer state of the UE indicated by the NAS message comprises:

determining whether the NAS message carries a first message, wherein the first message is used for indicating that the uplink service state of the UE is a request state;

if not, determining whether the NAS message carries a second message or not, wherein the second message is used for indicating that the bearing state of the UE is an establishment state;

and if not, determining the session type of the UE as the first type.

10. The method of claim 9, wherein the determining a session type of the UE according to the uplink traffic status and the bearer status of the UE indicated by the NAS message further comprises:

and if the NAS message carries the first message, determining that the session type of the UE is a second type, wherein the second type is used for indicating that the UE has the uplink service in the request state.

11. The method of claim 9, wherein the determining the session type of the UE according to the uplink traffic state and the bearer state of the UE indicated by the NAS message further comprises:

and if the NAS message does not carry the first message but carries the second message, determining that the session type of the UE is a third type, wherein the third type is used for indicating that the UE does not have the uplink service in the request state but establishes a bearer with a core network once.

12. The method of claim 11, wherein the determining that the session type of the UE is of a third type comprises:

acquiring a local context, and determining a local bearing state according to the local context;

and 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.

13. The method of claim 9, wherein the first message comprises an upstream Data Status message.

14. The method of claim 9, wherein the second message comprises a protocol data unit Session Status PDU Session Status message.

15. The method according to any of claims 1 to 14, wherein said core network element comprises an access and mobility management function, AMF;

after the performing the bearer recovery procedure when the NAS message indicates that the session type of the UE is not the first type, the method further includes:

and the AMF initiates a bearer update request to a Session Management Function (SMF) so that the SMF performs session management on the recovered session bearer.

16. A core network element, comprising: a memory, a transceiver, and a processor;

wherein the memory is used for storing a computer program; the transceiver is used for transceiving data under the control of the processor; the processor for reading a computer program in the memory to implement the method of recovering a bearer of any of claims 1 to 15.

17. An apparatus for recovering a bearer, applied to a network element of a core network, the apparatus comprising:

the device comprises a message receiving module, a message sending module and a message sending module, wherein the message receiving module is used for 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;

a release initiating module, configured to initiate a UE context release process to a base station if the UE context indicates that a connection state of the UE is an abnormal access state;

and a bearer recovery module, configured to execute a bearer recovery procedure when the NAS message indicates that the session type of the UE is not a first type, where the first type is used to indicate that the UE does not have the uplink service in the request state and no bearer is established between the UE and the core network.

18. A storage medium having stored thereon a computer program, characterized in that the computer program, when being executed by a processor, implements the method of restoring a bearer according to any one of claims 1 to 15.

Images