WO2001056307A2 - Détection/notification de conduite - Google Patents

Détection/notification de conduite Download PDF

Info

Publication number
WO2001056307A2
WO2001056307A2 PCT/US2001/002454 US0102454W WO0156307A2 WO 2001056307 A2 WO2001056307 A2 WO 2001056307A2 US 0102454 W US0102454 W US 0102454W WO 0156307 A2 WO0156307 A2 WO 0156307A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
communication unit
mobile communication
mobile
call
Prior art date
Application number
PCT/US2001/002454
Other languages
English (en)
Other versions
WO2001056307A3 (fr
Inventor
Oswaldo L. Do Nascimento, Jr.
Original Assignee
Transient Wireless Technology, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Transient Wireless Technology, Inc. filed Critical Transient Wireless Technology, Inc.
Priority to AU2001232966A priority Critical patent/AU2001232966A1/en
Publication of WO2001056307A2 publication Critical patent/WO2001056307A2/fr
Publication of WO2001056307A3 publication Critical patent/WO2001056307A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the invention relates to communication systems and in particular to mobile communication systems such as mobile telephones, personal data assistants, pagers and computers.
  • the invention provides a system for use with a mobile communication unit and a device for providing data associated with the mobile communication unit.
  • the system includes an apparatus configured to receive the data associated with the mobile communication unit from the device and to use the data to determine whether the mobile communication unit is likely to be traveling via a motor vehicle, the apparatus being further configured to provide apparatus output information indicative of whether the mobile communication unit is likely to be traveling in a motor vehicle.
  • the system also includes a control module communicatively coupled to the apparatus and configured to provide control signals in response to the apparatus output information to affect communication between the mobile communication unit and another communication unit.
  • Implementations of the invention may include one or more of the following features.
  • the apparatus is configured to determine a speed of the mobile communication unit from the data.
  • the apparatus is configured to determine the average speed of the mobile communication unit from the data.
  • the apparatus is configured to perform a comparison of the average speed of the mobile communication unit with a criterion to determine whether the mobile communication unit is likely to be traveling via a motor vehicle, the criterion being a threshold speed associated with the motor vehicle.
  • the threshold speed varies depending upon a property of the mobile communication unit.
  • the threshold speed depends on an occupation of a user associated with the mobile communication unit.
  • the control signals are for causing a user of the mobile communication unit to be prompted to indicate whether the user is a driver of the motor vehicle.
  • the control signals are for managing the communication, including disconnecting a call if applicable, between the mobile communication unit and the another communication unit in the absence of the control module receiving an indication that the user is not the driver.
  • the communication is, at least initially, from the another communication unit to the mobile communication unit, and wherein the control signals are for routing the communication to a destination other than the mobile communication unit in the absence of the control module receiving an indication that the user is not the driver.
  • the destination is a voicemail box associated with the mobile communication unit.
  • the control signals are for causing a message to be played by at least one of the mobile communication unit and the another communication unit in the absence of the control module receiving an indication that the user is not the driver.
  • Implementations of the invention may also include one or more of the following features.
  • the control signals are for causing at least one of the mobile communication unit and the another communication unit to prompt at least one of a first user of the mobile communication unit and a second user of the another communication unit to indicate whether the communication is an emergency.
  • the control signals are for causing the mobile communication unit to prompt the first user to indicate whether the first user is driving, and to enable the communication regardless of whether the first user indicates that the first user is driving if at least one of the first and second users indicates that the communication is an emergency.
  • the control module is configured to communicate in accordance with Bluetooth protocol.
  • the control module is configured to communicate with mobile communication units disposed near the control module in accordance with the Bluetooth protocol to determine which of multiple possible communication services to provide to each mobile communication unit.
  • the control module is configured to transmit the control signals wirelessly.
  • the apparatus is configured to receive indicia of a speed of the motor vehicle from a speedometer of the motor vehicle.
  • the control module is configured to determine which services to provide based upon service indicia received from each of the mobile communication units.
  • the control module is configured to store indicia of which services to provide to a particular mobile communication unit and to identify the particular mobile communication unit based upon communication with the particular mobile communication unit in accordance with the Bluetooth protocol.
  • Implementations of the invention may also include one or more of the following features.
  • the control signals are for causing at least one of the mobile communication unit and the another communication unit to play a message.
  • the speed module is configured to receive GPS signals and to determine from the GPS signals whether the mobile communication unit is likely to be traveling via a motor vehicle.
  • the apparatus output information is also indicative of a location of the mobile communication unit and the control signals are based on whether the mobile communication unit is likely to be traveling via a motor vehicle and on the location of the mobile communication unit.
  • the control module is configured to cause a user of the mobile communication unit to be prompted to indicate how the control module should affect the communication.
  • the invention provides a system for use with a mobile communication unit, the system including means for determining a speed of the mobile communication unit, and means for providing control signals to affect communication between the mobile communication unit and another communication unit based upon the speed of the mobile communication unit.
  • Implementations of the invention may include one or more of the following features.
  • the means for determining the speed includes means for determining the average speed and the control signals are for affecting the communication based upon the average speed of the mobile communication unit.
  • the control signals are for causing a user of the mobile communication unit to indicate whether the user is a driver.
  • the control signals are for managing the communication, including disconnecting a call if applicable, between the mobile communication unit and another communication unit in the absence of the means for providing receiving an indication that the user is not the driver.
  • the communication is, at least initially, from the another communication unit to the mobile communication unit, and wherein the control signals are for transferring the communication to a destination other than the mobile communication unit in the absence of the means for providing receiving an indication that the user is not the driver.
  • the control signals are for causing at least one of the mobile communication unit and the another communication unit to prompt at least one of a first user of the mobile communication unit and a second user of the another communication unit to indicate whether the communication is an emergency, and wherein the control signals enable the communication regardless of whether the first user indicates that the first user is driving if at least one of the users indicates that the communication is an emergency.
  • the system further includes means for prompting a user of the mobile communication unit to indicate how the means for providing the control signals should affect the communication.
  • the invention provides a method including determining whether a mobile telecommunication unit is likely to be traveling via a motor vehicle, detecting that communication is in progress or attempting to be initiated between the mobile telecommunication unit and another telecommunication unit, and at least temporarily inhibiting communication based upon the determining whether the mobile telecommunication unit is likely to be traveling via the motor vehicle.
  • Implementations of the invention may include one or more of the following features.
  • the determining includes determining an average speed of the mobile telecommunication unit.
  • the determining the average speed includes receiving and processing GPS signals from the mobile telecommunication unit.
  • the detern ⁇ iing an average speed includes receiving and processing signals indicative of locations of the mobile telecommunication unit over time.
  • the determining an average speed includes receiving and processing signals from a speedometer of the motor vehicle.
  • Implementations of the invention may also include one or more of the following features.
  • the method further includes prompting, while the communication is at least temporarily inhibited, a user of the mobile telecommunication unit to indicate whether the user is a driver of the motor vehicle.
  • the inhibiting of the communication ends in response to the user indicating that the user is not the driver.
  • the inhibiting includes connecting, for communication, the another telecommunication unit to a device other than the mobile telecommunication unit in the absence of the user indicating that the user is not the driver.
  • the user of the mobile telecommunication unit is a first user and wherein the inhibiting of the communication ends in response to at least one of the first user and a second user, of the another telecommunication unit, indicating that the communication is an emergency, regardless of whether the first user indicates that the first user is driving.
  • Implementations of the invention may also include one or more of the following features.
  • the determining whether the mobile telecommunication unit is likely to be traveling via a motor vehicle includes prompting a user of the mobile telecommunication unit to indicate how to inhibit the communication.
  • the inhibiting includes providing services related to the communication.
  • the services include prioritizing multiple communications.
  • Various embodiments of the invention may provide one or more of the following advantages.
  • Road safety can be improved.
  • the frequency and/or number of violations of laws prohibiting mobile phone use while driving can be reduced compared to the current frequency and/or number.
  • Mobile phone users can be notified of potential safety and legal concerns associated with driving while using a mobile phone. Useful and safe options to enabling or continuing calls to or from a current or prospective mobile phone user that is driving can be implemented.
  • Communication between persons can be assisted without enabling or continuing calls to or from a current or prospective mobile phone user that is driving. Communications such as calls can be routed or rerouted as desired, such as to promote safety and/or prevent illegal activity.
  • Mobile phone users can receive messages, be informed of emergencies, and be allowed to send prerecorded messages, even if the user is driving. Drivers can use mobile phones during emergencies. Security concerns of mobile communications users can be improved. Driving safety can be improved and illegal activity reduced. Additional revenue can be realized due to additional services provided to mobile phone users. Vehicular accidents and corresponding healthcare and insurance costs can be reduced. Mobile phone users can be alerted to traffic laws and possible violations thereof. Traffic management and control (e.g., vehicle routing depending on traffic conditions) can be improved.
  • Traffic management and control e.g., vehicle routing depending on traffic conditions
  • Vehicles and other assets can be tracked and managed.
  • Resource allocation in telephone operator networks can be improved or optimized, e.g., for handoff and other mobile-related communication processing depending on, for example, the number of mobile communication system users in an area.
  • Communication services can be provided such as blocking communications, enabling communications, prompting for responses as to whether a user is a driver or the communication is an emergency, disconnecting communication connections, playing messages, and routing communications, e.g., to voicemail boxes.
  • Safety of motor vehicle travel can be improved.
  • Telecommunication channel progress can be accommodated and channel access can be managed, controlled, and organized. Messages delivered to a mobile communication unit user can be managed by the user. Interference between devices or allocation of devices to a piconet can be reduced or eliminated.
  • FIG. 1 is a simplified partially-block diagram schematically showing interconnections of components of a system according to the invention.
  • FIG. 2 is a schematic diagram of a process of connecting a mobile-station-initiated call from a mobile station user that confirms that the user is not driving.
  • FIG. 3 is a schematic diagram of processing of a mobile-station-initiated call from a mobile station user that fails to confirm whether the user is driving.
  • FIG. 4 is a schematic diagram of processing of a mobile-station-initiated call from a mobile station user that confirms that the user is driving.
  • FIG. 5 is a schematic diagram of a process of connecting a mobile-station-terminated call to a mobile station user that confirms that the user is not driving.
  • FIG. 6 is a schematic diagram of processing of a mobile-station-terminated call to a mobile station user that fails to confirm whether the user is driving.
  • FIG. 7 is a schematic diagram of processing of a mobile-station-terminated call to a mobile station user that confirms that the user is driving.
  • FIG. 8 is a schematic diagram of a process of reconnecting a call in progress with a mobile station user that confirms that the user is not driving.
  • FIG. 9 is a schematic diagram of processing of a mobile-station call in progress where a mobile station user fails to confirm whether the user is driving.
  • FIG. 10 is a schematic diagram of processing of a mobile-station call in progress where a mobile station user confirms that the user is driving.
  • FIG. 11 is a schematic diagram of processing of a mobile-station-terminated call to a mobile station user that confirms that the user is driving where a party calling the mobile station user indicates that the call is an emergency.
  • FIG. 12 is a schematic diagram of a system for identifying the location of a mobile station and contacting the closest entity or entities to the mobile station.
  • FIG. 13 is a simplified partially-block diagram schematically showing interconnections of components of another system according to the invention.
  • FIG. 14 is a block diagram of a mobile station and a remote mobile module shown in FIG. 13.
  • FIG. 15 is a block diagram of a wireless vehicle communication system shown in FIG. 13.
  • FIG. 16 is a block diagram of a process of operation of the system shown in FIG. 13.
  • Embodiments of the invention provide techniques for determining that a mobile station, such as a mobile phone, is likely to be traveling in a car or other vehicle when a call is in progress or attempting to be made, and acting accordingly.
  • the invention provides a system that uses the estimated value of the speed of a Mobile Station (MS) to inquire if a user of the MS is a driver or not.
  • the speed of the MS may suggest that the MS is being used by a person that is driving, e.g., if the MS is moving excessively fast (e.g., above threshold level).
  • the system sends a message to the MS requesting information as to whether the MS is used by a driver or not. If a "not driving" message is sent by the MS, indicating that the user is not driving, then the system stores this information in a database. If a "not driving" message is not sent, the system can proceed accordingly such as by either disconnecting the call or giving instructions for both parties to a call about how to proceed, and storing call information.
  • the system can notify the user of possible undes ⁇ red/unlawful activity, route and/or reroute calls, provide messaging (including two-way messaging) to the user and another party to a current or prospective communication with the user, and provide announcements.
  • the MS can be a wireless device capable of mobile communication, especially two-way communication.
  • the MS could be a palmtop, laptop, or hand-held computer, a wideband data/voice integrated device such as an electronic organizer, a one-way or two-way pager, or a computer installed in a vehicle.
  • These devices can provide abilities and/or services such as telephone communications, one-way or two-way paging, and email and Internet connection at mobile locations such as in a car.
  • Such communication can be full duplex communication using, e.g., satellite links, or cellular and/or PCS infrastructure of the frequency spectrum.
  • the communication can use a variety of media such as radio waves and antennas, optical fibers or other optical transmission media, and satellites.
  • Other forms of mobile communication and transmission systems and/or media either known or developed in the future would be acceptable and within the scope of the invention.
  • the description refers principally to calls although other communications are possible.
  • a Speed Detection, Notification, and Messaging (SDNM) system 10 includes a Speed and Location Detection and Notification Module (SLDNM) 11, that includes a Speed and Location Detection System (SLDS) 30 and a Speed Notification and Message System (SNMS) 32, a Mobile Station (MS) 12, a base station 14, a serving Mobile Switching Center (MSC) 16, a Public Switched Telephone Network (PSTN) 34, and a phone 36.
  • SDNM Speed and Location Detection and Notification Module
  • MS Mobile Station
  • MS Mobile Station
  • base station 14 is hard-wire connected to the serving MSC 16.
  • the serving MSC 16 is connected to the SNMS 32 and the PSTN 34.
  • the SLDNM 11 includes a voice machine, SS7 servers, central control machines, and an Operation and Maintenance (O&M) machine.
  • O&M Operation and Maintenance
  • the voice machine supplies resources to interface with users of the MS 12, play prompts, and receive feedback via Dual-Tone Multi-Frequency (DTMF) tones and speech recognition.
  • the voice machine uses Intel®-based and Compact PCI (cPCI) bus platform with a cPCI 19U high enclosure with 8 6U sized slots, an HI 10 CT bus backplane, hot swappable fans, and front bays for a floppy drive and a CD-ROM drive.
  • cPCI Compact PCI
  • an Advantech MIC3032/8 or MIC-3021-8, made by Advantech, Inc. of Annapolis, MD may be used.
  • a CPU board with a Pentium® III 70 Mhz processor made by Intel® Corp.
  • the SS7 servers provide connectivity for the SLDNM 11. Two SS7 servers are used, each connected to a Signal Transfer Point (STP), and each connected to the other SS7 server.
  • the SS7 servers also use a cPCI bus and Intel®-based platform.
  • Each SS7 enclosure features a cPCI bust platform that is 19U high, 8 6U sized slots, an HI 10 CT bus backplane, hot swappable fans, front bays for a floppy drive and a CD-ROM drive, a -48V redundant power supply, and an alarm panel.
  • Advantech's MIC3032/8 or MIC-2031-8 may be used.
  • CPU boards with a Pentium® III 700 MHz processor and 256 Mbytes of RAM, such as Advantech's MIC3365 or MIC3376 may be used.
  • the SS7 machine may use a DataKinetics CPM8 with a rear teransition board such as CPR8RJ.
  • the interface board has T1/E1/V35 interfaces.
  • the SS7 protocols used are SS7 MTP, SS7 ISUP, SS7 SCCP, SS7 TCAP, and SS7 LNAP, and the operating system is Linux.
  • the central control machines supply location signaling, communication control, and database management.
  • a cluster of machines are provided to help ensure high availability, scalability, and affordability.
  • the central control includes a database server, a location server and a call/communication control server.
  • the database server stores information, e.g., to help identify users, of locations and speeds of users, and of chosen user options.
  • the location server receives information regarding MS location.
  • the call/communication control server controls the voice and SS7 machines and implements services based on, e.g., responses from users.
  • the central control can be implemented using a Sun Microsystems® Enterprise 220R server (made by Sun Microsystems® Inc. of Palo Alto, CA), with 2 450MHz processors, 2 Gbytes of RAM, and a redundant power supply.
  • the O&M machine provides resources for system operations and maintenance.
  • the O&M machine uses CORBA to interface with the SS7 machines, voice machine, and central control and database servers, and uses HTTP to interface with an operator terminal.
  • the operator terminal can employ a web browser for sending and receiving information regarding system and user status.
  • the O&M machine can be implemented with a Sun Microsystems® Enterprise 5 platform with a 450 MHz processor and 512 Mbytes of RAM using a Solaris® SPARC® operating system.
  • Portions of the system 10, and in particular of the SLDS 30 and the SNMS 32, are preferably implemented with software code that is stored on computer-readable media and that includes instructions that are readable by a computer for causing the computer to perform operations as described herein according to the instructions.
  • FIG. 1 is thus intended as illustrative and not limiting as to the physical location of the performance of functions described. Functions described as being performed by a particular block in FIG. 1 can be performed wholly or partially in other portions of the system 10 than as described.
  • the SLDS 30 includes a Speed Location and Detection Module (SLDM) 38 and a Serving and Interface Subsystem (SIS) 40.
  • the SLDM 38 is adapted to acquire information about the MS 12, including speed and location, and information about the date and time of day.
  • the SLDM 38 can acquire data regarding the average speed of the MS 12 to determine when the MS 12 is moving, according to its average speed, faster than a threshold.
  • the data regarding the average speed can be, e.g., position and location information over time, speed over time, or average speed itself. If other than average speed itself, the SLDM 38 calculates the average speed.
  • An average speed, over a predetermined time period, is used to guard against erroneous inferences that the user may be driving, for example if the MS 12 is dropped and briefly exceeds the threshold speed.
  • a Global Positioning System may be included in the SLDM 38 to ascertain the location and/or speed of the MS 12.
  • GPS Global Positioning System
  • information from, e.g., local cellular phone processing stations can relay information about a particular MS 12.
  • the SLDM 38 includes appropriate memory that stores software code, and a processor for executing the stored code. By executing the code, the SLDM 38 can process the received signals to determine a speed and location of the MS 12.
  • the MS 12 could include a GPS system and the SLDM 38 could determine the average speed of the MS 12 from signals from the GPS in the MS 12.
  • the information obtained by or calculated by the SLDM 38 is processed by the SIS 40.
  • the SIS 40 includes an open-standard data communication interface that can provide information (e.g., information for performing functions described herein) to other portions of the system 10, including to service providers.
  • service providers can be the providers of the communication abilities of the MS 12 (e.g., a cellular phone service provider), or independent of such communication service providers.
  • the independent service providers can work with the communication service providers.
  • Services provided can include fleet management, traffic control, emergency services (e.g., vehicle and/or user location to direct emergency vehicles to the user's location), and police notification (e.g., for traffic violation identification, and/or user tracking such as if the user is wanted by the police).
  • the SNMS 32 includes a Speed Notification Subsystem (SNS) 42 and a Database
  • the SNMS 32 is adapted to use the speed of the MS 12 and the call status of the MS 12 to provide services to a user of the MS 12.
  • the DS 44 is adapted to store information regarding MS 12, e.g., location and speed, date and time of day, and responses to inquiries provided by the user of the MS 12.
  • the SNS 42 is connected to the SLDS 30 and is adapted to use information from the
  • the SNS 42 can periodically receive information from the SLDS 30 regarding, e.g., the location, speed, and identity of an MS 12 within (or possibly approaching) a territory associated with the SLDS 30.
  • the SNS 42 can also access information from, and store information in, the DS 44.
  • the SNS 42 can determine whether the MS 12 is likely to be traveling in a car or other vehicle. This can be accomplished by, e.g., comparing the speed of the MS 12 with a predetermined rate.
  • the rate need not be associated with a particular type of motor vehicle, and can be an upper threshold associated with non-motor- vehicle movement such as walking or riding in an elevator.
  • the SNS 42 can also determine whether a call is in progress or attempting to be made using information received from the MSC 16 by the SLDNM 11 regarding calls or other communications.
  • the SNS 42 can, in accordance with the speed determination and call status of the MS 12, send notices and messages to, and provide services to, the user and to the other party to the call. These notices can inform the user and/or the other party (actual or prospective) that the user is likely to be driving (e.g., moving above a threshold speed), identify the user's location (e.g., area of the city or highway), and inquire whether the user is driving.
  • the user can be advised, e.g., about safety, legal, or other concerns regarding using the MS 12 while driving.
  • the notices can also inform the other party to the call of any actions to be taken affecting the call and any services available to the party, such as leaving a message for the user.
  • the SNS 42 can receive the user's response to the inquiry, such as in the form of speech or a dual-tone multi-frequency (DTMF) signal produced by the user pressing a button on the MS 12.
  • the SNS 42 can perform appropriate functions. Examples of these functions are connecting or reconnecting a call, stopping and/or disconnecting a call, forwarding a call, recording and/or delivering messages, and recording in the DS 44 information regarding the call and/or speed status of the MS 12. If the user responds that the user is not driving (a "not driving" response) or that the call is an emergency, then the SNS 42 can store this information in DS 44.
  • the SNS 42 can initiate appropriate action.
  • Appropriate action can include transferring a party calling the mobile phone user to a message service of the mobile phone user, and/or disconnecting the call, and/or connecting/reconnecting the call, and/or informing each party to the call of action to be taken, and/or giving each party instructions as to how to proceed, and/or storing call information.
  • the SNS 42 includes a Data Interface Module (DIM) 46, an Event Generator Module (EGM) 48, a Call Control Module (CCM) 50, a Prompt Generator Module (PGM) 52, a Driving Status Acknowledgement Detection Module (DSADM) 54 and a Signaling Module (SM) 56.
  • DIM Data Interface Module
  • ECM Event Generator Module
  • CCM Call Control Module
  • PGM Prompt Generator Module
  • DSADM Driving Status Acknowledgement Detection Module
  • SM Signaling Module
  • the DIM 46 is connected to, and adapted to interface with, the SLDS 30 in accordance with a communication protocol.
  • the DIM 46 is adapted to receive data to be used by the EGM 48 and convey these data to the EGM 48, and the DS 44 for storage. Also, the DIM 46 is adapted to remove data, from the DS 44, associated with an MS 12 that has not transmitted data 1 for a predetermined amount of time.
  • the EGM 48 includes a state machine (not shown) associated with each MS 12 and under the control of the SLDS 30.
  • a data input (not shown) is connected to the DIM 46 for receiving data from the DIM 46.
  • the EGM can produce indications of at least three events: (1) the MS 12 is moving faster than the threshold and initiating a call; (2) the MS 12 is moving faster than the threshold and receiving a call; and (3) the MS 12 is currently in a call and begins moving faster than the threshold.
  • the CCM 50 is connected to the EGM 48 and adapted to receive indications from the
  • the CCM 50 is adapted to manage interactions between the MS 12 and another party, if any, to control a call to/from the MS 12. Interactions controlled by the CCM 50 include sending messages to the MS 12, receiving answers from the MS 12, and connecting calls to/from the MS 12. How the CCM 50 controls the interactions depends, e.g., on the call status and the answers provided by the MS 12. Also, in accordance with the answers provided by the MS 12, the CCM 50 updates the DS 44 with the identity and location of the MS 12, and the time.
  • the PGM 52 is adapted to interface with the MS 12 and the other party, if any, current or prospective, to a call to or from the MS 12.
  • the PGM 52 is adapted to provide predetermined prompt messages to the MS 12 and the other party, under the control of the CCM 50.
  • DTMF and/or voice commands are detectable by the DSADM 54.
  • the DSADM 54 is connected to the MSC 16 such that DTMF and/or voice commands from the MS 12 can be received, detected, and interpreted by the DSADM 54.
  • the DSADM 54 can be adapted to interpret and/or recognize certain predefined speaker-independent voice commands. Indications of interpreted or otherwise detected commands can be sent by the DSADM 54 to the CCM 50, to which the DSADM 54 is connected.
  • the SM 56 is connected to the CCM 50 and the MSC 16 and is adapted to exchange data with the MSC 16 in order to implement call sequences according to instructions from the CCM 50.
  • the SM 56 can request the MSC 16, e.g., to transfer incoming/outgoing calls to/from the MS 12 to the SLDNM 11.
  • the DS 44 is a database for storing information that enables access to and updating of the call status and acknowledgement data of each moving MS 12 in an area associated with the SLDS 30. Data are preferably stored for only each MS 12 whose speed exceeds the threshold. At least two types of data, real time data and acknowledgement data, are stored in the DS 44. Real-time data are updated frequently, and possibly continuously, as a result of services provided by the SNS 42. Acknowledgement data are maintained in the DS 44 for a predetermined amount of time and can be downloaded onto back-up devices for future access and reference.
  • the SNMS 32 can be activated during four distinct states of the MS 18. These four states are: (1) call setup; (2) MS 12 starts moving above the threshold level while there is a call in progress; (3) the MS 12 initiates an emergency call (911); and (4) the MS 12 receives an emergency call.
  • Call setup includes MS-initiated calls (i.e., the MS 12 attempts to make an outgoing call) and MS-terminated calls (i.e., a party attempts to call the MS 12).
  • IS-41 signaling is used to obtain routing information and call treatment for mobile-originated calls.
  • IS-41 is used to obtain MS location, status and routing information.
  • calls are established from the MS 12 (the calling party) to a telecommunication termination point (the called party).
  • the called party can be an entity other than a person, e.g., a voicemail or paging system.
  • the MS 12 sends an outgoing call to the base station 14.
  • the MS 12 is authenticated for transmission by the base station 14, which sets up a circuit connection with the MSC 16.
  • a query is made by the MSC 16 to a Visitor Location Register (VLR) 22, for the service qualification status of the MS 12.
  • VLR 22 sends return information to the MSC 16. If the MSC 16 approves the return information, then the calling process proceeds.
  • the MSC 16 sends an outgoing call notification to the SLDNM 11.
  • the SLDNM 11 sends a transfer-call request to the MSC 16, and the MSC 16 transfers the call to the SLDNM 11.
  • the SLDM 38 determines the speed of the MS 12 and sends this information to the SNS 42. If the SNS 42 determines that the MS 12 is moving at an excessive speed, and given the knowledge that the MS 12 is attempting to initiate a call, then the SNS 42 notifies the user of the MS 12 of the excess speed.
  • This announcement requests confirmation as to whether the user of the MS is driving and can be, e.g., "Your mobile telephone system has identified that you are using your mobile phone and moving at the same time. If you are not the driver, please press *. If you are the driver please press #.”
  • the MS 12 sends the user's response to the announcement to the SNS 42, in particular to the DSADM 54 that interprets the response.
  • the SNS 42 takes appropriate action.
  • the SNS 42 is shown to include a Speed Notification Module (SNM) 43.
  • SNM 43 represents the portions of the SNS 42 other than the DSADM 54.
  • the DSADM 54 sends a message to the user confirming that the user is not the driver.
  • An example message is, "We are confirming that you have informed us that you are not the driver. We are storing this information on our database. We are now connecting your call. Thank you for your cooperation.”
  • the SNS 42 establishes the call to the called party.
  • the DSADM 54 sends the user's mobile identification number (MLN) and electronic identification number (EIN) and call information (date, time, and not-driving status of the user) received from the SLDS 30 to the DS 44.
  • MSN mobile identification number
  • EIN electronic identification number
  • the SNS 42 sends a voice message to this effect to the MS 12.
  • the message states that the SNS 42 failed to confirm that the user is not a driver and that the call will not be established if the user does not confirm non-driving status of the user.
  • An exemplary message is "You have failed to inform us that you are not the driver. Your call will be disconnected. Please call when you are not driving or press * now to indicate that you are not the driver.” If the user does not press *, then the SNS 42 sends another message to the MS 12 regarding the failure and that the call will not be connected.
  • An exemplary message is, "You have failed to inform us that you are not the driver. The call will not be completed at this time.” In response, the SLDNM 11 will not establish the requested call.
  • the SNS 42 sends a voice message to the MS 12 confirming that the user has acknowledged being the driver and that the call will not be completed.
  • An exemplary message is, "You have confirmed that you are driving now. Your call will not be connected. We can forward a message for your called party provided that you pre-recorded your messages. To send pre-recorded messages press # and the number of your pre-recorded message that you would like to forward. Otherwise, please call when you are not driving.” If sending a pre-recorded message is not selected, then the SLDNM 11 does not proceed with establishing the call.
  • the message sent by the MS 12 is pre-stored in memory (e.g., by the user or possibly by the manufacturer of the MS 12) and can be of a predetermined length, e.g., 10 seconds, according to the amount of memory allocated for the messages. If sending a pre-recorded message is selected, then the SLDNM 11 establishes a call to the called party, e.g., the phone 36. The SLDNM 11 retrieves the user's selected messages from memory and transmits the message toward the called party. After delivery of the message, the SLDNM 11 terminates the call.
  • memory e.g., by the user or possibly by the manufacturer of the MS 12
  • a predetermined length e.g. 10 seconds
  • a call is made to a user's MS 12 from, e.g., the telephone 36.
  • the user of the MS 12 is the called party.
  • no location information or special signaling or routing is required.
  • the delivery of mobile- terminated calls to a roaming user is a call feature known as "call delivery" and it is addressed in the IS-41 standard.
  • a query is made by the serving MSC 16 to the VLR 22 for registration and status features and the VLR 22 provides return information.
  • the MSC 16 sends an incoming-call notification to the SLDNM 11.
  • the SLDNM 11 sends a request for call transfer to the MSC 16.
  • the MSC 16 transfers the call to the SLDNM 11.
  • the SLDNM 11 establishes a call to the called party, e.g., the MS 12.
  • the SLDS 30 determines whether the speed of the MS 12 is excessive, and the SNS 42 determines the call status. If the SLDS 30 determines that the MS 12 is moving at an excessive speed, then the
  • SNS 42 sends an announcement to the MS 12 regarding excessive speed. This announcement requests confirmation as to whether the user of the MS is driving and can be, e.g., "You are receiving a call from [phone ID]. However, your mobile telephone system has identified that you are moving by means of a vehicle. If you are not the driver, then please press *. If you are the driver and would like to forward a message to the calling party please press # and another digit for your pre-recorded messages.” The SNS 42 also sends a voice message to the calling party warning to stay connected. This message can be, e.g., "The other party is talking and moving at the same time. This could be against [e.g., the law; our policy].
  • the SNS 42 sends a message to the user confirming that the user is not the driver.
  • An example message is, "We are confirming that you have informed us that you are not the driver. We are storing this information on our database. We are now connecting your call. Thank you for your cooperation.”
  • the SLDNM 11 establishes the call between the 'calling and called parties, e.g., the phone 36 and the MS 12.
  • the DSADM 54 sends the user's mobile identification number (MIN) and electronic identification number (ELN) and call information (date, time, and not-driving status of the user) received from the MSC 16 to the DS 44.
  • MIN mobile identification number
  • EPN electronic identification number
  • the SNS 42 sends a voice message to this effect to the MS 12 and to the calling party.
  • the message to the MS 12 states that the SNS 42 failed to confirm that the user is not a driver and that the call will not be established.
  • An exemplary message is "You have failed to inform us that you are not the driver. The call will not be completed at this time.”
  • the SNS informs the calling party that the call will not be connected.
  • the SNS 42 can send the following to the calling party, "The party you have called has failed to indicate whether the party is currently driving, and thus it is assumed that the called party is driving.
  • the call will not be established.”
  • the call is dropped by the SLDNM 11.
  • the SNS 42 sends a voice message to the MS 12 confirming that the user has acknowledged being the driver and that the call will not be completed.
  • An exemplary message is, "You have confirmed that you are currently driving.
  • the call will not be established at this time. If you would like to forward a message to the calling party, please press # and the number of your pre-recorded message that you would like to forward.
  • the SNS 42 informs the calling party that the call will not be connected, as discussed below, retrieves the message indicated by the called MS 12 from memory, and forwards this message to the calling party.
  • the SLDNM 11 transfers the call to the phone number preselected by the user.
  • the SLDNM 11 looks up the phone number in memory.
  • Several phone numbers may be stored in memory corresponding to, e.g., the user's home, work, pager, voicemail, or a message center with a pool of attendants that can record a message and send it to the user, for example through the MS 12 at a later time.
  • Which phone number to use can be determined, e.g., according to the time of day and day of the week.
  • the SNS 42 sends a message to the calling party that the called party is driving and that the call is being forwarded.
  • This message can be, e.g., "The party you called is currently driving. As it is against [e.g., the law; our policy] to drive while using a mobile phone, your call cannot be completed now. Your call will be forwarded to a destination selected by the party that you called.” Some MS's 12 can accept a recorded message from the calling party. If the called
  • the MS 12 can accept messages, then the SNS 42 sends a voice message to the calling party informing the calling party that the called party is driving, and gives the calling party a chance to record a voice message to the called MS 12.
  • the message sent to the calling party can be, e.g., "The party you have called is currently driving. As it is against [e.g., the law; our policy] to use a mobile phone will driving, the call will not be established at this time. Please press # to leave a brief message, or try your call later." If the calling party chooses to leave a message, then the SLDNM 11 establishes a call to a voicemail (VM) system 26.
  • VM voicemail
  • the system 10 initiates a call to forward and deliver all messages. No message waiting indication is presented to the user at the MS 12 while the MS 12 appears to be moving in an undesired way, such as moving faster than the threshold.
  • the SNS 42 sends a voice message to the calling party informing the calling party that called party is driving, and that the call will not be completed.
  • the message sent to the calling party may be, "The party you called is currently driving. As it is against [e.g., the law; our policy] to drive while using a mobile phone, your call cannot be completed now.”
  • the SLDNM 11 drops the call. This is preferably performed after the called party chooses whether to forward a message, and if so selects which message, and preferably after the calling party leaves a message, if any.
  • both parties are connected and the call is under the control of the SLDNM 11 when it is detected that the MS 12 starts moving in a way that indicates that the MS 12 may be being used by a person that is driving.
  • the MS 12 may be moving excessively fast, e.g., above a threshold level.
  • the SNS 42 determines whether a party to a call in progress may be driving.
  • the SLDS 30 determines whether the speed of the MS 12 is excessive.
  • the SNS 42 receives an indication from the SLDS 30 that the speed of the MS 12 is excessive, and determines that the call status of the MS 12 is active, then the SNS 42 interrupts the call.
  • the SNS 42 sends announcements to both parties regarding the excessive speed of the
  • An A-side announcement to the MS 12 requests confirmation as to whether the user of the MS 12 is driving and can be, e.g., "Your mobile telephone system has identified that you are using your mobile phone and moving at the same time. If you are not the driver, please press *. If you are the driver please press #. If this is an emergency, then please press #* and your call will be reconnected and a record of this call will be kept on our database.” If the A-side party indicates that the call is an emergency, then the call is processed as discussed below for an emergency call.
  • the B-side announcement requests the B-side party to stay connected. This message can be, e.g., "The party with whom you are talking is talking and moving at the same time.
  • the SNS 42 sends the user's mobile identification number (MIN) and electronic identification number (EIN) and call information (date and time) received from the MSC 16 to the DS 44.
  • MIN mobile identification number
  • EIN electronic identification number
  • call information date and time
  • the SNS 42 sends a voice message to this effect to the MS 12 and to the B-side party.
  • the message to the MS 12 states that the SNS 42 failed to confirm that the user is not a driver and that the call will be disconnected.
  • An exemplary message is "You have failed to inform us that you are not the driver. The call will be disconnected at this time.”
  • the SNS informs the B-side party that the call will be disconnected.
  • the SNS 42 can send the following to the B-side party, "The party with whom you were talking has failed to indicate whether the party is currently driving, and thus it is assumed that the called party is driving. As it is against [e.g., the law; our policy] to use a mobile phone will driving, the call will be disconnected.”
  • the SLDNM 11 disconnects the call.
  • the SNS 42 sends a voice message to the MS 12 confirming that the user has acknowledged being the driver and that the call will be terminated.
  • An exemplary message is, "You have confirmed that you are currently driving. As it is against [e.g., the law; our policy] to use a mobile phone while driving, the call will be disconnected at this time. If you would like to forward a message to the other party, please press # and the number of your pre-recorded message that you would like to forward.
  • the SNS 42 informs the B-side party that the call will be disconnected, as discussed below, and the SNS 42 retrieves the message indicated by the A-side party from memory and forwards this message. If the called party selected to transfer the call to a preselected forwarding destination, then the SLDNM 11 transfers the call to the phone number preselected by the user. The SLDNM 11 looks up the phone number in memory.
  • phone numbers may be stored in memory corresponding to, e.g., the user's home, work, pager, voicemail, or a message center with a pool of attendants that can record a message and send it to the user, for example through the MS 12 at a later time.
  • Which phone number to use can be determined, e.g., according to the time of day and day of the week.
  • the SNS 42 sends a message to the B-side party that the A-side party is driving and that the call is being forwarded. This message can be, e.g., "The party with whom you were talking is currently driving. As it is against [e.g., the law; our policy] to drive while using a mobile phone, your call will be forwarded to a destination selected by the party with whom you were talking.”
  • the SNS 42 sends a voice message to the B-side party informing the B-side party that the A-side party is driving, and gives the B-side party a chance to record a voice message to the A-side party.
  • the message sent to the B-side party can be, e.g., "The party with whom you were talking is currently driving. As it is against [e.g., the law; our policy] to use a mobile phone will driving, the call will be disconnected at this time. Please press # to leave a brief message, or try your call later." If the B-side party chooses to leave a message, then the SLDNM 11 will transfer the call to the VM system 26.
  • the system 10 In response to the speed of the MS 12 being reduced below the threshold for more than a predetermined number of minutes (or otherwise appears not to be moving in an undesired way), the system 10 initiates a call to forward and deliver all messages. No message waiting indication is presented to the user at the MS 12 while the MS 12 appears to be moving in an undesired way, such as moving faster than the threshold. If the MS 12 of the A-side party does not accept messages, then the SNS 42 sends a voice message to the B-side party informing the B-side party that the A-side party is driving and that the call will be disconnected. For example, the message sent to the calling party may be, "The party you called is currently driving.
  • the SLDNM 11 drops the call. This is preferably performed after the A-side party chooses whether to forward a message, and if so selects which message, and preferably after the B-side party leaves a message, if any.
  • the SNS 42 sends appropriate messages to the MS user that is driving. For example, if the MS user that is driving indicates that a current call being initiated or in progress is an emergency, then the SNS 42 can send, "You have indicated that this is an emergency call. Please stop driving as soon as practical at a safe place.
  • All emergency calls are registered for safety and security purposes." Also, for example, if the party other than the MS user that is driving (although the other party could also be an MS user) indicates that a current call being initiated or in progress is an emergency, the SNS 42 can send, "The other party has indicated that this call is an emergency. Please stop driving as soon as practical at a safe place. All emergency calls are registered for safety and security purposes.” As shown in FIG. 11, the MS 12 receives a call, the MS user confirms that the MS user is driving, and the other party indicates that the call is an emergency. The SLDNM 11 will connect/reconnect the call to the MS 12 as the case may be. The SNS 42 sends the user's mobile identification number (MIN) and electronic identification number (EIN) and call information (date and time) received from the MSC 16, and an indication that the call is an emergency call, to the DS 44.
  • MIN mobile identification number
  • EIN electronic identification number
  • the ability to leave a message can be added to the situations discussed above in which this ability is not specifically referred to, and can be removed from the situations in which this ability is referred to.
  • the speed of the MS 12 can be registered (e.g., stored in the DS 44). If the speed of the MS 12 is consistently above a predetermined speed (e.g., a legal limit), then the speed can be registered and the user notified.
  • the calling party may be given the option to leave a message if the called party fails to respond to the inquiry as to whether the called party is driving.
  • Communication from the MS 12 can also be routed through a PSTN.
  • the cost of a call can be altered depending on the call status and the user's response, or lack thereof, to the driving status inquiry. The user can be given the option to designate an incoming call as an emergency call.
  • a service could be provided for law enforcement organizations, e.g., identifying the user's location, identity, and speed. This could produce millions of dollars in additional traffic violation revenue, reduce the usefulness of radar detectors for drivers, and increase safety due at least in part to a reduction in the speed at which some drivers drive.
  • This service could be accomplished, e.g., by interfacing with a positioning system (for identification of the geographical position by means of the cell-phone or, e.g., a global positioning system (GPS)). Also, the user could be notified of excessive speed to help reduce the user's risk of receiving a speeding ticket or other traffic violation citation.
  • a positioning system for identification of the geographical position by means of the cell-phone or, e.g., a global positioning system (GPS)
  • GPS global positioning system
  • the user could be notified of excessive speed to help reduce the user's risk of receiving a speeding ticket or other traffic violation citation.
  • the threshold used to determine that a user of an MS may be driving may vary between persons. For example, if the user drives heavy machinery such as construction equipment, then the threshold speed may be reduced for that user. Also, while components of the system 10 have been described as software that includes computer-readable instructions for causing a computer to perform certain functions, these functions can be implemented using software, hardware, hardwiring, firmware, or combinations of any of these and can be located in the system 10 in places other than those shown and described.
  • the SNS 42 could query a user of the MS 12 that is driving as to when the user will not be driving.
  • the user's response can be provided to the other party to the call as part of a message, or as an independent message, sent to the other party so that the call can be attempted again after the time indicated by the user of the MS 12.
  • Various options are possible for how the user responds to the driving status inquiry. For example, the user may be required to depress two keys on a mobile phone for a period of time, e.g., three seconds, in order to indicate that the user is not driving.
  • an inactive MS that is not in use, and not trying to be used, to transmit or receive voice communications or other data by a user, can be monitored and its motion status (e.g., likely to be travelling in a motor vehicle) determined. This can be used, e.g., for an MS that is moving above a predetermined speed to then register the MS's status and notify the user and/or to identify the user's location, identity, and speed, e.g., to law enforcement personnel.
  • a GPS may be used to help determine location, identity, and/or speed of an MS. A portion of the GPS could thus reside in the MS.
  • Some MSs include GPS functionality due to mandate E-911 by the Federal Communications Commission.
  • the MS can store messages as discussed above for interaction with the user and can act upon replies by the user independently of other devices (e.g., shown in FIG. 1). This can be true even if the MS does not include GPS functionality.
  • the location of the MS can be ascertained by the SLDS 30 using a GPS, or using other techniques such as the local cellular phone processing stations. Using the location of the MS, calls to, e.g., local police, fire stations, paramedics, and/or hospitals can be made by the SNMS 32, e.g., the SLDS 30 and the MSC 16.
  • the user may be connected to one or more of the persons/entities such as the police and/or a hospital or a 911 attendant (e.g., at a console of a local, preferably the nearest, police station) through, e.g., the BS 14, the MSC 16, the PSTN 34, and the phone 36.
  • the SLDS 30 communicates with the SNMS 32 and the MSC 16 through interface buses.
  • the SNMS 32 and the MSC 16 transmit signaling information and notification and messaging information between each other.
  • the SLDS 30 thus receives information regarding MS status and location.
  • the SLDS 30 uses the information received to determine the closest MSs, here MS 12a and MS 12b to an MS 12c that is making an emergency call.
  • the MSs 12a and/or 12b can be operatively connected to the MS 12c for communication or otherwise alerted to take appropriate action such as going to the location of the MS 12c that can be provided to the MSs 12a and 12b by the SLDS 30.
  • a system 100 includes the BS 14, the MSC 16, a voice/data network 102 (e.g., the PSTN 34), the SLDNM 11, a Wireless Vehicle Communication System (WVCS) 104, and a Wideband Wireless Mobile Station 106.
  • the WVCS 104 includes a Vehicle Control Module (VCM) 108 and the MS 106 is housed together with a Remote Mobile Module (RMM) 110.
  • VCM Vehicle Control Module
  • RMM Remote Mobile Module
  • the MS 106 and the WVCS 104 are configured to communicate with the BS 14, e.g., using cellular communication.
  • the MS 106 and the WVCS 104 can thus communicate with the SLDNM 11 to provide the services described above to communications with the MS 106.
  • the VCM 108 is configured to communicate with the MS 106 through the RMM 110 to configure the MS 106 as to which services the MS 106 will receive and how those services will be provided.
  • the VCM 108 and the RMM 110 are configured to communicate wirelessly with each other, and other devices, according to the BluetoothTM protocol.
  • the Bluetooth protocol is based on an open specification for short-range wireless voice and data communication. Version 1.0 of Bluetooth provides for a bandwidth limit of 1.0 MHz per channel, with over 79 channels in many countries, and uses a Frequency
  • the master device defines the frequency hopping pattern and the frequency phase for the communication.
  • a master can communicate concurrently with up to 7 active slaves and up to 255 parked slaves. All slaves communicating with a master hop together in unison with the master.
  • the slaves and the master form a piconet, e.g., the piconet 112 including the VCM 108 and the RMM 110.
  • the VCM 108 initially acts as the master and any MS equipped with RMM will initially act as a slave to the VCM 108.
  • the Bluetooth protocol includes a protocol stack. This stack provides for devices to locate, connect to, and exchange voice and data with other devices. The stack also provides for devices to execute interoperable applications (i.e., applications that are executable on either device) and interactive applications with each other.
  • the VCM 108 and the RMM 110 can communicate without action by a user of either the MS 106 or the WVCS 104, and without indication to a user of either device that the communication is occurring.
  • Elements of the Bluetooth protocol stack e.g., protocols, layers, applications, are divided into a transport protocol group, a middleware protocol group, and an application protocol group.
  • the transport group includes protocols that help Bluetooth devices locate each other and configure, produce, and manage both physical and logical links.
  • the system 100 uses the transport group transparently to users of Bluetooth-equipped devices.
  • the middleware protocol group includes additional transport protocols, Internet-related protocols (e.g., PPP, IP, TCP), wireless-application protocols, object-exchange protocols, a serial port emulator protocol (RFCOMM), a packet-based telephony control signaling protocol, and a service discovery protocol.
  • the RFCOMM protocol is used by the system 100 for legacy applications to operate using Bluetooth transport protocols and to transmit data among the VMC 108 and the RMM 110.
  • the packet-based telephony control protocol is used by the system 100 to provide control of telephony operations.
  • the service discovery protocol is used by the system 100 for devices to learn each other's services and to obtain information about how to access these services.
  • the applications protocol group includes specific applications that use the Bluetooth link. Both the VCM 108 and the RMM 110 are applications that reside at the application layer.
  • the MS 106 is a device that is configured to exchange messages with other devices, preferably wirelessly using Bluetooth technology.
  • the MS 106 is preferably a portable, wideband, third-generation mobile communication system.
  • the MS 106 would include GPS and Bluetooth functionality. GPS functionality can be used by the MS 106 to determine the location of the MS 106.
  • the MS 106 can be a cellular telephone, a laptop computer, or a Personal Digital Assistant (PDA). Referring to FIG.
  • the MS 106 includes an input 112 such as a keypad, a multimedia audio and video (A/V) device 114 for controlling devices such as a microphone, a speaker, and a display (e.g., an LCD) and a wideband wireless communication unit 116 for long-range communication and the RMM 110 includes an RMM software application 118 that controls the RMM functions.
  • the application 118 can be imbedded in a Bluetooth module 120.
  • the Bluetooth module 120 can be implemented with an Ericcson Bluetooth module ROK101007 (made by
  • either the MS 106 or the RMM 110 can include the Bluetooth module 120 and/or a GPS 122. If the Bluetooth capabilities are in the MS 106, then the RMM application 118 will reside in the MS 106. Otherwise, the RMM application 118 resides in an RMM host module.
  • the MS 106 can be a device other than a third-generation mobile communication device, may not include GPS, and may not have wideband capabilities.
  • the RMM 110 includes a host module, an audio interface, and an external devices interface.
  • the host module implements the middleware layer of the Bluetooth protocol and the RMM application 118.
  • the host module can be implemented using a microcontroller such as an Intel® KU80386EXTC, RAM, ROM, FLASH EPROM, and logical circuits to implement USB interface connection with the Bluetooth module 120.
  • the audio interface module provides analog-to-digital and digital-to-analog conversion and encoding of audio signals from the MS 106 to the Bluetooth module 120 using PCM and CVSD coding schemes according to the Bluetooth specification.
  • the audio interface can be implemented using commercially available CODEC chipes such as AM79021QJC made by Advanced Micro Devices, Inc. (AMD) of Sunnyvale, CA, or TP3071 made by National Semiconductor Corp. of Santa Clara, CA.
  • the external devices interface provides connectivity between the host module and the MSs using interfaces such as USB or an MS-proprietary interface, and is implemented with commercially available components.
  • the WVCS 104 includes a vehicle device portion 124 and the VCM 108.
  • the portion 124 includes an on-board computer 126 and instruments and sensors 128.
  • the computer 126 and the instruments and sensors 128 can control, e.g., ignition, fuel injection, and braking and can measure/detect, e.g., speed and temperature and can inform/advise/warn a user of a vehicle (e.g., a car 130 shown in FIG. 13) regarding vehicle conditions.
  • the VCM 108 includes a VCM software application 132 that controls the VCM 108. Referring also to FIG.
  • the VCM can intercept calls to/from the BS 14 and the MS 106 and provide services to parties to the calls, or intervene at the MS 106 without intercepting calls.
  • the VCM 108 can receive information from the portion 124 such as vehicle speed, whether vehicle doors are open, whether the vehicle 130 is moving, if the vehicle's parking brake is engaged, and whether the vehicle's gear selector is in park and for how long. Using this information, the VCM 108 can determine whether to inhibit connection of a call or other communication (e.g., a message) to/from the MS 106 or whether to provide other services and if so which service(s) to provide.
  • the VCM 108 operates with a transmitter power of about 1 milliwatt, which is typical of Bluetooth radio.
  • the VCM 108 can establish communication with, e.g., six RMMs 110, although the VCM 110 may be configured to communicate with more or fewer RMMs 110.
  • the WVCS 104 is connected to a battery bus of the vehicle 104 for receiving power. Thus, the WVCS 104 receives power in response to the ignition switch of the vehicle 130 being activated.
  • the WNCS 104 includes a Bluetooth module, a host module, an audio interface module, and an external devices interface module.
  • the Bluetooth module of the WNCS 104 can be the Ericsson ROK101007 or Intel's Bluetooth module.
  • the host module implements the middleware layer of the Bluetooth protocols and the NCM application.
  • the host module can be implemented using a central processing unit (CPU) such as an Intel® Pentium® III or CeleronTM, commercially available RAM, ROM, FLASH EPROM, and a USB interface such as Intel's PIIX4, an other interfaces and/or resources.
  • CPU central processing unit
  • the audio interface module can be the AM79021QJC from AMD or the TP3071 from National Semiconductor.
  • the external devices interface module provides connectivity between the host module and the vehicle device portion 124 using interfaces such as USB, Ethernet, IDE, or RS232, and is implemented with commercially available components.
  • a terminal display 134 includes a terminal display 134, a man-machine interface 136, a multimedia AN module 138, a wideband wireless communication unit 140, a GPS 142, and a Bluetooth module 144.
  • the terminal display 134 can provide video data through a monitor such as a CRT or an LCD, and audio data through a speaker.
  • the man-machine interface 136 can be, e.g., a keyboard, a stylus and touch-sensitive screen, and/or a microphone, with appropriate controls for interpreting data input using any of these apparatus.
  • Combinations of the display 134 and the interface 136 can provide for various features/services currently available, or that may become available, such as Internet access, email, video telephone calls, and stock quote updates all provided wirelessly to the WNCS 104.
  • the multimedia AN module 138 controls the receipt and presentation of the audio and video information through the display 134 and the interface 136.
  • the wideband wireless communication unit 140 provides large bandwidth communication of multimedia messages and files.
  • the GPS 142 provides information regarding location of the WNCS 104.
  • the Bluetooth module 144 provides for short-range wireless communication between the WVCS 104 and other devices with Bluetooth functionality within the piconet 112.
  • VCM 108 can provide services provided by the SLD ⁇ M 11 (FIG. 1) described above either in conjunction with, or independent of, the SLD ⁇ M 11.
  • the VCM 108 can detect RMMs disposed within the piconet 112 that are configured to receive services and RMMs can detect the VCM 108 if the RMM 110 is within the VCM's piconet 112. Communication between the VCM 108 and RMMs 110 can be initiated in response to detection by the VCM 108 of the RMM 110, or vice versa.
  • Communication between the VCM 108 and the RMMs 110 can establish which services each RMM 110 is configured to receive, the available services depending on the particular RMM 110 and/or a service package associated with the RMM 110 (e.g., that a user of the RMM 110 purchases).
  • Functions/services provided by the SLDNM 11 can be provided by the WVCS 104 in the VCM 108 and/or the RMM 110.
  • the VCM 108 and/or the RMMs 110 can store sets of services for each RMM 110. There may be more than one stored set of services, in which case the desired set can be selected by the RMM user.
  • stored sets may be (1) to handle all incoming communications according to unified messaging and to inhibit all outgoing communications, (2) the same as set (1) but with emergency incoming communications conveyed to the RMM 110 and emergency outgoing communications permitted, (3) the same as set (2) but with a predetermined, or ad hoc, list of sources of incoming communications also conveyed to the RMM 110 or enabled, or (4) conveying all incoming communications to the VCM 108 and permitting all outgoing communications from the RMM 110.
  • Speed and location of the MS 106 can be determined by communication between the VCM 108 and other devices in the vehicle 130, such as a speedometer of the vehicle 130 and a GPS of the vehicle 130, the MS 106, or the WVCS 104.
  • the determined speed and/or location can be used to provide services to the MS 106 based, e.g., on the location of the MS 106 and a likelihood that the MS 106 is traveling via the vehicle 130.
  • Messages received by the MS 106 or the VCM 108 can be stored for later retrieval, e.g., when the VCM 108 determines that the vehicle 130 has stopped, possibly for a predetermined amount of time.
  • Recorded messages, announcements, or other audio information can be played, e.g., using the AN modules 114 and/or 138, and/or the display 134.
  • These devices can provide audio messages as visual messages, e.g., using speech recognition, or visual messages as audio messages, e.g., using text-to-speech apparatus.
  • Messages can be played/provided to the MS user in response to a determination that the vehicle 130 is no longer moving, such as by determining that the vehicle's parking brake has been engaged, or the vehicle's gear selector has been in park, for a predetermined amount of time.
  • Multimedia information and parameters e.g., regarding limitations on connecting calls while the MS 106 is moving and options for the MS user, can be played/provided to the MS user while the vehicle 130 is moving.
  • the driving status of the MS user can be determined in response to the vehicle 130 being started or moving by analyzing responses to inquiries during start-up as described below. The driving status of the MS user can be used until it is determined that the vehicle 130 has stopped or the MS user otherwise indicates that the user's driving status has changed.
  • the VCM 108 and RMM 110 can detect the existence of each other in the piconet 112 and establish relationships for communications. Which device, the VCM 108 or the RMM 110, will initially be the master and which the slave is established. The VCM 108 and the RMM 110 also establish how to manage and organize communication between the WVCS 104 and the BS 14, including whether the VCM 108 will seize the communication channel, intercepting communication to/from the MS 106, while the vehicle 130 is moving.
  • Unified messaging can be provided by the VCM 108 and/or the RMM 110 and/or the WVCS 104.
  • Unified messaging provides universal access to messages of various types in a common format.
  • emails and faxes can be converted to audio messages using text-to- speech apparatus, and these converted messages and voicemail messages audibly played to the MS user, e.g., through the MS 106, or a speaker of the WVCS 104 that may be part of the VCM 108 or the vehicle device portion 124.
  • voicemail messages can be converted to text using speech recognition apparatus and these converted messages and email and fax messages displayed, e.g., on a display screen of the MS 106 or the display 134 of the WVCS 104.
  • the VCM 108 can handle incoming messages of various formats that are received while the destination of the message is inhibited from receiving the message, e.g., while the vehicle 130 is moving.
  • the VCM 108 can further provide the messages, in converted or original format as applicable, if the message is not inhibited from being delivered, e.g., at a time when the vehicle 130 is not moving, or has not moved for a predetermined amount of time.
  • Unified messaging can be provided in various manners. For example, messages can be displayed as single-line summaries on the display 134 or the MS 106.
  • the MS 106 or the WVCS 104 can be configured to allow the user to select a displayed message, and in response to the selection, audibly play or display the full message. If the MS 106 is, e.g., a phone, the MS 106 can audibly play a list of messages.
  • the VCM 108 and/or the RMM 110 and/or the WVCS 104 can also notify the user of prioritized messages.
  • the messages can be audibly played to the user and can be prioritized based, e.g., on the identity of the caller/sender and/or the content and subject of the message.
  • the caller can record a brief message summarizing the subject of the call and the urgency of the call, and the summary played for the user.
  • text-to-speech apparatus can be used to convert a portion, e.g., the subject line of an email, to speech and play the speech to the user.
  • the piconet 112 includes the VCM 108 and one or more RMMs 110 and is a peer-to- peer, device-to-device ad hoc network.
  • the piconet 112 may include different RMMs 110 at different times.
  • Devices in the piconet 112 can exchange information to "self configure" by discovering each other and negotiating how each will operate (e.g., which will serve as master and which as slave) and which devices will collaborate, without intervention by a user.
  • the devices in the piconet 112 can use the Bluetooth middleware protocol SDP
  • SDP Service Discovery Protocol
  • SDP provides for devices being the master, providing services, and devices being slaves, looking for services, with devices being able to serve as master or slave at various times.
  • the VCM 108 controls transactions in the piconet 112. For example, the VCM 108 controls which frequency- hopping sequence the piconet 112 members follow, when frequency hops occur (thus regulating timed events), which frequency is the current frequency, and which slave transmits/receives.
  • the VCM 108 also provides audio, video and multimedia functionality, speed detection/calculation, location functionality, and other functionality available in the WVCS 104. This functionality can be used by the RMM 110 acting as a slave in the piconet 112.
  • the RMM 110 can act as a master and the VCM 108 as slave, with the RMM 110 providing wireless communication for the devices in the piconet 112.
  • the VCM 108 may also act as a slave if the VCM does not communicate wirelessly.
  • the system 100 establishes the piconet 112 and provides services to RMMs 110 in the piconet that are configured to receive the services.
  • These services e.g, may help users of the RMMs 110 to obey laws, be alerted of laws of which the users may not otherwise have been aware, inform callers that the user is unavailable to talk at the moment, inform callers that the user will return their calls, permit incoming communications to be stored and retrieved, receive emergency communications, receive variously-formatted communications in a unified format, and prioritize stored communications.
  • a process 200 of using the system 100 includes stages
  • the piconet 112 is established.
  • a communication to/from at least one of the RMMs 110 is initiated and services are provided according to those appropriate for the particular RMM 110 as determined at stage 204.
  • the piconet 112 is established by the VCM 108 communicating with devices in the vicinity of the VCM 108.
  • the VCM 108 is powered up in response to the vehicle's ignition switch being activated so that the VCM 108 receives power from the vehicle's battery. Having power, the VCM 108 establishes a communication channel with a GPS that is either internal or external to the VCM 108 and the VCM 108 locates itself by communicating with the GPS.
  • the VCM 108 further proceeds to establish the piconet 112 according to The Specification of the Bluetooth System, vl.OB, December 1, 1999.
  • a frequency selection mode ensures that the devices in the piconet 112 transmit and receive information on the same frequency, which may be different for various operation conditions.
  • the VCM 108 determines which RMMs 110 will receive which services according to inquiry operations.
  • the VCM 108 executes inquiry operations to detect the presence of devices within the piconet 112 that are able to receive services providable by the system 100.
  • Inquiry operations are performed by the VCM 108 periodically, e.g., every 312.5 microseconds.
  • a different listening frequency for the inquiry operations can be selected periodically also, e.g., every 1.28 seconds.
  • GIAC General Inquiry Access Code
  • the GIAC is, e.g., a 68 or 72 bit field that serves several purposes including identifying the piconet 112.
  • a device's receiver is tuned to a particular access code using a correlator. If the correlator matches the access code of an incoming transmission sufficiently, then the receiver will continue receiving the bit stream and pass the stream to higher layers for processing.
  • the system 100 uses three classes of access codes: (1) in normal operation, each transmission is preceded by a Channel Access Code; (2) in page operation, each paging transmission is preceded by a Device Access Code; and (3) during inquiry operations, each inquiry transmission is preceded by an Inquiry Access Code.
  • the VCM 108 initiates a start-up sequence.
  • This start-up sequence issues inquiries to determine which devices will receive which services.
  • the VCM 108 causes audio inquiries to be made through a speaker of the vehicle or displays video inquiries on the display 134.
  • Responses to these inquiries by one or more of the RMM users, provide parameters for operation of the VCM 108 and provision of services.
  • the VCM 108 identifies the devices found during inquiry operations and inquires what services are to be provided to the devices. For example, the VCM 108 can cause a prompt to be played/displayed in the vehicle 130.
  • the prompt may be, e.g., "Cellular phone number 123 and PDA 12 AX have been detected, please indicate which devices are to be active and which services are to be received by each.”
  • the VCM 108 can cause the devices to display menus of options of services that the users of the devices select.
  • the options can be individual services or sets of services defined by the VCM 108 or the user, or can be default sets programmed into the devices.
  • the responses to the VCM's inquiries determine which RMMs 110 receive which services.
  • all RMMs 110 in the piconet 112 may receive services, with the VCM 108 handling messages (e.g., voice calls, emails, messages, pages) to/from all the RMMs 110, or maybe only the driver's RMM 110 may receive services other than connecting all calls, or other variations of devices and services.
  • the start-up sequence can be superseded by preprogramming of devices that establish services to be received automatically. Devices can have which services are to be provided to them preprogrammed and recognized by the VCM 108.
  • the preprogrammed default services may be various combinations of services.
  • the device is a phone owned by the owner of the vehicle 130
  • the user may be assumed to be the driver of the vehicle 130 and the default services are the user's preferences for when the user is a driver.
  • the preprogrammed services may be overridden by the user selecting different services.
  • Another start-up sequence can be initiated if the VCM 108 detects a device is introduced into the piconet 112, after the initial start-up sequence, for a predetermined amount of time such as five minutes.
  • the introduced device may be an RMM 110 that is or is not configured to receive services from the system 100, or may be another VCM.
  • a new start-up sequence can be initiated in response to another RMM 110 being brought into the vehicle 130 such as if a person enters the vehicle 130, or stands close to the vehicle 130, and has an MS 106 such as a cell phone.
  • Another VCM can be introduced into the piconet 112, e.g., if another vehicle moves close to the vehicle 130 such that the VCM of the other vehicle is within the piconet 112. If another VCM and RMM for receiving services of system 100 are identified in the piconet 112, then the services that the additional RMM should receive are determined. At stage 206, communication with the piconet 112 is initiated and services are provided. For example, the VCM 108 can control all communication to/from any RMM 110 in the piconet 112 and can take care of all transactions during the life of the piconet 112.
  • the VCM 108 can receive/intercept all communications to a particular RMM 110 in the piconet 112, and can receive/intercept all communications to various RMMs 110 in the piconet 112 that are associated with a common user.
  • the VCM 108 can handle "one-number find me" services in which a caller can dial one number, and various devices associated with the user (e.g., home phone, work phone, cell phone, pager) are contacted in order to find the user.
  • the VCM 108 provides the services, among others, provided by the SLDNM 11 as described above.
  • the VCM 108 will not inhibit communications in order to establish whether the user of an RMM 110 to receive/transmit a communication is driving if the RMM's user has already established what services are to be provided, and therefore established how to affect communications to/from that RMM.
  • the VCM 108 can inform users of potential illegality (e.g., during the start-up sequence or when a communication is initiated), and the RMM user may choose whether to obey or ignore the law.
  • Processes 200 and 220 are exemplary, with variations being possible and within the scope of the invention. For example, stages can be added to or deleted from the processes 200 and/or 220, and the stages can be in orders other than those shown.
  • software for at least the system 100 can be written in JAVA and/or C++ programming languages.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Electric Propulsion And Braking For Vehicles (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention se rapporte à un système conçu pour être utilisé avec une unité de communication mobile et un dispositif de fourniture de données associé à l'unité de communication mobile. Ce système inclut un appareil conçu pour recevoir les données associées à l'unité de communication mobile et pour utiliser ces données pour déterminer si l'unité de communication mobile se trouve à bord d'un véhicule à moteur, ledit appareil étant par ailleurs conçu pour délivrer en sortie des informations indiquant si l'unité de communication mobile se trouve à bord d'un véhicule à moteur. Ce système comporte également un module de commande couplé aux fins de la communication avec ledit appareil et conçu pour délivrer des signaux de commande en réponse aux informations de sortie de l'appareil dans le but de modifier la communication entre l'unité de communication mobile et une autre unité de communication.
PCT/US2001/002454 2000-01-25 2001-01-25 Détection/notification de conduite WO2001056307A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001232966A AU2001232966A1 (en) 2000-01-25 2001-01-25 Affecting communication if a mobile communication unit is likely to be traveling via a motor vehicle

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US17784000P 2000-01-25 2000-01-25
US60/177,840 2000-01-25
US18809600P 2000-03-09 2000-03-09
US60/188,096 2000-03-09
US73066000A 2000-12-06 2000-12-06
US09/730,660 2000-12-06

Publications (2)

Publication Number Publication Date
WO2001056307A2 true WO2001056307A2 (fr) 2001-08-02
WO2001056307A3 WO2001056307A3 (fr) 2002-07-18

Family

ID=27390884

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/002454 WO2001056307A2 (fr) 2000-01-25 2001-01-25 Détection/notification de conduite

Country Status (2)

Country Link
AU (1) AU2001232966A1 (fr)
WO (1) WO2001056307A2 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003049380A1 (fr) * 2001-12-03 2003-06-12 Motorola, Inc. Procede et systeme permettant de rassembler des informations de localisation
EP1369837A2 (fr) * 2002-06-03 2003-12-10 Omron Corporation Système de surveillance, méthode de commande à distance d'un capteur, commandeur à distance d'un système de surveillance
EP2127407A1 (fr) * 2007-03-02 2009-12-02 Aegis Mobility, Inc. Gestion de sessions de communication de dispositif mobile pour réduire la distraction de l'utilisateur
EP3273723A4 (fr) * 2015-03-20 2018-09-05 Nec Corporation Système de communication, dispositif de gestion, terminal de communication, procédé de commande de communication, procédé de transmission d'informations de capteur, et support lisible par ordinateur
EP2632128B1 (fr) * 2012-02-27 2020-06-03 BlackBerry Limited Procédé et appareil concernant la gestion dynamique d'appels entrants

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0851699A2 (fr) * 1996-12-26 1998-07-01 Matsushita Electric Industrial Co., Ltd. Appareil de communication mobile possèdant une fonction de sécurité et procédé de communication avec une station de base sécurisée
WO1999013668A1 (fr) * 1997-09-10 1999-03-18 Siemens Automotive S.A. Procede et dispositif de commande d'une unite de telephonie mise en place dans un vehicule automobile

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0265536A (ja) * 1988-08-31 1990-03-06 Suzuki Motor Co Ltd 自動車電話機
JPH08149543A (ja) * 1994-11-15 1996-06-07 Kano Densan Hongkong Yugenkoshi 無線通信装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0851699A2 (fr) * 1996-12-26 1998-07-01 Matsushita Electric Industrial Co., Ltd. Appareil de communication mobile possèdant une fonction de sécurité et procédé de communication avec une station de base sécurisée
WO1999013668A1 (fr) * 1997-09-10 1999-03-18 Siemens Automotive S.A. Procede et dispositif de commande d'une unite de telephonie mise en place dans un vehicule automobile

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
PATENT ABSTRACTS OF JAPAN vol. 014, no. 241 (E-0931), 22 May 1990 (1990-05-22) & JP 02 065536 A (SUZUKI MOTOR CO LTD), 6 March 1990 (1990-03-06) *
PATENT ABSTRACTS OF JAPAN vol. 1999, no. 07, 31 March 1999 (1999-03-31) & JP 08 149543 A (KANO DENSAN HONGKONG YUGENKOSHI), 7 June 1996 (1996-06-07) *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003049380A1 (fr) * 2001-12-03 2003-06-12 Motorola, Inc. Procede et systeme permettant de rassembler des informations de localisation
EP1369837A2 (fr) * 2002-06-03 2003-12-10 Omron Corporation Système de surveillance, méthode de commande à distance d'un capteur, commandeur à distance d'un système de surveillance
EP1369837A3 (fr) * 2002-06-03 2004-05-06 Omron Corporation Système de surveillance, méthode de commande à distance d'un capteur, commandeur à distance d'un système de surveillance
US6950020B2 (en) 2002-06-03 2005-09-27 Omron Corporation Surveillance system, method of remotely controlling sensor apparatus, and surveillance remote controller
CN1316437C (zh) * 2002-06-03 2007-05-16 欧姆龙株式会社 监视系统、监控传感设备的方法
EP2127407A1 (fr) * 2007-03-02 2009-12-02 Aegis Mobility, Inc. Gestion de sessions de communication de dispositif mobile pour réduire la distraction de l'utilisateur
EP2127407A4 (fr) * 2007-03-02 2015-03-11 Aegis Mobility Inc Gestion de sessions de communication de dispositif mobile pour réduire la distraction de l'utilisateur
EP2632128B1 (fr) * 2012-02-27 2020-06-03 BlackBerry Limited Procédé et appareil concernant la gestion dynamique d'appels entrants
EP3273723A4 (fr) * 2015-03-20 2018-09-05 Nec Corporation Système de communication, dispositif de gestion, terminal de communication, procédé de commande de communication, procédé de transmission d'informations de capteur, et support lisible par ordinateur
US10863417B2 (en) 2015-03-20 2020-12-08 Nec Corporation Communication system, management apparatus, communication terminal, communication control method, sensor information transmission method, and computer readable medium

Also Published As

Publication number Publication date
AU2001232966A1 (en) 2001-08-07
WO2001056307A3 (fr) 2002-07-18

Similar Documents

Publication Publication Date Title
US20020128000A1 (en) Driving detection/notification and location/situation-based services
US6493629B1 (en) Method of and system for coupling location information
US8923826B2 (en) Mobility call management
US7058385B2 (en) Emergency call system within a telecommunication network
EP1276064A2 (fr) Système expert de gestion tous usages
US20080119203A1 (en) Method and system for providing location based services
US20050197096A1 (en) Emergency call system and control method thereof
EP1589779A2 (fr) Dispositif pour limiter la fonctionnalité et procédé pour limiter la fonctionnalité
CN101595712B (zh) 使用无线通信阻止紧急呼叫错误使用的系统和方法
JP2003502885A (ja) 無線端末の場所に基づく制御信号生成方法
US7715820B2 (en) Method for connecting a call in a mobile station during an emergency situation
US7336933B2 (en) Method of maintaining communication with a device
WO2001056307A2 (fr) Détection/notification de conduite
US20010029176A1 (en) Portable cellular phone system, method for controlling same and storage medium storing control program for conrtolling same
KR20050040373A (ko) 비상버튼이 내장된 무선단말기를 이용한 위급상황 구조요청 서비스 장치 및 그 방법
TW564629B (en) Driving detection/notification and location/situation-based services
TW519846B (en) Driving detection/notification
JP4093136B2 (ja) 通信制御方法
JP2003152867A (ja) 移動体通信システムにおける緊急呼通知方式
KR20050011612A (ko) 이동통신 단말기(핸드폰, pda 등)를 이용한 주변인물 신원확보를 통한 비상구호 시스템
JP3150118B2 (ja) 携帯電話機及びその通信方法
KR20110068782A (ko) 차량 운행 상황 인지에 따른 단말 제어 방법 및 장치
EP1282322B1 (fr) Systèmes de communication et stations mobiles et installations associés
KR20040013701A (ko) 블루투스를 이용한 이동통신 단말기의 근접여부 알림 방법
KR100288735B1 (ko) 위급상황처리및피보호자상태파악을위한서비스망

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP