Management Information Model Sample Clauses

Management Information Model. The Edge node is a device that can be managed via a managment interface. There are a number of attributes that are required to be managed in order to allow the edge node to support an end to end VoIP service. This section defines a management information model which will used as the framework for defining all the objects and attributes that are required to be managed in the edge node. The management information model is described using the Unified Modeling Language (UML) syntax. The management information model is management protocol agnostic, since the exact management protocol to be used for managing the AG is outside the scope of this IA. Edge Node 1 N Interface 1 N Static Gate Each edge node has one or more interfaces which themselves may have one or more static gates. A static gate provides equivalent functionality to a dynamically allocated gate (i.e. one created by H.248) but is defined by management and is always available at the edge node until explicitly deleted by management. A static gate would typically be used to provide classification, packet marking and forwarding rules for signaling (such as SIP) that is received at the edge node. Static gates may provide NAT and PAT functions for signaling, may provide traffic descriptors that limit the maximum amount of signaling traffic that can be sent through a gate and may provide access control type functions to prevent barred customers from gaining access to the network. The following tables provide a textural description of all the classes contained in the management information model and the attributes associated with each of the classes. Edge-Node – This class represents the edge node entity.
Sample 1
AutoNDA by SimpleDocs
Management Information Model. Because a Media Server is unaware of particular applications or services in the network, it is in general a plug and play component, with little initial network configuration or ongoing service provisioning required. Initial network configuration includes IP addresses, netmasks, gateway addresses, host names, etc. Since this information is set once and then left alone, it makes sense to use the Media Server's built-in management interface to do this configuration, and there is little urgency to support configuration of this set of data from an external EMS or OSS. Since Media Servers do not have configuration data for services, customer groups, and subscribers, service provisioning for a Media Server is composed only of media-related data such as audio and video files for playback (also known as announcements). Additionally, storing these media files inside the Media Server is optional as they can be placed on an external file server and retrieved by the Media Server as required. In general, files that change infrequently can be stored internal storage, while those that change frequently should be stored externally. File downloaded to the Media Server are persistent, i.e., remain there through power failures and restarts, until explicitly replaced or deleted by management action. At the simplest level of abstraction a Media Server has an internal directory structure for media files. The Media Server supports an automated management interface for downloading and deleting media files in internal storage. The download command takes as parameters an external, source URL and an internal, destination URL. The delete command takes as parameter an internal URL.
Sample 1
Management Information Model. The AG is a device that is managed through the QAG interface and there are a number of attributes that are required to managed in the AG in order to provide a end to end VoIP service. User Port
Sample 1
Management Information Model. The Management Information Model will be specified in the individual SIP IAs.
Sample 1

Related to Management Information Model

  • Management Information To be Supplied to CCS no later than the 7th of each month without fail. Report are to be submitted via MISO CCS Review 100% Failure to submit will fall in line with FA KPI CONTRACT CHARGES FROM THE FOLLOWING, PLEASE SELECT AND OUTLINE YOUR CHARGING MECHANISM FOR THIS SOW. WHERE A CHARGING MECHANISM IS NOT REQUIRED, PLEASE REMOVE TEXT AND REPLACE WITH “UNUSED”.

  • Management Information Systems A. The CONTRACTOR shall maintain a process that collects, analyzes, integrates, and reports data. (42 C.F.R. § 438.242(a); Cal. Code Regs., tit. 9, § 1810.376.) This process shall provide information on areas including, but not limited to, utilization, claims, grievances, and appeals. (42 C.F.R. § 438.242(a).)

  • Client Information (2) Protected Health Information in any form including without limitation, Electronic Protected Health Information or Unsecured Protected Health Information (herein “PHI”);

  • DEFECTIVE MANAGEMENT INFORMATION 5.1 The Supplier acknowledges that it is essential that the Authority receives timely and accurate Management Information pursuant to this Framework Agreement because Management Information is used by the Authority to inform strategic decision making and allows it to calculate the Management Charge.

  • Payment Information 3.1 The Authority shall issue a purchase order to the Contractor prior to commencement of the Service.

  • Parent Information The information relating to Parent and its Subsidiaries to be contained in the Proxy Statement and the S-4, or in any other document filed with any other regulatory agency in connection herewith, will not contain any untrue statement of a material fact or omit to state a material fact necessary to make the statements therein, in light of the circumstances in which they are made, not misleading. The Proxy Statement (except for such portions thereof that relate to the Company or any of its Subsidiaries) will comply with the provisions of the Exchange Act and the rules and regulations thereunder. The S-4 will comply with the provisions of the Securities Act and the rules and regulations thereunder.

  • Alert Information As Alerts delivered via SMS, email and push notifications are not encrypted, we will never include your passcode or full account number. You acknowledge and agree that Alerts may not be encrypted and may include your name and some information about your accounts, and anyone with access to your Alerts will be able to view the contents of these messages.

  • Current Information (a) During the period from the date of this Agreement to the Closing, each Party hereto shall promptly notify each other Party of any (i) significant change in its ordinary course of business, (ii) proceeding (or communications indicating that the same may be contemplated), or the institution or threat or settlement of proceedings, in each case involving the Parties the outcome of which, if adversely determined, could reasonably be expected to have a material adverse effect on the Party, taken as a whole or (iii) event which such Party reasonably believes could be expected to have a material adverse effect on the ability of any party hereto to consummate the Share Exchange.

  • Patient Information Each Party agrees to abide by all laws, rules, regulations, and orders of all applicable supranational, national, federal, state, provincial, and local governmental entities concerning the confidentiality or protection of patient identifiable information and/or patients’ protected health information, as defined by any other applicable legislation in the course of their performance under this Agreement.

  • Student Information Those living in The Village hereby agree that the Owner shall receive all Student information provided in the Agreement and waives and releases Owner from any duty of confidentiality that may apply to such information.

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