hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.1.5 onClosePost usage details | The onClosePost attribute is a URI provided by the AP to which a terminating PSAP or PSP indicates that the PSAP is ending the emergency communication. The URI is specified as an HTTPS URI and the same authentication and authorization procedures defined in clauses 9.2 and 9.3 shall apply. If the AP determines that the ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.1.6 subscribeClosePost usage details | The subscribeClosePost attribute is a URI provided by the AP to which a terminating PSAP or PSP indicates it wants to be notified when the caller ends the emergency communication. The terminating PSAP or PSP has to make an HTTP POST request to the provided subscribeClosePost URI when accepting the emergency communicati... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.2 emergencyDataReceived message | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.2.1 emergencyDataReceived message structure | Parameter Presence Type Description timeStamp Mandatory xs:timeStamp Time stamp that the message is sent specified in UTC. route Mandatory pemea:routeType Indicates the path that the message has followed up to this point. delivery Mandatory pemea:deliveryType The node to which the data has just been sent. ETSI ETSI TS ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.2.2 emergencyDataReceived example | <emergencyDataReceived xmlns="urn:pemea:apps:xml:ns:pemea:base" timeStamp="2016-01-14T19:43:01.521Z"> <route msgSeq="CoolAP-7496"> <hops> <hop position="0" timeStamp="2016-01-14T19:43:00.001Z"> <node>https://cooAP.example.com.be:2001/pemea/</node> </hop> <hop position="1" timeStamp="2016-01-14T19:43:00.098Z"> <node>htt... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.3 error message | Parameter Presence Type Description timeStamp Mandatory xs:timeStamp Time stamp that the message is sent specified in UTC. reason Mandatory xs:token The reason that the error was generated based on a token value defined in Table 10. message Optional pemea:msgInfoType The human readable text message describing the probl... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12 PEMEA PIDF-LO Profiling | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.1 Rationale | The Presence Information Data Format (PIDF) [7] Location Object (LO) [3] is a highly extensible data structure. IETF schemas are not repeated in the present document, however references are provided to the documents where these schemas are specified. Note that SubscriberData may be sent either by value or by reference ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.2 entity | Parameter Presence Type Value Description entity Mandatory xs:anyURI uri This value shall be expressed as a URI and should be a URI from the callerIds list if a URI is provided as a URI. |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.3 tuple | Element Parameter PEMEA Presence Type Value Description tuple id Mandatory xs:ID Unique token Used to identify the tuple within the PIDF-LO document. See note. status Mandatory element -- Container for the geopriv object. NOTE: IETF RFC 5491 [4] allows geopriv elements to be contained in a <person> or <device> element ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.4 status | Element Parameter PEMEA Presence Type Value Description status geopriv Mandatory element -- Container for location and user information. ETSI ETSI TS 103 478 V1.3.1 (2025-07) 53 |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.5 geopriv | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.5.1 geopriv element profile | Element Parameter PEMEA Presence Type Value Description geopriv Location-info Mandatory element -- Container for location and user information. usage-rules Mandatory element -- Container for usage rules. method Mandatory element From IANA [10] The value for the method should be based on the values from the IANA registr... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.5.2 location-info | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.5.2.1 location-info profile | The location-info element as defined in the PIDF-LO [3] is open to any XML namespace. PEMEA constrains the location types to those described in the PIDF-LO profile specification IETF RFC 5491 [4]. Element Parameter PEMEA Presence Type Description Location-info gml:Point Conditional element A 2 dimensional or 3 dimensio... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.5.2.2 Confidence | IETF RFC 7459 [6] introduced an explicit means of representing confidence and uncertainty into locations provided in a PIDF-LO. Inclusion of this parameter is mandatory with all shape-types with the exception of the point types. If the location API of the device provided a confidence then this value can be explicitly p... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.5.3 usage-rules | Element Parameter PEMEA Presence Type Default Value Description usage-rules retransmission- allowed Mandatory element yes This value should be set to "yes" whenever the application user may be roaming. See note. retention-expiry Mandatory xs:dateTime -- This value is set by the AP based on user policy. If no user polic... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.5.4 method | The method parameter is an element in the geopriv structure that is used to describe how the location information was determined. Often, this will be provided by the location API in the device, sometimes it is not. If is provided then one of values in the IANA registry [10] should be used. If the method is not provided... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.5.5 provided-by | Element Parameter PEMEA Presence Scheme Description provided-by provided-by Mandatory Additional-Data This element contains the provided-by element taken the from the "additional-data" scheme in IETF RFC 7852 [11]. |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.6 timestamp | This occurs after the status stanza is closed. It expresses the time that the PIDF-LO was created and in the context of PEMEA is represents the date and time that the AP received the location and other caller information associated with the current emergency. |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 12.7 PIDF-LO example | The following XML fragment is of a PIDF-LO. The Additional-Data information is not included for brevity. <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:con="urn:ietf:params:xml:ns:ge... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13 PEMEA Additional-Data Profiling | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.1 Rationale | The additional-data specification IETF RFC 7852 [11] was explicitly designed to provide containers for additional information about an emergency call, including who is making the call, what kind of device and network they are using and who the various providers are. The type and nature of the information being conveyed... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.2 Additional-Data: provided-by | PEMEA prefers to pass additional data by-value, clause 9.3 describes situations where this may not be allowed. Information relating to the AP shall always be passed by-value, however, caller information shall only be sent by reference. Entity authorization is described in clause 9.2. Element Parameter PEMEA Presence Ty... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.3 EmergencyCallDataValue | Element Parameter PEMEA Presence Type Description EmergencyCall DataValue EmergencyCallData. ProviderInfo Mandatory ProviderInfoType This information is filled in by the AP. EmergencyCallData. DeviceInfo Optional DeviceInfoType This information may be provided by the application to the AP either at call time or ahead o... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4 EmergencyCallData.ProviderInfo | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4.1 EmergencyCallData.ProviderInfo profile | Inclusion of this element is mandatory. It conveys information for contacting the AP that is originating an EDS message. A full example is of an XML EmergencyCallData.ProviderInfo structure that is compliant with the present document is provided in clause 13.4.3. ETSI ETSI TS 103 478 V1.3.1 (2025-07) 56 Element Paramet... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4.2 DataProviderContact: vcard | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4.2.1 DataProviderContact: vcard profile | The vcard is used extensively in the additional data specification. This is a very flexible and potentially unstructured information container. This table attempts to add structure to the data provider contact information. The information in this table shall be provided, other fields may be provided. Element Field bein... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4.2.2 DataProviderContact: org | Element Element PEMEA Presence Type Description org parameters Mandatory element Holds the parameter that defines the language that the organization name is provided in. text Mandatory xs:string Contains the full name of the AP. ETSI ETSI TS 103 478 V1.3.1 (2025-07) 57 Element Element PEMEA Presence Value Description p... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4.2.3 DataProviderContact: adr | Element Element PEMEA Presence Type Description adr parameters Mandatory element Block defining parameters that describe the type of address. pobox Optional xs:string Post office box of the AP if applicable. See note. ext Optional xs:string Not used. See note. street Mandatory xs:string Street address, street name, num... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4.2.4 DataProviderContact: email | Element Element PEMEA Presence Type Description email text Mandatory xs:string The primary email address of the Application Provider. <vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <email><text>jw@pemea.org</text></email> </vcard> |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4.2.5 DataProviderContact: URL | Element Element PEMEA Presence Type Description url uri Mandatory xs:anyURI The public website of the Application Provider. <vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <url> <uri>http://www.pemea.help</uri> </url> </vcard> |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.4.3 EmergencyCallData.ProviderInfo: Complete Example | This clause provides an example of a complete PEMEA compliant EmergencyCallData.ProviderInfo structure. <EmergencyCallData.ProviderInfo xmlns ="urn:ietf:params:xml:ns:EmergencyCallData" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> <pi:DataProviderReferenc... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.5 EmergencyCallData.DeviceInfo | Inclusion of this element is optional. Much of the information included in this element is unknown to the Application Provider and it need only be provided if the App provides it at call time. See IETF RFC 7852 [11] for examples. Element Parameter PEMEA Presence Type Description EmergencyCall Data.DeviceInfo DataProvid... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6 EmergencyCallData.SubscriberData | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.1 EmergencyCallData.SubscriberData profile | Inclusion of this element is mandatory. Future extension to the protocol usage may move its inclusion to conditional based on EDS origination. This clause defines the elements that make up the EmergencyCallData.SubscriberData structure for use in PEMEA. A full example of an EmergencyCallData.SubscriberData element comp... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2 SubscriberData: vcard | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.1 SubscriberData: vcard profile | The vcard is used extensively in the additional data specification. This is a very flexible and potentially unstructured information container. This table attempts to add structure to the caller information provided in the SubscriberData vcard. The information in this table shall be provided, other fields may be provid... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.2 SubscriberData: Caller's name | Element Element PEMEA Presence Type Description n parameter Mandatory element Used to specify the language that the name is written in. surname Mandatory xs:string Last name of the caller. given Mandatory xs:string Given/first name of the caller. additional Optional xs:string Any other names the caller may have if avai... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.3 SubscriberData: home address | Element Element PEMEA Presence Type Description adr parameters Mandatory element Block defining parameters that describe the type of address. pobox Optional xs:string Use is not recommended. See note. ext Optional xs:string Not used. See note. street Mandatory xs:string Street address, street name, number, suite and fl... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.4 SubscriberData: language | There shall be at least one of these elements but there may be more than one. Element Element PEMEA Presence Type Description lang parameters Mandatory element Used to assist in defining the order of preference if the caller can speak more than one language. Language-tag Mandatory xs:string Name of the language used by... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.5 SubscriberData: gender | Element Element PEMEA Presence Type Description gender sex Mandatory xs:string Indicates the gender of the caller. M, F, O, N, U. <vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <gender><sex>M</sex></gender> </vcard> |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.6 SubscriberData: bday | Element Element PEMEA Presence Value Description bday date Mandatory YYYYMMDD If a value is provided it shall be provided in the form YYYYMMDD. The purpose of the value is to prove the age of the caller. <vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <bday><date>19670722</date></bday> </vcard> |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.7 SubscriberData: tel | Inclusion of this element is optional but recommended. This clause defines how to specify additional telephone contacts for the caller. These may be repeats of the contacts provided in the callerIds specified in clause 10.3.10, however, the numbers in the tel fields are designed for display to the PSAP, while those in ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.8 SubscriberData: email | Inclusion of this element is optional. This element provides email contacts for the caller. No preference or types are specified for the email address. Element Element PEMEA Presence Type Description email text Conditional xs:string Specifying an email is completely optional. If an email element exists, then the text e... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.2.9 SubscriberData: Emergency Family Contacts | Inclusion of this element is optional. The vCard does not explicitly provide fields for this information. To support the representation of this information the vCard related construct is used. This type has a set of tokens explicitly defined in the vCard schema, however, only the types in Table 13 are valid within the ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.6.3 EmergencyCallData.SubscriberData: Complete Example | This clause provides an example of a complete PEMEA compliant EmergencyCallData.SubscriberData structure. <EmergencyCallData.SubscriberInfo xmlns="urn:ietf:params:xml:ns:EmergencyCallData" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:si="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"> <si:DataProviderRef... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.7 Additional-Data: EmergencyCallDataReference | The only valid additional-data element that shall be sent by reference is for caller information, contained in an EmergencyCallData.SubscriberInfo. Element Parameter PEMEA Presence Type Description EmergencyCall DataReference purpose Mandatory xs:token This value shall be set to "EmergencyCallData.SubscriberInfo". ref ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 13.8 provided-by: Complete Examples | The provided-by element is defined inside the PIDF-LO schema, it is therefore necessary to show the examples inside the geopriv structure in order to provide an example that validates. <geopriv xmlns="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:ecd="urn:ietf:params:xml:ns:Em... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14 Operating Procedures | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.1 Application Provider Operating Procedures | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.1.1 AP sending an EDS to the PSP | This clause defines the procedures for sending an emergencyDataSend message to a PSP: • Generate a unique message sequence (msgSeq) for the EDS. • Set the ttl value: - The value shall be set to 1 if the caller has indicated to the AP that they do not wish to roam beyond their home PSP area. - The value shall be set to ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.1.2 AP reach-back URI queries | This condition occurs when the AP has included an onCapSupportPost URI and an apMoreInformation element in the EDS. The PSAP uses the provided reach-back URIs to request further information about the call/caller from the AP: • The PSAP or tPSP receives the EDS message containing an onCapSupportPost URI and posts to thi... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.1.3 Call termination (ending) and URI invalidation | • AP shall invalidate URIs associated with caller data after a fixed period of time from a specific time X: - Unless the App explicitly notifies the AP that the call is still in progress: Location updates from the App to the AP are one example of how this may be achieved. - The time period shall not exceed more than ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.1.4 Call termination (ending) by the PSAP | This condition occurs when the AP has included an onClosePost URI in the EDS. The PSAP or tPSP uses the provided reach-back URIs to notify that the PSAP is ending the emergency communication: • The PSAP or tPSP receives the EDS message containing an onClosePost URI and posts to this URI when the PSAP ends the emergency... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.2 PSAP Service Provider Operating Procedures | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.2.1 PSP receiving an EDS message over Ps | This clause provides the PSP procedures when receiving an emergencyDataSend message from an AP: • The AP is authenticated: - If the AP fails authentication then an HTTP 403 "Forbidden" response is returned. • If the ttl value is less than one then an error is returned to the AP with a reason code of ttlExhausted. • If ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.2.2 PSP sending an EDS message over Pr | The PSP has received an EDS from an AP: • Send an EDS to an ASP: - Decrement the ttl value in the EDS received from the AP. - Add a <hop> to the <hops> element in the <route> element. - The new hop shall have a timeStamp value set to the time that the hop is added. - The new hop shall have position="1". - The new hop s... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.2.3 PSP receiving an EDS message over Pr | This clause provides the PSP procedures when receiving an emergencyDataSend message from an ASP: • The ASP is authenticated. • If the ASP fails authentication then an HTTP 403 "Forbidden" response is returned. • If the ttl value is less than one then an error is returned to the ASP with a reason code of ttlExhausted. •... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.2.4 Call termination (ending) by the caller | This clause provides the PSP the procedures to follow when the AP communicates to the PSP that the caller is ending the emergency communication. This can only be done if the EDS contains the subscribeClosePost attribute. • If the PSP receives an HTTP request to the URI provided to the AP in the subscribeClosePost reque... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.2.5 Call termination (ending) by the PSAP | This clause provides the PSP the procedures to follow when the PSAP communicates to the PSP that the PSAP is ending the emergency communication: • If the EDS contains an onClosePost URI the PSP shall: - Make an HTTP POST request with an empty body to the onClosePost URI contained in the EDS. - End the communication and... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.3 Aggregating Service Provider Operating Procedures | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.3.1 Overview of Pr | The aggregating service provider has two distinct interfaces, a receiving Pr interface on which it receives EDS messages from an oPSP or ASP, and a sending Pr interface on which it sends EDS messages to a tPSP or subsequent ASP. |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.3.2 ASP receiving an EDS message over Pr | This clause the procedures for an ASP when receiving an emergencyDataSend message over the Pr interface: • If the ttl value is less than two then an error is returned to the sender with a reason code of ttlExhausted, a message may be included in the preferred language of the ASP. • If the ASP does not have a relationsh... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 14.3.3 ASP sending an EDS message over Pr | The ASP has received an EDS from an oPSP or ASP: • Sends an EDS to a tPSP or ASP: - Decrement the ttl value in the EDS received from the oPSP. - Add a <hop> to the <hops> element in the <route> element. - The new hop shall have a timeStamp value set to the time that the hop is added. - The new hop position of the next ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 15 Example message Flows | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 15.1 Description | The following flows provide the messages from an AP to the oPSP and from the oPSP to an ASP and from the ASP to a tPSP. |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 15.2 AP to PSP EDS | <emergencyDataSend xmlns="urn:pemea:apps:xml:ns:pemea:base" xmlns:pdf="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:con="urn:ietf:params:xml:ns:geopriv:conf" xmlns:pi="urn:ietf:params:xml:ns:Emerge... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 15.3 oPSP to AP EDR | The oPSP determines that it needs the services of an ASP. It adds its address to the route, and marks the destination as being an ASP, along with the address of the ASP. <emergencyDataReceived xmlns="urn:pemea:apps:xml:ns:pemea:base" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:pemea="urn:pemea:apps:xml:ns:pemea:b... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 15.4 oPSP to ASP EDS | oPSP decrements ttl and adds its address to the route element. <emergencyDataSend xmlns="urn:pemea:apps:xml:ns:pemea:base" xmlns:pdf="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:con="urn:ietf:para... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 15.5 ASP to oPSP EDR | The ASP determines the tPSP. It adds its address to the route, and marks the destination as being a PSP, along with the address of the tPSP. <emergencyDataReceived xmlns="urn:pemea:apps:xml:ns:pemea:base" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:pemea="urn:pemea:apps:xml:ns:pemea:base" timeStamp="2016-02-02T18... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 15.6 ASP to tPSP EDS | The ASP determines the tPSP, decrements the ttl, adds its address to the route and sends the EDS to the tPSP. <emergencyDataSend xmlns="urn:pemea:apps:xml:ns:pemea:base" xmlns:pdf="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.o... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 15.7 tPSP to ASP EDR | The tPSP determines the correct PSAP. It adds its address to the route, and marks the destination as being a PSAP, along with the name of the PSAP. The example illustrates the name of the PSAP in the delivery element, this could also be a URI that provides a means to contact the PSAP. <emergencyDataReceived xmlns="urn:... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 16 PEMEA Schema | <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:pemea:apps:xml:ns:pemea:base" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:pemea="urn:pemea:apps:xml:ns:pemea:base" xmlns:cell="urn:ietf:params:xml:ns:geopriv:lm:cell" xmlns:wifi="urn:ietf:params:xml:ns:geopriv:lm:wifi" xmlns:xml="http://www.w3... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17 PEMEA Callback | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.1 Overview | During the resolution of an emergency, it is common for the PSAP to want to contact back a citizen who has previously made an emergency communication. If it is an emergency communication that has been made using PEMEA, the MSISDN could be used to callback the caller, but this would only work if an MSISDN has been sent ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.2 Service support indication and response | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.2.1 Service definition | Clause 17 provides a concrete definition of the "Callback" capability in PEMEA. Clause 10.3.11 of the present document presents a list with the capabilities available currently in PEMEA. It is an extensible list that may be extended with PEMEA capability extensions. The "Callback" capability described in clause 17 of t... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.2.2 Service support indication | An AP willing to indicate that the Application it is serving can support the "Callback" capability using the PEMEA protocol would include the following information element in the apMoreInformation element of the EDS associated with the emergency session: <information typeOfInfo="Callback" protocol="PEMEA"> https://cool... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.2.3 Service support response | A terminating node that can support the "Callback" capability using the PEMEA protocol includes this capability in the apMoreInformation element returned to the AP in the onCapSupportPost, as defined in clause 11.1.4: <apMoreInformation xmlns="urn:pemea:apps:xml:ns:pemea:base"/> <information typeOfInfo="Callback" proto... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.3 Procedures and signalling | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.3.1 Overview | Once an EDS arrives at a terminating PSP entity that accepts it, the terminating PSP shall send an apMoreInformation message to the URI provided by the AP in the onCapSupportPost element of the EDS. If the PEMEA Callback capability is supported by both the AP and the terminating entity, the message shall contain the st... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.3.2 Service invocation | Once the EDS has been received at the terminating PSP and it has determined that the Callback capability is supported by both the AP and the terminating PSP, the terminating PSP shall send an HTTP POST message to the URI sent by the AP for the PEMEA Callback capability in the apMoreInformation attribute of the EDS that... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 17.3.3 Callback operation | When the PSAP wants to start a callback with a PEMEA App that supports the PEMEA Callback capability as described in clause 17.2, the PSAP shall instruct the terminating PSP to send an empty HTTP POST request to the URI provided by the AP in the service invocation operation described in clause 17.3.2. Once the AP recei... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 1 Scope | The present document specifies an extension to the E-AC-3 codec. The extension adds an object-based three-dimensional spatial representation of coded audio information and metadata. It is backward compatible with the one- and two-dimensional channel-based spatial representation of coded audio information as defined in ... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 2 References | |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 2.1 Normative References | References are either specific (identified by date of publication and/or edition number or version number) or non- specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents that a... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 2.2 Informative References | References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks in... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 3.1 Terms | For the purposes of the present document, the following terms apply: audio channel: data representing an audio signal designated to a dedicated speaker position audio definition model: metadata model describing format and content of audio files, specified in Recommendation ITU-R BS.2076 [i.1] audio object: data represe... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: ⌈x⌉ round x towards plus infinity ⌊x⌋ round x towards minus infinity i the imaginary unit ETSI ETSI TS 103 420 V1.2.1 (2018-10) 13 |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADM Audio Definition Model CMAF Common Media Application Format DASH Dynamic Adaptive Streaming over HTTP E-AC-3 Enhanced AC-3 EMDF Extensible Metadata Delivery Format HH Hours HTTP HyperText Transfer Protocol IDX Index ISF Intermediate Spatia... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 3.4 Conventions | Unless otherwise stated, the following conventions are used in the present document. Typographic conventions: • Italic font denotes variables (n is a variable) • Monospace font denotes bitstream elements (bits is a bitstream element) Function prototypes can take scalars, vectors, or matrices as argument and operate ele... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 4 Object-based audio | |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 4.1 Introduction | OBA gives content creators more control over how content is rendered to loudspeakers in consumer homes. In channel-based audio coding, a set of tracks is implicitly assigned to specific loudspeakers by associating the set of tracks with a channel configuration. If the playback speaker configuration is different from th... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 4.2 Coordinate systems | |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 4.2.1 Room-anchored coordinate system | The room-anchored coordinate system is a left-handed Cartesian system normalized to the room cuboid. Coordinates are specified using three components: • The x component increases from x=0 at the left wall to x=1 at the right wall. • The y component increases from y=0 at the front wall to y=1 at the back wall. • The z c... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 4.2.2 Screen-anchored coordinate system | In this coordinate system, the physical location of an object at a given coordinate changes with screen size and screen location: • The x component increases from x=0 at the left screen edge to x=1 at the right screen edge. • The y component increases from y=0 at the front wall to y=1 at the back wall. • The z componen... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 4.2.3 Speaker-anchored system | In this system, the coordinates of the object are indicated by referring to a specific speaker, meaning the physical location of the object changes with the actual speaker placement. This system is typically used with objects contained in bed instances. NOTE: If there is no speaker at the referenced position, the physi... |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 4.3 Decoding of object-based audio content | OBA content is signalled using a specific configuration of the E-AC-3 bitstream. The decoder shall decode the incoming OBA content as specified in the present document, if the following requirements are met: • The metadata payloads of JOC and OAMD are present as specified in clause 8.2. • The incoming channel configura... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.