Interface Requirements

  • Interface Requirements (IR) refer to the requirements of an interface between two Network Elements at different layers of protocol stacks as applicable. Interfaces are defined at different layers for convenience of peer-to-peer communication
    a. Layer 1 Physical (E1, STM-n, Ethernet, etc.)
    b. Layer 2 Link (Ethernet, PPP, etc.)
    c. Layer 3 Network (IP, Q 931, etc.)
    d. Layer 4 Transport (TCP, UDP, etc.)
    e. Layer 5 Sessions (Call setup, teardown, etc.)
    f. Layer 6 Presentation (ASN.1, etc.)
    g. Layer 7 Applications (Telnet, FTP, www, mail, CORBA, etc.)
  • IRs are part of generic requirements that describe the interoperability specifications to be met by different types of equipment owned and maintained by subscribers or service providers and which are to be interfaced with equipment or network of Telecom Service Providers without degrading the network. Interface Requirements that are commonly used by multiple GRs are separate documents.
  • TEC concurrently creates Test Schedules and Test Procedures for every IR, in order to test and validate network interfaces.


  • IRs are assigned specific numbers for ease of identification, as follows No: TEC/IR/BBB–xxx/vv/MMM-YY
    TEC: Telecommunication Engineering Centre
    IR: Interface Requirements
    BBB: Interface name (alphabets)
    xxx: Interface reference (alpha-numeric value)
    vv: Version reference (numeric value)
    MMM: Month in which IR is released
    YY: Year in which IR is released