JP2011142385A - Charging method and qos network system between network domains - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To clarify the corresponding state of each domain to a network resource in response to a QoS request from a user. <P>SOLUTION: A first terminal of a first network and a second terminal of a second network perform QoS communication astride the respective networks. The communication equipment of the first network transmits a session start request including request QoS information from the first terminal to the second network. The communication equipment of the second network checks whether to allow the securement of a communication resource for achieving QoS shown by the request QoS information in the second network. When the communication resource cannot be secured, first penalty charging information for paying a penalty charge to the first network from the second network is registered, and the request QoS information is changed in accordance with the communication resource secured in the second network and reported to the communication equipment of the first network. The communication equipment of the first network checks whether to allow the securement of a communication resource for achieving QoS shown by the request QoS information in the first network. When the communication resource cannot be secured, second penalty charging information for paying a penalty charge to the second network from the first network is registered. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a billing method and a QoS network system between network domains, and more particularly to a billing method and a QoS network system between network domains for performing communication guaranteeing QoS between different network domains.

As for standards in recent IP networks, multimedia subsystems (IP Multimedia Subs), which have been studied by 3GPP (Third Generation Partnership Project) and 3GPP2 (Third Generation Partnership Project 2), which are standards for wireless systems, have become multimedia standards (IP Multimedia Subs). Yes. In addition, ITU-T (International Telecommunication Union-Telecommunication Standardization sector) is established as a standard of NGN (Next Generation Network) in which 3GPP standards are incorporated for authentication, service determination, and billing.
As a method for realizing a service (QoS service) that guarantees communication quality, bandwidth and priority in the NGN and IMS network system instead of the conventional Internet, for example, a method as shown in Patent Document 1 can be used. Information for realizing the QoS service is transmitted from the IMS system of the domain to the IMS system of the destination user domain by the description of the SDP header part in the SIP protocol. Regarding charging for users, charging information is transmitted from the domain SIP server to the charging function when a SIP session is transmitted or when QoS conditions are changed.
The communication network has a domain for each carrier, and a plurality of the domains are connected to each other, and the domain is divided into an access system to which a user connects and a relay system to connect the access systems. Regarding the QoS, when using a relay system, the priority and bandwidth of each user's QoS are not considered, and the QoS priority and bandwidth reservation are generally referred to as edge nodes having contact points with the access network. Part.
In the conventional system, it has been studied to secure network resources across multiple networks for the bandwidth and priority requested by the originating user, and the connection of the user when the network side cannot secure the bandwidth and priority In general, it is considered to reduce the charging of the user.

JP 2006-87133 A JP 2008-22312 A Special table 2009-515382 gazette

IETF standard RFC 3312, "Integration of Resource Management and Session Initiation Protocol (SIP)" IETF standard RFC 3556, “Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP). Bandwidth” IETF standard RFC 3312, "Integration of Resource Management and SIP" IETF standard RFC 4032, “Update to the Session Initiation Protocol (SIP) Preconditions Framework” IETF standard RFC 4566, "SDP: Session Description Protocol" IETF standard RFC 5027, “Security Preconditions for Session Description Protocol (SDP) Media Streams”

A contract is established between the user and the domain that defines the maximum available bandwidth corresponding to the priority of the QoS, and similarly, the maximum bandwidth that can be communicated between the domains is guaranteed, and the domain according to the QoS priority and bandwidth used for communication. Contracts that charge each other may be signed. At this time, when establishing a communication session between different domains, the QoS requested by the user within the range of the maximum bandwidth in the user's contract by a domain having an access network for which QoS priority or bandwidth cannot be secured for some reason. Communication may not be possible with the priority or bandwidth. In addition, the QoS priority and bandwidth requested by the user may not be ensured even though communication between domains is performed within the range of the maximum bandwidth between domains. For example, there may be a case where a QoS policy existing in one domain does not exist in the other domain, or due to a shortage of communication resources. In such a case, a charge is made according to the reserved QoS priority and bandwidth for the domain for which QoS priority and bandwidth could not be secured.
At present, the usage status of resources in each domain can be grasped in each domain's equipment, but the result of whether the QoS priority and bandwidth requested by the user can be secured and how much quality is compared with other domains. There is no means of objective measurement. For this reason, enhancement of facilities for securing QoS priority and bandwidth of communication has only been performed according to reports from users and internal indexes of domains. As a result, the serviceability of the entire network may be reduced due to insufficient enhancement. Moreover, it is conceivable that the utilization efficiency of the network is lowered, and in addition, the period of time for collecting the investment cost of the equipment is increased because the QoS usage charge from the user who should originally enter the domain is reduced.
In view of the above points, an object of the present invention is to provide a charging method between network domains and a QoS network system that improve the serviceability of the entire network by clarifying the state of correspondence of the domain to the QoS request from the user. It is to be.

  In order to solve the above-mentioned problem, the present invention is a method for generating information for transmitting a resource securing status in a service control function part of a conventional NGN network or the like to a charging function, which includes charging information between different network domains. Authentication authorization charging means for storing, means for confirming whether communication path priority and bandwidth necessary for communication from the terminal can be secured, means for securing communication path priority and bandwidth necessary for communication from the terminal, terminal Means for comparing the communication path necessary for communication from the information obtained from the confirmation means, the priority of the communication path that can be secured on the network side as a result of the comparing means, and the priority requested by the terminal and A network that could not secure priority and bandwidth for the means for storing billing information between the networks when the bandwidth is smaller than Characterized in that it comprises means for generating information to pay a penalty to signal destination network.

