CN108924893B - Bearer release method, bearer release device, MME and SAE-GW - Google Patents
Bearer release method, bearer release device, MME and SAE-GW Download PDFInfo
- Publication number
- CN108924893B CN108924893B CN201710282999.7A CN201710282999A CN108924893B CN 108924893 B CN108924893 B CN 108924893B CN 201710282999 A CN201710282999 A CN 201710282999A CN 108924893 B CN108924893 B CN 108924893B
- Authority
- CN
- China
- Prior art keywords
- release
- bearer
- base station
- request
- sae
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
Abstract
The invention provides a method and a device for releasing a bearer, a Mobility Management Entity (MME) and a user plane functional entity gateway (SAE-GW), wherein the method for releasing the bearer comprises the following steps: when receiving a switching request sent by a source base station, judging whether a bearer release request which is sent by a user plane functional entity gateway SAE-GW and carries a release initiation reason value is received or not before the switching request is received; if yes, sending a notification message for indicating the handover failure and a release instruction carried by S1 between the base station and the core network to the source base station. The scheme can avoid the situation that the terminal is meaningless repeatedly required to switch if the switching request is received after the release instruction is received, saves signaling overhead, and well solves the problems of extra signaling overhead and meaningless switching when the switching conflicts with the upper SIP release in the prior art.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a bearer release method and apparatus, a mobility management entity MME, and a user plane functional entity gateway SAE-GW.
Background
The conventional Voice service VoLTE srvcc (Enhanced Single Radio Voice Call Continuity) handover procedure is shown in fig. 1, and includes:
step 11: a VoLTE session is established between a terminal a and a terminal B, the terminal a is an SRVCC (Single Radio Voice Call Continuity) terminal, a Call signaling is anchored on an ATCF, and a media plane is anchored on an ATGW; an ATCF (Access Transfer Control function) and an ATGW (Access Transfer Gateway) as anchor points of the VoIP call on a Control plane and a user plane, respectively;
step 12: the terminal A measures the adjacent cells according to the indication of an eNB (E-UTRAN) and reports the measurement result;
step 13: the eNB decides to initiate eSRVCC handover and selects a target cell;
step 14: the eNB sends a Handover Required message to the MME, wherein the message carries a target cell ID (identity) and indicates that the Handover is SRVCC Handover through SRVCC HO Indication;
step 15: the MME judges that the switching is SRVCC switching according to SRVCC HO Indication, and separates out voice media stream (QCI is 1) in switching session for subsequent switching;
step 16: the MME selects an eMSC and sends an SRVCC packet switched PS to circuit switched CS Request to inform the eMSC to initiate circuit domain side resource reservation, and main parameters comprise international mobile subscriber identity IMSI, C-MSISDN (associated MSISDN), session transmission number STN-SR, Target Cell ID and Source to Target Transparent Container resource to Target Transparent Container;
step 17-110: the eMSC initiates a resource reservation flow of the circuit domain side, wherein the resource reservation flow comprises air interface resources and core network link resources;
step 111: the eMSC returns SRVCC PS to CS Response, informs the MME of a resource reservation result and carries a Target to Source transfer Container parameter;
step 11: if the resource reservation of the circuit domain side is finished, the MME sends a HANDOVER COMMAND message to the eNB, and the HANDOVER COMMAND message carries a Target to Source transfer Container parameter;
step 113: the eNB informs the terminal to switch from the LTE to a Target cell of a global system for mobile communication (GSM) according to the Target to Source transfer Container parameter;
step 114: the terminal air interface is switched to GSM;
step 115-117: after the terminal air interface is switched to GSM, the BSS sends HO Complete information to the target MSC, and informs the MME of finishing the switching after the eMSC;
step 118: MME initiates a bearer release process, deletes all GBR bearers on SAE GW, and suspends the default bearer;
step 119: MME initiates a wireless side bearer release process to release S1 interface and wireless resources;
step 120: eMSC sends SRVCC PS to CS Response message to trigger switch flow of access side, and sends SIP INVITE message to P-CSCF to trigger switch flow of conversation layer, the message carries STN-SR and C-MSISDN obtained from MME and SDP of MSC side;
step 121-122: the P-CSCF completes redirection of a media plane through interaction of the ATCF and the ATGW according to the SDP at the MSC side, and points media connection to the eMSC/MGW; simultaneously constructing a new INVITE message, setting the Request-URI AS the ATU-STI previously received from the registration message and pointing to the SCC AS;
step 123: the P-CSCF controls the ATGW to complete media plane redirection through the ATCF;
step 124-129: 200OK response and ACK;
step 130: after receiving the INVITE message, the SCC AS learns that SRVCC handover has occurred, associates the new signaling connection with the remote signaling connection through the C-MSISDN, and releases the original signaling connection through the BYE message;
step 131: after receiving the BYE message, the P-CSCF deletes the local signaling connection;
step 132-: after the release is finished and the switching is finished, the media plane is switched through the ATGW and the eMSC/MGW;
step 134-135: the eMSC initiates TMSI reallocation and replaces the user to perform circuit domain location update.
If the upper layer has already released the SIP message when the handover occurs, that is, the upper layer has already started sending the BYE message, then the network is triggered to release the SIP signaling connection, that is, release the NAS (non-access stratum) bearer, as shown in steps 28-210 in fig. 2, because the handover occurs at this time, as shown in fig. 1, the eNB sends a handover request to the MME (step 14), at this time, the MME ignores the bearer release request of step 28 and processes the handover request, so that the handover procedure is executed to require the UE to perform the handover execution step 113 and 114, and at this time, the UE considers that the SIP has not been connected last time and the handover is meaningless, so the handover is not performed, and the step 14 is repeatedly sent to require the UE to perform the handover, which may bring additional signaling overhead and unnecessary handover of the MME.
Disclosure of Invention
The invention aims to provide a bearer release method, a bearer release device, a Mobility Management Entity (MME) and a user plane functional entity gateway (SAE-GW), which solve the problems of extra signaling overhead and meaningless switching when the switching conflicts with the upper layer SIP release in the prior art.
In order to solve the foregoing technical problem, an embodiment of the present invention provides a bearer release method, which is applied to a mobility management entity MME, and includes:
when receiving a switching request sent by a source base station, judging whether a bearer release request which is sent by a user plane functional entity gateway SAE-GW and carries a release initiation reason value is received or not before the switching request is received;
if yes, sending a notification message for indicating the handover failure and a release instruction carried by S1 between the base station and the core network to the source base station.
Optionally, after the sending, to the source base station, the notification message for indicating the handover failure and the release instruction of the S1 bearer between the base station and the core network, the bearer release method further includes:
and sending a bearer release response message to the SAE-GW.
Optionally, the value of the initiation release reason includes a calling side hang-up or a called side hang-up.
The invention also provides a bearer release method, which is applied to the user plane functional entity gateway SAE-GW and comprises the following steps:
receiving a Random Access Response (RAR) message which is sent by a charging policy control unit (PCRF) and carries a release initiation reason value;
and obtaining a bearer release request carrying the release initiating reason value according to the RAR message, and sending the bearer release request to the corresponding mobile management entity.
The invention also provides a bearer release device, which is applied to a mobility management entity MME and comprises the following components:
a judging module, configured to judge, when receiving a handover request sent by a source base station, whether a bearer release request carrying a release initiation cause value sent by a user plane functional entity gateway SAE-GW is received before receiving the handover request;
a first sending module, configured to send a notification message for indicating a handover failure and a release instruction of the bearer S1 between the base station and the core network to the source base station when receiving a bearer release request that is sent by a user plane functional entity gateway SAE-GW and carries a release initiation cause value before receiving the handover request.
Optionally, the bearing releasing device further includes:
a second sending module, configured to send a bearer release response message to the SAE-GW after sending the notification message indicating the handover failure and the release instruction of the bearer between the base station and the core network S1 to the source base station.
Optionally, the value of the initiation release reason includes a calling side hang-up or a called side hang-up.
The invention also provides a bearer release device, which is applied to the user plane functional entity gateway SAE-GW and comprises the following components:
the receiving module is used for receiving a Random Access Response (RAR) message which is sent by the charging policy control unit (PCRF) and carries a release initiation reason value;
and the processing module is used for obtaining the bearer release request carrying the release initiating reason value according to the RAR message and sending the bearer release request to the corresponding mobile management entity.
The invention also provides a mobility management entity MME, which comprises:
a first processor, configured to determine, when receiving a handover request sent by a source base station, whether a bearer release request carrying a release initiation cause value sent by a user plane functional entity gateway SAE-GW is received before receiving the handover request;
if yes, sending a notification message for indicating the handover failure and a release instruction carried by S1 between the base station and the core network to the source base station.
Optionally, the first processor is further configured to:
and after the notification message for indicating the switching failure and the releasing instruction of the S1 bearer between the base station and the core network are sent to the source base station, sending a bearer releasing response message to the SAE-GW.
Optionally, the value of the initiation release reason includes a calling side hang-up or a called side hang-up.
The invention also provides a user plane functional entity gateway SAE-GW, comprising:
the input/output port is used for receiving a Random Access Response (RAR) message which is sent by the charging policy control unit (PCRF) and carries the value of the reason for initiating the release;
and the second processor is used for obtaining a bearer release request carrying the initiation release reason value according to the RAR message and sending the bearer release request to the corresponding MME.
The technical scheme of the invention has the following beneficial effects:
in the above scheme, the bearer release method determines whether a bearer release request carrying a release initiation cause value sent by a user plane functional entity gateway SAE-GW is received before receiving a handover request when receiving the handover request sent by a source base station; if yes, sending a notification message for indicating the switching failure and a release instruction loaded by S1 between the base station and the core network to the source base station; the situation that the terminal is meaninglessly and repeatedly required to switch if a switching request is received after a release instruction is received can be avoided, signaling overhead is saved, and the problems of extra signaling overhead and meaningless switching existing when the switching conflicts with the upper-layer SIP release in the prior art are well solved.
Drawings
Fig. 1 is a schematic diagram of a VoLTE eSRVCC handover process in the prior art;
fig. 2 is a schematic diagram illustrating a signaling release process in the prior art;
fig. 3 is a flowchart illustrating a bearer release method according to a first embodiment of the present invention;
fig. 4 is a flowchart illustrating a bearer release method according to a second embodiment of the present invention;
fig. 5 is a schematic diagram illustrating a specific flow of a bearer release method when a release initiation cause value is a calling side hang-up in an embodiment of the present invention;
fig. 6 is a schematic diagram illustrating a specific flow of a bearer release method when a release initiation cause value is a called side hook in the embodiment of the present invention;
fig. 7 is a schematic structural view of a load release apparatus according to a third embodiment of the present invention;
fig. 8 is a schematic structural view of a load release apparatus according to a fourth embodiment of the present invention;
fig. 9 is a schematic structural diagram of a mobility management entity according to a fifth embodiment of the present invention;
fig. 10 is a schematic structural diagram of a user plane functional entity gateway according to a sixth embodiment of the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.
The invention provides a plurality of solutions for the problems of extra signaling overhead and meaningless switching when the switching conflicts with the upper SIP release in the prior art, and the solutions are as follows:
example one
As shown in fig. 3, an embodiment of the present invention provides a bearer release method, which is applicable to a mobility management entity MME, where the bearer release includes:
step 31: when receiving a switching request sent by a source base station, judging whether a bearer release request which is sent by a user plane functional entity gateway SAE-GW and carries a release initiation reason value is received or not before the switching request is received;
step 32: if yes, sending a notification message for indicating the handover failure and a release instruction carried by S1 between the base station and the core network to the source base station.
The bearer release method provided in the embodiment of the present invention determines, when receiving a handover request sent by a source base station, whether a bearer release request carrying a cause value for initiating release and sent by a user plane functional entity gateway SAE-GW is received before receiving the handover request; if yes, sending a notification message for indicating the switching failure and a release instruction loaded by S1 between the base station and the core network to the source base station; the situation that the terminal is meaninglessly and repeatedly required to switch if a switching request is received after a release instruction is received can be avoided, signaling overhead is saved, and the problems of extra signaling overhead and meaningless switching existing when the switching conflicts with the upper-layer SIP release in the prior art are well solved.
Further, after the sending, to the source base station, the notification message indicating the handover failure and the release instruction of the bearer between the base station and the core network S1, the bearer release method further includes: and sending a bearer release response message to the SAE-GW.
Wherein, the initiating release reason value comprises a calling side hang-up or a called side hang-up.
Example two
As shown in fig. 4, a second embodiment of the present invention provides a bearer release method, which is applicable to a user plane functional entity gateway SAE-GW, where the bearer release method includes:
step 41: receiving a Random Access Response (RAR) message which is sent by a charging policy control unit (PCRF) and carries a release initiation reason value;
step 42: and obtaining a bearer release request carrying the release initiating reason value according to the RAR message, and sending the bearer release request to the corresponding mobile management entity.
In the bearer release method provided in the second embodiment of the present invention, by sending a bearer release request carrying a release initiation cause value to a corresponding mobility management entity, when receiving a handover request sent by a source base station, the corresponding mobility management entity can send a notification message indicating a handover failure and a release instruction of an S1 bearer between the base station and a core network to the source base station; and further, the situation that the terminal is meaninglessly and repeatedly required to be switched if a switching request is received after a release instruction is received is avoided, signaling overhead is saved, and the problems of extra signaling overhead and meaningless switching existing when the switching conflicts with the upper-layer SIP release in the prior art are solved well.
The bearer release method provided in the embodiments of the present invention is described below with reference to the MME and the SAE-GW.
For example, the initiating release cause value is the calling side hang-up, as shown in fig. 5:
51-53, the calling side hangs up, and the calling terminal UE (O) sends a BYE message to the calling session border controller VoLTE SBC (O), and then the message is forwarded to the called session border controller VoLTE SBC (T) and the called terminal UE (T).
Step 54, the VoLTE SBC (O) sends the session transport number STR message carrying the reason value to the calling charging policy control unit pcrf (O) to indicate that the calling side is on hook.
Step 55, pcrf (o) sends the message to the calling user plane functional entity gateway SAE-gw (o) to carry the reason value indication as the calling SIP layer hanging up (calling side hanging up).
Step 56, SAE-gw (o) replies to pcrf (o) with a re-authentication response RAA message.
Step 57, pcrf (O) replies an access authorization response AAA message to VoLTE SBC (O).
Step 58, the calling side mobility management entity mme (o) sends a Delete bearer command message to SAE-gw (o).
Step 59, SAE-gw (o) sends to mme (o) Delete bearer request message Delete bearer request, where the indication of the cause value is calling SIP layer hang-up, mme (o) receives the cause value, and then after receiving Handover request message Handover request sent by the source base station, mme (o) replies Handover preparation failure message Handover failure to notify the source base station of the current Handover failure, and at the same time, initiates a release process of S1 dedicated bearer to the source base station, and does not perform Handover process of the calling UE, thereby triggering a release process of radio bearer.
Step 510, the source base station releases the air interface bearer.
Step 511, MME (O) replies to SAE-GW (O) with a Delete bearer response message.
Step 512-519, the ue (t) side bearer release procedure is performed, which may refer to the conventional scheme and is not described herein again.
Step 520, the ue (t) replies to the 200ok message.
For example, the initiating release cause value is called side hang-up, as shown in fig. 6:
and 61-63, the called side hangs up, and the called terminal UE (T) sends a BYE message to a called session border controller VoLTE SBC (T), and then the message is forwarded to a calling session border controller VoLTE SBC (O) and a calling terminal UE (O).
Step 64, the VoLTE SBC (T) sends a session transport number STR message carrying a reason value to the called charging policy control unit pcrf (T) to indicate that the called side hangs up.
Step 65, the message sent by pcrf (t) to called user plane functional entity gateway SAE-gw (t) carries the reason value indication as called SIP layer hanging up (calling side hanging up).
Step 66, SAE-gw (t) replies to pcrf (t) with re-authentication response RAA message.
Step 67, pcrf (T) replies with an access authorization response AAA message to VoLTE SBC (T).
Step 68, the called mobility management entity mme (t) sends a Delete bearer command message to SAE-gw (t).
Step 69, SAE-gw (t) sends to mme (t) a Delete bearer request message Delete bearer request, where the indication of the cause value is called SIP layer hang-up, mme (t) receives the cause value, and then after receiving Handover request message Handover request sent by the source base station, returns a Handover preparation failure message Handover failure, notifies the source base station of the Handover failure, and at the same time, initiates a release process of S1 bearer to the source base station, and does not perform a Handover process of the called UE, thereby triggering a release process of radio bearer.
Step 610, the source base station releases the air interface bearer.
Step 611, mme (t) replies to SAE-gw (t) with Delete bearer response message Delete bearer response.
Step 612-.
Step 620, the ue (o) replies to the 200ok message.
Therefore, the scheme provided by the embodiment of the invention can solve the signaling conflict, and can not carry out extra signaling overhead and meaningless switching when the signaling conflict occurs.
EXAMPLE III
As shown in fig. 7, a bearer release apparatus according to a third embodiment of the present invention is applicable to a mobility management entity MME, and the bearer release apparatus includes:
a determining module 71, configured to determine, when receiving a handover request sent by a source base station, whether a bearer release request carrying a release initiation cause value sent by a user plane functional entity gateway SAE-GW is received before receiving the handover request;
a first sending module 72, configured to send a notification message for indicating a handover failure and a release instruction of the bearer S1 between the base station and the core network to the source base station when receiving a bearer release request that is sent by a user plane functional entity gateway SAE-GW and carries a release initiation cause value before receiving the handover request.
The bearer release apparatus provided in the third embodiment of the present invention determines, when receiving a handover request sent by a source base station, whether a bearer release request carrying a cause value for initiating release and sent by a user plane functional entity gateway SAE-GW is received before receiving the handover request; if yes, sending a notification message for indicating the switching failure and a release instruction loaded by S1 between the base station and the core network to the source base station; the situation that the terminal is meaninglessly and repeatedly required to switch if a switching request is received after a release instruction is received can be avoided, signaling overhead is saved, and the problems of extra signaling overhead and meaningless switching existing when the switching conflicts with the upper-layer SIP release in the prior art are well solved.
Further, the load release device further includes: a second sending module, configured to send a bearer release response message to the SAE-GW after sending the notification message indicating the handover failure and the release instruction of the bearer between the base station and the core network S1 to the source base station.
Preferably, the initiation release reason value includes a calling side hang-up or a called side hang-up.
The implementation embodiments of the bearer release method related to the MME side are all applicable to the embodiment of the bearer release apparatus, and the same technical effects can be achieved.
Example four
As shown in fig. 8, a fourth embodiment of the present invention provides a bearer release apparatus, which is applicable to a user plane functional entity gateway SAE-GW, and the bearer release apparatus includes:
a receiving module 81, configured to receive a random access response RAR message that is sent by the charging policy control unit PCRF and carries a release initiation cause value;
and the processing module 82 is configured to obtain a bearer release request carrying the release initiating cause value according to the RAR message, and send the bearer release request to the corresponding mobility management entity.
The bearer release apparatus provided in the fourth embodiment of the present invention sends the bearer release request carrying the release initiation cause value to the corresponding mobility management entity, so that the corresponding mobility management entity can send, when receiving the handover request sent by the source base station, a notification message for indicating the handover failure and a release instruction of the bearer in S1 between the base station and the core network to the source base station; and further, the situation that the terminal is meaninglessly and repeatedly required to be switched if a switching request is received after a release instruction is received is avoided, signaling overhead is saved, and the problems of extra signaling overhead and meaningless switching existing when the switching conflicts with the upper-layer SIP release in the prior art are solved well.
The implementation embodiments of the bearer release method related to the SAE-GW side are all applicable to the embodiment of the bearer release apparatus, and the same technical effect can be achieved.
EXAMPLE five
As shown in fig. 9, a fifth embodiment of the present invention provides a mobility management entity MME, including:
a first processor 91, configured to determine, when receiving a handover request sent by a source base station, whether a bearer release request carrying a release initiation cause value sent by a user plane functional entity gateway SAE-GW is received before receiving the handover request;
if yes, sending a notification message for indicating the handover failure and a release instruction carried by S1 between the base station and the core network to the source base station.
The mobility management entity provided in the fifth embodiment of the present invention determines, when receiving a handover request sent by a source base station, whether a bearer release request that is sent by a user plane functional entity gateway SAE-GW and carries a cause value for initiating release is received before receiving the handover request; if yes, sending a notification message for indicating the switching failure and a release instruction loaded by S1 between the base station and the core network to the source base station; the situation that the terminal is meaninglessly and repeatedly required to switch if a switching request is received after a release instruction is received can be avoided, signaling overhead is saved, and the problems of extra signaling overhead and meaningless switching existing when the switching conflicts with the upper-layer SIP release in the prior art are well solved.
Further, the first processor is further configured to: and after the notification message for indicating the switching failure and the releasing instruction of the S1 bearer between the base station and the core network are sent to the source base station, sending a bearer releasing response message to the SAE-GW.
Preferably, the initiation release reason value includes a calling side hang-up or a called side hang-up.
The implementation embodiments of the bearer release apparatus related to the MME side are all applicable to the embodiment of the MME, and the same technical effects can be achieved.
EXAMPLE six
As shown in fig. 10, a sixth embodiment of the present invention provides a user plane functional entity gateway SAE-GW, including:
an input/output port 101, configured to receive a random access response RAR message that is sent by the charging policy control unit PCRF and carries an initiation release cause value;
the second processor 102 is configured to obtain, according to the RAR message, a bearer release request carrying the origination release cause value, and send the bearer release request to a corresponding mobility management entity MME.
In the sixth embodiment of the present invention, by sending a bearer release request carrying a release initiation cause value to a corresponding mobility management entity, the user plane functional entity gateway enables the corresponding mobility management entity to send, to a source base station, a notification message for indicating a handover failure and a release instruction of an S1 bearer between the base station and a core network when receiving a handover request sent by the source base station; and further, the situation that the terminal is meaninglessly and repeatedly required to be switched if a switching request is received after a release instruction is received is avoided, signaling overhead is saved, and the problems of extra signaling overhead and meaningless switching existing when the switching conflicts with the upper-layer SIP release in the prior art are solved well.
The implementation embodiments related to the bearer release apparatus on the SAE-GW side are all applicable to the embodiment of the SAE-GW, and the same technical effect can be achieved.
It should be noted that many of the functional units described in this specification have been referred to as modules, in order to more particularly emphasize their implementation independence.
In embodiments of the present invention, modules may be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be constructed as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different bits which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Likewise, operational data may be identified within the modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
When a module can be implemented by software, considering the level of existing hardware technology, a module implemented by software may build a corresponding hardware circuit to implement a corresponding function, without considering cost, and the hardware circuit may include a conventional Very Large Scale Integration (VLSI) circuit or a gate array and an existing semiconductor such as a logic chip, a transistor, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.
Claims (9)
1. A bearer release method is applied to a Mobility Management Entity (MME), and is characterized by comprising the following steps:
when receiving a switching request sent by a source base station, judging whether a bearer release request which is sent by a user plane functional entity gateway SAE-GW and carries a release initiation reason value is received or not before the switching request is received;
if yes, sending a notification message for indicating the handover failure and a release instruction carried by S1 between the base station and the core network to the source base station.
2. The bearer release method according to claim 1, wherein after the sending, to the source base station, the notification message indicating the handover failure and the release instruction of the bearer between the base station and the core network S1, the bearer release method further comprises:
and sending a bearer release response message to the SAE-GW.
3. The bearer release method according to claim 1, wherein the origination release cause value comprises a calling side hang-up or a called side hang-up.
4. A bearer release apparatus applied to a Mobility Management Entity (MME), comprising:
a judging module, configured to judge, when receiving a handover request sent by a source base station, whether a bearer release request carrying a release initiation cause value sent by a user plane functional entity gateway SAE-GW is received before receiving the handover request;
a first sending module, configured to send a notification message for indicating a handover failure and a release instruction of the bearer S1 between the base station and the core network to the source base station when receiving a bearer release request that is sent by a user plane functional entity gateway SAE-GW and carries a release initiation cause value before receiving the handover request.
5. The carrier release device of claim 4, further comprising:
a second sending module, configured to send a bearer release response message to the SAE-GW after sending the notification message indicating the handover failure and the release instruction of the bearer between the base station and the core network S1 to the source base station.
6. The bearer release apparatus according to claim 4, wherein the initiation release cause value comprises a calling side hang-up or a called side hang-up.
7. A mobility management entity, MME, comprising:
a first processor, configured to determine, when receiving a handover request sent by a source base station, whether a bearer release request carrying a release initiation cause value sent by a user plane functional entity gateway SAE-GW is received before receiving the handover request;
if yes, sending a notification message for indicating the handover failure and a release instruction carried by S1 between the base station and the core network to the source base station.
8. The mobility management entity according to claim 7, wherein the first processor is further configured to:
and after the notification message for indicating the switching failure and the releasing instruction of the S1 bearer between the base station and the core network are sent to the source base station, sending a bearer releasing response message to the SAE-GW.
9. The mobility management entity according to claim 7, wherein the initiation release cause value comprises a calling side hang-up or a called side hang-up.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710282999.7A CN108924893B (en) | 2017-04-26 | 2017-04-26 | Bearer release method, bearer release device, MME and SAE-GW |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710282999.7A CN108924893B (en) | 2017-04-26 | 2017-04-26 | Bearer release method, bearer release device, MME and SAE-GW |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108924893A CN108924893A (en) | 2018-11-30 |
| CN108924893B true CN108924893B (en) | 2020-12-25 |
Family
ID=64402876
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710282999.7A Active CN108924893B (en) | 2017-04-26 | 2017-04-26 | Bearer release method, bearer release device, MME and SAE-GW |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108924893B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113543362B (en) * | 2020-04-14 | 2023-08-25 | 成都鼎桥通信技术有限公司 | Exception handling method and device for radio bearer establishment |
| CN114189913B (en) * | 2022-02-15 | 2022-05-17 | 深圳国人无线通信有限公司 | Method and system for 5G voice falling back to 4G |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101459907A (en) * | 2008-03-26 | 2009-06-17 | 中兴通讯股份有限公司 | Method for indicating service gateway bearing management |
| CN101682867A (en) * | 2007-06-08 | 2010-03-24 | 艾利森电话股份有限公司 | Handover from circuit switched domain to circuit switched service over packet switched domain |
| CN101686563A (en) * | 2008-09-23 | 2010-03-31 | 三星电子株式会社 | Method for releasing resources in mobile communication system |
| CN102333312A (en) * | 2011-10-27 | 2012-01-25 | 大唐移动通信设备有限公司 | Message transmission method and device for re-authentication (RA) process |
| CN102695222A (en) * | 2011-03-24 | 2012-09-26 | 中兴通讯股份有限公司 | Switching method of local access service and switching system thereof |
| CN103441862A (en) * | 2013-08-07 | 2013-12-11 | 华为技术有限公司 | Method, relative device and system for achieving restoration terminal called service |
| EP2844023A1 (en) * | 2012-04-27 | 2015-03-04 | Mitsubishi Electric Corporation | Communication system |
| US9510213B2 (en) * | 2013-04-04 | 2016-11-29 | St-Ericsson Sa | Methods and systems for interference immunity using frequency allocation lists in devices having embedded systems |
| CN106302638A (en) * | 2016-07-27 | 2017-01-04 | 华为技术有限公司 | A kind of data managing method, forwarding unit and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101047624B (en) * | 2006-04-27 | 2010-06-09 | 华为技术有限公司 | Tag distribution method and tag selling method |
| JP5337889B2 (en) * | 2012-02-24 | 2013-11-06 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile station and communication method |
-
2017
- 2017-04-26 CN CN201710282999.7A patent/CN108924893B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101682867A (en) * | 2007-06-08 | 2010-03-24 | 艾利森电话股份有限公司 | Handover from circuit switched domain to circuit switched service over packet switched domain |
| CN101459907A (en) * | 2008-03-26 | 2009-06-17 | 中兴通讯股份有限公司 | Method for indicating service gateway bearing management |
| CN101686563A (en) * | 2008-09-23 | 2010-03-31 | 三星电子株式会社 | Method for releasing resources in mobile communication system |
| CN102695222A (en) * | 2011-03-24 | 2012-09-26 | 中兴通讯股份有限公司 | Switching method of local access service and switching system thereof |
| CN102333312A (en) * | 2011-10-27 | 2012-01-25 | 大唐移动通信设备有限公司 | Message transmission method and device for re-authentication (RA) process |
| EP2844023A1 (en) * | 2012-04-27 | 2015-03-04 | Mitsubishi Electric Corporation | Communication system |
| US9510213B2 (en) * | 2013-04-04 | 2016-11-29 | St-Ericsson Sa | Methods and systems for interference immunity using frequency allocation lists in devices having embedded systems |
| CN103441862A (en) * | 2013-08-07 | 2013-12-11 | 华为技术有限公司 | Method, relative device and system for achieving restoration terminal called service |
| CN106302638A (en) * | 2016-07-27 | 2017-01-04 | 华为技术有限公司 | A kind of data managing method, forwarding unit and system |
Non-Patent Citations (2)
| Title |
|---|
| Bearer release control during handover from 3GPP to non3GPP;Huawei;《3GPP TSG-SA2 Meeting #62 S2-080158》;20080118;全文 * |
| LTE/SAE系统中用户移动性管理的研究与分析;姬自英;《现代电信科技》;20100831;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108924893A (en) | 2018-11-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2764259C1 (en) | Method for activating or deactivating user plane connection in each session | |
| US11638140B2 (en) | Method for transmitting and receiving signal related to switching access in wireless communication system, and device therefor | |
| US11432208B2 (en) | Network handover method, apparatus and system | |
| CN107079355B (en) | Pre-establishment of service disruption response for telecommunications network | |
| EP2732659B1 (en) | Method and apparatus for transferring telecommunications connections | |
| US11283932B2 (en) | Providing voice call support in a network | |
| US20140051443A1 (en) | Methods and Apparatus for Enhancing Circuit-Switched Call Fallback (CSFB) Service for a Shared Network Node | |
| US20200329397A1 (en) | Eps bearer context status synchronization upon inter-system change from evolved packet system (eps) to fifth generation system (5gs) | |
| US9521590B2 (en) | Multi-bearer connection control | |
| WO2019196649A1 (en) | Network switching method and apparatus for voice service | |
| JP6480011B2 (en) | Method and mobile radio communication network component for establishing communication | |
| CN109804665B (en) | Method and communication device for establishing communication | |
| TW202341797A (en) | Methods for managing radio bearer compatibility in a communication network, user device and radio access network for implementing the same | |
| WO2016054822A1 (en) | Csfb call establishment method and device | |
| CN108924893B (en) | Bearer release method, bearer release device, MME and SAE-GW | |
| WO2019029228A1 (en) | Method and device for processing voice service, and storage medium | |
| CN110708728A (en) | Method, equipment and storage medium for realizing voice call continuity | |
| US20230224772A1 (en) | Managing communication during mcg failure | |
| WO2022155139A1 (en) | Managing packet-based network connections during handover | |
| US11470528B2 (en) | Technique for preparing user equipment mobility | |
| EP3735031B1 (en) | Handover processing method, network device, terminal device, and computer storage medium | |
| US20190150049A1 (en) | Method for triggering circuit switching fallback procedure, apparatus, and system | |
| WO2020197454A1 (en) | Paging of idle state wireless communication devices | |
| CN113661734A (en) | Method and apparatus for optimizing inter-system handovers | |
| US20230284314A1 (en) | Managing Packet-Based Multimedia Network Connections During Master Cell Group Failure |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |