JP2009205265A - Method, device, and program for determining call destination - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a call destination determination method which dynamically determines an optimal calling/called user (call destination) in consideration of attributes of each user. <P>SOLUTION: The call destination determination method extracts event information corresponding to input information (x=router14) from a domain object 52 (S201) by using a repository 51 which stores call destination information which includes a plurality of attribute information containing identification information (SIP URI (Uniform Resource Identifier)), a domain object 52 which defines an event as a trigger in determining the call destination by a plurality of attribute information, and a policy 53 which defines a relation between the attributes of the call destination information and event information; retrieves the repository 51, the policy 53 and extracted event information by using a query retrieval expression 54 (S202); and specifies the call destination with reference to the policy 53 from the retrieval result and outputs the call destination (S203-204). <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention uses a technology for generating a cooperation scenario in a system that executes services by linking element services constituting services distributed on a network, for example, and when a certain event occurs, a connection destination corresponding to this event is determined. The present invention relates to a connection destination determination method and apparatus suitable for use in dynamic determination.

  In recent years, service cooperation technology has attracted attention as one of the technologies for realizing SOA (Service Oriented Architecture). Services are defined as Web (Web) service interface based on WSDL (Technical specification defined by Web Services Description Language) specification and service interface based on UPnP (Universal Plug and Play) specification, SOAP (Simple Object Access Protocol; international standardization organization) Provides a function to send and receive messages according to technical specifications established by W3C). A workflow that executes these interface-defined services sequentially or in parallel, that is, a cooperation scenario, is executed by a scenario execution engine. The interface-defined service that is referred to and called in the cooperation scenario is referred to as a service component in the present invention.

  Generally, BPEL (Business Process Execution Language) or the like is used as a workflow description language for describing a complex workflow using a Web service. A scenario execution engine that executes a workflow based on the BPEL description is called a BPEL engine. In addition to the BPEL system, there is a system (Patent Document 1) and a service that has a function of discovering an intermediary service and synthesizing the service including this if the interface between the scenario execution engine and the element service cannot be established. There is a system (Patent Document 2) that enables dynamic adaptation to other service elements having equivalent functions in the same area.

  Service components exist not only in services on the Internet but also in services of telecom networks. Parley X (Parlay X Web Services Specification, Version 3.0, http://www.parlay.org/en/specifications/pxws.asp) is a specification for converting a telecom network service into a service component. Parley X's Third Party Call Control (3PCC) API (Application Programming Interface) is an input parameter that represents the Uniform Resource Identifier (URI) of SIP UA (Session Initiation Protocol User Agent; callParticipant (s) such as source and destination) have. Here, callParticipant (s) is a public interface (interface accessible from all classes) that represents a connection destination (call participant) defined in the 3PCC API.

  As an example of a service that applies the 3PCC API, for example, when a failure occurs in the server, a scenario in which the administrator and the maintenance staff are connected by a conference call is considered. In this case, maintenance costs can be reduced by automating the determination of maintenance personnel who are familiar with the on-site failure equipment. In such a scene, a system that dynamically determines the incoming and outgoing users is required.

  The related conventional caller / caller determination method is to specify from the connection source terminal by dialing, etc., and since the connection destination terminal is uniquely specified by the caller, the communication network is connected to the specified connection destination terminal. Is the most common. Further, as a more advanced method, there is a method of selecting from a connection destination terminal registered in a connection destination specific node according to a predetermined procedure in a toll-free service or the like. As a result, the connection destination can be changed according to the state of the connection destination terminal (in use, etc.) and the transmission area information of the connection source terminal (e.g., it is difficult to make a call in a congested state), and the connection destination can be actually selected. ing. According to Patent Document 3, a terminal identification number for each connection source terminal that is a caller is registered in a customer computer. At the time of outgoing call, the customer computer that manages the connection source information including the caller name, address, and the person in charge, the airspace information, the address and the connection destination terminal information including the person in charge searches the customer information using the terminal identification number as a key. To determine the destination terminal. However, in the method described in Patent Document 3, in order to determine the terminal identification number of the connection source, the terminal connected to the communication network is transmitted by specifying the connection destination with a predetermined connection destination number. In this case, only the method of determining the incoming user is described, and the caller cannot be automatically determined in the first place.

In addition, the commercially available Predictive Dialing system uses a customer information file (call list) prepared in advance for outbound work (a work to send information from a certain system or network) to the agent that handles the average response rate and outbound. This is a dialing method in which a predictive (predictive) algorithm based on parameters such as average call time and follow-up operation time is used to calculate the agent's response probability, and the system automatically sends the call and connects to the agent only when the other party answers. However, the simple telephone number list used in the Predictive Dialing system does not include attribute information about people, and is insufficient to determine the caller / destination dynamically.
JP-A-2005-71052 JP-A-2005-250844 Japanese Patent No. 3239228

  The present invention has been made in view of the above-described background, and it is possible to dynamically determine an optimal outgoing / incoming user, that is, a connection destination in consideration of attributes (for example, details of equipment) for each user. Provided is a method and apparatus for determining a connection destination, and a program for making it possible to construct a general-purpose and highly reusable system configuration so that it can be used for various purposes (domains) without being limited to the above server management example The purpose is to do.

  In order to solve the above-described problem, the present invention provides connection destination information storage means for storing connection destination information configured to include attribute information related to a plurality of connection destinations including connection destination identification information, and determining a connection destination Event information storage means for storing event information that defines one or a plurality of attribute information as an opportunity for triggering, a relationship between the connection destination information and the attribute of the event information, and output contents of the connection destination information Definition information storage means for storing definition information for defining the event, and inputting input information indicating an event that triggers the determination of the connection destination, and the event information corresponding to the input information is stored in the event information storage An input process extracted from the means, a search process for searching the connection destination information, the definition information, and the event information extracted in the input process using a search expression including information corresponding to the input information, and the search Results of extent, characterized in that an output process for identifying and outputting a destination by referring to the definition information stored in the definition information storage means.

  In the present invention, the definition information includes a definition of a relationship between attributes of the connection destination information and the event information by an abstract logical relationship between the connection destination information and the event information. It is characterized by.

  In the invention, it is preferable that the search expression includes an element included in definition information that defines an output content of connection destination information stored in the definition information storage unit.

  The present invention also provides connection destination information storage means for storing connection destination information configured to include attribute information relating to a plurality of connection destinations including connection destination identification information, and an event that triggers the determination of the connection destination. Event information storage means for storing event information defined by one or more attribute information, and definition information for defining a relationship between the connection destination information and the attribute of the event information and defining output contents of the connection destination information A definition information storage means for storing; input information indicating an event that triggers the determination of a connection destination; and input means for extracting event information corresponding to the input information from the event information storage means; Using a search expression including information corresponding to the input information, a search means for searching the connection destination information, the definition information, and event information extracted by the input means, and a search result by the search means , Characterized by comprising an output means for specifying a destination by referring to the definition information stored in the definition information storage means.

In the present invention, the definition information includes a definition of a relationship between attributes of the connection destination information and the event information by an abstract logical relationship between the connection destination information and the event information. It is characterized by.
In the invention, it is preferable that the search expression includes an element included in definition information that defines an output content of connection destination information stored in the definition information storage unit.

  The present invention also provides connection destination information storage means for storing connection destination information configured to include attribute information relating to a plurality of connection destinations including connection destination identification information, and an event that triggers the determination of the connection destination. Event information storage means for storing event information defined by one or more attribute information, and definition information for defining a relationship between the connection destination information and the attribute of the event information and defining output contents of the connection destination information The computer of the connection destination determination device comprising the definition information storage means for storing inputs input information indicating an event that triggers the determination of the connection destination, and the event information corresponding to the input information is input to the event A search for searching the connection destination information, the definition information, and the event information extracted by the input means by using an input means extracted from the information storage means and a search expression including information corresponding to the input information. Means, from the search result by the searching means, a program for causing to function as output means for identifying and outputting a destination by referring to the definition information stored in the definition information storage means.

  According to the present invention, input information indicating an event that is a trigger for determining a connection destination is input, and from event information corresponding to the input information and attribute information about a plurality of connection destinations including connection destination identification information For the connection destination information and the definition information that defines the relationship between the attributes of the connection destination information and event information and the output contents of the connection destination information, use a search expression that includes information corresponding to the input information. The connection destination is identified by referring to the definition information from the search result, and the identification information of the identified connection destination is output in a predetermined format. Therefore, by using the present invention, it is possible to determine the caller / receiver in accordance with an event (domain or event) that triggers the determination of the connection destination. Further, the present invention can be applied to various uses (events; domains) including communication device management and English conversation lessons by exchanging event information (domain object), definition information (policy), and search expressions. A general-purpose and highly reusable calling / receiving user determination system can be realized.

  The best mode for carrying out the present invention will be described below with reference to the drawings. FIG. 1 illustrates a server (NWSPF client) 7, a SIP server 8, and a service component 9 in which a network service platform 1 maintains and monitors communication devices such as servers and routers via a network 10, a communication network 11, or an information network 12. It is a network block diagram at the time of cooperation.

  The network service platform 1 is a base in a system that executes services by linking element services (service components) constituting services distributed on a network, and includes one or a plurality of terminals such as servers, It consists of communication means such as communication networks and communication lines for connecting terminals, and various services are realized by executing predetermined programs on the terminals. The SIP server 8 is a server that cooperates with the communication network control server device 6 in the network service platform 1 and performs call control of the IP phone by SIP or the like. Controls connections for various communications such as videophone communications. The service component 9 is a service whose interface is defined, and is referred to and called sequentially or in parallel by the service composition unit 3 in the network service platform 1 based on the cooperation scenario.

  In the present embodiment, it is assumed that the network 10 includes a communication device group 13, and the communication device group 13 includes, for example, a router 14 and a server 15. The maintenance monitoring server (NWSPF client) 7 is a server that monitors and monitors the communication device group 13, and is a client that accesses the network service platform 1 in this embodiment. In FIG. 1, each configuration is shown one by one, but a plurality of configurations can be provided. Further, it is assumed that a plurality of terminals serving as SIP UAs (not shown) are connected to a network such as the communication network 11.

  In FIG. 1, it is appropriate that the network 10, the communication network 11, and the information network 12 are assumed to be arbitrary networks, communication carrier networks, and IP (Internet Protocol) data networks such as the Internet. Absent.

  In addition, the calling / called party determination system 2 in the network service platform 1 is a main configuration characterized by the present invention. In this embodiment, when a predetermined event (for example, a failure in the communication device group 13 or a failure occurs) occurs in a client such as the maintenance monitoring server 7, the calling / calling party determination system 2 serves as a connection destination corresponding to this event. This is a system that dynamically determines an optimum outgoing / incoming user in consideration of attributes for each user (connection destination). In FIG. 1, the calling / receiving party determination system 2 is arranged inside the network service platform 1, but may be arranged outside the network service platform 1.

  In the configuration example shown in FIG. 1, a service synthesizing unit 3, a service component database 4, a service scenario database 5, and a communication network control server device 6 are provided in the network service platform 1, in addition to the calling / receiving party determination system 2. The service composition unit 3 functions as a scenario execution engine, and is connected to the maintenance monitoring server 7, the SIP server 8, and the service component 9 directly or via the communication network control server device 6. The service composition unit 3, the caller determination system 2, the service component database 4, and the service scenario database 5 are connected by predetermined communication means.

  The service scenario database 5 stores one or a plurality of scenarios 21 as shown in FIG. Each scenario 21 describes the calling order of service components executed by the service composition unit 3. That is, as shown in FIG. 2, each scenario 21 includes a service component calling instruction 22, a calling / determining number determination calling instruction 23, a makeCall (calling) instruction 24, and the like. Here, the service component call command 22 is a command for calling the service component 9 of FIG. The calling / called number determination call command 23 is a command for calling the calling / called party determination system 2. The makeCall command 24 is a command for instructing the communication network control server device 6 to perform call connection or the like.

  Further, the service component database 4 in FIG. 1 includes a correspondence between the service component call command 22 and the service component 9 in the service scenario database 5, a correspondence between the calling / calling number determination calling command 23 and the calling / calling party determination system 2, and a make Ca11 command. 24, correspondence information between the communication network control server device 6 and the communication network control server device 6 is stored.

  In the network service platform 1 of FIG. 1, a scenario 21 itself as shown in FIG. 2 is called from the maintenance monitoring server (client) 7 and a thread is started. Then, the service composition unit 3 first interprets the service component call instruction 22 and executes the service component 9. Next, the service synthesizing unit 3 interprets the calling / called number determination call command 23 and executes predetermined processing in the calling / called party determination system 2. Then, the service composition unit 3 interprets the makeCall command 24 and executes predetermined processing in the communication network control server device 6.

  FIG. 3 shows a system configuration of the calling / called party determination system 2 in the present invention shown in FIG. The calling / calling party determination system 2 is configured as a server or the like, and is realized by a combination of a computer in the server and its peripheral devices and a program executed by the computer. The calling / calling party determination system 2 includes a storage device 50 that stores information on the repository 51, the domain object 52, the policy 53, and the query search expression 54, an input processing unit 61 that inputs information from the service composition unit 3 in FIG. A search execution unit 62 that performs a search process using each information in the storage device 50, and a search that extracts output information (information indicating a connection destination) in a predetermined format from the search result and outputs it to the service composition unit 3 And a result extraction / output unit 63.

  The repository 51 functions as a connection destination information storage unit that stores connection destination information including attribute information about a plurality of connection destinations including identification information of connection destinations such as SIP URIs, and is a subscriber information database. The attributes (α, β, etc. in FIG. 3) of one or a plurality of users (connection destinations) are defined. As a user attribute description format, RDF (Resource Description Framework) can be used. That is, as shown in FIG. 4, the user variable (connection destination information) representing each user has a name attribute (name attribute) representing the name of the user, an administrativeLocation attribute (management authority attribute) representing the management authority of the user, and SIP. The sipuri attribute (SIP URI attribute) indicating the identification information of the sender and destination, the rdf: type property in RDF, etc. are defined. The definition word rdf: type is a property indicating which class member (instance) the resource (in this case, a user variable) is. For example, the repository 51 describes “5thfloor” (5th floor) as the value of the administrativeLocation attribute of the user “Alice” (= name attribute), “sip: alice@company.com” as the sipuri attribute, and the user “Alice” (= name attribute). “Bob” belongs to the NetworkSpecialist class (network specialist class) (described using rdf: type), and “sip: bob@company.com” is described as its sipuri attribute. As the identification information of the caller and callee, in addition to the SIP URI, a telephone number, an e-mail address, an IP address of a predetermined terminal, or the like can be used.

  The domain object 52 functions as an event information storage unit that stores event information that defines an event that triggers the determination of a connection destination with one or more attribute information, and is used to determine a call destination. Define objects (events) that will be used as judgment materials. RDF can be used as a description format of the definition. In the present embodiment, it is assumed that a communication device failure is an event that triggers the determination of a domain (domain or domain), that is, a connection destination. In this case, as shown in FIG. 4, the domain object 52 describes information (object information) such as attributes related to the communication device that is the target (target event), that is, the router 14 and the server 15. Here, the class of the router 14 is “Router”, “router14” is the value of the ID (identification code) attribute that is information for identifying the individual, and “vendor” (the attribute of the product sales company) is “ ntt ”and“ 5thfloor ”are described as the value of the location attribute (location attribute). Further, as the information of the server 15, in addition to the class “Server”, the values “server15”, “A-Company”, and “7thfloor” of each attribute are also described in the same manner.

  The policy 53 functions as a definition information storage unit that defines the relationship between the attributes of the connection destination information and the event information and stores the definition information that defines the output contents of the connection destination information. A conditional expression to be satisfied by the relationship between the attributes and a conditional expression indicating the output contents of the connection destination information from the calling / receiving party determination system 2 are defined. If necessary, vocabulary (ontology) can be described at the same time. The description format of the conditional expression definition is SWRL (I. Horrocks et al., “SWRL: A Semantic Web Rule Language Combining OWL and RuleML,” W3C Document, 2004. 5., http://www.w3.org/ Submission / SWRL /) can be used, and OWL (Web Ontology Language, http://www.w3.org/TR/owl-features/) can be used as the vocabulary. Further, in the present embodiment, the definition information stored in the policy 53 includes a conditional expression that defines the relationship between the attributes of the connection destination information and the event information by the logical relationship between the connection destination information and the event information abstract type (class). include. In this embodiment, a conditional expression (policy) is, for example,

Write like this. Formula (1) defines the relationship between the attributes of the connection destination information and event information, and the intersection of the network specialist class (NetworkSpecialist) and the router class (Router) includes the maintainable class (Maintainable) It shows that Equation (2) is
Indicates the output contents of the connection destination information from the caller / determinant determination system 2, and indicates that the connection destination class (callParticipants) includes the union of the sender class (Sender) and the receiver class (Receiver). Yes.

  The search formula 54 is a query search formula for the repository 51, the domain object 52, and the policy 53. A query search expression is a query processing request for a database that manages each information to be searched, including a character string such as a logical operator that represents a relationship between keywords. In addition, the search formula 54 of the present embodiment includes information corresponding to information input to the caller / determinant determination system 2 as representing an event that triggers the determination of the connection destination. SPARQL (SPARQL Protocol and RDF Query Language) can be used for the query search expression. In the present embodiment, as a query search expression, for example,

  and

と記述する。（３）式を図示したグラフを図６に示す。

Is described. FIG. 6 shows a graph illustrating the expression (3).

  In other words, the expression (3) indicates that the variable sender described after “SELECT” (“?” Is a code representing the variable) is selected according to the condition indicated by the character string below “WHERE”. is there. Further, in the expression (3), the information “rouetr14” of the router 14 corresponding to information representing an event that triggers the determination of the connection destination is included in the description below “WHERE”. Specifically, the expression (3) means that a user having administrative authority at the location of the router 14 is selected as a sender. Further, the expression (4) means that a user who can maintain the router 14 is selected as a receiver.

  The procedure in the present embodiment will be described below based on the scenario 21 shown in FIG. 2, the system diagram of FIG. 3, and the sequence shown in FIG. The maintenance monitoring server (NWSPF client) 7 constantly monitors the status of the communication devices (communication devices) belonging to the communication device group 13, and when detecting that an abnormality has occurred in the router 14, SOAP (Simple Object Access Protocol) Is used to access the service composition unit 3 to execute the scenario 21. This SOAP message includes “<id> router14 </ id>” indicating the ID of the failed router 14, that is, information for identifying an individual communication device, which is information indicating an event that triggers determination of a connection destination. XML (Extensible Markup Language) tags.

  The service composition unit 3 executes the service component 9 according to the scenario 21. The service component 9 may be an arbitrary service. For example, if the service component 9 is a map service, “<id> router14 </ id>” is received as an input, and the position of the router 14 identified by the ID “router14” on the map is, for example, a maintenance monitoring server (NWSPF client). ) Display on the screen of 7.

  Next, the service synthesizing unit 3 executes the calling / receiving party determination system 2 according to the scenario 21. At this time, “<id> router14 </ id>” is passed as a parameter to the calling / receiving party determination system 2 (the above corresponds to S101 in FIG. 7).

  Upon receiving “<id> router14 </ id>” as an input, the calling / calling party determination system 2 receives an object instance corresponding to “<id> router14 <1id>” from the domain object 52 in the input processing unit 61. Are retrieved and extracted by XQuery (a query language for XML databases standardized by W3C). That is, the input processing unit 61 inputs input information (in this case, “<id> router14 </ id>”) indicating an event that triggers the determination of the connection destination, and event information corresponding to the input information. Functions as an input means for extracting from the domain object 52 (event information storage means). in this case. The input processing unit 61 inputs the instance router 14 of the inspection target object, and creates an object of the class Router of the instance router 14. The XQuery expression is as follows:

  In this way, an object instance related to the router 14 (in this case, “ntt”, “router14”, “5thfloor”) is obtained (the above corresponds to S201 in FIGS. 3 and 7).

  Next, the search execution unit 62 uses the query search formula 54 to connect the connection destination information (stored information in the repository 51), definition information (stored information in the policy 53), and event information (objects) extracted by the input processing unit 61. ) Function as a search means for searching. In this case, the search execution unit 62 performs the following search process in order to obtain the connection destination variable callParticipants that is the output of the calling / calling party determination system 2. The query search expressions (3) and (4) described above do not include the variable callParticipants. Therefore, inference must be performed and callParticipants must be replaced with variables appearing in equations (3) and (4). In this inference, the search execution unit 62 refers to the policy (2) defined in the policy 53, and the callParticipants are composed of a union of Sender and Receiver, so that the query search is performed for Sender and Receiver, respectively. Judging. Then, it is confirmed that Sender and Receiver appear as variables in the expressions (3) and (4), and the search expression (for the repository 51, the policy 53, and the object instance related to the router 14 previously extracted by Xquery Perform SPARQL search by 3) and (4). (3) As a result of SPARQL search of expression

