WO2007033564A1

WO2007033564A1 - A control method, system and device for updating bearer

Info

Publication number: WO2007033564A1
Application number: PCT/CN2006/001859
Authority: WO
Inventors: Fang You; Fengshao Zou; Wenyu Liu; Jie Xu; Hua Wei
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-09-22
Filing date: 2006-07-26
Publication date: 2007-03-29
Also published as: CN100466809C; CN1882177A

Abstract

A control method, system and device for updating bearer of A2p interface in soft switching system of mobile communication technology. When impact occurs between BS and mobile switch center emulation (MSCe) for starting bearer updating flow orderly or synchronously, the method mainly comprises: performing the parameter updating flow that MSCe starts and ending the parameter updating flow that BS starts. Alternatively, setting first identification information and/or second identification information for identifying that the bearer updating flow is started by MSCe or BS respectively. Then identifying BS and MSCe according to the first identification information and/or second identification information, performing the parameter updating flow that BS starts and ending the parameter updating flow that MSCe starts. The control system mainly comprises identification information adding/identifying module set in MSCe and BS respectively.

Description

Control method, system and device for updating bearer parameters

The present invention relates to mobile communication technologies, and in particular, to a control method, system and device for updating A2p interface bearer parameters under a softswitch architecture. Background technique

CDMA (Code Division Multiplex Access) system call control and bearer separation architecture mainly includes MSCe (Mobile Switch Center Emulation:), BS (Base Station, base station) and MGW (Media Gateway, Media Gateway) And other functional entities, wherein the A2p interface is an interface between the BS and the MGW, and is mainly used for transmitting user data of the mobile station (mobile station) as a bearer path. When the MS establishes a call through the MSCe, the MSCe and the BS need to negotiate the bearer parameters of the A2p interface, and during the call, the A2p interface bearer parameters of the established A2p interface are also updated, and the update process may be respectively performed by the MSCe or The BS initiated it.

In the prior art, the process of updating the A2P interface bearer parameters initiated by the BS is as shown in FIG. 1 , and includes the following steps:

Al, the BS sends an A2p interface bearer update request (Bearer Update Required) message to the MSCe;

When the BS needs to update the A2P interface bearer parameters of the BS to the MGW, it sends a Bearer Update Required message to the MSCe, which contains the recommended A2p interface bearer parameters, and starts the BS-side timer Tzzp until the A2p returned by the MSCe is received. The Tzz timer is stopped after the interface carries the Bearer Update Request message.

A2. After receiving the Bearer Update Required message sent by the BS, the MSCe returns a Bearer Update Request message to the BS.

The MSCe constructs a Bearer Update Request message according to the A2P interface bearer parameter carried in the Bearer Update Required message, and sends the message to the BS, and starts the timer Tyyp on the MSCe side. The Tyyp timing is stopped until a Response (Bearer Update Response) message is received.

After receiving the Bearer Update Request message, the ABS updates the A2P interface bearer parameters, and performs a service negotiation process with the MS to update the service channel or service option related to the A2p interface bearer parameter update.

A4. The BS returns a Bearer Update Response message to the MSCe after the update is completed.

The Bearer Update Response message returned by the BS to the MSCe carries the modification content according to the Bearer Update Request message. After receiving the message, the MSCe stops the Tyyp timer on the local side. If the timer expires, the Bearer Update Response is not received. The message, the MSCe actively tears down the call related to the current parameter update request.

If the BS does not receive the Bearer Update Request message when the timer Tzzp times out, the BS performs the retransmission of the Bearer Update Required message and the restart of the Tzzp timer according to the configured number of retransmissions. The default Tzzp timer duration is 6S.

In the prior art, the process of updating the A2P interface bearer parameters initiated by the MSCe is as shown in FIG. 2, and includes the following steps:

Bl, the MSCe sends a Bearer Update Request message to the BS, where the MSCe proposes the updated parameter content;

The MSCe needs to change the A2p bearer parameters of the BS to the MGW, and sends a Bearer Update Request message to the BS, and starts the MSCe side timer Tyyp.

After receiving the Bearer Update Request message, the BS updates the 承载2ρ interface bearer parameters, and performs a service negotiation process with the MS to update parameters such as service channels or service options related to the A2p interface bearer parameter update.

B3. The BS returns a Bearer Update Response message to the MSCe, where the content changed according to the Bearer Update Request message, and after receiving the Bearer Update Response message, the MSCe stops the Tyyp timer. If the Bearer Update Response message has not been received when the timer expires, the MSCe actively tears down the call related to the current parameter update request. Since both the BS and the MSCe can initiate the bearer parameter update process autonomously, the following two update process conflicts are inevitable:

1. The BS sends a bearer parameter update request message to the MSCe and starts monitoring the response time of the application message, where the application message carries the bearer parameter information recommended by the BS party to be updated; and, after the application message is sent, before the application message arrives at the MSCe The MSCe sends a bearer parameter update request message to the BS and starts monitoring the response time of the update request message, where the request message carries the bearer parameter information that the MSCe party proposes to update; or

