Sign In to Follow Application
View All Documents & Correspondence

System And Method For Verification Of Device Management Functionality Between User Agent Of User Equipment And Content Server In 4 G Networks

This invention explains a method and a system for verification of device management functionality between user agent of user equipment and content server in 4g networks comprising the steps of: initiating device management session and authentications by the client; checking the clients Device Information after starting the session from the client with the server; testing first server alerted session and authentications; and receiving large object and multiple messages by the client. The said method comprising the steps of: requesting the Authentication-Server for IMSI by the UE which is the UE identity for assigning a unique label for each UE-IP address; requesting the for channel type for any of the local interfaces such as IRDA, Blue tooth or a serial interface; providing the requested authentication and channel allocation; connecting all the intermediate and end nodes in the path between UE agent and the data base server through the selected interface; choosing through put as per the profiles selected for synchronization for each profile where it is filtered at data base server based on the interface and the location of UE; initiating Synchronization between, Data base server and UE where IP packet reaches the server through the interface established between UE and Server; taking the packets by the Data base server through the inter-working adaptors and intermediate nodes, till completion of synchronization of selected profile; selecting a synchronization for remote data base server, where when data packet destined for a particular UE-agent reaches 4G data base server, the IMSI is verified by the AAA server, and a channel on respective RF bearer handle the flow type and the UE-agent profile; and traversing the packet through the PLMN up to 4G data base server, using 4G intermediate nodes, where data base server takes the profiles to be synchronized from a remote UE-agent.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
04 July 2005
Publication Number
07/2005
Publication Type
Invention Field
COMPUTER SCIENCE
Status
Email
Parent Application
Patent Number
Legal Status
Grant Date
2016-05-10
Renewal Date

Applicants

WIPRO LIMITED
DODDAKANNELLI, SARJAPUR ROAD, BANGALORE 560035

Inventors

1. RAJARAM, KANYAMADUGU SURYANARAYANAIAH
NO 591, ASHIRWADHA 27TH MAIN, BTM LAYOUT II STAGE BANGALORE 560076

Specification

FIELD OF TECHNOLOGY
This invention relates to the area of Device management in a 4G wireless network. Particularly, this invention relates to setting adaptors of device a mobile terminal and a database server in 4G bearer networks. More specifically, this invention provides a system and method to do verification of system level functionalities of device management between user equipment and content of data base server in a 4G carrier networks. By incorporating the test strategy between UE (User equipment), SyncML (Synchronization mark Up language) this invention provides the ability to provide.
DESCRIPTION OF RELATED ART
The purpose of this invention is to present tests that verify the Device management functionality of the SyncML component. Focus on these tests is to test the SyncML protocol engine and content adapters. Ul application functionality tests and HW dependant system tests are specified in DM Application Ul Specification and SyncML DM System Test Specification of OMA 1.1. It is needed to execute all three tests to verify all functionality of SyncML component.
Not all test cases are possible in all platforms; possible platforms where the tests should be run are identified in the cases. When supports for new synchronization contents are implemented, corresponding test cases should be added into this test specification.
SyncML is an XML based protocol for synchronization of data between a client and a server, In a Wireless company specific Software platform SyncML is used for synchronization of respective profiles such as calendar data and contacts. SyncML is integrated in the XML Format process and the intention is to reuse as much of the already existing functionality as possible
Depending on internal configuration, the UE agent initiates Device management and network establishment with a SyncML_request on a 4G network.

1. UE performs a SyncML_request query to synchronies data on a bearer network server. The server response will contain an acknowledgement and a confirmation. The addresses of server that support the requested Device management in the 4G network according to standard OMA procedures. If the PLMN does not support the SyncML, then the Device management query returns a negative response. In this case, the UE continues with step 2.
2. The UE selects a profile from the list received in step 1, and the establishment of synchronization is performed between the UE and the server. The UE includes the user identity in the initial tunnel establishment request. The agent and server exchange information (via the Operator gateway and bearer) in order to establish a filtering policy to allow the forwarding of data packets to the UE agent.
This invention is based on the Device management in a 3G networks currently there are no 4G UE and networks. Hence there is no mechanism for the following features:
1. Device management over the air (Local method)
Device Management is a feature of SyncML (Synchronization Mark up Language) which facilitates synchronization of profiles such as device settings contacts, addresses etc. over the air. Local method uses OBEX interface for DM profiles between the UE and server.
2. Remote device management (4G bearer s)
Remote device management uses 4G bearers such as IP-WCDMA, WiMAX etc for synchronization of device settings and other profiles between server and the UE.
SUMMARY OF THE INVENTION
It is primary object of the invention to provide a system and method for testing SyncML DM in a UE agent-4G interworking system through WSP, OBEX

