US9438700B2 - System and method for servers to send alerts to connectionless devices - Google Patents
System and method for servers to send alerts to connectionless devices Download PDFInfo
- Publication number
- US9438700B2 US9438700B2 US13/735,235 US201313735235A US9438700B2 US 9438700 B2 US9438700 B2 US 9438700B2 US 201313735235 A US201313735235 A US 201313735235A US 9438700 B2 US9438700 B2 US 9438700B2
- Authority
- US
- United States
- Prior art keywords
- message
- client device
- client
- sending
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02M—SUPPLYING COMBUSTION ENGINES IN GENERAL WITH COMBUSTIBLE MIXTURES OR CONSTITUENTS THEREOF
- F02M25/00—Engine-pertinent apparatus for adding non-fuel substances or small quantities of secondary fuel to combustion-air, main fuel or fuel-air mixture
- F02M25/08—Engine-pertinent apparatus for adding non-fuel substances or small quantities of secondary fuel to combustion-air, main fuel or fuel-air mixture adding fuel vapours drawn from engine fuel reservoir
- F02M25/0809—Judging failure of purge control system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H04L67/2823—
-
- H04L67/327—
-
- 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
- H04L67/565—Conversion or adaptation of application format or content
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Abstract
Description
-
- Automatic Start on Reboot—Conventionally, when a reboot of a machine is necessary, the user re-booting can also log on and manually start any servers that need to be running on the machine. With an AutoStart function provided by the AimServiceAny, each intelligent messaging network server running as an NT service can automatically restart before the user logs on. This feature can be useful if, for example, the platform reboots at night without human intervention.
- No NT Logon Required to Run—As an added security measure, intelligent messaging network servers can run without having anyone logged onto the machine and, thus, can prevent unauthorized users from accessing the platform and the servers.
- Network Management Mechanism—In addition to SNMP, running as an NT service provides an additional simple network management capability by using a remote SvrMgr utility provided on all NT servers to monitor and start/stop intelligent messaging network services running anywhere on the network.
- Startup Dependencies—An NT service can depend on the presence of other services before it is allowed to start (e.g. some intelligent messaging network servers depend on the fact that an SQL database server is running as well as possible server-to-server dependencies).
-
- 1.
PGs 116; - 2.
MRs 124; and - 3.
BESs 122.
The simplest instance of an intelligent messaging network can include a server of each of the three types coupled together as depicted in the exemplary embodiment ofFIG. 1B .
- 1.
-
- 1. Upon start-up, an intelligent
messaging network server messaging network servers - 2. The intelligent messaging network server then registers the following information about the server in the intelligent messaging network MR database 128:
- The IP address of the server and the port that the server is listening on for new connections;
- The server's intelligent messaging network Domain; and
- An intelligent messaging network Domain is a text string (e.g. “MyTestDomain”) that allows multiple intelligent messaging networks to run on the same physical network without interfering with each other. An intelligent messaging network server can only connect to other intelligent messaging network servers in the same domain.
- The server's server type e.g.:
PG 116,MR 124, orBES 122.
- 3. After the server registers itself in the
MR database 128, the registering server can obtain a unique database registration identifier (ID) and then can search theMR database 128 for other registered servers in the server's intelligent messaging network domain and of the appropriate type; e.g.,PGs 116 can search forMRs 124 in their domain,MRs 124 can search forPGs 116 andBESs 122,BESs 122 can search forMRs 124. - 4. In the simplest intelligent messaging network, each
server PGs MRs 124, eachPG 116 can be coupled to each of theMRs 124. For each peer server it finds in thedatabase 128, the intelligent messaging network server can attempt to couple itself to that server on the peer server's TCP listener socket. - 5. If the intelligent
messaging network server - a) The connecting server can send an intelligent messaging network ServerConnect message to the peer server. This message can contain the connecting server's unique database registration ID (obtained when the server first registered in the database, see
step 2 above). The connecting server can then wait a specified amount of time for a reply from the peer server. - b) The peer server can receive the intelligent messaging network “connection message” and can verify that the version included as part of the intelligent messaging network message is compatible with its own communications version and that the message is indeed an intelligent messaging network connection message. If the version is incorrect or the message is not a connection message, the peer server can terminate the TCP connection. If the peer server accepts the connection message it can send an intelligent messaging network connection message back to the connector in reply.
- c) When the connecting server receives a “connection reply message” the connecting server can also verify the message version and type and can either keep the connection open, or close the connection if, e.g., the version and type verification fail.
- d) If the connecting server does not receive an intelligent messaging network connection reply message within the specified time window, the connecting server can assume that the peer server is, e.g., not a valid intelligent messaging network server, or is functioning improperly and so it can close the TCP connection to the peer server.
- a) The connecting server can send an intelligent messaging network ServerConnect message to the peer server. This message can contain the connecting server's unique database registration ID (obtained when the server first registered in the database, see
- 1. Upon start-up, an intelligent
-
- Server Class—
PG 116,BES 122, andMR 124; - Server Type—
PGs 116 types can include CDPD, Mobitex and ISP dialup.BES 122 types can depend on the server application; - Packet Header Version—can indicates the version of the packet header that the server supports; and
- IP Address and Listener Port—can indicate the IP address and the listener port number to be connected to by other servers in order to communicate with this server.
- Server Class—
ServiceTypes Table |
Column Name | Type | Description |
ServiceName | varchar[30] | Service Name |
TypeID | int | ID of the Service |
AllowMultiAccess | bit | True if service allows multiple device |
access from a single user, false if | ||
only allows single device access from | ||
single user concurrently | ||
1.1.2 RegisteredServers Table
The RegisteredServers table is used during the connection process and keeps track of the location and type of all Servers currently running on the Network. Access to this table is through the Server SDK.
RegisteredServers Table |
Column Name | Type | Description |
DbID | long | Unique DB ID used for cross referencing |
ServiceName | varchar[30] | Server Name |
Class | int | Server Class e.g. FES (PG), BES, |
etc | ||
SubClass | int | Server Subclass e.g. CDPD, Mobitex, etc |
DeathCount | int | The number of times connecting Servers |
have failed to connect to the Server | ||
ServerId | byte | Optional ID used for Server-Specific |
Message Routing | ||
NetHdrVersion | int | Network header version supported by |
this Server. | ||
IP Address | varchar[15] | Network location of Server |
Port | short | Listener port Server monitors for |
connection requests | ||
PortB | short | A second port the Server monitors |
Domain | varchar[20] | Name of the Domain the Server is |
running in | ||
Registration | FILETIME | Date/Time when Server registered |
Time | ||
1.1.3 ServerMsgMap Table
The ServerMsgMap is accessed during Server Registration,
ServerMsgMap Table |
Column Name | Type | Description |
ServerDBID | long | Cross reference to DBID column in |
RegisteredServer Table | ||
ServiceType | int | Type of Service message handled by this Server |
MessageID | int | Message Identifier of message handled by this |
Server | ||
ServerID | byte | Optional ID used for Server-Specific Message |
Routing | ||
1.1.4 AuthorizedUsers Table
The AuthorizedUsers table is accessed during Message authentication. The table contains a list of UserIDs/Passwords with authorized access to the intelligent messaging network Network. Access to this table is through the Server SDK.
AuthorizedUsers Table |
Column Name | Type | Description |
UserID | varchar[25] | Identifier chosen by the customer e.g. |
(rudy, RudyB etc). This is the login ID for | ||
ISP dial-up service. | ||
Password | varchar[25] | Customer Password |
AccountNo | char[8] | Customer Account Identifier |
CustomerID | long | Unique CustomerID used for cross |
referencing | ||
1.1.5 AuthorizedDevices Table
The AuthorizedDevices table is accessed during message authentication. This table contains a list of device addresses with authorized access to the intelligent messaging network Network. Entries may be permanent (a Mobile client Device) or temporary (a Wire-line device). Access to this table is through the intelligent messaging network Server.
AuthorizedDevices Table |
Column Name | Type | Description | |
DevAddress | varchar[25] | Mobile client device address | |
(IP, MAN, etc) | |||
| bit | 0 = Mobile client, 1 = Wire-line | |
CommType | int | Communication Type (CDPD, Mobitex, | |
CDMA, etc) of the client device | |||
Authentication | int | No. of | |
Count | device | ||
AccessFlag | int | Used to block access for devices reported | |
missing or stolen | |||
CustomerID | long | Cross reference to Customer ID in | |
AuthenticatedUsers table | |||
Token | long | Token used for security with wireline | |
devices | |||
1.1.6 UserRights Table
The UserRights table is accessed during message authentication. This table contains the service types an authorized user can access. Access to this table is through the Server SDK.
UserRights Table |
Column Name | Type | Description |
CustomerID | long | Cross reference to CustomerID in |
AuthenticatedUsers table. | ||
ServiceType | int | Service Type the Customer is authorized to use. |
Cross reference to TypeID in ServiceType table. | ||
1.1.7 ActiveUsers Table
The ActiveUsers table is accessed during message authentication. This table contains the list of active customer IDs and the services they are using with a count of
ActiveUsers Table |
Column Name | Type | Description |
CustomerID | long | Cross reference to CustomerID in |
AuthenticatedUsers table. | ||
ServiceType | int | Service type in use by Account No |
MRCount | byte | Number of |
authenticated the account for the service in | ||
use | ||
CommType | smallint | Communication Type (CDPD, Mobitex, |
etc) of the client device | ||
LinkStationID | varchar[25] | IP/Port or Mobitex Address |
1.1.8 CommTypes Table
The CommTypes table is a list of all communication Protocols supported by the intelligent messaging network.
CommTypes Table |
Column Name | Type | Description |
CommName | varchar[25] | Name of the communication Protocol |
TypeID | smallint | Communication Type ID |
1.2 Stored SQL Procedures
SQL procedures are used to manage the database. The following is a list of definitions commonly used as parameters in the stored SQL procedures.
CustomerID—The customer's unique identifier.
UserId—The user Id is used to authenticate ISP dial-up access.
Password—The password is used to authenticate dial-up access.
AccountNo—The account number can be both alpha and/or numeric and is for customer service purposes.
Service Type—The service type the customer is provisioned to access. For example, MarketClip, MarketTrader, etc.
DeviceAddress—For CDPD devices, this is an IP address in dot notation. For Mobitex, this is a MAN number.
Comm Type—The type of Network Protocol the client device is using to access the intelligent messaging network Network. For example, CDPD, Mobitex, CDMA.
DeviceType—The type of access to the intelligent messaging network Network, either wireless or wireline.
NotifyAMR—True to notify all
ReturnCode—The return code from the stored procedure.
1.2.1 NewCustomer
-
- ReturnCode (int)—0=Success, 1=Bad parameter, 2=Duplicate device address, 3=invalid customer id, 4=Customer already has device address.
1.2.9 DeleteDevice
This stored SQL procedure allows customer service to delete a device address from a defined customer in the database.
Input:
- ReturnCode (int)—0=Success, 1=Bad parameter, 2=Duplicate device address, 3=invalid customer id, 4=Customer already has device address.
Input:
-
- DeviceAddress (varchar[25])
- NotifyAMR 24 (bit)—True to suspend the device address from all
MRs 124 memory, false not to.
Output: - ReturnCode (int)—0=Success, 1=Error creating Server Manager, 2=Error calling Server Manager.
1.2.14 ReactivateDevice
This stored SQL procedure allows customer service to reactivate a device address' access to the intelligent messaging network.
Input:
-
- 1. The client application can send an application request message to the MR 124 (the
PG 116 is not explicitly involved in authentication), i.e., a device authentication; - 2. The client application running on a client device may fail the authentication of the
MR 124;- There are several ways a client application running on a client device can fail authentication. The
MR 124 cannot find the device address in its local cache or the AuthorizedDevices table in the intelligent messagingnetwork MR database 128. The device's security token in the LinkStationID is not the same as the device's security token in the intelligent messagingnetwork MR database 128. The subscriber does not have user rights to the requested service.
- There are several ways a client application running on a client device can fail authentication. The
- 3. The
MR 124 can send a a negative acknowledgment (NACK) message to the client application with the appropriate error code; - 4. The client application can respond with an authentication request message including an UserID, secure password, and the requested service type to authenticate; i.e., reauthentication;
- 5. The
MR 124 can check the UserID and password against the AuthorizedUsers in theMR DB 128;- If the UserID/password are valid, the
MR 124 can verify that the subscriber has rights to the requested service. If the subscriber does have user rights to the service, theMR 124 can add the device address to the AuthorizedDevices table, as well as to theMR 124 local cache and can assign a security token to the client application running on theclient device 112.
- If the UserID/password are valid, the
- 6. The
MR 124 can send an authenticated response message with a success value to the client application to let the client application know that the client application has been authenticated; the security token can also be sent to theclient device 112; i.e., an indication of success; - 7. The client application can re-send the original message (step 1) that caused the authentication challenge with the new security token; i.e., send request; and
- 8. The
MR 124 can verify the device address against the authentication cache of theMR 124 and can forward the message to theproper BES 122 or HBES 132 (not shown).
- 1. The client application can send an application request message to the MR 124 (the
-
- 1. Client application can send an application message to the MR 124 (again, the
PG 116 is not explicitly involved in authentication, in an exemplary embodiment, all client/MR 124 communications can pass through the PG 116); i.e., device authentication; - 2. The
client device 112 can fail theMRs 124 authentication;- There are several ways a device can fail authentication. For example, the
MR 124 cannot find the device address in its local cache or the AuthorizedDevices table in the intelligent messagingnetwork MR database 128. The security token of theclient device 112 in the LinkStationID can be not the same as the device's security token in the intelligent messagingnetwork MR database 128. The user of theclient device 112 can not have user rights to the requested service.
- There are several ways a device can fail authentication. For example, the
- 3. The
MR 124 can send a negative acknowledgment (NACK) message to the client application with the appropriate error code; - 4. The client application can respond with an authentication request including the UserID, secure password and the requested service type to authenticate; i.e., logon with userid and password;
- 5. The
MR 124 can check the UserID and password against the AuthorizedUsers in theMR DB 128; the UserID, password can be invalid and/or the user can not have rights to the requested service; - 6. The
MR 124 can send an authentication response message with a failure value to the client application to let it know that the authentication has failed; i.e., authentication failure; and - 7. The client may choose to prompt the
client user 102, e.g., to re-enter the UserID and password and repeat the flow diagram 500 starting fromstep 4; i.e., retry.
- 1. Client application can send an application message to the MR 124 (again, the
-
- 1. The client application that can be running on
client device 112 can create an application request (APP REQ) message and can pass the message to the transport layer to transmit over thenetwork 212; - 2. The transport layer can determine if the message needs to be segmented into multiple segments; the transport layer can transmit the message over the network and can wait for a transport level ACK;
- 3. Upon receiving the APP REQ message, the
PG 116 can assemble the message segment into a complete application message (if necessary) and can send the application message to the nextavailable MR 124;- If no
MR 124 is available, a NACK message can be generated by thePG 116 and can be sent back to the client application with the appropriate error code. Preferably, thePG 116 can not immediately send a transport ACK message back to the client application. This can be done when theBES 122 receives the application message and sends an ACK control message back to thePG 116.
- If no
- 4. The
MR 124 can look up the device address and the service type (first in its local cache, then if necessary in the intelligent messaging network MR DB 128) to see if the message is from an authorized source;- If the message is from an authorized source, the
MR 124 can choose the nextavailable BES 122 that has been registered to support the specified service type and can then send the message to thatBES 122. If there are noBESs 122 registered that can support the specified service type, a NACK message can be generated by theMR 124 and can be sent back to the client application with the appropriate error code.
- If the message is from an authorized source, the
- 5. Upon receiving the application message from the
MR 124, theBES 122 can send an acknowledgement (ACK) control message back to thePG 116 that received the application message; theBES 122 can also process the incoming message; and - 6. Upon receiving the ACK control message from the
BES 122, thePG 116 can send a transport ACK message to the client application atclient device 112; in some exemplary embodiments, sending ACK messages can be optional.
- 1. The client application that can be running on
-
- In
step 618,PG 116 can send acknowledgement of receipt of the multi-segment message at theBES 122 on toclient device 112.PG 116 can also send acknowledgment of receipt ofsegment 2 of the message as well. In one exemplary embodiment acknowledgment of receipt of the second segment can occur followingstep 606. Fromstep 618, flow diagram 602 can immediately complete.
- In
-
- 1. A
BES 122 can respond to a client application request as illustrated in flow diagram 600; theBES 122 can pass the response message (REQ RESP), message flags, customer ID and LinkStationID (cached from the previous incoming request) in flow diagram 700, which can represent a second or so-called “send” call;- Message flags can specify whether to compress and/or encrypt the message and whether the
BES 122 requires an ACK message when thePG 116 has successfully delivered the application message to the client application running onclient device 112. TheBES 122 can send the application message to the nextavailable MR 124. If noMR 124 is available, then a false can be returned from the send.
- Message flags can specify whether to compress and/or encrypt the message and whether the
- 2. The
MR 124 can use the LinkStationID to determine the associated communication type (e.g., CDPD, Mobitex, etc.) and can send the message to the nextavailable PG 116 of the correct communication type; - 3. The
PG 116 can segment the application message (if necessary) and can transmit the application message over the network; - 4. The transport layer can receive the message segment and can assemble the message segment into a complete application message (if necessary); the transport layer can send a transport ACK message to the
PG 116 that sent the message; it is important to note that, in some exemplary embodiments, sending ACK messages can be optional; and - 5. When the
PG 116 receives the transport ACK from the client application, thePG 116 can send an ACK control message back to the BES 122 (via the MR 124) that was the source of the original message (if required).
- 1. A
- 1. a
BES 122 can send an unsolicited alert to a client application; theBES 122 can pass the alert message, message flags, null LinkStation ID and customer/application information on the send call;- The customer/application information can include the customer ID or the customer ID and the port number of the client application running on
client device 112. Message flags can specify whether to compress and/or encrypt the message and whether theBES 122 requires an ACK message when thePG 116 has successfully delivered the message to the client application. TheBES 122 can then send the alert message to the nextavailable MR 124. If noMRs 124 are available, then a false can be returned from the send call.
- The customer/application information can include the customer ID or the customer ID and the port number of the client application running on
- 2. The
MR 124 can use the customer/application information to send the alert message;
If the customer/application information includes only the customer ID, then theMR 124 can search the local cache of theMR 124 and, if necessary, can search the ActiveUsers table to obtain the LinkStation ID associated with the customer ID. If the customer/application includes both the customer ID and application port number then theMR 124 can search the local cache of theMR 124 and may also search the first device assigned to the customer ID in the AuthorizedDevices table to obtain the LinkStation ID. TheMR 124 can use the LinkStation ID to determine a communication type (e.g., CDPD, Mobitex, etc.) associated with the client device and can send the message to the nextavailable PG 116 of the correct communication type. If the customer/application information includes only the customer ID and the LinkStation ID and these are not found in the local cache or ActiveUsers table, theMR 124 may not be able to send the outgoing message to the client application without further information. In this case, theMR 124 can send a customer inactive message back to theBES 122 that was the source of the outgoing message. If the customer/application information is both the customer ID and port number of the client application running onclient device 112, then the message can always be sent if a device address is found in the AuthorizedDevices table for the customer ID. If the customer ID is not found, then theMR 124 may send an Invalid Customer message back to theBES 122 that was the source of the outgoing message. - 3. The
PG 116 can segment the alert into message segments (if necessary) and can transmit the alert or message segments over the network; - 4. The transport protocol layer can receive the alert or message segments and can assemble the message segment into a complete alert (if necessary); the transport protocol layer can send a transport ACK message to the
PG 116 that sent the message; it is important to note that, in some exemplary embodiments, sending ACK messages can be optional; and - 5. The
PG 116 can receive the transport ACK from the client application running onclient device 112, and can send an ACK control message back to theBES 122 that was the source of the original message (if required). The ACK may be returned to theBES 122 viaMR 124.
-
- The client information object can include the customer ID and device ID. The device ID can be set to a define value of ALL_DEVICES if the
BES 122 wants to send the alert to all devices owned by the customer. Alternatively, theBES 122 can specify a specific device ID if theBES 122 wants to target a specific customer's device. Message flags can specify 1) whether theBES 122 requires an ACK message when thePG 116 has successfully delivered the message to the client application (ACK_REQUIRED flag is set), 2) that the intelligent messaging network only try sending the alert if the client is active on the network (SEND_IF_ACTIVE_ONLY flag is set), 3) that thePG 116 should only try sending the message once and not perform retries (SEND_ONLY_ONCE flag is set). The compression flags can indicate if the message needs to be compressed or not and, if so, what algorithm to use. The encryption flags can indicate if the message needs to be encrypted or not and, if so, what encryption algorithm to use.
2. TheMR 124 can use the customer ID and device ID information to send the alert message; - The LinkStation ID in the client information object is null so the
MR 124 should use the customer ID and device ID to construct one or more LinkStation ID(s). The following are 4 possible scenarios. - 1) If the message send flag is set to SEND_IF_ACTIVE_ONLY and device ID is specified, then the
MR 124 may first looks in its local cache to obtain the LinkStation ID of the specified device. If the device is not found in its local cache, the device could be active within the network on someother MR 124. Therefore theMR 124 may look in an ActiveUsers table to obtain the LinkStation ID of the customer's device. - 2) If the message send flag is set to SEND_IF_ACTIVE_ONLY and device ID is set to ALL_DEVICES, then the
MR 124 should only look in the ActiveUsers table to obtain the LinkStation ID's of all the customer's devices active on the network. - 3) If the message flag is not set to SEND_IF_ACTIVE_ONLY and the device ID is specified, then the
MR 124 may first look in its local cache to obtain the LinkStation ID of the specified device. If the device is not found in its local cache, then theMR 124 should look in an AuthorizedDevices table to obtain the LinkStation ID. - 4) If the message flag is not set to SENDIF_ACTIVE_ONLY and the device ID is set to ALL_DEVICES, then all of the customer's device(s) information is retrieved from the AuthorizedDevices table.
- Using the retrieved information, the
MR 124 constructs the LinkStation ID(s). If the device(s) are found, either from the cache or the database, theMR 124 uses the Linkstation ID of each device to determine the associated communication type (e.g., CDPD, Mobitex) and can send the message for each LinkStation ID(s) to the nextavailable PG 116 of the correct communication type. If no device(s) are found, theMR 124 sends a customer inactive message if the send message flag is set to SEND_IF_ACTIVE_ONLY. Otherwise theMR 124 can send a customer not valid message back to theBES 122 that was the source of the alert message.
- Using the retrieved information, the
- The client information object can include the customer ID and device ID. The device ID can be set to a define value of ALL_DEVICES if the
5. The
-
- Utility Library;
- Transport Library; and
- Security Library.
-
- Designate Target Destination—The client application can specify the) target destination of the machine to receive the message.
- Notification of Success/Failure of Transmission—The client application receives notification of the success or failure of the message transmission. For those platforms that support a multi-threaded environment (e.g. WinCE), the notification mechanism can be via an event that the transport library asserts. For those platforms that do not support a multi-threaded environment (e.g. Palm OS), the client application may be required to continuously poll the transport library to determine if the message transmission was successful or failed.
- Message Segmentation—All messages that are greater than the maximum segment size (configurable) should be segmented into multiple message segments.
- Message Re-Assembly—All multi-segmented messages received are re-assembled into a single message prior to presenting the message to the client application running on
client device 112. - Message Retries—All message segments that are not acknowledged by the peer wireless protocol layer within the configured time may be retried the configured number of attempts before notifying the client application that the message was delivered (acknowledgment) or not (negative acknowledgment).
- Configurable Communication Parameters—The communication parameters for the mobile client transport library can be tailored to the required communication behavior. These values can be configured via the registry (WinX platforms) or the preferences database (Palm OS platforms) prior to opening the mobile client transport library.
- Duplicate Message Segment Detection—All duplicate message segments received by the mobile client transport library can be acknowledged back to the peer wireless protocol layer, discarded, and conditionally logged.
- Duplicate Message Detection—All duplicate messages received by the mobile client transport library can be acknowledged back to the peer wireless protocol layer, discarded, and conditionally logged.
-
-
VER 902 - This field contains the version number of the Segment Header. It consists of two bits,
bit 0 andbit 1 of the 1st word in the Segment Header. Valid values are 0 through 3. -
MESSAGE ID 904 - This field contains a message identification value. It consists of thirteen bits,
bits 2 through 14 of the 1st word in the segment header. Valid values are 0 through 8,192. The transport protocol layer uses the message ID to discard segment/message duplications and to match acknowledgments with messages. -
FLAGS 906 - This field contains protocol information. It consists of five bits,
bits 15 through 19. Valid values are: - Bit 19—segmentation indicator (0—message not segmented, 1—message segmented)
- Bit 18—reserved
- Bit 17—reserved
- Bit 16—message type (0—positive acknowledgment, 1—negative acknowledgment)
-
Bit 15—message indicator (0—application message, 1—AIM control message) -
TOTAL LENGTH 908 - This field contains the total number of bytes contained in the message segment to be sent including the segment header. It consists of twelve bits,
bits 20 through 31 of the 2nd word in the segment header. Valid values are 4 through 4,096. -
SEGMENT NUMBER 910 - This field identifies the number of this message segment. It consists of 8 bits,
bits 0 through 7 of the 3rd word in the segment header. Valid values are 2 through 255. The peer wireless protocol layer uses this number to re-order the message segments into a single complete message. NOTE: This field is present only if the segmentation indicator is set in the flags field.
-
-
- Key Exchanee—Public and private keys may be used periodically to establish a common secret key that both the client application running on a client device and server use when exchanging messages. The reason for this is that the overhead of encrypting using public/private keys is much higher than when using a single secret key. The message flows to securely establish a secret key between a client application running on a client device and a server is the responsibility of the security library.
- Encryption—Mobile client application running on a client device can optionally encrypt application messages prior to transmitting the message to the target destination. Messages are encrypted with the secret key negotiated between the client application running on a client device and the server. Encryption is preferably always performed after compression.
- Decryption—Mobile client applications running on a client device can optionally decrypt client application messages prior to processing the message. To determine if a message needs to be decrypted, client applications can check the encryption flag contained in the message header. Messages are decrypted with the secret key negotiated between the client applications running on a client device and the server. Decryption is preferably always performed before compression.
- 1. Server classes—These are the core classes that server application developers use when creating
new PGs 116 andBESs 122. These classes may have no Graphical User Interface (GUI); thereby allowing developers to provide their own custom interfaces. - 2. Server user interface classes—These classes provide a graphical interface to the Server classes. Use of these classes is not required when developing a new Server.
AIM Server Classes
-
- Version (4 bits)—The version number of the AIMSvrPacket.
- Header Length (4 bits)—The length of the AIMSvrPacket header in bytes. The AIMSvrPacket header consists of the first 5 fields of the AIMSvrPacket: version, header length, flags, total packet length and source server ID. This length is used by the TCP connection classes to read enough of the packet in order to determine the total size of the remainder of the packet.
- Flags (BYTE)—contains protocol information. It consists of eight flag bits, valid values are:
-
Bit 1—acknowledgment indicator (1—ACK required, 0—ACK not required) -
Bit 2—message type indicator (1—server connect message) - Bits 3-8—reserved for future use.
- Total Packet Length (unsigned long)—Contains the total number of bytes in the AIMSvrPacket (including the packet header).
- Source Server Database ID (unsigned long)—Contains Database ID (a unique value assigned to a server when the server registers itself in the intelligent messaging
network MR database 128 of the originator of the packet. - LinkStationID (variable length)—Contains the device address of the source or destination of the message contained in the packet. This field's size and content varies depending on the communications type (CDPD, Mobitex, etc) of the device.
- Message ID (unsigned short)—server packet message identifier.
- Customer ID (unsigned long)—intelligent messaging
network MR database 128 ID of the customer who owns the device targeted by the message in the server packet. Although preferably always present, this field does not always contain a valid value and is set to 0 when not valid. This field is not valid when the AIMSvrPacket contains a network control message (server-to-server messages independent of application messages) or when passing a client message to/from aPG 116 andMR 124. The primary purpose of the field is forMR 124 toBES 122 communications, to identify the message source on incoming messages, and target a specific customer device on outgoing messages. - Port Number (unsigned short)—customer device port number. Although preferably always present in the packet, this field only contains a valid (non-zero) value when a
BES 122 sends an unsolicited message to a device. - Intelligent Messaging Network Message Header (in an exemplary embodiment can include 6 BYTES)—All application messages should prefix the intelligent messaging network message header to the beginning of the application message. The intelligent messaging network message header may consist of the following fields:
- 1. Compression Bits (3-bits)—0=message is not compressed, 1=System supplied compression type, 2=supplier supplied compression type, 3=application supplied compression type.
- 2. Security Bits (3-bits)—0=message is not encrypted, 1=System supplied encryption, 2=Supplier supplied encryption, 3=application supplied encryption.
- 3. Version (3-bits)—Message header version.
- 4. Reserved Bits (7-bits)—Reserved for future versions.
- 5. Service Type (12-bits)—Identifies which type of service (MarketClip, FX) the message pertains to. This field is used by both indirect and direct routing.
- 6. Message Type (12-bits)—Uniquely identifies the message within the context of the specified service type.
- 7. Server ID (1-byte)—Identifies a
specific BES 122 of the given service type. The value of 0 is reserved to indicate that indirect routing is desired. A non-zero value indicates that the message is targeted at aspecific BES 122.- Message Body (variable length)—Contains the body of the application message.
AeFEServer Class (for the PGs)
The AeFEServer class subclasses AeServer and encapsulates those functions that are common to allPGs 116. AllPGs 116 should be derived from the AeFEServer class. This class may perform the following functions on behalf of all PGs 116: - Encapsulates the Transport Header—Only this class preferably knows the implementation details of the transport header. The transport header contains control information for communicating between the intelligent messaging network enabled client applications and
PGs 116. - Asynchronous (non-blocking) Notification of Success/Failure of Transmission—This class optionally notifies the original sender of the message indication of the success or failure of the message transmitted to the client application running on
client device 112.- Message Segmentation—All outbound server messages to be sent to the client application that are greater than the maximum segment size (configurable) can be segmented into multiple message segments.
- Message Re-Assembly—All multi-segmented messages received from the client application can be re-assembled into a single message prior to sending the message to a
MR 124 to route to a registeredBES 122. - Message Retries—All message segments that are not acknowledged by the client device peer wireless protocol layer within the configured time can be retried the configured number of attempts before notifying the original sender that the message was delivered (acknowledgment) or not (negative acknowledgment).
- Message Pacing—For large multi-segmented messages, many device modems cannot keep up if they are quickly flooded with a series of segments.
PGs 116 contain a configurable setting that can be set to slow up the transmission of messages larger than a specified number of segments. - Duplicate Message Segment Detection—All duplicate message segments received from the client device are acknowledged back to the client device peer wireless protocol layer, discarded, and conditionally logged.
- Duplicate Message Detection—All duplicate messages received from the client device can be acknowledged back to the client device peer wireless protocol layer, discarded, and conditionally logged.
- Configurable Communication Preferences—The communication parameters for the
PG 116 can be configured to tailor the communication behavior. These values are configured prior to the starting thePG 116.
AeBEServer Class
The AeBEServer class subclasses from AeServer and can encapsulate those functions that are common to allBESs 122. This class may performs the following functions on behalf of all BESs 122:
- Generate ACK Control Messages—When this class receives an incoming from a
PG 116 routed viaMR 124, it can create an ACK control message and send it back to theoriginating PG 116 via aMR 124. When thePG 116 receives this ACK control message, it sends a transport layer ACK message to the client application on a client device that originated the message indicating that the message was delivered to theBES 122. - Process ACK Control Messages—When this class receives an ACK control message from a
PG 116, indicating that the server application message was delivered to the client device, it notifies the derivedBES 122. - Message Compression/Decompression—AeBEServer is responsible for compressing any outgoing messages and decompressing incoming messages. If an AIM provided compression type is involved, compression/decompression is done transparently relative to any subclasses of this type. Alternately, AeBEServer subclasses may implement compression in their message serialization.
- Message Encryption/Decryption—AeBEServer is responsible for encrypting any outgoing messages and decrypting incoming messages. If an AIM provided encryption type is involved, encryption/decryption is done transparently relative to any subclasses of this type. Alternately, AeBEServer subclasses may implement their own encryption algorithms by implementing the appropriate virtual methods that is invoked by AeBEServer at the appropriate times.
DerivedPGs 116
- Message Body (variable length)—Contains the body of the application message.
-
- Encapsulate the Communication Layer—Derived
PGs 116 provide the network specific interface to the communication layer used by thePG 116. The parent class (AeFEServer) does not know the implementation details of the underlying protocol layer used to send and receive messages to and from client applications running onclient devices 112. This is the sole responsibility of the derivedPG 116.
DerivedBESs 122
AllBESs 122, developed by the intelligent messaging network can be derived from either the AeBEServer. DerivedBESs 122 may provide the following functions: - Process application Specific Messages—All application specific knowledge is implemented in the derived
BES 122. For example, a news service can provide client devices with news stories related to a specific financial entity. The derived new services' parent class hierarchy (AeBEServer and AeServer) does not know the implementation details of the application message protocol. This is the sole responsibility of the derivedBES 122. - Special Compression Services—If a
BES 122 has specific compression requirements for their application data that is not addressed by the Intelligent messaging network supplied compression, theBES 122 is responsible for providing the compression mechanism. - Special Security Services—If a
BES 122 has specific encryption requirements for their application data that is not addressed by the Intelligent messaging network supplied encryption, the derivedBES 122 is responsible for providing the encryption mechanism.
Server User Interface Classes
- Encapsulate the Communication Layer—Derived
- 1. Persistent storage of configurable server settings as well as a common user interface for viewing/editing those settings.
- 2. Screen based error logging.
- 3. NT Event Log error logging and automatic batch file error notification.
- 4. Inbound/outbound message logging.
- 5. Inbound/outbound message statistics.
- 1. Persistent storage of configurable server settings and common user interface framework for viewing/editing those settings.—Persistent storage is implemented through the Windows registry and AeServerApp provides the base registry key for all of its subclasses to use. AeServerApp also provides a standard method of viewing/editing server settings in the form of a PropertySheet. Subclasses provide for their own individual server settings by adding PropertyPages to the base class PropertySheet. AeServerApp provides a common page for handling server settings common to all server types.
- 2. Screen based error logging.—In addition to providing a window where system events and errors can be displayed, AeServerApp also supplies a separate logging thread that can be used by subclasses when displaying output to their own windows. This thread runs at lower priority then the server processing threads so that screen logging does not negatively impact performance.
- 3. NT Event Log error logging and automatic batch file error notification.—AeServerApp provides a mechanism whereby system errors can be written to the NT Event log. The level of error reporting is configurable. In addition to the NT Event log, users may specify that a batch file be executed when an error of a specified severity occurs. Such batch files could be used to communicate problems to a system administrator via email or a pager.
AeFEServerApp
- 1. PG specific server settings—Preferably provides a user interface and persistent storage for transport settings such as maximum number of retries, retry timeout interval, segment size, etc.
- 2. Inbound/Outbound message logging—Provides two windows that log each inbound and outbound message. Makes use of the AeServerApp logging thread. Logging may be enabled/disabled for either window.
- 3. PG specific statistics—Gathers and displays statistical totals such as number of messages sent/received, number of ACKS/NACKS sent/received.
AeBEServerApp and CBEServerSampleApp
- 1. Inbound/Outbound message logging—Preferably provides two windows that log each inbound and outbound message. Makes use of the AeServerApp logging thread. Logging may be enabled/disabled for either window.
- 2. Back-End specific statistics—Gathers and displays statistical totals such as number of messages sent/received, number of ACKS/NACKS sent/received, and compressed vs. uncompressed byte totals.
- 3. Application message log view—Provides an additional logging window that applications should use to log their own errors or trace statements rather than intermingling them with the system messages in the system log window.
-
- CDPD
- Mobitex
- Dial-Up
- TCP/IP LAN
-
- Number of messages to send
- Application defined messages
- Relative send frequencies for each message type
- Compression
-
- Total messages sent
- Average message response time
Claims (36)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/735,235 US9438700B2 (en) | 2000-01-31 | 2013-01-07 | System and method for servers to send alerts to connectionless devices |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US49455300A | 2000-01-31 | 2000-01-31 | |
US69429700A | 2000-10-24 | 2000-10-24 | |
US09/732,285 US6435164B1 (en) | 2000-12-07 | 2000-12-07 | Fuel weathering method for vehicle evaporative emission system |
US13/735,235 US9438700B2 (en) | 2000-01-31 | 2013-01-07 | System and method for servers to send alerts to connectionless devices |
Related Parent Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US69429700A Continuation-In-Part | 2000-01-31 | 2000-10-24 | |
US09/723,285 Continuation US8370435B1 (en) | 2000-01-31 | 2000-11-28 | System and method for servers to send alerts to connectionless devices |
US09/732,285 Continuation US6435164B1 (en) | 2000-01-31 | 2000-12-07 | Fuel weathering method for vehicle evaporative emission system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/723,285 Continuation-In-Part US8370435B1 (en) | 2000-01-31 | 2000-11-28 | System and method for servers to send alerts to connectionless devices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130212195A1 US20130212195A1 (en) | 2013-08-15 |
US9438700B2 true US9438700B2 (en) | 2016-09-06 |
Family
ID=24942938
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/732,285 Expired - Lifetime US6435164B1 (en) | 2000-01-31 | 2000-12-07 | Fuel weathering method for vehicle evaporative emission system |
US13/735,235 Expired - Fee Related US9438700B2 (en) | 2000-01-31 | 2013-01-07 | System and method for servers to send alerts to connectionless devices |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/732,285 Expired - Lifetime US6435164B1 (en) | 2000-01-31 | 2000-12-07 | Fuel weathering method for vehicle evaporative emission system |
Country Status (1)
Country | Link |
---|---|
US (2) | US6435164B1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150140933A1 (en) * | 2013-11-15 | 2015-05-21 | Gpshopper, Llc | Method and system for distributed management of remote transmitters interacting with mobile devices |
US20210129865A1 (en) * | 2019-11-04 | 2021-05-06 | Research & Business Foundation Sungkyunkwan University | Context-aware navigation protocol for safe driving |
US11974197B2 (en) | 2021-09-13 | 2024-04-30 | Synchrony Bank | Method and system for distributed management of remote transmitters interacting with mobile devices |
Families Citing this family (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3714189B2 (en) * | 2001-04-24 | 2005-11-09 | 日産自動車株式会社 | Lubrication system |
US6892712B2 (en) | 2001-09-11 | 2005-05-17 | Denso Corporation | Leak check for fuel vapor purge system |
US7353455B2 (en) * | 2002-05-21 | 2008-04-01 | At&T Delaware Intellectual Property, Inc. | Caller initiated distinctive presence alerting and auto-response messaging |
US6877488B2 (en) * | 2002-05-29 | 2005-04-12 | Nartron Corporation | Vehicle fuel management system |
JP4140345B2 (en) * | 2002-11-05 | 2008-08-27 | トヨタ自動車株式会社 | Evaporative fuel processing device for internal combustion engine |
DE10252225A1 (en) * | 2002-11-11 | 2004-05-27 | Robert Bosch Gmbh | Method for determining the fuel vapor pressure in a motor vehicle with on-board means |
US6935317B2 (en) * | 2003-01-31 | 2005-08-30 | Siemens Vdo Automotive Corporation | Fuel supply and diagnostics module |
US7007893B2 (en) * | 2004-02-10 | 2006-03-07 | The Boeing Company | Methods and systems for controlling flammability control systems in aircraft and other vehicles |
US7093789B2 (en) * | 2004-05-24 | 2006-08-22 | The Boeing Company | Delta-winged hybrid airship |
US8995412B2 (en) * | 2006-05-16 | 2015-03-31 | Autonet Mobile, Inc. | Mobile router network providing remote emissions testing |
US20080308072A1 (en) * | 2007-06-13 | 2008-12-18 | Raja Banerjee | Hydrocarbon separation from air using membrane separators in recirculation tube |
US20080308073A1 (en) * | 2007-06-13 | 2008-12-18 | Allen Christopher D | Evaporative emissions canister having an integral membrane |
US20080308075A1 (en) * | 2007-06-13 | 2008-12-18 | Allen Christopher D | Automotive fuel system for substantially reducing hydrocarbon emissions into the atmosphere, and method |
US20080308074A1 (en) * | 2007-06-13 | 2008-12-18 | Allen Christopher D | Evaporative emissions canister with external membrane |
US8918124B2 (en) * | 2009-03-20 | 2014-12-23 | Kenneth Bland | Communications platform |
WO2011127022A1 (en) * | 2010-04-05 | 2011-10-13 | Stoneridge, Inc. | Three-port valve |
US8056540B2 (en) * | 2010-05-28 | 2011-11-15 | Ford Global Technologies, Llc | Method and system for fuel vapor control |
US8019525B2 (en) | 2010-05-28 | 2011-09-13 | Ford Global Technologies, Llc | Method and system for fuel vapor control |
US8447495B2 (en) | 2010-05-28 | 2013-05-21 | Ford Global Technologies, Llc | Method and system for fuel vapor control |
US8464590B2 (en) * | 2010-09-17 | 2013-06-18 | Cameron International Corporation | Pressure sensor configuration for pressurized tank |
US20110162625A1 (en) * | 2010-11-03 | 2011-07-07 | Ford Global Technologies, Llc | Method and Apparatus for Evaporative Emissions Control |
DE102010061429A1 (en) | 2010-12-21 | 2012-06-21 | Dr. Ing. H.C. F. Porsche Aktiengesellschaft | motor vehicle |
DE102010055310A1 (en) * | 2010-12-21 | 2012-06-21 | Audi Ag | Fuel system and method of operating a fuel system |
JP5704338B2 (en) * | 2011-07-07 | 2015-04-22 | 三菱自動車工業株式会社 | Fuel evaporative emission control device for internal combustion engine |
JP5672454B2 (en) * | 2011-07-07 | 2015-02-18 | 三菱自動車工業株式会社 | Fuel evaporative emission control device for internal combustion engine |
US9163585B2 (en) * | 2012-05-22 | 2015-10-20 | Alte Powertrain Technologies, Inc. | Apparatus and method of determining a leak condition of a fuel system |
JP5527391B2 (en) * | 2012-11-28 | 2014-06-18 | 三菱自動車工業株式会社 | Fuel evaporative emission control device for internal combustion engine |
EP2818351B1 (en) * | 2013-06-26 | 2016-04-06 | Inergy Automotive Systems Research (Société Anonyme) | Method and system for depressurizing a vehicular fuel storage system |
US20150120165A1 (en) * | 2013-10-28 | 2015-04-30 | Sgs North America Inc. | Evaporative Emission Control System Monitoring |
EP2962887A1 (en) * | 2014-07-02 | 2016-01-06 | Inergy Automotive Systems Research (Société Anonyme) | Method for controlling a filling operation of a vehicular liquid storage system |
KR102224447B1 (en) | 2014-07-03 | 2021-03-08 | 콘비다 와이어리스, 엘엘씨 | Application data delivery service for networks supporting multiple transport mechanisms |
US9797329B2 (en) * | 2014-11-07 | 2017-10-24 | Ford Global Technologies, Llc | Method for diagnosing a vacuum actuator |
DE102015214322A1 (en) * | 2015-07-29 | 2017-02-02 | Robert Bosch Gmbh | Method for determining the loading of a storage tank for hydrocarbons |
DE102015217609A1 (en) * | 2015-09-15 | 2017-03-16 | Kautex Textron Gmbh & Co. Kg | Operating fluid container for a motor vehicle |
US10044595B1 (en) * | 2016-06-30 | 2018-08-07 | Dell Products L.P. | Systems and methods of tuning a message queue environment |
EP3498515A1 (en) * | 2017-12-18 | 2019-06-19 | Plastic Omnium Advanced Innovation and Research | Method for determining the thermodynamic state of the fuel in a fuel system |
JP7141378B2 (en) * | 2019-10-03 | 2022-09-22 | Kddi株式会社 | Terminal device, base station device, control method, and program for executing conditional handover |
WO2021089312A1 (en) * | 2019-11-04 | 2021-05-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods providing v2x application server registration |
US11636870B2 (en) | 2020-08-20 | 2023-04-25 | Denso International America, Inc. | Smoking cessation systems and methods |
US11760169B2 (en) | 2020-08-20 | 2023-09-19 | Denso International America, Inc. | Particulate control systems and methods for olfaction sensors |
US11881093B2 (en) | 2020-08-20 | 2024-01-23 | Denso International America, Inc. | Systems and methods for identifying smoking in vehicles |
US11828210B2 (en) | 2020-08-20 | 2023-11-28 | Denso International America, Inc. | Diagnostic systems and methods of vehicles using olfaction |
US11813926B2 (en) | 2020-08-20 | 2023-11-14 | Denso International America, Inc. | Binding agent and olfaction sensor |
US11760170B2 (en) | 2020-08-20 | 2023-09-19 | Denso International America, Inc. | Olfaction sensor preservation systems and methods |
US11932080B2 (en) | 2020-08-20 | 2024-03-19 | Denso International America, Inc. | Diagnostic and recirculation control systems and methods |
CN115225299B (en) * | 2021-04-19 | 2023-06-27 | 中国科学院计算机网络信息中心 | User authentication method, server and system |
Citations (81)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5564070A (en) | 1993-07-30 | 1996-10-08 | Xerox Corporation | Method and system for maintaining processing continuity to mobile computers in a wireless network |
US5583859A (en) | 1994-08-30 | 1996-12-10 | Bell Communications Research, Inc. | Data labeling technique for high performance protocol processing |
US5590122A (en) | 1994-12-22 | 1996-12-31 | Emc Corporation | Method and apparatus for reordering frames |
US5689505A (en) | 1996-01-16 | 1997-11-18 | Lucent Technologies Inc. | Buffering of multicast cells in switching networks |
US5742592A (en) | 1995-09-01 | 1998-04-21 | Motorola, Inc. | Method for communicating data in a wireless communication system |
US5754774A (en) | 1996-02-15 | 1998-05-19 | International Business Machine Corp. | Client/server communication system |
US5771353A (en) | 1995-11-13 | 1998-06-23 | Motorola Inc. | System having virtual session manager used sessionless-oriented protocol to communicate with user device via wireless channel and session-oriented protocol to communicate with host server |
US5781549A (en) | 1996-02-23 | 1998-07-14 | Allied Telesyn International Corp. | Method and apparatus for switching data packets in a data network |
US5828843A (en) | 1996-03-21 | 1998-10-27 | Mpath Interactive, Inc. | Object-oriented method for matching clients together with servers according to attributes included in join request |
US5850517A (en) | 1995-08-31 | 1998-12-15 | Oracle Corporation | Communication link for client-server having agent which sends plurality of requests independent of client and receives information from the server independent of the server |
US5862481A (en) | 1996-04-08 | 1999-01-19 | Northern Telecom Limited | Inter-technology roaming proxy |
US5862345A (en) | 1996-02-07 | 1999-01-19 | Nec Corporation | System for location multicasting and database management for mobile sessions in any computer subnetworks without using a home router of a home subnetwork |
US5894478A (en) | 1996-07-24 | 1999-04-13 | Lucent Technologies Inc. | Protocol converter and router for multi-mode wireless data communications |
US5937161A (en) | 1996-04-12 | 1999-08-10 | Usa.Net, Inc. | Electronic message forwarding system |
US5949799A (en) | 1996-12-27 | 1999-09-07 | Cypress Semiconductor Corp. | Minimum-latency data mover with auto-segmentation and reassembly |
US5970059A (en) | 1995-01-10 | 1999-10-19 | Nokia Telecommunications Oy | Packet radio system and methods for a protocol-independent routing of a data packet in packet radio networks |
US6067545A (en) | 1997-08-01 | 2000-05-23 | Hewlett-Packard Company | Resource rebalancing in networked computer systems |
US6078690A (en) | 1997-06-20 | 2000-06-20 | Olympus Optical Co., Ltd. | Image data conversion device and method having function of inserting delimiter code into position in image data where a predetermined amount of data is reached |
US6078960A (en) | 1998-07-03 | 2000-06-20 | Acceleration Software International Corporation | Client-side load-balancing in client server network |
US6108314A (en) | 1998-08-31 | 2000-08-22 | Motorola, Inc. | Method, subscriber device, wireless router, and communication system efficiently utilizing the receive/transmit switching time |
US6160793A (en) | 1998-10-13 | 2000-12-12 | Nokia Telecommunications, Oy | ECN-based approach for congestion management in hybrid IP-ATM networks |
US6167450A (en) | 1997-07-30 | 2000-12-26 | International Business Machines Corporation | Data communications management system and protocol replacement method for mobile communication environments |
US6185625B1 (en) | 1996-12-20 | 2001-02-06 | Intel Corporation | Scaling proxy server sending to the client a graphical user interface for establishing object encoding preferences after receiving the client's request for the object |
US6192029B1 (en) | 1998-01-29 | 2001-02-20 | Motorola, Inc. | Method and apparatus for performing flow control in a wireless communications system |
US6233577B1 (en) | 1998-02-17 | 2001-05-15 | Phone.Com, Inc. | Centralized certificate management system for two-way interactive communication devices in data networks |
US6247048B1 (en) | 1998-04-30 | 2001-06-12 | Openwave Systems Inc | Method and apparatus for transcoding character sets between internet hosts and thin client devices over data networks |
US6246684B1 (en) | 1997-12-24 | 2001-06-12 | Nortel Networks Limited | Method and apparatus for re-ordering data packets in a network environment |
US6252884B1 (en) | 1998-03-20 | 2001-06-26 | Ncr Corporation | Dynamic configuration of wireless networks |
US6272129B1 (en) | 1999-01-19 | 2001-08-07 | 3Com Corporation | Dynamic allocation of wireless mobile nodes over an internet protocol (IP) network |
US6311215B1 (en) | 1997-03-25 | 2001-10-30 | Intel Corporation | System for dynamic determination of client communications capabilities |
US20010037358A1 (en) | 2000-01-31 | 2001-11-01 | Ken Clubb | System and method to publish information from servers to remote monitor devices |
US6331983B1 (en) | 1997-05-06 | 2001-12-18 | Enterasys Networks, Inc. | Multicast switching |
US6343318B1 (en) | 1998-05-29 | 2002-01-29 | Palm, Inc. | Method and apparatus for communicating information over low bandwidth communications networks |
US6374305B1 (en) | 1997-07-21 | 2002-04-16 | Oracle Corporation | Web applications interface system in a mobile-based client-server system |
US6389465B1 (en) | 1998-05-08 | 2002-05-14 | Attachmate Corporation | Using a systems network architecture logical unit activation request unit as a dynamic configuration definition in a gateway |
US6393014B1 (en) | 1997-06-03 | 2002-05-21 | At&T Wireless Services, Inc. | Method and system for providing data communication with a mobile station |
US6397259B1 (en) | 1998-05-29 | 2002-05-28 | Palm, Inc. | Method, system and apparatus for packet minimized communications |
US6421733B1 (en) | 1997-03-25 | 2002-07-16 | Intel Corporation | System for dynamically transcoding data transmitted between computers |
US6445691B2 (en) | 1998-06-08 | 2002-09-03 | Koninklijke Philips Electronics N. V. | Wireless coupling of standardized networks and non-standardized nodes |
US6452910B1 (en) | 2000-07-20 | 2002-09-17 | Cadence Design Systems, Inc. | Bridging apparatus for interconnecting a wireless PAN and a wireless LAN |
US6473411B1 (en) | 1997-05-12 | 2002-10-29 | Kabushiki Kaisha Toshiba | Router device, datagram transfer method and communication system realizing handoff control for mobile terminals |
US6473609B1 (en) | 1995-12-11 | 2002-10-29 | Openwave Systems Inc. | Method and architecture for interactive two-way communication devices to interact with a network |
US6477577B1 (en) | 1996-04-05 | 2002-11-05 | Fujitsu Limited | Network connection system and connection substitute correspondence client |
US6477543B1 (en) | 1998-10-23 | 2002-11-05 | International Business Machines Corporation | Method, apparatus and program storage device for a client and adaptive synchronization and transformation server |
US6490617B1 (en) | 1998-06-09 | 2002-12-03 | Compaq Information Technologies Group, L.P. | Active self discovery of devices that participate in a network |
US6490266B1 (en) | 1998-03-31 | 2002-12-03 | Samsung Electronics, Co., Ltd. | Method for test call synchronization of code division multiple access cellular system |
US6505248B1 (en) | 1999-03-24 | 2003-01-07 | Gte Data Services Incorporated | Method and system for monitoring and dynamically reporting a status of a remote server |
US6507589B1 (en) * | 1998-04-30 | 2003-01-14 | Openwave Systems Inc. | Method and apparatus for routing between network gateways and service centers |
US6510464B1 (en) | 1999-12-14 | 2003-01-21 | Verizon Corporate Services Group Inc. | Secure gateway having routing feature |
US6512754B2 (en) | 1997-10-14 | 2003-01-28 | Lucent Technologies Inc. | Point-to-point protocol encapsulation in ethernet frame |
US6529722B1 (en) | 1998-06-19 | 2003-03-04 | Microdata | System and method for enhanced 9-1-1 address development, maintenance and call routing using road access zones |
US6529882B1 (en) | 1999-11-03 | 2003-03-04 | Electronics And Telecommunications Research Institute | Method for managing group membership in internet multicast applications |
US6539422B1 (en) | 1998-05-04 | 2003-03-25 | Intermec Ip Corp. | Automatic data collection device having a network communications capability |
US6539019B1 (en) | 1999-05-24 | 2003-03-25 | 3Com Corporation | Methods and apparatus for automatically connecting a dynamic host configuration protocol (DHCP) client network device to a virtual local area network (VLAN) |
US6563919B1 (en) | 1999-12-17 | 2003-05-13 | Nortel Networks Limited | System and method for unifying the implementation and processing of mobile communications and a unified mobility manager for providing such communications |
US6567857B1 (en) | 1999-07-29 | 2003-05-20 | Sun Microsystems, Inc. | Method and apparatus for dynamic proxy insertion in network traffic flow |
US6578066B1 (en) | 1999-09-17 | 2003-06-10 | Alteon Websystems | Distributed load-balancing internet servers |
US6590885B1 (en) | 1998-07-10 | 2003-07-08 | Malibu Networks, Inc. | IP-flow characterization in a wireless point to multi-point (PTMP) transmission system |
US6590588B2 (en) | 1998-05-29 | 2003-07-08 | Palm, Inc. | Wireless, radio-frequency communications using a handheld computer |
US6633910B1 (en) | 1999-09-16 | 2003-10-14 | Yodlee.Com, Inc. | Method and apparatus for enabling real time monitoring and notification of data updates for WEB-based data synchronization services |
US6640248B1 (en) | 1998-07-10 | 2003-10-28 | Malibu Networks, Inc. | Application-aware, quality of service (QoS) sensitive, media access control (MAC) layer |
US6665722B1 (en) | 2000-05-31 | 2003-12-16 | Bbnt Solutions Llc | Store-and-forward packet radio system and method |
US6665718B1 (en) | 1997-10-14 | 2003-12-16 | Lucent Technologies Inc. | Mobility management system |
US6675208B1 (en) | 1997-10-14 | 2004-01-06 | Lucent Technologies Inc. | Registration scheme for network |
US6681262B1 (en) | 2002-05-06 | 2004-01-20 | Infinicon Systems | Network data flow optimization |
US6683870B1 (en) * | 1997-02-10 | 2004-01-27 | Mci Communications Corporation | Method and system for multicasting call notifications |
US6691165B1 (en) | 1998-11-10 | 2004-02-10 | Rainfinity, Inc. | Distributed server cluster for controlling network traffic |
US6771742B2 (en) | 2001-11-05 | 2004-08-03 | Intrado Inc. | Geographic routing of emergency service call center emergency calls |
US6772195B1 (en) | 1999-10-29 | 2004-08-03 | Electronic Arts, Inc. | Chat clusters for a virtual world application |
US6826173B1 (en) * | 1999-12-30 | 2004-11-30 | At&T Corp. | Enhanced subscriber IP alerting |
US6857013B2 (en) | 1999-01-29 | 2005-02-15 | Intermec Ip.Corp. | Remote anomaly diagnosis and reconfiguration of an automatic data collection device platform over a telecommunications network |
US6862622B2 (en) | 1998-07-10 | 2005-03-01 | Van Drebbel Mariner Llc | Transmission control protocol/internet protocol (TCP/IP) packet-centric wireless point to multi-point (PTMP) transmission system architecture |
US6879582B1 (en) | 2000-09-29 | 2005-04-12 | Lucent Technologies Inc. | Media terminal adapter-cellular transceiver (MTA-CT) |
US20050213716A1 (en) | 2004-03-23 | 2005-09-29 | Yinjun Zhu | Solutions for voice over internet protocol (VoIP) 911 location services |
US20060072547A1 (en) | 2004-09-29 | 2006-04-06 | Lucent Technologies Inc. | Systems and methods for serving VolP emergency calls |
US20080063153A1 (en) | 2006-08-21 | 2008-03-13 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a voip system |
US20080101552A1 (en) | 2006-11-01 | 2008-05-01 | Khan Richard L | Systems and methods for location management and emergency support for a voice over internet protocol device |
US20080200143A1 (en) | 2007-02-20 | 2008-08-21 | Chaoxin Charles Qiu | Systems and methods for location management and emergency support for a voice over internet protocol device |
US20090003312A1 (en) | 2007-06-26 | 2009-01-01 | Leonardo Velazquez | Methods and apparatus to provide enhanced 911 (e911) services for nomadic users |
US20090103687A1 (en) | 2007-10-17 | 2009-04-23 | Vixxi Solutions, Inc. | Geographic referenced telephone switching |
US7711094B1 (en) | 2005-11-16 | 2010-05-04 | Verizon Data Services Llc | E911 location server |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4547201A (en) * | 1983-12-14 | 1985-10-15 | International Coal Refining Co. | SRC Residual fuel oils |
US4815323A (en) * | 1985-06-28 | 1989-03-28 | Simmonds Precision Products, Inc. | Ultrasonic fuel quantity gauging system |
US5490414A (en) | 1992-08-21 | 1996-02-13 | Mercedes-Benz Ag. | Method for detecting leaks in a motor vehicle tank ventilation system |
GB9302958D0 (en) | 1993-02-13 | 1993-03-31 | Lucas Ind Plc | Method of and apparatus for detecting fuel system leak |
US5878727A (en) | 1997-06-02 | 1999-03-09 | Ford Global Technologies, Inc. | Method and system for estimating fuel vapor pressure |
US6016690A (en) | 1997-09-05 | 2000-01-25 | Siemens Canada Limited | Automotive evaporative emission leak detection system and method |
-
2000
- 2000-12-07 US US09/732,285 patent/US6435164B1/en not_active Expired - Lifetime
-
2013
- 2013-01-07 US US13/735,235 patent/US9438700B2/en not_active Expired - Fee Related
Patent Citations (82)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5564070A (en) | 1993-07-30 | 1996-10-08 | Xerox Corporation | Method and system for maintaining processing continuity to mobile computers in a wireless network |
US5583859A (en) | 1994-08-30 | 1996-12-10 | Bell Communications Research, Inc. | Data labeling technique for high performance protocol processing |
US5590122A (en) | 1994-12-22 | 1996-12-31 | Emc Corporation | Method and apparatus for reordering frames |
US5970059A (en) | 1995-01-10 | 1999-10-19 | Nokia Telecommunications Oy | Packet radio system and methods for a protocol-independent routing of a data packet in packet radio networks |
US5850517A (en) | 1995-08-31 | 1998-12-15 | Oracle Corporation | Communication link for client-server having agent which sends plurality of requests independent of client and receives information from the server independent of the server |
US5742592A (en) | 1995-09-01 | 1998-04-21 | Motorola, Inc. | Method for communicating data in a wireless communication system |
US5771353A (en) | 1995-11-13 | 1998-06-23 | Motorola Inc. | System having virtual session manager used sessionless-oriented protocol to communicate with user device via wireless channel and session-oriented protocol to communicate with host server |
US6473609B1 (en) | 1995-12-11 | 2002-10-29 | Openwave Systems Inc. | Method and architecture for interactive two-way communication devices to interact with a network |
US5689505A (en) | 1996-01-16 | 1997-11-18 | Lucent Technologies Inc. | Buffering of multicast cells in switching networks |
US5862345A (en) | 1996-02-07 | 1999-01-19 | Nec Corporation | System for location multicasting and database management for mobile sessions in any computer subnetworks without using a home router of a home subnetwork |
US5754774A (en) | 1996-02-15 | 1998-05-19 | International Business Machine Corp. | Client/server communication system |
US5781549A (en) | 1996-02-23 | 1998-07-14 | Allied Telesyn International Corp. | Method and apparatus for switching data packets in a data network |
US5828843A (en) | 1996-03-21 | 1998-10-27 | Mpath Interactive, Inc. | Object-oriented method for matching clients together with servers according to attributes included in join request |
US6477577B1 (en) | 1996-04-05 | 2002-11-05 | Fujitsu Limited | Network connection system and connection substitute correspondence client |
US5862481A (en) | 1996-04-08 | 1999-01-19 | Northern Telecom Limited | Inter-technology roaming proxy |
US5937161A (en) | 1996-04-12 | 1999-08-10 | Usa.Net, Inc. | Electronic message forwarding system |
US5894478A (en) | 1996-07-24 | 1999-04-13 | Lucent Technologies Inc. | Protocol converter and router for multi-mode wireless data communications |
US6185625B1 (en) | 1996-12-20 | 2001-02-06 | Intel Corporation | Scaling proxy server sending to the client a graphical user interface for establishing object encoding preferences after receiving the client's request for the object |
US5949799A (en) | 1996-12-27 | 1999-09-07 | Cypress Semiconductor Corp. | Minimum-latency data mover with auto-segmentation and reassembly |
US6683870B1 (en) * | 1997-02-10 | 2004-01-27 | Mci Communications Corporation | Method and system for multicasting call notifications |
US6421733B1 (en) | 1997-03-25 | 2002-07-16 | Intel Corporation | System for dynamically transcoding data transmitted between computers |
US6311215B1 (en) | 1997-03-25 | 2001-10-30 | Intel Corporation | System for dynamic determination of client communications capabilities |
US6331983B1 (en) | 1997-05-06 | 2001-12-18 | Enterasys Networks, Inc. | Multicast switching |
US6473411B1 (en) | 1997-05-12 | 2002-10-29 | Kabushiki Kaisha Toshiba | Router device, datagram transfer method and communication system realizing handoff control for mobile terminals |
US6393014B1 (en) | 1997-06-03 | 2002-05-21 | At&T Wireless Services, Inc. | Method and system for providing data communication with a mobile station |
US6078690A (en) | 1997-06-20 | 2000-06-20 | Olympus Optical Co., Ltd. | Image data conversion device and method having function of inserting delimiter code into position in image data where a predetermined amount of data is reached |
US6374305B1 (en) | 1997-07-21 | 2002-04-16 | Oracle Corporation | Web applications interface system in a mobile-based client-server system |
US6167450A (en) | 1997-07-30 | 2000-12-26 | International Business Machines Corporation | Data communications management system and protocol replacement method for mobile communication environments |
US6067545A (en) | 1997-08-01 | 2000-05-23 | Hewlett-Packard Company | Resource rebalancing in networked computer systems |
US6512754B2 (en) | 1997-10-14 | 2003-01-28 | Lucent Technologies Inc. | Point-to-point protocol encapsulation in ethernet frame |
US6665718B1 (en) | 1997-10-14 | 2003-12-16 | Lucent Technologies Inc. | Mobility management system |
US6675208B1 (en) | 1997-10-14 | 2004-01-06 | Lucent Technologies Inc. | Registration scheme for network |
US6246684B1 (en) | 1997-12-24 | 2001-06-12 | Nortel Networks Limited | Method and apparatus for re-ordering data packets in a network environment |
US6192029B1 (en) | 1998-01-29 | 2001-02-20 | Motorola, Inc. | Method and apparatus for performing flow control in a wireless communications system |
US6233577B1 (en) | 1998-02-17 | 2001-05-15 | Phone.Com, Inc. | Centralized certificate management system for two-way interactive communication devices in data networks |
US6252884B1 (en) | 1998-03-20 | 2001-06-26 | Ncr Corporation | Dynamic configuration of wireless networks |
US6490266B1 (en) | 1998-03-31 | 2002-12-03 | Samsung Electronics, Co., Ltd. | Method for test call synchronization of code division multiple access cellular system |
US6507589B1 (en) * | 1998-04-30 | 2003-01-14 | Openwave Systems Inc. | Method and apparatus for routing between network gateways and service centers |
US6247048B1 (en) | 1998-04-30 | 2001-06-12 | Openwave Systems Inc | Method and apparatus for transcoding character sets between internet hosts and thin client devices over data networks |
US6539422B1 (en) | 1998-05-04 | 2003-03-25 | Intermec Ip Corp. | Automatic data collection device having a network communications capability |
US6389465B1 (en) | 1998-05-08 | 2002-05-14 | Attachmate Corporation | Using a systems network architecture logical unit activation request unit as a dynamic configuration definition in a gateway |
US6397259B1 (en) | 1998-05-29 | 2002-05-28 | Palm, Inc. | Method, system and apparatus for packet minimized communications |
US6590588B2 (en) | 1998-05-29 | 2003-07-08 | Palm, Inc. | Wireless, radio-frequency communications using a handheld computer |
US6343318B1 (en) | 1998-05-29 | 2002-01-29 | Palm, Inc. | Method and apparatus for communicating information over low bandwidth communications networks |
US6445691B2 (en) | 1998-06-08 | 2002-09-03 | Koninklijke Philips Electronics N. V. | Wireless coupling of standardized networks and non-standardized nodes |
US6490617B1 (en) | 1998-06-09 | 2002-12-03 | Compaq Information Technologies Group, L.P. | Active self discovery of devices that participate in a network |
US6529722B1 (en) | 1998-06-19 | 2003-03-04 | Microdata | System and method for enhanced 9-1-1 address development, maintenance and call routing using road access zones |
US6078960A (en) | 1998-07-03 | 2000-06-20 | Acceleration Software International Corporation | Client-side load-balancing in client server network |
US6862622B2 (en) | 1998-07-10 | 2005-03-01 | Van Drebbel Mariner Llc | Transmission control protocol/internet protocol (TCP/IP) packet-centric wireless point to multi-point (PTMP) transmission system architecture |
US6590885B1 (en) | 1998-07-10 | 2003-07-08 | Malibu Networks, Inc. | IP-flow characterization in a wireless point to multi-point (PTMP) transmission system |
US6640248B1 (en) | 1998-07-10 | 2003-10-28 | Malibu Networks, Inc. | Application-aware, quality of service (QoS) sensitive, media access control (MAC) layer |
US6108314A (en) | 1998-08-31 | 2000-08-22 | Motorola, Inc. | Method, subscriber device, wireless router, and communication system efficiently utilizing the receive/transmit switching time |
US6160793A (en) | 1998-10-13 | 2000-12-12 | Nokia Telecommunications, Oy | ECN-based approach for congestion management in hybrid IP-ATM networks |
US6477543B1 (en) | 1998-10-23 | 2002-11-05 | International Business Machines Corporation | Method, apparatus and program storage device for a client and adaptive synchronization and transformation server |
US6691165B1 (en) | 1998-11-10 | 2004-02-10 | Rainfinity, Inc. | Distributed server cluster for controlling network traffic |
US6272129B1 (en) | 1999-01-19 | 2001-08-07 | 3Com Corporation | Dynamic allocation of wireless mobile nodes over an internet protocol (IP) network |
US6857013B2 (en) | 1999-01-29 | 2005-02-15 | Intermec Ip.Corp. | Remote anomaly diagnosis and reconfiguration of an automatic data collection device platform over a telecommunications network |
US6505248B1 (en) | 1999-03-24 | 2003-01-07 | Gte Data Services Incorporated | Method and system for monitoring and dynamically reporting a status of a remote server |
US6539019B1 (en) | 1999-05-24 | 2003-03-25 | 3Com Corporation | Methods and apparatus for automatically connecting a dynamic host configuration protocol (DHCP) client network device to a virtual local area network (VLAN) |
US6567857B1 (en) | 1999-07-29 | 2003-05-20 | Sun Microsystems, Inc. | Method and apparatus for dynamic proxy insertion in network traffic flow |
US6701374B2 (en) | 1999-07-29 | 2004-03-02 | Sun Microsystems, Inc. | Method and apparatus for dynamic proxy insertion in network traffic flow |
US6633910B1 (en) | 1999-09-16 | 2003-10-14 | Yodlee.Com, Inc. | Method and apparatus for enabling real time monitoring and notification of data updates for WEB-based data synchronization services |
US6578066B1 (en) | 1999-09-17 | 2003-06-10 | Alteon Websystems | Distributed load-balancing internet servers |
US6772195B1 (en) | 1999-10-29 | 2004-08-03 | Electronic Arts, Inc. | Chat clusters for a virtual world application |
US6529882B1 (en) | 1999-11-03 | 2003-03-04 | Electronics And Telecommunications Research Institute | Method for managing group membership in internet multicast applications |
US6510464B1 (en) | 1999-12-14 | 2003-01-21 | Verizon Corporate Services Group Inc. | Secure gateway having routing feature |
US6563919B1 (en) | 1999-12-17 | 2003-05-13 | Nortel Networks Limited | System and method for unifying the implementation and processing of mobile communications and a unified mobility manager for providing such communications |
US6826173B1 (en) * | 1999-12-30 | 2004-11-30 | At&T Corp. | Enhanced subscriber IP alerting |
US20010037358A1 (en) | 2000-01-31 | 2001-11-01 | Ken Clubb | System and method to publish information from servers to remote monitor devices |
US6665722B1 (en) | 2000-05-31 | 2003-12-16 | Bbnt Solutions Llc | Store-and-forward packet radio system and method |
US6452910B1 (en) | 2000-07-20 | 2002-09-17 | Cadence Design Systems, Inc. | Bridging apparatus for interconnecting a wireless PAN and a wireless LAN |
US6879582B1 (en) | 2000-09-29 | 2005-04-12 | Lucent Technologies Inc. | Media terminal adapter-cellular transceiver (MTA-CT) |
US6771742B2 (en) | 2001-11-05 | 2004-08-03 | Intrado Inc. | Geographic routing of emergency service call center emergency calls |
US6681262B1 (en) | 2002-05-06 | 2004-01-20 | Infinicon Systems | Network data flow optimization |
US20050213716A1 (en) | 2004-03-23 | 2005-09-29 | Yinjun Zhu | Solutions for voice over internet protocol (VoIP) 911 location services |
US20060072547A1 (en) | 2004-09-29 | 2006-04-06 | Lucent Technologies Inc. | Systems and methods for serving VolP emergency calls |
US7711094B1 (en) | 2005-11-16 | 2010-05-04 | Verizon Data Services Llc | E911 location server |
US20080063153A1 (en) | 2006-08-21 | 2008-03-13 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a voip system |
US20080101552A1 (en) | 2006-11-01 | 2008-05-01 | Khan Richard L | Systems and methods for location management and emergency support for a voice over internet protocol device |
US20080200143A1 (en) | 2007-02-20 | 2008-08-21 | Chaoxin Charles Qiu | Systems and methods for location management and emergency support for a voice over internet protocol device |
US20090003312A1 (en) | 2007-06-26 | 2009-01-01 | Leonardo Velazquez | Methods and apparatus to provide enhanced 911 (e911) services for nomadic users |
US20090103687A1 (en) | 2007-10-17 | 2009-04-23 | Vixxi Solutions, Inc. | Geographic referenced telephone switching |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150140933A1 (en) * | 2013-11-15 | 2015-05-21 | Gpshopper, Llc | Method and system for distributed management of remote transmitters interacting with mobile devices |
US11159919B2 (en) * | 2013-11-15 | 2021-10-26 | Synchrony Bank | Method and system for distributed management of remote transmitters interacting with mobile devices |
US20210129865A1 (en) * | 2019-11-04 | 2021-05-06 | Research & Business Foundation Sungkyunkwan University | Context-aware navigation protocol for safe driving |
US11753033B2 (en) * | 2019-11-04 | 2023-09-12 | Research & Business Foundation Sungkyunkwan University | Context-aware navigation protocol for safe driving |
US11974197B2 (en) | 2021-09-13 | 2024-04-30 | Synchrony Bank | Method and system for distributed management of remote transmitters interacting with mobile devices |
Also Published As
Publication number | Publication date |
---|---|
US20130212195A1 (en) | 2013-08-15 |
US20020104516A1 (en) | 2002-08-08 |
US6435164B1 (en) | 2002-08-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9521185B2 (en) | System and method for re-directing requests from browsers for communications over non-IP based networks | |
US9438700B2 (en) | System and method for servers to send alerts to connectionless devices | |
US9220010B2 (en) | System and method for developing applications in wireless and wireline environments | |
US7970898B2 (en) | System and method to publish information from servers to remote monitor devices | |
US7418498B2 (en) | System and method to publish information from servers to remote monitor devices | |
US7689696B2 (en) | System and method for re-directing requests from browsers for communications over non-IP based networks | |
US7693981B2 (en) | System and method to publish information from servers to remote monitor devices | |
US8370435B1 (en) | System and method for servers to send alerts to connectionless devices | |
US11223990B2 (en) | WiFi and cellular communication traversal | |
US9510277B2 (en) | Efficient transactional messaging between loosely coupled client and server over multiple intermittent networks with policy based routing | |
EP1494426B1 (en) | Secure network processing | |
US20110276636A1 (en) | Efficient transactional messaging between loosely coupled client and server over multiple intermittent networks with policy based routing | |
WO2001056251A9 (en) | Method and apparatus for sending and receiving client-server messages over multiple wireless and wireline networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TSYS ACQUISITION CORP., MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AETHER SYSTEMS, INC.;REEL/FRAME:029576/0384 Effective date: 20040113 Owner name: AETHER SYSTEMS, INC., MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BONEFAS, RUDY G.;SOBCHAK, RICHARD K.;SIGNING DATES FROM 20010403 TO 20010404;REEL/FRAME:029576/0319 Owner name: TELECOMMUNICATION SYSTEMS CORPORATION OF MARYLAND, Free format text: CHANGE OF NAME;ASSIGNOR:TSYS ACQUISITION CORP.;REEL/FRAME:029576/0483 Effective date: 20050915 Owner name: TELECOMMUNICATION SYSTEMS, INC., MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TELECOMMUNICATION SYSTEMS CORPORATION OF MARYLAND;REEL/FRAME:029576/0488 Effective date: 20061004 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: CITIBANK, N.A., NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:COMTECH TELECOMMUNICATIONS CORP.;COMTECH EF DATA CORP.;COMTECH XICOM TECHNOLOGY, INC.;AND OTHERS;REEL/FRAME:048104/0080 Effective date: 20181031 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20200906 |