Entity Types and Message Structures Clause Samples

Entity Types and Message Structures. The COCOP system consists of entities (also called components or modules). The entities have various types as given in the following table. Each entity type is explained in the coming subsections. The entities and their associated APIs and message structures will be detailed during the project and described in the future deliverable D3.7
View Source
Entity Types and Message Structures. 9 2.6 Information Security 11 2.7 Robust Module Design 12 3 Conclusion 13 References 14 1 A r c h i te ct ur a l Re q u i re m e n t s a nd C or e A s pe c t s
View Source

Related to Entity Types and Message Structures

  • TEXT MESSAGING WHILE DRIVING In accordance with Executive Order (EO) 13513, “Federal Leadership on Reducing Text Messaging While Driving,” any and all text messaging by Federal employees is banned: a) while driving a Government owned vehicle (GOV) or driving a privately owned vehicle (POV) while on official Government business; or b) using any electronic equipment supplied by the Government when driving any vehicle at any time. All cooperators, their employees, volunteers, and contractors are encouraged to adopt and enforce policies that ban text messaging when driving company owned, leased or rented vehicles, POVs or GOVs when driving while on official Government business or when performing any work for or on behalf of the Government.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,

  • Reducing Text Messaging While Driving Pursuant to Executive Order 13513, 74 FR 51225 (Oct. 6, 2009), Recipient should encourage its employees, subrecipients, and contractors to adopt and enforce policies that ban text messaging while driving, and Recipient should establish workplace safety policies to decrease accidents caused by distracted drivers.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Alerts via Text Message To stop Alerts via text message, text "STOP" to 99785 at anytime. Alerts sent to your primary email address will be unaffected by this action. To restore Alerts on your Mobile Device, just visit the Alerts tab in Online Banking and click the box next to your mobile number for the Alert(s) you would like to receive again. For help with SMS text alerts, text “HELP” to 99785. In case of questions, please contact Customer Care at ▇-▇▇▇-▇▇▇-▇▇▇▇. Our participating carriers include (but are not limited to) AT&T® Wireless, T-Mobile®, U.S. Cellular®, Verizon Wireless.