JP5142957B2 - Service component management system, execution control server, and service component management method - Google Patents

Description

The present invention, the service component management system, related to the execution control server及 Beauty Services component management method.

Currently, there are attempts to easily realize new services by using service components such as web services in cooperation.
In the technologies described in Non-Patent Documents 1 and 2, the execution control server collectively performs common processing such as user authentication and traffic control in a system that links the telephone service and the web service.
Yamato Koji, Onishi Hiroyuki, Nakano Yusuke, “Examination of Execution Control Function to Promote Telephone-Web Collaboration” Proceedings of 2008 IEICE General Conference, B-19-10, Mar. 2008. Y. Yamato, H. Ohnishi, and H. Sunaga. “Development of ServiceControl Server for Web-Telecom Coordination Service,” IEEE International Conference on Web Services, ICWS2008, Sep.2008.

However, since Non-Patent Documents 1 and 2 assume the operation of a single execution control server, when multiple execution control servers are used, a request from the user to the service component is sent to the entire system. There is a problem that it cannot be monitored.
For example, when the number of times that a user a can use the service component A per day is set to 100 times, the user a is 30 times for the execution control server 1, 80 times for the execution control server 2, and the execution control server 3 Even when the service component A is used 60 times, the user a cannot be detected as a user who exceeds the daily usage limit of 100 times.
The present invention has been made in view of the above points, and an object of the present invention is to monitor requests in the entire system even when a plurality of execution control servers are executed in parallel, and to process requests to service components. service component management system capable of improving is to provide a running control server及 beauty services component management method.

  SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and one aspect of the present invention provides user information including a black list that is a list of users who are temporarily unable to use a service component, and a service component. A profile database that holds service component information including a service component blocking flag indicating whether or not is in a blocked state, and the profile database holds a request for updating the user information or the service component information Based on the blacklist, a profile server comprising a database registration control function unit that updates the service component information or the user information, a receiving unit that receives a request from a user terminal to a service component, A blacklist verification function unit that determines whether or not the service component is temporarily unavailable and a service component blockage that determines whether or not the service component is blocked based on the service component blockage flag The confirmation function unit and the blacklist matching function unit determine that the user is temporarily unavailable for the service component, and the service component block confirmation function unit determines that the service component is not blocked. A transmission unit that transmits the request to a service component server of the service component, user-specific statistical information indicating a status of a request from a specific user to a specific service component, and a specific service component. A traffic information totaling function unit that generates traffic information including error rate information for each service component that represents an error status of a client based on the request and transmits the traffic information to a traffic information management server. A traffic collection function unit that receives the traffic information from the execution control server, a traffic aggregation function unit that aggregates the traffic information received by the traffic collection function unit, and a traffic aggregation function unit Based on the service component monitoring function unit for extracting service components to be blocked based on the error rate information for each service component, and on the basis of the statistical information for each user aggregated by the traffic aggregation function unit A user monitoring function unit for extracting users temporarily unavailable for the service component, and an update request for the service component block flag corresponding to the service component extracted by the service component monitoring function unit to the profile server A traffic information management server comprising: a reaction function unit that transmits to the profile server an update request for transmitting and adding the user extracted by the user monitoring function unit to the black list of the specific service component This is a service component management system characterized by the above.

  According to another aspect of the present invention, in the service component management system, the service component information includes a flow control flag indicating whether to perform flow control on the service component, and the traffic information includes a specific service component Response time information representing the response time status from the service component monitoring function unit, based on the response time information aggregated by the traffic aggregation function unit, extracts a service component for performing flow control, The reaction function unit transmits an update request for the flow control flag corresponding to the service component that performs the flow control extracted by the service component monitoring function unit to the profile server, and the execution control server transmits the flow control Based on the lug, characterized in that it comprises a flow regulating function section for delaying a predetermined time the request uniformly to the service component.

  Further, according to one aspect of the present invention, in the service component management system, the execution control server performs user authentication when receiving an authentication ticket request from a user terminal, and issues an authentication ticket to the terminal when authenticated. A password authentication function unit that replies, and a single sign-on function unit that verifies an authentication ticket included in the request when a request from the user terminal to the service component is received by the receiving unit, To do.

  According to another aspect of the present invention, in the service component management system, the component service information includes a white list that is a list of users who can use the service component, and the execution control server includes the white list in the white list. A whitelist collation function unit that determines whether or not the user is registered, and the transmission unit transmits the request to the service component server only when the user is registered in the whitelist. It is characterized by that.

  Further, according to one aspect of the present invention, in the service component management system described above, when the database registration control function unit updates the profile database, the execution control server notifies the execution control server, and the execution control server A cache data management function unit that holds user information and the service component information, and when the update of the user information or the service component information is notified from the profile server, the user information or the cache data management function unit A database update notification function unit for updating the service component information.

  According to another aspect of the present invention, in the service component management system described above, when the number of requests transmitted from the user to the service component within a predetermined time exceeds a predetermined threshold, an error is transmitted to the execution control server. The transmitting unit transmits the request to the service component server only when no error is notified from the throttling server.

  According to another aspect of the present invention, in the service component management system, the profile server includes a Cascon function unit that receives registration, update, and deletion of the service component information and the user information stored in the profile database. It is characterized by providing.

  Further, according to one aspect of the present invention, based on a receiving unit that receives a request from a user terminal to a service component, and a black list that is a list of users who are temporarily unable to use the service component, Whether the service component is blocked based on the blacklist verification function unit that determines whether the service component is temporarily unavailable and the service component block flag that indicates whether the service component is blocked A service component blockage confirmation function unit that determines whether or not the user is temporarily unavailable for the service component by the blacklist verification function unit, and the service component blockage confirmation function unit determines that the service component blockage confirmation function unit When it is determined that the service component is not in the blocked state, the transmission unit that transmits the request to the service component server of the service component, the statistical information for each user that represents the status of the request from the specific user to the specific service component, and the specific A traffic information totaling function unit that generates traffic information including error rate information for each service component representing an error status of each service component based on the request and transmits the traffic information to the traffic information management server. It is a featured execution control server.

  In addition, according to one aspect of the present invention, user information including a black list that is a list of users who are temporarily unable to use a service component, and a service component blocking flag indicating whether the service component is blocked are displayed. When a profile server having a profile database that holds service component information includes a request to update the user information or the service component information, the service component information or the user information held in the profile database is updated. A step in which the execution control server receives a request from the user's terminal to the service component; and the execution control server determines that the user is in charge of the service component based on the blacklist. Determining whether the service component is temporarily unavailable, a step in which the execution control server determines whether the service component is blocked based on the service component block flag, and the execution control server Determining that the user is not temporarily unavailable to the service component and determining that the service component is not blocked, sending the request to a service component server of the service component; The execution control server includes traffic information including statistical information for each user indicating a status of a request from a specific user to a specific service component, and error rate information for each service component indicating an error status of the specific service component. Generating based on the request and transmitting the traffic information to the traffic information management server, the traffic information management server receiving the traffic information from the execution control server, and the traffic information management server receiving Summing the traffic information, extracting the service component to be blocked based on the summed error rate information by the service component, and the traffic information management server summing the traffic information Extracting a user temporarily unavailable for a specific service component based on the user-specific statistical information, and a service component that the traffic information management server puts into the blocked state extracted A request to update the service component block flag corresponding to is transmitted to the profile server, and an update request to add the extracted user to be temporarily unavailable to the black list of the specific service component is transmitted to the profile server. A service component management method comprising: steps.

