Network Architecture Clause Samples
POPULAR SAMPLE Copied 1 times
Network Architecture. 2.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result.
2.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a 24-hour contact number for network traffic management issues to the other's surveillance management center.
2.3 Each Party maintains the right to implement protective network traffic management controls, such as "cancel to", "call gapping" or 7-digit and 10- digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed.
2.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Such alternative routing shall be used only when mutually agreed to by the Parties. The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events.
2.5 The Parties agree that, unless otherwise mutually negotiated, the quality of such network connections shall be equal to that of the existing facilities that are jointly provided by each Party.
Network Architecture. Schedule 3.18 of the Seller Disclosure Schedule sets forth a true and complete statement (detailed by Cable System) as of December 31, 2004 (or, in the case of clauses (c) and (f), as of the date hereof), of (a) the approximate number of plant miles (aerial and underground) for each headend located in each Specified Business, (b) the approximate bandwidth capability expressed in MHz of each such headend, (c) the stations and signals carried by each such headend and the channel position of each such signal and station, (d) the approximate number of multiple dwelling units served by such Specified Business, (e) the approximate number of homes passed in such Specified Business as reflected in the system records of Seller or any of its Affiliates, (f) a description of basic and optional or tier services available and the rates charged for each such Specified Business, (g) the bandwidth capacity of each Cable System in such Specified Business for each headend, and (h) the municipalities served by each of the Cable Systems in such Specified Business and the public service numbers of such municipalities.
Network Architecture. Schedule 4.20 of the Buyer Disclosure Schedule sets forth in all material respects a true and complete statement as of December 31, 2004, of (a) the approximate number of plant miles (aerial and underground) for each division of the Parent Business, (b) the approximate bandwidth capability expressed in MHz of each such division of the Parent Business, (c) the stations and signals carried by each such division and the channel position of each such signal and station of the Parent Business, (d) the approximate number of bulk accounts served by the Parent Cable Systems, (e) the approximate number of homes passed in the Parent Business as reflected in the system records of Parent or any of its Affiliates, (f) a description of basic and optional or tier services available from each such division of the Parent Business and the rates charged for each, (g) the channel capacity of each such division of the Parent Business, and (h) the municipalities served by each such division of the Parent Business and the community unit numbers of such municipalities.
Network Architecture. 6.1.1. The Contractor Platform shall be protected behind a layer of firewalls.
6.1.2. At County’s request, Contractor shall submit a network architecture diagram of County’s stored and transmitted data, including the location of the data center and details of connectivity for all third parties who have access to County Data. Any network security changes implemented by Contractor must not compromise the security of County Data. Contractor shall ensure that all database servers are protected behind a second set of internal firewalls.
6.1.3. Contractor shall restrict inbound and outbound traffic to County’s network to “deny all, permit by exception” configuration.
6.1.4. Contractor’s wireless networks connected to the Contractor Platform shall at a minimum, be configured for Wi-Fi Protected Access 2 (WPA2)-Enterprise using Advanced Encryption Standard (AES) and Protected Extensible Authentication Protocol (PEAP), or current industry security standards (whichever is higher) to secure and protect County data.
Network Architecture. You understand and agree that the Services and fees described in a SOW are based upon the architecture of your network and the System as described in an applicable SOW. In the event that your network or the System is subsequently modified in any manner, FWC reserves the right to change the scope of services and/or the fees charged to you under an applicable SOW. You agree to notify FWC prior to (i) installing any software to, or modifying any hardware of, the System, or (ii) moving the System, in part or in whole, to any location other than the locations at which FWC installed the components comprising the System. Your failure to notify FWC as described in this paragraph may result in you incurring additional costs, on a time and materials basis, to restore the System or to bring the System back to a functioning condition.
Network Architecture. On-Net sites are customer access points for microwave links that transmit traffic to and from Hubs. Hub and On-Net sites communicate via multiple DS3/DS1 radio links in the 38 Ghz portion of the spectrum. The Hubs function as concentrators for these microwave links, providing DS3 or DS1 service for buildings within the Hub service area. In some instances , the traffic from these buildings will be bundled into multiple DS3 links over a fiber SONET Ring backbone, or connected by low frequency radio shots. This fiber backbone will initially be provided by a competitive access provider (CAP). In simple terms, the network architecture features On-Net sites as customer access points for traffic, with Hubs transmitting and receiving traffic from On-Net sites via microwave links. Hubs concentrate that traffic from On-Nets and transmit (or receive) traffic over fiber links to any one of the following:
Network Architecture. (i) Hubs and Lit Buildings communicate via multiple DS3/DS1 radio links in the 38-40 Ghz portion of the spectrum. The Hubs function as concentrators for these milliwave links, providing DS3 or DS1 service for Lit Buildings within the Hub service area. The traffic from the Lit Buildings will be bundled into multiple DS3 links over a fiber SONET ring backbone, or connected by lower frequency radio shots (i.e., 18 and 23 Ghz currently and 6 and 11 Ghz in the future).
(ii) The network architecture features Lit Buildings as customer access points for traffic, with Hubs transmitting and receiving traffic from Lit Buildings via milliwave links. Hubs concentrate, transmit and receive that traffic over fiber links to central office switch sites, other Hubs and points of collocation (each a point of presence).
Network Architecture. Network diagrams need to be conformed to the agreed upon Clearwire - BCE Nexxia architectures. The consumer VoIP application is based on the Nortel MCS 5200/CS2K platform. There are two types of sites deployed - a "main site" and a "POP". Main sites (location to be confirmed by BCE Nexxia) have the MCS/CS2K server complex, several PSTN gateways, multimedia servers to support offerings such as voicemail and conferencing as well as voice adapter provisioning servers. Main sites are fully redundant from a network perspective and BCE Nexxia would work to enable fail-over functionality between the Main Sites (with delivery timeframe updates to CW). POP sites provide local "dial tone" for incoming and outgoing calls in various areas through the means of PSTN gateways. For POP sites, redundancy is only deployed for outgoing calls. (i.e., in the event of a main site failure it would still be possible to place calls from the area served by a given POP (by using PSTN failover i.e. calls would be "backhauled" to our Toronto or Montreal main sites and routed through our network) but incoming calls to primary or secondary phone numbers in that site would not be possible.) The Internet is used to interconnect to the main sites. Such sites must be protected with a firewall. The current plan anticipates that the VoIP service may share a firewall with other services delivered through the Clearwire POP.)
Network Architecture. The network architecture is mainly composed of: the patient side and the caregiver side (see Figure 1). The most appropriate e-health scenario is the case of a patient who has one or more critical illnesses, such as health-related data are collected from sensors and transmitted to the caregiver. The latter sends the right medical prescriptions to the patient.
1 Mobile and contextual sensor nodes: the sensors are planted in, on, or around a patient body to collect health-related data (e.g., electrocardiogram sensor, blood glucose level, body temperature level, etc.).
Network Architecture. Yes CenturyLink is a facilities-based network services provider. The network is on CenturyLink built and owned fiber network. All POP locations are housed in environmentally secure, physically secure, security card-access mandated facilities. We own and operate our own network and do not purchase transit in lieu of peering. CenturyLink MPLS VPN Infrastructure The MPLS VPN product rides on the CenturyLink IP backbone. The backbone is composed of Juniper routers deployed in TeraPOPs across the U.S. and parts of Europe and Asia. Each TeraPOP has at least two connections, typically at OC-192 speed, connected to TeraPOPs in at least two different cities for redundancy. IP backbone connections use Packet over SONET interfaces. Provider Edge (PE) routers are deployed singly in smaller sites or in redundant clusters. OC-48 or OC-12 uplinks are used, with each PE having two uplinks. Backbone routers Juniper MX960 Juniper M320 Juniper T640 PE routers (Private Edge) Juniper M40 Cisco 7613 The CenturyLink IP/MPLS backbone uses a fully redundant architecture with primary and backup transport circuits. Every core