Search

Brenda Gates Spielman

from Mechanicsville, VA
Age ~78

Brenda Spielman Phones & Addresses

  • 9154 Graff Ct, Mechanicsville, VA 23116 (804) 559-5831
  • Mechanicsvlle, VA
  • 18 Chase Gayton Ter, Richmond, VA 23233
  • 110 Scarborough Pl, Charlottesville, VA 22903 (804) 296-9954
  • 9154 Graff Ct, Mechanicsvlle, VA 23116 (804) 986-2500

Work

Company: Acision Apr 1998 to May 2013 Position: Technical team manager

Education

School / High School: Emory and Henry College Specialities: Mathematics, Physics

Skills

C++ • Software Engineering • Linux • Agile Methodologies • C • Programming • Scrum • Software Documentation • Software Design • Embedded Software • Waterfall • Technical Documentation • Embedded Systems • Published Author • Document Review • Code Review • Forth • Telecommunications • Sdlc • Management • Unix • Testing • Software Development • Requirements Analysis • Software Development Life Cycle

Industries

Computer Software

Resumes

Resumes

Brenda Spielman Photo 1

Brenda Spielman

View page
Location:
Mechanicsville, VA
Industry:
Computer Software
Work:
Acision Apr 1998 - May 2013
Technical Team Manager

Avionics Specialties Oct 1986 - Feb 1998
Manager of Software Engineering
Education:
Emory and Henry College
University of Virginia
Masters, Computer Science, Applied Mathematics
Skills:
C++
Software Engineering
Linux
Agile Methodologies
C
Programming
Scrum
Software Documentation
Software Design
Embedded Software
Waterfall
Technical Documentation
Embedded Systems
Published Author
Document Review
Code Review
Forth
Telecommunications
Sdlc
Management
Unix
Testing
Software Development
Requirements Analysis
Software Development Life Cycle

Publications

Us Patents

Ip-Based Notification Architecture For Unified Messaging

View page
US Patent:
6665378, Dec 16, 2003
Filed:
Jul 31, 2000
Appl. No.:
09/629053
Inventors:
Brenda Gates Spielman - Charlottesville VA, 22903
Lewis Dean Dodrill - Richmond VA, 23233
Satish Joshi - Glen Allen VA, 23060
Nagendran Parasu - Richmond VA, 23233
Robert James Lockwood - Richmond VA, 23233
International Classification:
H04M 164
US Classification:
379 8812, 379 8813, 709318, 709230, 370353
Abstract:
A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture includes a notification process, configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. The notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. The notification process determines, for each received notification message, the subscribers notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscribers notification preference. The notification process may have access via the prescribed open protocol to multiple notification delivery processes, each configured for outputting a notification to a subscribers notification device according to a corresponding device protocol. Hence, subscribers may be notified of events according to their respective preferences, including subscriber device type, or time of notification.

Arrangement For Common-Format Notification Delivery Messages Based On Notification Device Type In An Ip-Based Notification Architecture

View page
US Patent:
6671355, Dec 30, 2003
Filed:
Jul 31, 2000
Appl. No.:
09/629052
Inventors:
Brenda Gates Spielman - Charlottesville VA
Lewis Dean Dodrill - Richmond VA
Satish Joshi - Glen Allen VA
Nagendran Parasu - Richmond VA
Robert James Lockwood - Richmond VA
Assignee:
Cisco Technology, Inc. - San Jose CA
International Classification:
H04M 164
US Classification:
379 8812, 379 8817, 370356, 709230
Abstract:
A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture includes a notification process, configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. The notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. The notification process determines, for each received notification message, the subscribers notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscribers notification preference. The notification process may have access via the prescribed open protocol to multiple notification delivery processes, each configured for outputting a notification to a subscribers notification device according to a corresponding device protocol. Hence, subscribers may be notified of events according to their respective preferences, including subscriber device type, or time of notification.

Scalable Ip-Based Notification Architecture For Unified Messaging