According to the present invention, the traffic information management server collects traffic information from a plurality of execution control servers, extracts the service components that are blocked and aggregated, and the users that are temporarily unavailable for a specific service component Therefore, even if a plurality of execution control servers perform processing in parallel, the consistency of traffic information can be maintained as a whole system.
In addition, since a plurality of execution control servers perform request processing on the service component in parallel, it is possible to improve the amount of request processing on the service component per unit time.
In addition, since the execution control server collectively performs common processing in each service component, it is possible to reduce the investment and cost for implementation of functions (non-functional requirements) other than service components on the service provider side.
Further, the execution control server can prevent the influence of the service component server in which the failure has occurred from spreading to other service components by blocking the request to the service component in the blocked state.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a block diagram showing the configuration of a service component management system according to an embodiment of the present invention.
The service component management system includes an execution control server cluster 4, a throttling server 10, a traffic information management server 14, a profile server 21, a traffic information database 20, service requester terminals 11 and 12, and a plurality of service component servers. 25.
The service requester terminals 11 and 12 and the execution control server cluster 4 and the execution control server cluster 4 and the service component server 25 transmit and receive messages via the network 13. The network 13 is a network composed of a communication network such as telephone exchange, an information network such as the Internet, an NGN (Next Generation Network) having a service control layer and a packet transfer layer, or a mobile network.

The service component server 25 is a server device that provides a plurality of service components to the service requester terminals 11 and 12. The service component is a service such as a web service or a telephone service provided by a service provider.
The service requester terminals 11 and 12 are terminals used by a user (requester) who uses a service formed by cooperation of a plurality of service components.

The execution control server cluster 4 is a group of execution control servers 1, 2, and 3.
The execution control servers 1, 2, and 3 are server devices that perform common processing for each service component. Common processing of each service component includes user authentication and traffic control. The functional configuration of the execution control servers 1, 2, and 3 will be described later. Requests from the service requester terminals 11 and 12 are sent to the execution control servers 1, 2 and 3 by a load balancer (not shown) according to the round robin algorithm and the CPU (central processing unit) usage rate of the execution control servers 1, 2 and 3. Sorted.
The profile server 21 is a server device that holds user information and service component information. The functional configuration of the profile server 21 will be described later.

  The throttling server 10 is a server device that performs a throttling process for controlling so that an excessive number of requests are not transmitted from the user to the service component server 25 in a short cycle. Specifically, the throttling server 10 stores the number of requests transmitted from a specific user to a specific service component within a rate determination time (for example, a short cycle such as several seconds) on a memory, and executes execution control. When a request is received from the server 1, 1 is added to the number of requests. Then, the throttling server 10 determines whether or not the number of requests exceeds a preset throttling threshold corresponding to the service component of the request destination, and if the number of requests exceeds the rate threshold The request is blocked and an error is returned to the execution control server 1. On the other hand, if the number of requests is equal to or less than the throttling threshold, the request is returned to the execution control server 1. The throttling server 10 acquires the throttling threshold value from the profile server 21.

The traffic information management server 14 is a server device that performs service component quality monitoring control for monitoring the load status of each service component. The functional configuration of the traffic information management server 14 will be described later.
The traffic information database 20 is a database that stores and holds traffic information aggregation results, and holds a service component table, an operation table, an operation-user table, and a user table. The traffic information is information obtained by tabulating items in the service component table, the operation table, the operation-user table, and the user table for each traffic information generation time (for example, 3 minutes). In addition, each item of the operation-user table and the user table is statistical information for each user indicating the status of a request from a specific user to a specific service component. Each item of the service component table is error rate information for each service component that represents an error status of a specific service component. Each item of the operation table is response time information for each operation of the service component representing the status of response time from a specific service component.

  FIG. 2 is a schematic diagram illustrating a data structure and a data example of the service component table in the present embodiment. The service component table has columns of items of date, time, service ID, number of requests, and number of errors. The hour indicates the time. For example, the hour “10” represents from 10:00 to 10:59. The service ID is identification information for identifying a service component. The number of requests is the number of requests transmitted to the service component. The number of errors is the number of errors with respect to the request transmitted to the service request, and includes items of authentication NG, authorization NG, and response timeout. Authentication NG is an error when user authentication is not performed. Authorization NG is an error when the user does not have authority to use the service component, for example. The response timeout is an error when the response to the request is not returned within a certain time.

  FIG. 3 is a schematic diagram showing the data structure and data example of the operation table in the present embodiment. The operation table includes columns of items of date, time, service ID, operation name, number of responses, and total response time. The operation name is a name of an operation of the service component (for example, in the case of a telephone service, calling or receiving). The number of responses is the number of responses to the request. The total response time is a total value of response times from when the execution control servers 1, 2, 3 transmit a request to when a response is received, and the unit is milliseconds (ms).

  FIG. 4 is a schematic diagram showing the data structure and data example of the operation-user table in the present embodiment. The operation-user table has columns of items of date, time, service ID, operation name, user ID, and number of requests. The user ID is identification information for identifying the user.

  FIG. 5 is a schematic diagram showing the data structure and data example of the user table in the present embodiment. The user table has columns of items of date, time, user ID, number of requests, and number of errors.