(Objective Exchange Protocol) and HTTP (Hyper Text Transfer Protocol) interfaces and 4G intermediate nodes.
It is another object of the invention to provide mechanisms by which the testing dependencies in System testing of SyncML i.e. reduced in 4G network scenarios
It is another object of the invention to provide mechanisms by which a UE agent is subjected to different profile and network conditions as specified in SyncML specifications (OMA-SyncML 1.x). These scenarios are based on the location of UE, type of profile request by UE and the information available on the server. The invention also provides mechanism of testing of the synchronised data labels on the Ul (User interface) in the chosen path between UE and SyncML Server.
It is another object of the invention to provide a mechanism for testing a UE in the absence of a 4G network, required UE hardware.
The present invention is related to system tests that verify the functionality of User agent of UE for Device management with a database server within a 4G network and, to resolve the above mentioned problems associated with the current systems in 2.5G and 3G networks and provides end-to-end interoperability of UE and 4G contents. This would require a test setup, which would simulate all the data conditions, originated from UE agent. From UE agent up to the selected data base server within the PLMN, all the test scenarios are proposed for verification
The system for the invention comprises of a 4th Generation UE (4G UE) emulator interconnected to a 4th Generation (4G) delivery network consisting of a database-Server, Objective Exchange Protocol (OBEX), Hyper Text Transfer Protocol (HTTP) interfaces intermediate RF interfaces which could be simulated on a TCP/IP port.
The method of the invention comprises of mechanisms, which would be solving the problems associated with the following Device management scenarios:
1. Device management is established between the UE agent and profile
adaptors within PLMN, based profiles and the gateway path. This

addressing is a logical functionality that does the authentication (AAA) in the PLMN, and decides the path to be taken by each packet. For the sake of discussion, the selected profiles under synchronization & logical functionality is shown co-existing with database-Server, but as such this functionality can be residing in any component reachable by UE agent, adaptors and 4G network. Incase its not residing along with database-Server; the information on user ID has to be exchanged between authentication server and UE. For further discussion in this proposition, all the UE profiles are shown residing in data base-Server as an example, though it doesn't mandate it to be co-existing. These profiles are applied at the UE and 4G database server. The UE receives the acknowledgement of authenticated User ID from Authentication Authorization and Accounting (AAA) server and filters based on the status and location, and distributes to the respective RF bearer, which makes data flow and real-time synchronization possible between UE agent and 4G database server.
Using the SyncML mechanism, based on profiles selected for synchronization,, it would be possible to verify the performance management based on the latency of the RF data link, which has limited packet through put in the in the current 2.5G/3G networks . Based on the bearer interfaces with the user agent, UE shall be assigning a best path for either OBEX or HTTP links. This would allow synchronization of packets either in locally or remotely. Based on the method of synchronization, two methods are provided to enable effective testing on all the 4G RF interfaces and the existing OBEX interfaces. Making use of advantages of Device management as per OMA SyncML 1.1 compared to cater for better performance, scalability and easy of implementation.
The other objects, features and advantages of the present invention will be apparent from the accompanying drawings and the detailed description as follows:

Accordingly this invention explains a method for verification of device management functionality between user agent of user equipment and content server in 4g networks comprising the steps of:
initiating device management session and authentications by the client;
checking the clients Device Information after starting the session from the client with the server;
testing first server alerted session and authentications; and receiving large object and multiple messages by the client.
Here the initiating device management session and authentications by the client includes initializing settings for the SyncML server and starting the session with the server. The initiating device management session and authentications by the client includes configuring server to require other authentication type than in the first session. The testing first server ajerted session and authentications includes starting session from the server and configuring server to require other authentication type than in the first session. The receiving large object and multiple messages by the client involves setting up server to send large object and starting session from client or from server.
Accordingly this invention explains a method for verification of device management functionality between user agent of user equipment and content server in 4g networks comprising the steps of:
requesting the Authentication-Server for IMSI by the UE which is the UE identity for assigning a unique label for each UE-IP address;
requesting the for channel type for any of the local interfaces such as IRDA, Blue tooth or a serial interface;
providing the requested authentication and channel allocation; connecting all the intermediate and end nodes in the path between UE agent and the data base server through the selected interface;
choosing through put as per the profiles selected for