Is obtained. That is, “Alice” having the administrative authority at the location of the router 14 is selected as the sender sender.

  Similarly, the policy (1) is applied to the SPARQL search of (4), and the search result is

Is obtained. That is, the user “Bob” who can maintain the router 14 is selected as the receiver (S202).

  Next, the search result extraction / output unit 63 refers to the definition information stored in the policy 53 (definition information storage unit) from the search result by the search execution unit 62 and outputs the output by specifying the connection destination. It functions as. In this case, the search result extraction / output unit 63 determines the variable callParticipants as follows by extracting the user set that matches the policy 53 from the search execution results (5) and (6). The search result extraction / output unit 63 is called immediately before the makeCall command 24 (that is, 3PCC API execution) in the scenario 21, and functions as a unit that determines a calling / receiving user and outputs its SIP URI.

  Expressions (5) and (6) of the query search result by the search execution unit 62 do not include the value of the variable callParticipants. Therefore, the search result extraction / output unit 63 must make an inference and replace callParticipants with variables appearing in the equations (5) and (6). Therefore, the search result extraction / output unit 63 refers to the policy (2), and callParticipants are composed of the union of Sender and Receiver. Therefore, the values of Sender and Receiver are specified from (5) and (6), and each SIP Extract the URI. For Sender, the following Xquery expression:

Thus, the SIP URI “<sipuri> sip: alice@company.com </ sipuri>” of “Alice” is obtained. Similarly, for Receiver, the following Xquery expression:

Thus, the SIP URI “<sipuri> sip: bob@company.com (</ sipuri>” ”of“ Bob ”is obtained (S203).

  The search result extraction / output unit 63 follows the SIP URI according to the array format, that is, “<xs: element name =“ Output ”type =“ xsd: any URI ”maxOccurs =“ unbounded ”/>”.

Is output (S204).

  Next, according to the scenario 21, the service synthesizing unit 3 inputs the result output from the search result extracting / outputting unit 63 of the calling / determining party determination system 2 into the makeCall command 24, thereby communicating the values of the two SIP URIs. The message is transferred to the network control server device 6 as a 3PCC API message parameter. The communication network control server device 6 provides a function corresponding to the API of Parlay X (Web Service Specification, http://wwwparlay.org/), and receives two or more SIP URIs as input. The SIP server 8 is controlled to make a call connection between these SIP URIs. In other words, the communication network control server device 6 makes a call connection between “sip: alice@cempany.com” and “sip: bob@cornpany.com” (S102).

  In the procedure of the above embodiment, the calling / calling party determination system 2 determines the calling / calling party. However, the calling / receiving party determination system 2 can search not only two SIP URIs as described above but also three or more SIP URIs. Such a case occurs when information of three or more users is stored in the repository, and the SPARQL search result of the expressions (3) and (4) includes a plurality of users.

  Further, in the above embodiment, the failure communication device (failure monitoring device) is written in the domain object 52, and the caller search / determination condition is written in the SPARQL search formula 54 and the policy 53, so that an administrator / person in charge who is familiar with the failed device can be obtained. Although it applied to the service to extract, it can also be easily applied to another service by replacing these. For example, the English conversation lesson menu and the English conversation instructor according to the student's ability are determined by recording the English conversation lesson menu in the domain object 52 and the conditions for searching and determining the English lecturer and the student in the SPARQL search formula 54 and the policy 53. It can also be applied to such services.

  By using the present invention, callers can be determined according to the domain. Since the present invention can be applied to various uses (domains) such as the above communication device management and English conversation lessons by exchanging domain objects, policies, and search expressions, it is possible to make general-purpose and highly reusable user determination The system becomes feasible.

  Note that the embodiment of the present invention is not limited to the above, and each component and each information (data file) are integrated, divided, or further distributed and arranged between them with a communication means. It is possible to appropriately change the connection. In the present embodiment, part or all of the configuration can be configured by using a computer and a program executed by the computer, and part or all of the program can be read by a computer-readable recording medium or communication means. It is possible to distribute via

The network block diagram in the best embodiment for implementing this invention. The figure which shows the example of a cooperation scenario in embodiment of FIG. FIG. 2 is a system configuration diagram of the calling / calling party determination system 2 of FIG. 1. The figure for demonstrating the description content of the repository 51 of FIG. The figure for demonstrating the description content of the domain object 52 of FIG. The figure for demonstrating the description content of the query search expression 54 of FIG. The flowchart in embodiment of FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Network service platform 2 Calling / calling party decision system 3 Service composition part 4 Service component database 5 Service scenario database 6 Communication network control server device 7 Maintenance monitoring server (NWSPF client)
8 SIP Server 9 Service Component 10 Network 11 Communication Network 12 Information Network 13 Communication Device Group 14 Router 15 Server 21 Scenario 22-24 Instruction in Scenario 50 Storage Device 51 Repository 52 Domain Object 53 Policy 54 Query Search Formula 61 Input Processing Unit 62 Search Execution unit 63 Search result extraction / output unit S101-204 Processing step number

Claims (7)

Connection destination information storage means for storing connection destination information including attribute information regarding a plurality of connection destinations including identification information of the connection destination;
Event information storage means for storing event information that defines one or more attribute information as an opportunity for determining a connection destination;
A definition information storage means for defining a relationship between the attributes of the connection destination information and the event information and storing definition information for defining output contents of the connection destination information;
While inputting input information indicating an event that triggers the determination of the connection destination, an input process of extracting event information corresponding to the input information from the event information storage means,
A search process for searching the connection destination information, the definition information, and the event information extracted in the input process, using a search formula including information corresponding to the input information,
A connection destination determination method comprising: an output step of identifying and outputting a connection destination by referring to definition information stored in the definition information storage means from a search result of the search process. The definition information includes information defining a relationship between attributes of the connection destination information and the event information by an abstract logical relationship between the connection destination information and the event information. Item 2. The connection destination determination method according to Item 1. The connection destination according to claim 1, wherein the search expression includes an element included in definition information that defines an output content of connection destination information stored in the definition information storage unit. Decision method. Connection destination information storage means for storing connection destination information including attribute information regarding a plurality of connection destinations including identification information of the connection destination;
Event information storage means for storing event information that defines one or more attribute information as an opportunity for determining a connection destination;
Definition information storage means for storing definition information defining the output contents of the connection destination information as well as defining the relationship between the attributes of the connection destination information and the event information;
An input unit that inputs input information indicating an event that triggers the determination of a connection destination, and that extracts event information corresponding to the input information from the event information storage unit;
Search means for searching the event information extracted by the connection destination information, the definition information, and the input means using a search formula including information corresponding to the input information;
An output means for specifying and outputting a connection destination by referring to definition information stored in the definition information storage means from a search result obtained by the search means; The definition information includes information defining a relationship between attributes of the connection destination information and the event information by an abstract logical relationship between the connection destination information and the event information. Item 5. The connection destination determination device according to Item 4. The connection destination according to claim 4 or 5, wherein the search formula includes an element included in definition information that defines an output content of connection destination information stored in the definition information storage unit. Decision device. Connection destination information storage means for storing connection destination information including attribute information regarding a plurality of connection destinations including identification information of the connection destination;
Event information storage means for storing event information that defines one or more attribute information as an opportunity for determining a connection destination;
Definition information storage means for storing definition information defining the output contents of the connection destination information as well as defining the relationship between the attributes of the connection destination information and the event information;
A computer of a connection destination determination device comprising:
An input unit that inputs input information indicating an event that triggers the determination of a connection destination, and that extracts event information corresponding to the input information from the event information storage unit,
Search means for searching the event information extracted by the connection destination information, the definition information, and the input means, using a search formula including information corresponding to the input information,
A program that functions as an output unit that specifies and outputs a connection destination by referring to definition information stored in the definition information storage unit from a search result by the search unit.

Images