`

`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 Mtl'l Technologies, Inc. (601.944.7300)
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`- - - - - - - - - -
`
`MTEL1212278
`
`MTel., Exhibit 2004, Google v. MTel., Page 2, IPR2017-00532
`
`

`

`Assigned To:
`ID: aa-ack-broadcast-msg
`Brief Description: Provide the capability to send delivery & read acks to certain broadcasts.
`Detailed Description: 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: I
`
`Issues Description:
`Source: mtel-smo
`Subsystems:
`
`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 Description: Destineer shall provide the capability to send delivery acknowledgement and read acknowledgement ofa reply. For
`example, if you 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 ack may be provided to a PMU, PC terminal, fax machine, or voice mailbox.
`
`Issues Description:
`Source: mtel-smo
`Subsystems:
`
`Issues: No
`Reference:
`
`ID: aa-broadcast-mcr
`Assigned To:
`Brief Description: Provide the capability to send broadcast MCR msgs.
`Detailed Description: Destineer shall provide the capability to send broadcast Multiple Choice Response (MCR) messages.
`Issues Description:
`Source: mtel-smo
`Subsystems:
`
`Counter: 3
`
`Issues: No
`Reference:
`
`ID: aa-broadcast-news
`Brief Description: Provide Skynews.
`Detailed Description: Destineer shall provide the capability to distribute Sky News. This is an existing UMS feature needed for Destineer.
`Issues Description:
`Source: UMS
`Subsystems:
`
`Assigned To:
`
`Counter: 4
`
`Issues: No
`Reference:
`
`ID: aa-broadcast-quotes
`Brief Description: Provide SkyQuotes
`Detailed Description: Destineer shall provide the capability to distribute SkyQuotes for 1-4 stocks twice each business day. This is an
`existing UMS feature needed for Destineer.
`
`Assigned To:
`
`Counter: 5
`
`Issues Description:
`Source: UMS
`Subsystems:
`
`Issues: No
`Reference:
`
`ID: aa-confirm-mcr-choice
`Assigned To:
`Brief Description: Check for confirmation before sending MCR choice.
`Detailed Description: Destineer shall provide the capability for a user to confirm an MCR choice before sending the MCR response.
`Issues Description:
`Source: mtel-jh
`Subsystems:
`
`Counter: 6
`
`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)
`
`2
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`MTEL1212279
`
`MTel., Exhibit 2004, Google v. MTel., Page 3, IPR2017-00532
`
`

`

`ID: aa-customer-individual-enable-dis Assigned To:
`Brief Description: Authorize individual turn on/off of acks.
`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: mtel-smo
`Subsystems:
`
`Issues: No
`Reference:
`
`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: mtel-smo
`Subsystems:
`
`Counter: 8
`
`Issues: No
`Reference:
`
`ID: aa-log-msgs
`Assigned To:
`Brief Description: Store a log of all outgoing messages.
`Detailed Description: Destineer shall provide the capability to store a log of all messages sent by a subscriber. This is essentially an
`autocopy of all message sent out.
`
`Counter: 9
`
`Issues Description:
`Source: mtel-smo
`Subsystems:
`
`Issues: No
`Reference:
`
`ID: aa-mt-trouble-ticket-send
`Assigned To:
`Brief Description: Provide the capability to send trouble ticket bewteen MTs.
`Detailed Description: 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: mtel-mg
`Subsystems:
`
`Issues: No
`Reference:
`
`ID: 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: 11
`
`Scenario: a caller leaves the following MCR message for PIN 9999999: "What's the status of the proposal? a)
`accepted b) rejected". The recipient sends the !st 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: "accepted". [Source: Stephen]
`
`Issues Description:
`Source: mtel-smo
`Subsystems:
`
`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
`
`MTel., Exhibit 2004, Google v. MTel., Page 4, IPR2017-00532
`
`

`

`ID: aa-originate-canned-msg
`Assigned To:
`Brief Description: Provide capability to send canned message to NOC.
`Detailed Description: Destineer 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 of CANNED MESSAGES is loaded into the PMU. The subscriber can send any of these
`special canned messages to the NOC without first receiving a message from the NOC, i.e., 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 that message.
`
`- Example I: Canned message "IO" for a subscriber is defined as "send local weather information now." When the
`PMU sends canned message I 0 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: mtel-bp
`Subsystems:
`
`Issues: No
`Reference:
`
`Assigned To:
`ID: aa-real-time-track-msgs
`Brief Description: Provide real-time tracking of certain subscriber actions.
`Detailed Description: Destineer shall provide real-time tracking of the 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:
`
`- - - - - - - - - - - - - - - - - - - - - - - - - - - - - · · - - - - - - ·-------------------_. ....... ·----------·-···------------·
`ID: access-db-people
`Assigned To:
`Counter: 14
`Brief Description: Restrict access to authorized people
`Detailed Description: Data services shall make data available only to authorized persons as defined by the System Operator.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.2.2.2.a, SRl-5.2.2.1, SRl-5.4.4
`
`Data Management
`Security Management
`
`ID: access-db-processes
`Assigned To:
`Brief Description: Restrict access to data to authorized processes
`Detailed Description: Data shall be accessible only to authorized processes as defined by the System Operator.
`Issues Description:
`Source:
`Subsystems:
`
`Issues: No
`Reference: SRl-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
`
`MTel., Exhibit 2004, Google v. MTel., Page 5, IPR2017-00532
`
`

`

`ID: access-delinquent-accts
`Assigned To: SAE/CEI
`Brief Description: Denial of service to subscribers whose accounts are delinquent
`Detailed Description: 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: 16
`
`Application Message Transfer
`Business Support System Interface
`Character User Interface
`Core Messaging
`Data Management
`Fax Message ·:·ransfer
`Interactive Voice Response User Interface
`RF Message Transfer
`
`· - - - - - - - - - · - - - - - - - - · - - - - - - - - -
`ID: access-files
`Counter: 17
`Assigned To: SAE/CEI
`Brief Description: Use OS security for file access
`Detailed Description: The system shall make use of operating system provided file access permissions as one of its security mechanisms.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.4.4.a-2, SRl-5.2.2.2.a-l
`
`Master Terminal
`
`ID: adhoc-distribution-list
`Brief Description: Adhoc distribution lists
`Detailed Description: 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/CE!
`
`Counter: 18
`
`Issues Description:
`Source: cei-jdg
`Subsystems:
`
`Issues: No
`Reference: SRl-5.3.3.g
`
`Destineer Access for Mac
`Interactive Voice Response User Interface
`MHS Mail Transfer
`
`ID: agent-msg-transport
`Assigned To:
`Brief Description: Transport an agent message to and from a PMU.
`Detailed Description: 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
`
`Counter: 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
`
`MTEL1212282
`
`MTel., Exhibit 2004, Google v. MTel., Page 6, IPR2017-00532
`
`

`

`Assigned To:
`ID: alarm-hr
`Brief Description: Report 5 alarms for BRs.
`Detailed Description: Destineer shall provide the capability to report the following Base Receiver alarm conditions:
`
`Counter: 20
`
`I) Receiver failure (loss of injection, etc.). This alarm sahll latch until reset remotely.
`
`2) Cabinet intrustion. 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
`out period is needed, for example, I 0 seconds, I minute, 5 minutes, I hour.
`
`Source document: Destineer Interoffice Memo, Neal Smith, subject: Alarm Functionality, dated January 12, 1995.
`
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: CET RR 1/25/95
`
`Integrated Network Management System
`
`ID: alarm-bf
`Brief Description: Report 8 alarms for BTs.
`Detailed Description: Destineer shall provide the capability to report the following Base Transmitter alarm conditions:
`
`Assigned To:
`
`Counter: 21
`
`I) 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
`if limits are exceeded;. Once set, this alarm 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 of state 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.
`
`Source document: Destineer Interoffice Memo, Neal Smith, subject: Alarm Functionality, dated January 12, 1995.
`Issues Description: Is a separate requirement needed for the 9 CE alarms?
`Source: cet
`Issues: Yes
`Subsystems:
`Reference: CET RR 1/25/95
`
`ID: alarm-contents
`Assigned To: ALL
`Brief Description: Alarm contents reporting
`Detailed Description: Alarms sent to the Integrated Network Management Subsystem by Destineer components shall contain device
`identifier and alarm type identifier.
`
`Counter: 22
`
`----··--·-·-·---~---·
`
`Issues Description:
`Source: OP
`Subsystems:
`
`Issues: No
`Reference: SRI-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 CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`MTEL1212283
`
`MTel., Exhibit 2004, Google v. MTel., Page 7, IPR2017-00532
`
`

`

`International Message Transfer
`
`ID: alarm-threshold
`Assigned To: CE!
`Brief Description: Specify alarm threshold for notification
`Detailed Description: 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
`Subsystems:
`
`Issues: No
`Reference: BDMl-3.4.1.1.5, BDMl-3.4.3
`
`Integrated Network Management
`Master Terminal
`
`Assigned To: CE!
`ID: 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: cei-gws
`Subsystems:
`
`Issues: No
`Reference: SRl-3.5.2.1.c
`
`Application Message Transfer
`Messaging Application Programming Interface
`
`ID: attributes-discovery-auto
`Assigned To: CEI
`Brief Description: Automatically discover managed objects
`Detailed Description: The system shall automatically survey the network to ascertain the attributes of managed objects.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.4.2.d, BDMl-3.2.1.4.7.1
`
`Counter: 25
`
`Integrated Network Management
`
`ID: attributes-discovery-manual
`Assigned To: CEI
`Brief Description: Manually discover managed objects
`Detailed Description: The system shall be able to query/poll for network component attributes individually.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.4.2.b. I
`
`Counter: 26
`
`Integrated Network Management
`
`ID: audit-event-data
`Brief Description: Audit Record Contents
`Detailed Description: 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 of the event (start and end times). success
`
`Issues Description:
`Source: cet
`Subsystems:
`
`Security Management
`
`Issues: No
`Reference: BDM 1-3.5.2.6.1,BDM-3.5.2.6.5.BDM 1-3.5.2.6.6.BDM 1-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. (601.944.7300)
`
`7
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`MTEL1212284
`
`MTel., Exhibit 2004, Google v. MTel., Page 8, IPR2017-00532
`
`

`

`

`

`ID: authentication-subscriber
`Assigned To: CE!
`Brief Description: Authentication of subscribers prior to network access
`Detailed 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 Vis to support encryption at the point of entry?
`Source: cet
`Subsystems:
`
`Issues: Yes
`Reference: SRl-5.4.4.b-l, SRl-5.6.1.a(v)
`
`Security Management
`
`Assigned To: CEI
`ID: authorization-revoke
`Brief Description: Revocation of User/Group Authorizations.
`Detailed Description: 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: cet
`Subsystems:
`
`Issues: No
`Reference: BDMl-3.5.1.3.1.4
`
`Data Management
`
`Master Terminal
`Security Management
`
`ID: billing-access
`Assigned To: SAE
`Brief Description: Customer service access of billing data
`Detailed Description: 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
`Subsystems:
`
`Issues: No
`Reference: SRl-5.2.3.g
`
`Business Sup port 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 Description: 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 MIS systems.
`mtel-iih
`Issues: Yes
`Reference: BKM
`
`Source:
`Subsystems:
`
`Counter: 36
`
`Business Support System Interface
`Data Management
`Transaction Management
`
`ID: hr-message
`Assigned To: SAE
`Brief Description: The base receiver forwards messages to the SC.
`Detailed Description: The PMU will transmit messages to the base receiver. The Base receiver will forward the message to the sub controller.
`Issues Description:
`Source: sae-fpk
`Subsystems:
`
`Issues: No
`Reference: SA2-2. l .2.a SA2-2. l .3.g
`
`Counter: 37
`
`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
`
`MTEL1212286
`
`MTel., Exhibit 2004, Google v. MTel., Page 10, IPR2017-00532
`
`

`

`ID: canned-messages
`Assigned To: CEI/SAE
`Brief Description: Canned messages shall be available to a subscriber.
`Detailed Description: 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
`Subsystems:
`
`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
`Assigned To:
`Brief Description: Identification of a clone PMU
`Detailed Description: The system shall ~nable 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
`(i.e. if a PMU responds in multiple zones simultaneously).
`Source: cet
`Issues: Yes
`Subsystems:
`Reference:. SRl-5.4.4.e-I, SRl-5.4.4
`
`Counter: 39
`
`RF Message Transfer
`
`Assigned To: SAE
`ID: compression-pmu
`Brief Description: Destineer will provided compression
`Detailed Description: 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: SRl-5.4.4.c-2
`
`Counter: 40
`
`RF Message Transfer
`
`ID: configuration-archive
`Assigned To: CEI
`Brief Description: The system shall log config changes
`Detailed Description: The system shall maintain a history of specified configuration changes.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.4.2.g
`
`Counter: 41
`
`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 Mtel Technologies, Inc. (601.944.7300)
`
`JO
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`MTEL1212287
`
`MTel., Exhibit 2004, Google v. MTel., Page 11, IPR2017-00532
`
`

`

