A METHOD FOR SIGNALING INTERACTION OF ENSURING THE INTERNET PROTOCOL (IP) QUALITY OF SERVICE (QoS)
11 claims: 1 independent, 10 dependent
- 1インターネットプロトコルのサービス品質を保証するシグナリングエクスチェンジ方法であって、独立ベアラ制御レイヤーを備えるネットワークに適用され、 サービスサーバCAが送り元ユーザエージェントUAからのサービスストリームを伝送するリクエストを受信した後、ベアラ制御レイヤーにサービス品質QoSリソースリクエストを送信し、サービス品質QoSリソースリクエストがストリームQoSパラメーター及び宛先UAの情報を含むことと、 送り先リソース管理器CMが、CAからサービス品質QoSリソースリクエストを受信した後、サービス品質QoSリソースリクエストの宛先UAが、送り先CMが属する本管理域にあるかどうかを判断し、 宛先の結果に従ってベアラ制御レイヤーが当該ユーザのサービスストリームにリソースを分配し、リソース分配の結果に基づいてエッジルータERにフローマッピングコマンドを送信することと、 ERがフローマッピングコマンドを受信した後、分配されたリソースに基づいて当該サービスストリームにベアラパスを指定し、ベアラ制御レイヤーを通じて実行の結果をCAに送信することと、 ユーザのサービスストリームがベアラネットワークを通じて伝送された後、CAがベアラ制御レイヤーにゲート制御をクローズする指示を起こし、ベアラ制御レイヤーが当該指示をERに送信し、ERが当該指示に基づいてサービスストリームが本ERを通過することを許さないことと、 CAがベアラ制御レイヤーにゲート制御をオープンする指示を起こし、ベアラ制御レイヤーが当該指示をERに送信し、ERが当該指示に基づいてサービスストリームが本ERを通過することを許可することと、 を含むことを特徴とする方法。
- 2上記QoSリソースリクエストは単方向リソースリクエストであり、 上記ベアラ制御レイヤーがユーザのサービスストリームにリソースを分配することは、送り先ベアラネットワークのリソース管理器CMにより起こし、ベアラ制御レイヤーで上りリソースを分配することであることを特徴とする請求項1に記載の方法。
- 3ベアラ制御レイヤーでの送り先CMがベアラ制御レイヤーにより分配された上りリソースを送り先ERに送信し、送り先ERにフローマッピングコマンド及びゲート制御指示を送信することを更に含み、 上記ERが分配されたリソースに基づいてサービスストリームにベアラパスを指定することは、送り先ERがフローマッピングコマンドを受信した後、上記上りリソースに基づいて当該ユーザのサービスストリームにベアラパスを指定し、ゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することであることを特徴とする請求項2に記載の方法。
- 4上記QoSリソースリクエストは、ゲート制御指示を含み、 ベアラ制御レイヤーでの送り先CMが上りリソース分配の結果情報をCAに送信し、CAが当該上りリソースの分配に成功したことを確定した後、送り先CMにベアラリソースの予約をスタートする指示を送信することと、 送り先CMがベアラリソースの予約をスタートする指示を受信した後、分配された上りリソースを送り先ERに送信し、送り先ERにフローマッピングコマンド及びゲート制御指示を送信することとを更に含み、 上記ERが分配されたリソースに基づいてサービスストリームにベアラパスを指定することは、送り先ERがフローマッピングコマンドを受信した後、上記上りリソースに基づいて当該ユーザのサービスストリームにベアラパスを指定し、ゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することであることを特徴とする請求項2に記載の方法。
- 5上記QoSリソースリクエストは、ゲート制御指示を含み、 ベアラ制御レイヤーでの送り先CMがベアラ制御レイヤーにより分配された上りリソースを送り先ERに送信し、送り先ERにフローマッピングコマンド及びゲート制御指示を送信することを更に含み、 上記CAが実行の結果を受信した後、送り先CMにサービスストリームの活性化をスタートする指示を送信し、送り先CMが当該指示に基づいて送り先ERにゲート制御指示を送信し、送り先ERがゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することを更に含む、ことを特徴とする請求項2に記載の方法。
- 6上記QoSリソースリクエストは、双方向リソースリクエストであり、 上記ベアラ制御レイヤーが当該ユーザのサービスストリームにリソースを分配することは、送り先CMから起こし、ベアラ制御レイヤーで上りリソースを分配し、次に、宛先CMから起こし、ベアラ制御レイヤーで下りリソースを分配することであることを特徴とする請求項1に記載の方法。
- 7上記QoSリソースリクエストは、双方向リソースリクエストであり、 上記ベアラ制御レイヤーが当該ユーザのサービスストリームにリソースを分配することは、送り先CMから起こし、ベアラ制御レイヤーで上りリソースと下りリソースを同時に分配することである、ことを特徴とする請求項1に記載の方法。
- 8ベアラ制御レイヤーでの宛先CMが分配された下りリソースを宛先ERに送信し、フローマッピングコマンド及びゲート制御指示を宛先ERに送信することと、 ベアラ制御レイヤーでの送り先CMが分配された上りリソースを送り先ERに送信し、フローマッピングコマンド及びゲート制御指示を送り先ERに送信することと、を更に含み、 上記ERが分配されたリソースに基づいて当該サービスストリームにベアラパスを指定することは、 宛先ERが上記下りリソースに基づいて当該ユーザのサービスストリームにベアラパスを指定し、ゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することと、 送り先ERが上記上りリソースに基づいて当該ユーザのサービスストリームにベアラパスを指定し、ゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することと、を含む、ことを特徴とする請求項6又は7に記載の方法。
- 9上記QoSリソースリクエストは、ゲート制御指示を含み、 ベアラ制御レイヤーでの送り先CMがリソース分配の結果情報をCAに送信し、CAが上りリソースと下りリソースの分配に成功したことを確定した後、ベアラリソースの予約をスタートする指示を送り先CMに送信することと、 送り先CMがベアラリソースの予約をスタートする指示を受信した後、分配された上りリソースを送り先ERに送信し、フローマッピングコマンド及びゲート制御指示を送り先ERに送信することと、 送り先CMがベアラ制御レイヤーを通じて分配された下りリソースを宛先CMに送信し、宛先CMが宛先ERにフローマッピングコマンド及びゲート制御指示を送信することと、を更に含み、 上記ERが分配されたリソースに基づいてサービスストリームにベアラパスを指定することは、 送り先ERがフローマッピングコマンドを受信した後、上記上りリソースに基づいて当該ユーザのサービスストリームにベアラパスを指定し、ゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することと、 宛先ERがフローマッピングコマンドを受信した後、上記下りリソースに基づいて当該ユーザのサービスストリームにベアラパスを指定し、ゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することと、を含む、ことを特徴とする請求項6又は7に記載の方法。
- 10上記QoSリソースリクエストは、ゲート制御指示を含み、 ベアラ制御レイヤーでの宛先CMが分配された下りリソースを宛先ERに送信し、フローマッピングコマンド及びゲート制御指示を宛先ERに送信することと、 ベアラ制御レイヤーでの送り先CMが分配された上りリソースを送り先ERに送信し、フローマッピングコマンド及びゲート制御指示を送り先ERに送信することと、を更に含み、 上記CAが実行の結果を受信した後、 送り先CMにサービスストリームの活性化をスタートする指示を送信し、送り先CMが当該指示に基づいて送り先ERにゲート制御指示を送信し、送り先ERがゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することと、 送り先CMがベアラ制御レイヤーを通じて当該指示を宛先ERに送信し、宛先ERがゲート制御指示に基づいてサービスストリームが本ERを通過することを許可することと、を更に含むことを特徴とする請求項6又は7に記載の方法。
- 11上記ERがベアラ制御レイヤーを通じて実行の結果をCAに送信することは、送り先ERがベアラ制御レイヤーでの送り先CMを通じて実行の結果をCAに送信することであることを特徴とする請求項1に記載の方法。
Independent claims11
104 paragraphs, as filed
The present invention relates to Signaling Exchange technology, in particular to a signaling exchange method that guarantees quality of service (QoS) of the Internet Protocol (IP).
With the ever-increasing scale of the Internet network and the emergence of various network services and advanced multimedia systems, the Internet network has always been a sudden file transfer protocol (FTP), or hypertext containing image files. You need to send multimedia services such as Transfer Protocol (HTTP). For real-time services in a network, the impact on real-time services when the network sends services such as FTP or HTTP because it is more sensitive to characteristics such as network transmission time delays and delay fluctuations. Is larger. Then, multimedia services occupy a large amount of network bandwidth, and it is difficult to reliably transmit essential services that require bandwidth guarantee in existing networks.
In response to the above problems, the industry has submitted various QoS technologies. For example, the Internet Engineering Task Force (IETF) has established many service models and mechanisms to meet network demands. Among these QoS technologies, a technology proposed to the IETF that uses an integrated services model (Int-Serv) for network access and edges and a differentiated services model (Diff-Serv) at the core of the network. Is industry licensed. Since Diff-Serv in the plan guarantees QoS by setting only the priority, the transmission of the entire network is performed even though the network using the plan has the characteristic of high circuit utilization rate. It is difficult to guarantee reliability and transmission effect.
IP QoS between the service control layer and resource managers and between resource managers to determine if the resources in each control area meet the demands of the conversation when the path of the user's service stream is determined. It is necessary to perform the signaling exchange of, and the resource reservation method is determined at the request of the service provider. As can be seen, the IP QoS signaling process is an important factor in guaranteeing QoS in bearer networks. However, at this time, there is no unified IP QoS signaling process yet.
<p> The present invention has been made in view of the above, and by providing a signaling exchange method that guarantees IP QoS, a network of Diff-Serv models having an independent bearer control layer can stream a user's service stream according to the signaling exchange method. The main purpose is to be able to determine the bearer path of.</p>
<p> In order to achieve the above object, the technical plan of the present invention has been realized as follows. A signaling exchange method that guarantees the quality of service of the Internet Protocol and is applied to networks with an independent bearer control layer. The method includes the following steps: After the service server CA receives the request to transmit the service stream from the source user agent UA, it sends a service quality QoS resource request to the bearer control layer, and the service quality QoS resource request provides the stream QoS parameters and destination UA information. To include and After the destination resource manager CM receives the service quality QoS resource request from the CA, it determines whether the destination UA of the service quality QoS resource request is in the control area to which the destination CM belongs. The bearer control layer distributes resources to the user's service stream according to the result of the destination, and sends a flow mapping command to the edge router ER based on the result of resource allocation. After the ER receives the flow mapping command, it specifies a bearer path for the service stream based on the distributed resources and sends the execution result to the CA through the bearer control layer.<u style="single">、</u><u style="single">After the user's service stream is transmitted through the bearer network, the CA instructs the bearer control layer to close the gate control, the bearer control layer sends the instruction to the ER, and the ER bases the service stream on the instruction. Do not allow it to pass through this ER and</u><u style="single">The CA instructs the bearer control layer to open the gate control, the bearer control layer sends the instruction to the ER, and the ER allows the service stream to pass through the ER based on the instruction.</u>。 </p><p> The above QoS resource request is a one-way resource request.<u style="single"> Up</u>Note Distributing resources to the user's service stream by the bearer control layer is caused by the resource manager CM of the destination bearer network, and the upstream resources are distributed by the bearer control layer.</p><p><u style="single"> Be</u>The destination CM in the Ara control layer sends the upstream resources distributed by the bearer control layer to the destination ER, and sends the flow mapping command and gate control instruction to the destination ER.<u style="single">Including</u>、<u style="single"> Up</u>Note Specifying a bearer path for the service stream based on the distributed resource means that after the destination ER receives the flow mapping command, the bearer path is specified for the user's service stream based on the above upstream resource, and gate control is performed. Allowing the service stream to pass through this ER according to the instructions.</p><p> The above QoS resource request is a gate control instruction.<u style="single">Including</u>Can be<u style="single"> Be</u>The destination CM in the Ara control layer sends the result information of the uplink resource distribution to the CA, and after confirming that the CA has succeeded in distributing the uplink resource, sends an instruction to start the bearer resource reservation to the destination CM.<u style="single">When</u>、<u style="single"> Send</u>After the destination CM receives the instruction to start the reservation of the bearer resource, the distributed uplink resource is sent to the destination ER, and the flow mapping command and gate control instruction are sent to the destination ER.<u style="single">And further included</u>、<u style="single"> Up</u>Note Specifying a bearer path for the service stream based on the distributed resource means that after the destination ER receives the flow mapping command, the bearer path is specified for the user's service stream based on the above upstream resource, and gate control is performed. Allowing the service stream to pass through this ER according to the instructions.</p><p> The above QoS resource request is a gate control instruction.<u style="single">Including</u>Can be<u style="single"> Be</u>The destination CM in the Ara control layer sends the upstream resources distributed by the bearer control layer to the destination ER, and sends the flow mapping command and gate control instruction to the destination ER.<u style="single">Including</u>、<u style="single"> Up</u>After the CA receives the execution result, it sends an instruction to start the activation of the service stream to the destination CM, the destination CM sends a gate control instruction to the destination ER based on the instruction, and the destination ER controls the gate. It further includes allowing the service stream to pass through this ER on the basis of instructions.</p><p> The above QoS resource request is a bidirectional resource request.<u style="single"> Up</u>Note: When the bearer control layer distributes resources to the service stream of the user, it originates from the destination CM, distributes the upstream resource at the bearer control layer, then originates from the destination CM, and distributes the downstream resource at the bearer control layer. That is.</p><p> The above QoS resource request is a bidirectional resource request.<u style="single"> Up</u>Note: The bearer control layer distributes resources to the service stream of the user, which is caused by the destination CM and simultaneously distributes the upstream resource and the downstream resource in the bearer control layer.</p><p><u style="single"> Be</u>Sending the downlink resource to which the destination CM is distributed in the Ara control layer to the destination ER, and sending the flow mapping command and gate control instruction to the destination ER, Sending the upstream resource to which the destination CM in the bearer control layer is distributed to the destination ER, and sending the flow mapping command and gate control instruction to the destination ER.<u style="single">Furthermore</u>Including<u style="single"> Up</u>Note ER can specify a bearer path for the service stream based on the distributed resources. The destination ER specifies a bearer path to the user's service stream based on the downlink resource, and allows the service stream to pass through this ER based on the gate control instruction. This includes that the destination ER specifies a bearer path for the user's service stream based on the upstream resource and allows the service stream to pass through the ER based on the gate control instruction.</p><p> The above QoS resource request is a gate control instruction.<u style="single">Including</u>Mi,<u style="single"> Be</u>The destination CM in the Ara control layer sends the resource distribution result information to the CA, and after confirming that the CA has succeeded in distributing the upstream and downstream resources, sends an instruction to start the reservation of the bearer resource to the destination CM. To do<u style="single">When</u>、<u style="single"> Send</u>After the destination CM receives the instruction to start the reservation of the bearer resource, the distributed uplink resource is sent to the destination ER, and the flow mapping command and the gate control instruction are sent to the destination ER. The destination CM sends the downlink resources distributed through the bearer control layer to the destination CM, and the destination CM sends the flow mapping command and gate control instruction to the destination ER.<u style="single">Furthermore</u>Including<u style="single"> Up</u>Note that specifying a bearer path for a service stream based on the distributed resources of the ER is After the destination ER receives the flow mapping command, specify a bearer path for the user's service stream based on the above upstream resource, and allow the service stream to pass through this ER based on the gate control instruction. After the destination ER receives the flow mapping command, it includes specifying a bearer path for the user's service stream based on the downlink resource and allowing the service stream to pass through this ER based on the gate control instruction. ..</p><p> The above QoS resource request is a gate control instruction.<u style="single">Including</u>Mi,<u style="single"> Be</u>Sending the downlink resource to which the destination CM is distributed in the Ara control layer to the destination ER, and sending the flow mapping command and gate control instruction to the destination ER, Sending the upstream resource to which the destination CM in the bearer control layer is distributed to the destination ER, and sending the flow mapping command and gate control instruction to the destination ER.<u style="single">Furthermore</u>Including<u style="single"> Up</u>After the CA receives the result of the execution An instruction to start activation of the service stream is sent to the destination CM, the destination CM sends a gate control instruction to the destination ER based on the instruction, and the destination ER passes the service stream through this ER based on the gate control instruction. Allowing to do and It further includes that the destination CM sends the instruction to the destination ER through the bearer control layer, and the destination ER allows the service stream to pass through the ER based on the gate control instruction.</p><p><u style="single"> Up</u>When the ER sends the execution result to the CA through the bearer control layer, the destination ER sends the execution result to the CA through the destination CM in the bearer control layer.</p>
<p> In the present invention, after the CA receives the transmission request of the service stream, the bearer control layer requests the distribution of resources, the bearer control layer distributes the resources, and then the flow mapping is applied to the ER based on the result of the resource distribution. By doing so, the ER provided the bearer path for the service stream, providing an IP QoS signaling process for the service stream, and networks with an independent bearer control layer made distribution to the bearer path much more convenient.</p><p> Further, the present invention provides single-step and two-step IP QoS signaling processes. The single stage sends the flow mapping to the ER and opens the gate control without passing the instruction of the CA. In both stages, after the distribution of resources in the bearer control layer is completed, the gate control instruction can be sent to the ER after receiving the instruction sent from the CA. Therefore, a single-step IP QoS signaling process should be performed when other information exchanges are required before the user's service stream is transmitted, or when the service provider does not need to strictly determine the charging point. use. Of course, if strict charging divisions are required within or between service providers, or if the service provider has other special requirements, the two-step signaling process provided in the present invention is adopted. Good. That is, the method of the present invention allows the network to adopt different measures based on different demands, and thus is highly adaptable.</p><p> Further, the signaling process provided in the present invention transmits the service stream through the bearer network, but transmits the information flow through the bearer control layer to ensure the safety and reliability of the signaling transmission.</p>
As an invention concept of the present invention, the conversation / service control function entity (SeCFE / SvCFE) sends a QoS resource request to the bearer control layer after receiving a request for transmission of the service stream from the user, and the bearer control layer Based on the received QoS resource request, the resource is distributed to the service stream of the user, and the exchange function entity (SFE) performs flow mapping based on the resource distributed to the bearer control layer, specifies the bearer path of the service stream, and specifies the bearer path of the service stream. Send the execution result information to the CA. The conversation / service control function entity may be a service server (CA). The exchange function entity is an edge router (ER).
When distributing resources, the system may both need to distribute only unidirectional streams and it may need to distribute bidirectional streams. Here, the unidirectional stream transmits the service stream of the source user, and the bidirectional stream transmits the service stream of the source user and the destination user. As such, the present invention provides a reasonable processing process for these two situations. Next, these two types of processing processes will be described in detail by linking the drawings with specific examples.
First, the situation of a unidirectional stream will be described.
In the IP QoS signaling process of a unidirectional stream, single-step processing and bi-step processing can be performed. Specifically, the single-step process is to send the flow mapping to the ER and open the gate control after the bearer control layer finishes distributing the resources without passing the instruction of the CA, and the two-step process. That is, after the bearer control layer finishes distributing resources, it always receives the instruction sent from the CA and then sends the gate control instruction to the ER.
First, as shown in the process shown in FIG. 2, a single-step work procedure of the IP QoS signaling process of a unidirectional stream will be described. The work procedure includes the following steps.
In step 201, after receiving the request to transmit the service stream of the source user agent (UA), the CA sends a QoS resource request containing the stream QoS parameters and destination UA information to the destination CM.
In step 202, after receiving the QoS resource request transmitted from the CA, the destination CM determines whether the destination of the resource request is in the control area, and if it is not in the control area, it is sent to the service stream of the user. After distributing the uplink resources in this area, the QoS resource request is transferred to the intermediate CM, that is, the intermediate bearer control function entity (Intermediate BCFE). If not, the upstream resources of the main area are distributed to the service stream of the user, and then the process proceeds to step 206.
In step 203, after receiving the QoS resource request, the intermediate CM distributes the upstream resources of the region to the service stream of the user, and then makes a QoS resource request to the destination CM, that is, the destination bearer control function entity (Destination BCFE). Forward.
In step 204, after receiving the QoS resource request, the destination CM distributes the uplink resources of the main region to the service stream of the user, and sends the uplink resources back to the intermediate CM.
In step 205, the intermediate CM merges the uplink resource transmitted from the destination CM with the uplink resource distributed by itself, and sends the processed uplink resource back to the destination CM.
In step 206, the destination CM merges the uplink resource transmitted from the intermediate CM with the uplink resource distributed by itself, and gates the uplink resource and flow mapping command to the destination ER, that is, the destination exchange function entity (Source SFE). Send control instructions.
In step 207, the destination ER specifies a bearer path for the user's service stream based on the flow mapping command and uplink resource sent from the destination CM, and the service stream is set to this ER based on the gate control instruction sent from the destination CM. After allowing to pass through, the result of execution is sent back to the destination CM.
In step 208, the destination CM receives the execution result transmitted from the destination ER, and then transmits the execution result to the CA.
When the destination CM confirms that the bearer path has been successfully specified based on the execution result, the success information is included in the execution result sent by the CM to the CA. When the destination CM determines that the bearer path specification has failed based on the execution result, the failure information is included in the execution result.
The above is a single-step processing procedure for a unidirectional stream IP QoS signaling process. Next, the processing procedure of both stages of the unidirectional stream IP QoS signaling process will be described.
In the two-stage signaling process, the distributed resources may be held in the destination CM or in the destination ER before sending the gate control instruction to the destination ER. First, based on FIG. 3, the work procedure of holding resources in the CM will be described at both stages of the IP QoS signaling process. The implementation procedure corresponds to the following steps.
In step 301, after receiving the request to transmit the service stream of the destination UA, the CA sends a QoS resource request containing the stream QoS parameters, gate control instructions, and destination UA information to the destination CM.
In step 302, after receiving the QoS resource request transmitted from the CA, the destination CM determines whether the destination of the resource request is in the control area, and if it is not in the control area, it is sent to the service stream of the user. After distributing the uplink resources in this area, the QoS resource request is transferred to the intermediate CM. If not, the upstream resources of the main area are distributed to the service stream of the user, and then the process proceeds to step 306.
In step 303, after receiving the QoS resource request, the intermediate CM distributes the uplink resources of the main region to the service stream of the user, and then transfers the QoS resource request to the destination CM.
In step 304, after receiving the QoS resource request, the destination CM distributes the uplink resources of the main region to the service stream of the user, and sends the uplink resources back to the intermediate CM.
In step 305, the intermediate CM merges the uplink resource transmitted from the destination CM with the uplink resource distributed by itself, and sends the processed uplink resource back to the destination CM.
In step 306, the destination CM merges the uplink resource transmitted from the intermediate CM and the uplink resource distributed by itself, and sends the merged uplink resource back to the CA.
What is carried in the distribution result of the resource may be success information or failure information.
In step 307, if the information carried in the distribution result of the received resource is success information, the CA sends an instruction to the destination CM to start the reservation of the bearer resource. If the information is failure information, the processing process is terminated.
In step 308, the destination CM performs flow mapping to the destination ER based on the received instruction and the uplink resource received in step 306, and transmits the gate control instruction to the destination ER.
In step 309, the destination ER executes the flow mapping command sent from the destination CM, specifies the bearer path of the user's service stream, and allows the user's service stream to pass through this ER based on the gate control instructions. Then, the execution result is sent back to the destination CM.
In step 310, the destination CM receives the execution result transmitted from the destination ER, and then transmits the execution result to the CA.
Compared to the single-step work procedure shown in Fig. 4, the above procedure adds a procedure to send back the distribution result information of the upstream resource to the CA after the destination CM completes the distribution of the resource. If the resource distribution fails, the CA does not need to perform the subsequent steps, and if the resource distribution is successful, the CA sends an instruction to start the reservation of the bearer resource to the destination CM. In this processing process, the CA controls the service stream to pass through the ER in response to demand, thus allowing precise control of the charging point and keeping the bearer and control in sync.
As shown in FIG. 4, the work procedure for holding resources in the ER corresponds to the following steps at both stages of the unidirectional stream IP QoS signaling process.
In step 401, after receiving the request to transmit the service stream of the destination UA, the CA sends a QoS resource request containing the stream QoS parameters, gate control instructions, and destination UA information to the destination CM.
In step 402, after receiving the QoS resource request transmitted from the CA, the destination CM determines whether the destination of the resource request is in the control area, and if it is not in the control area, the service stream of the user. After distributing the uplink resources of this area to the intermediate CM, the QoS resource request is transferred to the intermediate CM. If not, the upstream resources of the main area are distributed to the service stream of the user, and then the process proceeds to step 406.
In step 403, after receiving the QoS resource request, the intermediate CM distributes the uplink resources of the main region to the service stream of the user, and then transfers the QoS resource request to the destination CM.
In step 404, after receiving the QoS resource request, the destination CM distributes the uplink resources of the main region to the service stream of the user, and sends the distributed uplink resources back to the intermediate CM.
In step 405, the intermediate CM merges the uplink resource transmitted from the destination CM and the uplink resource distributed by itself, and sends the processed uplink resource back to the destination CM.
In step 406, the destination CM merges the uplink resource transmitted from the intermediate CM and the uplink resource distributed by itself, sends the merged uplink resource to the destination ER, and sends a flow mapping command to the destination ER. To do.
At step 407, the destination ER executes the flow mapping command sent from the destination CM, specifies the bearer path of the user's service stream based on the distributed uplink resources, and then sends the result of the execution back to the destination CM.
In step 408, the destination CM receives the execution result transmitted from the destination ER, and then transmits the execution result to the CA.
In step 409, if the information carried in the received execution result is success information, the CA sends an instruction to the destination CM to start the service stream activation procedure. If the information is failure information, the processing process is terminated.
In step 410, after receiving the instruction, the destination CM sends a command to open the gate control to the destination ER so that the service stream passes through the destination ER.
All of the above are the distribution status of unidirectional streams. Regarding the distribution status of the bidirectional stream, the bidirectional stream can be divided into two unidirectional streams, upstream and downstream, depending on the service provider's request or other circumstances, that is, resources can also be distributed separately. For each of these unidirectional streams, the above unidirectional stream realization process can be adopted. Specifically, the upstream unidirectional stream is resource-distributed by the destination CM, and the downstream unidirectional stream is resource-distributed by the destination CM. That is, the destination CM receives the QoS resource request transmitted from the destination CM, causes resource distribution, and then sends the resource distribution result back to the destination CM. After confirming that the destination CM succeeds in distributing the upstream and downstream resources, the distribution success information is sent back to the CA.
When distributing a bidirectional stream, the upstream and downstream can be distributed in a unified manner. That is, each CM distributes the upstream resource and the downstream resource at the same time. First, a detailed explanation will be given regarding the situation in which ascending and descending are set and distributed in a unified manner. Regarding the situation where upstream and downstream are set and distributed in a unified manner, there are two situations, one is a single stage and the other is a two-stage, and there are two situations in which resources are similarly held in CM and ER in the implementation procedure of both stages. Therefore, each of these two processing procedures will be described next.
Figure 5 shows a single-step procedure for the IP QoS signaling process bidirectional stream, which corresponds to the steps below.
In step 501, after receiving the request to transmit the service stream of the destination UA, the CA sends a QoS resource request containing the stream QoS parameters and the destination UA information to the destination CM.
The QoS resource request must be a bidirectional resource request.
In step 502, after receiving the QoS resource request transmitted from the CA, the destination CM determines whether the destination of the resource request is in the control area, and if it is not in the control area, the service stream of the user. Allocate resources in this area to. The distributed resources in the main area include upstream resources for the upstream stream and downstream resources for the downstream stream. Then, at the same time as transferring the QoS resource request to the intermediate CM, the downlink resource distributed by the present CM is transmitted to the intermediate CM, and step 503 is executed. If not, the upstream and downstream resources of the main area are distributed to the service stream of the user, and then the process proceeds to step 508.
In step 503, after receiving the QoS resource request, the intermediate CM distributes the uplink and downlink resources of the main region to the service stream of the user, and the downlink resource transmitted from the destination CM and the downlink resource distributed by itself. After the merger process, the QoS resource request is transferred to the destination CM, and the downlink resource after the merger is sent to the destination CM. In step 504, after receiving the bidirectional QoS resource request, the destination CM distributes the uplink and downlink resources of the main region to the service stream of the user, and is distributed by the downlink resources transmitted from the intermediate CM and itself. After the merged processing with the downlink resource, the flow mapping command and the gate control instruction are transmitted to the destination ER based on the downlink resource after processing, and the downlink resource after processing is transmitted to the destination ER.
In a single-step processing procedure, the flow mapping is transmitted and the gate control instruction is transmitted.
In step 505, after receiving the flow mapping command and the gate control instruction, the destination ER distributes the bearer path to the service stream of the user, allows the service stream of the user to pass through the ER, and then executes. The result of is sent back to the destination CM.
In step 506, the destination CM sends the upstream resource of this CM back to the intermediate CM after receiving the execution result.
In step 507, the intermediate CM merges the received uplink resource with the uplink resource distributed by itself, and transmits the processed resource allocation result to the destination CM.
In step 508, the destination CM similarly merges the received uplink resource and the uplink resource distributed by itself, and if the distributed uplink resource is successful, sends the uplink resource to the destination ER and flows. Send mapping commands and gate control instructions to the destination ER.
In step 509, the destination ER executes a flow mapping command, specifies the bearer path of the user's service stream based on the uplink resources, and allows the user's service stream to pass through this ER based on the gate control instructions. Then, the execution result is sent back to the destination CM.
In step 510, the destination CM receives the result of the execution sent back from the destination ER, and then sends the result of the execution to the CA.
The above is a single-step processing procedure for a bidirectional stream IP QoS signaling process. For both stages of the bidirectional stream IP QoS signaling process, the distributed resources can be held in the CM or in the ER. The process corresponding to the former method is shown in FIG. 6, and the process corresponding to the later method is shown in FIG. Next, each of these two types of methods will be described.
As shown in FIG. 6, the processing procedure for controlling resources by CM is realized through the following steps.
In step 601, after receiving the request to carry the service stream of the destination UA, the CA sends a QoS resource request containing the stream QoS parameters, gate control instructions, and destination UA information to the destination CM.
The QoS resource request must be a bidirectional resource request.
In step 602, after receiving the QoS resource request transmitted from the CA, the destination CM determines whether the destination of the resource request is in the control area, and enters the control area.<u style="single">If not</u>After distributing the uplink and downlink resources of the main area to the service stream of the user, the QoS resource request is transferred to the intermediate CM, and at the same time, the downlink resources distributed by the CM are transmitted to the intermediate CM. If not, the upstream and downstream resources of the main area are distributed to the service stream of the user, and then the process proceeds to step 606.
In step 603, after receiving the QoS resource request, the intermediate CM distributes the uplink and downlink resources of the main region to the service stream of the user, and the downlink resource transmitted from the destination CM and the downlink resource distributed by itself. After the merger process, the QoS resource request is transferred to the destination CM, and the downlink resource after the merger is sent to the destination CM.
In step 604, after receiving the QoS resource request, the destination CM distributes the uplink and downlink resources of the main region to the service stream of the user, and the downlink resource transmitted from the intermediate CM and the downlink resource distributed by itself. After merging with, the upstream resources distributed by itself are transmitted to the intermediate CM.
In step 605, the intermediate CM merges the uplink resources transmitted from the destination CM and the uplink resources distributed by itself, and sends the processed uplink resources back to the destination CM.
In step 606, the destination CM merges the uplink resource transmitted from the intermediate CM and the uplink resource distributed by itself, and sends back the distribution result of the uplink and downlink resources to the CA.
In step 607, when the resource distribution result includes success information, the CA sends an instruction to start the bearer resource reservation procedure to the destination CM, and the destination CM receives the instruction and then simultaneously steps 608 and 610. To start.
In step 608, the destination CM sends a flow mapping command and a gate control instruction to the destination ER based on the CA's instruction and the upstream resource determined before that, and then proceeds to step 609.
In step 609, the destination ER executes a flow mapping command to specify a bearer path for the user's service stream based on the uplink resources distributed to the bearer control layer, and that the user's service stream passes through this ER. After permitting, the execution result information is sent to the destination CM, and then the process proceeds to step 616.
In steps 610 to 611, the destination CM transmits the instruction received through the intermediate CM to the destination CM.
In fact, the destination CM can directly transmit the received instruction to the destination CM without going through the intermediate CM.
At step 612, the destination CM sends a flow mapping command and a gate control instruction to the destination ER based on the downlink resources distributed in front of it.
At step 613, the destination ER executes the flow mapping command, specifies the bearer path of the traffic service based on the downlink resource, allows the user's service stream to pass through this ER, and then determines the result of the execution. Send back to the destination CM.
In steps 614 to 615, the destination CM sends the execution result to the destination CM through the intermediate CM.
Similarly, the destination CM can send the execution result directly to the destination CM without going through the intermediate CM.
At step 616, the destination CM sends the result of the execution to the CA.
Figure 7 shows the processing procedure for holding resources in the ER. The procedure is realized by the following steps.
In step 701, after receiving the request to transmit the service stream of the destination UA, the CA sends a QoS resource request including stream QoS parameters, gate control instructions and destination UA information to the destination CM.
The QoS resource request must be a bidirectional resource request.
In step 702, after receiving the QoS resource request sent from the CA, the destination CM determines whether the destination of the resource request is in the control area, and enters the control area.<u style="single">If not</u>, Distribute the upstream and downstream resources of the main area to the service stream of the user, and then transfer the QoS resource request to the intermediate CM.<u style="single">At the same time, the downlink resources distributed by this CM are transmitted to the intermediate CM.</u>.. If not, the upstream and downstream resources of the main area are distributed to the service stream of the user, and then the process proceeds to step 708.
In step 703, after receiving the QoS resource request, the intermediate CM distributes the uplink and downlink resources of the main region to the service stream of the user, and the downlink resource transmitted from the destination CM and the downlink resource distributed by itself. After the merger process, the QoS resource request is transferred to the destination CM, and the downlink resource after the merger is sent to the destination CM.
In step 704, after receiving the QoS resource request, the destination CM distributes the uplink and downlink resources of the main region to the service stream of the user, and the downlink resource transmitted from the intermediate CM and the downlink resource distributed by itself. After merging with, a flow mapping command is sent to the destination ER based on the downlink resources after the merger.
In step 705, after receiving the flow mapping command, the destination ER specifies the bearer path of the user's service stream based on the downlink resource, and sends the execution result back to the destination CM.
At step 706, after receiving the result of the execution, the destination CM sends the upstream resource distributed in front of it back to the intermediate CM.
In step 707, the intermediate CM merges the received uplink resource and the uplink resource distributed by itself, and transmits the processed uplink resource to the destination CM.
In step 708, the destination CM merges the received uplink resource and the uplink resource distributed by itself, and when the uplink resource is successfully distributed, sends a flow mapping command to the destination ER based on the uplink resource. To do.
In step 709, the destination ER executes the flow mapping command, specifies the bearer path of the user's service stream based on the upstream resource, and then sends the execution result back to the destination CM.
In step 710, the destination CM receives the execution result of the destination ER and then sends the execution result information back to the CA.
At step 711, if the distribution result contains success information, the CA instructs the destination CM to start the service stream activation procedure, causing steps 712 and 713 to start at the same time. If the distribution result contains failure information, this processing process is terminated.
At step 712, the destination CM sends an instruction to open the gate control to the destination ER, allowing the service stream to pass through.
Up to this point, the user's service stream can pass through the destination ER into pre-distributed bearer resources.
In steps 713 to 714, the destination CM transmits a gate control instruction to the destination CM through the intermediate CM.
Of course, the destination CM can also directly transfer the gate control instruction to the destination CM without passing through the intermediate CM.
At step 715, the destination CM sends a gate control instruction to the destination ER, allowing the user's service stream to pass through.
Through the above process, the user's service stream can realize bidirectional distribution.
Regarding the situation where the bearer control layer distributes the upstream resource and the downstream resource separately, the specific processing procedure after completing the resource distribution is the processing when the above upstream and downstream are set and distributed uniformly. Since it is the same as the procedure, it is omitted.
After specifying the bearer path through any of the above steps, the user's service stream can traverse the bearer network, establishing a conversation between the users. However, after the conversation is established, the CA can instruct the bearer control layer to close or open the gate control at any time on demand. For example, when the CA attempts to terminate the transmission of the service stream, it sends an instruction to close the gate control. After closing the service stream, if the service stream needs to be retained or restored, the CA retransmits the instruction to open the gate control. The CM sends the instruction to the ER, which executes the instruction and allows or disallows the service stream to pass through the ER.
Specifically, if the service stream is a unidirectional stream, the CA sends an instruction to the destination CM, the destination CM sends the instruction to the destination ER, and the destination ER is based on the instruction that the service stream is the ER. Allow or disallow passing through.
If the service stream is a bidirectional stream, after the CA sends the instructions to the destination CM, the destination CM not only sends the instructions to the destination ER, but also the instructions to the destination CM through the bearer control layer. In addition, the destination CM sends the instruction to the destination ER. Of course, the destination and destination ERs allow or do not allow the service stream to pass through the ER based on the instructions.
The above contents are merely preferable examples of the present invention, and do not limit the scope of protection of the present invention.
<figref num="1">It is a figure which shows the Diff-Serv model which has the existing independent bearer control layer.</figref><figref num="2">It is a single-step flowchart of the IP QoS signaling process of a unidirectional stream in the present invention.</figref><figref num="3">It is a flowchart in which resources are held in CM at both stages of the IP QoS signaling process of a unidirectional stream in the present invention.</figref><figref num="4">FIG. 5 is a flowchart in which resources are held in the ER at both stages of the unidirectional stream IP QoS signaling process in the present invention.</figref><figref num="5">It is a one-step flowchart of the bidirectional stream IP QoS signaling process in the present invention.</figref><figref num="6">It is a flowchart in which resources are held in CM at both stages of the bidirectional stream IP QoS signaling process in the present invention.</figref><figref num="7">FIG. 5 is a flowchart in which resources are held in the ER at both stages of the bidirectional stream IP QoS signaling process in the present invention.</figref>
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2002314587A | Cites | Japan |
| JP2001156838A | Cites | Japan |
| JP2002374286A | Cites | Japan |
| JP2003534716A | Cites | Japan |
| WO03094447A1 | Cites | World Intellectual Property Organization (WIPO) |
13 members in 7 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 200410070400 | China | A | |
| 200410070400 | China | A | |
| 2004100704006 | China | – | |
| 2005001177 | China | W | |
| 2005001177 | China | W | |
| 20042004070400 | – | – | – |
| 2005001177 | – | – | – |
| CN2004170400 | – | – | – |
| WO2005CN01177 | – | – | – |
Members13
| Document | Office | Kind | |
|---|---|---|---|
| WO2006012794A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CN1735092A | China | A | |
| EP1760935A1 | European Patent Office (EPO) | A1 | |
| US2007147389A1 | United States of America | A1 | |
| JP2008508820A | Japan | A | |
| CN100514961C | China | C | |
| EP1760935A4 | European Patent Office (EPO) | A4 | |
| US7751349B2 | United States of America | B2 | |
| EP1760935B1 | European Patent Office (EPO) | B1 | |
| AT484900T | Austria | T | |
| ATE484900T1 | Austria | T1 | |
| DE602005024135D1 | Germany | D1 | |
| JP4701246B2This record | Japan | B2 |
29 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Transfer to examiner for re-examination before appeal (zenchi)AppealJAPANESE INTERMEDIATE CODE: A911A911 | A911 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A821A521 | A521 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Notification of resignation of power of attorneyJAPANESE INTERMEDIATE CODE: A7424RD04 | RD04 |
Numbers
- Publication
- 4701246
- Publication, DOCDB
- 4701246
- Publication, EPODOC
- JP4701246B
- Application
- 2007524159
- Application, DOCDB
- 2007524159
- Application, EPODOC
- JP20070524159
Titles2
- Japanese
- インターネットプロトコルのサービス品質を保証するシグナリングエクスチェンジ方法
- English
- Signaling exchange method that guarantees the quality of service of the Internet Protocol
Classification
- CPC, 6
- H04L41/5054
- H04L12/2856
- H04L47/724
- H04L47/785
- H04L47/805
- H04L47/70
- IPC, 2
- H04L12 56
- H04L47 724