According to the first solution of the present invention,
A charging method between network domains in a QoS network system in which a first terminal of a first network and a second terminal of a second network perform QoS communication across the first network and the second network,
A communication device of the first network transmitting a session start request including the requested QoS information from the first terminal to the second network via the first network;
A first confirmation step in which a communication device of the second network confirms whether communication resources for realizing the QoS indicated by the requested QoS information can be secured in the second network;
When communication resources for realizing the QoS cannot be secured, the communication device of the second network registers the first penalty charging information for paying the penalty fee from the second network to the first network, and requests QoS Changing information according to communication resources secured in the second network and notifying the communication device of the first network;
A second confirmation step in which the communication device of the first network confirms whether communication resources for realizing the QoS indicated by the requested QoS information can be secured in the first network;
A step of registering second penalty billing information for the first network communication device to pay a penalty fee from the first network to the second network when communication resources for realizing the QoS cannot be secured; A billing method between the network domains is provided.

According to the second solution of the present invention,
A first communication device of a first network accommodating a first terminal;
A QoS network system comprising a second communication device in a second network accommodating a second terminal that performs QoS communication with the first terminal via a first network and a second network,
The first communication device transmits a session start request including the requested QoS information from the first terminal to the second network via the first network;
The second communication device confirms whether communication resources for realizing the QoS indicated by the requested QoS information in the second network can be secured,
When communication resources for realizing the QoS cannot be secured in the second network, the second communication device registers first penalty billing information for paying a penalty fee from the second network to the first network. Changing the requested QoS information according to communication resources secured in the second network and notifying the first communication device;
The first communication device confirms whether communication resources for realizing the QoS indicated by the requested QoS information can be secured in the first network,
When communication resources for realizing the QoS cannot be secured in the first network, the first communication device registers second penalty billing information for paying a penalty fee from the first network to the second network. The QoS network system is provided.

According to the present invention, it is possible to provide a billing method between network domains and a QoS network system that improve the serviceability of the entire network by clarifying the state of correspondence between domains in response to a QoS request from a user.
More specifically, according to the present invention, when establishing a session via a plurality of domains, it is possible to determine whether priority and bandwidth have been secured, and charging from other domains is possible. Therefore, it is possible to obtain an objective index regarding QoS priority and bandwidth reservation by comparing with the payment status of the own domain. For this reason, the correspondence state of the domain becomes clear, and there is an effect of improving the serviceability of the entire network.

Block diagram of the entire network. The functional block diagram in the block of a user A home network. FIG. 6 is a flowchart of a conventional SIP message. The functional block diagram in the block of the user A home network which concerns on this invention. FIG. 3 is a flowchart of a SIP message according to the present invention. 9 is a processing flowchart in proxy call session control function P-CSCF134. 9 is a processing flowchart in proxy call session control function P-CSCF 114. Explanatory drawing of the information of a SDP1 header part. Explanatory drawing of the information of a SDP2 header part. Explanatory drawing of the information of SDP2 'header part. Explanatory drawing of the information of SDP2 '' header part. Explanatory drawing of the relationship of session connection availability and penalty charge.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a block diagram of the entire network according to the present invention. In FIG. 1, the communication network includes a user A home network 105 and a user B home network 125, which are two network domains to which users A and B who are trying to communicate exist, and are connected to each other. The user A home network 105 and the user B home network 125 have the same configuration, and the configuration on the user A side will be described below, but the same applies to the user B side.
The user terminal 101 has an application function 102 for communication, a client function 103 for performing an authentication process for authenticating the terminal by a connected network, and a SIP agent function 104 for controlling a communication session with a communication partner. ing.
The user A home network 105 is divided into a service layer 106 that manages and controls communication services provided in the network, and a transfer layer 107 that controls, manages, and transfers data within the network.
The transfer hierarchy 107 is divided into a transfer control function 109 and a transfer function 108. The transfer control function 109 includes a network registration control function (Network Attachment Functions) NACF 112 for performing terminal registration and user function initialization, and a policy and charging rule function having a charging registration function for users and a QoS policy control function. (Policy and Charging Rules Function) PCRF113 is included. The transfer function 108 that performs data transfer includes a policy and charge enforcement function PCEF 111 that executes a QoS policy for the transfer information and acquires charging information, and an actual data transfer and SIP between the user terminal and the proxy call session control function P-CSCF 114. A transfer device 110 that transfers information is included.
The terminal A101 used by the user A is logically connected to the transfer device 110 of the user A home network 105, and is connected to the terminal B121 used by the user B via the transfer device 130 of the user B home network 125.