synchronization for each profile where it is filtered at data base server based on the interface and the location of UE;
initiating Synchronization between, Data base server and UE where IP packet reaches the server through the interface established between UE and Server;
taking the packets by the Data base server through the inter-working adaptors and intermediate nodes, till completion of synchronization of selected profile;
selecting a synchronization for remote data base server, where when data packet destined for a particular UE-agent reaches 4G data base server, the IMSI is verified by the AAA server, and a channel on respective RF bearer handle the flow type and the UE-agent profile; and
traversing the packet through the PLMN up to 4G data base server, using 4G intermediate nodes, Where data base server takes the profiles to be synchronized from a remote UE-agent.
Here the RF bearer is a wcdma, cdma 1XEV DO or Wi MAX wherein an emulator of a UE is used in the absence of a real hardware for UE-agent. The simulated 4G bearers using a standard protocol simulator is used in place of 4G real time networks eliminating dependencies on a 4G UE and the networks. The said method is performed locally or remotely. In the local method, UE agent emulator is connected to the local server through IRDA or blue tooth, USB or a serial port. The data synchronization is initiated from UE by selecting a profile such as contacts, e-mail, MMS, video. In the remote method, establishing connection between a database server on a 4G network to the UE-agent emulator through RF bearers is done by initiating a data call and connection to a data access point on the 4G network. The synchronization request is forwarded by Access Point to the data base server on the specified interface using SyncML protocol along with IMSI, which assist 4G gateway in identifying the location from which UE is accessing the network. The Remote data base server knows the location of UE form the Access point from which the request is forwarded. The Data base server forwards the acknowledgment for the synchronization initiation

request to UE .where the information is carried over the RF interface or a 4G network simulator. The local tests are performed using an emulator set up where the setup uses a UE-agent emulator, PC suite for test cases, and a flash device to load the module under test. The remote tests are performed using a 4G network simulator with RF bearers such as wcdma, cdma 1XEv DO or Wi MAX.
Accordingly this invention explains a system for verification of device management functionality between user agent of user equipment and content server in 4g networks comprising:
means for initiating device management session and authentications by the client;
means for checking the clients Device Information after starting the session from the client with the server;
means for testing first server alerted session and authentications; and
means for receiving large object and multiple messages by the client.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
Figurel shows the different network nodes of a UE agent-4G inter-working system, involved in Device management.
Figure 2 shows the test setup with different network nodes for local Device management
Figure 3 shows the local test setup for Device management presented in SyncML 1.1, and different Object exchange protocol interfaces for local device management
Figure 4 shows the test setup for remote tests with different network elements of a 4G inter-working system, involved in establishing a channel between UE and data base server and few examples of profiles and respective adaptors.

DETAILED DESCRIPTION OF THE INVENTION
The present invention provides a system and method to test different profiles such as contacts, calendar, video conference, wireless village etc., available on a user agent of a 4G UE with the data base server of a 4G network either through local method or remote method.
The method of the invention comprises of mechanisms of testing the Device management UE to a local data base server with UE requesting the Authentication-Server for IMSI, which is the UE identity for assigning a unique label for each UE-IP address and the channel type requested for any of the local interfaces such as IRDA, Blue tooth or a serial interface. Up on authentication and channel allocation, all the intermediate and end nodes in the path between UE agent and the data base server are connected through the selected interface. Through put is chosen as per the profiles selected for synchronization for each profile is filtered at data base server based on the interface and the location of UE. When Synchronization between, Data base server -UE is initiated IP packet reaches the server through the interface established between UE and Server. Data base server takes the packets through the inter-working adaptors and intermediate nodes, till completion of synchronization of selected profile. When an synchronization is selected for remote data base server, data packet destined for a particular UE-agent reaches 4G data base server, the IMSI is verified by the AAA server, and a channel on respective RF bearer such as W cdma, cdma 1XEV DO or Wi MAX will handle the flow type and the UE-agent profile. The packet traverses through the PLMN up to 4G data base server, using 4G intermediate nodes, where data base server takes the profiles to be synchronized from a remote UE-agent. In the absence of a real hardware for UE-agent, an emulator of a UE is used. Similarly in place of 4G real time networks, simulated 4G bearers using a standard protocol simulator is sued. This would be eliminating dependencies on a 4G UE and the networks. This invention would be providing all the advantages of testing the functionality of a Device management of a UE-agent on a 4G network and ensure interoperability of the system.
Figurel shows the different network nodes of a UE agent-4G inter-working system, involved in Device management.

