X hits on this document

PDF document

  - page 68 / 70





68 / 70

PN-4407 (to be published as TIA/EIA TSB-110)

  • Accommodate service provider applications such as customer care, service administration

and billing, and other maintenance functions. The RG OS may facilitate applications such as:

  • Controlling telecommunications calls and data exchanges in progress.

  • Initiating signaling exchanges with access networks to support call forwarding and related


  • Sending and receiving directory and related information requests.

  • Coordinating cross-media services. For example, a packet radio control uplink to a network server that delivers IP format data via a unidirectional cable (data) channel.

  • Relaying tuning choices, interactive TV responses, and other commands received from user input devices.

  • Service provider GUIs and electronic program guides.

5.4 RG Access Security

A method of identification and authentication, using valid user identifier and password shall be applied for all accesses to the RG and its subsystems. Access control and non-repudiation security management functions shall be provided to control access for reading or changing data base information, and shall be used by the RG to perform real time functions for services being provided by the RG. Apart from these data base security management functions, physical security management functions shall be provided to protect against physical as well as environmental threats.

5.4.1 Authentication

The resident shall have the ability to enable or disable the authentication functions that are under the resident’s control. User Identifier

User identification shall be required of all persons attempting to communicate with the RG. The relevant security requirements shall include the following:

  • A valid user identifier should support an alphanumeric character string.

  • The RG shall support at least 10 unique user identifiers for maintenance and administrative


  • At the resident's option, repeated unsuccessful RG access attempts shall result in disconnecting the session after a resident-specified number of consecutive attempts.

  • Alarms shall be automatically generated after a resident-specified number of consecutive unsuccessful RG access attempts.

  • All access attempts by user identifiers shall be logged in appropriate log files.

  • The RG access log file shall include the date, the time, and the user identifier.

  • The deleted and/or deactivated user identifiers shall be noted in a User Identifier log file.


Document info
Document views316
Page views316
Page last viewedFri Jan 20 04:10:12 UTC 2017