Sligth change in design docs

srsepc/docs/source/epc_design.rst

@@ -3,16 +3,17 @@ EPC Design
 
 Code Structure
 **************
-.. blockdiag::
 
 The LTE library should include the following functionality that will be common accress multiple nodes.
 
+.. blockdiag::
+
   blockdiag {
      srsLTE -> lib -> src -> upper -> gtpu.cc;
                              upper -> gtpc.cc; 
                              upper -> s1app.cc;
                              upper -> diameter.cc;
-                src -> asn1; 
+                      src -> asn1; 
   }
 
 
@@ -22,23 +23,22 @@ The examples should aim to include the following classes
 
   blockdiag {
      srsLTE -> srsepc -> src -> mme -> mme.cc;
+                                mme -> main.cc;
                          src -> hss -> hss.cc;
+                                hss -> main.cc;
                          src -> spgw -> spgw.cc;
-               srsepc -> examples -> srsepc.cc;
+                                spgw -> main.cc;
-                         examples -> srsmme.cc;
+               srsepc -> src -> main.cc;
-                         examples -> srshss.cc;
+                         src -> epc.cc;
-                         examples -> srsspgw.cc;
    }
 
 
 MME Design
 **********
 
-The srsMME must maintain three EPC interfaces, the S1-MME, the S11 and the S6a interfaces. The S1-MME will use SCTP (one-to-many or one-to-one) sockets and the S11 will use the GTP-Cv2 protocol over UDP. The S6a will be implmented as a Diameter application over UDP.
+The srsMME must maintain three EPC interfaces, the S1-MME, the S11 and the S6a interfaces. The S1-MME will use an SCTP (many-to-one) socket and the S11 will use the GTP-Cv2 protocol over UDP. The S6a will be implmented as a Diameter application over UDP.
-
-The main loop of this 
 
-In a future, multi-threading scenario, 
+The main loop of the MME will 
 
 HSS Design
 **********