MRV Communications MR2228-S2C User Manual Page 1

215Chapter – 6 IMS Client Development and Deployment 6.1 Introduction 6.2 Other IMS Clients 6.2.1 FOKUS Open IMS Client Lite 6.2.2 IMS-

224ii) Connected, Limited Device Configuration (CLDC) CLDC is designed for smaller devices than those targeted by the CDC. Such devices include mobi

225 MIDP complements the CLDC by minimizing both the memory and power required for limited devices. It also provides the basic API that i

2266.4.1 SIP API for J2ME Nokia Corporation is the specification lead within the JCP in the development of the SIP API for J2ME, which was giv

227major components of this package will be defined, but the full specification of the package can be found on the Java Community Process (JCP) webs

228 There are two ways to process an incoming request using the JSR 180 API. The first method uses the synchronous approach, which involves blocking

229 Figure 6.10: IMS Client Stack (Based on [131]) Depicted in Figure 6.11 is the position of a proposed IMS Client on the existing I

230 Figure 6.12: Session Establishment Main Flow diagram

231 Figure 6.13: IMS Client Sequence Diagram [135] The system is designed to perform the following functions, as shown in Figure 6.13: o Regi

232mechanism o Terminating a session o Exchanging text messages (Instant Messaging) o Cancelling the early session using CANCEL method o Ending the

233 Figure 6.14: IMS Client Display before Registration The Java code to create the above display is provided in Appendix H. In order to avoid

2166.8.1 Registration Request 6.8.2 Invite Request 6.8.3 Trying Response 6.8.4 Session Progress Response 6.8.5 PRACK Request

234to allow the user to establish a session or to de-register from the IMS network. The sequence diagram for session establishmen

235destination SIP URI, and pressing an "Invite" command or return to the main display be pressing the "Back" command. Whe

236a=des:qos mandatory local sendrecv a=des:qos none remote sendrecv 6.5.3 Session Description Protocol (SDP) Offer/Answer When establishing t

2375) client_connection.setHeader("Content-Type","text/plain"); 6) client_connection.setHeader("Content-Length", Integ

238Figure 6.18 depicts the commands appearing on an IMS Client display during IM communication. A "Send" command is used to sen

239two users. The discussion of the implementation of the IMS Client is presented in this subsection. i. Creating the IMS Client A

240into a mobile device emulator or a real device. The JAR and JAD files are the important files used to deploy the MIDlet into the emulated or rea

2416.7.1 Testing Requirements The list of hardware and software requirements, and tools used for setting up the experiments are provided in the fo

2426.7.1.2 Software Requirements Table 6.4 lists the software requirements for conducting the experiment using two IMS Clients and an Open IMS

2436.7.1.3 Testbed Specifications The specifications provided in this subsection were provided based on Open IMS Core testbed. Table 6.5: IMS

217Chapter – 6 IMS Client Development and Deployment 6.1 Introduction IP Multimedia Subsystem introduced since 2002, since initiation of IMS many

244The P-CSCF, E-CSCF and the S-CSCF are hosted within the same machine, while the HSS is on a separate machine. The IMS Client applicati

245 Figure 6.22: Demonstration of How to Establish a Session 6.8 Results Discussion In this section the evaluation and discussion of the

246found is based on SDP parameters negotiated at the IMS session. 6.8.1 Registration Request Figure 6.23 shows the SIP REGESTER request sent

247Table 6.6: SDP Attributes Attribute Tags Description Curr (Current) Indicates the extent to which the set preconditions have al

248 Figure 6.24: INVITE Request Trace 6.8.3 Trying Response To avoid frequent re-transmission of the INVITE request from the UE, the P-CSCF sends

249 6.8.4 Session Progress Response The 183-Session-in-Progress response is sent by the remote client to indicate that session establishment pr

250 The local client sends back a PRACK request to acknowledge the received 183-Session in Progress response. This PRACK also carries the second

251 Figure 6.29: UPDATE Request Trace The remote client, on receipt of the UPDATE request, will respond with a 200-OK response containing the S

252 Figure 6.31: ACK Request Trace 6.8.8 Communication Mode Communication between the two Light-Weight IMS Clients was achieved making

253network S-CSCF IP address before registering, registering can be performed automatically without prompting the user. This can be achieved

218 Figure 6.1: FOKUS OpenIC Lite [125] While OpenIC Lite is free and available for download, the FOKUS group has a commercial Open IMS Client vers

254discussion of results was based on the SIP signalling messages exchanged between the IMS Clients and the IMS network (IMS testbed) for

219 Figure 6.2: IMS-Communicator Screenshot [126] According to the IMS-Communicator website, the developers of IMS-Communicator have no

220 Figure 6.3: UCT IMS Client Screenshot [127] 6.3 Overview of Tools Used For Developing IMS Client The development of the IMS Client bas

221 Table 6.1: Mobile Development Platforms [129] Functionality Symbian J2ME BREW Foundation C++ Java C++ Learning Curve Difficult Average

222The IMS Client is developed as a MIDlet and emulated using the Nokia smart-phone emulator provided with the Sun WTK version 2.5. Version 2.5

223EclipseME plug-in to enable the integration between the Eclipse and the Sun WTK. In order to integrate both the Eclipse IDE an