1

Scope

1

2

References

1

3

Definitions

1

3.19

Definitions imported from other Recommendations

2

4

Abbreviations and acronyms

3

5

Conventions

4

6

Introduction to the F interface

4

6.1

Why Is The F interface needed?

4

7

F interface architecture

5

7.1

The F interface within the TMN architecture

5

7.2

TMN functional architecture and the F interface

5

7.3

TMN Physical architecture and the F interface

7

7.4

TMN information architecture and the F interface

8

7.5

F interface/f reference point and the g reference point

8

7.6

Summary of architectural implications for requirements

9

8

TMN user’s requirements impacting the F interface

9

8.1

General requirements

10

8.2

Task-related user requirements

10

9

Initialization requirements

11

10

Object management requirements

11

10.1

Relationships between WOs and MOs

12

10.1.1

UMO/MO cardinality

13

10.2

Naming

15

10.3

Retrieval services

15

10.4

Modification services

15

10.5

Notification services

16

10.6

Create services

16

10.7

Destruction services

16

11

Shared Management Knowledge requirements

17

11.1

Roles

17

11.2

Establishment of Shared Management Knowledge

17

12

Event registration/notification requirements

18

12.1

Receiving event notifications

18

12.2

Controlling event notification

18

13

Location transparencies requirements

18

14

Data consistency requirements

19

15

Quality, performance, and OA&M requirements

19

15.1

Initialization performance

19

15.2

Message transfer

19

15.3

Reliability, availability, survivability

19

15.4

Software management

19

15.5

Real-time message management

20

16

Security requirements

20

16.1

User identification requirements

20

16.2

Authentication

20

16.3

Access control

20

16.4

Data integrity

20

16.5

Privacy

20

16.6

Auditing

20

17

Physical implementation requirements

21

18

What’s part of WSF but not part of the F interface

21

Appendix I

Recommendation M.3300 (1992)

21

Appendice II

Bibliography

22