Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 32.376  Word version:  16.0.0

Top   Top   None   None   Next
0…   2…


0  IntroductionWord‑p. 5

The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
  • TS 32.371: "Security Management concept and requirements".
  • TS 32.372: "Security services for Integration Reference Points (IRP); Information Service (IS)".
  • TS 32.376: "Security services for Integration Reference Point (IRP); Solution Set (SS) definitions".
In 3GPP SA5 context, IRPs are introduced to address process interfaces at the Itf-N interface. The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101 and TS 32.102. IRP consists of IRPManager and IRPAgent. Usually there are three types of transaction between IRPManager and IRPAgent, which are operation invocation, notification, and file transfer.
However, there are different types of intentional threats against the transaction between IRPManagers and IRPAgents. All the threats are potential risks of damage or degradation of telecommunication services, which operators should take measures to reduce or eliminate to secure the telecommunication service, network, and data.
The present document is applicable to the Interface IRP specifications. That is to say, it is only concerned with the security aspects of operations/notifications/file deployed across the Itf-N.

1  ScopeWord‑p. 6

The present document specifies the Solution Set for the IRP whose semantics is specified in TS 32.372 Security Service for IRP Information Service.
This Solution Set specification is related to 3GPP TS 32.372 V14.0.X [5].
Note that within the present document there are several alternate solutions. Specific choices will to be made to counter identified security threats, and to consider performance and cost criteria, i.e. an implementation is not expected to have to support every option for every deployment.

Up   Top   ToC