In the service layer 106 that manages and controls the communication service provided in the network, the call session control function S-CSCF 115 that controls the service function and the relay session control function I that resolves the destination of the call session control function S-CSCF 115 CSCF 116, application server function A / SF 118 having an application server function in the network, authentication / authorization / charging management function (hereinafter referred to as charging AAA) 119 having a function to control user authentication / authorization / charging in the network, The call session control function S-CSCF 115 includes a proxy call session control function P-CSCF (first communication device) 114 that performs communication with the proxy function and transfer control function 109 and communication with the charging AAA 119.
In performing communication from the user, the session information is processed by the P-SCSF 114, the call session control function S-CSCF 115, and the relay session control function I-CSCF 116 from the terminal A101 via the transfer device 110 and then to the user B's home network. After being processed by the relay session control function I-CSCF 136, the call session control function S-CSCF 135, and the proxy call session control function P-CSCF (second communication device) 134, it reaches the terminal B 121 via the transfer device 130 To do. After the session information processing is completed, communication between the terminal A 101 and the terminal B 121 is performed via the transfer device 110 and the transfer device 130.
Each function described above is realized by each functional unit, communication device, server, and the like provided in the network.

FIG. 2 shows the functions in the block of the user A home network 105.
In FIG. 2, charging AAA 119 includes charging management means 201 for centrally managing information related to charging for users in the network.
Further, in the proxy call session control function P-CSCF 114, QoS request analysis means 204 for analyzing the contents of the SDP information in the SIP message, and the policy in the transfer control function 109 and the charging rule function PCRF 113, the QoS resource QoS resource confirmation means 205 that sends confirmation information and receives a reply, and compares the QoS policy and SDP information such as priority and bandwidth for each user registered in advance and the reply from the policy and charging rule function PCRF 113 to the policy A user policy determination unit 206 that determines whether or not there is a match, and a billing information creation unit 207 that creates billing information associated with user communication.
In the call session control function S-CSCF 115, a service for checking service availability by comparing service provision information to a user registered in advance for each user and communication requested by the user described in the SIP message. A possible check means 208 is provided. The transfer control function 109 includes resource management means 203 for confirming a communication band, a use band for each priority, and a reservation for a band for each priority, and a priority usable by the user, User QoS policy management means 202 holds and manages, as information registered in advance for each user, whether or not to permit change of bandwidth and priority of communication and change of bandwidth. Other functions are the same as those in FIG.

FIG. 3 is a flowchart of SIP message processing.
This flow diagram explains how the block of FIG. 1 is involved in the normal SIP session processing when communication is started between the terminal A and the terminal B in accordance with the present embodiment. is there. As a premise for explaining the flow diagram, there must be a contract between the user and the network domain and a connection contract between the networks. The contract between the user and the network domain requires that the following four contracts are exchanged.
The first is a connection contract to a network domain, which is a basic connection contract such as connection to a network, terminal authentication, IP address assignment, charging, and payment method. The contract information is registered in the network registration control function NACF 112 and the network registration control function NACF 132. If there is no connection contract, it cannot be used even if a terminal is connected to the network domain.
The second is a connection contract with another network, which is a contract for connecting to another network outside the contracted network. The contract information is registered in the call session control function S-CSCF 115 and the call session control function S-CSCF 135, and communication with other network domains is not possible when there is no connection contract.
The third is a service contract that is a contract of the maximum bandwidth that can be used by the user, the protocol and maximum bandwidth that can be used for communication, and the maximum bandwidth that can be used with the network application that is used. The contract information is registered in the call session control function S-CSCF 115 and the call session control function S-CSCF 135, and if there is no service contract, communication cannot be performed through the network domain.
The fourth is a QoS connection contract that sets a plurality of priority settings, a maximum bandwidth setting that can be used for each priority, and media (image, audio, data, and stored data) that are used for each priority. The contract information is registered in the charging rule functions PCRF 113 and PCRF 133, and if there is no QoS connection contract, communication can be performed only with the minimum priority and bandwidth specified in advance.
In addition, a contract between networks requires, for example, a common comprehensive contract between connected network domains, and the network domain of the connection partner needs to have a contract.
The first is a billing contract that defines a billing method between domains, and contract information is registered in the call session control function S-CSCF 115 and the call session control function S-CSCF 135. Communication between network domains is not possible without a billing contract.
The second is a contract relating to QoS setting of priority and communication quality and setting of priority and inter-domain communication unit price. The contract information is registered in the call session control function S-CSCF115 and the call session control function S-CSCF135. If there is no service contract related to QoS, communication between network domains cannot be performed.

