Agent features Sample Clauses

Agent features. The DP features Intermediate routing DP and Messaging metadata DP are implemented through a service agent as shown in Table 1. Thus, we define them as optional child features of the feature Service agent DP in FMSP . In contrast of SOAP and REST, the SC request messages which are dedicated to MOM do not explicitly contain information about the capability and service that the SC wants to invoke. As a consequence, it would be not possible to invoke the required capability and service. As a solution, we propose, to implement the feature Intermediate routing DP which exploits the metadata (Messaging metadata DP) presented in the SC request messages to dynamically routing these messages to the required capability and service. To support this dynamic routing, we define, in our FMSP , “requires” constraints from the feature MOM to the features Intermediate routing DP and Messaging metadata DP. From our study on SOA DPs [2], we notice that the four features Service callback DP, Event-driven messaging DP, Atomic service transaction DP and Reliable messaging DP require the feature Messaging metadata DP. This requirement is already considered in our FMSP because (1) we have already defined these four features as optional children to the feature MOM and we have already defined a “requires” constraint from the feature MOM to the feature Mes- saging metadata DP.
Sample 1
AutoNDA by SimpleDocs

Related to Agent features

  • Standard Service Features Ethernet Access allows Customer to terminate single and/or multiple Ethernet Virtual Circuits (EVCs) from Customer equipment onto a single Ethernet Access UNI.

  • SYSTEM AGENCY DATA A. As between the Parties, all data and information acquired, accessed, or made available to Grantee by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Grantee in the course of providing data processing services in connection with Xxxxxxx’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • Local Number Portability Database 10.6.1 The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. BellSouth agrees to provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.

  • Operating Procedures The Service Provider intends to clear trades for Fund Shares through, and make use of, the National Securities Clearing Corporation’s (“NSCC’s”) Fund/Serv and, in connection therewith, agrees to follow and comply with the procedures, terms and conditions set forth in the operating procedures set forth in Exhibit A hereto, as supplemented or amended from time to time by the mutual agreement of the parties hereto (the “Operating Procedures”).

  • DISTRIBUTION AND DEFAULT SERVICE TERMS AND CONDITIONS Capacity Pipeline Capacity, Underground Storage Withdrawal Capacity, Underground Storage Capacity and Peaking Capacity as defined in these Terms and Conditions. Capacity Allocators The proportion of the Customer’s Total Capacity Quantity that comprises Pipeline Capacity, Underground Storage Withdrawal Capacity and Peaking Capacity. City Gate The interconnection between a Delivering Pipeline and the Company’s distribution facilities. Company Eversource Gas Company of Massachusetts d/b/a Eversource Energy Company Gas Allowance The difference between the sum of all amounts of Gas received into the Company’s distribution system and the sum of all amounts of Gas delivered from the Company’s distribution system as calculated by the Company for the most recent twelve (12) month period ending July 31. Such difference shall include, but not be limited to, Gas consumed by the Company for its own purposes, line losses and Gas vented and lost as a result of an event of Force Majeure, excluding gas otherwise accounted for. Company-Managed Supplies Capacity contracts held and managed by the Company in accordance with governing tariffs, but made available to the Supplier pursuant to Section 13.9 of these Terms and Conditions, including supply-sharing contracts and load- management contracts. Consumption Algorithm A mathematical formula used to estimate a Customer’s daily consumption. Critical Day In accordance with Section 19.0 of these Terms and Conditions, a Day declared at any time by the Company in its reasonable discretion when unusual operating conditions may jeopardize operation of the Company’s distribution system.

  • Description of Goods or Services and Additional Terms and Conditions The Contractor shall perform as set forth in Exhibit A. For purposes of this Contract, to perform and the performance in Exhibit A is referred to as “Perform” and the “Performance.”

  • TELEPHONE BANKING SERVICE TERMS AND CONDITIONS Before using any Telephone Banking Service, please read the terms and conditions set out below, which govern your use of such service. By using your TBS Access Code to operate the Telephone Banking Service, you are accepting the terms and conditions set out below and will be bound by them.

  • Rights Protection Mechanisms and Abuse Mitigation ­‐ Registry Operator commits to implementing and performing the following protections for the TLD:

Time is Money Join Law Insider Premium to draft better contracts faster.