Data Coding Scheme - Revision history

Bruce1ee: Reverted edit by 154.80.20.162 (talk) to last version by Frap

2023-10-29T07:09:44Z

Reverted edit by 154.80.20.162 (talk) to last version by Frap

← Previous revision		Revision as of 07:09, 29 October 2023
Line 73:		Line 73:
	\|style="text-align:center;"\| 0		\|style="text-align:center;"\| 0
	\| GSM 7 bit \|\| Default		\| GSM 7 bit \|\| Default
			\|style="text-align:center;"\| - \|\|
	\|style="unfortunatly block them''''''Bold text'''''
	[[File:Sabiav\|normalpx\|frame\|none\|alt=Without any media includes\|writer2023]]
	±'''''r;"\| - \|\|
	\|-		\|-
	\|style="text-align:center;"\| 01		\|style="text-align:center;"\| 01
Line 337:		Line 335:
	\|style="text-align:center;"\| 50		\|style="text-align:center;"\| 50
	\| GSM 7 bit \|\| Class 2 (SIM/USIM-specific)		\| GSM 7 bit \|\| Class 2 (SIM/USIM-specific)
	\|style="~~warning block buster 2023~~;"\| + \|\|		\|style="text-align:center;"\| + \|\|
	\|-		\|-
	\|style="~~Warning u~~ ;"\| 33		\|style="text-align:center;"\| 33
	\|style="~~warning u tor~~;"\| 51		\|style="text-align:center;"\| 51
	\| GSM 7 bit \|\| Class 3 (TE-specific)		\| GSM 7 bit \|\| Class 3 (TE-specific)
	\|style="text-align:center;"\| + \|\|		\|style="text-align:center;"\| + \|\|
	\|-ǃǂ		\|-
	\|style="text-align:center;"\| 34		\|style="text-align:center;"\| 34
	\|style="text-align:center;"\| 52		\|style="text-align:center;"\| 52

154.80.20.162 at 05:03, 29 October 2023

2023-10-29T05:03:40Z

← Previous revision		Revision as of 05:03, 29 October 2023
Line 73:		Line 73:
	\|style="text-align:center;"\| 0		\|style="text-align:center;"\| 0
	\| GSM 7 bit \|\| Default		\| GSM 7 bit \|\| Default
			\|style="unfortunatly block them''''''Bold text'''''
	\|style="text-align:center;"\| - \|\|
			[[File:Sabiav\|normalpx\|frame\|none\|alt=Without any media includes\|writer2023]]
			±'''''r;"\| - \|\|
	\|-		\|-
	\|style="text-align:center;"\| 01		\|style="text-align:center;"\| 01
Line 335:		Line 337:
	\|style="text-align:center;"\| 50		\|style="text-align:center;"\| 50
	\| GSM 7 bit \|\| Class 2 (SIM/USIM-specific)		\| GSM 7 bit \|\| Class 2 (SIM/USIM-specific)
	\|style="~~text-align:center~~;"\| + \|\|		\|style="warning block buster 2023;"\| + \|\|
	\|-		\|-
	\|style="~~text-align:center~~;"\| 33		\|style="Warning u ;"\| 33
	\|style="~~text-align:center~~;"\| 51		\|style="warning u tor;"\| 51
	\| GSM 7 bit \|\| Class 3 (TE-specific)		\| GSM 7 bit \|\| Class 3 (TE-specific)
	\|style="text-align:center;"\| + \|\|		\|style="text-align:center;"\| + \|\|
	\|-		\|-ǃǂ
	\|style="text-align:center;"\| 34		\|style="text-align:center;"\| 34
	\|style="text-align:center;"\| 52		\|style="text-align:center;"\| 52

Frap: MOS:HEAD

2023-01-06T15:43:24Z

MOS:HEAD

← Previous revision		Revision as of 15:43, 6 January 2023
Line 10:		Line 10:
	The field is described in [[GSM 03.40\|3GPP 23.040]] and [[GSM 03.38\|3GPP 23.038]] under the name TP-DCS.		The field is described in [[GSM 03.40\|3GPP 23.040]] and [[GSM 03.38\|3GPP 23.038]] under the name TP-DCS.

	==Message ~~Character~~ ~~Sets~~==		==Message character sets==

	A special 7-bit encoding called the [[GSM 03.38\|''GSM 7 bit default alphabet'']] was designed for the Short Message System in GSM. The alphabet contains the most-often used symbols from most Western-European languages (and some Greek uppercase letters). Some [[ASCII]] characters and the [[Euro sign]] did not fit into the GSM 7-bit default alphabet and must be encoded using two septets. These characters form GSM 7 bit default alphabet ''extension table''. Support of the GSM 7-bit alphabet is mandatory for GSM handsets and network elements.<ref name="3GPP 23.038"/>		A special 7-bit encoding called the [[GSM 03.38\|''GSM 7 bit default alphabet'']] was designed for the Short Message System in GSM. The alphabet contains the most-often used symbols from most Western-European languages (and some Greek uppercase letters). Some [[ASCII]] characters and the [[Euro sign]] did not fit into the GSM 7-bit default alphabet and must be encoded using two septets. These characters form GSM 7 bit default alphabet ''extension table''. Support of the GSM 7-bit alphabet is mandatory for GSM handsets and network elements.<ref name="3GPP 23.038"/>
Line 24:		Line 24:
	* 8-bit data		* 8-bit data

	==Message ~~Classes~~==		==Message classes==

	The TP-DCS octet has a complex syntax to allow carrying of other information; the most notable are message classes:		The TP-DCS octet has a complex syntax to allow carrying of other information; the most notable are message classes:
Line 44:		Line 44:
	[[Short Message Service#Flash SMS\|Flash messages]] are received by a mobile phone even though it has full memory. They are not stored in the phone, they just displayed on the phone display.		[[Short Message Service#Flash SMS\|Flash messages]] are received by a mobile phone even though it has full memory. They are not stored in the phone, they just displayed on the phone display.

	==Other ~~Features~~==		==Other features==

	===Automatic ~~Deletion~~ after ~~Reading~~===		===Automatic deletion after reading===

	The handset should delete any message received with a TP-DCS value falling to the "Message Marked for Automatic Deletion Coding Group" after user has read it.		The handset should delete any message received with a TP-DCS value falling to the "Message Marked for Automatic Deletion Coding Group" after user has read it.

	===Message ~~Waiting~~ ~~Indication~~===		===Message waiting indication===

	Message Waiting Indication group of DCS values serves to set or reset flags indicating presence of unread [[voicemail]], [[fax]], [[e-mail]] or other messages.		Message Waiting Indication group of DCS values serves to set or reset flags indicating presence of unread [[voicemail]], [[fax]], [[e-mail]] or other messages.

	===Data ~~Compression~~===		===Data compression===

	A special DCS value also allows message [[Data compression\|compression]], but it perhaps is not used by any operator.		A special DCS value also allows message [[Data compression\|compression]], but it perhaps is not used by any operator.

	==DCS ~~Values~~==		==DCS values==

	===SMS ~~Data~~ ~~Coding~~ ~~Scheme~~===		===SMS data coding scheme===

	The values of TP-DCS are defined in [[GSM 03.38\|GSM recommendation 03.38]].<ref name="3GPP 23.038">[http://www.3gpp.org/ftp/Specs/html-info/23038.htm 3GPP TS 23.038], Alphabets and language-specific information.</ref>		The values of TP-DCS are defined in [[GSM 03.38\|GSM recommendation 03.38]].<ref name="3GPP 23.038">[http://www.3gpp.org/ftp/Specs/html-info/23038.htm 3GPP TS 23.038], Alphabets and language-specific information.</ref>
Line 1,095:		Line 1,095:
	[[iDEN]] mobile standard uses values F7<sub>16</sub> and F8<sub>16</sub> in a special way.		[[iDEN]] mobile standard uses values F7<sub>16</sub> and F8<sub>16</sub> in a special way.

	===CBS ~~Data~~ ~~Coding~~ ~~Scheme~~===		===CBS data coding scheme===

	For the DCS values in Cell Broadcast Messages see [[GSM 03.38\|GSM recommendation 03.38]].<ref name="3GPP 23.038"/>		For the DCS values in Cell Broadcast Messages see [[GSM 03.38\|GSM recommendation 03.38]].<ref name="3GPP 23.038"/>
Line 1,101:		Line 1,101:
	==See also==		==See also==

	* [[Short Message Service]]		* [[Short Message Service]] (SMS)
	* [[Cell Broadcast]]		* [[Cell Broadcast]]
	* [[GSM 03.38]]		* [[GSM 03.38]]

Sauer202 at 11:37, 30 September 2021

2021-09-30T11:37:51Z

← Previous revision		Revision as of 11:37, 30 September 2021
Line 1:		Line 1:
	'''Data Coding Scheme''' is a one-octet field in Short Messages (SM) and Cell Broadcast Messages (CB) which carries a basic information how the recipient handset should process the received message. The information includes:		'''Data Coding Scheme''' is a one-[[Octet (computing)\|octet]] field in [[SMS\|Short Messages]] (SM) and [[Cell Broadcast\|Cell Broadcast Messages]] (CB) which carries a basic information how the recipient handset should process the received message. The information includes:

	* the character set or message coding, which determines the encoding of the message user data		* the character set or message coding, which determines the encoding of the message user data

Cloudjpk: diction fixes

2020-11-23T19:04:26Z

diction fixes

← Previous revision		Revision as of 19:04, 23 November 2020
Line 1:		Line 1:
	'''Data Coding Scheme''' is a one-octet field in Short Messages (SM) and Cell Broadcast Messages (CB) which carries a basic information how the recipient handset should process the received message. The information includes:		'''Data Coding Scheme''' is a one-octet field in Short Messages (SM) and Cell Broadcast Messages (CB) which carries a basic information how the recipient handset should process the received message. The information includes:

	* the character set or message coding which determines the encoding of the message user data		* the character set or message coding, which determines the encoding of the message user data
	* the message class which determines to which component of the Mobile Station (MS) or User Equipment (UE) ~~should be~~ the message delivered		* the message class, which determines to which component of the Mobile Station (MS) or User Equipment (UE) the message should be delivered
	* the request to automatically delete the message after reading		* the request to automatically delete the message after reading
	* the state of flags indicating presence of unread voicemail, fax, e-mail or other messages		* the state of flags indicating presence of unread voicemail, fax, e-mail or other messages

185.116.111.2: Updated reserved columns to clarify compression can not be used with 8 bit data and UCS2 Encoding and clarified difference between undefined and reserved character set

2018-12-07T03:44:21Z

Updated reserved columns to clarify compression can not be used with 8 bit data and UCS2 Encoding and clarified difference between undefined and reserved character set

Show changes

Comp.arch: "7-bit", similar change to my previous edit elsewhere.

2017-11-01T12:45:26Z

"7-bit", similar change to my previous edit elsewhere.

← Previous revision		Revision as of 12:45, 1 November 2017
Line 1:		Line 1:
	'''Data Coding Scheme''' is a one-octet field in Short Messages (SM) and Cell Broadcast Messages (CB) which carries a basic information how the recipient handset should process the received message. The information includes:		'''Data Coding Scheme''' is a one-octet field in Short Messages (SM) and Cell Broadcast Messages (CB) which carries a basic information how the recipient handset should process the received message. The information includes:

	* the character set or message coding which determines the encoding of the message user data		* the character set or message coding which determines the encoding of the message user data
	* the message class which determines to which component of the Mobile Station (MS) or User Equipment (UE) should be the message delivered		* the message class which determines to which component of the Mobile Station (MS) or User Equipment (UE) should be the message delivered
Line 11:		Line 12:
	==Message Character Sets==		==Message Character Sets==

	A special 7 bit encoding called the [[GSM 03.38\|''GSM 7 bit default alphabet'']] was designed for the Short Message System in GSM. The alphabet contains the most-often used symbols from most Western-European languages (and some Greek uppercase letters). Some [[ASCII]] characters and the [[Euro sign]] did not fit into the GSM 7 bit default alphabet and must be encoded using two septets. These characters form GSM 7 bit default alphabet ''extension table''. Support of the GSM 7-bit alphabet is mandatory for GSM handsets and network elements.<ref name="3GPP 23.038"/>		A special 7-bit encoding called the [[GSM 03.38\|''GSM 7 bit default alphabet'']] was designed for the Short Message System in GSM. The alphabet contains the most-often used symbols from most Western-European languages (and some Greek uppercase letters). Some [[ASCII]] characters and the [[Euro sign]] did not fit into the GSM 7-bit default alphabet and must be encoded using two septets. These characters form GSM 7 bit default alphabet ''extension table''. Support of the GSM 7-bit alphabet is mandatory for GSM handsets and network elements.<ref name="3GPP 23.038"/>

	Languages which use [[Latin script]], but use characters which are not present in the GSM 7 bit default alphabet, often replace missing characters with [[diacritic]] marks with corresponding characters without diacritics, which causes not entirely satisfactory user experience, but is often accepted. In order to include these missing characters the 16-bit [[UTF-16]] (in GSM called UCS-2) encoding may be used at the price of reducing the length of a (non-segmented) message from 160 to 70 characters.		Languages which use [[Latin script]], but use characters which are not present in the GSM 7-bit default alphabet, often replace missing characters with [[diacritic]] marks with corresponding characters without diacritics, which causes not entirely satisfactory user experience, but is often accepted. In order to include these missing characters the 16-bit [[UTF-16]] (in GSM called UCS-2) encoding may be used at the price of reducing the length of a (non-segmented) message from 160 to 70 characters.

	The messages in Chinese, Korean or Japanese languages must be encoded using the [[UTF-16]] character encoding. The same was also true for other languages using non-Latin scripts like Russian, Arabic, Hebrew and various Indian languages. In 3GPP TS 23.038 8.0.0 published in 2008 a new feature, an extended [[GSM 03.38#National language shift tables\|National language shift table]] was introduced, which in the version 11.0.0 published in 2012 covers [[Turkish language\|Turkish]], [[Spanish language\|Spanish]], [[Portuguese language\|Portuguese]], [[Bengali language\|Bengali]], [[Gujarati language\|Gujarati]], [[Hindi]], [[Kannada]], [[Malayalam]], [[Oriya language\|Oriya]], [[Punjabi language\|Punjabi]], [[Tamil language\|Tamil]], [[Telugu language\|Telugu]] and [[Urdu]] languages. The mechanism replaces GSM 7 bit default alphabet code table and/or extended table with a national table(s) according to special information elements in [[User Data Header]]. The non-segmented message using national language shift table(s) may carry up to 155 (or 153) 7-bit characters.		The messages in Chinese, Korean or Japanese languages must be encoded using the [[UTF-16]] character encoding. The same was also true for other languages using non-Latin scripts like Russian, Arabic, Hebrew and various Indian languages. In 3GPP TS 23.038 8.0.0 published in 2008 a new feature, an extended [[GSM 03.38#National language shift tables\|National language shift table]] was introduced, which in the version 11.0.0 published in 2012 covers [[Turkish language\|Turkish]], [[Spanish language\|Spanish]], [[Portuguese language\|Portuguese]], [[Bengali language\|Bengali]], [[Gujarati language\|Gujarati]], [[Hindi]], [[Kannada]], [[Malayalam]], [[Oriya language\|Oriya]], [[Punjabi language\|Punjabi]], [[Tamil language\|Tamil]], [[Telugu language\|Telugu]] and [[Urdu]] languages. The mechanism replaces GSM 7-bit default alphabet code table and/or extended table with a national table(s) according to special information elements in [[User Data Header]]. The non-segmented message using national language shift table(s) may carry up to 155 (or 153) 7-bit characters.

	GSM recognizes only 2 encodings for [[text file\|text message]]s and 1 encoding for [[binary file\|binary messages]]:		GSM recognizes only two encodings for [[text file\|text message]]s and one encoding for [[binary file\|binary messages]]:

	* GSM 7 bit default alphabet (which includes using of National language shift tables as well)		* GSM 7-bit default alphabet (which includes using of National language shift tables as well)
	* UCS-2		* UCS-2
	* 8 bit data		* 8-bit data

	==Message Classes==		==Message Classes==
Line 1,088:		Line 1,089:
	* [[Universal Computer Protocol]]		* [[Universal Computer Protocol]]

	== References ==		==References==
	{{Reflist}}		{{Reflist}}

156.67.241.62: /* Message Character Sets */

2017-10-11T13:33:24Z

Message Character Sets

← Previous revision		Revision as of 13:33, 11 October 2017
Line 11:		Line 11:
	==Message Character Sets==		==Message Character Sets==

	A special 7 bit encoding called [[GSM 03.38\|''GSM 7 bit default alphabet'']] was designed for Short Message System in GSM. The alphabet contains the most-often used symbols from most Western-European languages (and some Greek uppercase letters). Some [[ASCII]] characters and the [[Euro sign]] did not fit into the GSM 7 bit default alphabet and must be encoded using two septets. These characters form GSM 7 bit default alphabet ''extension table''. Support of the GSM 7-bit alphabet is mandatory for GSM handsets and network elements.<ref name="3GPP 23.038"/>		A special 7 bit encoding called the [[GSM 03.38\|''GSM 7 bit default alphabet'']] was designed for the Short Message System in GSM. The alphabet contains the most-often used symbols from most Western-European languages (and some Greek uppercase letters). Some [[ASCII]] characters and the [[Euro sign]] did not fit into the GSM 7 bit default alphabet and must be encoded using two septets. These characters form GSM 7 bit default alphabet ''extension table''. Support of the GSM 7-bit alphabet is mandatory for GSM handsets and network elements.<ref name="3GPP 23.038"/>

	Languages which use [[Latin script]], but use characters which are not present in the GSM 7 bit default alphabet, often replace missing characters with [[diacritic]] marks with corresponding characters without diacritics, which causes not entirely satisfactory user experience, but is often accepted. ~~For~~ ~~best~~ ~~look~~ the 16-bit [[UTF-16]] (in GSM called UCS-2) encoding may be used at price of reducing length of a (non segmented) message from 160 to 70 characters.		Languages which use [[Latin script]], but use characters which are not present in the GSM 7 bit default alphabet, often replace missing characters with [[diacritic]] marks with corresponding characters without diacritics, which causes not entirely satisfactory user experience, but is often accepted. In order to include these missing characters the 16-bit [[UTF-16]] (in GSM called UCS-2) encoding may be used at the price of reducing the length of a (non-segmented) message from 160 to 70 characters.

	The messages in Chinese, Korean or Japanese languages must be encoded using the [[UTF-16]] character encoding. The same was also true for other languages using non-Latin scripts like Russian, Arabic, Hebrew and various Indian languages. In 3GPP TS 23.038 8.0.0 published in 2008 a new feature, an extended [[GSM 03.38#National language shift tables\|National language shift table]] was introduced, which in the version 11.0.0 published in 2012 covers [[Turkish language\|Turkish]], [[Spanish language\|Spanish]], [[Portuguese language\|Portuguese]], [[Bengali language\|Bengali]], [[Gujarati language\|Gujarati]], [[Hindi]], [[Kannada]], [[Malayalam]], [[Oriya language\|Oriya]], [[Punjabi language\|Punjabi]], [[Tamil language\|Tamil]], [[Telugu language\|Telugu]] and [[Urdu]] languages. The mechanism replaces GSM 7 bit default alphabet code table and/or extended table with a national table(s) according to special information elements in [[User Data Header]]. The non-segmented message using national language shift table(s) may carry up to 155 (or 153) 7-bit characters.		The messages in Chinese, Korean or Japanese languages must be encoded using the [[UTF-16]] character encoding. The same was also true for other languages using non-Latin scripts like Russian, Arabic, Hebrew and various Indian languages. In 3GPP TS 23.038 8.0.0 published in 2008 a new feature, an extended [[GSM 03.38#National language shift tables\|National language shift table]] was introduced, which in the version 11.0.0 published in 2012 covers [[Turkish language\|Turkish]], [[Spanish language\|Spanish]], [[Portuguese language\|Portuguese]], [[Bengali language\|Bengali]], [[Gujarati language\|Gujarati]], [[Hindi]], [[Kannada]], [[Malayalam]], [[Oriya language\|Oriya]], [[Punjabi language\|Punjabi]], [[Tamil language\|Tamil]], [[Telugu language\|Telugu]] and [[Urdu]] languages. The mechanism replaces GSM 7 bit default alphabet code table and/or extended table with a national table(s) according to special information elements in [[User Data Header]]. The non-segmented message using national language shift table(s) may carry up to 155 (or 153) 7-bit characters.

103.42.1.250: /* Data Compression */Fixed a typo

2016-08-01T08:21:47Z

Data Compression: Fixed a typo

← Previous revision		Revision as of 08:21, 1 August 2016
Line 55:		Line 55:
	===Data Compression===		===Data Compression===

	A special DCS ~~values~~ also allows message [[Data compression\|compression]], but it perhaps is not used by any operator.		A special DCS value also allows message [[Data compression\|compression]], but it perhaps is not used by any operator.

	==DCS Values==		==DCS Values==

Gronk Oz: /* CBS Data Coding Scheme */General clean up & spelling; using AWB

2015-04-01T08:00:37Z

CBS Data Coding Scheme: General clean up & spelling; using AWB

← Previous revision		Revision as of 08:00, 1 April 2015
Line 1,072:		Line 1,072:
	===CBS Data Coding Scheme===		===CBS Data Coding Scheme===

	For the DCS values in Cell Broadcast Messages see [[GSM 03.38\|GSM recommendation 03.38]].<ref name="3GPP 23.038"~~>[http:~~/~~/www.3gpp.org/ftp/Specs/html-info/23038.htm 3GPP TS 23.038], Alphabets and language-specific information.</ref~~>		For the DCS values in Cell Broadcast Messages see [[GSM 03.38\|GSM recommendation 03.38]].<ref name="3GPP 23.038"/>

	==See also==		==See also==

← Previous revision		Revision as of 07:09, 29 October 2023
Line 73:		Line 73:
	\|style="text-align:center;"\| 0		\|style="text-align:center;"\| 0
	\| GSM 7 bit \|\| Default		\| GSM 7 bit \|\| Default
			\|style="text-align:center;"\| - \|\|
	\|style="unfortunatly block them''''''Bold text'''''
	[[File:Sabiav\|normalpx\|frame\|none\|alt=Without any media includes\|writer2023]]
	±'''''r;"\| - \|\|
	\|-		\|-
	\|style="text-align:center;"\| 01		\|style="text-align:center;"\| 01
Line 337:		Line 335:
	\|style="text-align:center;"\| 50		\|style="text-align:center;"\| 50
	\| GSM 7 bit \|\| Class 2 (SIM/USIM-specific)		\| GSM 7 bit \|\| Class 2 (SIM/USIM-specific)
	\|style="~~warning block buster 2023~~;"\| + \|\|		\|style="text-align:center;"\| + \|\|
	\|-		\|-
	\|style="~~Warning u~~ ;"\| 33		\|style="text-align:center;"\| 33
	\|style="~~warning u tor~~;"\| 51		\|style="text-align:center;"\| 51
	\| GSM 7 bit \|\| Class 3 (TE-specific)		\| GSM 7 bit \|\| Class 3 (TE-specific)
	\|style="text-align:center;"\| + \|\|		\|style="text-align:center;"\| + \|\|
	\|-ǃǂ		\|-
	\|style="text-align:center;"\| 34		\|style="text-align:center;"\| 34
	\|style="text-align:center;"\| 52		\|style="text-align:center;"\| 52

← Previous revision		Revision as of 05:03, 29 October 2023
Line 73:		Line 73:
	\|style="text-align:center;"\| 0		\|style="text-align:center;"\| 0
	\| GSM 7 bit \|\| Default		\| GSM 7 bit \|\| Default
			\|style="unfortunatly block them''''''Bold text'''''
	\|style="text-align:center;"\| - \|\|
			[[File:Sabiav\|normalpx\|frame\|none\|alt=Without any media includes\|writer2023]]
			±'''''r;"\| - \|\|
	\|-		\|-
	\|style="text-align:center;"\| 01		\|style="text-align:center;"\| 01
Line 335:		Line 337:
	\|style="text-align:center;"\| 50		\|style="text-align:center;"\| 50
	\| GSM 7 bit \|\| Class 2 (SIM/USIM-specific)		\| GSM 7 bit \|\| Class 2 (SIM/USIM-specific)
	\|style="~~text-align:center~~;"\| + \|\|		\|style="warning block buster 2023;"\| + \|\|
	\|-		\|-
	\|style="~~text-align:center~~;"\| 33		\|style="Warning u ;"\| 33
	\|style="~~text-align:center~~;"\| 51		\|style="warning u tor;"\| 51
	\| GSM 7 bit \|\| Class 3 (TE-specific)		\| GSM 7 bit \|\| Class 3 (TE-specific)
	\|style="text-align:center;"\| + \|\|		\|style="text-align:center;"\| + \|\|
	\|-		\|-ǃǂ
	\|style="text-align:center;"\| 34		\|style="text-align:center;"\| 34
	\|style="text-align:center;"\| 52		\|style="text-align:center;"\| 52