Setup consists of user agent flashed on user equipment, which is under test, simulated OR real time 4G networks and a content server which houses the profiles which needs to be managed in both directions. The setup hold good for both one-way and two-way device management of profiles such as contacts, calendar, scheduler and email. These profiles could set from an UE to content server vise versa.
Figure 2 shows the test setup with different network nodes for local Device management
Setup uses a UE which is a prototype mobile handset, a flashing device to upload the synchronization software image, a PC suite housing the test cases and an OBEX connectivity providing various interfaces for synchronization
Figure 3 shows the local test setup for Device management presented in SyncML 1.1, and different Object exchange protocol interfaces for local device management
Local method is used for device management of profiles on a standard OBEX interface as per OMA specifications. The local interfaces include Blue tooth, Infrared (IrDA) and serial connectivity. Profiles under transfer between the server and the UE will pass through the local interfaces and ensure bi-directional device management
Figure 4 shows the test setup for remote tests with different network elements of a 4G inter-working system, involved in establishing a channel between UE and data base server and few examples of profiles and respective adaptors.
Remote tests are done either in a real network environment OR in a simulated test environment using a dummy server. A protocol/network simulator is used for simulation of a radio access network, which is connected to the content server with profiles via an internet protocol port with a known address. The dummy server and a protocol network simulator could be developed using the available 3GPP and OMA specifications
The subsequent subsections detail the test scenarios and the method of testing Used in the invention:

Operation of the Invention
fication of Device management is performed as mentioned below:
In a local method, UE agent emulator is connected to the local server through IRDA or blue tooth, USB or a serial port. A profile such as contacts, e-mail, MMS, video is selected and Device management is initiated from UE.
In remote method, as database server on a4G network is connected to the UE-agent emulator through RF bearers such as wcdma, cdmalx EV DO or Wl MAX. This is established by initiating a data call and connection to a data access point on the 4G networks.
This synchronization request is forwarded by Access Point to the data base server on the specified interface using SyncML protocol along with IMSI, which would assist 4G gateway in identifying the location from which UE is trying to access the network.
Remote data base server knows the location of UE form the Access point
from which the request is forwarded. Data base server forwards DM the
acknowledgment for the synchronization initiation request to UE is
attached to it. This information is carried over the RF interface or a 4G
network simulator.
All the local tests are performed using an emulator set up as given in the
figure 2. The setup uses a UE-agent emulator, PC suite for test cases,
flash device to load the software under test.
All the remote tests are performed using a 4G network simulator with RF
bearers such as wcdma, cdma 1XEv DO or Wi MAX. The test setup is
given in figure 4.
A test methodology to address end to end test life cycle from unit tests to
Interoperability and maintenance tests are illustrated in figure 4
An illustrative Example for the operation of the invention:


The above-presented description is of the best mode contemplated for carrying out the present invention. The manner and process of making and using it is in such a full, clear, concise and exact terms as to enable to any person skilled in the art to which it pertains to make and use this invention. New embodiments in particular, which also lie within the scope of the invention can be created, in which different details of the different examples can in a purposeful way be combined with one another.
This invention is however, susceptible to modifications and alternate constructions from that disclosed above which are fully equivalent. Consequently, it is not the intention to limit this invention to the particular embodiment disclosed. On the contrary, the intention is to cover all modifications and alternate constructions coming within the spirit and scope of the invention as generally expressed by the following claims which particularly point out and distinctly claim the subject matter of the invention.