`ID: configuration-attributes-region
`Assigned To: CE!
`Brief Description: Region attributes shall include POC for mgmt functions
`Detailed Description: Points of contact (POCs) for each network management function shall be designated for each region.
`Issues Description: There is no concept of a REGION in Destineer with respect to the RF. What is meant by a REGION? Is REGION a
`concept for network management/maintenance only?
`Source: cet
`Issues: Yes
`Subsystems:
`Reference: SRl-5.4.2.h, BDMl-3.2.1.5.1
`
`Counter: 42
`
`Assigned To: CEl/SAE
`ID: configuration-hr-location
`Brief Description: The base receiver location will be known
`Detailed Description: Destineer shall contain data to define locations of BRs.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.6.1.a.2
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`ID: configuration-ht-location
`Assigned To: CEl/SAE
`Brief Description: Destineer will maintain the base transmitter location.
`Detailed Description: Destineer shall contain data to define locations ofBTs.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SR 1-5 .6.1.a.2
`
`Counter: 43
`
`Counter: 44
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`- - - - - - - ----------------·
`Counter: 45
`Assigned To: ALL
`ID: configuration-coverage
`Brief Description: Configuration coverage requirements
`Detailed Description: The system configuration shall be able to support 500 coverage areas and 55 zones of operation.
`Issues Description:
`Source:
`Subsystems:
`
`Issues: No
`Reference:
`
`Integrated Network Management
`- - - - ------------------ -
`ID: configuration-data-access
`Assigned To: CEI
`Brief Description: Access to configuration data
`Detailed Description: The system shall provide Destineer processes with access to configuration data.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-3.5.1.1.a. SRl-5.5.5.C
`
`Counter: 46
`
`ID: configuration-database
`Assigned To: CEI
`Brief Description: The system shall maintain a configuration database.
`Detailed Description: The system shall maintain a configuration database.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.4.2.f
`
`Integrated Network Management
`
`11
`
`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
`
`MTEL1212288
`
`MTel., Exhibit 2004, Google v. MTel., Page 12, IPR2017-00532
`
`

`

`

`

`ID: configuration-sc-location
`Assigned To: CEI/SAE
`Brief Description: Store SubController location data
`Detailed Description: The system shall store the location of each subcontroller.
`Issues Description:
`Source:
`Subsystems:
`
`Issues: No
`Reference:
`
`Counter: 53
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`----·-------------~------- - - - - -
`Assigned To: CEI/SAE
`ID: configuration-topology
`Counter: 54
`Brief Description: Configuration of network topology
`Detailed Description: The system shall describe logical relationships between managed objects.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.4.2.d, BDMl-3.2.1.4.5.2
`
`Data Management
`Integrated Network Management
`Master Terminal
`- - - - - - - - - - - - - - - - - - - - - - - - -
`ID: configuration-topology-add-delete Assigned To: CEI/SAE
`Brief Description: Network components can be added and deleted to/from topology
`Detailed Description: The system shall have the ability to add and delete network components in the configuration database.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.4.2.b.3, BDM 1-3.2.2.3
`
`Counter: 55
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`ID: configuration-topology-network-
`Assigned To: CEI
`Brief Description: A network map is required to view topology
`Detailed Description: The system shall display topological configuration data in the form of a network map.
`Issues Description:
`Source: cet
`Subsystems:
`
`Issues: No
`Reference: SRl-5.4.2.b
`
`Counter: 56
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`ID: configuration-update-managed-ob Assigned To: CEl/SAE
`Brief Description: Store current attributes of managed objects
`Detailed Description: 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: cet
`Subsystems:
`
`Issues: No
`Reference: SR 1-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 authorization from Mtel Technologies, Inc. (601.944.7300)
`
`13
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`MTEL1212290
`
`MTel., Exhibit 2004, Google v. MTel., Page 14, IPR2017-00532
`
`

