name: 3GPP TS 23.038
full_form: 3GPP Technical Specification 23.038
context: 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Â [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Â [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Â [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
description: Specifies the format of sub-services fields in emergency service URNs.
explanation: Categorized as a Specification because it outlines key technical requirements and standards for sub-services fields.
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message
biotag_Description: O,O,O,O,O,O,O,O,O,O