Sender Alias – Approval alias 42/13/ CIR

How to communicate the senders or aliases of SMS messages and comply with all the obligations set forth in the resolution and annex A.

On October 16th, Resolution 42/13 / CIR of Agcom, the Authority for Communications Guarantees, came into force.

The resolution regulates, on an experimental basis, the identification of the calling party in the SMS used for corporate messaging services (among which: SMS marketing, SMS alert, SMS informative).

Totalconnect proposes, without any additional cost, to carry out the necessary procedures, on your behalf, facilitating and simplifying as far as possible the process of presenting the aliases to Agcom.

All you need to do is to enter the required data on the dedicated page within your private area accessible from the main menu before sending.

Requests can be submitted only by persons who are in possession of VAT number or numeric tax code. The individuals, according to the resolution, can not send SMS with alias instead of the sender.

Totalconnect will still send their text messages, but substituting the alias.

To be accepted by Agcom, the senders (aliases) must meet the following requirements: they will have to clearly identify the subject who commissions the sending must comply with the legislation on registered trademarks can not consist of a common word (eg sms, promo, hello, message …), except for some cases for which Agcom will provide more information they will not be able to identify an entity or sensitive subject (eg ministry, police, post office, cartasi, mastercard …) they can not be composed of numbers only.

The information requested by Agcom refers to the communicating party (and not to others, such as the messaging service provider).

The following is a list of the requested information extracted from the resolution:
“I) Alias, ii) the number E.164 associated, iii) the name of the subject to which it is used, iv) the relevant Tax Code, v) the VAT number and vi) the methods for contacting this subject and in detail: vi.1) address, vi.2) telephone number, if any, in order of preference for customer service and switchboard, vi.3) fax, vi.4) e-mail, vi.5) PEC, vi .6) website address, if any, vii) date on which it is given to customers; viii) termination date, when no longer in use. ”
The “associated E.164 number” is provided free of charge by Totalconnect.

Code of Conduct

Code of Conduct concerning the supply of business messaging services containing alphanumeric codes (Alias) as senders

Version 1.0

Premise

This Code of Conduct is drawn up pursuant to art. 5 paragraph 4 of the Authority for Communications (AGCom) resolution 42/13 / CIR “Rules for the testing of alphanumeric indicators for the identification of the calling party in SMS / MMS used for corporate messaging services” (” Resolution “) and proposes to regulate the establishment, assignment and use of the Alias ​​in the field of corporate messaging services and to define the rules to protect the users of the aforesaid services.

Messaging services

The messaging services are the services provided by an authorized supplier pursuant to the Resolution in favor of a Customer / Company, natural or legal person, who intends to reach its Final Customers through SMS or MMS messages by communicating their offers of products or services , or service information and, depending on the case, requesting the same Final Customers a response to the communication sent. Messaging services that send a message to end customers are commonly referred to as “MT” (“Mobile Terminated”) messaging services, while messaging services that provide a response from end users, messaging services of type “MO” (“Mobile Originated”). MT services can be provided through the use of Alias ​​as an alternative to using the CLI. This code will only deal with corporate messaging services through the use of Aliases.

1. Definitions

For the purposes of this Code, consistent with the aforementioned resolution, the following are defined:

a) Customer / Company: the natural or legal person who uses or requests to use a corporate messaging service, by signing an offer of a company messaging service provider;

b) Final Customer: the natural or legal person who uses or requests to use an electronic communication service accessible to the public for purposes not related to their working, commercial or professional activity;

c) Corporate Messaging: communications of the SMS / MMS type, in single or mass modality, towards Final Customers by a Customer / Company, such as Companies or Organizations, for social, informative and advertising purposes;

d) Supplier of the company messaging service: legal entity authorized pursuant to art. 25 of the CCE which provides, on the basis of specific contracts with Customers / Company, the corporate messaging service through the use of the Aliases to the Final Customers (see Article 4 paragraph 1);

