ADR (Additional Data Repository): Difference between revisions
Content added Content deleted
MikeVislocky (talk | contribs) (Added reference to FE) |
No edit summary |
||
Line 1: | Line 1: | ||
A data storage facility for Additional Data. The ADR dereferences a URI passed in a Call-Info header or PIDF-LO <provided-by> and returns an Additional Data object block. It replaces and deprecates the concept of CIDB previously defined in 08-003 v1. ADR is considered a [[FE (Functional Element)|Functional Element (FE)]]. |
A data storage facility for Additional Data. The ADR dereferences a URI passed in a SIP Call-Info header field or PIDF-LO <provided-by> element and returns an Additional Data object block. It replaces and deprecates the concept of CIDB previously defined in 08-003 v1. ADR is considered a [[FE (Functional Element)|Functional Element (FE)]]. |
||
== Relevant NENA Documents == |
|||
[https://www.nena.org/?page=NG911_AdditionalData NENA Standard for NG9 1 1 Additional Data] |
|||
[[Category:Glossary]] |
[[Category:Glossary]] |
Revision as of 14:11, 14 April 2018
A data storage facility for Additional Data. The ADR dereferences a URI passed in a SIP Call-Info header field or PIDF-LO <provided-by> element and returns an Additional Data object block. It replaces and deprecates the concept of CIDB previously defined in 08-003 v1. ADR is considered a Functional Element (FE).