Revision: d8beb9db8f57
Author:   Normandes Junior <[email protected]>
Date:     Tue Dec  4 11:41:30 2012
Log:      Update issue 14

Providing more documentation

On branch master
Changes to be committed:

        modified:   docs/sources/src/main/resources/en-US/Author_Group.xml
        modified:   
docs/sources/src/main/resources/en-US/Chapter-Introduction.xml
modified: docs/sources/src/main/resources/en-US/Chapter-Source_Build_Binary.xml new file: docs/sources/src/main/resources/en-US/images/binnar-structure.png new file: docs/sources/src/main/resources/en-US/images/eir-architecture.png new file: docs/sources/src/main/resources/en-US/images/eir-connection-example1.png new file: docs/sources/src/main/resources/en-US/images/eir-return-types.png

http://code.google.com/p/jeir/source/detail?r=d8beb9db8f57

Added:
 /docs/sources/src/main/resources/en-US/images/binnar-structure.png
 /docs/sources/src/main/resources/en-US/images/eir-architecture.png
 /docs/sources/src/main/resources/en-US/images/eir-connection-example1.png
 /docs/sources/src/main/resources/en-US/images/eir-return-types.png
Modified:
 /docs/sources/src/main/resources/en-US/Author_Group.xml
 /docs/sources/src/main/resources/en-US/Chapter-Introduction.xml
 /docs/sources/src/main/resources/en-US/Chapter-Source_Build_Binary.xml

=======================================
--- /dev/null   
+++ /docs/sources/src/main/resources/en-US/images/binnar-structure.png Tue Dec 4 11:41:30 2012
Binary file, no diff available.
=======================================
--- /dev/null   
+++ /docs/sources/src/main/resources/en-US/images/eir-architecture.png Tue Dec 4 11:41:30 2012
Binary file, no diff available.
=======================================
--- /dev/null   
+++ /docs/sources/src/main/resources/en-US/images/eir-connection-example1.png Tue Dec 4 11:41:30 2012
Binary file, no diff available.
=======================================
--- /dev/null   
+++ /docs/sources/src/main/resources/en-US/images/eir-return-types.png Tue Dec 4 11:41:30 2012
Binary file, no diff available.
=======================================
--- /docs/sources/src/main/resources/en-US/Author_Group.xml Wed Oct 31 10:52:43 2012 +++ /docs/sources/src/main/resources/en-US/Author_Group.xml Tue Dec 4 11:41:30 2012
@@ -6,16 +6,16 @@
 <authorgroup
        id="authors">
        <author>
-               <firstname>Normandes</firstname>
-               <surname>Junior</surname>
-               <email>&AUTHOR.EMAIL.NORMANDES;</email>
-       </author>
-       <author>
                <firstname>Amit</firstname>
                <surname>Bhayani</surname>
                <email>&AUTHOR.EMAIL.AMIT;</email>
        </author>
        <author>
+               <firstname>Normandes</firstname>
+               <surname>Junior</surname>
+               <email>&AUTHOR.EMAIL.NORMANDES;</email>
+       </author>
+       <author>
                <firstname>Sergey</firstname>
                <surname>Vetyutnev</surname>
                <email>&AUTHOR.EMAIL.SERGEY;</email>
=======================================
--- /docs/sources/src/main/resources/en-US/Chapter-Introduction.xml Wed Oct 31 10:52:43 2012 +++ /docs/sources/src/main/resources/en-US/Chapter-Introduction.xml Tue Dec 4 11:41:30 2012
@@ -35,13 +35,60 @@
                        <para>
EIR (Equipment Identity Register) is a network element connected to Mobile SoftSwitch Center (MSC) that knows if some IMEI is allowed to be registered or not.
                        </para>
+                       <para>
+ It is so important as a network element because operators can protect their customers and because in some countries is mandatory.
+                       </para>
+                       <para>
+ The message exchange between MSC and EIR is a MAP message called checkIMEI. It carries the IMEI and maybe other subscriber info as MSISDN and/or IMSI (International Mobile Subscriber Identity).
+                       </para>
+                       <para>
+ If EIR find the IMEI stored as blackList, the return will be blackListed and the mobile will not be able to register at MSC. See the picture bellow.
+                       </para>
+                       <mediaobject id="eir-connection-example1.png">
+                    <imageobject>
+ <imagedata width="450px" align="center" fileref="images/eir-connection-example1.png" format="PNG" />
+                    </imageobject>
+                    <caption>
+                            <para>EIR returning blackList to MSC.</para>
+                    </caption>
+            </mediaobject>
+
+            <para>
+               The EIR could return whiteList, blackList or grayList.
+            </para>
+            <mediaobject id="eir-return-types.png">
+                    <imageobject>
+ <imagedata width="450px" align="center" fileref="images/eir-return-types.png" format="PNG" />
+                    </imageobject>
+                    <caption>
+                            <para>EIR return types.</para>
+                    </caption>
+            </mediaobject>
                </section>

                <section id="eir_server_overview">
                        <title>EIR Server Overview</title>
                        <para>
-                               jEIR is built on top of Mobicents SS7.
+ jEIR is built on top of Mobicents SS7 and uses Cassandra as a persistent database.
                        </para>
+                       <mediaobject id="eir-architecture.png">
+                    <imageobject>
+ <imagedata width="400px" align="center" fileref="images/eir-architecture.png" format="PNG" />
+                    </imageobject>
+                    <caption>
+                            <para>EIR architecture.</para>
+                    </caption>
+            </mediaobject>
+            <para>
+ EIR has a high CAPs because each time a mobile is turn on and depending of MSC configuration, each hour a new checkIMEI request is performed.
+               So it is important that the architecture support high CAPs.
+            </para>
+            <para>
+ As the EIR just query the database about IMEI and just return if it is white, black or grayList the simultaneous calls is very short.
+            </para>
+            <para>
+ For logging purpose EIR should be able to handle a high volume of data. Think that each request could be stored.
+            </para>
                </section>
        </section>

=======================================
--- /docs/sources/src/main/resources/en-US/Chapter-Source_Build_Binary.xml Wed Nov 14 03:28:31 2012 +++ /docs/sources/src/main/resources/en-US/Chapter-Source_Build_Binary.xml Tue Dec 4 11:41:30 2012
@@ -19,7 +19,7 @@

                        <mediaobject id="binary_layout">
                <imageobject>
- <imagedata width="300px" align="center" fileref="images/binnar-structure.png" format="PNG" /> + <imagedata width="241px" align="center" fileref="images/binnar-structure.png" format="PNG" />
                 </imageobject>
                 <caption>
<para>&THIS.PLATFORM; &THIS.APPLICATION; binary layout.</para>

Reply via email to