Abstract: A mechanism to insert a correct call identifier as a session identifier in an accounting request (AR) record and a mechanism for a charging control function (CCF) device to check the value and generate an error as required. A method can comprise receiving a session initiation protocol packet representing a first attribute value pair; based on the session initiation protocol packet, checking for an existence of an identity between a first field associated with the session initiation protocol packet and a second field associated with a second attribute value pair; and in response to a result of the checking being that the existence of the identity is not determined to be presents between the first field and the second field, updating a third attribute value pair.

Abstract: Technology to respond to a termination reason of an accounting record via an improved charging component is disclosed. The disclosed subject matter can be backwards compatible to support responding to a conventional SIP ‘BYE’ method and a conventional SIP ‘CANCEL’ method. Additionally, the disclosed subject matter can respond to other SIP methods, empty reason-headers, etc. In an aspect, a reason-header can be forced into an accounting record based on received session termination information. In an embodiment, the reason-header can be determined to satisfy a rule related to acceptable reason-headers. Where the rule is determined to be unsatisfied, a query can be generated toward a device that supported the now terminated communication, wherein a response to the query can comprise another reason-header that can be determined to satisfy the rule. The accounting record can be updated based on the other reason-header and employed in generating a charging data record that can alter corresponding billing.

Abstract: A mechanism to insert a correct call identifier as a session identifier in an accounting request (AR) record and a mechanism for a charging control function (CCF) device to check the value and generate an error as required. A method can comprise receiving a session initiation protocol packet representing a first attribute value pair; based on the session initiation protocol packet, checking for an existence of an identity between a first field associated with the session initiation protocol packet and a second field associated with a second attribute value pair; and in response to a result of the checking being that the existence of the identity is not determined to be presents between the first field and the second field, updating a third attribute value pair.

Abstract: Technology to respond to a termination reason of an accounting record via an improved charging component is disclosed. The disclosed subject matter can be backwards compatible to support responding to a conventional SIP ‘BYE’ method and a conventional SIP ‘CANCEL’ method. Additionally, the disclosed subject matter can respond to other SIP methods, empty reason-headers, etc. In an aspect, a reason-header can be forced into an accounting record based on received session termination information. In an embodiment, the reason-header can be determined to satisfy a rule related to acceptable reason-headers. Where the rule is determined to be unsatisfied, a query can be generated toward a device that supported the now terminated communication, wherein a response to the query can comprise another reason-header that can be determined to satisfy the rule. The accounting record can be updated based on the other reason-header and employed in generating a charging data record that can alter corresponding billing.

Abstract: A control plane entity can perform validation checks to confirm the validity of a device identifier, for example, an international mobile equipment identity (IMEI), received from a user equipment (UE) during registration of the UE with a communication network. In one aspect, the control plane entity can verify that the IMEI conforms to a defined format; for example, the IMEI is fifteen digits long, does not comprise alphabets and/or symbols, and/or comprises a valid type allocation code (TAC) of eight decimal digits, etc. The validation of the IMEI can reduce errors in billing that can otherwise result in revenue loss for the service provider.

Abstract: A mechanism to insert a correct call identifier as a session identifier in a accounting request (AR) record and a mechanism for a charging control function (CCF) device to check the value and generate an error as required. A method can comprise receiving a session initiation protocol packet representing a first attribute value pair; based on the session initiation protocol packet, checking for an existence of an identity between a first field associated with the session initiation protocol packet and a second field associated with a second attribute value pair; and in response to a result of the checking being that the existence of the identity is not determined to be presents between the first field and the second field, updating a third attribute value pair.

Abstract: A mechanism to insert a correct call identifier as a session identifier in a accounting request (AR) record and a mechanism for a charging control function (CCF) device to check the value and generate an error as required. A method can comprise receiving a session initiation protocol packet representing a first attribute value pair; based on the session initiation protocol packet, checking for an existence of an identity between a first field associated with the session initiation protocol packet and a second field associated with a second attribute value pair; and in response to a result of the checking being that the existence of the identity is not determined to be presents between the first field and the second field, updating a third attribute value pair.

Abstract: A control plane entity can perform validation checks to confirm the validity of a device identifier, for example, an international mobile equipment identity (IMEI), received from a user equipment (UE) during registration of the UE with a communication network. In one aspect, the control plane entity can verify that the IMEI conforms to a defined format; for example, the IMEI is fifteen digits long, does not comprise alphabets and/or symbols, and/or comprises a valid type allocation code (TAC) of eight decimal digits, etc. The validation of the IMEI can reduce errors in billing that can otherwise result in revenue loss for the service provider.

Abstract: A control plane entity can perform validation checks to confirm the validity of a device identifier, for example, an international mobile equipment identity (IMEI), received from a user equipment (UE) during registration of the UE with a communication network. In one aspect, the control plane entity can verify that the IMEI conforms to a defined format; for example, the IMEI is fifteen digits long, does not comprise alphabets and/or symbols, and/or comprises a valid type allocation code (TAC) of eight decimal digits, etc. The validation of the IMEI can reduce errors in billing that can otherwise result in revenue loss for the service provider.

Abstract: A control plane entity can perform validation checks to confirm the validity of a device identifier, for example, an international mobile equipment identity (IMEI), received from a user equipment (UE) during registration of the UE with a communication network. In one aspect, the control plane entity can verify that the IMEI conforms to a defined format; for example, the IMEI is fifteen digits long, does not comprise alphabets and/or symbols, and/or comprises a valid type allocation code (TAC) of eight decimal digits, etc.