2. The MSCe sends a bearer parameter update request message to the BS and starts monitoring the response time of the update request message, where the update request message carries the bearer parameter information that the MSCe party proposes to update; and, after the request message is sent, the request message arrives. Before the BS, the BS sends a bearer parameter update request message to the MSCe and starts monitoring the response time of the application message, where the application message carries the bearer parameter information recommended by the BS.

According to the provisions of the existing process, the general processing flow for conflict occurs as shown in FIG. 3. In FIG. 3, it is assumed that the MSCe sends a Bearer Update Request message and the BS sends a Bearer Update Required message almost simultaneously. For the convenience of description, the Bearer Update Request message is sent according to the description. The sequence number is 1, 2, and the corresponding Bearer Update Response message is numbered 1, 2:

The Cl and the BS send a Bearer Update Required message to the MSCe to apply for the A2p bearer parameter update, and start the timer Tzzp. Almost at the same time, the MSCe sends a Bearer Update Request message 1 to the BS to instruct the A2p bearer parameter update to start the timer Tyypl. The two messages are not necessarily connected. According to the usual situation, the recommended bearer update parameters are different in the message;

C2, MSCe side: Receive the Bearer Update Required message, construct the corresponding Bearer Update Request message 2 and send it to the BS to start the Tyyp2 timer.

The BS side: Receives the Bearer Update Request message 1, stops the timer Tzzp, updates the A2P interface bearer parameters according to the bearer update parameters recommended by the MSCe, and performs a service negotiation process with the MS to update the service related to the current A2p interface bearer parameter update. The channel or service option and other parameters are updated, and the Bearer Update Response message 1 is returned;

C3, MSCe side: Receive Bearer Update Response message 1, MSCe stops timer Tyypl;

BS side: Receives the Bearer Update Request message 2, the BS considers that it is the newly initiated bearer update request of the MSCe, and the BS and the MS perform the service negotiation process, and return the Bearer Update Response response message 2;

The MSCe receives the Bearer Update Response message 2 and stops the Ty p2 timer.

The above process has the following problems:

1. The existing processing procedure does not consider the conflict between the Bearer Update Required and the Bearer Update Request message. Once the message conflicts, the MSCe continuously sends two Bearer Update Request messages for the same call, starts two timers, and adds MSCe call processing. Complexity and system burden;

2. The BS side cannot distinguish whether the received Bearer Update Request message is a response of the Bearer Update Required message or a bearer update message initiated by the MSCe. Therefore, when the message conflicts, the BS will mistake the Bearer Update Request message sent by the MSCe as a response. The A2p bearer update process required by the MSCe may be covered by the bearer update process required by the BSC. The MSCe is in the call control state, especially in the supplementary service scenario. The MSCe initiates a large number of A2p interface bearer parameter updates, if the MSCe is required due to a message conflict. Failure of A2p bearer update will have an impact on the business. Summary of the invention

The present invention first provides a control method, system and device for updating bearer parameters under a softswitch architecture, so as to solve the problem that the existing processing flow is complicated, and further solve the problem that the A2p bearer update failure rate required by the MSCe side is low.

In order to solve the above technical problem, the present invention provides the following technical solutions:

And a control method for updating the bearer parameters, where the control method includes the following steps when the bearer parameter update process initiated by the base station side and the mobile softswitch side occurs simultaneously or simultaneously:

A. Perform a bearer parameter update process initiated by the mobile softswitch; and

B. End the bearer parameter update process initiated by the base station. The step A specifically includes the following steps:

Al, the base station receives a bearer parameter update request message sent by the mobile softswitch, where the request message carries the bearer parameter information recommended by the mobile softswitch to be updated;

A2. The base station performs bearer parameter update according to the bearer parameter information recommended by the mobile softswitch, and sends an update response message to the mobile softswitch.

A3. The mobile softswitch receives the update response message and ends monitoring the response time of the request message. The step A1 further includes: when the base station receives the bearer parameter update request message sent by the mobile softswitch, stopping, by the base station, monitoring the response time of the application message that has been sent to the mobile softswitch.

The step B includes: when the mobile softswitch is monitoring the response time of the update request message sent to the base station, if the update request message sent by the base station is received, the update request message is discarded.

Further, the step B further includes:

When the mobile softswitch is monitoring the response time of the update request message sent to the base station, if the update request message sent by the base station is received, the reject response message is returned to the base station;

The base station stops monitoring the response time of the application message after receiving the reject response message.

Further, the method further includes:

Setting, in the message indicating that the bearer parameter update process is initiated by the mobile softswitch, and in the message exchanged in the update process initiated by the mobile softswitch, the message sender carries the message in all messages sent by the message An identification information, the message receiving party confirms that the ongoing update process is initiated by the mobile softswitch according to the first identification information, and then performs a corresponding operation; and/or

And setting, in the message that the bearer parameter update process is initiated by the base station, the second identifier information that is sent by the base station, and the message sender carries the second identifier information in all the sent messages in the message that is sent in the update process initiated by the base station, The message receiver confirms that the ongoing update process is initiated by the base station according to the second identity information, and then performs a corresponding operation.