In the flow of FIG. 3, it is assumed that authentication and registration processing of the terminal A 101 and the terminal B 121 are performed by the NACFs 122 and 132. Also, in order to reduce complexity, the transfer device 110 or 130 that simply transfers the SIP message is omitted, and the transferring message 100 trying between the functions of the transfer device is omitted for the same purpose.
First, the INVITE message 301 is issued from the terminal A101 to the terminal B121. INVITE 301 is attached with SDP information SDP1 356 in which several patterns of bandwidth, priority, and media information for communication with terminal B 121 are stored (see FIG. 8). The priority may be determined in advance according to media such as audio and video, and the media information may be described in the SDP by omitting the priority. INVITE 301 is sent from terminal A 101 via proxy device 110 to proxy call session control function P-CSCF 114 as a proxy, but is not shown in the drawing to reduce complexity. INVITE 301 reaches call session control function S-CSCF 115 as INVITE 302 via P-CSCF 114. The call session control function S-CSCF 115 confirms whether the service can be received by the user A, and sends it to the call session control function S-CSCF 135 of the user B home network as INVITE 303. The call session control function S-CSCF 135 confirms whether the service can be received by the user B, and sends it to the proxy call session control function P-CSCF 134 as INVITE 304. The proxy call session control function P-CSCF 134 sends INVITE 305 to the user terminal B121. Although INVITE 305 reaches the terminal 121 from the P-CSCF 134 via the transfer device 130, the transfer device 130 is only transferring, and is omitted in the figure to reduce complexity.

  The terminal B121 confirms whether the SDP1 information from the terminal A101 is acceptable using a known technique, and issues SDP2 357. The contents of SDP2 357 are selected and copied from the contents of several patterns in SDP1 356 (see FIG. 9). Thereafter, the terminal B 121 issues a 183 Session Progress message (hereinafter referred to as 183 message) 306 including the information of SDP2 357 to the proxy call session control function P-CSCF 134 as a response message to the terminal A 101 for the INVITE 305. The proxy call session control function P-CSCF 134 analyzes the received SDP2 information and issues a resource inquiry 307 as to whether the QoS resource (priority, bandwidth) of the network can be secured to the policy and charging rule function PCRF 133. Policy and charging rule function PCRF 133 confirms the status of the QoS resource of the network, and QoS resource (priority, bandwidth) information that can be secured as a response to whether or not the QoS resource inquired from proxy call session control function P-CSCF 134 can be secured The resource answer 308 is returned. The proxy call session control function P-CSCF 134 inquires of the policy and charging rule function PCRF 133 about the user QoS request 309, which is a request for the QoS policy information of the user B, to the policy and charging rule function PCRF 133. The policy and charging rule function PCRF 133 returns a QoS answer 310 which is a reply of the QoS information of the user B corresponding to the user QoS request 309 from the proxy call session control function P-CSCF 134. The proxy call session control function P-CSCF 134 determines the continuation or termination of the session based on the information of the QoS answer 310, the resource answer 308, and the SDP2 357. In the case of continuation, the priority / bandwidth for the policy and charging rule function PCRF 133 is determined. And set up billing for the session. Thereafter, the proxy call session control function P-CSCF 134 sends out an 183 message 312 with the information of SDP2 357.