e) Access service provider: authorized legal entity pursuant to art. 25 of the CCE which provides mobile services, including the messaging service, to the Final Customer;

f) CLI – Calling line identification: identification of the call line by the number defined by the UIT-T Recommendation E.164 and nationally by the National Numbering Plan (Del. 52/12 / CIR and s.m.i.) associated to the same line;

g) Alias: string of alphanumeric characters transmitted in the field provided for sending the sender / CLI in SMS / MMS communications no longer than 11 characters as indicated in Annex A of this Code;

2. Inspiring principles of the Code

The Code aims to guarantee the correct development of corporate messaging services by ensuring the rights of the Clients / Company on one side and of the Final Customers on the other side and proper competition among the players in the sector.

In this context, the players in the sector intend to adopt common rules of conduct with the aim of increasing the market through the respect of the rights of the end customers who receive the messages. In this regard, the players in the sector will adopt their best experience and diligence to ensure the correct use by the Customers / Company of the Aliases.

3. Constitution of the Aliases

Aliases consist of a set of alphanumeric strings no longer than 11 characters, the details of which are indicated in Annex A of this code.

4. Assignment of the Aliases

The assignment of the Alias ​​takes place on the basis of the current trademark regulations.
The Company’s messaging service provider will use its utmost diligence in order to avoid that non-rights holders of a given Alias ​​may use Alias, whose legitimate use is due to third parties under the trademark law. To this end, in the first place, the company messaging service providers will adopt authentication procedures of the Customer / Company through credentials in order to ensure that the Customer / Company that has subscribed to a range of corporate messaging services is actually the subject that accesses to the system for sending messages and using Aliases.

Furthermore, the providers of corporate messaging services will do their best to include in the contracts with Customers / Company specific clauses in which they will assume to the Customers / Company the responsibility for the use of only Aliases that they have legitimately and to that end. end they can make the Customer / Company also sign a specific self-declaration. Customers / companies who prove to have used Alias ​​illegitimately will be prevented from using the related Aliases.

5. Assigning generic Aliases

The resolution provides for the prohibition of using Alias ​​already used for other Customers / Company and which do not significantly differ from Alias ​​already used. In this context, the assignment of generic Aliases is allowed provided that the Customers / Company undertake contracts with the company messaging service providers to insert in the text of the message a reference to their company name or to their own brand legitimately used in order to however, be recognizable for the Final Customer.

6. Assignment of Aliases that attract public bodies and institutions

Aliases that refer to public bodies and institutions are reserved exclusively for the same bodies or institutions and can not be associated with other subjects.

7. Uploading Aliases to the database managed by the AGCom

Before sending a message with Alias, the messaging service providers will take care to load on the database managed by the AGCom (also for short “Alias ​​System”) the Alias ​​used by the Customers / Company.

The following information will be inserted indicatively in the database:

– Alias ​​and associated E.164 numbering;
– Name Customer / company, VAT number / tax code;
– Customer / company contacts: only contact data between phone number, fax number, e-mail address;
– Cessation of the use of Alias ​​when it is no longer in use;

The name of the company messaging service provider and the date and time of records are automatically detected by the Alias ​​System.

The actual specific information to be associated with each Alias ​​can be updated following any changes to the technical-operational modalities of the Alias ​​System.

8. Use of Aliases by Customers / Company

The use of Aliases is allowed to Customers / Companies who have subscribed to a range of corporate messaging services with the company messaging service providers who have obtained one or more E.164 PNN numbers to be associated with the Aliases, in the respect of the art. 3, paragraph 2 of the Resolution.

Multiple providers of different business messaging services can subscribe to a business messaging service offer with the same Customer / Company.

A unique numbering must be associated with each Customer / Company. This numbering may be associated with multiple Aliases as long as they are used by the same Customer / Company.

9. Termination of use of the Alias ​​by Customers / Company

A specific Alias ​​will remain active as long as the contract between the Supplier of corporate messaging services and Customer / Company is in force, except in the event that, under the contract, the Customer / Company itself informs the Supplier that it no longer wishes to use a certain Alias.

