Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 31.102  Word version:  18.5.0

Top   Top   Up   Prev   Next
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.4.11.17…   4.4.12…   4.5…   4.6…   4.6.5…   4.6.6…   4.7   5…   5.2…   5.3…   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M…

 

4.2.68  EFEXT8 (Extension 8) |R4|p. 82

If service No. 53 is "available", this file shall be present.
This EF contains extension data of a MMS Notification (Multimedia Messaging Service - see clause 4.2.67).
Identifier: '6FCF'Structure: linear fixedOptional
Record length: X+2 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Record typeM1 byte
2 to X+1Extension dataMX bytes
X+2IdentifierM1 byte
The structure of this EF is identical to the structure of EFEXT1 (see clause 4.4.2.4).
Record type
Contents:
type of the record, see clause 4.4.2.4
Coding:
according to the "additional data" type
Extension data
Contents:
additional data (MMS notification extension)
Coding:
the first byte of the extension data gives the number of bytes of the remainder of the MMS notification in this record. The following bytes contain the extension of the MMS notification.
Identifier
Contents:
identifier of the next extension record (in EXT8) to enable longer storage of information.
Coding:
record number of next record. 'FF' identifies the end of the chain.
Up

4.2.69  EFMMSICP (MMS Issuer Connectivity Parameters) |R4|p. 83

If service No. 52 is "available", this file shall be present.
This EF contains values for Multimedia Messaging Connectivity Parameters as determined by the issuer, which can be used by the ME for MMS network connection. This file may contain one or more sets of Multimedia Messaging Issuer Connectivity Parameters. The first set of Multimedia Messaging Issuer Connectivity Parameters is used as the default set. Each set of Multimedia Messaging Issuer Connectivity Parameters may consist of one or more Interface to Core Network and Bearer information TLV objects, but shall contain only one MMS implementation TLV object, one MMS Relay/Server TLV object and one Gateway TLV object. The order of the Interface to Core Network and Bearer information TLV objects in the MMS Connectivity TLV object defines the priority of the Interface to Core Network and Bearer information, with the first TLV object having the highest priority.
Identifier: '6FD0'Structure: TransparentOptional
File Size: X1+…+ Xn bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to X1MMS Connectivity Parameters TLV objectMX1 bytes
X1+1 to X1 + X2MMS Connectivity Parameters TLV objectOX2 bytes
X1+…+ Xn-1+1 to X1+…+ XnMMS Connectivity Parameters TLV objectOXn bytes
Description Tag Value
MMS Connectivity Parameters Tag'AB'
MMS Implementation Tag
'80'
MMS Relay/Server Tag'81'
Interface to Core Network and Bearer Information Tag'82'
GatewayTag'83'
Reserved for 3GPP2: MMS Authentication Mechanism Tag'84'
Reserved for 3GPP2: MMS Authentication User Name Tag'85'
 
MMS Connectivity Parameters contents
Description Value M/O Length (bytes)
MMS Connectivity Parameters Tag'AB'M1
LengthNote 1MNote 2
MMS Implementation Tag'80'M1
Length1M1
MMS Implementation Information--M1
MMS Relay/Server Tag'81'M1
LengthX1MNote 2
MMS Relay/Server Address--MX1
MMS Authentication Mechanism Tag'84'C11
LengthX2C1Note 2
MMS Authentication Mechanism--C1X2
MMS Authentication User Name Tag'85'C11
LengthX3C1Note 2
MMS Authentication User Name--C1X3
1st Interface to Core Network and Bearer Information Tag (highest priority)'82'C21
LengthY1C2Note 2
1st Interface to Core Network and Bearer information--C2Y1
2nd Interface to Core Network and Bearer Information Tag'82'C21
LengthY2C2Note 2
2nd Interface to Core Network and Bearer information--C2Y2
Nth Interface to Core Network and Bearer Information Tag (lowest priority)'82'C21
LengthY3C2Note 2
Nth Interface to Core Network and Bearer information--C2Y3
GatewayTag'83'O1
LengthZONote 2
Gateway Information--OZ
NOTE 1:
This is the total size of the constructed TLV object.
NOTE 2:
The length is coded according to ISO/IEC 8825-1 [35].
C1:
Reserved for 3GPP2: only present if M-IMAP or SIP indicated in tag 80.
C2:
Only present if WAP is indicated in tag 80.
 