The 183 message 312 reaches the proxy call session control function P-CSCF 114 via the call session control function S-CSCF 135 and the call session control function S-CSCF 115. The proxy call session control function P-CSCF 114 that received the 183 message analyzes the received SDP2 information, and issues a resource inquiry 315 as to whether the QoS resource (priority, bandwidth) of the network can be secured for the policy and charging rule function PCRF 113. Issue. Policy and charging rule function PCRF 113 confirms the status of the QoS resource of the network, and QoS resource (priority, bandwidth) information that can be secured as a response to whether or not the QoS resource that is inquired from proxy call session control function P-CSCF 114 can be secured A resource answer 316 is returned. The proxy call session control function P-CSCF 114 inquires of the policy and charging rule function PCRF 113 about the user QoS request 317, which is a request for QoS policy information of the user B, to the policy and charging rule function PCRF 113. The policy and charging rule function PCRF 113 returns a QoS answer 318 which is a reply of the QoS information of the user B corresponding to the user QoS request 317 from the proxy call session control function P-CSCF 114. The proxy call session control function P-CSCF 114 determines the continuation or termination of the session based on the information of the QoS answer 318, the resource answer 316, and the SDP2 357. In the case of continuation, the priority / bandwidth for the policy and charging rule function PCRF 113 is determined. And set up billing for the session. Thereafter, the proxy call session control function P-CSCF 114 sends the 183 message 314 with the information of SDP2 357 to the terminal A101.
The reservation of priority and bandwidth is completed as described above. Next, between terminal A 101 and terminal B 121, PRACKs 321, 322, 323, 324, 325 and 200 OK 326, 327, 328, 329 as a response from terminal B 121 to terminal A 101 , 330 are issued. Similarly, UPDATEs 331, 332, 333, 334, and 335 are issued from the terminal A101 to the terminal B121, and 200 OK 336, 337, 338, 339, and 340 are issued as responses. Thereafter, 180 RINGING 341, 342, 343, 344, and 345 are issued from the terminal B121 to the terminal A101, and then 200OK 346, 347, 348, 349, and 350 are issued. When terminal A 101 receives 200 OK 350, it issues ACKs 351, 352, 353, 354, and 355 to terminal B 121.
When terminal B receives 200 OK 355, communication between terminal A 101 and terminal B 121 is possible. A series of operations for establishing a session between the terminal A101 and the terminal B121 can comply with RFC 3312 of the IETF standard.

  FIG. 4 is a functional block diagram in the block of the user A home network according to the present invention. In FIG. 4, the functions of the same symbols as those in FIG. 2 are not changed. In FIG. 4, functions newly added from FIG. 2 are added to the SDP, the priority and bandwidth secured based on the priority and bandwidth information secured by the policy and charging rule function PCRF 113, and the priority change information and SDP generation means 401 for adding band change information to SDP, and a penalty for generating billing information so that payment is made to the communication partner side network as a penalty when communication resource QoS information cannot be prepared This is billing information generating means 402.

FIG. 5 is a flowchart of SIP message processing according to an embodiment of the present invention.
This flow diagram explains how the block of FIG. 1 is involved in SIP session processing when communication is started between terminal A and terminal B, for example, the difference from FIG.
As a premise for explaining the flow diagram, there must be a contract between the user and the network domain and a connection contract between the networks. The difference from the contract in FIG. 3 is that, for example, in the fourth contract between the user and the network domain, a contract is set to set whether to allow / disallow when the priority of the network convenience or the bandwidth is changed. And, in the second comprehensive contract common to all networks, a contract is added to set a penalty unit price to be paid to the partner network domain when the QoS response from the terminal is low. is there.
8 and 9 show examples of SDP1 and SDP2.

  FIG. 8 is an example of SDP1 556. The IP address, session identification number, port number, protocol, requested bandwidth, QoS priority, and the like of terminal A101 and terminal B121 are designated. The detailed meaning is described in, for example, Non-Patent Document 2, Non-Patent Document 3, Non-Patent Document 4, Non-Patent Document 5, Non-Patent Document 6, and the like.

FIG. 9 is an example of SDP2 557. The terminal B121 returns information used for communication with the terminal A101 to the terminal A101. A known technique is used for selection of priority, bandwidth and protocol. The content is the same as SDP2 357.
5 differs from FIG. 3 in that the process after the proxy call session control function P-CSCF 134 receives the QoS response message 510 from the policy and charging rule function PCRF 133, and the policy and charging on the user A home network side. This is processing after the QoS answer message 518 from the rule function PCRF 113 to the proxy call session control function P-CSCF 114.
After the proxy call session control function P-CSCF 134 receives the QoS reply message 510 from the policy and charging rule function PCRF 133, the policy and charging rule function PCRF 133 can secure the generation of penalty charging information to the opposite network and the information of SDP2 557. SDP information (hereinafter referred to as SDP2 ′ information) 558 with the added priority and bandwidth information is generated. Further, after the QoS response message 518 from the policy on the user A home network side and the charging rule function PCRF 113 to the proxy call session control function P-CSCF 114, the proxy call session control function P-CSCF 114 indicates the penalty charging information for the opposite network. The SDP information (hereinafter referred to as SDP2 ″ information) 559 is generated by adding the priority and bandwidth information that can be secured by the policy and charging rule function PCRF 113 to the information of generation and SDP2 ′ 558. It may be QoS information indicating QoS.