FIG. 6 is a block diagram showing a functional configuration of the profile server 21 in the present embodiment.
The profile server 21 includes a cascon function unit 22, a database registration control function unit 23, and a profile database 24.
The profile database 24 is a database that holds user information and service component information, and holds a user information table, a user block information table, a service component information table, a service component threshold information table, and an operation threshold information table. Yes.
The cascon function unit 22 provides an interface (for example, a web page) for updating service component information and user information held in the profile database 24. Specifically, the Cascon function unit 22 accepts service component information and user information registration requests, update requests, and deletion requests from the service requester terminals 11, 12, etc., and stores the profile database 24 via the database registration control function unit 23. Update. As a result, a user, a system maintenance operator who maintains and operates the service component management system, or a service provider who provides service components can update user information and service component information using a web browser or the like.
When the database registration control function unit 23 receives an update request for user information or service component information from the traffic information management server 14 or the cascon function unit 22, the database registration control function unit 23 updates the user information and service component information held in the profile database 24. The updated information is notified to the execution control servers 1, 2, and 3 by SOAP (Simple Object Access Protocol). However, even if the user authentication information (for example, password) is updated, the database registration control function unit 23 does not notify the execution control servers 1, 2, and 3 that the user authentication information has been updated. For example, when receiving an instruction to set a block flag for a service component from the traffic information management server 14, the database registration control function unit 23 sets a block flag for the service component stored in the profile database 24, and The execution control servers 1, 2 and 3 are notified that the block flag of the service component has been set. The block flag is a flag indicating whether or not the service component is in a block state. The blocked state is a state where the service component cannot be used.

  FIG. 7 is a schematic diagram illustrating a data structure and a data example of the user information table in the present embodiment. The user information table has columns of items of user ID and password as user information. The user ID is identification information for identifying the user. The password is a password for performing user authentication. In this embodiment, the password is user authentication information.

  FIG. 8 is a schematic diagram illustrating a data structure and a data example of the user blocking information table in the present embodiment. The user information table has columns of items of user ID and blockage flag (user blockage flag) as user information. The block flag is a flag indicating whether or not the user is in a block state (a state in which the service component cannot be used) in the component management system. The block flag “1” indicates the block state, and the block flag “0”. Indicates that it is not occluded.

  FIG. 9 is a schematic diagram illustrating a data structure and a data example of the service component information table in the present embodiment. The service component information table includes, as service component information, a service ID, a shaping value, a priority, a flow restriction flag, a block flag (service component block flag), a white list, a black list, a filter condition, It has a column for each item of processing to be applied. The service ID is identification information for identifying a service component. The shaping value is the number of requests that can be sent to the service component per second. The priority is a priority of each service component in traffic control. The flow restriction flag is a flag indicating whether or not the service component has flow control. The flow restriction flag “1” indicates that there is a flow restriction, and the flow restriction flag “0” indicates that there is no flow restriction. Represent. The block flag is a flag indicating whether or not the service component is in a block state (unusable state). The block flag “1” indicates a block state, and the block flag “0” is not a block state. Represents. The white list is a list of user IDs that can use the service component. The black list is a list of user IDs whose service components are temporarily unavailable. The filter condition is a filter condition for each request parameter. For example, it is conceivable to set “parameter a> 100 (the number of searches is 100 or more for one search)” or the like as a filter condition for the parameter a indicating the number of requests to be searched. The process to be applied is a process executed on the request in the execution control servers 1, 2, 3.

  FIG. 10 is a schematic diagram illustrating a data structure and a data example of the service component threshold information table in the present embodiment. The service component threshold information table has columns of items of service ID, service unavailability threshold, error threshold, and size threshold. The service unavailability threshold is a threshold relating to a rate at which a service becomes unavailable. The error threshold is a threshold relating to the error rate. The size threshold is a threshold related to the size of the request.

  FIG. 11 is a schematic diagram illustrating a data structure and a data example of the operation threshold information table in the present embodiment. The operation threshold information table includes columns of items of service ID, operation name, rate threshold, average response time threshold, and throttling threshold. The operation name is a name of an operation of the service component (for example, in the case of a telephone service, calling or receiving). The rate threshold is a threshold of the number of requests that one user can transmit to the service component in a rate monitoring period (for example, one day). The average response time threshold is a threshold related to the average response time for a request. The throttling threshold value is a threshold value for the number of requests that one user can transmit in a rate determination time (for example, a short cycle such as several seconds).

FIG. 12 is a block diagram showing a functional configuration of the execution control server 1 in the present embodiment.
In the execution control server cluster 4, load sharing is performed by causing a plurality of execution control servers 1, 2, and 3 to perform common processing in parallel. By performing load distribution, it is possible to increase the processing amount of requests to service components in the entire system. Further, the request processing amount of each execution control server 1, 2, 3 is reduced, so that requests can be processed at high speed.
The execution control server 1 includes an authentication function unit 5, a user block confirmation function unit 31, an authorization function unit 6, a database update notification reception function unit 33, a cache data management function unit 34, and a service component block confirmation function unit 32. A content filter function unit 7, a transfer execution control function unit 30, an authentication communication control function unit 27, a traffic control function unit 8, a transfer communication control function unit 29, a traffic information aggregation function unit 9, and a message proxy. And a functional unit 28. The functional configuration of the execution control servers 2 and 3 is the same as that of the execution control server 1.

The cache data management function unit 34 holds cache data of a user information table, a user blocking information table, and a service component information table. However, the cache data management function unit 34 does not hold user authentication information.
When the update of user information or service component information is notified from the profile server 21, the database update notification reception function unit 33 displays the user information table, user blockage information table, or service component information table held by the cache data management function unit 24. Update. For example, when the profile server 21 notifies that the block flag of the user block information table has been changed to “1”, the database update notification reception function unit 33 stores the user block stored in the cache data management function unit 34. Replace the block flag in the information table with “1”.
Thus, when the profile database 24 of the profile server 21 is updated, the cache data of the cache data management function unit 34 is also updated, so that the data held in the cache data management function unit 34 is always used as the latest data. can do. As a result, the execution control server 1 does not need to make an inquiry to the profile server 21 when processing is performed using the information held in the profile database 24, so that the processing can be performed at a higher speed. The execution control server 1 acquires the user authentication information from the profile database 24 of the profile server 21 when using the user authentication information.

  When the authentication communication control function unit 27 receives an authentication ticket issue request for a service component request (hereinafter referred to as a request) from the service requester terminal 11 (or 12), the authentication communication control function unit 27 outputs the received authentication ticket issue request to the authentication function unit 5. . The authentication ticket issue request is an authentication ticket issue request message for using the service component, and includes a user ID and a password. Further, when a response to the authentication ticket issuance request is input from the authentication function unit 5, the authentication communication control function unit 27 transmits the response to the requesting service requester terminal 11.

  The authentication function unit 5 includes a password authentication function unit 5-1 and an SSO (single sign-on) function unit 5-2. When the authentication ticket issuance request is input, the password authentication function unit 5-1 acquires user authentication information from the profile server 21 using the user ID included in the authentication ticket issuance request. If the user ID included in the authentication ticket issuance request is not stored in the profile server 21, the password authentication function unit 5-1 returns an error to the authentication communication control function unit 27 as a response to the authentication ticket issuance request. . Next, the password authentication function unit 5-1 performs password authentication for determining whether or not the password of the acquired user authentication information matches the password included in the authentication ticket issue request. When the passwords match (authenticate), the password authentication function unit 5-1 issues an authentication ticket as a response to the authentication ticket issuance request and outputs the authentication ticket to the authentication communication control function unit 27. The authentication ticket includes a user ID and an issuer's signature. On the other hand, when the passwords do not match, the password authentication function unit 5-1 returns an error to the authentication communication control function unit 27 as a response to the authentication ticket issue request. In this embodiment, the password authentication function unit 5-1 uses password authentication. However, in addition to password authentication, biometric authentication or authentication based on the identifiers of the service requester terminals 11 and 12 may be used. When the SSO function unit 5-2 receives a request for the service component from the service requester terminals 11 and 12 via the message proxy function unit 28, the SSO function unit 5-2 verifies the signature of the issuer of the authentication ticket included in the request, and performs proper authentication. It is determined whether the ticket is valid (the authentication ticket is valid). If the SSO function unit 5-2 determines that the ticket is a valid authentication ticket, the SSO function unit 5-2 outputs a request to the user blocking confirmation function unit 31 via the transfer execution control function unit 30. On the other hand, if it is determined that the ticket is not a valid authentication ticket, an error is returned to the service requester terminals 11 and 12. Note that once the password is authenticated, the user can use a plurality of service components by single sign-on using an authentication ticket.

  The user blocking confirmation function unit 31 is a function for blocking a request from a user whose contract violation is detected in the entire system, and determines whether or not the user is in a blocking state. Specifically, the user blocking confirmation function unit 31 acquires a blocking flag corresponding to the user ID included in the authentication ticket from the user blocking information table of the cache data management function unit 34, and the blocking flag is set (that is, Whether it is “1”). Then, when the blockage flag is set, the user blockage confirmation function unit 31 blocks the request and returns an error to the service requester terminal 11. On the other hand, if the block flag is not set, a request is output to the authorization function unit 6 via the transfer execution control function unit 30.

