Using-the-pycrate-asn1-runtime.md

@@ -1128,6 +1128,7 @@ in the directory
 [pycrate_asn1dir/3GPP_MAP_29002/](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/3GPP_MAP_29002/)
 and the corresponding Python modules are in the compiled file
 [pycrate_asn1dir/MAP.py](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/MAP.py).
+This corresponds to the MAP protocol in version 3 and further.
 
 The CAP specification can be found in the 3GPP standard
 [TS 29.078](http://www.3gpp.org/DynaReport/29078.htm), the ASN.1 definition is available 
@@ -1147,15 +1148,28 @@ The *TCMessage* object which corresponds to the structure of a TCAP message tran
 needs actually to be parameterized with higher level protocol definition. Moreover, the EXTERNAL object
 used within the TCAP specification is from an older ASN.1 standard (the one from 1988)
 and does not correspond to the EXTERNAL structure defined in the pycrate ASN.1 runtime.
-For this reasons, two custom modules have been created:
+For this reasons, several custom modules have been created:
 - [pycrate_asn1dir/Pycrate-TCAP-MAP](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/Pycrate-TCAP-MAP/) 
   with the corresponding compiled file
   [pycrate_asn1dir/TCAP_MAP.py](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/TCAP_MAP.py) 
-  and the top-level object *TCAP-MAP-Message*
+  and the top-level object *TCAP-MAP-Message* in the module *TCAP-MAP-Messages*,
+  corresponding only to messages defined in MAP version 3 and further.
 - [pycrate_asn1dir/Pycrate-TCAP-CAP](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/Pycrate-TCAP-CAP/) 
   with the corresponding compiled file
   [pycrate_asn1dir/TCAP_CAP.py](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/TCAP_CAP.py); 
   CAP has multiple top-level objects defined in the *CAP-gsm* and *CAP-gprs* modules.
+  A global top-level object *TCAP-CAP-Message* is also provided in the custom module *TCAP-CAP-Messages*.
+
+Because the initial MAP version developed at ETSI in the early 90's (MAP version 1 and 2) is not completely compatible
+with the current version maintained by the 3GPP (MAP version 3 and further), two others TCAP-MAP modules are provided:
+- [pycrate_asn1dir/Pycrate-TCAP-MAPv2](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/Pycrate-TCAP-MAPv2/) 
+  with the corresponding compiled file
+  [pycrate_asn1dir/TCAP_MAPv2.py](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/TCAP_MAPv2.py) 
+  and the top-level object *TCAP-MAP-Message*, corresponding only to messages defined in MAP version 1 and 2.
+- [pycrate_asn1dir/Pycrate-TCAP-MAPv2v3](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/Pycrate-TCAP-MAPv2v3/) 
+  with the corresponding compiled file
+  [pycrate_asn1dir/TCAP_MAPv2v3.py](https://github.com/p1sec/pycrate/blob/master/pycrate_asn1dir/TCAP_MAPv2v3.py) 
+  and the top-level object *TCAP-MAP-Message*, corresponding to messages for all MAP versions.
 
 All those protocols are using the ASN.1 BER encoding.