Functional Scalability Sample Clauses

Functional Scalability. The software must be designed from the beginning to allow further improvements in the future. For example, in the text analysis area, the supported languages will be English, German, French and Spanish. The software must be designed in a way that it should be easy to add support for more languages. The same principle applies to the input sources (it must be opened to new ones such as new social networks).
Sample 1Sample 2
AutoNDA by SimpleDocs
Functional Scalability. HSvEPC is formed with virtual network functions which means that they can be scaled in or out depend on the situation. With scalability, it can be applied to any network functions such as Massive IoT or Mission-critical IoT which requires small amount of resource from hardware but specific functionality. For example, we can have an IoT device that requires single core to run, and then we can scale VNF to meet the requirement of that specific IoT device instead of spending whole EPC hardware such as using non-ip address device. Main functionality and features of HSvEPC for functional scalability are as follows:  OpenStack and NFV based EPC function and separation of Control Plane and Data Plane  Dynamic core network resources management and control management  Designed from standard to apply any 3rd party platform  NFV based scalable and dynamic network condition projection HSvEPC is mainly formed with vMME, vSGW-CU, vPGW-CU, vSGW-DU, and vPGW-DU. CU is control plane which controls device management and DU is user plane which controls data transfer between devices. The main reason why we separated functions by each plane is to have scalability by situation. Since our vEPC is divided into CU and DU functions, they function as VNF, therefore they can be modified and have micro-control on each function. Node Description vMME Manage mobility of UE and process authentication. vSGW-CU vSGW-CU creates a session with vMME and GTP-C, then send it to vSGW-DU with using SDP. vSGW-DU vSGW-DU connects with vSGW-CU to get session information, then communicate UE traffic between eNB and PGW-DU with GTP-U. vPGW-CU vPGW-CU creates session with vSGW-CU and GTP-C, send related session information to vPGW-DU with using SDP, and apply QoS from PCRF. vPGW-DU vPGW-DU gets session information from vPGW-CU, communicate UE traffic between SGW-DU by GTP-U, and communicate traffic between PDN by SGi interface.
Sample 1

Related to Functional Scalability

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Year 2000 Compatibility Take all action necessary to assure that its computer based systems are able to operate and effectively process data including dates on and after January 1, 2000, and, at the reasonable request of the Administrative Agent or the Required Lenders, provide evidence to the Lenders of such year 2000 compatibility.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!