The authorization function unit 6 is a function for determining whether or not the user can use the service component of the request destination. The whitelist collation function unit 6-1, the blacklist collation function unit 6-2, and the ID conversion function unit 6-3. The white list collation function unit 6-1 is a function that determines whether or not the user has authority to use the requested service component. Specifically, the whitelist collation function unit 6-1 acquires the whitelist of the request destination service component from the service component information of the cache data management function unit 34, and the user ID included in the authentication ticket is registered in the whitelist. It is determined whether or not it has been done. Then, when the user ID is registered in the white list, the white list collation function unit 6-1 outputs a request to the black list collation function unit 6-2. On the other hand, when the user ID is not registered in the white list, the white list collation function unit 6-1 blocks the request and returns an error to the service requester terminal 11. The blacklist collation function unit 6-2 is a function that determines whether or not the user has temporarily stopped using the requested service component. Specifically, the blacklist collation function unit 6-2 acquires the blacklist of the service component of the request destination from the service component information table of the cache data management function unit 34, and the user ID included in the authentication ticket becomes a blacklist. Judge whether it is registered or not. Then, when the user ID is not registered in the black list, the black list collation function unit 6-2 outputs a request to the ID conversion function unit 6-3. On the other hand, when the user ID is registered in the black list, the request is blocked and an error is returned to the service requester terminal 11 via the message proxy function unit 28. The ID conversion function unit 6-3 converts the user ID included in the authentication ticket into a user ID in the service component of the request destination, and outputs the request to the service component blockage confirmation function unit 32 via the transfer execution control function unit 30. . Note that a table indicating the correspondence between the user ID and the user ID in each service component is stored in the profile database 24 of the profile server 21, and the cache data management function unit 34 holds it as cache data.
The white list collation function unit 6-1 and the black list collation function unit 6-2 acquire the white list or black list from the cache data management function unit 34. If the black list does not exist, it is acquired from the profile server 21.
In the present embodiment, both the processing of the whitelist matching function unit 6-1 and the processing of the blacklist matching function unit 6-2 are performed, but the processing of the whitelist matching function unit 6-1 is not performed. You may perform only the process of the blacklist collation function part 6-2. Alternatively, only the process of the white list collation function unit 6-1 or the process of the black list collation function unit 6-2 may be performed.