Further, the reject response message carries a cause value corresponding to the message conflict setting.

In the method, the response message carrying the rejection information refers to: a bearer parameter update request message carrying the cause value, or a specifically extended reject message. Further, after the base station fails to update the bearer parameter according to the bearer parameter information that is recommended by the mobile softswitch, the method further includes the following steps:

The base station sends an update request message to the mobile softswitch again immediately or when the set time expires, and the application message carries the bearer parameter information currently recommended by the base station.

The second method for controlling the bearer parameters is used to: when the bearer parameter update process initiated by the base station side and the mobile softswitch side conflicts, the control method includes the following steps: a. setting is used to indicate the bearer parameter And updating, by the mobile softswitch, the first identifier information, and the first identifier information is carried in all the messages exchanged in the update process initiated by the mobile softswitch, and/or is configured to indicate that the bearer parameter update process is And second identifier information that is sent by the base station, and carries the second identifier information in all messages that are exchanged in the update process initiated by the base station;

And identifying, by the first identifier information and/or the second identifier information, a bearer parameter update procedure initiated by the base station side; and

c. Identify and end the bearer parameter update procedure initiated by the mobile softswitch according to the first identifier information and/or the second identifier information.

When the first identifier information is carried in all the messages that are exchanged in the update process initiated by the mobile softswitch, the step b includes the following steps:

The mobile softswitch receives the bearer parameter update request message from the base station when monitoring the response time of the first update request message sent to the base station, and ends monitoring the response time of the first update request message, and according to the update request message The base station side carrying the updated bearer parameter information to generate the second update request message is sent to the base station, and the response time of the second update request message is monitored. When the base station receives the second update request message, the base station confirms the second update. After the request message does not carry the first identifier information, end monitoring the response time of the bearer application message and perform bearer parameter update, and then send an update response message to the mobile softswitch;

After receiving the update response message, the mobile softswitch ends monitoring the response time of the second update request message.

In the foregoing implementation manner, the step C specifically includes the following steps: the base station receives the first After updating the request message and confirming that the first update request message carries the first identifier information, discarding the first update request message.

When the second identifier information is carried in all the messages that are exchanged in the update process initiated by the base station, the step b includes the following steps:

When the mobile softswitch monitors the response time of the first update request message sent to the base station, and receives the second identity information bearer parameter update request message sent by the base station, the response time of monitoring the first update request message is ended. And monitoring, according to the bearer parameter information that is updated by the base station, and the second update request message carrying the second identifier information, and sending the second update request message to the base station, and monitoring the response time of the second update request message. ;

When receiving the second update request message carrying the second identifier information, the base station ends monitoring the response time of the bearer application message and performs bearer parameter update, and then sends the second identifier information to the mobile softswitch. Update response message;

After receiving the update response message carrying the second identifier information, the mobile softswitch ends monitoring the response time of the second update request message.

In the foregoing real-time mode, the step c includes the following steps: the base station receives the first update request message, and confirms that the first update request message does not carry the second identifier information, and discards the first update request. Message.

The step C includes the following steps: the base station receives the first update request message, when the first identifier information is also carried in the message that is exchanged in the update process initiated by the mobile softswitch. And confirming that the first identifier is not carried in the first update request message or carrying the first identifier information, discarding the first update request message.

Further, after the bearer parameter update of the base station fails, the method further includes the following steps: the mobile softswitch sends an update request message to the base station again, or when the set time expires, the request message carrying the mobile softswitch Currently recommended updated bearer parameter information.

In the above two methods, the bearer parameter refers to an A2p interface bearer parameter.

The present invention also provides a control system for implementing a first type of update bearer parameters, including a mobile softswitch and a base station, wherein: The base station includes: a first update processing module, processing related messages sent and received by the base station in a bearer parameter update process, where: performing each bearer parameter update request message received from the mobile softswitch;

The mobile softswitch includes: a second update processing module, processing a related message sent and received by the mobile softswitch in a bearer parameter update process, where: when the bearer parameter update process initiated by the two parties generates a conflict, discarding the update received from the base station Application message.

The mobile softswitch further includes: a second timer, after the second update processing module sends a bearer parameter update request message to the base station, starting the second timer to monitor a response time of the request message, and receiving the base station When the application message is updated, it is determined whether the second timer is in an activated state, and if so, the update request message received from the base station is discarded, otherwise the update request message is executed.

The base station further includes: a first timer, after the first update processing module sends a bearer parameter request message to the mobile softswitch, the first timer is started to monitor the response time of the application message, and the mobile softswitch is received. The first timer is stopped when the update request message or the reject message of the application message is responded to.

The base station further includes: a first identifier information adding/identifying module, connected to the first processing module; the mobile softswitch further comprising: a second identifier information adding/identifying module, connecting the second processing module;

The first identifier information adding/identifying module and the second identifier information adding/identifying module are respectively configured to add first identifier information to all messages exchanged in the bearer parameter update process initiated by the base station side, and identify the first identifier information. And/or, adding second identification information to all messages interacting in the bearer parameter update process initiated by the mobile softswitch side, and identifying the second identification information.

The invention also provides a base station for implementing the first method, comprising:

a first update processing module, configured to process, by the base station, a related message sent and received in a bearer parameter update process, where: performing each bearer parameter update request message received from the mobile softswitch;

The first timer is connected to the first update processing module, and after the first update processing module sends a bearer parameter request message to the mobile softswitch, the first timer is started to monitor the response time of the application message, and is received. An update request message of the mobile softswitch or a rejection of the response to the application message When the information is on, the first timer is stopped.

a first identifier information adding/identifying module, configured to connect to the first update processing module, configured to add first identifier information to all messages interacting in the bearer parameter update process initiated by the base station side, and identify the first identifier information; Or, adding second identification information to all messages exchanged in the bearer parameter update process initiated by the mobile softswitch side, and identifying the second identification information.

The present invention also provides a mobile softswitch for implementing the first method, comprising: a second update processing module and a second timer connected to the second update processing module;

The second update processing module processes the related message sent and received by the mobile softswitch in the bearer parameter update process, where after the bearer parameter update request message is sent to the base station, the second timer is started to monitor the response time of the request message, And receiving the update request message of the base station, determining whether the second timer is in an activated state, and if yes, discarding the update request message received from the base station, otherwise executing the update request message.

a second identifier information adding/identifying module, which is connected to the second update processing module; the second identifier information adding/identifying module is configured to add a first identifier to all messages exchanged in the bearer parameter update process initiated by the base station side Information, and identifying the first identification information; and/or, adding second identification information to all messages interacting in the bearer parameter update process initiated by the mobile softswitch side, and identifying the second identification information.

The present invention also provides an update control system implementing a second type of bearer parameter, including a base station and a mobile softswitch, wherein:

The base station includes: a first update processing module and a first identification information adding/identifying module connected;

The mobile softswitch includes: a second update processing module and a second identification information adding/identifying module;

The first identifier information adding/identifying module and the second identifier information adding/identifying module are respectively configured to add first identifier information to all messages exchanged in the bearer parameter update process initiated by the base station side, and identify the first identifier. Information; and/or, adding second identification information to all messages interacting in the bearer parameter update process initiated by the mobile softswitch side, and identifying the second identification information; And outputting the identification result to the corresponding first update processing module and the second update processing module; the first update processing module and the second update processing module perform a bearer parameter update process initiated by the base station side according to the recognition result, ending the mobile The bearer parameter update process initiated by the softswitch.

The beneficial effects of the technical solution of the present invention are as follows:

The method of the present invention can be used to process the message conflict processing process. Optionally, the BS side can detect whether a message conflict occurs, thereby flexibly formulating a control policy according to the MSCe priority principle or the BS side priority principle, which can be based on the MSCe priority principle. The update success rate of the A2P interface bearer parameters initiated by the MSCe is ensured, and the impact of the A2p bearer update failure required by the MSCe caused by the message conflict is reduced. DRAWINGS

1 is a flowchart of normal update of A2p interface bearer parameters initiated by a BS in the prior art; FIG. 2 is a flowchart of normal update of A2p interface bearer parameters initiated by MSCe in the prior art; FIG. 3 is a message conflict in the prior art. Time processing flow chart;

4 is a flow chart of Embodiment 1 of a control method for implementing the present invention;

Figure 5 is a flow chart of Embodiment 2 of the control method for implementing the present invention;

6 is a flow chart of Embodiment 3 of a control method for implementing the present invention;

7 is a flow chart of Embodiment 4 of a control method for implementing the present invention;

8 is a schematic structural diagram of a control system for implementing priority processing of a bearer parameter update process initiated by the MSCe side according to the present invention;

FIG. 9 is a schematic structural diagram of a control system for implementing priority processing of a bearer parameter update process initiated by a BS side according to the present invention. detailed description

Embodiment 1

In this embodiment, according to the MSCe priority principle, after the MSCe sends the Bearer Update Request message, it does not receive the Bearer Update Response message returned by the BS. After the Bearer Update Required message is sent, it can be determined that a message conflict occurs, and the MSCe discards the Bearer Update Required message sent by the BS.

Each time the BS receives the Bearer Update Request message, according to the MSCe priority principle, the A2p interface bearer parameter update is performed according to the process of receiving the Bearer Update Request message from the MSCe, regardless of the response of the Bearer Update Required message. As shown in Figure 4, the following steps are included:

S101, SI 02, and BS send a Bearer Update Required message to the MSCe, where the A2p interface parameter recommended by the BS is updated, and the Tzzp timer is started to monitor the response time. At about the same time, the MSCe sends a Bearer Update Request message to the BS, where the MSCe proposes to update. A2p interface parameters, and start the Tyyp timer to monitor the response time;

5103. When the Tzzp timer that monitors the response time of the Bearer Update Request message is started, the MSCe may determine that a collision occurs after receiving the Bearer Update Required message sent by the BS, and discard the received Bearer Update Required according to the MSCe priority principle. Message

After receiving the Bearer Update Request message sent by the MSCe, the BS stops the Tzzp timer. At this time, the update process initiated by the BS side ends.

The BS performs a service negotiation process with the MS according to the recommended A2P interface parameter information carried in the Bearer Update Request message sent by the MSCe, and performs parameters such as a service channel or a service option related to the current A2p interface bearer parameter update according to the proposal of the MSCe side. Update;

S105. The BS returns a Bearer Update Response message to the MSCe, where the content is changed according to the Bearer Update Request message, and after receiving the Bearer Update Response message, the MSCe stops the Tyyp timer. If the Bearer Update Response message has not been received when the timer expires, the MSCe actively tears down the call related to the current parameter update request.

In the foregoing embodiment, the MSCe is configured to continuously send two Bearer Update Request messages to the same call, and the timer is started twice. The MSCe call processing is simple and reliable, and the success rate of the MSCe actively initiating the A2p interface bearer parameter update is improved.

When the BS side is required to identify whether a message conflict has occurred, that is, the BS needs to match the Bearer Update Required and the Bearer Update Request request message that responds to the application message. The following message collision discovery mechanism is provided:

1. All the messages in the bearer parameter update process initiated by the BS side carry an identifier information, and the message sender carries the identifier information in all the sent messages, and the message receiver confirms the ongoing update process according to the identifier information by the base station. After launching, perform the corresponding action. That is, a bearer Update Required message is added to the Bearer Update Required, such as a Tag, and a Bearer Update Required message containing the Tag is received. The MSCe should store the value in the Tag and carry it in the response Bearer Update Request message. After the BS starts the Tzzp timer, it can detect the bearer update message conflict after receiving the Bearer Update Request message without the tag.

2. In the same way, the tag may be carried in all the messages in the bearer parameter update process initiated by the BS side, but in all the messages in the bearer parameter update process initiated by the MSCe side, and the message sender is in all the messages sent. Carrying the identification information, the message receiver confirms that the ongoing update process is initiated by the mobile softswitch according to the identification information, and then performs the corresponding operation. That is, the tag is added to the Bearer Update Request message that the MSCe initiates the change process. The BS detects the conflict according to the Bearer Update Request message with the tag initiated by the MSCe after the timer Tzzp is started.

3. In addition, different identifier information may be carried in all the messages in the bearer parameter update process initiated by the BS side and all the messages in the bearer parameter update process initiated by the MSCe side. In this way, the message receiver can determine whether the message belongs to the bearer parameter update process according to whether the received message carries the corresponding identifier in one of the processes, and can also determine whether the received message does not carry the corresponding identifier information of another process. .

The identification information is usually composed of parameter identification and parameter values for associating request and response messages. When the identifier information needs to be used, the sending message party generates the identifier information (including the parameter identifier and the parameter value), and carries it in the message to the receiver. The receiver also includes the same parameter identifier and parameter value in the returned response message.

The present invention provides the following message conflict processing method based on the above-mentioned message conflict detection mechanism. The following embodiment is described by taking the identifier tag in the update message initiated by the MSCe side or the BS as an example, and carrying different in the two processes. The implementation principle of the logo is the same and will not be described again. Embodiment 2

In this embodiment, the MSCe priority principle is still adopted, and the BS abandons the initiative-initiated update process, and performs the update of the A2p interface bearer parameters according to the Bearer Update Request message initiated by the MSCe side. The specific process is as shown in FIG. 5, and includes the following steps:

S201: The BS sends a Bearer Update Required message to the MSCe, where the A2p interface parameter recommended by the BS side is updated, and the Tzzp timer is started to monitor the response time.

S202: At the same time, the MSCe sends a Bearer Update Request message to the BS, where the identifier tag and the A2p interface parameter recommended by the MSCe are updated, and the Tyyp timer is monitored to monitor the response time.

S203: After transmitting the Bearer Update Request message, the MSCe has started the Tyyp timer, and has received the Bearer Update Required message when the Bearer Update Response is not received, and determines that a message conflict occurs, according to the principle that the A2p bearer update initiated by the MSCe is prioritized. MSCe discards the Bearer Update Required message;

S204: The BS receives the Bearer Update Request message that is first initiated by the MSCe. The message carries the identifier tag, so that the message conflict may be determined. The BS stops the Tzzp timing that has been started according to the priority of the A2p bearer update initiated by the MSCe. And abandoning the previously initiated bearer parameter update, and performing a service negotiation process with the MS, and updating parameters such as a service channel or a service option related to the current A2p interface bearer parameter update according to the proposal of the MSCe side;

S205. The BS returns a Bearer Update Response message to the MSCe, where the modified content and the identifier tag are performed according to the Bearer Update Request message. After receiving the Bearer Update Response message carrying the identifier Tag, the MSCe stops the Tyyp timer.

If the Bearer Update Response message has not been received when the timer expires, the MSCe actively tears down the call related to the current parameter update request.

After the step S205, after the bearer update conflict has occurred and the BS fails to support the bearer parameter modification requested by the MSCe or the service negotiation process with the MS fails, the BS can immediately send a Bearer Update Required message to the MSCe to start the update process. After the process fails for a period of time (such as 2s), the BS-side expected bearer parameter update process is re-initiated. The interval (such as 2s) can be monitored by starting a timer to further improve the success rate of the update. Embodiment 3

