CN106921988B

CN106921988B - Method for processing ERAB management process in S1 switching process

Info

Publication number: CN106921988B
Application number: CN201510983114.7A
Authority: CN
Inventors: 门曼
Original assignee: Beijing Xinyouda Video Technology Co ltd; Beijing Xinwei Telecom Technology Inc
Current assignee: Beijing Xinyouda Video Technology Co ltd; Beijing Xinwei Telecom Technology Inc
Priority date: 2015-12-24
Filing date: 2015-12-24
Publication date: 2020-04-24
Anticipated expiration: 2035-12-24
Also published as: CN106921988A

Abstract

The invention provides a method for processing an ERAB management process in an S1 switching process, which comprises the following steps: and after the switching process of S1 is finished, the base station at one side reserved with the UE instance processes the ERAB management request message. The invention completely processes the S1 switching process and the ERAB management process, and can ensure that the two processes are not abnormally ended due to flow intersection.

Description

Method for processing ERAB management process in S1 switching process

Technical Field

The invention relates to the field of wireless communication, in particular to a method for processing an ERAB management process in an S1 switching process.

Background

According to the provisions of the standard protocol, if the core network triggers the ERAB management process in the S1 handover preparation process, the core network sends an ERAB management REQUEST (E-RAB SETUP REQUEST/E-RAB MODIFY REQUEST/E-RAB release REQUEST) message to the source side base station, and the source side base station can select two ways to process after receiving the message: (1) sending a HANDOVER CANCEL (HANDOVER CANCEL) message to a core network, canceling the HANDOVER process, and then processing an ERAB management request message; (2) and sending an ERAB management RESPONSE message (E-RAB SETUP RESPONSE/E-RAB MODIFYRESPONSE/E-RAB RELEASE RESPONSE) carrying the corresponding failure reason to the MME, and ending the ERAB management process. This approach inevitably leads to an abnormal termination of either the S1 handover procedure or the ERAB management procedure.

Disclosure of Invention

The invention aims to provide a method for processing a triggered ERAB management process in an S1 switching process so as to ensure that the two processes are not abnormally ended due to flow intersection. The method comprises the following steps:

and after the switching process of S1 is finished, the base station at one side reserved with the UE instance processes the ERAB management request message.

Preferably, after the ERAB management request message is generated by the core network, the request message is sent to the target base station after the target base station successfully establishes the link with the UE of the core network.

Preferably, if the S1 handover process is successfully completed, the target base station processes the ERAB management request message, and the core network processes the subsequent flow of the ERAB management process when the UE instance is in a stable state; if the switching process of S1 is cancelled, the source side base station processes the ERAB management request message, and the core network processes the subsequent flow of the ERAB management process when the UE instance is in a stable state; if the abnormal switching of S1 results in the release of both UE-related links of the base stations on both sides, the subsequent ERAB management process is not processed.

The invention completely processes the S1 switching process and the ERAB management process, considers various conditions after the switching process is finished, and avoids the problem that the ERAB management process can not be executed correctly due to UE instance migration caused by S1 switching.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.

Fig. 1 is a process flow diagram for an ERAB management process according to a first embodiment of the present invention;

FIG. 2 is a process flow diagram for the ERAB management process in accordance with a second embodiment of the invention;

fig. 3 is a flowchart of processing for the ERAB management process according to a third embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some embodiments of the present invention, but not all embodiments; it should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The basic idea of the invention is: when the core network needs to trigger the ERAB management process in the S1 switching process, an ERAB management REQUEST message (E-RAB SETUP REQUEST/E-RAB MODIFYREQUEST/E-RAB RELEASE COMMAND) is sent to both the source side base station and the target side base station, the received message is cached by the two side base stations, and after the S1 switching process is finished, the one side base station which retains the UE instance processes the ERAB management REQUEST message and returns a response to the core network, so that the problem that the two processes are abnormally finished due to flow intersection can be solved.

When the S1 handover procedure has different handover results, the processing of the ERAB management procedure by each network element will also be different. The following three embodiments will respectively describe the processing steps of the ERAB management procedure for different S1 switching results.

Example one

In this embodiment, the ERAB management process is triggered in the S1 handover process, and after the S1 handover is successfully completed, the ERAB management process is completed by the handover target base station. The specific processing steps are shown in fig. 1:

(1) the core network side UE instance is in S1 switching state, at this time, an ERAB management process is required to be triggered due to the request of the terminal side, the core network firstly generates an ERAB management request message and sends the ERAB management request message to the switching source side base station, and meanwhile, the ERAB management request message is sent to the target side base station after the target side base station and the UE related link of the core network are successfully established.

(2) The switching source side base station UE instance is in S1 switching state, at this time, the source side base station temporarily caches the information after receiving the ERAB management request information; the UE instance of the handover target base station is in the S1 handover state, and when receiving the ERAB management request message, the target base station temporarily buffers the message.

(3) And S1, the switching process is successfully finished, the UE related link of the core network and the source side base station is released, and the source side base station does not need to process the subsequent ERAB management process.

(4) And the UE instance of the target side base station returns to a stable state, the ERAB management process is completed by the target side base station, and the target side processes the previously received ERAB management request message at the beginning of the stable state and returns a response to the core network.

(5) The core network handles the subsequent flow of the ERAB management procedure when the UE instance is in a stable state.

Example two

In this embodiment, the ERAB management process is triggered in the S1 handover process, and after the S1 handover is cancelled, the ERAB management process is completed by the handover source side base station. The specific processing steps are shown in fig. 2:

(3) The S1 handover process is cancelled by the source side base station, the UE-related link between the core network and the target side base station is released, and the target side base station does not need to process the subsequent ERAB management process.

(4) And the UE instance of the source side base station returns to a stable state, the ERAB management process is completed by the source side base station, and the source side base station processes the previously received ERAB management request message and returns a response to the core network when the stable state starts.

EXAMPLE III

In this embodiment, an ERAB management process is triggered in the S1 handover process, and after the UE-related links of the base stations on both sides are released due to the S1 handover exception, the subsequent ERAB management process is not processed any more. The specific processing steps are shown in fig. 3:

(3) S1 switching abnormity causes the UE related links of the base stations on both sides to be released, and the core network, the source side base station and the target side base station do not need to process the subsequent ERAB management process.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

The method for processing the ERAB management process in the S1 switching process is characterized by comprising the following steps:

and after the switching process of S1 is finished, the base station at one side reserved with the UE instance processes the ERAB management request message.
2. The method of claim 1, wherein:

after the core network generates the ERAB management request message, the ERAB management request message is sent to the target side base station after the target side base station and the UE related link of the core network are successfully established.
3. The method of claim 2, wherein:

if the S1 switching process is successfully finished, the target side base station processes the ERAB management request message, and the core network processes the subsequent flow of the ERAB management process when the UE instance is in a stable state;

if the switching process of S1 is cancelled, the source side base station processes the ERAB management request message, and the core network processes the subsequent flow of the ERAB management process when the UE instance is in a stable state;

if the abnormal switching of S1 results in the release of both UE-related links of the base stations on both sides, the subsequent ERAB management process is not processed.