The service component blockage confirmation function unit 32 is a function for determining whether or not the service component at the request destination is blocked due to suspension of use or SLA (Service Level Agreement) violation. Specifically, the service component blockage confirmation function unit 32 acquires a blockage flag corresponding to the service component of the request destination from the service component information table of the cache data management function unit 34, and the blockage flag is set (that is, “ 1 ”). When the block flag is set, the service component confirmation function unit 32 blocks the request and returns an error to the service requester terminal 11. On the other hand, the component confirmation function unit 32 transfers the request to the throttling server 10 via the transfer execution control function unit 30 when the blocking flag is not set.
In this embodiment, the service component blockage confirmation function unit 32 performs the process after the authorization function unit 6 performs the authorization process, but the service component blockage confirmation function unit 32 first confirms the blockage of the service component. Later, the authorization function unit 6 may perform an authorization process.

  The content filter function unit 7 is a function that prevents disturbance (such as spam) and determines whether or not an invalid parameter is included in the request. When a request is input from the throttling server 10 via the transfer execution control function unit 30, the content filter function unit 7 sets a filter condition corresponding to the request destination service component in the service component information table of the cache data management function unit 34. To determine whether each parameter included in the request matches the filter condition. When there is a parameter that matches the filter condition, the content filter function unit 7 blocks the request and returns an error to the service requester terminal 11. On the other hand, when there is no parameter that matches the filter condition, the content filter function unit 7 outputs a request to the traffic control function unit 8 via the transfer execution control function unit 30.

  The traffic control function unit 8 is a function that limits the maximum number of requests per unit time for each service component, and includes a shaping function unit 8-1, a priority control function unit 8-2, and a flow regulation function unit 8-3. Consists of including. The shaping function unit 8-1 is a function that shapes requests so that an excessive number of requests do not flow to the service component. Specifically, first, the shaping function unit 8-1 temporarily stores the request in a queue. Then, the shaping value of the service component of the request destination is acquired from the service component information table of the cache data management function unit 34, the request is taken out from the queue so as to match the acquired shaping value, and output to the priority control function unit 8-2 To do. Specifically, the shaping function unit 8-1 retains data indicating how many times a request has been extracted from the queue per second, and refers to the data, and requests the request when the number of requests extracted is smaller than the shaping value. The data is taken out from the queue and output to the priority control function unit 8-2. The priority control function unit 8-2 is a function for transferring requests in order from the service component with the highest priority. Specifically, the priority control function unit 8-2 acquires the priority of each service component from the service component information table of the cache data management function unit 34, and the flow regulation function unit in order from the request of the service component with the highest priority. Output to 8-3. The flow restriction function unit 8-3 is a function that uniformly delays requests to service components having flow restriction. Specifically, the flow control function unit 8-3 acquires the flow control flag corresponding to the service component of the request destination from the service component information table of the cache data management function unit 34, and the flow restriction flag is set (that is, If the request is “1”, the request is uniformly delayed for a fixed time, and then the request is sent to the service component server 25 via the transfer execution control function unit 30, the transfer communication control function unit 29, and the message proxy function unit 28. And a request is output to the traffic information totaling function unit 9 via the transfer execution control function unit 30 and the transfer communication control function unit 29. This can limit excessive requests to congested service components.

  The message proxy function unit (transmission unit, reception unit) 28 receives a request to the service component from the service requester terminal 11 (or 12), and transfers the received request to the transfer communication control function unit 29 and the transfer execution control function unit 30. To the SSO function unit 5-2 of the authentication function unit 5. The message proxy function unit 28 includes an authentication function unit 5, a user blocking confirmation function unit 31, an authorization function unit 6, a service component blocking confirmation function unit 32, a content filter function unit 7, and a traffic control function unit 8. When the request for which the processes in (1) and (2) are completed is called from the transfer communication control function unit 29, the request is transferred to the service component server 25. When the message proxy function unit 28 receives a response to the request from the service component server 25, the message proxy function unit 28 outputs the response to the transfer communication control function unit 29. The message proxy function unit 28 transfers the response to the service requester terminal 11 when a response for which processing such as log output related to the response has been completed is input from the transfer communication control function unit 29.

  The transfer execution control function unit 30 acquires processing to be applied to the service component of the request destination from the service component information table of the cache data management function unit 34, and sequentially outputs the request to each unit according to the acquired processing to be applied. For example, in a case where a request to a certain service component is set to a process that applies that the process of the content filter function unit 7 is not performed, the transfer execution control function unit 30 sends a request to the content filter function unit 7. Do not output. Or you may set to the process which applies performing only the process of the black list collation function part 6-2, without performing the process of the white list collation function part 6-1. In this way, the processing applied to each server component can be customized in various ways. Thereby, processing unnecessary for a certain service component can be omitted, and the time for performing common processing can be shortened.

The transfer communication control function unit 29 is a function that mediates communication between the message proxy function unit 28 and the transfer execution control function unit 30. When a request for which common processing is completed is input, a log related to the request is output. The request is output to the traffic information totaling function unit 9 and the message proxy function unit 28. When a response is input from the message proxy function unit 28, a log related to the response is output, and the response is output to the traffic information totaling function unit 9 and the message proxy function unit 28.
The traffic information totaling function unit 9 generates traffic information based on the request and response, and transmits the generated traffic information to the traffic information management server 14 by polling.

FIG. 13 is a block diagram showing a functional configuration of the traffic information management server 14 in the present embodiment.
The traffic information management server 14 collects traffic information from a plurality of execution control servers 1, 2, 3 and aggregates it, and performs service component quality monitoring control by aggregating all traffic information. As a result, the entire system can be matched, and inconsistencies in service component quality monitoring control can be prevented. The traffic information management server 14 includes a traffic collection function unit 15, a traffic aggregation function unit 16, a service component monitoring function unit 17, a user monitoring function unit 18, and a reaction function unit 19.

The traffic collection function unit 15 collects traffic information from the execution control servers 1, 2, and 3 by polling at every traffic information generation time, and outputs the traffic information to the traffic aggregation function unit 16.
The traffic totalization function unit 16 totalizes the input traffic information. Specifically, the traffic counting function unit 16 counts the number of requests and the number of errors for each service component. Further, the traffic totalization function unit 16 counts the number of responses and the total response time for each operation. Moreover, the traffic totalization function unit 16 counts the number of requests for each set of operation and user. The traffic totalization function unit 16 counts the number of requests, the number of errors, and the total number of request messages for each user. Then, the traffic totalization function unit 16 transmits the value counted together with the date and time when the traffic information is generated to the traffic information database 20 to be stored.

  A monitoring execution control function unit (not shown) is a function that causes the service component monitoring function unit 17 and the user monitoring function unit 18 to perform processing independently at a fixed time or a fixed cycle. The processing in the service component monitoring function unit 17 and the user monitoring function unit 18 is service component monitoring control.

  The service component monitoring function unit 17 is a function for extracting a service component to be in a blocked state or a service component to be in a flow restriction state, and includes a service component unavailability monitoring function unit and a response delay monitoring function unit.

  The service component unavailability monitoring function unit is a function that monitors whether the number of responses of the service component is within an allowable range, and executes the following processing for each service component. First. The service component unavailability rate function unit obtains a service unavailability rate threshold corresponding to the service component from the profile server 21, and this service component unavailability rate monitoring period (for example, 1 hour) from the service component table of the traffic information database 20. Get service component request count and error count response timeout. Then, the service component unusable rate function unit determines whether the ratio of the response timeout number to the acquired number of requests (error rate) exceeds the service unusable rate threshold. When the error rate is larger than the service unavailability rate threshold, it is determined that this service component is blocked, and the fact is notified to the reaction function unit 19 via the monitoring execution control function unit.

  The response delay monitoring function unit executes the following processing for the operation of each service component. First, the response delay monitoring function unit obtains an average response time threshold corresponding to the operation from the profile server 21, and from the operation table of the traffic information database 20, the operation response time total and response in the response delay monitoring period (for example, 1 hour). Get the number. Then, the response delay monitoring function unit determines whether or not a value obtained by dividing the number of responses by the total response time (average response time) is larger than the average response time threshold. When the average response time is larger than the average response time threshold, the response delay monitoring function unit determines that the service component of this operation is in the flow restriction state, and notifies the reaction function unit 19 via the monitoring execution control function unit. Notice.

  The user monitoring function unit 18 is a function for extracting users temporarily unavailable for a specific service component, and includes a rate monitoring function unit, an error rate monitoring function unit, and a message size monitoring function unit. .

  The rate monitoring function unit is a function that monitors whether or not the number of requests to a service component of a certain user exceeds the usage limit number, and performs the following processing for each operation. The rate monitoring function unit acquires a rate threshold value for the operation from the profile server 21, and calculates the number of requests in the rate monitoring period (for example, from 0:00 to 24:00 today) from each user to the operation of the traffic information database 20. Get from user table. Next, the rate monitoring function unit extracts users whose number of requests is greater than the rate threshold. Then, the rate monitoring function unit determines that the user whose number of requests is greater than the rate threshold value is temporarily unavailable for the service component of the operation, and notifies the reaction function unit 19 via the monitoring execution control function unit. Notice.

  The error rate monitoring function unit is a function for checking whether or not the user is using the service component illegally, and performs the following processing for each set of the user and the service component. The error rate monitoring function unit obtains an error threshold for the service component from the profile server 21, and from the user table of the traffic information database 20, the number of requests in each user's error rate monitoring period (for example, from 0:00 to 24:00 today) Get the number of errors. Next, the error rate monitoring function unit extracts a user whose ratio of error numbers to the number of requests (error rate) is larger than an error threshold. Then, the error rate monitoring function unit determines that a user whose error rate is greater than the error threshold is temporarily unavailable for the service component, and notifies the reaction function unit 19 via the monitoring execution control function unit. To do.

  The message size monitoring function unit is a function for checking whether or not the message size of the request from the user to the service component is too large, and performs the following processing for each set of user and service component. The message size monitoring function unit obtains a size threshold for the service component from the profile server 21, and from the user table of the traffic information database 20, the number of requests in each user's message size monitoring period (for example, from 0:00 to 24:00 today) Get the total request message size. Next, the message size monitoring function unit extracts users whose value obtained by dividing the total request message size by the number of requests (average request message size) is larger than the size threshold. Then, the message size monitoring function unit determines that a user whose average request message size is larger than the size threshold value is temporarily unavailable for the service component, and notifies the reaction function unit 19 via the monitoring execution control function unit to that effect. To be notified.

  When the service component to be blocked is notified from the service component monitoring function unit 17 via the monitoring execution control function unit, the reaction function unit 19 transmits an instruction for setting a blocking flag to the service component to the profile server 21. When receiving the instruction to set the block flag, the profile server 21 sets the block flag of the service component in the service component information table to “1”. Then, the alarm notification function of the reaction function unit 19 notifies the service component server 25, the system maintenance operator's terminal, and the like by e-mail or the like that the request transfer to the service component has been stopped.

  When the service component to be set in the flow restriction state is notified from the service component monitoring function unit 17 via the monitoring execution control function unit, the reaction function unit 19 issues an instruction to set a flow restriction flag for the service component configuration to the profile server. 21 to send. When receiving the instruction to set the flow control flag, the profile server 21 sets the flow control flag of the service component in the service component information table to “1”. Then, the alarm notification function of the reaction function unit 19 notifies the service component server 25, the system maintenance operator's terminal, etc. by e-mail or the like that the request transfer flow restriction for the service component has been performed.

  Also, when the reaction function unit 19 is notified of a user to temporarily disable a service component from the user monitoring function unit 18 via the monitoring execution control function unit, the user is added to the black list of the service component. Is sent to the profile server 21. When receiving an instruction to add a user to the black list, the profile server 21 adds the user ID of the user to the black list in the service component information table. Then, the alarm notification function of the reaction function unit 19 notifies the service requester terminals 11 and 12 of the user and the terminal of the system maintenance operator by e-mail or the like.

Here, the difference in concept between the throttling processing in the throttling server 10, the processing of the rate monitoring function unit in the traffic information management server 14, and the processing of the shaping function unit 8 in the execution control servers 1, 2 and 3 will be described. .
First, the processing of the shaping function unit 8 monitors the number of requests that can be transmitted to a specific service component in a certain time. For example, for the service component A, it is conceivable to set the shaping value so that all users total 100 times per second.
Next, the throttling process is a function for eliminating malicious users, and monitors the number of requests that can be transmitted from a specific user to a specific service component in a short period of time. For example, for the service component A, it is conceivable to set a throttling threshold so that one user can transmit up to five times per second.
Finally, the processing of the rate monitoring function unit is a function for eliminating the limit number of times defined by the contract, and monitors the number of requests that a specific user can transmit to a specific service component in a long period of time. . For example, it is conceivable to set a rate threshold value so that one user can transmit up to five times per day for the service component A.
Although the throttling process and the process of the rate monitoring function unit are the same in function, the throttling server 10 counts the number of requests on the memory in order to prevent a short-cycle attack, whereas the rate monitoring function unit Since the traffic information is monitored at a long period, the traffic information management server 14 counts the number of requests at a constant period and holds the number of requests in the traffic information database 20.

Next, the operation of the service component management system described above will be described with reference to FIGS. FIG. 14 is a sequence diagram showing the procedure of the authentication ticket issuing process.
First, the service requester terminal 11 transmits an authentication ticket issue request to the execution control server 1 (step Sa1). In the execution control server 1, the authentication communication control function unit 27 receives the authentication ticket issue request and outputs it to the password authentication function unit 5-1 of the authentication function unit 5 (step Sa2). The password authentication function unit 5-1 inquires of the profile server 21 about user authentication information using the user ID included in the authentication ticket issue request (step Sa3). The profile server 21 returns the user authentication information corresponding to the received user ID to the password authentication function unit 5-1 of the execution control servers 1, 2, 3 (step Sa4). Next, the password authentication function unit 5-1 performs password authentication, and upon authentication, generates an authentication ticket (step Sa5). Then, the password authentication function unit 5-1 outputs the generated authentication ticket to the authentication communication control function unit 27 (step Sa6). The authentication communication control function unit 27 returns the authentication ticket to the service requester terminal 11 that has issued the authentication ticket issuance request (step Sa7).

FIGS. 15 and 16 are sequence diagrams showing a procedure of common processing for service component requests.
First, the service requester terminal 11 transmits a request for a service component to the execution control server 1 (step Sb1). In the execution control server 1, the message proxy function unit 28 receives the request, and outputs the received request to the SSO function unit 5-2 of the authentication function unit 5 via the transfer communication control function unit 29 and the transfer execution control function unit 30. (Step Sb2). When the SSO function unit 5-2 verifies the signature of the authentication ticket included in the request and determines that it is a legitimate authentication ticket, the SSO function unit 5-2 sends a request to the user blocking confirmation function unit 31 via the transfer execution control function unit 30. Output (step Sb3). The user blocking confirmation function unit 31 acquires a blocking flag for the user ID included in the authentication ticket from the user blocking information table of the cache data management function unit 34, and determines whether the blocking flag is set. If the blockage flag is not set, a request is output to the whitelist verification function unit 6-1 of the authorization function unit 6 via the transfer execution control function unit 30 (step Sb4). If the block flag is set, the user block check function unit 31 blocks the request and returns an error to the service requester terminal 11.

  The whitelist collation function unit 6-1 acquires the whitelist of the request destination service component from the service component information table of the cache data management function unit 34, and whether or not the user ID included in the authentication ticket is registered in the whitelist. Determine whether. Then, when the user ID is registered in the white list, the white list collation function unit 6-1 outputs a request to the black list collation function unit 6-2 (step Sb5). If the user ID is not registered in the white list, the white list collation function unit 6-1 blocks the request and returns an error to the service requester terminal 11. The blacklist matching function unit 6-2 acquires the blacklist of the requested service component from the service component information table of the cache data management function unit 34, and whether or not the user ID included in the authentication ticket is registered in the blacklist. Determine whether. Then, when the user ID is not registered in the black list, the black list collation function unit 6-2 outputs a request to the ID conversion function unit 6-3 (step Sb6). If the user ID is registered in the black list, the request is blocked and an error is returned to the service requester terminal 11.

The ID conversion function unit 6-3 converts the user ID included in the authentication ticket into a user ID in the service component of the request destination, and outputs the request to the service component blockage confirmation function unit 32 via the transfer execution control function unit 30. (Step Sb7). The service component blockage confirmation function unit 32 acquires a blockage flag corresponding to the request destination service component from the service component information table of the cache data management function unit 34, and determines whether or not the blockage flag is set. Then, when the block flag is not set, the service component block confirmation function unit 322 transfers the request to the throttling server 10 via the transfer execution control function unit 30 (step Sb8). The service component blockage confirmation function unit 322 blocks the request and returns an error to the service requester terminal 11 when the blockage flag is set.
In this example, the service component blockage confirmation function unit 32 performs processing after the authorization function unit 6 performs processing, but the user blockage confirmation function unit 31 and the service component blockage confirmation function unit 32 perform processing. The authorization function unit 6 may perform processing later. Further, the processing of the black list matching function unit 6-2 may be performed without performing the processing of the white list matching function unit 6-1.

  When the throttling server 10 receives a request from the execution control server 1, the throttling server 10 determines whether the number of requests within the rate determination time from the service requester terminal 11 to the service component server 25 exceeds the throttling threshold. If the number of requests is equal to or less than the throttling threshold, the request is transferred to the execution control server 1 (step Sb9). If the number of requests exceeds the throttling threshold, the throttling server 10 blocks the request and returns an error to the execution control server 1. In the execution control server 1, the content filter function unit 7 receives the request, and determines whether each parameter included in the request matches the filter condition. Then, when there is no parameter that matches the filter condition, the content filter function unit 7 outputs a request to the shaping function unit 8-1 of the traffic control function unit 8 via the transfer execution control function unit 30 (step Sb10). . If there is a parameter that matches the filter condition, the content filter function unit 7 blocks the request and returns an error to the service requester terminal 11.

  The shaping function unit 8-1 acquires the shaping value of the request destination service component from the service component information table of the cache data management function unit 34, and sends the request to the priority control function unit 8-2 so as to match the acquired shaping value. (Step Sb11). The priority control function unit 8-2 acquires the priority of each service component from the service component information table of the cache data management function unit 34, and outputs it to the flow regulation function unit 8-3 in order from the request of the service component with the highest priority. (Step Sb12). The flow restriction function unit 8-3 acquires the flow control flag corresponding to the service component of the request destination from the service component information table of the cache data management function unit 34, and when the flow restriction flag is set, the request is uniformly set. The request is transferred to the service component server 25 via the transfer execution control function unit 30, the transfer communication control function unit 29, and the message proxy function unit 28 (step Sb13) and the transfer execution control function The request is output to the traffic information totaling function unit 9 via the unit 30 and the transfer communication control function unit 29 (step Sb14). The traffic information totaling function unit 9 generates traffic information and transmits the traffic information generated by polling from the traffic information management server 14 to the traffic collection function unit 15 of the traffic information management server 14 (step Sb15).

FIG. 17 is a sequence diagram showing a procedure of rate monitoring processing.
The traffic collection function unit 15 of the traffic information management server 14 collects traffic information every few minutes by polling from the execution control server 1 and outputs it to the traffic aggregation function unit 16 (step Sc1). The traffic aggregation function unit 16 aggregates the input traffic information and transmits the aggregated result to the traffic information database 20 (step Sc2). The traffic information database 20 stores the received data (step Sc3).

  The monitoring execution control function starts the rate monitoring function of the user monitoring function unit 18 after the traffic totaling function unit 16 totals the traffic information (step Sc4). The user monitoring function unit 18 acquires a rate threshold value from the service component threshold value information table of the profile server 21 (step Sc5), and from the operation-user table of the traffic information database 20, the number of requests in the rate monitoring time for each set of user and operation. (Step Sc6), a set of users and operations whose number of requests exceeds the rate threshold is extracted, and the monitoring execution control function as a user who makes the extracted users temporarily unavailable to the service component of the operations (Step Sc7). The monitoring execution control function unit issues a reaction to the user blocking function and the alarm notification function of the reaction function unit 19 (step Sc8). The user blocking function of the reaction function unit 19 transmits to the profile server 21 an instruction to add a user who is temporarily unavailable to the service component to the black list of the service component (step Sc9). The profile server 21 adds the user ID of the user to the black list of the service component in the service component information table stored in the profile database 24. Further, the alarm notification function of the reaction function unit 19 notifies the alarm by sending a warning mail to the service requester terminal 11 of the user and the terminal of the system maintenance operator (step Sc10).

FIG. 18 is a sequence diagram showing the procedure of the profile database update viewing process.
A service provider, a user, or a system maintenance operator registers, updates, and deletes service component information or user information from a web page provided by the Cascon function unit 22 of the profile server 21 using a web browser or the like. In addition, when a service provider detects a malicious user, the service provider performs user blockage that can temporarily stop the use of the user. Information input from the web page is transmitted from the service requester terminal 11 to the Cascon function unit 22 (step Sd1), for example. The cascon function unit 22 outputs the received information to the database registration control function unit 23 (step Sd2). The database registration control function unit 23 updates and saves service component information or user information stored in the profile database 24 based on the received information (step Sd3). Further, the database registration control function unit 23 notifies the information updated in the profile database 24 to the database update notification reception function unit 33 of the execution control servers 1, 2, and 3.

On the other hand, when an instruction to add a user in the service component black list with the reaction function unit 19 of the traffic information management server 14 is transmitted to the profile server 21, the database registration control function unit 23 receives the instruction ( Step Sd4). Then, the database registration control function unit 23 adds the user ID of the user to the black list of the service component, and updates the profile database 24 (step Sd5). Subsequently, the database registration control function unit 23 notifies the database update notification reception function unit 33 of the execution control servers 1, 2, and 3 that the user has been added to the black list of the service component (step Sd6). Thereby, the database update notification reception function unit 33 updates the cache data stored in the cache data management function unit 34.
The execution control servers 1, 2, and 3 access the profile database 24 when necessary when using data that is not stored in the cache data management function unit 34 (for example, at the first user authentication). The stored information is referred to (step Sd7).

As described above, according to the present embodiment, the traffic information management server 14 collects and aggregates traffic information from the plurality of execution control servers 1, 2, 3 and performs each service component quality monitoring control. Even if a plurality of execution control servers 1, 2, and 3 perform processing in parallel, the consistency of traffic information can be maintained as a whole system.
In addition, since a plurality of execution control servers 1, 2, and 3 perform request processing to the service component in parallel, the request processing amount to the service component in unit time can be improved.
In addition, since the execution control servers 1, 2, and 3 perform the common processing for each service component in a lump, the investment and expense for implementing functions (non-functional requirements) other than service components on the service provider side are reduced. can do.
In addition, the execution control servers 1, 2, and 3 can prevent the influence of the service component server in which the failure has occurred from spreading to other service components by blocking the request to the service component in the blocked state.
Further, since the service provider, the user, or the system maintenance operator can add / update / delete user information and service component information from the Cascon function unit 22 of the profile server 21, it is possible to easily use this service. A new application can be easily created by using a plurality of service components.

Further, a program for realizing the functions of the profile server shown in FIG. 6, the execution control server shown in FIG. 12, the traffic information management server shown in FIG. 13, and the throttling server is recorded on a computer-readable recording medium. Service component management processing may be performed by causing a computer system to read and execute a program recorded on a recording medium. Here, the “computer system” may include an OS and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

Further, the “computer-readable recording medium” means a volatile memory (for example, DRAM (Dynamic DRAM) in a computer system that becomes a server or a client when a program is transmitted through a network such as the Internet or a communication line such as a telephone line. Random Access Memory)), etc., which hold programs for a certain period of time.
The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line.
The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