When the MSCe determines that a message conflict has occurred, it may also reply to the Bearer Update Reject message (with a failure cause value, such as a message conflict), or return a Bearer Update Request message carrying a failure cause value (eg, a message conflict) indicating failure; After determining the message conflict according to the detection mechanism of the present invention, the original Tzzp timer is not immediately stopped, but the Tzzp timer is stopped after receiving the Bearer Update Reject or the Bearer Update Request paired with the Bearer Update Required message. The process shown in Figure 6 includes the following steps:

S301 to S302 are the same as the corresponding steps S201 and S202 in the second embodiment, and are not described here; the differences are as follows:

S303 and S304, the BS and the MS perform a service negotiation process, and update parameters such as a service channel or a service option related to the A2p interface bearer parameter update according to the proposal of the MSCe side, and then send an update success response message to the MSCe;

And after the BS determines the message conflict according to the detection mechanism of the present invention, the original Tzzp timer is not immediately stopped; instead, in step S305, the Bearer Update Reject message sent by the MSCe carrying the Tag identifier is received (with The failure cause value), or the received MSCe sends a Bearer Update Request message carrying a failure cause value (such as a message conflict) to indicate a failure and then stops.

The above processing flow is more in line with the condition that the Tzzp timer is stopped in a general sense, that is, the process ends when a matching response message is received.

Similarly, after the bearer update conflict has occurred and the BS fails to support the bearer parameter modification requested by the MSCe or the service negotiation process with the MS fails, the BS may immediately send a Bearer Update Required message to the MSCe to start the update process, or may be in the process. After a period of failure (such as 2s), the host side parameter update process is re-initiated, and the period (such as 2s) can be monitored by starting a timer to further improve the success rate of the update.

Compared with the prior art, the processing procedures of the first embodiment, the second embodiment, and the third embodiment are simpler, and the success rate of the MSCe actively initiating the A2p interface bearer parameter update is improved.

Embodiment 4 In this embodiment, the BS priority principle is adopted, and the BS determines that the Bearer Update Request message initiated by the MSCe side is discarded after the bearer update conflict occurs, and waits for the MSCe side to perform the A2p interface bearer parameter after receiving the request message replied according to the application message of the BS side. Update.

As shown in Figure 7, the following steps are included:

S401. The BS sends a Bearer Update Required message to the MSCe, where the identifier tag and the A2p interface parameter recommended by the BS are updated, and the Tzzp timer is started to monitor the response time.

According to the detection mechanism of the present invention, when the MSCe receives the Bearer Update Required message carrying the identifier tag sent by the BS, the MSCe should carry the same identifier tag in the returned Bearer Update Request message.

S402. At about the same time, the MSCe sends a Bearer Update Request message to the BS, where

The MSCe carries the proposed updated A2P interface parameter, and starts the Tyypl timer to monitor the response time, but the Bearer Update Request message does not carry the identifier tag;

When the MSCe sends the Bearer Update Request message, the MSCe has started the Tyypl timer. The Bearer Update Response B has not received the Bearer Update Required message. It determines that a message conflict has occurred. The A2p bearer update priority is initiated according to the BS. The MSCe stops the Tyypl timer, discards the previous bearer update request, and performs step S404.

S403: The BS receives the Bearer Update Request message that is first initiated by the MSCe, and determines that the message conflict occurs according to the identifier tag detection conflict method, and discards the received Bearer Update Request message according to the principle that the A2p bearer update priority initiated by the BS is performed;

S404> The MSCe sends a Bearer Update Request message to the BS according to the content of the BS-side recommendation update carried in the Bearer Update Required message, and restarts the timer Tyyp2, where the Bearer Update Request message carries the identifier Tag;

S405. After receiving the Bearer Update Request message carrying the tag tag in the same manner as the Bearer Update Required, perform a service negotiation process with the MS, and perform parameters such as a service channel or a service option related to the A2p interface bearer parameter update according to the proposal of the MSCe side. Update

S406. If the update is successful, the BS returns a Bearer Update Response message to the MSCe, where the modification content is performed according to the Bearer Update Request message, and the identifier is carried at the same time. Tag;

After the MSCe receives the Bearer Update Response message, the MSCe stops the Tyyp2 timer and ends the entire parameter update process. If the Bearer Update Response message has not been received when the timer expires, the MSCe actively tears down the call related to the current parameter update request.

In the foregoing method, after the MSCe determines that the bearer update conflicts and the BS-recommended bearer parameter update process fails, the MSCe side expected bearer parameter update process may be re-initiated immediately after a period of time (eg, 2s), Such as 2s) can be monitored by starting a timer to further improve the update success rate.

Compared with the prior art, the method of the fourth embodiment prioritizes the bearer update of the BS application, omits a bearer update response message, and simplifies the control difficulty of the Tyyp timer on the MSCe side.

As shown in FIG. 8, the method for implementing the update process initiated by the mobile softswitch side is a priority processing principle, and the present invention further provides a bearer parameter update control system, including a base station 100 and a mobile softswitch 200, where :

