Section: 9.9.3.37A Extended emergency number list
Content: The purpose of this information element is to encode one or more local emergency number(s) together with a sub-services field containing zero or more sub-services of the associated emergency service URN and a validity indication. An emergency service URN is a service URN with top level service type of "sos" as specified in IETF RFC 5031 [55]. EXAMPLE 1: If the associated emergency service URN is "urn:service:sos.gas", there is only one sub-service provided in the sub-services field which is "gas". EXAMPLE 2: If the associated emergency service URN is "urn:service:sos", there is no sub-services provided in the sub-services field and the length of the sub-services field is "0". NOTE: The associated emergency service URN can be a country-specific emergency service URN as defined in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [13D]. The Extended emergency number list information element is coded as shown in figure 9.9.3.37A.1 and table 9.9.3.37A.1. The Extended emergency number list IE is a type 6 information element with a minimum length of 7 octets and a maximum length of 65538 octets. NOTE 1: The length shall contain the number of octets used to encode the number digits. NOTE 2: The number digit(s) in octet 6 precedes the digit(s) in octet 7 etc. The number digit, which would be entered first, is located in octet 6, bits 1 to 4. The contents of the number digits are coded as shown in table 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ]  [13]. NOTE 3: If the emergency number contains an odd number of digits, bits 5 to 8 of the last octet of the respective emergency number shall be filled with an end mark coded as "1111". NOTE 4: The length shall contain the number of octets used to encode the sub-services field. NOTE 5: The characters of the sub-services of the associated emergency service URN shall be coded in accordance to GSM 7 bit default alphabet and the appropriate padding characters and bit-fill are added to octet boundary as specified in clause 6.1.2.3.1 of 3GPP TS 23.038[ Alphabets and language-specific information ]  [3]and the first character starts in octet j+1, l+1 or n+1. Figure 9.9.3.37A.1 Extended Emergency Number List IE EXAMPLE 3: If the associated emergency service URN is "urn:service:sos.police.municipal", the sub-services field contains "police.municipal" and the first character is "p". Table 9.9.3.37A.1: Extended Emergency Number List Validity information IE