MMS Implementation Tag '80'
See clause 4.2.67 for contents and coding.
MMS Relay/server Tag '81'
Contents:
The MMS relay/server contains the address of the associated MMS relay/server.
Coding:
The MMS relay/server address is coded according to the guideline provided in TS 23.140.
MMS Authentication Mechanism Tag '84'
Contents:
The MMS authentication mechanism contains the authentication mechanism used for M-IMAP and SIP.
Coding:
The MMS authentication mechanism is coded according to the guidelines provided in X.S0016-000-A v1.0 [45].
MMS Authentication User Name Tag '85'
Contents:
The MMS Authentication User Name contains the authentication user name used for M-IMAP and SIP.
Coding:
The MMS authentication User Name is coded according to the guidelines provided in X.S0016-000-A v1.0 [45].
Interface to Core Network and Bearer Information Tag '82'
Contents:
The Interface to Core Network and Bearer Information may contain the following information to set up the bearer: Bearer, Address, Type of address, Speed, Call type, Authentication type, Authentication id, Authentication password.
Coding:
The coding is according to the guideline provided in TS 23.140.
Gateway Tag '83'
Contents:
The Gateway may contain the following information; Address, Type of address, Port, Service, Authentication type, Authentication id and Authentication password.
Coding:
The coding is according to the guideline provided in TS 23.140.
Unused bytes shall be set to 'FF'.
 
An Example for the coding of these parameters can be found in clause J.2.
Up

4.2.70  EFMMSUP (MMS User Preferences) |R4|p. 85

If service No. 52 is "available", this file shall be present.
This EF contains values for Multimedia Messaging Service User Preferences, which can be used by the ME for user assistance in preparation of mobile multimedia messages (e.g. default values for parameters that are often used).
Identifier: '6FD1'Structure: Linear FixedOptional
Record Length: X bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XMMS User Preference TLV ObjectsMX bytes
MMS User Preference tags
Description Tag Value
MMS Implementation Tag'80'
MMS User preference profile name Tag'81'
MMS User Preference information Tag'82'
 
MMS User Preference information
Description Value M/O Length (bytes)
MMS Implementation Tag'80'M1
Length1MNote
MMS Implementation information--M1
MMS User preference profile name Tag'81'M1
LengthXMNote
MMS User profile name--MX
MMS User Preference information Tag'82'M1
LengthYMNote
MMS User Preference information--MY
NOTE:
The length is coded according to ISO/IEC 8825-1 [35].
 
MMS Implementation Tag '80'
For contents and coding see clause 4.2.67
MMS User preference profile name Tag '81'
Contents:
Alpha tagging of the MMS user preference profile.
Coding:
this alpha-tagging shall use
either:
  • the SMS default 7-bit coded alphabet as defined in TS 23.038 with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to 'FF'.
or
MMS User Preference information Tag '82'
Contents:
The following information elements may be coded; Sender Visibility, Delivery Report, Read-Reply, Priority, Time of Expiry and Earliest Delivery Time.
Coding:
Depending upon the MMS implementation as indicated in Tag '80'.
An Example for the coding of these parameters can be found in clause J.1.
Up

4.2.71  EFMMSUCP (MMS User Connectivity Parameters) |R4|p. 86

If service No. 52 and No. 55 are "available", this file shall be present.
This EF contains values for Multimedia Messaging Connectivity Parameters as determined by the user, which can be used by the ME for MMS network connection. This file may contain one or more sets of Multimedia Messaging User Connectivity Parameters. Each set of Multimedia Messaging User Connectivity Parameters may consist of one or more Interface to Core Network and Bearer information TLV objects, but shall contain only one MMS implementation TLV object, one MMS Relay/Server TLV object and one Gateway TLV object. The order of the Interface to Core Network and Bearer information TLV objects in the MMS Connectivity TLV object defines the priority of the Interface to Core Network and Bearer information, with the first TLV object having the highest priority.
Identifier: '6FD2'Structure: TransparentOptional
File Size: X1+…+ Xn bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN/PIN2 (fixed during administrative management)
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to X1MMS Connectivity Parameters TLV objectOX1 bytes
X1+1 to X1 + X2MMS Connectivity Parameters TLV objectOX2 bytes
X1+…+ Xn-1+1 to X1+…+ XnMMS Connectivity Parameters TLV objectOXn bytes
For the contents and coding see clause 4.2.69
Up

4.2.72  EFNIA (Network's Indication of Alerting) |R4|p. 86

If service No. 56 is "available", this file shall be present.
This EF contains categories and associated text related to the Network's indication of alerting in the MS service defined in TS 22.101.
Identifier: '6FD3'Structure: linear fixedOptional
Record length : X+1 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Alerting categoryM1 byte
2 to X+1Informative textMX bytes
Alerting category
Contents:
category of alerting for terminating traffic.
Coding:
according to TS 24.008. Value 'FF' means that no information on alerting category is available.
Informative text
Contents:
text describing the type of terminating traffic associated with the category.
Coding:
see the coding of the Alpha Identifier item of the EFADN. The maximum number of characters for this informative text is indicated in TS 22.101.
Up

4.2.73  EFVGCS (Voice Group Call Service) |R4|p. 87

If service No. 57 is "available", this file shall be present.
This EF contains a list of those VGCS group identifiers the user has subscribed to. The elementary file is used by the ME for group call establishment and group call reception.
Identifier: '6FB1'Structure: transparentOptional
File size: 4n bytes, (1≤ n ≤ 50)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 4Group ID 1M4 bytes
5 to 8Group ID 2O4 bytes
(4n-3) to 4nGroup ID nO4 bytes
Group ID
Contents:
VGCS Group ID, according to TS 23.003
Coding:
The VGCS Group ID is of a variable length with a maximum length of 8 digits. Each VGCS Group ID is coded on four bytes, with each digit within the code being coded on four bits corresponding to BCD code. If a VGCS Group ID of less than 8 digits is chosen, then the unused nibbles shall be set to 'F'. VGCS Group ID Digit 1 is the most significant digit of the Group ID.
 
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 2 of Group ID 1 LSB of Digit 2 of Group ID 1 MSB of Digit 1 of Group ID 1 LSB of Digit 1 of Group ID 1
 
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 4 of Group ID 1 LSB of Digit 4 of Group ID 1 MSB of Digit 3 of Group ID 1 LSB of Digit 3 of Group ID 1
 
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 6 of Group ID 1 LSB of Digit 6 of Group ID 1 MSB of Digit 5 of Group ID 1 LSB of Digit 5 of Group ID 1
 
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 8 of Group ID 1 LSB of Digit 8 of Group ID 1 MSB of Digit 7 of Group ID 1 LSB of Digit 7 of Group ID 1
 
:
: etc........
Byte (4n-3) to 4n:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 8 of Group ID n LSB of Digit 8 of Group ID n MSB of Digit 7 of Group ID n LSB of Digit 7 of Group ID n
 
If storage for fewer than the maximum possible number n of VGCS Group Ids, is required, the excess bytes shall be set to 'FF'.
Up

4.2.74  EFVGCSS (Voice Group Call Service Status) |R4|p. 89

If service No. 57 is "available", this file shall be present.
This EF contains the status of activation for the VGCS group identifiers. The elementary file is directly related to the EFVGCS. This EF shall always be allocated if EFVGCS is allocated.
Identifier: '6FB2'Structure: transparentOptional
File size: 7 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN/ADM (fixed during administrative management)
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 7Activation/Deactivation FlagsM7 bytes
Activation/Deactivation Flags
Contents:
Activation/Deactivation Flags of the appropriate Group Ids
Coding:
bit = 0 means - Group ID deactivated
bit = 1 means - Group ID activated
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
Group ID 8 Group ID 1
 
etc.
 
Byte 7:
b8 b7 b6 b5 b4 b3 b2 b1
b8=1 b7=1 b6=1 b5=1 b4=1 b3=1 Group ID 50 Group ID 49
Up

4.2.75  EFVBS (Voice Broadcast Service) |R4|p. 89

If service No. 58 is "available", this file shall be present.
This EF contains a list of those VBS group identifiers the user has subscribed to. The elementary file is used by the ME for broadcast call establishment and broadcast call reception.
Identifier: '6FB3'Structure: transparentOptional
File size: 4n bytes, (1 ≤ n ≤ 50)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 4Group ID 1M4 bytes
5 to 2Group ID 2O4 bytes
(4n-3) to 4nGroup ID nO4 bytes
Group ID
Contents:
VBS Group ID, according to TS 23.003
Coding:
The VBS Group ID is of a variable length with a maximum length of 8 digits. Each VBS Group ID is coded on four bytes, with each digit within the code being coded on four bits corresponding to BCD code. If a VBS Group ID of less than 8 digits is chosen, then the unused nibbles shall be set to 'F'. VBS Group ID Digit 1 is the most significant digit of the Group ID.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 2 of Group ID 1 LSB of Digit 2 of Group ID 1 MSB of Digit 1 of Group ID 1 LSB of Digit 1 of Group ID 1
 
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 4 of Group ID 1 LSB of Digit 4 of Group ID 1 MSB of Digit 3 of Group ID 1 LSB of Digit 3 of Group ID 1
 
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 6 of Group ID 1 LSB of Digit 6 of Group ID 1 MSB of Digit 5 of Group ID 1 LSB of Digit 5 of Group ID 1
 
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 8 of Group ID 1 LSB of Digit 8 of Group ID 1 MSB of Digit 7 of Group ID 1 LSB of Digit 7 of Group ID 1
 
etc.
 
Byte (4n-3) to 4n:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 8 of Group ID n LSB of Digit 8 of Group ID n MSB of Digit 7 of Group ID n LSB of Digit 7 of Group ID n
 
If storage for fewer than the maximum possible number n of VBS Group Ids, is required, the excess bytes shall be set to 'FF'.
Up

Up   Top   ToC