WO2011128904A1 - A method of transmitting data, voice or multimedia messages from one wireless computing device to another wireless computing device using gprs/wi fi - Google Patents
A method of transmitting data, voice or multimedia messages from one wireless computing device to another wireless computing device using gprs/wi fi Download PDFInfo
- Publication number
- WO2011128904A1 WO2011128904A1 PCT/IN2010/000235 IN2010000235W WO2011128904A1 WO 2011128904 A1 WO2011128904 A1 WO 2011128904A1 IN 2010000235 W IN2010000235 W IN 2010000235W WO 2011128904 A1 WO2011128904 A1 WO 2011128904A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- computing device
- messages
- wireless computing
- voice
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/10—Multimedia information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
- H04L65/765—Media network packet handling intermediate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/06—Message adaptation to terminal or network requirements
- H04L51/066—Format adaptation, e.g. format conversion or compression
Definitions
- This invention relates to technique of sending data, voice or multimedia messages from one wireless computing device to another wireless computing device
- This invention revolutionizes the way mobile data
- MMS message is uploaded on a personalized web server that's independent of the service or content provider, allowing you to upload file on any size and storing them on the server for as long as you desire. All of this for only a fraction of the cost of GPRS, what a mobile service provider would charge.
- Schools can use it for authorized students/personnel access areas
- Government/Army/ Aircraft can use it to meet specific goal- oriented needs
- the invention provides users with the following revolutionary features:
- Live video streaming capabilities This can prove advantageous to medical professionals and police units handling both, routine tasks and in extreme situations. This feature of the invention could also usher in a new wave of citizen journalism.
- the system model consists of following main parts:
- a) GPRS system and also through Fig No.1 User is generally a user who requests to use application(s).
- the users need to authenticate themselves by using the user information securely stored in a Snip DB before accessing the application(s).
- the single sign-on is required in this process so that the user can access several applications without necessity to be authenticated by each system
- SAIS Snip Application Integration System
- API/WS web services
- User WS is responsible for validating user information, verifying user requests, and delegating corresponding
- Each UWS will be dead after a complete logout, or after certain idle period, which is the SSO session timeout value.
- Application WS is mapped to a particular application and functions as the representative of an application in serving requests from UWSs. Its job is to schedule the sequence of users connecting to applications, to support the voice recording application, and to send it to sever
- SMWS State Maintaining WS
- Event Log / Log WS To verify the authentication process and current status of application to which the users connect, the administrator can check all activities from the event log /Log. Event Log / Log WS will generate the logs to maintain the records of all the activities done on Snip by, user as well as activities done on administrator level
- Setup Phase Only when a user signs in to the system, the Setup phase is done for user authentication and UI preparation. Upon the receipt of an application access request from the user, the Runtime phase starts for access verification and application delegation. The processes are described as follow: Setup Phase:
- Step 2 User Authentication: User will use the IMEI or user id & password to authenticate himself/herself via SSL to the Web Server.
- Step 2 Snip UI Construction: After the successful user authentication, Web Server requests the Snip module to generate a UI. The UI will be mapped to the user for managing all of its application requests. Logically, the Snip module, a trusted core component, will generate the UI whenever the user has
- Step 3 User Certificate Validation: The UI looks up the WS (web services), verifies the authenticity of the client certificate, and checks its validity against a pre-defined policy (e.g. CRL status, specific content rules, application settings, last user state)
- a pre-defined policy e.g. CRL status, specific content rules, application settings, last user state
- Application Delegation Once the WS recognizes an application access request (application and action) from the user information, it will verify such a request against the user capability list (and maybe some additional policies). If the user is authorized, the WS will then make a request to an appropriate Application and Action in the scheme detailed in Step 5 to start the new session.
- UA User Action
- AA Application Action
- Message Delivery The message that WS sends to the AA(Application Action) includes ⁇ Mobile No, or IMEI , session id, app id, role, timestamp> where
- - user_id is the id of user asking for the request
- - session id is the id of communication session of the request (this could be randomly generated at the beginning of the session)
- app_id is the id of Application which is requested by the user
- - role is the function that the user presents himself/herself to the application, used together with user id to obtain proper authorization.
- Step 6 UA Message Verification: Upon receipt of a message, AA will acknowledged the UA and verify the trustworthiness of the message by verifying the digital signature signed by SAS in the previous step.
- Step 7 Multi-Application Control: After the process in Step 6 is done, Snip functions will then be responsible for controlling the use of multi-application requests by several users (UAs). It manages the application access queue. As a consequence, all processes above achieve the multi-user and multi-application authentication purpose with Snip functions.
- Administrator will configure the applications, user roles, message codes, manage content and user logs.
- the following use case diagram describes the different activities of the administrator:
Abstract
The invention is about a method of transmitting one or more voice/ multimedia messages from one computing device to another computing device by involving a personalized, purpose- specific web server. Live chatting and live streaming is achieved thru this method. Also scheduling of messages can also be done.
Description
Title: A method of transmitting data, voice or multimedia messages from one wireless computing device to another wireless computing device using GPRS/Wi Fi
Field of invention
This invention relates to technique of sending data, voice or multimedia messages from one wireless computing device to another wireless computing device
Brief Description of Related Developments
This invention revolutionizes the way mobile data
communication takes place. A java based mobile phone
application; it enhances the process of sending MMS messages like never before. Up till now, mobile phone users were limited to their service providers' limited server storage capacities when they sent or received MMS messages. Now, with the help of this invention, MMS message is uploaded on a personalized web server that's independent of the service or content provider, allowing you to upload file on any size and
storing them on the server for as long as you desire. All of this for only a fraction of the cost of GPRS, what a mobile service provider would charge.
This opens up a vast vista of possibilities for not just regular users, but even for corporate and government organizations. While regular users can use it to communicate to their dear ones, the invention holds greater advantages for corporate because added layer of security to prevent data misuse and hacking. Corporates can have multiple servers and assign them to various staff members according to their rank and priority. By doing so, using this invention they can send specific top-priority proprietary information to only those set of employees who need it. This has the following applications:
• Accessing a restricted area which allows access only through a authorized user and MMS
• Banks can use it for high security access points
• Schools can use it for authorized students/personnel access areas
• Government/Army/ Aircraft can use it to meet specific goal- oriented needs
• Auto industry can initiate a voice and video start capability in cars The invention's ability to transfer large videos becomes advantageous to call centers and support cells. Since videos are more instructional to people, the call centre employees can upload a video on their personalized server and use this invention to send it to their clients via GPRS. This can serve as an additional support for customer convenience and will also help those with a hearing disability.
Features of the Invention
The invention provides users with the following revolutionary features:
Personalized server with enhanced security
• Audio and video recognition and authentication
• Scheduled MMS Capabilities: Corporates and Advertisers can send specific messages at appropriate timings
• Personal Greetings: These can be customized, personalized,
scheduled and even rescheduled accordingly
• Higher transfer rate as compare to existing technology
• Live video streaming capabilities: This can prove advantageous to medical professionals and police units handling both, routine tasks and in extreme situations. This feature of the invention could also usher in a new wave of citizen journalism.
• Served database comparison: Using this feature, data uploaded by an organization can be frequently compared against users' online behavior patterns for relevancy and validation. This helps the organization to create and schedule the sending of relevant ads using this invention.
• Minimal charges as compared to those of service providers.
Brief Description of the Drawings
In the following, the invention will be described with reference to the appended figure in which
Detailed Description of the Invention:
The system model consists of following main parts:
Mobile Application that will record the voice and saved in the same and can be send using
a) GPRS system and also through Fig No.1 User is generally a user who requests to use application(s). In our system, the users need to authenticate themselves by using the user information securely stored in a Snip DB before accessing the application(s). In addition, the single sign-on is required in this process so that the user can access several applications without necessity to be authenticated by each system
individually. Web Server is responsible for accepting HTTP requests from clients and giving responses along with the data contents, which usually are executable jar. In our system environment, web sessions are secured by SSL.
Snip Application Integration System (SAIS) is the core part of the proposed model. At the SAIS server, the key pair and certificate are installed to further use for securing and
authenticating the communication process among WS (web services). Since MAIS is the core trusted entity, all active WS trust all information signed by the MAIS key. Application Server is a server provisioning application service(s). There will be several types of API/WS (web services):
User WS (UWS) is responsible for validating user information, verifying user requests, and delegating corresponding
application(s) to the user. Each UWS will be dead after a complete logout, or after certain idle period, which is the SSO session timeout value.
Application WS (AWS) is mapped to a particular application and functions as the representative of an application in serving requests from UWSs. Its job is to schedule the sequence of users
connecting to applications, to support the voice recording application, and to send it to sever
• State Maintaining WS (SMWS) is saving and maintaining the latest state of the user. Whenever user login his last saved state will be displayed or if user visiting/dialing the for first time, the default state will be shown
• Event Log / Log WS - To verify the authentication process and current status of application to which the users connect, the administrator can check all activities from the event log /Log. Event Log / Log WS will generate the logs to maintain the records of all the activities done on Snip by, user as well as activities done on administrator level
In the process, there will be two major phases: Setup and Runtime. Only when a user signs in to the system, the Setup phase is done for user authentication and UI preparation. Upon the receipt of an application access request from the user, the Runtime phase starts for access verification and application delegation. The processes are described as follow:
Setup Phase:
[Stepl] User Authentication: User will use the IMEI or user id & password to authenticate himself/herself via SSL to the Web Server. [Step 2] Snip UI Construction: After the successful user authentication, Web Server requests the Snip module to generate a UI. The UI will be mapped to the user for managing all of its application requests. Logically, the Snip module, a trusted core component, will generate the UI whenever the user has
successfully authenticated to the system. On this ground, this newly-created UI is automatically trusted.
[Step 3] User Certificate Validation: The UI looks up the WS (web services), verifies the authenticity of the client certificate, and checks its validity against a pre-defined policy (e.g. CRL status, specific content rules, application settings, last user state)
[Step 4] Application Delegation: Once the WS recognizes an application access request (application and action) from the user information, it will verify such a request against the user capability list (and maybe some additional policies). If the user is authorized, the WS will then make a request to an appropriate Application and Action in the scheme detailed in Step 5 to start the new session.
[Step 5] UA (User Action) Message Delivery: The message that WS sends to the AA(Application Action) includes <Mobile No, or IMEI , session id, app id, role, timestamp> where
- user_id is the id of user asking for the request
- session id is the id of communication session of the request (this could be randomly generated at the beginning of the session)
app_id is the id of Application which is requested by the user
- role is the function that the user presents himself/herself to
the application, used together with user id to obtain proper authorization.
[Step 6] UA Message Verification: Upon receipt of a message, AA will acknowledged the UA and verify the trustworthiness of the message by verifying the digital signature signed by SAS in the previous step.
[Step 7] Multi-Application Control: After the process in Step 6 is done, Snip functions will then be responsible for controlling the use of multi-application requests by several users (UAs). It manages the application access queue. As a consequence, all processes above achieve the multi-user and multi-application authentication purpose with Snip functions.
Framework Administration Overview
Administrator will configure the applications, user roles, message
codes, manage content and user logs. The following use case diagram describes the different activities of the administrator:
Claims
Claims:
We claim:
A method of transmitting one or more data, voice or multimedia messages from one wireless computing device to another wireless computing device comprising:
a. Sender /user records the audio /video or multimedia message in the wireless computing device
b. Sender sends the audio /video or multimedia message thru GPRS to a purpose specific web server
c. Server stores the file and sends a text message with the content link to the recipient
d. Recipient/user follows the link and accesses or downloads the file The method according to claim 1, wherein the messages can be sent by using GPRS or wi-fi technology.
The method according to claim 1 , wherein the users need to authenticate themselves at least once by using the user information securely stored in the server.
4. The method according to claim 1, where in application reads the data, voice or multimedia massage using input stream and output stream or byte Array.
5. The method according to claim 1 , wherein the messages are transferred bit by bit using input stream and output stream where the connection will be live through out the transmission or massages are transferred as data packets where the connection which will not necessarily be live.
6. The method according to claim 5, wherein the multimedia
messages are sent or received one after another so that this process of sending multimedia messages constitute a continuous action thereby be shown as a running film, live streaming or broadcasting.
7. The method according to claim 1, wherein server is saving and maintaining the latest state of the user, maintaining log report of the user log ins and log outs.
8. The method according to claim 1, wherein a user may send the messages to multiple computing devices for the purpose of different recipients to receive
9. The method according to claim 1, wherein sending or receiving of messages by the users may be scheduled to be sent or received as per requirement.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IN2010/000235 WO2011128904A1 (en) | 2010-04-12 | 2010-04-12 | A method of transmitting data, voice or multimedia messages from one wireless computing device to another wireless computing device using gprs/wi fi |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IN2010/000235 WO2011128904A1 (en) | 2010-04-12 | 2010-04-12 | A method of transmitting data, voice or multimedia messages from one wireless computing device to another wireless computing device using gprs/wi fi |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011128904A1 true WO2011128904A1 (en) | 2011-10-20 |
Family
ID=42799894
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IN2010/000235 WO2011128904A1 (en) | 2010-04-12 | 2010-04-12 | A method of transmitting data, voice or multimedia messages from one wireless computing device to another wireless computing device using gprs/wi fi |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2011128904A1 (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1517258A2 (en) * | 2003-09-17 | 2005-03-23 | Openwave Systems Inc. | Content download to wireless devices |
US20050144251A1 (en) * | 2003-12-29 | 2005-06-30 | Slate Michael L. | Cellular telephone download locker |
US20070112938A1 (en) * | 2005-11-17 | 2007-05-17 | Nokia Corporation | Intermediary, source and methods for sharing content |
WO2008104216A1 (en) * | 2007-03-01 | 2008-09-04 | Actimagine | Video image transfer system for mobile terminals |
-
2010
- 2010-04-12 WO PCT/IN2010/000235 patent/WO2011128904A1/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1517258A2 (en) * | 2003-09-17 | 2005-03-23 | Openwave Systems Inc. | Content download to wireless devices |
US20050144251A1 (en) * | 2003-12-29 | 2005-06-30 | Slate Michael L. | Cellular telephone download locker |
US20070112938A1 (en) * | 2005-11-17 | 2007-05-17 | Nokia Corporation | Intermediary, source and methods for sharing content |
WO2008104216A1 (en) * | 2007-03-01 | 2008-09-04 | Actimagine | Video image transfer system for mobile terminals |
Non-Patent Citations (1)
Title |
---|
LAHTI J ET AL: "MobiCon: mobile video recording with integrated annotations and DRM", CONSUMER COMMUNICATIONS AND NETWORKING CONFERENCE, 2006. CCNC 2006. 20 06 3RD IEEE LAS VEGAS, NV, USA 8-10 JAN. 2006, PISCATAWAY, NJ, USA,IEEE LNKD- DOI:10.1109/CCNC.2006.1593022, vol. 1, 8 January 2006 (2006-01-08), pages 233 - 237, XP010893206, ISBN: 978-1-4244-0085-0 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10243945B1 (en) | Managed identity federation | |
US8578465B2 (en) | Token-based control of permitted sub-sessions for online collaborative computing sessions | |
JP2020064668A (en) | Network connection automatization | |
CA2633311C (en) | Method, apparatus and program products for custom authentication of a principal in a federation by an identity provider | |
US20200067903A1 (en) | Integration of Publish-Subscribe Messaging with Authentication Tokens | |
CN105378768B (en) | Proximity and context aware mobile workspaces in enterprise systems | |
US9038138B2 (en) | Device token protocol for authorization and persistent authentication shared across applications | |
CN109815656A (en) | Login authentication method, device, equipment and computer readable storage medium | |
US7975287B2 (en) | System and method for validating a user of an account using a wireless device | |
US9432355B2 (en) | Single sign-on method in multi-application framework | |
KR20080053298A (en) | Creating secure interactive connections with remote resources | |
US9344417B2 (en) | Authentication method and system | |
CN101361082A (en) | System and method for secure remote desktop access | |
EP2743857A1 (en) | Methof for allowing establishment of a secure session between a device and a server | |
CN109815684A (en) | A kind of identity identifying method, system and server and storage medium | |
CN109067785A (en) | Cluster authentication method, device | |
CN102546166A (en) | Method, system and device for identity authentication | |
CN103179104A (en) | Method, system and equipment thereof for accessing remote service | |
US20040250135A1 (en) | Method of authenticating a log-on request and related apparatus | |
JP2002007345A (en) | User authenticating method | |
EP4030687A1 (en) | Authenticating anonymous information | |
CN114202840B (en) | Authentication control method, device and medium | |
WO2011128904A1 (en) | A method of transmitting data, voice or multimedia messages from one wireless computing device to another wireless computing device using gprs/wi fi | |
EP2003838B1 (en) | Distributed access manager | |
US11611541B2 (en) | Secure method to replicate on-premise secrets in a cloud environment |
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: 10752199 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10752199 Country of ref document: EP Kind code of ref document: A1 |