Insert Subscriber Data
API reference for diameter.message.commands.insert_subscriber_data.
This module contains Insert Subscriber Data Request and Answer messages for the S6a/S6d and S7a/S7d interfaces, implementing AVPs documented in 3GPP TS 29.272.
InsertSubscriberData ¶
InsertSubscriberData(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: DefinedMessage
An Insert-Subscriber-Data base message.
This message class lists message attributes based on the current 3GPP TS 29.272 version 19.4.0 Release 19 as python properties, accessible as instance attributes. AVPs not listed in the spec protocol can be retrieved using the InsertSubscriberData.find_avps search method.
Examples:
AVPs accessible either as instance attributes or by searching:
>>> msg = Message.from_bytes(b"...")
>>> msg.session_id
dra1.python-diameter.org;2323;546
>>> msg.find_avps((AVP_SESSION_ID, 0))
['dra1.python-diameter.org;2323;546']
When diameter message is decoded using
Message.from_bytes, it returns
either an instance of InsertSubscriberDataRequest or
InsertSubscriberDataAnswer automatically:
>>> msg = Message.from_bytes(b"...")
>>> assert msg.header.is_request is True
>>> assert isinstance(msg, InsertSubscriberDataRequest)
When creating a new message, the InsertSubscriberDataRequest or
InsertSubscriberDataAnswer class should be instantiated directly,
and values for AVPs set as class attributes:
>>> msg = InsertSubscriberDataRequest()
>>> msg.session_id = "dra1.python-diameter.org;2323;546"
Other, custom AVPs can be appended to the message using the
InsertSubscriberData.append_avp
method, or by overwriting the avp attribute entirely. Regardless of the
custom AVPs set, the mandatory values listed in TS 29.272 must be set,
however they can be set as None, if they are not to be used.
Warning
Every AVP documented for the subclasses of this command can be accessed
as an instance attribute, even if the original network-received message
did not contain that specific AVP. Such AVPs will be returned with the
value None when accessed.
Every other AVP not mentioned here, and not present in a
network-received message will raise an AttributeError when being
accessed; their presence should be validated with hasattr before
accessing.
InsertSubscriberDataAnswer ¶
InsertSubscriberDataAnswer(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: InsertSubscriberData
An Insert-Subscriber-Data-Answer message.
3GPP TS 29.272 version 19.4.0
monitoring_event_config_status
instance-attribute
¶
monitoring_event_config_status: list[MonitoringEventConfigStatus]
vendor_specific_application_id
instance-attribute
¶
vendor_specific_application_id: VendorSpecificApplicationId
InsertSubscriberDataRequest ¶
InsertSubscriberDataRequest(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: InsertSubscriberData
An Insert-Subscriber-Data-Request message.
3GPP TS 29.272 version 19.4.0
vendor_specific_application_id
instance-attribute
¶
vendor_specific_application_id: VendorSpecificApplicationId
vplmn_csg_subscription_data
instance-attribute
¶
vplmn_csg_subscription_data: list[VplmnCsgSubscriptionData]