Within 24 hours after the termination of the contract between the Company’s messaging service provider and Customer Company or the receipt by the Supplier of corporate messaging services of the communication of no longer want to use a specific Alias, the Supplier will communicate the cessation of use of Alias ​​to the Alias ​​System.

10. Protection of Final Customers

The Final Customer who receives an SMS / MMS message having as sender an Alias ​​deemed unexpected, deceptive or spam, can contact the Customer Care of their mobile operator reporting the case and communicating to the operator the following necessary information to make the due controls:

a) numbering of the final customer;
b) Alias ​​that appears in the sender of the message;
c) day, date and time of receipt;

Customer Care, through the query of the database managed by AGCom, receives the following information concerning the Customer / Company who sent the message and communicates it to the Final Customer:

– Customer / Company name;
– Alias ​​used;
– Customer / Company contacts;

In the event that the competent authorities request the tracking data of the message sent, the Company’s messaging service provider will deliver such data as soon as possible in order to ensure the purposes of justice.

11. Successive versions of the Code

The Supplier of the company’s messaging service reserves the right to prepare new and more evolved versions of this Code in the future in order to better meet the business needs of the players in the sector and to better protect the rights of end customers, in step with the evolution of the business messaging services containing Alias ​​and related discipline, currently still in the experimental phase.

ANNEX A
SET OF CHARACTERS ADMITTED FOR THE CONSTITUTION OF THE ALIAS

With reference to paragraph 6.2.1 “GSM 7 bit Default Alphabet” of the technical standard “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Alphabets and language-specific information “, 3GPP TS 23.038 version 11.0.0 (2012-10) Release 11, only the following is allowed for the establishment of the aliases.

the letters of the international alphabet in lowercase and uppercase:

  • ABCDEFGHIJKLMNOPQRSTUVXYWZ (HEX codes from 41 to 5A respectively)
  • abcdefghijklmnopqrstuvxywz (HEX codes from 61 to 6A respectively)

Accented lowercase letters in the Italian keyboard:

  • èéùìò (HEX codes from 04 to 08 respectively)
  • à (code HEX 7F)

The digits from 0 to 9

  • 0123456789 (HEX codes from 30 to 39 respectively)

Common punctuation marks:

  • SP (space: HEX code 20)
  • ! (exclamation mark: HEX code 21)
  • ‘(Apostrophe: HEX code 27)
  • , (comma: HEX 2C code)
  • . (point: HEX 2E code)
  • : (colon: HEX 3A code)
  • ; (semicolon: HEX 3B code)
  • ? (question mark: HEX 3F code)

the preceding characters can not be preceded by the space character.

Consecutive use of spaces is not permitted

  • “(Quotation marks, HEX code 22)

In an Alias, there may be only two quotation marks: one as an opening and a closing one. The first can not precede a space and the second can not follow a space.

Common currency symbols

  • € (euro: two-digit code HEX 1B 65)
  • £ (lira: HEX 01 code)
  • $ (dollar: HEX 02 code)

Common mathematical symbols

  • % (percentage: HEX code 25)
  • ((round parenthesis: HEX code 28)
  • ) (closed round bracket: HEX code 29)
  • + (plus: HEX 2B code)
  • – (minus or even dash: HEX 2D code)
  • = (same: HEX 3D code)

Symbols used in the internet:

  • @ (snail or “at”: code HEX 00)
  • _ (underlined or “underscore”: HEX code 11)
  • # (hash or “hash”: HEX code 23)
  • & (and: HEX code 26)
  • * (asterisk or “star”: code HEX 2A)

Ultimately, the list of permitted characters and the relevant encodings in hexadecimal ETSI to be used in the transmission of SMS / MMS as well as the relative encodings in hexadecimal UTF-8 to be used in communication to the Authority’s database are:

Carattere Codifica ETSI Codifica UTF-8 Carattere Codifica ETSI Codifica UTF-8 Carattere Codifica ETSI Codifica UTF-8
@ 00 40 8 38 38 Z 5A 5A
£ 01 C2 A3 9 39 39 a 61 61
$ 02 24 : 3A 3A b 62 62
è 04 C3 A8 ; 3B 3B c 63 63
é 05 C3 A9 = 3D 3D d 64 64
ù 06 C3 B9 ? 3F 3F e 65 65
ì 07 C3 AC A 41 41 f 66 66
ò 08 C3 B2 B 42 42 g 67 67
_ 11 5F C 43 43 h 68 68
SP 20 20 D 44 44 i 69 69
! 21 21 E 45 45 j 6A 6A
22 22 F 46 46 k 6B 6B
# 23 23 G 47 47 l 6C 6C
% 25 25 H 48 48 m 6D 6D
& 26 26 I 49 49 n 6E 6E
27 27 J 4A 4A o 6F 6F
( 28 28 K 4B 4B p 70 70
) 29 29 L 4C 4C q 71 71
* 2A 2A M 4D 4D r 72 72
+ 2B 2B N 4E 4E s 73 73
, 2C 2C O 4F 4F t 74 74
2D 2D P 50 50 u 75 75
. 2E 2E Q 51 51 v 76 76
0 30 30 R 52 52 w 77 77
1 31 31 S 53 53 x 78 78
2 32 32 T 54 54 y 79 79
3 33 33 U 55 55 z 7A 7A
4 34 34 V 56 56 à 7F C3 A0
5 35 35 W 57 57 1B 65 E2 82 AC
6 36 36 X 58 58
7 37 37 Y 59 59

As a consequence, the table of usable characters organized according to the ETSI coding is as follows.

b7 0 0 0 0 1 1 1 1
b6 0 0 1 1 0 0 1 1
b5 0 1 0 0 1 1 0 1
b4 b3 b2 b1 HEX 0 1 2 3 4 5 6 7
0 0 0 0 0 @
40
SP
20
0
30
P
50
p
70
0 0 0 1 1 £
C2 A3
_
5F
!
21
1
31
A
41
Q
51
a
61
q
71
0 0 1 0 2 $
24

22
2
32
B
42
R
52
b
62
r
72
0 0 1 1 3 #
23
3
33
C
43
S
53
c
63
s
73
0 1 0 0 4 è
C3 A8
4
34
D
44
T
54
d
64
t
74
0 1 0 1 5 è
C3 A9
%
25
5
35
E
45
U
55
e
65
u
75
0 1 1 0 6 ù
C3 B9
&
26
6
36
F
46
V
56
f
66
v
76
0 1 1 1 7 ì
C3 AC

27
7
37
G
47
W
57
g
67
W
77
1 0 0 0 8 ò
C3 B2
(
28
8
38
H
48
X
58
h
68
x
78
1 0 0 1 9 (
29
9
39
I
49
Y
59
i
69
y
79
1 0 1 0 A *
2A
:
3A
J
4A
Z
5A
j
6A
z
7A
1 0 1 1 B 1) +
2B
;
3B
K
4B
k
6B
1 1 0 0 C ,
2C
L
4C
l
6C
1 1 0 1 D
2D
=
3D
M
4D
m
6D
1 1 1 0 E .
2E
N
4E
n
6E
1 1 1 1 F ?
3F
O
4F
o
6F
à
C3 A0

SP corresponds to the space character

1) is not a character but indicates the code (HEX 1B) to be prefixed to indicate the characters present in the Extension table. In particular to the HEX 1B code 65 corresponds the character €, whose UTF-8 encoding is E2 82 AC. The € character is the only usable character of the Extension table.

In each cell the character relating to the encoding according to the 3GPP standard TS 23.038 version 11.0.0 (2012-10) is shown in the first line

The second line shows the relative UTF-8 code to be used in communications to the AGCOM DB

[/md_text][/vc_column][/vc_row]

Utilizziamo cookie per migliorare la tua navigazione sul sito Informativa Privacy