I CLAIM
1. A method for verification of device management functionality between user agent of user equipment and content server in 4g networks comprising the steps of:
initiating device management session and authentications by the client; checking the clients Device Information after starting the session from the client with the server;
testing first server alerted session and authentications; and receiving large object and multiple messages by the client.
2. A method as claimed in claim 1 wherein initiating device management session and authentications by the client includes initializing settings for the SyncML server and starting the session with the server.
3. A method as claimed in claim 1 wherein initiating device management session and authentications by the client includes configuring server to require other authentication type than in the first session .
4. A method as claimed in claim 1 wherein testing first server alerted session and authentications includes starting session from the server and configuring server to require other authentication type than in the first session .
5. A method as claimed in claim 1 wherein receiving large object and multiple messages by the client involves setting up server to send large object and starting session from client or from server.
6. A method for verification of device management functionality between user agent of user equipment and content server in 4g networks comprising the steps of:
requesting the Authentication-Server for IMSI by the UE which is the UE identity for assigning a unique label for each UE-IP address;

requesting the for channel type for any of the local interfaces such as IRDA, Blue tooth or a serial interface;
providing the requested authentication and channel allocation;
connecting all the intermediate and end nodes in the path between UE agent and the data base server through the selected interface;
choosing through put as per the profiles selected for synchronization for each profile where it is filtered at data base server based on the interface and the location of UE;
initiating Synchronization between, Data base server and UE where IP packet reaches the server through the interface established between UE and Server;
taking the packets by the Data base server through the inter-working ■ adaptors and intermediate nodes, till completion of synchronization of selected profile;
selecting a synchronization for remote data base server, where when data packet destined for a particular UE-agent reaches 4G data base server, the IMSI is verified by the AAA server, and a channel on respective RF bearer handle the flow type and the UE-agent profile; and
traversing the packet through the PLMN up to 4G data base server, using 4G intermediate nodes, where data base server takes the profiles to be synchronized from a remote UE-agent.
7. A method as claimed in claim 1 wherein the RF bearer is a wcdma, cdma 1XEV DO or Wi MAX.
8. A method as claimed in claim 1 wherein an emulator of a UE is used in the absence of a real hardware for UE-agent.
9. A method as claimed in claim 1 wherein simulated 4G bearers using a standard protocol simulator is used in place of 4G real time networks eliminating dependencies on a 4G UE and the networks.
10. A method as claimed in claim 1 wherein the said method is performed locally or
remotely.

11. A method as claimed in claim 5 wherein in the local method, UE agent emulator is connected to the local server through IRDA or blue tooth, USB or a serial port.
12. A method as claimed in claim 6 wherein data synchronization is initiated from UE by selecting a profile such as contacts, e-mail, MMS, video.
13. A method as claimed in claim 5 wherein in the remote method, establishing connection between a database server on a 4G network to the UE-agent emulator through RF bearers is done by initiating a data call and connection to a data access point on the 4G network.

14. A method as claimed in claim 1 wherein the synchronization request is forwarded by Access Point to the data base server on the specified interface using SyncML protocol along with IMSI, which assist 4G gateway in identifying the location from which UE is accessing the network.
15. A method as claimed in claim 1 wherein the Remote data base server knows the location of UE form the Access point from which the request is forwarded.
16. A method as claimed in claim 1 wherein the Data base server forwards the acknowledgment for the synchronization initiation request to UE ,where the information is carried over the RF interface or a 4G network simulator.
»
17. A method as claimed in claim 1 wherein the local tests are performed using an emulator set up where the setup uses a UE-agent emulator, PC suite for test cases, and a flash device to load the module under test.
18. A method as claimed in claim 1 wherein the remote tests are performed using a 4G network simulator with RF bearers such as wcdma, cdma 1XEv DO or Wi MAX.
19. A system for verification of device management functionality between user agent of user equipment and content server in 4g networks comprising:

means for initiating device management session and authentications by the client;
means for checking the clients Device Information after starting the session from the client with the server;
means for testing first server alerted session and authentications; and
means for receiving large object and multiple messages by the client.
*
20. A method for verification of device management functionality between user
agent of user equipment and content server in 4g networks substantially as herein
described particularly with reference to the drawings.
21. A system for verification of device management functionality between user
agent of user equipment and content server in 4g networks substantially as herein
described particularly with reference to the drawings.

Documents

Application Documents

