6 Specification with the binary option
29.3643GPPIP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperabilityRelease 17TS
6.1 MMTEL service sontent with the binary option
6.1.1 List of IMS Multimedia Telephony supplementary services
This list of MMTEL services refers to the list identified in 3GPP TS 22.173 [1] and mentions the associated 3GPP Technical Specifications:
Originating Identification Presentation (OIP) 3GPP TS 24.607 [5]
Originating Identification Restriction (OIR) 3GPP TS 24.607 [5]
Terminating Identification Presentation (TIP) 3GPP TS 24.608 [6]
Terminating Identification Restriction (TIR) 3GPP TS 24.608 [6]
Malicious Communication IDentification (MCID) 3GPP TS 24.616 [10]
Anonymous Communication Rejection (ACR) 3GPP TS 24.611 [8]
Communication DIVersion (CDIV) 3GPP TS 24.604 [2]
Communication Waiting (CW) 3GPP TS 24.615 [9]
Communication HOLD (HOLD) 3GPP TS 24.610 [7]
Communication Barring (CB) 3GPP TS 24.611 [8]
Completion of Communications to Busy Subscriber (CCBS) 3GPP TS 24.642 [12]
Completion of Communications on No Reply (CCNR) 3GPP TS 24.642 [12]
Message Waiting Indication (MWI) 3GPP TS 24.606 [4]
CONFerence (CONF) 3GPP TS 24.605 [3]
Advice Of Charge (AOC) 3GPP TS 24.647 [13]
Explicit Communication Transfer (ECT) 3GPP TS 24.629 [11]
Reverse charging
Closed User Group (CUG) 3GPP TS 24.654 [14]
Three-Party (3PTY) 3GPP TS 24.605 [5]
Flexible Alerting (FA) 3GPP TS 24.239 [15]
Customized Alerting Tones (CAT) 3GPP TS 24.182 [21]
This list is taken as the reference to address the services and their content that the binary option shall support.
6.1.2 Subset of MMTEL services matching PSTN/ISDN and CS supplementary services
The binary option shall support the subset of MMTEL services matching PSTN/ISDN and CS supplementary services.
The following subclauses indicate:
– for each MMTEL Service how it matches the corresponding PSTN/ISDN and CS supplementary service,
– the relevant information elements of the service as defined in 3GPP TS 22.173 [1] and 3GPP TS 24.6xxx series and that shall be coded in the Service Data.
6.1.2.1 Originating Identification Presentation (OIP)
OIP is described in 3GPP TS 24.607 [5] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated
– Override Capability.
6.1.2.2 Originating Identification Restriction (OIR)
OIR is described in 3GPP TS 24.607 [5] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated
– Mode: permanent mode; temporary mode
– Temporary mode default: presentation restricted; presentation not restricted
– Restriction: restrict the asserted identity; restrict all private information appearing in headers.
6.1.2.3 Terminating Identification Presentation (TIP)
TIP is described in 3GPP TS 24.608 [6] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated
– Override Capability.
6.1.2.4 Terminating Identification Restriction (TIR)
TIR is described in 3GPP TS 24.608 [6] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated
– Mode: permanent mode; temporary mode
– Temporary mode default: presentation restricted; presentation not restricted.
6.1.2.5 Malicious Communication IDentification (MCID)
MCID is described in 3GPP TS 24.616 [10] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated
– Mode: permanent mode; temporary mode.
6.1.2.6 Anonymous Communication Rejection (ACR)
ACR is described in 3GPP TS 24.611 [8] and matches the corresponding PSTN/ISDN and CS supplementary service.
ACR is identified as a supplementary service in 3GPP TS 22.173 [1]. Its stage 3 specification is a special case of the incoming Communication Barring (ICB) service (c.f. subclause 4.2.1 of 3GPP TS 24.611 [8]).
– Information elements
– Service Authorized
– Service Activated
6.1.2.7 Communication DIVersion (CDIV)
CDIV is described in 3GPP TS 24.604 [2]
Subclause 8.2.7.1 in 3GPP TS 22.173 [1] defines the following Communication DIVersion services:
– Communication Forwarding Unconditional (CFU)
– Communication Forwarding Busy (CFB)
– Communication Forwarding No Reply (CFNR)
– Communication Forwarding on Not Logged in (CFNL)
– Communication Deflection (CD)
– Communication Forwarding on Subscriber Not Reachable (CFNRc)
The service content matching PSTN/ISDN and CS supplementary services and supported by the binary option is hereafter described for each of the CDIV services.
6.1.2.7.1 Subscription options for CDIV services
3GPP TS 24.604 [2] Table 4.3.1.1 describes the following subscription options:
Table 6.1.2.7.1-1: Subscription options for CDIV services
|
Subscription options |
Value |
Applicability |
|
Served user receives indication that a communication has been forwarded (indication of communication diversion to the diverting user). |
No (default) Yes |
CFU CFNRc |
|
Originating user receives notification that his communication has been diverted (forwarded or deflected). |
No Yes (default) |
CFU CFNRc |
|
Served user allows the presentation of diverted to URI to originating user in diversion notification. |
No Not reveal as GRUU Yes (default) |
CFU CFNRc |
|
Served user receives reminder indication on outgoing communication that CDIV is currently activated. |
No (default) Yes |
CFU CFNRc |
|
Served user allows the presentation of his/her URI to diverted‑to user. |
No Not reveal as GRUU Yes (default) |
CFU CFNRc |
|
Served user allows the presentation of his/her URI to originating user in diversion notification. |
No Not reveal as GRUU Yes (default) |
CFU CFNRc |
PSTN/ISDN and CS Call forwarding services have similar subscription options.
6.1.2.7.2 Communication Forwarding Unconditional (CFU)
CFU fulfils the corresponding PSTN/ISDN and CS supplementary service, taking into account that the communication diversion rule conditions described in 3GPP TS 24.604 [2] subclause 4.9.1.3 shall not be used.
– Information elements
– Service Authorized
– Service Activated
– Diverted-to destination
– Subscription options for CFU.
6.1.2.7.3 Communication Forwarding Busy (CFB)
To fulfil the corresponding PSTN/ISDN and CS supplementary service, only the busy condition among the communication diversion rule conditions described in 3GPP TS 24.604 [2] subclause 4.9.1.3 is used.
– Information elements
– Service Authorized
– Service Activated
– Diverted-to destination: A SIP URI or a TEL URI
– Subscription options for CFB.
6.1.2.7.4 Communication Forwarding No Reply (CFNR)
To fulfil the corresponding PSTN/ISDN and CS supplementary service, only the no-answer condition among the communication diversion rule conditions described in 3GPP TS 24.604 [2] subclause 4.9.1.3 is used.
– Information elements
– Service Authorized
– Service Activated
– Diverted-to destination: A SIP URI or a TEL URI
– Subscription options for CFNR.
– Communication forwarding on no reply timer : Timer duration is a network provider option.
6.1.2.7.5 Communication Forwarding on Not Logged in (CFNL)
To fulfil the corresponding CS supplementary service, only the not-registered condition among the communication diversion rule conditions described in 3GPP TS 24.604 [2] subclause 4.9.1.3 is used.
– Information elements
– Service Authorized
– Service Activated
– Diverted-to destination: A SIP URI or a TEL URI
– Subscription options for CFNL.
6.1.2.7.6 Communication Deflection (CD)
CD matches the corresponding PSTN/ISDN supplementary service.
– Information elements
– Service Authorized
– Service Activated
– Subscription options for CD.
6.1.2.7.7 Communication Forwarding on Subscriber Not Reachable (CFNRc)
To fulfil the corresponding CS supplementary service, only the not-reachable condition among the communication diversion rule conditions described in 3GPP TS 24.604 [2] subclause 4.9.1.3 is used.
– Information elements
– Service Authorized
– Service Activated
– Diverted-to destination: A SIP URI or a TEL URI.
– Subscription options for CFNRc.
6.1.2.7.8 Void
6.1.2.7.9 Network provider options for CDIV services
The network provider options for CDIV services supported with the binary option are those described in 3GPP TS 24.604 [2] Table 4.3.1.2.
6.1.2.8 Communication Waiting (CW)
CW is described in 3GPP TS 24.615 [9] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated
– Subscription option: Served user subscribes to "calling user receives notification that his call is waiting".
6.1.2.9 Communication HOLD (HOLD)
HOLD is described in 3GPP TS 24.610 [7] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated.
6.1.2.10 Communication Barring (CB)
CB is described in 3GPP TS 24.611 [8] and comprises 2 services: Incoming Communication Barring (ICB) and Outgoing Communication Barring (OCB).
CB partially matches the corresponding PSTN/ISDN and CS Call Barring supplementary service. As no one of the communication barring rule conditions described in 3GPP TS 24.611 [8] subclause 4.9.1.4 applies to the corresponding PSTN/ISDN and CS Call Barring service, ICB applies to all incoming communications and OCB applies to all outgoing communications.
– Information elements for ICB
– Service Authorized
– Service Activated.
– Information elements for OCB
– Service Authorized
– Service Activated.
6.1.2.11 Completion of Communications to Busy Subscriber (CCBS)
CCBS is described in 3GPP TS 24.642 [12] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated.
6.1.2.12 Completion of Communications on No Reply (CCNR)
CCNR is described in 3GPP TS 24.642 [12] and matches the corresponding PSTN/ISDN and CS supplementary service.
Information elements
– Service Authorized
– Service Activated.
6.1.2.13 Message Waiting Indication (MWI)
MWI is described in 3GPP TS 24.606 [4] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated.
6.1.2.14 CONFerence (CONF)
CONF is described in 3GPP TS 24.605 [3] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated.
6.1.2.15 Advice Of Charge (AOC)
AOC is described in 3GPP TS 32.280 [22] and in 3GPP TS 24.647 [13] . Itcomprises 3 services AOC-S, AOC-D, AOC-E.
AOC matches the corresponding PSTN/ISDN and CS service.
– Information elements
– Service Authorized (for each service AOC-S, AOC-D, AOC-E)
– Service Activated (for each service AOC-S, AOC-D, AOC-E).
– AOC service type: as described in 3GPP TS 32.280 [22]
– AOC service obligatory type: as described in 3GPP TS 32.280 [22]
– Preferred AOC currency: as described in 3GPP TS 32.280 [22]
– AOC format: as described in 3GPP TS 32.280 [22]
6.1.2.16 Explicit Communication Transfer (ECT)
ECT is described in 3GPP TS 24.629 [11] and matches the corresponding PSTN/ISDN and CS supplementary service.
– Information elements
– Service Authorized
– Service Activated.
6.1.2.17 Reverse Charging
Reverse charging for the binary option is not supported in this release.
6.1.2.18 Closed User Group (CUG)
CUG is described in 3GPP TS 24.654 [14].
CUG for the binary option is not supported in this release.
6.1.2.19 Three-Party (3PTY)
3PTY is described in 3GPP TS 24.605 [3] as a particular case of CONF service and matches the corresponding PSTN/ISDN and CS supplementary service.
6.1.2.20 Flexible Alerting (FA)
FA is described in 3GPP TS 24.239 [15].
– Information elements for the FA Pilot of a FA group
– Service Authorized
– Service Activated.
– Single user, Multiple users: as described in 3GPP TS 24.239 [15]
– Pilot/Member status: states if the FA Pilot identity is also a FA Member identity
– Membership: Demand or Permanent as described in 3GPP TS 24.239 [15]
– List of FA Members identities
– Information elements for the FA member
– Service Authorized
– List of FA groups to which the FA member belongs to
– FA Member status: Active / Inactive on a per FA group basis
– Default FA groups for the FA member
6.1.2.21 Customized Alerting Tones (CAT)
CAT is described in 3GPP TS 24.182 [21] and matches the corresponding CS supplementary service.
– Information elements
– Service Authorized
– Service Activated.
6.2 Datasets and Service Indications
6.2.1 Introduction
The subclause 6.2 specifies the binary description of the service data of the subset of MMTEL service to be stored on the HSS and corresponding to the PSTN/ISDN and CS supplementary services. Care has been taken to define rules for extendibility, backward compatibility and compactness, since future data structures can evolve from this definition.
The Service Data contained in the Repository Data of one Service Indication may be a complete service suite definition, or can be viewed as a portion of a service definition. The remaining portion of a service definition may be comprised of elements specific to a subsequent part of the standardised service or a later addition of elements due to new functionalities of a service in a new release, or proprietary extensions.
To ensure these possibilities, Service Data for the binary option are grouped in a certain number of binary datasets hereafter presented.
6.2.2 Datasets
The structure of datasets described in subclause 6.3.2 allows to define different types of datasets. In this release, the following datasets are defined:
– the MMTELPSTN-ISDN-CS dataset containing parameters associated to the subset of MMTEL services matching the PSTN/ISDN and CS supplementary services.
– the AOC dataset containing parameters for the AOC service,
– the FA pilot dataset containing parameters of the FA pilot in the FA service,
– the FA member dataset containing parameters of the FA member in the FA service.
Additional services (e.g. new MMTEL services or proprietary MMTEL services) may be defined using new datasets.
6.2.3 Service Indications
Dedicated Service Indications shall be used within the binary option for the subset of MMTEL services corresponding to the PSTN/ISDN and CS supplementary services.
The Service indication with the value "MMTEL-PSTN-ISDN-CS-BINARY" shall have a Service Data field containing:
– the MMTEL-PSTN-ISDN-CS dataset.
– the AOC dataset when the AOC service is configured for the user.
The Service indication with the value "MMTEL-EXTENSION-BINARY-1" shall be used when the FA service is configured for a user and shall have a Service Data field containing the FA dataset.
New Service Indications can be introduced in the future and associated to new types of datasets.
Proprietary extensions shall use not standardized Service Indications. There is no constraint for the data structure of the proprietary Service Data. Nevertheless, the concept of dataset can be used with a proprietary content.
6.3 Binary coding general
6.3.1 Introduction
The subclause6.3 gives the general specifications to describe the MMTEL Service data in a binary coding.
6.3.2 Dataset layout
The datasets are defined with a compact structure. The compact structure shall consist:
– of a tag-length-value format: this includes a defined ‘dataset identifier’ and ‘length’,
– followed by a fixed format structure, wherein defined bits, bytes, 4byte tuples represent known or reserved information elements of a MMTEL service,
– finally, to accommodate length variation of some data (e.g. SIP-URI), it accommodates a variable length section.
A dataset shall be 4-byte aligned.
Within a dataset structure, different common data forms are defined. These include some fairly standard terms and rules, derived from common practice for 32-bit processors:
Byte == octet
Long == 4 bytes (signed and unsigned)
Short == 2 bytes (signed, unsigned)
Data alignment is such that the size of the data set shall be a 4-byte multiple and be achieved with a padding feature at the end of the dataset.
Bit fields take up only the number of bits they say they do. Alignment of bit fields is not across a 4-byte boundary.
6.3.3 Order
Network byte ordering means most significant byte first.
Bit field order: Most significant bit first.
6.3.4 Character representation
Character representation uses UTF-8 representation.
String representations should be displayable.
6.3.5 Byte representation
Byte structures can be variable in length. They use the tag-length value approach, wherein the length defines the end of a variable length byte definition.
Variable byte structures interpreted as strings should not contain the null character.
If no variable length data were defined, then a dataset would have fixed length.
When there are variable length data, the dataset length will not remain constant from subscriber to subscriber, as each may have different variable length parameters.
6.3.6 Variable size data
Some data must remain flexibly defined regarding their length. Main example is strings, such as URIs, digit-strings, IMPUs.
The fixed format part of the dataset contains the information that is used when identifying variable length data described in the dataset. This information comprises:
– variable_data_offset (unsigned short ): byte offset from the dataset start
– variable_data_length (unsigned short ): number of bytes.
The variable_data_offset is the offset (in bytes) from the beginning of dataset to the beginning of a variable data. The variable_data_length determines the end of the variable data. A variable_data_offset of 0 indicates a non-provided sequence.
A specific dataset does not have a specific size, although it will at least have a minimum size (the size if no variable data are defined at all).
The offset plus the length information shall verify:
i. offset >= fixed size of the fixed part of the dataset (unless offset == 0), and
ii. offset+length <= total size of the dataset.
iii. there is no overlap between variable data.
6.3.7 Variable length data constraints
The following complements the usage of the pointer references (offset and length):
a) The order of variable data values in the variable section of the dataset shall match the order of the offset + length elements in the fixed section of the dataset. Offsets to data shall have increasing values in the order the offsets are encountered in the fixed portion of the dataset.
b) When the size of a variable length data field increases, the entire variable length section of the dataset must be realigned.
c) When there is no variable data associated to an offset data, the length shall be 0, and the offset shall have a value equal to the value of the next offset encountered in the fixed portion of the dataset.
d) If the same data value appears more than once in a given dataset, it shall not be implemented as two pointers to the same value.
e) Holes should not occur between variable data values.
If they do, then the AS is not responsible for maintaining the information in these holes and alternate ASs may remove them in subsequent write actions.
f) Space after the last variable data value is not significant, and may not be retained.
An example of a dataset with variable length data is given for information in Annex A.
6.4 Binary coding of datasets
6.4.1 Dataset Header
Each dataset shall start with a Dataset Header.
– DATASET_HEADER
Table 6.4.1-1: Dataset Header
|
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
|
dataset_identifier | dataset_length | |
– dataset_identifier
It differentiates the data sets contained in the Service Data of the same Service Indication. It identifies the data structure of the dataset.
– dataset_length
Length in bytes of the dataset including the DATASET_HEADER.
6.4.2 MMTEL-PSTN-ISDN-CS Dataset
6.4.2.1 MMTEL-PSTN-ISDN-CS Dataset content
Table 6.4.2.1-1: MMTEL-PSTN-ISDN-CS Dataset fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
0 |
DATASET_HEADER |
|
4 |
|
|
8 |
service_authorisation |
|
12 |
|
|
16 |
service_activation |
|
20 |
|
|
24 |
RESERVED |
|
28 |
identity_services_param |
|
32 |
|
|
36 |
CFU_param |
|
40 |
|
|
44 |
CFB_param |
|
48 |
|
|
52 |
CFNR_param |
|
56 |
|
|
60 |
CFNRc_param |
|
64 |
|
|
68 |
CFNL_param |
|
72 |
|
|
76 |
CD_param |
|
80 |
|
|
84 |
CDIV_network_provider_options |
|
88 |
CW_param |
|
92 |
|
|
96 |
ICB_param |
|
100 |
|
|
104 |
0CB_param |
|
108 |
|
|
112 |
RESERVED |
|
116 |
|
|
120 |
RESERVED |
|
124 |
|
|
Data with variable length |
|
|
n |
NOTE: ACR, HOLD, CCBS, CCNR, MWI, CONF, AOC, ECT, CAT have no parameter field.
6.4.2.2 Dataset Header
– dataset_identifier
The value of dataset_identifier of the MMTEL-PSTN-ISDN-CS Dataset is 1.
6.4.2.3 service_authorisation
Bit field that can support up to 64 services. A bit is associated to a MMTEL Service and indicates if:
– it is authorized: bit value 1,
– or not: bit value 0.
Bit-0 Reserved
Bit-1 OIP
Bit-2 OIR
Bit-3 TIP
Bit-4 TIR
Bit-5 MCID
Bit-6 ACR
Bit-7 CFU
Bit-8 CFB
Bit-9 CFNR
Bit-10 CFNRc
Bit-11 CFNL
Bit-12 CD
Bit-13 Reserved
Bit-14 CW
Bit-15 HOLD
Bit-16 Incoming CB
Bit-17 Outgoing CB
Bit-18 CCBS
Bit-19 CCNR
Bit-20 MWI
Bit-21 CONF
Bit-22 AOC-S
Bit-23 AOC-D
Bit-24 AOC-E
Bit-25 Reserved
Bit-26 Reserved
Bit-27 ECT
Bit-28 CAT
Bit-29 FA
6.4.2.4 service_activation
Bit field that can support up to 64 services. A bit is associated to a MMTEL Service and indicates if the MMTEL service is activated. Indexation is the same as for service_authorization.
6.4.2.5 identity_services_param
Table 6.4.2.5-1: identity_services_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
28 |
(a)|(b)|(c)|(d)|(e)|(f)|(g)|(h)|(i)| RESERVED | | | | | | | | | |
Table 6.4.2.5-2: identity_services_param values
|
Field |
Identity services Parameters |
Value |
Binary value |
|
|
(a) |
OIR mode |
Permanent mode |
Bit 31 0 0 |
Bit 30 0 1 |
|
(b) |
OIR Temporary Mode Default |
Presentation restricted |
Bit 29 0 0 |
Bit 28 0 1 |
|
(c) |
OIR restriction |
Restrict the asserted identity |
Bit 27 0 0 |
Bit 26 0 1 |
|
(d) |
OIP Override capability |
No |
Bit 25 0 0 |
Bit 24 0 1 |
|
(e) |
TIR Mode |
Permanent mode |
Bit 23 0 0 |
Bit 22 0 1 |
|
(f) |
TIR Temp Mode Default |
Presentation restricted |
Bit 21 0 0 |
Bit 20 0 1 |
|
(g) |
TIP Override capability |
No |
Bit 19 0 0 |
Bit 18 0 1 |
|
(h) |
Reserved |
|||
|
(i) |
MCID Mode |
Permanent |
Bit 15 0 0 |
Bit 14 0 1 |
6.4.2.6 CFU_param
Table 6.4.2.6-1: CFU_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
32 |
RESERVED |CFU_subscription_options |(a)|(b)|(c)|(d)|(e)|(f)|(g)|(h) |
|
36 |
CFU_divertedto_destination_ |CFU_divertedto_destination_ Offset |Length |
– CFU_divertedto_destination_offset is the pointer to CFU diverted-to destination in the variable part of the MMTEL-PSTN-ISDN-CS Dataset.
– CFU_subscription_options: described in subclause 6.4.2.12.
6.4.2.7 CFB_param
Table 6.4.2.7-1: CFB_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
40 |
RESERVED |CFB_subscription_options |(a)|(b)|(c)|(d)|(e)|(f)|(g)|(h) |
|
44 |
CFB_divertedto_destination_ |CFB_divertedto_destination_ Offset |Length |
– CFB_divertedto_destination_offset is the pointer to CFB diverted-to destination in the variable part of the MMTEL-PSTN-ISDN-CS Dataset.
– CFB_subscription_options: described in subclause 6.4.2.12.
6.4.2.8 CFNR_param
Table 6.4.2.8-1: CFNR_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
48 |
no_reply_timer |CFNR_subscription_options |(a)|(b)|(c)|(d)|(e)|(f)|(g)|(h) |
|
52 |
CFNR_divertedto_destination_ |CFNR_divertedto_destination_ Offset |Length |
– CFNR_divertedto_destination_offset is the pointer to CFNR diverted-to destination in the variable part of the MMTEL-PSTN-ISDN-CS Dataset.
– CFNR_subscription_options: described in subclause 6.4.2.12.
– no_reply_timer is an integer with values between 0 and 180 seconds for communication forwarding on no reply timer.
6.4.2.9 CFNRc_param
Table 6.4.2.9-1: CFNRc_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
56 |
RESERVED |CFNRc_subscription_options |(a)|(b)|(c)|(d)|(e)|(f)|(g)|(h) |
|
60 |
CFNRc_divertedto_destination_ |CFNRc_divertedto_destination_ Offset |Length |
– CFNRc_divertedto_destination_offset is the pointer to CFNRc diverted-to destination in the variable part of the MMTEL-PSTN-ISDN-CS Dataset.
– CFNRc_subscription_options: described in subclause 6.4.2.12.
6.4.2.10 CFNL_param
Table 6.4.2.10-1: CFNL_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
64 |
RESERVED |CFNL_subscription_options |(a)|(b)|(c)|(d)|(e)|(f)|(g)|(h) |
|
68 |
CFNL_divertedto_destination_ |CFNL_divertedto_destination_ Offset |Length |
– CFNL_divertedto_destination_offset is the pointer to CFNL diverted-to destination in the variable part of the MMTEL-PSTN-ISDN-CS Dataset.
– CFNL_subscription_options: described in subclause 6.4.2.12.
6.4.2.11 CD_param
Table 6.4.2.11-1: CD_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
72 |
RESERVED |CD_subscription_options |(a)|(b)|(c)|(d)|(e)|(f)|(g)|(h) |
|
76 |
RESERVED | RESERVED | |
– CD_subscription_options: described in subclause 6.4.2.12.
6.4.2.12 Subscription options of CDIV Services
CFU_subscription_options, CFB_subscription_options, CFNR_subscription_options, CFNRc_subscription_options, CFNL_subscription_options, CD_subscription_options use the same format with bit fields according to the following tables:
Table 6.4.2.12-1: CDIV Subscription options bit field
|
1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
| | | | | | | (a)|(b)|(c)|(d)|(e)|(f)|(g)|(h) |
Table 6.4.2.12-2: CDIV Subscription options binary values
|
Field |
Subscription options |
Value |
Binary value |
Applicability |
|
|
(a) |
Served user receives indication that a communication has been forwarded |
No |
Bit 15 0 0 |
Bit 14 0 1 |
CFU CFNRc |
|
(b) |
Originating user receives notification that his communication has been diverted (forwarded or deflected). |
No |
Bit 13 0 0 |
Bit 12 0 1 |
CFU CFNRc |
|
(c) |
Served user allows the presentation of diverted to URI to originating user in diversion notification. |
No |
Bit 11 0 1 0 |
Bit 10 0 0 1 |
CFU CFNRc |
|
(d) |
Served user receives reminder indication on outgoing communication that CDIV is currently activated. |
No |
Bit 9 0 0 |
Bit 8 0 1 |
CFU CFNRc |
|
(e) |
Served user allows the presentation of his/her URI to diverted‑to user. |
No |
Bit 7 0 1 0 |
Bit 6 0 0 1 |
CFU CFNRc |
|
(f) |
Served user allows the presentation of his/her URI to originating user in diversion notification. |
No |
Bit 5 0 1 0 |
Bit 4 0 0 1 |
CFU CFNRc |
|
(g) |
Reserved |
||||
|
(h) |
Reserved |
||||
6.4.2.12A CDIV_network_provider_options
Table 6.4.2.12A-1: CDIV_network_provider_options fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
80 |
| | |number_of diversions (a)|(b)| | |
|
84 |
CDIV_indication_timer | RESERVED | |
– Fields (a) and (b)
Table 6.4.2.12A-2: CDIV_network_provider_options values
|
Field |
Network provider option |
Value |
Binary value |
Applicability |
|
|
(a) |
Served user communication retention on invocation of diversion |
Retain communication to the served user until alerting begins at the diverted-to user |
Bit 31 0 0 |
Bit 30 1 0 |
CFNR |
|
(b) |
Served user communication retention when diverting is rejected at |
Continue to alert the diverting user |
Bit 29 0 0 |
Bit 28 1 0 |
CFNR CD |
– umber_of diversions is an integer giving the total number of all diversions for each communication
– CDIV_indication_timer is an integer with values between 0 and 60 seconds.
6.4.2.13 CW_param
Table 6.4.2.13-1: CW_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
88 |
(a)| RESERVED | RESERVED | | |
Table 6.4.2.13-2: CW_param values
|
Field |
CW Parameters |
Value |
Binary value |
|
|
(a) |
calling user receives notification that his call is waiting |
No |
Bit 31 0 0 |
Bit 30 0 1 |
6.4.2.14 ICB_param
Table 6.4.2.14-1: ICB_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
92 |
RESERVED | RESERVED | |
|
96 |
RESERVED | RESERVED | |
In this release, as indicated in subclause 6.1.2.10, there is no parameter that applies to the ICB service; ICB_param fields are Reserved.
6.4.2.15 OCB_param
Table 6.4.2.15-1: OCB_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
100 |
RESERVED | RESERVED | |
|
102 |
RESERVED | RESERVED | |
In this release, as indicated in subclause 6.1.2.10, there is no parameter that applies to the OCB service; 0CB_param fields are Reserved.
6.4.2.16 Void
6.4.3 AOC Dataset
6.4.3.1 AOC Dataset content
Table 6.4.3.1-1: AOC Dataset fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
0 |
DATASET_HEADER |
|
4 |
AOC_service_ |AOC_service_obl| RESERVED |AOC_format type |igatory_type | | |
|
8 |
Preferred_AOC_currency |
6.4.3.2 Dataset Header
– dataset_identifier
The value of dataset_identifier of the AOC Dataset is 2.
6.4.3.3 AOC_service_type
Table 6.4.3.3-1: AOC_service_type fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
4 |
(a)|(b)|(c)|(d)| | | | | |
Table 6.4.a.3-2: AOC_service_type values
|
Field |
AOC service type |
Value |
Binary value |
|
|
(a) |
AOC service type (AOC-S) |
No |
Bit 31 0 0 |
Bit 30 0 1 |
|
(b) |
AOC service type (AOC-D) |
No Yes |
Bit 29 0 0 |
Bit 28 0 1 |
|
(c) |
AOC service type (AOC-E ) |
No Yes |
Bit 27 0 0 |
Bit 26 0 1 |
|
(d) |
RESERVED |
Bit 25 |
Bit 24 |
|
6.4.3.4 AOC_service_obligatory_type
Table 6.4.3.4-1: AOC_service_obligatory_type fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
4 |
|(a)|(b)|(c)|(d)| | | | | | |
Table 6.4.3.4-2: AOC_service_obligatory_type values
|
Field |
AOC service obligatory type |
Value |
Binary value |
|
|
(a) |
AOC service obligatory type for AOC-S |
None AOC-I AOC-C |
Bit 23 0 0 1 |
Bit 22 0 1 0 |
|
(b) |
AOC service obligatory type for AOC-D |
None AOC-I AOC-C |
Bit 21 0 0 1 |
Bit 20 0 1 0 |
|
(c) |
AOC service obligatory type for AOC-E |
None AOC-I AOC-C |
Bit 19 0 0 1 |
Bit 18 0 1 0 |
|
(d) |
RESERVED |
Bit 17 |
Bit 16 |
|
6.4.3.5 Preferred_AOC_currency
Preferred_AOC_currency is of type Unsigned32 and contains the currency numeric code as defined in ISO 4217 [23].
6.4.3.6 AOC_format
Table 6.4.3.6-1: AOC_format fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
4 |
|(a)|(b)|(c)|(d) | | | | |
Table 6.4.3.6-2: AOC_format values
|
Field |
AOC_format |
Value |
Binary value |
|
|
(a) |
AOC format for AOC-S |
None Monetary Non Monetary CAI |
Bit 23 0 0 1 1 |
Bit 22 0 1 0 1 |
|
(b) |
AOC format for AOC-D |
None Monetary Non Monetary CAI |
Bit 21 0 0 1 1 |
Bit 20 0 1 0 1 |
|
(c) |
AOC format for AOC-E |
None Monetary Non Monetary CAI |
Bit 19 0 0 1 1 |
Bit 18 0 1 0 1 |
|
(d) |
RESERVED |
Bit 17 |
Bit 16 |
|
6.4.4 FA Pilot Dataset
6.4.4.1 FA Pilot Dataset contentTable
6.4.4.1-1: FA Pilot Dataset fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
0 |
DATASET_HEADER |
|
4 |
FA_pilot_param |
|
8 |
FA_members_list_pointer | FA_members_number | |
|
12 |
FA members list |
|
FA member IMPU |
|
|
FA member IMPU |
|
6.4.4.2 Dataset Header
– dataset_identifier
The value of dataset_identifier of the FA Pilot Dataset is 3.
6.4.4.3 FA_pilot_param
Table 6.4.4.3-1: FA_pilot_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
Reserved | Reserved | |
Table 6.4.4.3-2: FA_pilot_param values
|
Field |
FA Pilot Parameters |
Value |
Binary value |
|
|
(a) |
Pilot/Member status |
FA Pilot is not FA Member |
Bit 31 0 1 |
|
|
(b) |
Single/multiple user |
Single User |
Bit 30 0 1 |
|
|
(c) |
Membership |
FA Membership is Permanent |
Bit 29 0 1 |
|
6.4.4.4 FA_members_list_pointer
The FA_members_list_pointer is an offset, as defined in clause 6.3.6, pointing to the beginning of FA_members_list.
6.4.4.5 FA_members_number
FA_members_number indicates the number of FA members and is an integer.
6.4.4.6 FA_members_list
Table 6.4.4.6-1: FA_members_list fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
FA_member_offset | FA_member_length | |
|
|
Reserved |
|
|
FA_member_offset | FA_member_length | |
|
|
Reserved |
FA_members_list comprises identical field sets of which the number is the number of FA members.
Each field set comprises:
– FA_member_offset: as defined in clause 6.3.6, it points to the beginning of the FA member IMPU field
– FA_member_length: it gives the length of the FA_member_IMPU field
– A Reserved field
6.4.4.7 FA_member_IMPU
FA_member_IMPU gives the IMPU of a FA member and is a string of variable length.
6.4.5 FA Member Dataset
6.4.5.1 FA Member Dataset content
Table 6.4.5.1-1: FA Member Dataset fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
0 |
DATASET_HEADER |
|
4 |
FA_member_param |
|
8 |
FA_groups_list_pointer | FA_groups_number | |
|
12 |
FA groups list |
|
FA pilot IMPU |
|
|
FA pilot IMPU |
|
6.4.5.2 Dataset Header
– dataset_identifier
The value of dataset_identifier of the FA Member Dataset is 4.
6.4.5.3 FA_member_param
Table 6.4.5.3-1: FA_member_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
Reserved | Reserved | |
6.4.5.4 FA_groups_list_pointer
The FA_groups_list_pointer is an offset, as defined in clause 6.3.6, pointing to the beginning of FA_groups_list.
6.4.5.5 FA_groups_number
FA_groups_number indicates the number of FA groups which the FA member belongs to and is an integer.
6.4.5.6 FA_groups_list
Table 6.4.5.6-1: FA_groups_list fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
FA_group_offset | FA_group_length | |
|
|
FA_group_param | Reserved | |
|
|
FA_group_offset | FA_group_length | |
|
|
FA_group_param | Reserved | |
FA_groups_list comprises identical field sets of which the number is the number of FA groups.
Each field set comprises:
– FA_group_offset: as defined in clause 6.3.6, it points to the beginning of the FA_Pilot_IMPU field
– FA_member_length: it gives the length of the FA_pilot_IMPU field
– FA_group_param
– A Reserved field
6.4.5.7 FA_group_param
Table 6.4.5.7-1: FA_group_param fields
|
4-byte tuple |
3|3|2|2|2|2|2|2|2|2|2|2|1|1|1|1|1|1|1|1|1|1|0|0|0|0|0|0|0|0|0|0 1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0|9|8|7|6|5|4|3|2|1|0 |
|
a|b| Reserved | Reserved | | | |
Table 6.4.5.7-2: FA_group_param values
|
Field |
FA Group Parameters |
Value |
Binary value |
|
|
(a) |
FA Member status in the FA group |
FA Member is inactive in the FA group |
Bit 31 0 1 |
|
|
(b) |
Default FA group |
The FA group is not a default FA group for the FA member The FA group is a default FA group for the FA member |
Bit 30 0 1 |
|
6.4.5.8 FA_pilot_IMPU
FA_pilot_IMPU gives the IMPU of the FA pilot of the FA group and is a string of variable length.
6.5 Compatibility mechanism
6.5.1 General
The subclause 6.5 describes the mechanism to aid compatibility of the binary format when introducing extensions to the binary option content given in subclause 6.1.2 for new features in the services supported or for new services.
An AS supporting the new feature/service may generate transparent data where reserved fields of a dataset are allocated or new datasets are defined. This transparent data may be accessed by another AS that does not support the extensions which may cause interoperability issues.
6.5.2 Reserved fields
Reserved fields are defined in the datasets. An AS shall not modify the content of such reserved fields when updating a dataset in the HSS.
6.5.3 Addition of new datasets
As new datasets defined according to subclause 6.2.2 may be introduced in the same transparent data containing the MMTEL-PSTN-CS dataset and so associated to the same service indication, an AS that does not support these new datasets shall not modify the content of these datasets when rewriting the transparent data in the HSS.