`
`_
`
`1
`
`Distribution
`
`Jerry Huller
`
`March 13, 19
`
`Destineer Rec! fi v
`
`_
`
`Update
`
`. An update to the Destineer Functional Requirements Database (FRD) is now available. The
`update incorporates most of the changes discussed at the Requirements Review held in
`January. A few are still being worked on.
`
`0 Remember that the new features may require that new transactions be identified and
`implemented.
`
`.
`
`I incorporated all inputs I had as of last Friday, and I generated the file “nocreqimdb.” I also
`included proposed new requirements which are described in four memos dating from
`February 20 to March 9; their requirement ID starts with “aa-”, to facilitate review.
`
`. A copy of the report of open requirements is attached. There are 594 outstanding
`requirements, counting 13 proposed new ones. Request that you review the report and
`identify any changes which are needed by April 28. If necessary, we will hold another
`technical session to update the FRD.
`
`. A copy of the latest version of the Functionality Matrix is also attached. It needs to be
`updated to reflect the changes in the FRD, particularly for release 1.0 (e.g., add SkyNews and
`SkyQuotes capabilities).
`
`. The above files are available on soflcopy to ATC personnel.
`
`0 The FRD is on the ATC network in ATC_DATA\RQMTS\nocreq5.mdb (Microsoft
`Access format)
`
`The Functionality Matrix is on the ATC network in ATC_DATA\RQMTS\rel06j.xls
`(Microsoft Excel format)
`
`. The FRD is available to CE] and SAE personnel in the xfer directory on Puma.
`
`Attachments (2)
`
`Distribution: Ed Chwieseni
`Bruce Deer _
`_
`Stephen OshmskKE/
`Ro er Dauzat S
`)- without attachments
`Pau Kee anC(EAE) -_w1thout attachments
`Gar Spre
`I) - without attachments
`
`cc:
`
`Jefl‘Nielson ~ without attachments
`Dmesh Sheth
`
`MTEL1212277
`
`1
`
`GOOGLE 1017
`
`
`
`NWN Functional Requirements
`
`Open Requirements
`13-Mar-95
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtcl Technologies. lnc. (6(ll.944.7300)
`
`I
`
`HIGHLY CONFIDENTIAL - ATTORNEYS’ EYES ONLY
`
`MTET1212278
`
`2
`
`
`
`Assigned To:
`ID: aa-ack-broadcast-msg
`Brief Description: Provide the capability to send delivery & read acks to certain broadcasts.
`Demllfid Dfiscrlplloni Destineer shall provide the capability to send delivery acknowledgement and a read acknowledgement of certain
`broadcast messages. The system will also provide the capability to limit the size of groups which have the
`acknowledgement features.
`
`Counter:
`
`1
`
`Issues Description:
`Source: mtel-smo
`5'1l7SYSt°‘“51
`
`Issues: No
`Reference:
`
`Assigned To:
`ID: aa-ack-to-msg-reply
`Brief Description: Provide the capability to send delivery & read acks to a msg reply.
`Detailed Descflpfiflfll Dcstineer shall provide the capability to send delivery acknowledgement and read acknowledgement of a reply. For
`example, ifyou send me an MCR message, and I send you an MCR reply back, then I will receive delivery and/or
`read acknowledgement that you have gotten my reply.
`
`Counter: 2
`
`The aclc may be provided to a PMU, PC terminal, fax machine, or voice mailbox.
`
`Issues Description:
`Source: mtel-smo
`S“l3S)’Sl€mS3
`
`Issues: No
`Reference:
`
`Assigned To:
`ID: aa-broadcast-mer
`Brief Description: Provide the capability to send broadcast MCR msgs.
`Detallltd D¢9¢TlPtl°n3 Destineer shall provide the capability to send broadcast Multiple Choice Response (MCR) messages.
`Issues Description:
`Source: mtel-smo
`S‘-ll’5)’5l9m53
`
`Issues: No
`Reference:
`
`Counter: 3
`
`ID:
`
`ID:
`
`ID:
`
`Assigned To:
`
`Counter: 4
`
`aa—broadcast-news
`Brief Description: Provide Skyncws.
`Delfilled D€SCTlPll0"= Destineer shall provide the capability to distribute SkyNews. This is an existing UMS feature needed for Destineer.
`Issues Description:
`Source: UMS
`Sllbsyslcmsi
`
`Issues: No
`Reference:
`
`,aa—broadcast-quotes
`Brief Description: Provide SkyQuotes
`Delalled D95°"lPll°"5 Destineer shall provide the capability to distribute SkyQu0les for 1-4 stocks twice each business day. This is an
`existing UMS feature needed for Destinccr.
`
`Assigned To:
`
`Counter: 5
`
`Issues Description:
`Source: UMS
`5|1b5)’5l€m51
`
`Issues: No
`Reference:
`
`an-confirm-mcr-choice
`
`Counter: 6
`
`Assigned To:
`Bfltf Description: Check for confirmation before sending MCR choice.
`Dflalled D¢5“'lPll0"3 Destineer shall provide the capability for a user to confirm an MCR choice before sending the MCR response.
`Issues Description:
`Source: mtel-jh
`S"l)5)’5l€mS1
`
`Issues: No
`Reference:
`
`This document contains confidential. restricted, and proprietary information and may not be duplicated or distributed. in whole or in
`part, without prior written authorization from Mtel Technologies, Inc. (601.944.730ll)
`
`2
`
`HIGHLY CONFIDENTIAL - ATTORNEYS’ EYES ONLY
`
`MTEL1212279
`
`3
`
`
`
`ID:
`
`aa-customer-individual—enable-dis Assigned To:
`Authorize individual turn on/off of ticks.
`Brief Description:
`Detailed Description:
`Destineer shall provide the capability for a customer to authorize associated subscribers to individually enable and
`disable delivery and read acknowledgments.
`
`Counter: 7
`
`Issues Description:
`Source:
`Subsystems:
`
`mtcl-smo
`
`Issues: No
`Reference:
`
`Counter: 8
`
`Assigned To:
`ID: aa-disable-pmu-acks
`Brief Description:
`Provide capability to disable delivey & read acks for PMU:
`Detailed Description:
`Destineer shall provide the capability for a subscriber to disable delivery and read acknowledgments for a PMU
`Issues Description:
`Source:
`Subsystems:
`
`mtel-smo
`
`Issues: No
`Reference:
`
`aa-log-msgs
`Brief Description:
`Detailed Description:
`
`Assigned To:
`Store a log of all outgoing messages.
`Destineer shall provide the capability to store a log of all messages sent by a subscriber. This is essentially an
`autoeopy of all message sent out.
`
`Counter: 9
`
`Issues Description:
`Source:
`Subsystems:
`
`mtel—smo
`
`Issues: No
`Reference:
`
`aa-mt-trouble-ticket-send
`Brief Description:
`Detailed Description:
`
`Assigned To:
`Provide the capability to send trouble ticket bcwtcen MTs.
`Destineer shall provide the capability to send a trouble ticket from one Master Terminal to another: Destineer shall
`provide the capability for the operator to attach a text or voice message to the trouble ticket
`
`Counter: 10
`
`Issues Description:
`Source:
`Subsystems:
`
`mtel-mg
`
`Issues: No
`Reference:
`
`aa-multi-response
`Assigned To:
`Brief Description:
`Can respond with MCR and canned response.
`Detailed Description:
`Destineer shall provide the capability for a subscriber to respond to a Multiple Choice Response (MCR) message with
`an MCR response and with a canned response. which may be initiated at different times.
`
`Counter:
`
`ll
`
`ID:
`
`ID:
`
`Scenario: a caller leaves the following MCR message for PIN 9999999: “Whal’s the status ofthe proposal? a)
`accepted b) rejected“. The recipient sends the lst response from the canned message list: “Will get back to you". At
`some time later, the recipient sends the 2nd response from the MCR list: “aecepted".
`[Sourcet Stephen]
`
`Issues Description:
`Source:
`Subsystems:
`
`mtel-smo
`
`Issues: No
`Reference:
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtel Technologies, Inc. (601.944.7300)
`
`3
`
`HIGHLY CONFIDENTIAL - ATTORNEYS’ EYES ONLY
`
`MTEL1212280 I
`
`4
`
`
`
`Assigned To:
`ID: aa-originate-canned-msg
`Brief Description: Provide capability to send canned message to NOC.
`Defined D¢5¢FiPll°n3 Destinecr shall provide the capability for a subscriber to originate sending a canned message addressed to the NOC.
`The objective is to offer advanced information/transaction service with a simple Tango type PMU device.
`
`Counter: 12
`
`A customer subscribes to "special services and option" from Destineer. His/her NOC record is configured with this
`new option. A special set ofCANNED MESSAGES is loaded into the PMU. The subscriber can send any ofthese
`special canned messages to the NOC without first receiving a message from the NOC, i.c., the subscriber can originate
`a canned message to the NOC. This canned message is addressed to the NOC, which analyzes the message and takes
`appropriate action on mat message.
`
`- Example 1: Canned message "10" for a subscriber is defined as "send local weather information now." When the
`PMU sends canned message I0 to the NOC, the NOC will get the weather information from the information service
`provider and send it to the subscriber PMU.
`
`- Example 2: Canned Message "17" for a subscriber is defined as "call home (601-123-4567) and deliver a voice
`message that ‘I will be late'." When the PMU sends this message to the NOC, the NOC will call the home number and
`deliver the recorded message ”I will be late."
`
`In this implementation a simple PMU will have up to 128 canned messages that can be used for these type of
`applications. By implementing this functions with simple PMU, we move into advanced functionality (kind of agent
`service) without waiting on an advanced PMU.
`
`Issues Description:
`Source: mte|—bp
`Sub-5)’5'°|“53
`
`Issues: No
`Reference:
`
`ID:
`
`ID:
`
`ID:
`
`Assigned To:
`aa-real-time-track—msgs
`Brief Description‘. Provide real-time tracking of certain subscriber actions.
`Detailed DESCFIIJWJHZ Destineer shall provide real-time tracking ofthe following items, considered as a single subscriber transaction:
`- message entry,
`- messages sent (and attempts),
`- message acknowledgments and replies,
`~ attempts to check on acknowledgments and replies.
`
`Counter:
`
`13
`
`Issues Description:
`Source: mtel-smo
`Subsystems:
`
`Issues: No
`Reference:
`
`Counter:
`
`14
`
`Assigned To:
`access-db-people
`Brief Description: Restrict access to authorized people
`Defined Description? Data services shall make data available only to authorized persons as defined by the System Operator.
`Issues Description:
`Source:
`Subsystems:
`
`cet
`
`Issues: No
`Reference: sRi—5.2.2.2.a, SR1-5.2.2.1, SRl—5.4.4
`
`Data Management
`Security Management
`
`Assigned To:
`access—db-processes
`Brief Description: Restrict access to data to authorized processes
`Delfllled Description! Data shall be accessible only to authorized processes as defined by the System Operator.
`Issues Description:
`Source:
`5'-'b5Y5‘¢m53
`
`Issues: No
`Reference: SR1-5.2,2.2.a
`
`Counter:
`
`15
`
`Data Management
`Security Management
`
`4
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part. without prior written authorization from Mtel Technologies, Inc. (601.944.7300)
`
`HIGHLY CONFIDENTIAL - ATTORNEYS’ EYES ONLY
`
`MTEL1212281
`
`5
`
`
`
`ID:
`
`Assigned To: SAE/CEI
`access-delinquent-accts
`Brief Dcscriptiont Denial of service to subscribers whose accounts are delinquent
`Dflmied DC-5¢|'|P“0"3 The system shall deny service to subscribers whose accounts are not current.
`Issues Description: This may be based on billing data or flags in the subscriber profile.
`Source: cet
`Issues: No
`Subsystems:
`Reference: SRl—5.4.4.b~l
`
`Counter:
`
`I6
`
`Application Message Transfer
`Business Support System Interface
`Character User Interface
`
`Core Messaging
`Data Management
`Fax Message ‘Transfer
`Interactive Voice Response User Interface
`RF Message Transfer
`
`ID:
`
`Assigned To: SAE/CEI
`access-files
`Brief Description: Use OS security for file access
`Demiicd D°5°i’iI“i0“¢ The system shall make use of operating system provided file access permissions as one of its security mechanisms.
`Issues Description:
`Source: cet
`5“b5.Vstems:
`
`Issues: No
`Reference: SR1-5.4.4.a-2, SR1-5.2.2.2.a-1
`
`Counter: 17
`
`Master Terminal
`
`ID: adhoc-distribution-list
`Brief Description: Adhoc distributionlists
`Dfitaiied D€5U'iPfi01'l3 Destineer shall provide the capability for non-subscribers and subscribers to create "on-the-fly" temporary distribution
`lists. The system shall be able to process temporary distribution lists.
`
`Assigned To: SAE/CEI
`
`Counter: 18
`
`Issues Description:
`Source: cei-jdg
`Subsystems:
`
`Issues: No
`Reference: SR1-S.3.3.g
`
`Destineer Access for Mac
`Interactive Voice Response User Interface
`MHS Mail Transfer
`
`Assigned To:
`ID: agent-msg-transport
`Brief Description: Transport an agent message to and from a PMU.
`Detailed D95"iPii0“? Destineer shall provide the capability to transport an agent message to a PMU or from a PMU.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: CET RR 1/25/95
`
`19
`
`Application Message Transfer
`Core Messaging
`Data Management
`Messaging Application Programming Interface
`RF Message Transfer
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtel Technologies, Inc. (601.944.7300)
`
`5
`
`HIGHLY CONFIDENTIAL - ATTORNEYS’ EYES ONLY
`
`MTEIj2]2282
`
`6
`
`
`
`lD: alarm-br
`
`Assigned To:
`
`Counter: 20
`
`Brief Description:
`Detailed Description:
`
`Report 5 alarms for BRs.
`Destineer shall provide the capability to report the following Base Receiver alarm conditions:
`
`1) Receiver failure (loss of injection, etc). This alarm sahll latch until reset remotely.
`
`2) Cabinet intnrstion. This info will give NOC personnel knowledge of the time a door was opened and again when
`the door is closed.
`
`3) Loss of AC power (input from UPS). A change of state must be reported.
`
`4) Alarm on reset. Each CPU reset shall cause an alarm to be generated.
`
`5) Lack of forward channel sync time—out. Each change of state shall be reported. As a design goal, an adjustable time
`outperiod is needed, for example, 10 seconds, 1 minute, 5 minutes, 1 hour.
`
`Source document: Destineer lnteroffrce Memo, Neal Smith, subject: Alarm Functionality, dated January 12, 1995.
`
`Issues Description:
`Source:
`Subsystems:
`
`cet
`
`Issues: No
`Reference: CET RR 1/25/95
`
`Integrated Network Management System
`
`ID: alarm-bt
`
`Assigned To:
`
`Counter: 21
`
`Brief Description:
`Detailed Description:
`
`Repon 8 alanns for BTs.
`Destineer shall provide the capability to report the following Base Transmitter alarm conditions:
`
`1) Average power output hi/lo limit. A station must generate an alarm iflimits are exceeded;. Once set, this alarm
`must be cleared remotely in order to prevent repetitive alarms on key up.
`
`2) Secondary average RF power output hi/lo limit. If a remote power sensor is used, a station must generate an alarm
`iflimits are exceeded; Once set, this alamt must be cleared remotely in order to prevent repetitive alarms on key up.
`
`3) Reflected power hi limit. This condition requires remote clearing.
`
`4) Secondary reflected power hi limit. This condition requires remote clearing.
`
`5) Power amplifier module fault, to include forward and reflected power limits, module current limits, PA temperature
`and fan failure. This condition requires remote clearing.
`
`6) Exciter fault. This condition requires remote clearing.
`
`7) Door intrusion alarm. A change ofstate must be reported. This information will give NOC personnel knowledge of
`the time a door was opened and again when the door is closed.
`
`8) High temperature cutback alarm. This condition requires remote clearing.
`
`Issues Description:
`Source:
`Subsystems:
`
`Source document: Destineer Interoffice Memo, Neal Smith. subject: Alarm Functionality, dated January 12, 1995.
`is a separate requirement needed for the 9 CE alarms’?
`issues: Yes
`Reference: CET RR l/25/95
`
`ID: alarm-contents
`Brief Description:
`Detailed Description:
`
`Assigned To: ALL
`
`Counter: 22
`
`Alarm contents reporting
`Alarms sent to the integrated Network Management Subsystem by Destineer components shall contain device
`identifier and alarm type identifier.
`
`Issues Description:
`Source:
`Subsystems:
`
`OF
`
`lssu es: N0
`Reference: SR1-5.4.1.h-1
`
`Character User Interface
`
`6
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtel Technologies, Inc. (601.944.7300)
`
`HIGHLY CONETDENTML L ATTORNEYS’ EYES ONLY
`
`MTEL12l2283
`
`7
`
`
`
`lntemational Message Transfer
`
`Assigned To: CEI
`ID: alarm-threshold
`Brief Description: Specify alarm threshold for notification
`D“-“flied DeS¢FiPfi0"= The system shall allow the system operator to specify the threshold value and sense for attribute values and severity of
`the alarm, for automatic generation of alarms.
`
`Counter: 23
`
`Issues Description:
`Source: cet
`S“b5Y5'9m53
`
`Issues: No
`Reference: BDMl—3.4.l.].5, BDMI-3.4.3
`
`Integrated Network Management
`Master Terminal
`
`ID:
`
`Assigned To: CEI
`api-messaging
`Brief Description: High level messaging AP]
`Detailed Description: Destineer shall provide a high level C++ and C application programming interface which will allow the development
`of customized services,
`
`Counter: 24
`
`Issues Description:
`Source: cci-gws
`5Ub5YS“5m53
`
`Issues: No
`Reference: SRl-3.5.2.l.c
`
`Application Message Transfer
`Messaging Application Programming Interface
`
`Assigned To: CEI
`ID: attributes-discovery-auto
`Brief Description: Automatically discover managed objects
`Dflaiifid D¢5¢FiPti0n= The system shall automatically survey the network to ascertain the attributes of managed objects.
`Issues Description:
`Source: cet
`5“b5)’5t‘*-ms?
`
`Issues: No
`Reference: SR1-5.4.2.d, BDM1-3.2.1.4.7.1
`
`Counter: 25
`
`Integrated Network Management
`
`Counter: 26
`
`Assigned To: CEI
`ID: attributes-discovery-manual
`Brief Description: Manually discover managed objects
`Dflaikd D95CriPTi0ll3 The system shall be able to query/poll for network component attributes individually.
`Issues Description:
`Source:
`s“b5.V5t9mS1
`
`cet
`
`Issues: No
`Reference: SR1-5.4.2.b.l
`
`Integrated Network Management
`
`ID:
`
`audit—event-data
`Brief Description: Audit Record (,‘ontenLs
`Delaiied D°5¢TiPll0"5 The audit record shall identify. at a minimum.
`or failure of event, and requestor of event.
`
`Assigned To:
`
`Counter: 27
`
`type of event. date and time ofthe event (start and end times). success
`
`Issues Description:
`Source:
`5“b5.V5t¢m5¢
`
`cet
`
`Security Management
`
`Issues: No
`Reference: BDM1-3.5.2.6.1,BDM-3.5.2.6.5,BDM1-3.5.2.6.6.BDMl—3.5.2.6.7
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtcl Technologies. Inc. (60I.944.7300)
`
`7
`
`HIGHLYICONFIDENTIAL - ATTORNEYS’ EYES ONLY
`
`MTEL1212284
`
`8
`
`
`
`ID:
`
`audit-event-def
`Assigned To:
`Brief Description: Definition ofaudit events
`invalid user authentication attempts, logins by persons, process registrations, unsuccessful
`Demiled Description: Audit events shall include:
`data access attempts by processes, changes to user security profiles by System Operators.
`Issues Description: Detailed description needs rcwording.
`Source: cet
`Issues: Yes
`Subsystems:
`Reference: BDMI-3.5.2.3.l.l thru BDMI-3.5.2.3.l.5,BDMl-3.5.2.3.2.l2,BDMl—3.
`
`Counter: 28
`
`Security Management
`
`ID:
`
`Assigned To:
`audit-event-selection
`Brief Description: Dynamic Audit Event Selection.
`Detailed D°5CTiPti°“5 The system will be capable of dynamically selecting events for display,
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: BDMI-3.52.3
`
`Counter: 29
`
`Master Terminal
`
`Security Management
`
`ID: audit-exception-reports
`Brief Description: Audit Exception Reports.
`Dfifamd D¢5“iPti0n= The system shall include the capability to produce security exception and summary reports by user or role, access
`event, and domain.
`
`Assigned To:
`
`Counter: 30
`
`Issues Description:
`
`Source:
`S“b5Y5‘em55
`
`cet
`
`‘
`
`‘
`
`Issues: No
`-Reference: BDMI-3.5.2.7
`
`Data Management
`Master Terminal
`Security Management
`
`Assigned To:
`
`audit—trail
`Brief Description: maintain audit trail
`Dflfliled D€5C|’iPfi0fl=
`The system shall maintain an audit trail ofsecurity sensitive events.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: BDMI-3.5.2.3
`
`Counter: 3]
`
`Data Management
`Security Management
`
`Counter: 32
`
`Assigned To:
`authen—files-maintenance
`Brief Description: Create/Modify ID/Authentication Files.
`Dflflikd Description! The system shall be able to create/modify lD & authentication files for subscribers and NOC users.
`Issues Description:
`Source:
`Subsystems:
`
`cet
`
`Issues: No
`Reference: BDMl-3.5.l.3.l.l0
`
`ID:
`
`ID:
`
`Data Management
`Master Terminal
`
`Security Management
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtel Technologies, Inc. (601.944.7300)
`
`8
`
`HIGHLY CONfiDENTIAL — ATTORNEYS’ EYES ONLY
`
`MTEL1212285
`
`9
`
`
`
`ID:
`
`Assigned To: CEI
`authentication—subscriber
`Brief Description: Authentication ofsubscribers prior to network access
`Detaiied Description: Subscriber access security shall authenticate the subscriber, third parties, and NOC operators before granting network
`access.
`
`Counter: 33
`
`Issues Description: Reliable authentication requires encryption equipment in the PMU and NOC hardware platforms and secure key
`distribution.
`Is there a requirement for the Uls to support encryption at the point of entry?
`cet
`Issues: Yes
`
`Source:
`
`Subsystems:
`
`Reference: SR1-5.4.4.b-l, SR]-5.6.l.a(v)
`
`Security Management
`
`Assigned To: CEI
`ID: authorization-revoke
`Brief Description: Revocation of User/Group Authorizations.
`Detaited De5eriPti0i13 The system shall be able to revoke authorization of subscribers and NOC users or groups of subscribers and NOC
`users.
`
`Counter: 34
`
`Issues Description:
`Source: cct
`Siibsystems:
`
`Issues: No
`Reference: BDMI-3.5.l.3.l.4
`
`Data Management
`Master Terminal
`Security Management
`
`Assigned To: SAE
`ID: billing-access
`Brief Description: Customer service access ofbilling data
`Detaiied De5eriPti0"1 Customer service shall have access to subscriber configuration options, message recall, and billing queries. This
`implies a tightly coupled interconnect between the NOC and the billing system.
`
`Counter: 35
`
`Issues Description:
`Source:
`
`cet
`
`S“t?5Y5te"|5¥
`
`Issues: No
`
`Reference: SR1-5.7..3.g
`
`Business Support System Interface
`Data Management
`Transaction Management
`
`Assigned To: SAE
`ID: billing-interconnect
`Brief Description:
`transaction data to be sent to billing system in real-time
`Detailed DeSeriPti0n3 Selected transactions shall be sent to the billing system as they are stored in the transaction database. This is to
`facilitate up-to-the-minute billing data to be accessable by customer service.
`Issues Description: What is the interconnect? Possibles are networked connection or simple RS232 protocol. This is not done in existing
`UMS system. and will require modifications in M15 systems.
`Source: mtel—j_ih
`Issues: Yes
`Subsystems:
`Reference: BKM
`
`Counter: 36
`
`Business Support System interface
`Data Management
`Transaction Management
`
`Counter: 37
`
`Assigned To: SAE
`ID: br-message
`Briet Description: The base receiver forwards messages to the SC.
`Deteiied Deserilitiefli The PMU will transmit messages to the base receiver. The Base receiver will forward the message to the sub controller.
`Issues Description:
`Source:
`5“b53'5te"|53
`
`sae-lipk
`
`Issues: NO
`Reference: SA2-2.l.2.a SA2-2.l.3.g
`
`Subcontroller
`
`9
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtel Technologies. Inc. (601.944.7300)
`
`HIGHLY CONFIDENTIAL - ATTORNEYS’ EYES ONLY
`
`if it
`
`MTEL1212286
`
`10
`
`
`
`ID: canned-messages
`Assigned To: CEI/SAE
`Brief Description: Canned messages shall be available to a subscriber.
`Detailcd D35¢"iP“0"5 A total of 128 canned messages (standard and subscriber-defined) shall be available to a subscriber. A subscriber shall
`be able to view, select, and send both
`types of canned messages, as well as create, edit, and delete all subscriber-defined messages.
`
`Counter: 38
`
`Issues Description:
`Source: cet
`S“b5Y5t°m53
`
`Issues: No
`Reference: CET
`
`Application Message Transfer
`Business Support System Interface
`Character User Interface
`
`Core Messaging
`Data Management
`Destineer Access for Mac
`Destineer Access For MS Windows
`Destineer Access for Xwindows
`Master Terminal
`
`Messaging Application Programming Interface
`Operator Dispatch
`
`ID:
`
`clone—identify
`Brief Description:
`
`Assigned To:
`Identification of a clone PMU
`
`Counter: 39
`
`Deifilled Dfscripfiofli The system shall enable an operator to identify a clone PMU.
`Issues Description: A procedure needs to be defined for detection of clones. This may be accomplished by monitoring PMU locations
`(Le. ifa PMU responds in multiple zones simultaneously).
`cet
`Issues: Yes
`
`Sou rce:
`
`Subsystems:
`
`Reference: SR1-5.4.4.e-1, SR1-5.4.4
`
`RF Message Transfer
`
`Assigned To: SAE
`1]): compression-pmu
`Brief Description: Destineer will provided compression
`Dflailed DC-SCTIPWOHZ Compression will be provided on Destineer for transmission of message to the PMU/PCMCIA. A by product of
`compression may be a more secure message for the RF system. Security is not a requirement for compression.
`Issues Description: What compression algorithms are to be used. What will the PMU support. What will be supported on the PCMCIA
`interface. This may be a future requirement.
`Source: cet
`Issues: Yes
`Subsystems:
`Reference: SR1-S.4.4.c-2
`
`Counter: 40
`
`RF Message Transfer
`
`Assigned To: CE]
`ID: configuration-archive
`Brief Description: The system shall log config changes
`Detailed D°5C|‘iP“0"'- The system shall maintain a history of specified configuration changes.
`Issues Description:
`Source: cet
`
`Issues: No
`
`Subsystems:
`
`Reference: SR1-5.4.2.g
`
`Counter: 4]
`
`Data Management
`Integrated Network Management
`Transaction Management
`
`This document contains confidential. restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part. without prior written authorization from Mtcl Technologies. Inc. (601.944.7300)
`
`10
`
`HIGHLY CONFIDENTIAL - ATTORNEYS’ EYES ONLY
`
`MTEL12]2287
`
`11
`
`
`
`ID:
`
`Assigned To: CEI
`configuration-attributes—region
`Brief Description: Region attributes shall include POC for mgmt functions
`Detailed DCSCTIWOHZ Points of contact (POCS) for each network management function shall be designated for each region.
`Issues Description: There is no concept ofa REGION in Destineer with respect to the RF. What is meant by a REGION? 15 REGION a
`concept for network management/maintenance only?
`Source: cet
`Issues: Yes
`S“b5)’5‘9mS1
`Reference: SR1—5.4.2.h, BDMI-3.2.15.1
`
`Counter: 42
`
`ID:
`
`Assigned To: CEI/SAE
`configuration-br-location
`Brief Description? The base receiver location will be known
`D¢t3il¢d D°5°"lP‘i°n1 Destineer shall contain data to define locations of BRS.
`Issues Description:
`Source:
`Sub-5)’5t€m53
`
`Issues: No
`Reference: SR1-5,6.1.a.2
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`ID:
`
`Assigned To: CEI/SAE
`configuration-bt-location
`Brief Description: Destineer will maintain the base transmitter location.
`Demiled DCSCTIPIIM5 Destineer shall contain data to define locations of BTs.
`Issues Description:
`Source: cet
`SUI’-W5t¢m53
`
`Issues: No
`Reference: SR1-5.6.1.a.2
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`Counter: 43
`
`Counter: 44
`
`Assigned To: ALL
`ID: configuration-coverage
`Brief Description: Configuration coverage requirements
`Dflaikd DCSCVIPIWH1 The system configuration shall be able to support 500 coverage areas and 55 zones of operation.
`Issues Description:
`Source:
`Subsystems:
`
`Issues: No
`Referen ce:
`
`Counter: 45
`
`Integrated Network Management
`
`Assigned To: CEI
`ID: configuration-data-access
`Bricf DNCTIPTIOH1 Access to configuration data
`Demled DCSCFIPIIOD? The system shall provide Destineer processes with access to configuration data.
`Issues Description:
`Source:
`Subsystems:
`
`Issues: No
`Reference: SR]—3.5.l.l.a. SRI-5.5.5.C
`
`cet
`
`Assigned To: CEI
`ID: configuratiomdatabase
`Brief Description: The system shall maintain a configuration database.
`Detailed DBSCTIPHOHI The system shall maintain at configuration database.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRI-5.4.2.f
`
`Integrated Network Management
`
`1]
`
`Counter: 46
`
`Counter: 47
`
`This document contains confidential. restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtel Technologies, Inc. (601.944.7300)
`
`HIGHLY CONFIDENTIAL — ATTORNEYS’ EYES ONLY 4
`
`I
`
`MTEL1212288
`
`12
`
`
`
`Assigned To: CEI
`ID: configuration-gui
`Brief Description: A GUI is required for manipulating configuration data
`Detailed Dtsfifipiiflnt A user interface shall be provided for the display and manual entry/change of managed object attribute values in the
`configuration database.
`
`Counter: 48
`
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SR1-5.4.2.d, BDMI-3.2.l.4.7.2
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`Assigned To: CEI
`ID: configuration-gui-report
`Brief Description: A GUI is required for configuration report generation
`Detailed Description: The system shall include a report generation tool for reporting configuration information.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: sR1—5.5.5.b, SRl-5.4.2.h, BDM1—3.2.4
`
`Counter: 49
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`ID:
`
`configuration-managed—objects-de-V Assigned To: CEI/SAE
`Brief Description: Store default attributes in the DB
`I
`Detailed D°5C"iPti°|l1 The system shall store default attribute values for all managed objects.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SR1-5.4.2.c, BDM1—3.2.l.6.l
`
`Counter: 50
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`ID:
`
`configuration-min-managed—ohjec Assigned To: CEI/SAE
`Brief Description: Minimum set Ofmanaged Object attributes
`Detail“ D¢5°TiPfi°||1 The system will store for each managed object the following set of attributes:
`- device type, location, software name and version, network address, point of contact, status, and warranty expiration
`date
`
`Counter: 51
`
`Issues Description:
`Source: cet
`S“b53’5‘€m55
`
`Issues: No
`Reference: SRI-5.4.2.h. BDMl~3.2.l.2,4
`
`Data Management
`Integrated Network Management
`
`Assigned To: CEI/SAE
`ID: contiguration-poc-attributes
`Brief Description: POC attributes shall include name, location, email, phone #
`Delailtd Description: The configuration database shall contain fields for names, addresses, email addresses and phone numbers for every
`designated Point ofConlact (POC), if available.
`
`Counter: 52
`
`Issues Description:
`Source: oet
`5“b5Y3|€"'|-S3
`
`Issues: No
`Reference: SRl—5.4.Z.h. BDMI-3.2.1.53
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`12
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorization from Mtel Technologies, Inc. (60l.944.7300)
`
`HIGHLY CONFIDENTIAL — ATTORNEYS’ EYES ONLY
`
`MTEL1212289
`
`13
`
`
`
`ID:
`
`Assigned To: CE]/SAE
`configuration-sc—location
`Brief Description? Store SubController location data
`Demled D°5C"iPli0"5 The system shall store the location of each subcontroller.
`Issues Description:
`Source:
`S“bSYSl€fl15=
`
`Issues: No
`Reference:
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`ID:
`
`.
`
`Assigned To: CEI/SAE
`configuration-topology
`Brief Description: Configuration of network topology
`Detailed DC-Scrilliioni The system shall describe logical relationships between managed objects.
`Issues Description:
`Source:
`Subsystems:
`
`Issues: No
`Reference: SRl—5.4.2.d, BDMl—3.2.l.4.5.2
`
`cet
`
`Counter:
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`configuration-topology-add-delete Assigned To: CEI/SAE
`Brief D95¢"lPti0Yl1 Network components can be added and deleted tolfrom topology
`Dflalled D°59"iP'i°“3 The system shall have the ability to add and delete network oomponents in the configuration database.
`Issues Description:
`Source: eet
`Subsystems:
`
`Issues: No
`Reference: SRl—5.4.2.b.3, BDMl—3.2.2.3
`
`Counter: 55
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`Assigned To: CEI
`ID: configurati0n-topology-network-
`Brief Description: A network map is required to view topology
`Detailed De§°"iPfi0"5 The system shall display topological configuration data in the form olia network map.
`Issues Description:
`Source:
`S“b5Y5“‘-"153
`
`Issues: No
`Reference: SR1-5.4.2.b
`
`cet
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`ID: configuration-update-managed-ob Assigned To: CEI/SAE
`Briff Description: Store current attributes of managed objects
`Dciailw D¢5C|’iPti0"5 The system shall store current attributes for all managed objects in the configuration database, updating these
`attributes automatically as changes occur.
`
`Counter: 57
`
`Issues Description:
`Source:
`Subsystems:
`
`cet
`
`Issues: No
`Reference: SRl—5.4.2.b.2
`
`Data Management
`Integrated Network Management
`
`This document contains confidential, restricted, and proprietary information and may not be duplicated or distributed, in whole or in
`part, without prior written authorizat