# Name Date
1 0855-che-2005-form 13.pdf 2011-09-03
2 0855-che-2005-form 1.pdf 2011-09-03
3 0855-che-2005-drawings.pdf 2011-09-03
4 0855-che-2005-description(complete).pdf 2011-09-03
5 0855-che-2005-correspondnece-others.pdf 2011-09-03
6 0855-che-2005-claims.pdf 2011-09-03
7 0855-che-2005-assignement.pdf 2011-09-03
8 0855-che-2005-abstract.pdf 2011-09-03
9 855-CHE-2005 POWER OF ATTORNEY 22-10-2012.pdf 2012-10-22
10 855-CHE-2005 FORM-13 22-10-2012.pdf 2012-10-22
11 855-CHE-2005 FORM-1 22-10-2012.pdf 2012-10-22
12 855-CHE-2005 EXAMINATION REPORT REPLY RECEIVED 22-10-2012.pdf 2012-10-22
13 855-CHE-2005 ASSIGNMENT 22-10-2012.pdf 2012-10-22
14 855-CHE-2005 POWER OF ATTORNEY 22-10-2012.pdf 2012-10-22
15 855-CHE-2005 FORM-13 22-10-2012.pdf 2012-10-22
16 855-CHE-2005 FORM-1 22-10-2012.pdf 2012-10-22
17 855-CHE-2005 ASSIGNMENT 22-10-2012.pdf 2012-10-22
18 Power of Attorney [16-09-2015(online)].pdf 2015-09-16
19 Form 6 [16-09-2015(online)].pdf 2015-09-16
20 Examination Report Reply Recieved [16-09-2015(online)].pdf 2015-09-16
21 Description(Complete) [16-09-2015(online)].pdf 2015-09-16
22 Assignment [16-09-2015(online)].pdf 2015-09-16
23 855-CHE-2005 FORM-6 16-09-2015.pdf 2015-09-16
24 855-CHE-2005 EXAMINATION REPORT REPLY RECEIVED 16-09-2015.pdf 2015-09-16
25 855-CHE-2005-Power of Attorney-220915.pdf 2015-09-25
26 855-CHE-2005-OTHERS-220915.pdf 2015-09-25
27 855-CHE-2005-Other Patent Document-220915.pdf 2015-09-25
28 855-CHE-2005-Form 5-220915.pdf 2015-09-25
29 855-CHE-2005-Form 3-220915.pdf 2015-09-25
30 855-CHE-2005-Form 2(Title Page)-220915.pdf 2015-09-25
31 855-CHE-2005-Examination Report Reply Recieved-220915.pdf 2015-09-25
32 855-CHE-2005-Drawing-220915.pdf 2015-09-25
33 855-CHE-2005-Claims-220915.pdf 2015-09-25
34 855-CHE-2005-Amended Pages Of Specification-220915.pdf 2015-09-25
35 855-CHE-2005-Abstract-220915.pdf 2015-09-25
36 Marked up Claims_Granted 273012_10-05-2016.pdf 2016-05-10
37 Drawings_Granted 273012_10-05-2016.pdf 2016-05-10
38 Description_Granted 273012_10-05-2016.pdf 2016-05-10
39 Claims_Granted 273012_10-05-2016.pdf 2016-05-10
40 Abstract_Granted 273012_10-05-2016.pdf 2016-05-10
41 Form 27 [24-03-2017(online)].pdf 2017-03-24
42 855-CHE-2005-RELEVANT DOCUMENTS [03-03-2018(online)].pdf 2018-03-03
43 855-CHE-2005-RELEVANT DOCUMENTS [17-03-2018(online)].pdf 2018-03-17
44 855-CHE-2005-RELEVANT DOCUMENTS [16-02-2019(online)].pdf 2019-02-16

ERegister / Renewals

3rd: 08 Jun 2016

From 04/07/2007 - To 04/07/2008

4th: 08 Jun 2016

From 04/07/2008 - To 04/07/2009

5th: 08 Jun 2016

From 04/07/2009 - To 04/07/2010

6th: 08 Jun 2016

From 04/07/2010 - To 04/07/2011

7th: 08 Jun 2016

From 04/07/2011 - To 04/07/2012

8th: 08 Jun 2016

From 04/07/2012 - To 04/07/2013

9th: 08 Jun 2016

From 04/07/2013 - To 04/07/2014

10th: 08 Jun 2016

From 04/07/2014 - To 04/07/2015

11th: 08 Jun 2016

From 04/07/2015 - To 04/07/2016

12th: 08 Jun 2016

From 04/07/2016 - To 04/07/2017

13th: 13 Jun 2017

From 04/07/2017 - To 04/07/2018

14th: 26 Jun 2018

From 04/07/2018 - To 04/07/2019