FIG. 6 is a flowchart showing the operation of proxy call session control function P-CSCF 134 after receiving 183 Session Progress 506 from terminal B 121 in FIG.
This flowchart shows, for example, registration of a penalty charge that the user B home network pays to the user A home network when the request priority and bandwidth from the opposite user A home network cannot be prepared in the user B home network. This is for explaining the process and the process of adding information to the SDP information.
After receiving the 183 message 506 in the process 601, the QoS request analysis means in the network B analyzes the SDP2 557 of the SIP message in the process 602 to separate the request priority and the request band. In processing 603, based on the request priority and the requested bandwidth, a confirmation message (resource inquiry) 507 is sent to the policy and charging rule function PCRF 133 whether the priority and bandwidth can be secured by the QoS confirmation means in the network B. . In a process 604, a response 508 from the policy and charging rule function PCRF 113 is waited. After the reply 508 arrives, the contents of the reply 508 are analyzed in a process 605.
In the process 606, the QoS answer 510 of the user B is referred. For example, the QoS answer includes information on whether or not the change of priority and bandwidth is allowed for each user. In step 607, the content of the resource answer 508 is determined. If the network cannot prepare for the priority and bandwidth at all, an end message such as 487 (request stop) is sent to the SIP message at step 612 (SIP end processing). Thereafter, in the charging process 613, the charging information generating means deletes the charging information for the corresponding session, sends a message to the charging AAA 139 to end the session, and ends the process.
If the result of the processing 607 indicates that preparation is possible, in the next processing 608, the request priority and bandwidth of the SDP2 557 are compared with the priority and bandwidth of the answer 508. If there is no difference, a charging process for communication is performed in process 609, and the corresponding charging information is sent to the charging AAA 139. Further, in processing 610, the priority and bandwidth setting registration processing of the corresponding communication is performed for the policy and charging rule function PCRF 133, and the processing is terminated.
In step 608, the request priority and bandwidth of SDP2 557 are compared with the priority and bandwidth of answer 508. If there is a difference in at least one of them, the priority and bandwidth of the network factor are determined in steps 614 and 616. User B's QoS policy determination is performed for the change. In the process 614, the policy is matched only when the priority change is permitted / not permitted in the user B's QoS policy, the priority change is permitted based on the difference in priority between the SDP2 557 and the answer 508, and when there is no difference in priority. Otherwise, it is determined that the policy does not match. If the policies do not match, the process proceeds to the SIP end process 612 and the end process is performed.

On the other hand, in the case of policy matching, SDP2 ′ 558 is generated in process 615, and the priority addition secured in the SDP information and the priority change information meaning that the priority has been changed are additionally written.
Further, in the process 616, the policy match is made only when the bandwidth change is permitted and when there is no bandwidth difference based on whether or not the bandwidth change is permitted / not permitted in the QoS policy of the user B and the difference in priority between the SDP2 557 and the answer 508. Otherwise, it is determined that the policy does not match. If the policies do not match, the process proceeds to the SIP end process 612 and the end process is performed. On the other hand, in the case of policy coincidence, SDP2 ′ 558 is generated in process 617, and additional band addition information reserved in the SDP information and additional band change information meaning that the band has been changed are added.
Note that the processing related to the priorities of the processing 614 and 615 and the processing related to the bandwidths of the processing 616 and 617 may be performed in the reverse order limited to the above-described example.

FIG. 10 shows an example of SDP2 ′ 558.
Based on the priority and bandwidth status from the policy and charging rule function PCRF 133, the reserved priority and bandwidth are described. In the figure, there is a part where the band cannot be secured, and the part is corrected (changed from bold part 1024 to 512). In addition, since the band is changed, band change information (rb = 1) is entered. If there is a change from the priority request, it is set in advance according to the priority in which the part after the equal sign of the media type described as “m =” can be secured as in the example. It is corrected to any of “audio”, “video”, “application”, “data”, “control”, etc. associated with the priority, and the priority change information (ra = 1) is entered.
Returning to the flow of FIG. 6, after that, charge processing is performed by the charge information generation means in the proxy call session control function P-CSCF 134 in process 618, and the charge information in the corresponding session is reduced. Further, the penalty billing registration for paying a penalty from the network B to the network A is performed by the penalty billing information generating means in the proxy call session control function P-CSCF 134. The charge reduction and penalty may be obtained according to, for example, the requested priority and bandwidth and the secured priority and bandwidth difference.
In process 610, priority and bandwidth setting registration processing of the corresponding communication is performed for the policy and charging rule function PCRF 133, and the process ends in process 611.