`

`ID: configuration-zone-location
`Assigned To: CEl/SAE
`Brief Description: The zone location shall be known.
`Detailed Description: The zone location must be defined in geographic coordinates (latitude,longitude) to support the location of a PMU. A
`zone is also provided in a text format (greater New York area), recorded for the voice system, and stored as a fax map.
`
`Counter: 58
`
`Issues Description:
`Source: sae-fpk
`Subsystems:
`
`Issues: No
`Reference: SRl-5.3 .. 6.a
`
`Data Management
`Integrated Network Management
`Master Terminal
`
`Assigned To:
`ID: configuration-zones
`Brief Description: Zones are included in the configuration database
`Detailed Description: The system shall be able to add and delete zones (defined as a set ofBTs) to/from the database. The database shall be
`configurable to support 1 or more zones.
`Issues Description: Note that SysOps define zones, !NM merely stores the zone configuration information. How does Customer Service
`reallocate zones to individual PMUs?
`Source: cet
`Issues: Yes
`Subsystems:
`Reference: SRl-5.2.5.e
`
`Counter: 59
`
`Business Support System Interface
`Data Management
`Integrated Network Management
`Master Terminal
`RF Message Transfer
`Subcontroller
`
`Assigned To: SAE/CEI
`ID: control-commands
`Brief Description: Managed devices and processes shall accept control commands
`Detailed Description: All Destineer managed devices and NOC software processes must accept control commands from the Integrated
`Network Management function. Control commands shall include initialization, shutdown, reset, mode control and
`configuration control commands. Control commands shall be logged.
`
`Counter: 60
`
`Issues Description:
`Source:
`Subsystems:
`
`Issues: No
`Reference:
`
`ALL
`Integrated Network Management
`Transaction Management
`
`ID: conversion-ascii-tiff
`Assigned To: CEI
`Brief Description: An ASCII file to TIFF/F fax file conversion will be supported.
`Detailed Description: The system will provide a service to convert an ASCII file to a TIFF/F fax file. A transaction will be generated when
`this feature is invoked.
`
`Counter: 61
`
`Issues Description:
`Source: cei-nps
`Subsystems:
`
`Issues: No
`Reference: SRl-3.3.1.a
`
`Fax 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)
`
`14
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`MTEL1212291
`
`MTel., Exhibit 2004, Google v. MTel., Page 15, IPR2017-00532
`
`

`

`ID: conversion-email-tiff
`Assigned To: CE!
`Brief Description: Convert an email message to TIFF/F format
`Detailed Description: The system will provide a service to convert an e-mail message to a TJFF/F fax message. The only email body parts
`that will actually get converted are the ASCII text, and TIFF/F fax body parts. Since an email file can contain many
`other body parts, the non-convertable body parts will produce a single page that contains a message similar to
`"Message content of type x could not be converted to fax" where x is the type of body part that could not be
`converted. A transaction will be generated when this feature is invoked.
`
`Counter: 62
`
`Issues Description:
`Source: cei-nps
`Subsystems:
`
`Issues: No
`Reference: SRl-3.3.1.a
`
`Data Management
`Fax Message Transfer
`
`ID: coverage-info
`Brief Description: Coverage info
`Detailed Description: The NOC shall provide a description of geographical area covered by Destineer transmitters and receivers. The
`description shall be offered in text, voice, and fax formats. A transaction shall be generated when this feature is
`invoked.
`
`Assigned To: CE!
`
`Counter: 63
`
`Issues Description:
`Source: cei-jdg
`Subsystems:
`
`Issues: No
`Reference: SRl-3.3.1.a.i
`
`Application Message Transfer
`Character User Interface
`Data Management
`Destineer Access for Mac
`Destineer Access For MS Windows
`Interactive Voice Response User Interface
`Master Terminal
`Transaction Management
`
`ID: coverpage-confidential
`Assigned To: CEl/SAE
`Brief Description: Place confidential on fax cover page!
`Detailed Description: The phrase "Confidential" shall appear on the cover page of outbound faxes that have been designated as such. Faxes
`designated as confidential with no cover page will be treated as non-confidential. When multiple faxes are sent in one
`phone call, all will have the same confidentiality. A transaction will indicate ifthe fax
`was sent confidential.
`
`Counter: 64
`
`Issues Description:
`Source: cei-nps
`Subsystems:
`
`Issues: No
`Reference:
`
`Data Management
`Fax Message Transfer
`Transaction Management
`
`This document contains confidential, restricted, and proprietary inf