FIELD OF TECHNOLOGY
This invention relates to the area of Data synchronization in a 4G wireless network. Particularly, this invention relates to adaptors of different profiles within 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 data synchronization 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 Data Synchronization functionality of the SyncML component. Focus on these tests is to test the SyncML protocol engine and content adapters. It is needed to execute all the functional tests of adaptors and profiles between UE agent and the 4G content server to verify effectiveness of data synchronization in the real time and simulated scenarios.
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 data synchronization 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 data synchronization in the 4G networks according to standard OMA procedures. If the PLMN does not support the SyncML, then the data synchronization 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.
Currently there are no 4G UE and networks. Hence there is no mechanism for the following features:
1. Synchronization for device management
Device management is the feature in the SyncML application, for the device settings either locally through an OBEX interface or remotely through a 4G radio access network. DM helps in device settings and profiles to be controlled from a local OR remote database server
2. Synchronization of data beyond 1000 bits long
User Interface specs as per OMA 1.x OR 2.x is applicable to a maximum data string of 1000 bits long, beyond which the user interface has to be designed for a higher pixel ratio of the order of 5Megapixels/frame and beyond. The current invention limits the User interface form factor supporting 1000 bits long only.
SUMMARY OF THE INVENTION
It is primary object of the invention to provide a system and method for testing SyncML DS in a UE agent-4G interworking system through WSP, OBEX and HTTP 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 data synchronization 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 provide 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 4G UE emulator interconnected to a 4G delivery network consisting of a database-Server, OBEX, 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 data synchronization scenarios: SyncML Sync protocol
• Sync Initialization
• Two way sync
• One way sync, from either side
• Server alerted sync
• Authentication

• Large object handling
• Device capability exchange
• ID mapping of data items
Adaptors
• Synchronization of contacts
• Synchronization of calendar
• Synchronization of e-mail
• Synchronization of MMS
• Synchronization of Video telephony

1. Data synchronization is established between the UE agent and profile adaptors within PLMN, based profiles and the gateway path. This addressing is a logical functionality, which 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 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.
2. 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.
3. 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.
4. Making use of advantages of data synchronization as per OMA SyncML 1.1 compared to cater for better performance, scalability and easy of implementation.
Accordingly this invention explains a method for verification of data synchronization between user agent and content server in 4g networks comprising the steps of:
synchronization with server where all the contents are selected ;
authenticating with the server;
receiving and sending Multiple Messages;
verifying number of changes;
synchronizing local database to multiple remote database; and
mixing multiple sync types in the same session.
In this method synchronization with server includes checking that synchronization runs through without errors and Sync header has correct values. Synchronization with server includes checking that Device Information of client is sent. The authenticating with the server includes checking that server challenges basic authentication scheme and checking that the client sends SyncML. In the invention receiving and sending multiple messages include checking that client added all server items for all data types. Here the wherein verifying number of changes includes checking that new items are added to the server and checking that number of changes match to the count of new items.