FIG. 12 shows the relationship between the priority and bandwidth secured by the network domain, the request priority of the information of SDP 2 ′ 558 and the availability of session connection and the penalty charge depending on the bandwidth.
FIG. 7 is a flowchart of processing after receiving the 183 message 514 in the proxy call session control function P-CSCF 114.
This process clarifies the registration process of the penalty charge that the user A home network pays to the user B home network when the bandwidth of the request priority and the bandwidth of the user B facing the user B in the home network of the user A cannot be prepared. It is to make.
After receiving the 183 message 514 in the process 701, the QoS request analysis means 204 in the network A analyzes the SDP2 ′ 558 of the SIP message in the process 702, and the request priority and the request band are separated. The request priority and the requested bandwidth may be changed in the user B's home network as described above. Also, if there is priority change information and band change information, these are also separated. In step 703, the QoS answer 518 which is the QoS policy of the user A is referred to. In step 704, the priority of the network factor and the change of the bandwidth are changed based on the priority change information and the bandwidth change information of the SDP 2 ′ A's QoS policy is determined. In the process 704, if the priority change is permitted in the QoS policy of the user A, if the change of the bandwidth is permitted, or if the priority change information and the bandwidth change information are not present, the policy is matched, and otherwise, the policy is not matched. And
If the policies do not match, an end message such as 487 (request cancellation) is sent to the SIP message in processing 713. After that, the charging information generation means deletes the charging information of the corresponding session in the charging process 714, and a message to end the session is sent to the charging AAA 139 to end the process.
On the other hand, if the policies match in the process 704, the priority for the policy and the charging rule function PCRF 113 in the QoS confirmation means in the network A based on the request priority and the requested bandwidth of the SDP 2 ′ 558 in the process 705 A confirmation message 515 is sent out whether the bandwidth can be secured. In the process 706, the response 516 from the policy and charging rule function PCRF 113 is waited.
In step 708, the content of the answer 516 is determined. When the network cannot prepare for the priority and bandwidth at all, the process proceeds to processing 713, and an end message such as 487 (request cancellation) is transmitted as a SIP message. After that, the charging information generation means deletes the charging information of the corresponding session in charging processing 714, and a message to end the session is sent to the charging AAA 119, and the processing ends.

If the result of the processing 708 indicates that preparation is possible, in the next processing 709, the request priority and bandwidth of the SDP 2 ′ 558 are compared with the priority and bandwidth of the answer 516. If there is no difference, a charging process for communication is performed in process 710, and the corresponding charging information is sent to the charging AAA 119. Further, in processing 711, the priority and bandwidth setting registration processing of the corresponding communication is performed for the policy and charging rule function PCRF 113, and the processing ends.
When the request priority and bandwidth of SDP2 ′ 558 are compared with the priority and bandwidth of answer 512 in processing 709 and there is a difference in at least one of them, the priority and bandwidth of the network factor are processed in processing 715 and processing 717. The user A QoS policy is determined for the change.
In the process 715, the policy match is made only when the priority change is permitted / not permitted in the QoS policy of the user A, the priority change is permitted based on the difference in priority between the SDP 2 ′ 558 and the answer 516, and when there is no priority difference. Otherwise, it is determined that the policy does not match.
If the policies do not match, the end process is performed in the SIP end process 713. In the case of policy match, SDP2 ″ 559 is generated in process 716, and the priority secured in the SDP information is added, and priority change information meaning that the priority has been changed is additionally written.
Further, in the process 717, the policy is matched only when the band change is permitted / not permitted in the QoS policy of the user A and when the band change is permitted due to the difference in priority between the SDP 2 ′ 558 and the answer 516 or when there is no band difference. Otherwise, it is determined that the policy does not match. If the policies do not match, the end process is performed in the SIP end process 713. In the case of policy match, SDP2 ″ 559 is generated in process 718, and the reserved bandwidth is added to the SDP information, and the bandwidth change information meaning that the bandwidth has been changed is added. Note that the processing related to the priorities of the processing 715 and 716 and the processing related to the bandwidths of the processing 717 and 718 may be performed in the reverse order limited to the above example.

FIG. 11 shows an example of SDP2 ″ 559.
Policy and charging rule function The priority and bandwidth secured based on the priority and bandwidth status from the PCRF 113 are described. In the figure, since the request priority from SDP 2 ′ 558 and the bandwidth can be secured, there is no change from SDP 2 ′ 558, and the contents are the same. If priority and bandwidth cannot be secured and there is a change from the request, the corresponding part is corrected in the same manner as in the example of SDP2'558, and priority change information (ra = 1) or bandwidth change (rb = 1) is changed. Fill out.
Thereafter, in a process 719, a charging process is performed by the charging information generating means in the proxy call session control function P-CSCF 114, and the charging information in the corresponding session is reduced. Further, the penalty billing registration for paying the penalty from the network A to the network B is performed by the penalty billing information generating means in the proxy call session control function P-CSCF 114.
In process 711, the priority and bandwidth setting registration process of the corresponding communication is performed for the policy and charging rule function PCRF 113, and the process ends in process 712.
The registered billing information and penalty billing information are transmitted to the billing AAA of each network at an appropriate timing. In addition, based on the contract between networks, the charging AAA of each network can send penalty charging information to a predetermined device and server, cancel the penalty charging information between domains, and perform billing processing between domains. . Penalty billing information between domains, billing information offset, and the like can be transmitted to the management device of each network, and the management device may display or output these.
In each network, the requested priority, the bandwidth, the priority that can be secured, and the difference between the bandwidths may be displayed or output to the management apparatus.
According to the above-described embodiment, when the QoS priority and bandwidth reserved on the domain side are not satisfied with respect to the QoS priority and bandwidth request in the communication between the user A and the user B, the QoS priority is determined by penalty charging. In addition, both domains are notified by the amount paid to the opposite domain from the domain that could not secure the bandwidth, and the QoS priority that could be secured in the domain in the SDP header information for the opposite domain and terminal and By notifying the bandwidth, the priority and the type of the bandwidth that cannot be satisfied, it is possible to clarify the correspondence state of the domain with respect to the QoS request from the user.

  The present invention can be used, for example, in a communication system that establishes a session via a plurality of domains.