The base station 100 includes: a first update processing module 101, processing related messages sent and received by the base station 100 in the bearer parameter update process, where: performing each bearer parameter update request message received from the mobile softswitch 200;

The mobile softswitch 200 includes: a second update processing module 201, which processes a related message that is sent and received by the mobile softswitch 200 in a bearer parameter update process, where: when the bearer parameter update process initiated by the two parties conflicts, the slave base station 100 discards Received update request message.

The mobile softswitch 200 further includes: a second timer 202, and a second update processing module 201 to the base station

After transmitting the bearer parameter update request message, the second timer 202 is started to monitor the response time of the request message, and when receiving the update request message of the base station 100, it is determined whether the second timer 202 is in the startup state, and if The update request message received from the base station 100 is then discarded, otherwise the update request message is executed.

The base station 100 further includes: a first timer 102, the first update processing module 101 to the mobile softswitch

After transmitting the bearer parameter request message, the first timer 102 is started to monitor the response time of the application message, and the update request message of the mobile soft switch 200 or the reject message of the response application message is received. When the first timer 102 is stopped.

The base station 100 further includes: a first identification information adding/identifying module 103, connecting the first processing module

101 ;

The mobile softswitch 200 further includes: a second identification information adding/identifying module 203, connected to the second processing module 201;

The first identification information adding/identifying module 103 and the second identification information adding/identifying module 203 are respectively configured to add first identification information to all messages exchanged in the bearer parameter update process initiated by the base station 100 side, and identify the first identifier. Information; and/or, adding second identification information to all messages interacting in the bearer parameter update process initiated by the mobile softswitch 200, and identifying the second identification information.

Still referring to FIG. 8, the structure of the two devices, the base station 100 and the mobile softswitch 200, is used to implement the technical solution of the present invention, and is also within the protection scope of the present invention.

As shown in FIG. 9, in order to implement the method in which the update procedure initiated by the base station side is the priority processing principle, the present invention further provides a second bearer parameter update control system, including a base station 300 and a mobile softswitch 400, where:

The base station 300 includes: a first update processing module 301 and a first identification information adding/identifying module 302;

The mobile softswitch 400 includes: a connected second update processing module 401 and a second identification information adding/identifying module 402;

The first identification information adding/identifying module 302 and the second identification information adding/identifying module 402 are respectively configured to add first identification information to all messages exchanged in the bearer parameter update process initiated by the base station 300 side, and identify the first identifier. Information; and/or, adding second identification information to all messages interacting in the bearer parameter update process initiated by the mobile softswitch 400, and identifying the second identification information; and outputting the recognition result to the corresponding first update respectively Processing module 301 and second update processing module 401;

The first update processing module 301 and the second update processing module 401 perform a bearer parameter update process initiated by the base station side according to the recognition result, and end the bearer parameter update process initiated by the mobile softswitch. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Claims

Rights request

A control method for updating a bearer parameter, where the control method includes the following steps: when a bearer parameter update process initiated by a base station side and a mobile softswitch side occurs simultaneously or simultaneously:

B. End the bearer parameter update process initiated by the base station.

2. The method according to claim 1, wherein the step A specifically includes the following steps:

A receiving, by the base station, a bearer parameter update request message sent by the mobile softswitch, where the request message carries the bearer parameter information recommended by the mobile softswitch to be updated;

A3. The mobile softswitch receives the update response message and ends monitoring the response time of the request message.

The method of claim 2, wherein the step A1 further comprises: when the base station receives the bearer parameter update request message sent by the mobile softswitch, stopping, by the base station, monitoring the application message that has been sent to the mobile softswitch. Response time.

The method according to claim 2, wherein the step B includes: when the mobile softswitch is monitoring the response time of the update request message sent to the base station, if receiving the update request message sent by the base station, Discard the update request message.

The method according to claim 2, wherein the step B further comprises: when the mobile softswitch is monitoring the response time of the update request message sent to the base station, if the update request sent by the base station is received The message returns a reject response message to the base station;

The method according to any one of claims 1 to 5, wherein the method further comprises: setting first identification information for indicating that the bearer parameter update procedure is initiated by the mobile softswitch, and In all the messages exchanged in the update process initiated by the mobile softswitch, the message sender carries the first identifier information in all the sent messages, and the message receiver confirms according to the first identifier information. After the ongoing update process is initiated by the mobile softswitch, the corresponding operation is performed; and/or the second identification information used to indicate that the bearer parameter update process is initiated by the base station is set, and interacts in the update process initiated by the base station. In all the messages, the message sender carries the second identifier information in all the sent messages, and the message receiver confirms that the ongoing update process is initiated by the base station according to the second identifier information, and then performs corresponding operations.

The method according to claim 5, wherein the reject response message carries a cause value corresponding to the conflict setting of the message.

The method according to claim 7, wherein the response message carrying the rejection information refers to: a bearer parameter update request message carrying the cause value, or a specially extended rejection message.

9. The method according to claim 1, after the base station fails to update the bearer parameters according to the bearer parameter information recommended by the mobile softswitch, the method further includes the following steps: the base station immediately or at a set time At the same time, the update request message is sent to the mobile softswitch again, and the application message carries the bearer parameter information currently recommended by the base station.