View page
US Patent:
6874011, Mar 29, 2005
Filed:
Jul 31, 2000
Appl. No.:
09/629051
Inventors:
Brenda Gates Spielman - Charlottesville VA, US
Lewis Dean Dodrill - Richmond VA, US
Satish Joshi - Glen Allen VA, US
Nagendran Parasu - Richmond VA, US
Robert James Lockwood - Richmond VA, US
Assignee:
Cisco Technology, Inc. - San Jose CA
International Classification:
G06F015/16
US Classification:
709206, 709230, 379 8812, 719318
Abstract:
A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture enables use of multiple instances of a notification process, each configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. Each notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. Each notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference. Each notification process may have access via the prescribed open protocol to multiple notification delivery processes, each configured for outputting a notification to a subscriber's notification device according to a corresponding device protocol. Multiple instances of each type of notification delivery process may also be utilized for increased capacity.

Arrangement For Common-Format Notification Delivery Messages Based On Notification Device Type In An Ip-Based Notification Architecture

View page
US Patent:
7092497, Aug 15, 2006
Filed:
Nov 12, 2003
Appl. No.:
10/704764
Inventors:
Brenda Gates Spielman - Charlottesville VA, US
Lewis Dean Dodrill - Richmond VA, US
Satish Joshi - Glen Allen VA, US
Nagendran Parasu - Richmond VA, US
Robert James Lockwood - Richmond VA, US
Assignee:
Cisco Technology, Inc. - San Jose CA
International Classification:
H04M 1/64
US Classification:
379 8812, 379 8813, 709230
Abstract:
A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture includes a notification process, configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. The notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. The notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference. The notification process may have access via the prescribed open protocol to multiple notification delivery processes, each configured for outputting a notification to a subscriber's notification device according to a corresponding device protocol. Hence, subscribers may be notified of events according to their respective preferences, including subscriber device type, or time of notification.

Scalable Ip-Based Notification Architecture For Unified Messaging

View page
US Patent:
7668919, Feb 23, 2010
Filed:
Mar 3, 2005
Appl. No.:
11/069961
Inventors:
Brenda Gates Spielman - Charlottesville VA, US
Lewis Dean Dodrill - Richmond VA, US
Satish Joshi - Glen Allen VA, US
Nagendran Parasu - Richmond VA, US
Robert James Lockwood - Richmond VA, US
Assignee:
Cisco Technology, Inc. - San Jose CA
International Classification:
G06F 15/16
US Classification:
709206, 709230, 370465
Abstract:
A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture enables use of multiple instances of a notification process, each configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. Each notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. Each notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference. Each notification process may have access via the prescribed open protocol to multiple notification delivery processes, each configured for outputting a notification to a subscriber's notification device according to a corresponding device protocol. Multiple instances of each type of notification delivery process may also be utilized for increased capacity.

Arrangement For Managing Notification Preferences For Notification Delivery Messages In An Ip-Based Notification Architecture

View page
US Patent:
6560318, May 6, 2003
Filed:
Sep 7, 2000
Appl. No.:
09/656840
Inventors:
Brenda Gates Spielman - Charlottesville VA
Geetha Ravishankar - Glen Allen VA
Govind Pande - Richmond VA
Satish Joshi - Glen Allen VA
Nagendran Parasu - Richmond VA
Robert James Lockwood - Richmond VA
Assignee:
Cisco Technology, Inc. - San Jose CA
International Classification:
H04M 164
US Classification:
379 8812, 379 671, 379 8807, 379 8813, 379 8817, 379 8822, 379908
Abstract:
A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture includes a notification process, configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. The notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. The subscriber directory is controlled by a directory management process, configured for storing subscriber notification preference information in an open protocol-based subscriber directory (such as LDAP). The directory management process stores, as a first object class, notification attributes for respective notification types, each notification attribute specifying for the corresponding notification type a corresponding notification device tag. The notification device tag can include native device information usable to generate a message for a corresponding native notification device.
Brenda Gates Spielman from Mechanicsville, VA, age ~78 Get Report