As described above, the embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to the above, and various design changes and the like can be made without departing from the scope of the present invention. It is possible to
For example, in the present embodiment, three execution control servers are used, but two or more servers may be used.

It is a block diagram which shows the structure of the service component management system by one Embodiment of this invention. It is the schematic which shows the data structure and data example of a service component table in this embodiment. It is the schematic which shows the data structure and data example of the operation table in this embodiment. It is the schematic which shows the data structure and data example of the operation-user table in this embodiment. It is the schematic which shows the data structure and data example of a user table in this embodiment. It is a block diagram which shows the function structure of the profile server in this embodiment. It is the schematic which shows the data structure and data example of the user information table in this embodiment. It is the schematic which shows the data structure and data example of a user blockage information table in this embodiment. It is the schematic which shows the data structure and data example of the service component information table in this embodiment. It is the schematic which shows the data structure and data example of the service component threshold value information table in this embodiment. It is the schematic which shows the data structure and data example of the operation threshold value information table in this embodiment. It is a block diagram which shows the function structure of the execution control server in this embodiment. It is a block diagram which shows the function structure of the traffic information management server in this embodiment. It is a sequence diagram which shows the procedure of the authentication ticket issue process in this embodiment. It is a sequence diagram which shows the procedure of the common process with respect to the service component request in this embodiment. It is a sequence diagram which shows the procedure of the common process with respect to the service component request in this embodiment. It is a sequence diagram which shows the procedure of the rate monitoring process in this embodiment. It is a sequence diagram which shows the procedure of the profile database update view process in this embodiment.