Accordingly this invention also explains a method for verification of data synchronization between user agent 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 data synchronization between user agent and content server in 4g networks comprising:
means for synchronization with server where all the contents are selected;
means for authenticating with the server;
means for receiving and sending Multiple Messages;
means for verifying number of changes;
means for synchronizing local database to multiple remote database; and
means for mixing multiple sync types in the same session.
The other objects, features and advantages of the present invention will be apparent from the accompanying drawings and the detailed description as
follows:

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
Figurel shows the different network nodes of a UE agent-4G inter-working system, involved in data synchronization.
Figure 2 shows the test setup with different network nodes for local data synchronization.
Figure 3 shows the local test setup for data synchronization presented in SyncML 1.1, and different OBEX interfaces for local synchronization.
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 data synchronization 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 a 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 wcdma, 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 used. 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 data synchronization 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 data synchronization.
Setup consists of user agent flashed on user equipment, which is under test, simulated OR real time 4G network and a content server which houses the profiles which needs to be synchronized in both directions. The setup hold good for both one-way and two-way synchronization of profiles such as contacts, calendar, scheduler and email. These profiles could synchronized from an UE to content server vise versa.
Figure 2 shows the test setup with different network nodes for local data synchronization
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 data synchronization presented in SyncML 1.1, and different OBEX interfaces for local synchronization
Local method is used for synchronization of profiles on a standard OBEX interface as per OMA specifications.The local interfaces include Blue tooth, Infrared (IrDA) and serial connectivity. Profiles under synchronization between the server and the UE will pass through the local interfaces and ensure bidirectional synchronization.
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
Verification of data synchronization is performed as mentioned below:
1. 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 Data synchronization is
initiated from UE.
2. 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
Wi MAX. This is established by initiating a data call and connection to a
data access point on the 4G network.
3. 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.
4. Remote data base server knows the location of UE form the Access point from which the request is forwarded. Data base server forwards 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.
5. 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.
6. 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.
7. 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:
An illustrative example for the invention is given here.
Test synchronization with server (SyncHdr, Devlnfo, Sync)
• Create synchronization profile with all possible contents selected
• Start synchronisation with server
Check that synchronisation runs through without errors.
Check that Sync header has correct values
Check that Device Information is sent (client's device information)
• Mod has correct phone model number
• SWV has correct Software version number
• Device ID has correct IMEI value
• Check that Device Information is received (server's device information)
• Check that supports same content formats as client, otherwise test should end to error -synchronisation not completed
Check that correct databases (same as selected in synchronisation profile) are alerted with slow-sync alert code
Test SyncML basic authentication with the server
• Start synchronization with server
• Start synchronisation again
• Check that synchronisation runs through without errors.
. • Check that server challenges basic authentication scheme (SyncML: auth-basic).

• Check that client sends SyncML: auth-basic credentials automatically in the second
synchronisation without challenge.
Receiving Multiple Messages
• Set all supported data types for synchronisation
• Create enough data items for each data type in server so that MaxMsgSize exceeds (for each data type)
• Start synchronisation with server
• Check that synchronisation runs through without errors.
• Check that multiple messages occurred (i.e. when server send it's data to client, it does not include final flag in (first) modification packet and that client asks more modifications with next alert code.
• Check that client added all server items for all data types.
Sending Multiple Messages
• Set all supported data types for synchronisation
• Create enough data items for each data type in client so that MaxMsgSize exceeds (for each data type)
• Start synchronisation with server
• Check that synchronisation runs through without errors.
• Check that multiple messages occurred (i.e. when client send its data to server, it does not include final flag in (first) modification packet and that server asks more modifications with next alert code.
• Check that server added all server items for all data types (and that client actually sent all data it had).

Verification of Number of changes
• Set all supported data types for synchronisation
• Create over 10 new item to each data type (database) in client
• Synchronise
• Create 1 to 5 new items to each database in client
• Modify 1 to 5 items in each database in client
• Delete 1 to 5 item in each database in client
• Synchronise
• Check that synchronisation runs through without errors.
• Check that new items are added to the server.
• Check that number of changes match to the count of new items.
• Check that second synchronisation runs through without errors.
• Check that new, modified and deleted items are synchronised to the server.
• Check that number of changes match to the count of (new+modified+deleted) items.

Synchronizing local database to multiple remote database
• Create two (2) synchronisation profiles that have different server but same local database. Use all contents supported for the platform.
• For all possible contents: create 5 new items in client, 5 new items at server 1 and also in server 2
• Synchronise with server 1
• Synchronise with server 2
• Synchronise with server 1
• For all possible contents: Modify 1 item in client and 1 item in server 1 and 1 item in server 2
• Synchronise with server 1
• Synchronise with server 2
• Synchronise with server 1
• For all possible contents: Delete 1 item in client and 1 item in server 1 and 1 item in server 2
• Synchronise with server 1
• Synchronise with server 2
• Synchronise with server 1
• Check that synchronisation runs through without errors.
• Check after synchronisation every synchronisation that both databases (what were
synchronised) are exactly in the same level.

• Check that all three databases are in the same level in the end (i.e. synchronised
correctly) for all contents.
Mixed multiple sync types in the same session
• Select two database which have different sync types: two-way and one-way from server
• Synchronise
• Select two databases which have different sync types: one-way from server and one way from client
• Synchronise
• Select two databases which have same sync type: two-way and two-way
• Synchronise
• Select two databases which have same sync type: one-way and one-way
• Synchronise
• Check that synchronisation runs through without errors.
• Check that in every session only items that were meant to synchronise was
synchronised.
Canceling synchronization
• Create data for synchronization
• Start synchronisation, cancel during connecting phase
• Synchronise, modify data
• Start synchronisation, cancel during initialization phase
• Synchronise, modify data
• Start synchronisation, cancel during synchronisation phase
• Synchronise, modify data
• Start synchronisation, cancel during finalizing phase
• Synchronise
• Check that synchronisation can be cancelled (does not "hang up").
• Check that following synchronisation runs through without errors and correct items are synchronized.
• Check that client does not initiate slow sync.
• Check that there is no memory leak.

Update existing item at server
• Modify existing calendar item in server
• Modify existing calendar item in server
• Start synchronisation
• Check that synchronisation runs through without errors.
• Check that items are modified in the client.
* *
• [Check that client sends status XXX back to server replace.]
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.

GLOSSARY OF TERMS AND DEFINITIONS THEREOF
AAA Authentication, Authorization, Accounting,
cdma coded decimal multiple access
DS Data Synchronization
DM Device Management
GSM Global System for Mobile communication
• *
GPRS General Packet Radio Service
HTTP Hyper Text Transfer Protocol
HW Hardware
IP Internet Protocol
IRDA Infrared Access
MMS Multimedia message service
OBEX Object Exchange Protocol
OMA Open Mobile alliance
PLMN Public Land Mobile network
RF Radio Frequency
SyncML Synchronization mark up language
USB Universal serial bus
UE User Equipment
Ul User Interface
UMTS Universal Mobile Telephone system
Wi MAX wide band multiple access
WSP wireless session protocol
4G 4th Generations
3GPP Third generation partnership project

I CLAIM:
1. A method for verification of data synchronization between user agent and content
server in 4g networks comprising the steps of:
synchronization with server where all the contents are selected ;
authenticating with the server;
receiving and sending Multiple Messages;
verifying number of changes;
synchronizing local database to multiple remote database; and
mixing multiple sync types in the same session.
2. A method as claimed in claim 1 wherein synchronization with server includes checking that synchronization runs through without errors and Sync header has correct values.
3. A method as claimed in claim 1 wherein synchronization with server includes checking that Device Information of client is sent.
4. A method as claimed in claim 1 wherein authenticating with the server includes checking that server challenges basic authentication scheme and checking that the client sends SyncML.
5. A method as claimed in claim 1 wherein receiving and sending multiple messages include checking that client added all server items for all data types.

6. A method as claimed in claim 1 wherein verifying number of changes includes checking that new items are added to the server and checking that number of changes match to the count of new items.
7. A method for verification of data synchronization between user agent 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.
* ■
8. A method as claimed in claim 1 wherein the RF bearer is a wcdma, cdma 1XEV DO or Wi MAX.
9. 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.

10. 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.
11. A method as claimed in claim 1 wherein the said method is performed locally or remotely.
12. 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.
13. 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.

7
14. 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.
15. 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.
16. 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.
17. 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.
18. 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.
19. 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.

20. A system for verification of data synchronization between user agent and content
server in 4g networks comprising:
means for synchronization with server where all the contents are selected;
means for authenticating with the server;
means for receiving and sending Multiple Messages;
means for verifying number of changes;
means for synchronizing local database to multiple remote database; and
means for mixing multiple sync types in the same session.
21. A method for verification of data synchronization between user agent and content server in 4g substantially as herein described particularly with reference to the drawings.
22. A system for verification of data synchronization between user agent and content server in 4g substantially as herein described particularly with reference to the drawings.