V5.2 Database Creation (1)

V5.2 Database Creation of 18 Before You Start! – Refer to Delta Training Courses and E-Doc to learn more details about V5.2 interface and its integration in EWSD – This short procedure can be used as a sample or a cook-book while you are preparing the database for V5.2 interface with EWSD V16 – This sample is an adaptation from the procedure used in V16 testing phase – Any feedbacks and modifications should come to TSC2 Thumb rules for connecting V5.2 Interfaces to EWSD If a V5.2 interface is to be connected to the EWSD and it consists of more than one link, then the following rules must be applied: • The V5.2 interface has to be connected via LTGs • The links of a V5.2 interface have to be arranged symmetrically over both LTGs • Both LTGs must be connected to the same MBU:LTG • Since one V5.2 interface has been connected via LTGs, any other V5.2 interface which will be connected to one of those LTGs has to use the same partner LTG as the one which has been used by the first V5.2 interface on that LTG For one-link interfaces those rules not apply, however it is not recommended to use one-link interfaces (see recommendation below) The possible connections of V5.2 interfaces to the EWSD are shown below in Figure Figure shows an example of a V5.2 interface, which consist of links and C-channels (plus standby C-channels) that is connected to the EWSD Figure shows connections of V5.2 interfaces to the EWSD, which are not allowed Recommended connection rules for a V5.2 interface: • Even number of V5.2 links • C-path for PSTN protocol should be mapped to protection group1 • C-paths for ISDN protocols should be mapped to protection group2 • 1:1 redundancy of C-channels These definitions are not caused by any technical restrictions of the system They are defined to minimize the variety of O&M activities of 18 V5.2 IF V5.2 IF V5.2 IF LTG LTG LTG LTG one 8-link interface on two LTG's V5.2 IF V5.2 IF V5.2 IF V5.2 IF two 4-link interfaces on two LTG's LTG V5.2 IF V5.2 IF V5.2 IF V5.2 IF LTG four 1-link interfaces on one LTG (this type of connection is possible, but it is against the recommended connection rules) four 2-link interfaces on two LTG's Figure 1: Possible connections of V5.2 interfaces to the EWSD of 18 LTG AN a/b V5.2 Interface EWSD max C-Channel ISDN BA LTGx PCM 30 AN V5.1 V5.1 max C-Channel Figure 2: Example of an 8-link V5.2 connection to the EWSD of 18 LTGy V5.2 IF V5.2 IF LTG V5.2 IF LTG V5.2 IF LTG LTG 4-link interface on one LTG two 4-link interfaces connected asymetrically to two LTG's V5.2 IF V5.2 IF LTG LTG LTG two 4-link interfaces on three LTG's (chaining) Figure 3: Connections that are not allowed of 18 Administration Notices Creating and Canceling V5 links The creation or cancellation of V5.2 links is only allowed if every other existing link of the V5.2 interface has the operation state maintenance blocked (MBL) or planned (PLA) Modification of time slot usage - The modification of the usage of a time slot (bearer channel “BCH” to communication channel “CCH” and vice versa) can be done by using of the MML command “MOD V5TS” with the parameter “USAGE” - The modification is only allowed if every link of the V5.2 interface has the operation state maintenance blocked (MBL) or planned (PLA) - The modification of a time slot 15 and/or 31 from BCH to CCH is only allowed when all available time slots 16 (at each link of the v5.2 interface) have been already used as communication channels - The modification of a time slot 16 from CCH to BCH is only allowed when neither time slots 15 nor time slots 31 of any link of the V5.2 interface are used as communication channels - If a V5.2 interface consists of more than one link, the arrangement of the time slots, which are used as communication channels, must be symmetrical over both LTGs Modification of C-channel assignment - The assinment of C-channels to time slots can be modified with the MML command „MOD V5CMCHAN“ - The modification is only allowed if every link of the V5.2 interface has the operation state maintenance blocked (MBL) or planned (PLA) Restrictions of V5.2 interface connection via LTGs - A V5.2 interface that exists of more than one link must be connected to the EWSD via LTGs This is necessary to apply requirements of redundancy Remark: The following restriction does not exist in case of MBD It has to be considered only in case of a “classical” MB - The active message channel of those LTGs must be connected on the CP via the same MBU:LTG This is needed to allow sending of reports between both LTGs without using the CP The following table shows the possible combinations of LTGs of 18 A B C D E F G H 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Table 1: Connected LTGs via the same MBU:LTG Explanation to Table 1: • All LTGs with LTG numbers that are listed in columns A, C, F and H (columns with white background) of Table are connected with the active message channel via the same MBU:LTG and can be combined for connecting a V5.2 interface • All LTGs with LTG numbers that are listed in columns B, D, E and G (columns with gray background) of Table are connected with the active message channel via the same MBU:LTG and can be combined for connecting a V5.2 interface Configuration and Administration of DIU - DIUs that are used for connecting a V5.2 interface are created by using the MML command “CR LTU” (as usual for EWSD) However the MML command “CONF DIU” will be rejected in case of DIU that carries a V5.2 link The configuration of those DIUs is done implicitly in case of executing the V5.2 link configuration (MML command “CONF V5LINK”) - The diagnosis of the DIU can be initiated by using the MML command “DIAG DIU” as for any other DIU of 18 PROCEDURE DESCRIPTION I Creation of an LTG with loadtype V52 Following example shows the creation of the LTG, DIUs and code receivers, which can be used afterwards for a V5.2 interface CR LTG: CR LTU: CR LTU: CR LTU: CR LTU: CR LTU: LTG=0-24, TYPE=LTGB, LDPARP=52; LTG=0-24, LTU=5, TYPE=PMA; /* High performance SILC */ LTG=0-24, LTU=0, TYPE=D30, APPLIC=V52IF; LTG=0-24, LTU=1, TYPE=D30, APPLIC=V52IF; LTG=0-24, LTU=2, TYPE=D30, APPLIC=V52IF; LTG=0-24, LTU=3, TYPE=D30, APPLIC=V52IF; Notes: - In general, PHMA module is not madatory because SILC function can be integrated in LTGM/N itself However, without PHMA, processing power of LTG for V5.2 will be much lower PHMA is normally offered CR CRMOD: LTG=0-24, CRMOD=0, TYPE=CRPC; CR CRMOD: LTG=0-24, CRMOD=1, TYPE=CRPC; CONF CR: LTG=0-24, CRPOS=0, OST=MBL; CONF CR: LTG=0-24, CRPOS=0, OST=ACT; CONF CR: LTG=0-24, CRPOS=1, OST=MBL; CONF CR: LTG=0-24, CRPOS=1, OST=ACT; CR LTU: LTG=0-24, LTU=6, TYPE=V03; CR LTU: LTG=0-24, LTU=6, TYPE=V03; CONF CR: LTG=0-24, LCPOS=06-0, OST=MBL; CONF CR: LTG=0-24, LCPOS=06-1, OST=MBL; CONF CR: LTG=0-24, LCPOS=06-0, OST=ACT; CONF CR: LTG=0-24, LCPOS=06-1, OST=ACT; II EWSD V5.2 database : links, no packet data Please note that the ISDN subscribers are created without any services It is assumed that the exchange adds the default services: CMSPEECH, TEL3K, CMUNRST, /