Explanation of symbols

  1, 2, 3 ... Execution control server 4 ... Execution control server cluster 5 ... Authentication function part 5-1 ... Password authentication function part 5-2 ... SSO function part 6 ... Authorization function part 6-1 ... White list collation function part 6 -2 ... Blacklist verification function unit 6-3 ... ID conversion function unit 7 ... Content filter function unit 8 ... Traffic control function unit 8-1 ... Shaping function unit 8-2 ... Priority control function unit 8-3 ... Flow regulation function Unit 9 ... Traffic totaling function unit 10 ... Throttling server 11, 12 ... Service requester terminal 13 ... Network 14 ... Traffic information management server 15 ... Traffic collecting function unit 16 ... Traffic totaling function unit 17 ... Service component monitoring function unit 18 ... User Monitoring function unit 19 ... Reaction function unit 20 ... Traffic Information database 21 ... Profile server 22 ... Cascon function unit 23 ... Database registration control function unit 24 ... Profile database 25 ... Service component server 28 ... Message proxy function unit 29 ... Transfer communication control function unit 30 ... Transfer execution control function unit 31 ... User Blocking confirmation function unit 32 ... Service component blocking confirmation function unit 33 ... Database update notification reception unit 34 ... Cache data management function unit

Claims (9)

A profile that holds user information including a black list that is a list of users whose service components are temporarily unavailable, and service component information including a service component blocking flag indicating whether or not the service component is blocked. A database,
Upon receiving an update request for the user information or the service component information, a database registration control function unit that updates the service component information or the user information held in the profile database;
A profile server comprising:
A receiving unit for receiving a request from the user terminal to the service component;
Based on the black list, a black list matching function unit that determines whether or not the user can temporarily use the service component;
A service component blocking confirmation function unit that determines whether the service component is blocked based on the service component blocking flag;
When the blacklist matching function unit determines that the user is not temporarily unavailable for the service component and the service component blockage confirmation function unit determines that the service component is not blocked, the service A transmission unit for transmitting the request to the service component server of the component;
Based on the request, traffic information including statistical information for each user indicating the status of a request from a specific user to a specific service component and error rate information for each service component indicating an error status of the specific service component is generated based on the request. A traffic information totaling function unit for transmitting traffic information to a traffic information management server;
A plurality of execution control servers comprising:
A traffic collection function unit that receives the traffic information from the execution control server;
A traffic counting function unit for counting the traffic information received by the traffic collecting function unit;
A service component monitoring function unit that extracts service components to be blocked based on the error rate information for each service component that is aggregated by the traffic aggregation function unit;
A user monitoring function unit that extracts users temporarily unavailable for a specific service component based on the statistical information for each user that is aggregated by the traffic aggregation function unit;
An update request for the service component blocking flag corresponding to the service component extracted by the service component monitoring function unit is transmitted to the profile server, and the user extracted by the user monitoring function unit is referred to as the black of the specific service component. A reaction function unit that transmits an update request to be added to the list to the profile server;
A traffic information management server comprising:
A service component management system comprising: The service component information includes a flow control flag indicating whether to perform flow control on the service component,
The traffic information includes response time information indicating a response time situation from a specific service component,
The service component monitoring function unit extracts a service component that performs flow control based on the response time information aggregated by the traffic aggregation function unit;
The reaction function unit transmits an update request for the flow control flag corresponding to the service component performing flow control extracted by the service component monitoring function unit to the profile server,
2. The service component management system according to claim 1, wherein the execution control server includes a flow restriction function unit that uniformly delays the request to the service component for a predetermined time based on the flow control flag. . The execution control server is
Upon receiving an authentication ticket request from the user's terminal, user authentication is performed, and when authenticated, a password authentication function unit that issues an authentication ticket and sends it back to the terminal;
When a request from the user terminal to the service component is received by the receiving unit, a single sign-on function unit that verifies an authentication ticket included in the request;
The service component management system according to claim 1 or 2, further comprising: The component service information includes a white list that is a list of users who can use the service component,
The execution control server has a white list matching function unit that determines whether or not the user is registered in the white list.
The service component management according to any one of claims 1 to 3, wherein the transmission unit transmits the request to the service component server only when the user is registered in the white list. system. When the database registration control function unit updates the profile database, it notifies the execution control server to that effect,
The execution control server is
A cache data management function unit for holding the user information and the service component information;
When the update of the user information or the service component information is notified from the profile server, the database update notification function unit for updating the user information or the service component information held by the cache data management function unit;
The service component management system according to any one of claims 1 to 4, further comprising: A throttling server for notifying the execution control server of an error when the number of requests transmitted from the user to the service component within a predetermined time exceeds a predetermined threshold;
The service component management according to any one of claims 1 to 5, wherein the transmission unit transmits the request to the service component server only when an error is not notified from the throttling server. system.   The said profile server is provided with the Cascon function part which receives the registration, update, and deletion of the said service component information and the said user information which are memorize | stored in the said profile database, The any one of Claim 1 to 6 characterized by the above-mentioned. Service component management system. A receiving unit for receiving a request from the user terminal to the service component;
Based on a blacklist that is a list of users whose service components are temporarily unavailable, a blacklist matching function unit that determines whether or not the user can temporarily use the service components;
A service component blocking confirmation function unit that determines whether the service component is blocked based on a service component blocking flag that indicates whether the service component is blocked;
When the blacklist matching function unit determines that the user is not temporarily unavailable for the service component and the service component blockage confirmation function unit determines that the service component is not blocked, the service A transmission unit for transmitting the request to the service component server of the component;
Traffic information including user-specific statistical information indicating the status of a request from a specific user to a specific service component and service component-specific error rate information indicating an error status of the specific service component is generated based on the request. A traffic information totaling function unit for transmitting the traffic information to the traffic information management server;
An execution control server comprising: A profile that holds user information including a black list that is a list of users whose service components are temporarily unavailable, and service component information including a service component blocking flag indicating whether or not the service component is blocked. A profile server comprising a database, when receiving an update request for the user information or the service component information, updating the service component information or the user information held in the profile database;
The execution control server receiving a request from the user terminal to the service component;
The execution control server determining, based on the black list, whether the user is temporarily unable to use the service component;
The execution control server determines whether or not the service component is blocked based on the service component block flag;
When the execution control server determines that the user is not temporarily unavailable to the service component and determines that the service component is not blocked, the execution control server sends the request to the service component server of the service component. Sending, and
The execution control server includes traffic information including user-specific statistical information indicating a request status from a specific user to a specific service component and service component error rate information indicating an error status of the specific service component in the request. And generating the traffic information based on the traffic information to the traffic information management server,
A traffic information management server receiving the traffic information from the execution control server;
The traffic information management server totalizing the received traffic information;
The traffic information management server extracts service components to be blocked based on the aggregated error rate information for each service component, and
The traffic information management server extracting users temporarily unavailable for a specific service component based on the aggregated statistical information for each user;
The traffic information management server sends an update request for the service component block flag corresponding to the extracted service component to be blocked to the profile server, and the user who has made the temporary use of the extracted specific service component Sending an update request to be added to the blacklist to the profile server;
A service component management method comprising:

Images