101: Terminal A used by user A
102: Application function in terminal A 103: Authentication client function in terminal A 104: SIP agent function in terminal A 105: Home network of user A 106: Service layer 107: Transfer layer 108: Transfer function 109: Transfer control function 110: Router device function 111: Policy and charging enforcement function PCEF (Policy and Charging Enforcement Function)
112: Network registration control function NACF (Network Attachment Control Functions)
113: Policy and Charging Rule Function PCRF (Policy and Charging Rules Function)
114: Proxy call session control function P-CSCF (Proxy Call Session Control Function)
115: Call session control function S-CSCF (Serving Call Session Control Function)
116: Relay session control function I-CSCF (Interrogating Call Session Control Function)
118: Application server function A / SF (Application Server Function)
119: Billing AAA (Authentication, Authorization, Accounting)

Claims (8)

A charging method between network domains in a QoS network system in which a first terminal of a first network and a second terminal of a second network perform QoS communication across the first network and the second network,
A communication device of the first network transmitting a session start request including the requested QoS information from the first terminal to the second network via the first network;
A first confirmation step in which a communication device of the second network confirms whether communication resources for realizing the QoS indicated by the requested QoS information can be secured in the second network;
When communication resources for realizing the QoS cannot be secured, the communication device of the second network registers the first penalty charging information for paying the penalty fee from the second network to the first network, and requests QoS Changing information according to communication resources secured in the second network and notifying the communication device of the first network;
A second confirmation step in which the communication device of the first network confirms whether communication resources for realizing the QoS indicated by the requested QoS information can be secured in the first network;
A step of registering second penalty billing information for the first network communication device to pay a penalty fee from the first network to the second network when communication resources for realizing the QoS cannot be secured; A charging method between the network domains. The request QoS information includes one or both of a request priority and a request bandwidth,
In the first confirmation step, the communication device of the second network confirms whether the request priority or the request bandwidth can be secured in the second network,
2. The accounting method between network domains according to claim 1, wherein in the second confirmation step, the communication device of the first network confirms whether or not the request priority or the requested bandwidth can be secured in the first network. Indicates whether the communication device of the second network allows a change in priority or bandwidth when there is a difference between the request priority or bandwidth and the priority or bandwidth secured in the second network. The method according to claim 2, further comprising a step of determining whether the policy matches with the policy information set in advance, ending the process if the policy does not match, and performing a process of establishing a session if the policy matches. Billing method between network domains. When the communication device of the second network has a difference between the request priority or the requested bandwidth and the priority or the bandwidth secured in the second network, it indicates that the request priority or the requested bandwidth could not be secured. Send the change information to the communication device of the first network,
The communication device of the first network determines whether or not it matches the policy according to the received change information and preset policy information indicating whether or not to change the priority or the bandwidth, and if it does not match the policy The method for charging between network domains according to claim 2, further comprising a step of ending the process and performing a process of establishing a session if the policy matches. When the communication device of the second network has a difference between the request priority or the request bandwidth and the priority or the bandwidth secured in the second network;
The communication device of the first network further includes a step of reducing the charge of the corresponding session when there is a difference between the request priority or the requested bandwidth and the priority or the bandwidth secured in the first network. 2. A charging method between network domains according to 2. The accounting method between network domains according to claim 1, further comprising the step of canceling the first penalty accounting information and the second penalty accounting information and notifying the management device of the first network and / or the second network. A step of storing the difference when the communication device of the first network or the second network has a difference between the requested priority or the requested bandwidth and the priority or the bandwidth secured in the first network or the second network; The accounting method between network domains according to claim 2, further comprising: A first communication device of a first network accommodating a first terminal;
A QoS network system comprising a second communication device in a second network accommodating a second terminal that performs QoS communication with the first terminal via a first network and a second network,
The first communication device transmits a session start request including the requested QoS information from the first terminal to the second network via the first network;
The second communication device confirms whether communication resources for realizing the QoS indicated by the requested QoS information in the second network can be secured,
When communication resources for realizing the QoS cannot be secured in the second network, the second communication device registers first penalty billing information for paying a penalty fee from the second network to the first network. Changing the requested QoS information according to communication resources secured in the second network and notifying the first communication device;
The first communication device confirms whether communication resources for realizing the QoS indicated by the requested QoS information can be secured in the first network,
When communication resources for realizing the QoS cannot be secured in the first network, the first communication device registers second penalty billing information for paying a penalty fee from the first network to the second network. The QoS network system.

Images