10. The method according to claim 1, wherein the bearer parameter refers to an A2p interface bearer parameter.

A control method for updating a bearer parameter, when the bearer parameter update process initiated by the base station side and the mobile soft switch party is interrupted, the control method includes the following steps: a. setting is used to indicate the bearer The parameter update process carries the first identification information initiated by the mobile softswitch, and carries the first identification information in all the messages exchanged in the update process initiated by the mobile softswitch, and/or is configured to indicate the bearer parameter update process. And second identifier information that is sent by the base station, and carries the second identifier information in all messages that are exchanged in the update process initiated by the base station;

c. The bearer parameter update procedure initiated by the mobile softswitch is identified and terminated according to the first identifier information and/or the second identifier information.

The method according to claim 11, wherein when the first identifier information is carried in all the messages exchanged in the update process initiated by the mobile softswitch, the step b specifically includes the following Steps:

The method of claim 11, wherein the step c includes the following steps: the base station receives the first update request message and confirms that the first update request message carries the first identifier After the information, the first update request message is discarded.

The method of claim 11, wherein the step b includes the following steps when the second identifier information is carried in all the messages that are exchanged in the update process initiated by the base station:

After receiving the update response message carrying the second identification information, the mobile softswitch ends monitoring The response time of the second update request message.

The method according to claim 14, wherein the step c includes the following steps: the base station receives the first update request message, and confirms that the second update request message does not carry the second After the information is identified, the first update request message is discarded.

The method according to claim 14, wherein when the first identification information is carried in all the messages exchanged in the update process initiated by the mobile softswitch, the step c is specific. Including the following steps:

The base station receives the first update request message, and confirms that the first update request message does not carry the second identifier or carries the first identifier information, and then discards the first update request message.

The method according to claim 11, wherein after the failure of the bearer parameter update performed by the base station, the method further includes the following steps:

The mobile softswitch sends an update request message to the base station immediately or when the set time expires. The request message carries the bearer parameter information currently carried by the mobile softswitch.

18. The method according to claim 11, wherein the bearer parameter refers to an A2p interface bearer parameter.

19. An update control system for carrying parameters, comprising a base station and a mobile softswitch, characterized by:

The base station includes: a first update processing module, processing related messages that are sent and received by the base station in a bearer parameter update process, where: performing each bearer parameter update request message received from the mobile softswitch;

The system according to claim 19, wherein the mobile softswitch further comprises: a second timer, wherein the second update processing module starts the second timing after transmitting a bearer parameter update request message to the base station The device monitors the response time of the request message, and when receiving the update request message of the base station, determines whether the second timer is in an activated state, and if yes, discards the received from the base station. Update the application message, otherwise execute the update request message.

The system according to claim 19, wherein the base station further comprises: a first timer, after the first update processing module sends a bearer parameter request message to the mobile softswitch, starting the first timer The response time of the application message is monitored, and the first timer is stopped upon receiving the update request message of the mobile softswitch or the reject message of the application message.

22. The system of claim 19, 20 or 21, wherein:

The base station further includes: a first identification information adding/identifying module, and connecting the first update processing module;

The mobile softswitch further includes: a second identification information adding/identifying module, connecting the second update processing module;

The first identifier information adding/identifying module and the second identifier information adding/identifying module are respectively configured to add first identifier information to all messages exchanged in the bearer parameter update process initiated by the base station side, and identify the first identifier. Information; and/or, adding second identification information to all messages interacting in the bearer parameter update process initiated by the mobile softswitch side, and identifying the second identification information.

23. A base station, comprising:

The first timer is connected to the first update processing module, and after the first update processing module sends a bearer parameter request message to the mobile softswitch, the first timer is started to monitor the response time of the application message, and is received. The first timer is stopped when the update request message of the mobile softswitch or the reject message of the application message is responded to.

The base station according to claim 23, wherein the base station further comprises: a first identification information adding/identifying module, connected to the first update processing module; and a bearer parameter update process initiated for the base station side Adding first identification information to all messages in the interaction, and identifying the first identification information; and/or adding second identification information to all messages interacting in the bearer parameter update process initiated by the mobile softswitch side, and identifying the Second identification information.

25. A mobile softswitch, comprising: a second update processing module and a connection to the second update The second timer of the module;

The mobile softswitch of claim 25, wherein the mobile softswitch further comprises:

27. An update control system for carrying parameters, comprising a base station and a mobile softswitch, characterized by:

The first identifier information adding/identifying module and the second identifier information adding/identifying module are respectively configured to add first identifier information to all messages exchanged in the bearer parameter update process initiated by the base station side, and identify the first identifier information. And/or, adding second identification information to all messages exchanged in the bearer parameter update process initiated by the mobile softswitch side, and identifying the second identification information; and outputting the identification result to the corresponding first update processing module And a second update processing module;

The first update processing module and the second update processing module perform a bearer parameter update process initiated by the base station side according to the recognition result, and end the bearer parameter update process initiated by the mobile softswitch.