WO2008004981A1 - Système et procédé pour fournir des services mobiles - Google Patents
Système et procédé pour fournir des services mobiles Download PDFInfo
- Publication number
- WO2008004981A1 WO2008004981A1 PCT/SG2007/000185 SG2007000185W WO2008004981A1 WO 2008004981 A1 WO2008004981 A1 WO 2008004981A1 SG 2007000185 W SG2007000185 W SG 2007000185W WO 2008004981 A1 WO2008004981 A1 WO 2008004981A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mobile
- providing
- mobile service
- hub server
- service request
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000012545 processing Methods 0.000 claims abstract description 9
- 230000004044 response Effects 0.000 claims description 9
- 238000005516 engineering process Methods 0.000 claims description 7
- 230000007246 mechanism Effects 0.000 claims description 7
- 238000012546 transfer Methods 0.000 claims description 6
- 230000006855 networking Effects 0.000 claims description 5
- 238000013500 data storage Methods 0.000 claims description 4
- 230000003993 interaction Effects 0.000 description 11
- 239000002420 orchard Substances 0.000 description 7
- 230000000694 effects Effects 0.000 description 6
- 239000008186 active pharmaceutical agent Substances 0.000 description 5
- 230000002452 interceptive effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012432 intermediate storage Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
Definitions
- This invention relates to a system and method for providing mobile services.
- a system for providing mobile services comprising: a mobile device executing a client application for generating a mobile service request; and a hub server for receiving and processing the mobile service request, wherein the mobile service request comprises location data of the mobile device, and the hub server pushes one or more mobile service offers to the mobile device based on the location data.
- the client application may comprise an avatar-based user interface.
- the client application may obtain the location data of the mobile device and provides the location data to the hub server.
- the mobile service may comprise one or more of a group consisting of: peer to peer networking; providing information; providing quizzes; providing games; pushing of advertisements; purchase or selling of items; bill payment; and redeeming electronic vouchers.
- the client application may learn from user inputs and adapts to user preferences.
- the hub server may interact with agency servers for providing the mobile service.
- the agency servers may be operated by private sector entities and by government bodies.
- the hub server may utilise Web Service Orchestration Technology for seamlessly providing two or more mobile services associated with a single mobile service request.
- the hub server may utilise XML Web Services for seamlessly providing two or more mobile services associated with a single mobile service request.
- the hub server may utilise HTTP (HyperText Transfer Protocol) request and response mechanisms for seamlessly providing two or more mobile services associated with a single mobile service request.
- HTTP HyperText Transfer Protocol
- a method for providing mobile services comprising: executing a client application for generating a mobile service request on a mobile device; receiving and processing the mobile service request at a hub server; and pushing one or more mobile service offers from the hub server to the mobile device based on location data, wherein the mobile service request comprises location data of the mobile device.
- the client application may comprise an avatar-based user interface.
- the method may further comprise obtaining the location data of the mobile device and providing the location data to a hub server utilizing the client application.
- the mobile service may comprise one or more of a group consisting of: peer to peer networking; providing information; providing quizzes; providing games; pushing of advertisements; purchase or selling of items; bill payment; and redeeming electronic vouchers.
- the method may further comprise learning from user inputs and adapting to user preferences utilizing the client application.
- the method may further comprising interacting with agency servers for providing the mobile service utilizing the hub server.
- the agency servers may be operated by private sector entities and by government bodies.
- the method may comprise providing two or more mobile services associated with a single mobile service request seamlessly utilizing Web Service Orchestration Technology at the hub server.
- the method may comprise providing two or more mobile services associated with a single mobile service request seamlessly utilizing XML Web Services at the hub server.
- the method may comprise providing two or more mobile services associated with a single mobile service request seamlessly utilizing HTTP (HyperText Transfer Protocol) request and response mechanisms at the hub server.
- HTTP HyperText Transfer Protocol
- a data storage device containing computer readable code means for instructing a mobile device to execute a method for providing mobile services, the method comprising: executing a client application for generating a mobile service request on the mobile device for processing at a hub server; and pushing one or more mobile service offers from the hub server to the mobile device based on location data, wherein the mobile service request comprises location data of the mobile device.
- Figure 1 is the system architecture of an example embodiment of the present invention.
- FIG. 2 illustrates interaction between the elements of the example embodiment of the present invention.
- Figure 3 is a user interface for selecting a service.
- Figure 4 is a user interface for entering user payment details.
- Figure 5 is a user interface for entering credit card information.
- Figure 6 illustrates interaction between the elements of the example embodiment of the present invention.
- Figure 7 shows user interfaces for personal area networking.
- Figure 8 shows user interfaces for messaging in a personal area network.
- Figure 9 shows a menu for selecting services provided in an area.
- Figure 10 shows a menu of services available at a place of interest.
- Figure 11 shows a picture and a user interface relating to a place of interest.
- Figure 12 shows user interfaces for taking a quiz relating to a place of interest.
- Figure 13 shows user interfaces during and after user login.
- Figure 14 shows user interfaces for purchasing movie tickets.
- Figure 15 shows user interfaces for payment of movie tickets.
- Figure 16 shows user interfaces for purchasing last minute movie tickets.
- Figure 17 shows user interfaces for payment of the last minute movie tickets.
- Figure 18 shows user selection to show mVoucher (mobile voucher) from a menu.
- Figure 19 shows user interfaces for mVoucher redemption.
- Figure 20 illustrates an electronic message received at a movie ticket counter.
- Figure 21 shows user interfaces for notifying Government authorities of overseas trip.
- Figure 22 illustrates a schematic drawing of a mobile device for implementing the system and method according to the example embodiment.
- the example embodiment comprises a system or Web Services Hub 100 interconnected via the Internet to Government Web Services 102, Commercial Web Services 104, a Payment Gateway 108, and to Mobile Users 106 through a Java 2 Mobile Enterprise (J2ME) client after Web Services Transcoding is performed.
- J2ME Java 2 Mobile Enterprise
- a mobile user 106 accesses mobile services provided by the Web Services Hub 100 through a graphical, interactive, user-friendly client application referred to herein as JeneSpace that is developed in J2ME.
- JeneSpace a graphical, interactive, user-friendly client application referred to herein as J2ME.
- the mobile user 106 first downloads JeneSpace via General Packet Radio Service (GPRS), Third Generation (3G) Telecommunication Network means, Wireless Local Area Network (WLAN) or the like into the mobile user's mobile device.
- GPRS General Packet Radio Service
- 3G Third Generation
- WLAN Wireless Local Area Network
- JeneSpace When a mobile user 106 navigates through the mobile services on his/her mobile device, JeneSpace sends a request to the Web Services Hub 100 via GPRS, 3G, WLAN or the like to obtain the content to be displayed.
- the content may be informational (e.g. text articles) or may be form-based. If the content is form-based, JeneSpace prompts the mobile user 106 to fill in the form and then transmits the form data to the Web Services Hub 100 for processing.
- the Web Services Hub 100 integrates with government and commercial agencies 102 and 104 utilizing standard XML Web Services and standard HTTP (HyperText Transfer Protocol) request and response mechanisms, to obtain the mobile content and to submit form data.
- JeneSpace requests content from an agency's server
- the Web Services Hub 100 transcodes the request and forwards it to the agency server.
- the resulting content is transcoded by Web Services Hub 100 and displayed by JeneSpace.
- the XML Web Services are based on the World Wide Web Consortium (W3C) standards. It is appreciated that the Web Services Hub 100 may be integrated with government and commercial agencies 102 and 104 utilising standard XML Web Services alone, or utilizing only standard HTTP request and response mechanisms, in different embodiments.
- W3C World Wide Web Consortium
- the agency server When the agency server is activated to collect payment in response to a user input, the agency server returns a Payment Form to the Web Services Hub 100, which will perform the payment collection. Upon payment, the Web Services Hub 100 sends a Payment Status message to the agency servers.
- FIG. 1 the Web Services Hub 100 ( Figure 1 ) is a computer server named Portal City. It is appreciated that Portal City may comprise more than one computer server for performing the tasks stated in the flow of events below.
- a mobile user 224 downloads and installs JeneSpace from Portal City 226 into his/her mobile device 228. This is a one-time installation.
- the mobile user 224 activates JeneSpace and selects the Bill payment service on the user interface of JeneSpace.
- Figure 3 shows an example of a simplified user interface or form 300 generated by JeneSpace on the mobile device 228 ( Figure 2) of the mobile user 224 ( Figure 2), which displays the selection of "Agency A Bill Payment” 302 and the clicking of "OK” button 304 to confirm the selection.
- JeneSpace transmits the selection 302 ( Figure 3) to Portal City 226 via a GPRS/3G/WLAN Network 232 and the Internet 234.
- Portal City 226 transcodes the request from Mobile Platform to Web platform and invokes Agency A server 230 for Web Services to obtain the content requested.
- the Agency server 230 returns a form to Portal City 226 to be rendered for display on the mobile device, and the form contains 2 fields, Bill Number and Amount.
- the representation of Portal City 226 interactions with the Agency server 230 in this step is as follow:
- FIG. 4 shows an example of a simplified user interface or the form 400 that is generated by JeneSpace on the mobile device 228 ( Figure 2) of the mobile user 224 ( Figure 2).
- the form 400 displays a Bill Number field 402 and an Amount field 404 for the mobile user 224 ( Figure 2) to fill in, and an "OK" button 406 for submitting the form and confirming the payment to be made.
- the mobile user 224 Figure 2 fills up the Bill Number field 402 with the Bill reference number and the Amount field 404 with the amount to be paid and click the "OK" button 406 for submitting the form 400.
- the Agency server 230 validates the form data and returns a Payment Form to request for collection of payment.
- a transaction reference identifier (ID) is included in the Payment Form for the Agency server 230 to track the status of the payment transaction.
- ID transaction reference identifier
- the representation of Portal City 226 interactions with the Agency server 230 in this step is as follow:
- FIG. 5 shows an example of a simplified user interface or the form 500 that is generated by JeneSpace on the mobile device 228 ( Figure 2) of the mobile user 224 ( Figure 2).
- the form 500 displays a Credit Card Number field 502 and an expiry date field of the credit card number 504 for the mobile user 224 ( Figure 2) to fill in, and an "OK" button 506 to submit the form.
- the mobile user 224 Figure 2 enters the Credit Card Number 502 and the expiry date of the credit card number 504 and click the "OK" button 506 for submitting the form 500.
- the credit card information i.e.
- the credit card number and expiry date, of the mobile user 224 are stored in the internal memory of the mobile device 228 or in external memory connected to the mobile device 228 ( Figure 2).
- the credit card information is stored in an encrypted form.
- the credit card information may upon successful verification of a pin number on a form (Not shown in the Figures) specially generated by Jenespace for entering the pin number, gain access to view the credit card information on another form (Not shown in the Figures) specially generated by Jenespace for viewing and/or editing the stored credit card information on the mobile device 228 ( Figure 2).
- Portal City 226 clears the payment with a Payment Gateway 108 ( Figure 1 ) and transmits the status and the Payment Gateway's payment reference ID to the Agency server 230.
- the representation of Portal City 226 interactions with the Agency server 230 in this step is as follow:
- the Agency server 230 returns a payment acknowledgement page to the Portal City 226 for transcoding and then instructs JeneSpace to display the acknowledgement page.
- the representation of Portal City 226 interactions with the Agency server 230 in this step is as follow:
- the Agency server 230 exposes a Web Service named GetContentWebService.
- GetContentWebService The possible parameters of GetContentWebService are:
- This parameter is the name of the service requested by the mobile user e.g. "Bill Payment”.
- the Web Service is required to return the content to be displayed when the request is made.
- the content may be plain text or a form.
- Form Data This parameter is a collection of form field names and the corresponding form field values e.g. "BillNumber:12345678, Amount:10". This is invoked in response to the mobile user 224 submitting a form.
- the Web Service is required to return the content to be displayed subsequently.
- the content may be plain text or a form.
- Payment Status This parameter is a collection of fields and values that indicate the status of a mobile payment transaction e.g. "TransactionRef:54321 , Status:OK, PaymentRef:9876".
- the Web Service is required to return the content to be displayed subsequently.
- the content may be plain text or a form.
- the transmission of forms in the Agency server 230 is based on a subset of the W3C XForms standard.
- Bill Payment form 500 in Figure 5 can be represented by the following XForm:
- Portal City 226 may be extended to provide location based services for mobile users.
- Some examples of location sensitive services are the providing of information such as promotions and activities happening around the vicinity of the mobile device user, information about specific landmarks at places of interest in the vicinity of the mobile device user, and sending instant messages and data sharing in a selected personal network.
- FIG. 6 illustrates how the example embodiment provides location based services.
- All the mobile devices support at least the J2ME version 1.0 virtual machine including some having support for Java Specification Request (JSR) 118 (Mobile Information Device Profile 2.0) and JSR179 [Location Application Program Interface (API) for J2ME], and some are e.g. Nokia Series 60 (Symbian) and Palm Treo 650 mobile devices.
- JSR Java Specification Request
- API Application Program Interface
- the example embodiment may be adapted to provide location based services to other types of mobile devices that run on different operating systems e.g. Windows Mobile, or the like.
- a mobile user 612 downloads a helper Symbian Client application named JeneHelper (one time installation only) along with the JeneSpace J2ME Client application on his/her mobile device 614.
- the mobile device 614 is running on Symbian OS and it is a Nokia Series 60 mobile device.
- JeneHelper is a mobile application that may be developed in C++, Java etc. and uses Symbian API.
- JeneSpace queries JeneHelper for the Cell ID.
- JeneHelper is capable of reading the Global System for Mobile Communication (GSM) or Universal Mobile Telecommunications System (UMTS) Cell ID through the Symbian API when requested by JeneSpace.
- GSM Global System for Mobile Communication
- UMTS Universal Mobile Telecommunications System
- JeneHelper obtains the Cell ID via Symbian API and returns the Cell ID to JeneSpace. JeneSpace then transmits the Cell ID to Portal City 618 (226 in Figure 2) via the Mobile Telecommunication Network 620 and the Internet 622 to translate the Cell ID into a location name.
- Portal City 618 performs the translation by looking up a database of known Cell IDs to match the Cell ID obtained from JeneHelper. If the Cell ID is not found in the database, the Portal City Server 618 returns the location that corresponds to the nearest known Cell ID.
- the location name is transmitted to an Agency server 624 via a Web Service, so that an Agency server 624 may generate location-specific content and services.
- the Agency server transmits content/services to a list of users who are in a particular location. This advantageously makes it possible to provide location-sensitive mobile services like "Last Minute Ticket Sales", where a cinema operator can push discounted tickets to users within a specific location just before the movie begins.
- JeneHelper will have a native PalmOS application that obtains the Cell ID via the PalmOS API.
- Location Based Services are still available to the mobile device users through JeneSpace prompting the user to enter the name of the location.
- JSR118 Java APIs are available to mobile devices installed with Java Platform version 7.3 and above. Using JSR118 Java APIs, the mobile device manufacturer can expose the current cell ID of mobile devices supporting JSR118 for use in any mobile device application such as JeneSpace or JeneHelper.
- Jenespace may bypass JeneHelper or utilize JeneHelper to retrieve the cell ID provided by the mobile device manufacturer from GPS coordinates through the use of JSR179 Java APIs.
- JeneSpace communicates with JeneHelper via a TCP socket (for Symbian OS) or through a shared file (for Palm OS).
- JeneSpace and JeneHelper both use APIs provided by the Symbian OS, Palm OS and J2ME virtual machine in the present example.
- JeneSpace may comprise an avatar-based user interface named, for example, Jene, which acts as a virtual concierge that provides electronic commercial activities such as purchasing and selling. Jene interfaces the functionality of JeneSpace and JeneHelper. Jene, is capable of learning from user inputs and adapting to the user preferences. Jene is also capable of tracking the exact location of the mobile user and provides suggestions for the electronic services available at the location. For instance, Jene may send instant messages to users to alert them of events and promotions and users can send a message to Jene to request for help and recommendations e.g. "where is the nearest Shell station?". Jene may then reply by showing a map and direct the user to the location. Jene is programmed with the necessary intelligence to understand basic sentences that users may query.
- JeneSpace is location sensitive and works based on the telco cell ID. JeneSpace enables searching out personnel around the user and sending of instant messages to the personnel. JeneSpace also provides updates and enable discovery of promotions and activities happening around the user. Information of landmarks in the form of sound/video clips or text and pictures may also be made available through JeneSpace to the user based on the location of the user.
- JeneSpace is implemented using C++, Java or the like and is installed in the user's mobile device such as hand phones, Personal Digital Assistants (PDA) or the like upon request.
- PDA Personal Digital Assistants
- users can interact with the avatar, Jene, and with other users in the personal area network at the vicinity of the users or other users in a network of selected personnel.
- JeneSpace may be used as a ubiquitous mobile tool for Secure mobile commerce transactions and Secure eGovelement (electronic Government) transactions.
- Example of applications for JeneSpace are purchase of products and services (e.g. movie tickets) electronically through the mobile device, redemption of electronic vouchers, viewing of mobile content such as text, images, 3G streaming video, participation in electronic quizzes, and because JeneSpace is location sensitive, merchants can push offers to users near specific locations.
- products and services e.g. movie tickets
- redemption of electronic vouchers viewing of mobile content such as text, images, 3G streaming video
- viewing of mobile content such as text, images, 3G streaming video
- participation in electronic quizzes and because JeneSpace is location sensitive, merchants can push offers to users near specific locations.
- Figure 7 shows two windows 700 and 706 that are created by JeneSpace when the personal network is activated.
- static pictures or animated objects 702 are used to represent neighbouring mobile devices.
- the location 704, Orchard North, of the user is automatically detected and indicated on the display.
- the neighbouring mobile devices are detected from the surrounding area of the user mobile device via Bluetooth, WLAN or the like.
- the neighbouring mobile devices displayed may be configured to show only selected peers and not all detected mobile devices.
- the identifiers 708 of the neighbouring mobile devices at the location 704 are displayed.
- the identifier "Everyone" 710 is used for instant messaging to all of the detected neighbouring mobile devices shown in the window 706.
- a window 800 containing information of the selected peer and interaction means with the peer will appear.
- the window 800 contains options such as "View Pics" 802 and "Send Message" 804 and displays the name or alias of the selected peer.
- Selecting "View Pics” 802 will call out another window containing a gallery of pictures taken or uploaded by the peer.
- Selecting "Send Message" 804 will call out an editable window 806, which the user can type messages on to be sent to the selected peer.
- Window 808 shows the same window 806 containing a reply from the selected peer.
- Figure 9 shows a window 900 that is created by JeneSpace when the user activates a search to look for promotions and activities happening in the vicinity of the user location.
- the user location 902 is at Orchard North.
- the options available for the user are, show mVouchers 904 (mobile vouchers), buy movie tickets 906, take an NS (National Service) Quiz 908, commence Mobile learning 910 on a particular topic, play a 3G video clip 912, help features on the usage of JeneSpace 914 and "More..” 916 for displaying more options.
- the promotions and activities happening in the vicinity of the user location are discovered via Bluetooth, WLAN, GPRS, 3G or the like and the information is supplied by surrounding wirelessly connected servers in the area and/or from servers via the Internet.
- Figure 10 shows a window 1000 that is created by JeneSpace when the user activates a search to look for activities associated with a landmark or place of interest and information about the landmark or place of interest at the user location.
- Window 1000 shows the user location 1002 at the place of interest, Merlion Park.
- the user interaction options available are Show puzzle 1004 for playing a puzzle game about the Merlion, play a Merlion video 1006 introducing the origins of the Merlion Park, take a Merlion Quiz 1008 and show Merlion clue 1010 for the quiz. These user interaction options change depending on the time and location of the user.
- Discovery is performed via Bluetooth, WLAN, GPRS, 3G or the like and the information is supplied by surrounding wirelessly connected servers in the area and/or from servers via the Internet.
- Figure 11 shows the starting frame 1100 of the Merlion video clip 1006 ( Figure 10) and the window 1102 containing the clues 1010 (Figure 10) for the Merlion Quiz 1008 ( Figure 10).
- Figure 12 illustrates a user's participation in a quiz. After the user activates the NS quiz option through JeneSpace, a window 1200 containing the question of the quiz will appear. In this case, the user needs to select the correct answer from a list of choices. In Figure 12, the correct answer is the second option 1202. Windows 1204 and 1206 show the prize won for answering the quiz correctly.
- Figures 13 - 15 illustrate purchasing movie tickets through JeneSpace.
- window 1300 shows the user login screen containing username field 1306, password field 1308 and location field 1310, all of which requires user input. It is appreciated that JeneSpace can automatically fill in fields 1306 and 1308 by reusing previous user entries or is programmed by user settings to always use the same entries for the fields. Also, the location field 1310 may be detected , by JeneSpace wirelessly and then automatically filled in by JeneSpace.
- Window 1302 is similar to window 706 ( Figure 7) and window 1302 appears after user login is successful.
- Window 1304 shows a menu for selecting currently held events, which can be called out from window 1302 by clicking specific icons. Examples of such icons are 1310 and 1312. The user selection from window 1304 for purchasing movie tickets is "Buy movie tickets" 1314.
- window 1400 in Figure 14 will appear for selecting a cinema to watch the movie.
- Orchard cinema 1408 is selected.
- window 1404 appears with options for selecting the movies available to watch at Orchard cinema. In this case, "King Kong" 1410 is selected.
- window 1406 the desired time 1412 to watch the movie is selected.
- window 1500 in Figure 15 appears for selecting the quantity of movie tickets.
- window 1516 representing an mWallet or mobile wallet for payment of the ticket via credit card appears.
- the mWallet window 1516 contains a summary 1502 of the cost of the number of tickets selected and entries for entering name 1504 of the owner of a credit card, credit card number 1506, expiry date 1508 of the credit card and password 1509 of the credit card owner. It is appreciated that JeneSpace can automatically fill in fields 1504, 1506, 1508 and 1509 by reusing previous user entries or is programmed by user settings to always use the same entries for the fields. For security, encryption is performed on the alphanumeric characters of the fields for the display, hence only asterisks can be seen.
- window 1512 appears. Window 1512 summarizes the amount paid by credit card and provides a booking reference number for collection of tickets. Selecting "Exit" 1510 in window 1512 ends the movie purchase session.
- Figure 16 shows the case when last minute movie tickets are bought.
- Window 1600 is similar to window 1300 ( Figure 13), which is the user login screen.
- the username 1606 is pre-filled by JeneSpace by reusing a previous login entry.
- window 1602 which is similar to window 1302 ( Figure 13), appears.
- Window 1604 shows the confirmation window for purchase of 2 tickets for movie King Kong at 1pm in Jene cinema at cost of $10.
- Window 1702 and 1704 shows the mWallet and confirmation window that is similar to windows 1516 and 1512 respectively for the payment of the last minute movie tickets by credit card.
- Window 1702 is for entering credit card details and window 1704 summarizes the transaction and provides a booking reference for collection of the last minute movie tickets at the cinema ticket counter.
- Figures 18 - 20 illustrate mVoucher (mobile voucher) redemption through JeneSpace.
- FIG. 18 shows a window 1800 with a menu of choices present for the current user location. These choices are detected by the mobile device from the surroundings and downloaded to the mobile device. In this case, "Show mVouchers" 1802 is selected.
- Window 1900 shows the mVouchers available at the user location.
- "Jene Cinemas" 1906 is selected.
- Window 1902 contains the details of the mVoucher.
- the detected mVoucher at Orchard North location comprises the deal of purchasing Jene cinema movie tickets at half price.
- Selecting "Redeem mVoucher” 1908 sends the user request to redeem the mVoucher to the ticketing computers used at the cinema ticket counter.
- Window 1904 appears to inform the user of the voucher code after selecting "Redeem mVoucher” 1908.
- Selecting "Exit” 1910 exits the mVoucher redemption session.
- Figure 20 shows an electronic message displayed on the ticketing computers at the cinema ticket counter.
- the electronic message notifies the counter staff that the user wishes to redeem the mVoucher.
- the ticketing computers are linked to the Internet and receive the electronic message from the servers of the telco network, which the user of the mobile device is subscribed to
- the electronic message contains details of the voucher code 2000, the item redeemed 2002, the personalised greeting name of the user 2004, and the date and time of the mVoucher redemption 2006.
- the counter staff may be notified of the mVoucher redemption by receiving the electronic message on their mobile devices such as pagers, mobile phones, Personal Digital Assistants (PDA) or the like through communication technologies such as GSM, 3G 1 WLAN or the like.
- Another way of notification is via a point of sale credit card terminal, which can be activated to show the electronic message to the counter staff when the user swipes his/her credit card or keys in a special activation code on the terminal such as the voucher code 2000.
- Figure 21 illustrates notifying relevant Government authorities of an overseas trip.
- Window 2100 shows a menu of choices where "Travel overseas" 2108 is selected.
- Window 2102 is a menu of services related to travelling overseas.
- the menu of services in window 2102 are advantageously integrated together utilising Web Service Orchestration Technology by a hub server such as Portal City (226 in Figure 2) and displayed via JeneSpace on the user mobile device.
- Web Service Orchestration Technology includes the use of standard XML Web Services and standard HTTP (HyperText Transfer Protocol) request and response mechanisms. Users can use the three services shown in the menu in window 2102 seamlessly i.e. buy flight tickets, notify MINDEF and buy travel insurance without having to separately click or activate each of the three services.
- Window 2104 appears after the selection.
- Window 2104 contains fields for entering the citizenship identity card number 2112, the contact telephone number of the user 2114, the day of birth of the user 2116, the month of birth of the user 2118 and the year of birth of the user 2120.
- window 2106 appears for the user to select the city, which he/she is visiting. After that, another window (not shown in Figure 21 ) appears for the user to enter the duration of the trip and dates of travel.
- the method of the example embodiment can be implemented on a wireless device 2200, schematically shown in Figure 22. It may be implemented as software, such as a computer program being executed within the wireless device 2200, and instructing the wireless device 2200 to conduct the method of the example embodiment.
- the wireless device 2200 comprises a processor module 2202, an input module such as a keypad 2204 and an output module such as a display 2206.
- the processor module 2202 is connected to a wireless network 2208 via a suitable transceiver device 2210, to enable wireless communication and/or access to e.g. the Internet or other network systems such as Wireless Local Area Network (WLAN), Wireless Personal Area Network (WPAN) or Wide Area Network (WAN).
- WLAN Wireless Local Area Network
- WPAN Wireless Personal Area Network
- WAN Wide Area Network
- the processor module 2202 in the example includes a processor 2212, Random Access Memory (RAM) 2214 and Read Only Memory (ROM) 2216.
- the processor module 2202 also includes a number of Input/Output (I/O) interfaces, for example I/O interface 2218 to the display 2206, and I/O interface 2220 to the keypad 2204.
- I/O Input/Output
- the components of the processor module 2202 typically communicate via an interconnected bus 2222 and in a manner known to the person skilled in the relevant art.
- JeneSpace may be supplied to the user of the wireless device 2200 encoded on a data storage medium such as a flash memory module or memory card/stick or downloaded via the Internet and read utilising a corresponding memory reader-writer of a data storage device 2224. JeneSpace is read and controlled in its execution by the processor 2212. Intermediate storage of program data may be accomplished using RAM 2214.
- a data storage medium such as a flash memory module or memory card/stick or downloaded via the Internet and read utilising a corresponding memory reader-writer of a data storage device 2224.
- JeneSpace is read and controlled in its execution by the processor 2212.
- Intermediate storage of program data may be accomplished using RAM 2214.
- Example embodiments of the present invention may have the following features and advantages.
- J2ME + GPRS/3G/WLAN-enabled devices e.g. mobile phones, PDAs etc.
- Location-based services are also supported by the infrastructure of the example embodiments.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multi Processors (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
La présente invention concerne un système et un procédé destinés à fournir des services mobiles. Le système comprend : un dispositif mobile exécutant une application client pour générer une demande de service mobile et un serveur central recevant et traitant cette demande, celle-ci comprenant des données de localisation du dispositif mobile et le serveur central proposant une ou plusieurs offres de service mobile au dispositif selon les données de localisation. Le procédé consiste à exécuter une application client qui génère une demande de service mobile sur un dispositif mobile, à recevoir et traiter cette demande sur un serveur central et à proposer une ou plusieurs offres de service mobile au dispositif depuis le serveur selon des données de localisation, la demande de service mobile comprenant des données de localisation du dispositif.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SG200604592-6 | 2006-07-07 | ||
SG200604592-6A SG138502A1 (en) | 2006-07-07 | 2006-07-07 | A system and method for providing mobile services |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008004981A1 true WO2008004981A1 (fr) | 2008-01-10 |
Family
ID=38894849
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SG2007/000185 WO2008004981A1 (fr) | 2006-07-07 | 2007-06-27 | Système et procédé pour fournir des services mobiles |
Country Status (2)
Country | Link |
---|---|
SG (1) | SG138502A1 (fr) |
WO (1) | WO2008004981A1 (fr) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000050844A1 (fr) * | 1996-08-22 | 2000-08-31 | Go2 Systems, Inc. | Systeme et procede de referenciation a une situation geographique bases sur internet |
WO2002017567A2 (fr) * | 2000-08-25 | 2002-02-28 | Yogogo Limited | Communications de donnees |
US20030174683A1 (en) * | 2000-07-07 | 2003-09-18 | Sverre Vegge | Personal mobile internet |
EP1381197A1 (fr) * | 2002-07-08 | 2004-01-14 | Sony International (Europe) GmbH | Procédé de fourniture de services basés sur la localisation |
US20060026070A1 (en) * | 2004-07-28 | 2006-02-02 | Industrial Technology Research Institute | Electronic coupon transaction system and method |
-
2006
- 2006-07-07 SG SG200604592-6A patent/SG138502A1/en unknown
-
2007
- 2007-06-27 WO PCT/SG2007/000185 patent/WO2008004981A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000050844A1 (fr) * | 1996-08-22 | 2000-08-31 | Go2 Systems, Inc. | Systeme et procede de referenciation a une situation geographique bases sur internet |
US20030174683A1 (en) * | 2000-07-07 | 2003-09-18 | Sverre Vegge | Personal mobile internet |
WO2002017567A2 (fr) * | 2000-08-25 | 2002-02-28 | Yogogo Limited | Communications de donnees |
EP1381197A1 (fr) * | 2002-07-08 | 2004-01-14 | Sony International (Europe) GmbH | Procédé de fourniture de services basés sur la localisation |
US20060026070A1 (en) * | 2004-07-28 | 2006-02-02 | Industrial Technology Research Institute | Electronic coupon transaction system and method |
Also Published As
Publication number | Publication date |
---|---|
SG138502A1 (en) | 2008-01-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20190333105A1 (en) | System and Method for Interactive Marketing | |
Kroski | On the move with the mobile web: libraries and mobile technologies | |
US10579224B2 (en) | Enabling participation in an online community using visual machine-readable symbols | |
Sadeh | M-commerce: technologies, services, and business models | |
KR101671895B1 (ko) | 메시지 기반 구매를 위한 시스템 및 방법 | |
US8156206B2 (en) | Contextual data communication platform | |
US20090024530A1 (en) | Automatic gift messaging system | |
US20080182563A1 (en) | Method and system for social networking over mobile devices using profiles | |
US20090204511A1 (en) | System and method for distributing targeted content | |
US8392447B2 (en) | System and method for using symbol command language within a communications network | |
US20080133647A1 (en) | System and method for delivering web content to a mobile network | |
WO2009023591A2 (fr) | Systèmes et procédés de navigation dans une hiérarchie d'informations | |
JP2008299556A (ja) | データ処理装置、データ通信システム、コンピュータプログラム | |
WO2001057724A1 (fr) | Agent interactif pour dispositif mobile | |
WO2008004981A1 (fr) | Système et procédé pour fournir des services mobiles | |
Karagiozidis et al. | Commercial use of mobile, personalised location-based services | |
KR20040081506A (ko) | 휴대폰의 광고 방법 | |
GB2448125A (en) | Method of making content available on a network | |
Bessa et al. | Ubiquitous System for Events Promotion | |
Correia et al. | Ubiquitous System for Events Promotion | |
KR20060118155A (ko) | 멀티미디어 메시지 서비스를 이용한 사용자 요청 정보 전송시스템 | |
Pedersen et al. | Mobile e-commerce (m-commerce): TENIA National Report Denmark | |
JP2002230396A (ja) | メニューサービス方法及びメニューサービスシステム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07748730 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07748730 Country of ref document: EP Kind code of ref document: A1 |