WO2014075715A1 - Method, network and network entity for providing information of communication devices close to a location of an event - Google Patents

Abstract

Method, network and network entities for providing information of communication devices having a location within a predetermined range of a location of an event to a receiving entity. The method includes determining for each device information, including a device identification code and location information, receiving, from a triggering device, an event message including information associated with the location of the event, and determining, on the basis of the location of the event, a location area associated with the location of the event. The method further includes determining for each device whether the location of that device is within the location area, retrieving device information of devices having location information indicating a location of that device within the location area, and transmitting the retrieved device information to the receiving entity.

Description

Title: Method, network and network entity for providing information of communication devices close to a location of an event

TECHNICAL FIELD

The invention relates to communications networks. BACKGROUND

It is known that, in case of a certain event, such as an emergency, a government is able to send a free text alert message, broadcasted via a Cell Broadcast messaging function of a telecommunication network, so that mobile terminals of subscribers receive the alert message.

Often a special emergency centre is in charge of sending the emergency message. This emergency centre selects all base stations of one or more mobile telecommunication networks in the emergency area, assembles an emergency message, and broadcasts the message via all the selected base stations. The message is then received by mobile terminals registered with those base stations.

This known method commonly depends on the subscribers associated with the receiving terminals being subscribed to a certain alert service and/or depends on an operator the subscriber has a subscription with.

The emergency can be reported to the emergency centre as a manually generated message, such as a voice call or a text message. It is also possible that the emergency is automatically generated, e.g. by an in- home alarm system. The European Commission aims to have new cars in the European Union, to be equipped with a black box that supports eCall (SIM-based) which in case of a serious accident causes the car to

automatically transmit information relating to the accident. That information contains information relating to the location of the car and the status of certain sensors, such as airbag. Although the prior art systems allow mobile terminals of subscribers in the emergency area to be notified of the emergency, there is no mechanism in place for automatically storing information of

communication devices that are close to the location of the event, while such information could be highly valuable for e.g. authorities in view of contacting potential witnesses of the event.

SUMMARY

It is an object of the invention to obviate at least some of the above disadvantages. It is also an object to provide a network entity for a communications network providing more versatility.

Thereto, according to the invention is provided a method for providing information of communication devices having a location within a predetermined range of a location of an event to a receiving entity. The method includes the steps of: determining, for each device of at least a group of devices within a plurality of devices, device information, including a device identification code and location information, associated with that device; receiving, from a triggering device, an event message including information associated with the location of the event; determining, on the basis of the location of the event, a location area associated with the location of the event; determining for each device of the group of devices whether the location of that device is within the location area; retrieving device information of devices of the group of devices having location information indicating a location of that device within the location area; and

transmitting the retrieved device information to the receiving entity.

This provides the advantage that the device information, including a device identification code and location information, of the device having a location within the predetermined range of the location of the event is transmitted to the receiving entity. The event can be an alarm situation, such as a car accident, robbery, fire, home break-in or the like. The receiving entity is e.g a governmental authority. This receiving entity can e.g. be associated with a public service and/or an emergency service, such as a police department, fire department, ambulance service, medical emergency service. The method can include transmitting information relating to the event and/or the location of the event to the receiving entity.

The method enables to inform the receiving entity about subscribers within a predetermined range of a location of an event. This information can be additional to the information about the event itself. Also, the information about the subscribers within a predetermined range of a location of an event can be independent of whether or not subscribers are subscribed to a certain alert service and can also be independent of to which operator a subscriber belongs.

Optionally, at least some of the communication devices are mobile communication devices, such as mobile terminals. Hence, not only fixed devices having a location within a predetermined range of a location of an event, but also (or even only) mobile device which happened to be at a location within a predetermined range of a location of an event can participate in the method.

The triggering device can be arranged for manually and/or automatically generating and transmitting the event message.

Optionally, the step of determining, for each device of at least a group of devices within a plurality of devices, the device information includes storing said device information in a database. Then, the step of retrieving device information of the devices of the group of devices having location information indicating a location of that device within the location area includes retrieving said device information from the database. This provides that the advantage that the device information is already present in the database at the moment that the event occurs, so that retrieval of the device information of devices of the group of devices having location information indicating a location of that device within the location area can be performed immediately without necessitating determining, for each device of at least a group of devices within a plurality of devices, the device information at the moment the event occurs.

Optionally, the step of determining includes extracting the device information, including the identification code and location information, from a message, such as a Mobile Application Part version 3, MAPv3, Mobility Management event notification, Note-MM-event, transmitted by a device of the group of devices. This allows the device information to be extracted from a message that the device transmits, while the message need not be specifically transmitted for the purpose of providing the device information in view of the event.

Optionally, the method includes the step of updating in the database location information of at least one device of at least the group of devices, e.g. if the location of the device changes.

The step of determining the device information for each device of at least a group of devices within a plurality of devices can be performed by a storing entity including a collector arranged for collecting for each device of at least the group of devices within the plurality of devices the device information including the device identification code and the location information. Optionally, the storing entity includes a storing unit arranged for storing the device information in the database. The database can be associated with the storing entity.

Optionally, the device information includes additional information, such as one or more of a photograph, a video recording, an audio recording, and text information.

Optionally, the step of storing the device information in the database includes storing, by a group of two or more storing entities, e.g. each associated with a different provider, device information in a single database. Hence, a first storing entity determines and stores the device information for each device of at least a first group of devices within the plurality of devices and a second storing entity determines and stores the device information for each device of at least a second group of devices within the plurality of devices. This provides the advantage that a centralised database is provided for more than one storing entities. The centralised database renders retrieving device information of devices having location information indicating a location of that device within the location area easier.

Optionally, the retrieved device information is stored in an event database together with an indication of the event and location of the event. This allows the device information of the device(s) having a location within the predetermined range of the location of an event to be accessible for future reference.

Optionally, the step of determining whether the location of the device is within the location area includes determining whether the location information, such as a cell-ID, associated with that device corresponds with the location area, and if the location information corresponds with the location area, requesting an actual location, such as a current location, of the device, e.g. using a MAP Any Time Interrogation (MAP-ATI) message, and determining whether the actual location is within the location area. This allows for more accurate and more up to date determination of whether or not the device is within the location area.

Optionally, a message related to the event is transmitted to one or more devices of the group of devices having location information indicating a location of that device within the location area. Hence, the subscribers associated with those devices can be informed about the event. This may cause the subscribers to be more alert, e.g. in the event of a missing child. Optionally, the message includes a request to the subscriber to provide additional information such as one or more of a photograph, a video recording, an audio recording, and text information.

Optionally, the device information transmitted to the receiving entity is anonymised. Thereto, the device identification code can be encoded and/or anonimysed. Anonymisation of the device information protects the privacy of the subscribers associated with the devices within the location area, while it is e.g. still possible to the message related to the event to these devices.

The invention also relates to a network entity including a receiver arranged for receiving, from a triggering device, an event message including information associated with a location of the event. The network entity further includes a processing unit arranged for determining, on the basis of the location of the event, a location area associated with the location of the event, a retrieval unit arranged for retrieving device information of devices of the group of devices having location information indicating a location of that device within the location area, and a transmitter arranged for transmitting the retrieved device information to a receiving entity.

Optionally, the retrieval unit is arranged for retrieving the device information from the database storing for each device of at least a group of devices within a plurality of devices device information including the device identification code and location information.

Optionally, the network entity further includes a storing unit arranged for storing the retrieved device information in the event database together with an indication of the event and location of the event.

The invention also relates to a triggering device including a detector for detecting an event, a location determination unit arranged for determining a location of the event, a processor arranged for generating an event message including information associated with the location of the event, and a transmitter arranged for transmitting the event message to a network entity, such as the above mentioned network entity. The triggering device can be a mobile communications device.

The invention also relates to a storing entity as described above. The invention also relates to a communications device including a processor arranged for generating device information, including a device identification code and location information, associated with that device and arranged for transmitting said device information to the storing entity mentioned above. Optionally, the communications device is a mobile communications device. The communications device can also be a fixed communications device. Optionally, the communications device is further arranged to include additional information in the device information. The additional information can include one or more of a photograph, a video recording, an audio recording, and text information. Thereto, the

communications device can include a recording unit such as a digital camera, a microphone, a keyboard and/or a touch screen. Optionally, the communications device is arranged for recording the additional information in response to an invitation to record said additional information. The invitation may be an invitation to the user of the device to actively record the additional information. Alternatively, or additionally, the recording unit of the communications device is arranged to automatically generate the additional information, e.g. upon receiving an instruction thereto, e.g. from the receiving entity and/or the network entity. The communications device can be arranged such that the recording unit can be remotely activated and/or deactivated by the receiving entity and/or the network entity in case it has been determined that the communications device is located within the location area. The communications device can be arranged such that the recording unit ignores instructions to be remotely activated and/or

deactivated by the receiving entity and/or the network entity in case it has been determined that the communications device is located outside the location area. Optionally, the communications device is further arranged for, in response to a request from a storing entity for further location information, determining a location of the communications device and transmitting the location information to the storing entity. Optionally the communications device includes a location determination unit arranged for determining the location of the communications device.

The invention also relates to a telecommunications network, such as a Global System for Mobile Communications (GSM) network or Universal Mobile Telecommunications System (UMTS) network, including a triggering device as descried above, a network entity as described above, a database storing for each device of at least a group of devices within a plurality of devices device information including a device identification code and location information, and a receiving entity arranged for receiving the retrieved device information from the network entity. Optionally, the telecommunications network, further includes one or more storing entities as described above, and one or more communications devices as described above.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will now be further elucidated by means of non-limiting examples referring to the drawings, in which

Figure 1 is a schematic representation illustrating the network; Figure 2 is a flow chart illustrating an embodiment of the method steps performed by the network;

Figure 3 is a schematic representation illustrating the network;

Figure 4 is a schematic representation, illustrating a part of the network;

Figure 5 is a schematic representation, illustrating a part of a network; and Figure 6 is a schematic representation, illustrating a network unit.

In the Figures like reference numerals refer to like entities or processes.

DETAILED DESCRIPTION

Figure 1 shows a schematic representation illustrating a network 1 according to the invention. The network 1 includes a plurality of communication devices 2. The network 1 further includes a storing entity 6 that stores device information of each device 2 of at least a group of devices within the plurality of devices in a database 12. The network 1 further includes a triggering device 4. The network 1 further includes a network entity 16 to which the triggering device 4 transmits an event message in case an event occurs. The network entity 16 determines, on the basis of the location of the event, a location area associated with the location of the event, and retrieves device information of devices 2 of the group of devices having location information indicating a location of that device within the location area.

In Figure 1 the triggering device is a mobile communications device. The triggering device 4 includes an event detector 9 arranged for determining whether or not an event occurs. In this example, the event is an emergency situation, such as a car accident. The event detector 9 can be arranged for automatically and autonomously detecting an event. In this example, the event detector 9 is arranged to detect activation of an airbag or detect a deceleration beyond a predetermined threshold value (potentially indicating a crash). It is also possible that the event detector 9 includes an actuator for manual activation, such as a push-button.

When the processing unit 11 determines that the event occurs, it generates an event message and transmits this by means of a transmitter 14. The event message includes information representative of a location of the event. It will be appreciated that the triggering device 4 can include a location determination unit 13 for determining the location of the triggering device.

The network 1 further includes a network entity 16. The network entity 16 includes a receiver 18 arranged for receiving 101 (see Figure 2) the event message transmitted by the transmitter 14 of the triggering device 4. The network entity 16 further includes a processing unit 20 arranged for determining 102, on the basis of the location of the event, a location area associated with the location of the event. The location area can be defined by e.g. a set of geographic coordinates defining a polygon, or a circle with a geographic centre and radius. The determining 102 of the location area on the basis of the location of the event can be performed by an application running on the processing unit 20. The network entity 16 can include a memory 21 for storing i.a. the location area.

The network 1 further includes a plurality of devices 2. Here, the plurality of devices includes mobile terminals. The network 1 further includes a storing entity 6. The storing entity 6 includes a collector 8 arranged for collecting device information for each device 2, of at least a group of devices within the plurality of devices. The device information includes a device identification code and location information of the device 2. The storing entity 6 further includes a storing unit 10 arranged for storing 104 the device information in a database 12 associated with the storing entity 6. It will be appreciated that the network 1 can include two or more storing entities 6. In Figure 1 two storing entities 6 are shown. The first storing entity 6 (shown in drawn lines) collects device information from a first group of devices. The second storing entity (shown in dashed lines) collects device information from a second group of devices. In Figure 1 both storing entities 6 store the device information in a common database 12. It will be appreciated that the first storing entity can be associated with a first operator, while the second storing entity is associated with a second operator.

In an embodiment, one or more of the devices 2 is further arranged to include additional information in the device information and to transmit this to the storing entity 6 using a transmitter 29. The additional information can be recorded by a recorder 27, such as a digital camera, a microphone, a keyboard and/or a touch screen. The additional information can include a photograph or a video recording recorded by a digital camera of the device 2, an audio recording recorded by a microphone of the device 2, and/or text information recorded by a text input device, such as a keyboard or touch screen, of the device 2. Optionally, the recorder 27 of the

communications device 2 is arranged to automatically generate the additional information, e.g. upon receiving an instruction thereto, e.g. from the receiving entity 26 and/or the network entity 16. It will be appreciated that it is possible that the device 2 transmits the additional information directly to the receiving entity 26 without first transmitting the additional information to the storing entity 6. A processor 25 of the device 2 controls the recording of the additional information.

The network entity 16 further includes a retrieval unit 22 arranged for retrieving 105 from the database 12 device information of devices of the group of devices having location information indicating a location of that device within the location area. Thereto, a location comparator 15 (in Figure 1 associated with the database 12) compares 106, 108 the location information of each device information with the location area. If the location information of a device information stored in the database 12 is within the location area, i.e. within a predetermined range of the location of the event, that device information is transmitted to the network entity 16. The network entity further includes a transmitter 24 arranged for transmitting 116 the retrieved device information to a receiving entity 26. The receiving entity 26 can e.g. be associated with a public service and/or an emergency service, such as a police department, fire department, ambulance service, or medical emergency service. It will be appreciated that the network entity 16 can generate a report including all retrieved device information, and can transmit said report to the receiving entity 26.

In the example of Figure 1, the network entity 16 further includes a storing unit 30 arranged for storing 118 the retrieved device information in an event database 32 together with an indication of the event and location of the event.

The receiving entity 26 can transmit, or initiate transmittal of, a message relating to the event to the devices 2 within the location area. This message can contain information, such as location and nature, about the event. The message can also contain a request to subscribers associated with the devices 2 in the location area to be alert and/or to record additional information such as a photograph, a video recording, an audio recording or a text message. The message can also contain an instruction to the processors of the devices in the location area to automatically generate the additional information. The storing entity 6 stores the additional information in the database 12.

The storing entity 6 can be arranged to receive device location update messages, extract location information and device identification codes out of the messages, and store the location information and the device identification codes for a plurality of devices in the database 12. The storing entity 6 can be embodied as a Service Control Point, SCP, or a Service Transfer Point, STP, or any other suitable network element.

Referring now to Figure 3, in case of an emergency situation, such as a car accident, an event message will be raised. In case of an emergency, the event message can also be referred to as emergency message. In this example, the emergency message is generated

automatically by the triggering device 4. Based on the capabilities of the triggering device 4, additional information can be added to the event message. The additional information can e.g. include a photograph and/or video recording recorded by a digital camera of the triggering device, an audio recording recorded by a microphone of the triggering device 4 or a text message recorded by a text input device, such as a keyboard or touch screen, of the triggering device 4. The additional information can also include an event indictor, such as a code or text string associated with the event, e.g. a code indicating deployment of an air bag, a code indicating a panic button being activated, etc.. In Figure 3 the emergency message is received by a combined Mobile Switching Centre, MSC, and Service Switching Point, SSP, 17.

Based on the service request (e.g. number based triggering) associated with the emergency message, in Step 2 an Intelligent Network, IN, application 9 (in Figure 3 running on top of Telecom Service Platform, TSP, 7) will be triggered. In Figure 3 the application 9 is referred to as Automatic Witness Service, AWS, 9. Based on the service request, the application 9 will analyse triggering information of the emergency message. The triggering information can include Mobile Station Integrated Services Digital Network number (MSISDN), International Mobile Subscriber

Identity (IMSI), location of the triggering device 4, and the optional additional information. The TSP 7 provides the triggering information of the emergency message to the AWS database 12.

In Step 3, the triggering information, provided by the AWS application 9 is stored in the AWS database 12.

In step 4, during an emergency situation, the retrieving unit 22 will fetch triggering information out of the database 12 to provide a receiving entity 26 (e.g. the nearest police department) information about the location of the emergency. In this example, an alerting application 19 is running on the network entity 16, more specifically on the TSP 23. It will be appreciated that in this example the MSC/SSP 17 and the TSP 23 together form the network entity 16. The Alerting Application 19 retrieves the device information of communication devices 2 within a predetermined range of the location of the event and provides this to the receiving entity 26. The Alerting application can also retrieve the additional information from the devices 2 within the predetermined range of the location of the event and provides this to the receiving entity 26.

Figure 4 schematically shows an example of a part of a telecommunication network. In this example, the telecommunication network 1 comprises a Global System for Mobile Communications, GSM, network. It will be appreciated that it is also possible that the network 1 comprises a Universal Mobile Telecommunications System, UMTS, network.

In Figure 4 a device 2, here a mobile terminal, is shown located in a coverage area 40 of a base station 42 of a GSM network. The coverage area 40 is also referred to as cell. The base station 42 is in communication with a Visted Mobile Switching Centre, VMSC, 44 comprising a Visited Location Register ,VLR, 46. The VMSC 44 is in communication with a Service Control Point, SCP, 48 on which an AWS IN application 50 is running. In this example the SCP 48 is also referred to as gsmSCP.

The AWS IN application 50 is using a database (AWS database 12) to store information. The location of the mobile terminal 2 is constantly updated and stored into the GSM network. Updates occur during a periodic location update, when making or receiving a call, when sending or receiving a Short Message Service, SMS, or when switching on or off the mobile terminal 2.

In this example, the VLR 46 is a state of the art VLR which sends a Mobile Application Part version 3, MAPv3, Mobility Management event notification, NoteMM-event, to the gsmSCP 48. Such notification is defined in 3GPP TS 29.002 for R99 as a MAP Operation ("NoteMM- Event"). A NoteMM-Event contains the following information: IMSI code, Locationlnformation, and MSISDN of the device 2. The

Locationlnformation field comprises the following parameters:

- CellGloballdOrServiceArealdOrLai;

- Geodeticlnformation;

- Geographicallnformation;

- LocationNumber;

- IsdnAddressString;

- AgeOfLocationlnformation.

Based on the NoteMM-Event the IN application 50 extracts device information, including subscriber information and corresponding location information, from the NoteMM-event and stores this device information into the database 12. The IN application 50 stores the device information of at least a group of devices 2 within a plurality of devices in the database 12. For this reason, the AWS IN application 50 is also referred to as Storing application. The SCP 48 therefore acts as the storing entity 6. The subscriber information can comprise the IMSI and/or the MSISDN for a specific mobile terminal 2.

In this example, an entry in the database 12 includes: a Cell-ID of the cell 40 in which the terminal 2 is located (i.e. registered), an IMSI code of the terminal 2, and an MSISDN code of the terminal 2. The AWS database 12 can be a central database accessible for multiple Storing applications (multiple storing entities 6), e.g. an external Service Data Point, SDP, serviced by different telecommunication providers. In this way, one database 12 comprises location information of mobile terminals 2 of different providers.

The device information stored in the AWS database 12 is used to be provided to one or more receiving entities 26 of all (kind of mobile) terminals 2 within a certain area.

It is possible that the Alerting application 19 is arranged to cooperate with an entity- specific User Interface, UI, (e.g. Graphical UI, GUI) executed at a certain receiving entity 26. Thereto, the processor 20 and/or the transmitter 24 of the network entity 16 can be arranged to arrange the device information in a predetermined format. The receiving entity 26 can be embodied as a computer, or computer system, of a public service and/or an emergency service, such as a police department, fire department, ambulance service, medical emergency service.

Such receiving entity 26, e.g. the police department, is informed in case of an emergency. At the police department, a decision is taken whether to contact people (subscribers) in an area around the emergency, such as in case of a robbery or pyromaniac attack.

In this example, the Alerting application 19 is arranged to translate metrics of the emergency location area into Cell-IDs of cells that at least partly overlap the emergency location area. The Alerting application 19 accesses the AWS database 12 to identify all terminals having location information indicating the presence of that terminal 2 within cells with the Cell-IDs indicating that those cells at least partly overlap the emergency location area. The Alerting application 19 sends device information of each of the identified terminals 2 to the receiving entity 26, e.g. to the police department.

The Alerting application 19 can provide detailed info of all devices

2 within the location area to the receiving entity 26. To provide more detailed and exact location information, the selection of terminals 2 in the location area can be done in several steps. In a first step, the Alerting application 19 selects each mobile terminal 2 that has a Cell-ID associated with a cell at least partly overlapping with said location area. In a second step, the current position of the selected terminals 2 is requested by means of an active location request using a MAP-AnyTime Interrogation, MAP- ATI, message, e.g. by the network entity 16. In a third step, a set of terminals 2 is determined for which the actual location information received from the terminals is within the location area. In this way the number of mobile terminals 2 of which the device information is provided to the receiving entity 26 is limited to those terminals 2 that are actually located in the emergency location area at the given time.

It is also possible that information about the origin of the device 2 (for example the country code (CC) contained in the IMSI code) is included in the device information provided to the receiving entity 26.

Referring now to Figure 5, when the user of a mobile terminal 2 inserts his Subscriber Identity Module, SIM, card and switches on the mobile terminal 2, the mobile terminal will identify available public land mobile networks, PLMNs. Based on ruling on the SIM card in co-operation with the networks, one specific PLMN is selected to attach the terminal 2 to. As is known by the skilled person, this attachment is initiated by a Direct Transfer Application Part, DTAP, Attach message 56 from the mobile terminal 2 to an MSC 52. A PLMN can have multiple MSCs each covering a specific part of the total coverage area of the PLMN and/or having

overlapping coverage areas. The receiving MSC 52 is responsible for all mobile terminals 2 connected to the PLMN in that specific part. The MSC 52 receives the DTAP-Attach 56 which contains the IMSI as stored on the SIM card.

Upon receiving the DTAP-Attach 56, the MSC 52 sends a

MAP_LOCATION_UPDATE message 58 to a Home Location Register, HLR, 54. In Figure 5, the message 58 is sent to the HLR 54 via the STP. In this example, the STP acts as the storing entity 6. This HLR 54 is the own network HLR for a home subscriber or another network HLR for a visiting subscriber, as indicated by the country and network code of the IMSI. The HLR 54 receiving the message 58 registers the terminal location of the terminal 2 with the subscription having the corresponding IMSI together with the MSC 52 to address. Where IMSI and MSISDN are static parts of the subscription, the terminal location and the MSC 52 to be addressed are dynamic. The HLR 54 acknowledges the MAP_LOCATION_UPDATE message 58 with a response 60 back to the MSC 52 which includes the MSISDN as contained in the subscription.

When switching off a mobile terminal 2 or when moving out of MSC coverage area this is notified to the MSC 52 by means of a DTAP- Detach message send by the mobile terminal 2 to the MSC 52, which includes again the IMSI.

In this example, the MSC 52 does not immediately discard the subscriber's subscription data which the MSC 52 obtained from the HLR 54 and maintains it in its internal data store. The MSC 52 sets a timer for this subscription, because the terminal 2 may be switched on again in short time or may re-enter the coverage area like in border cases. The timer value is a MSC parameter and can be set to several hours or a day.

When the terminal 2 is switched on again or re-enters the coverage area of the MSC 52 before the timer has expired, the timer is cancelled together with sending the MAP_LOCATION_UPDATE message. If, however, the terminal 2 is not switched on or does not re-enter the coverage area within the maximum duration of the timer, the timer expires and the MSC 52 sends a MAP_PURGE_MS message to the HLR 54 indicating that the local registration of the IMSI/MSISDN is discarded.

When moving out of the MSC coverage area it may be that the mobile terminal 2 does not moves into another MSC coverage area at the same time (e.g. in case of a non network covered area, e.g. a tunnel).

Therefore, the MSC 52 also sends a MAP_CANCEL_LO CATION message to the HLR 54 indicating that the terminal location is no longer valid. This message is not subject to a timer as the MAP_PURGE_MS.

It is noted that instead of using IMSI, also MSISDN may be used to couple to the location.

In an embodiment, the HLR 54 contains couplings for all mobile terminals 2 that are marked as switched on and connected in the area covered by MSCs of multiple telecommunication networks serviced by different providers. It is noted that the subscription of the mobile terminals 2 can be maintained in an HLR of a different network than the one used to locate the terminals. In an embodiment, the AWS application 9 running on the storing entity 6 comprises an allocation table 62, where the actual coupling between an IMSI and the location is maintained (see Figure 6).

For the operation of a Signaling System 7, SS7, network, the AWS DB's 12 may be mirrored databases, as will be known to the skilled person. The state of the art mirror mechanism uses the Internet Protocol, IP, interface 64 for exchanging updates. Alternatively, a dedicated database (not shown) can be joined with the distributed database mentioned above. An example is a service data point, SDP.

Now a more detailed description will be given of the routines involved in maintaining the IMSI-location coupling.

In principle any message containing location information of a terminal as well as a IMSI and/or a MSISDN that is received by an STP 6 which can be used for maintaining the coupling in a database 12. Some MAP messages most suited for this purpose will now be discussed. A suitable moment to start a coupling is when a mobile terminal 2 moves into a new coverage area of the network or switches on inside the network. In those cases, as discussed above, an MSC 52 related to the (part of the) network coverage area in question will issue a MAP_LOCATION_UPDATE message 58 towards the HLR 54, indicating that the MSC 52 needs to be addressed for setting up a call towards the mobile terminal 2. The

MAP_LOCATION_UPDATE message 58 comprises both the IMSI and the locations of the terminal 2. The message travels, on its route to the HLR 54, through one of the STPs 6 of the SS7 network. Upon receipt of the message 58 by the STP 6 a new entry is stored in the allocation table 62 containing the IMEI and IMSI values as retrieved from the message 58.

In the foregoing specification, the invention has been described with reference to specific examples of embodiments of the invention. It will, however, be evident that various modifications and changes may be made therein, without departing from the essence of the invention.

It will be appreciated that the collector 8, event detector 9, storing unit 10 processing unit 11, location determination unit 13, transmitter 14, location comparator 15, receiver 18, processing unit 20, retrieving unit 22, transmitter 24, processor 25, recorder 27, receiver 28, transmitter 29 and/or storing unit 30 can be embodied as dedicated electronic circuits, possibly including software code portions. The collector 8, event detector 9, storing unit 10 processing unit 11, location determination unit 13, transmitter 14, location comparator 15, receiver 18, processing unit 20, retrieving unit 22, transmitter 24, processor 25, recorder 27, receiver 28, transmitter 29 and/or storing unit 30 can also be embodied as software code portions executed on, and e.g. stored in a memory of, a programmable apparatus such as a computer.

In the example of Figure 1, the location comparator 15 is associated with the database 12. It is also possible that the location comparator is associated with, or included in, the network entity 16.

In the example, the position of the terminals is requested by means of an active location request using a MAP- ATI message. It will be appreciated that the position of the terminal can also be determined by other methods, e.g. by using information from a Global Positioning System, GPS, device of the terminal.

However, other modifications, variations, and alternatives are also possible. The specifications, drawings and examples are, accordingly, to be regarded in an illustrative sense rather than in a restrictive sense.

Generally, the invention provides an automatic method and network that stores information of communication devices that are within a predetermined range of a location of an event, such as an emergency, and makes this information available. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word 'comprising' does not exclude the presence of other features or steps than those listed in a claim. Furthermore, the words 'a' and 'an' shall not be construed as limited to 'only one', but instead are used to mean 'at least one', and do not exclude a plurality. The mere fact that certain measures are recited in mutually different claims does not indicate that a combination of these measures cannot be used to an advantage.

Claims

Claims

1. Method for providing information of communication devices (2) having a location within a predetermined range of a location of an event to a receiving entity (26), including the steps of:

determining (104), for each device (2) of at least a group of devices within a plurality of devices, device information, including a device identification code and location information, associated with that device ;

receiving (101), from a triggering device (4), an event message including information associated with the location of the event;

determining (102), on the basis of the location of the event, a location area associated with the location of the event;

determining (106, 108, 110, 112, 114) for each device of the group of devices whether the location of that device is within the location area;

retrieving (105) device information of devices (2) of the group of devices having location information indicating a location of that device within the location area; and

transmitting (116) the retrieved device information to the receiving entity (26).

2. Method according to claim 1, wherein the step of determining the device information (104) includes extracting the device identification code and location information from a message transmitted by a device (2) of the group of devices.

3. Method according to any one of the preceding claims, wherein the step of determining whether the location of the device is within the location area includes determining (108) whether the location information associated with that device stored in the database (12) corresponds with the location area, and

if the stored location information corresponds with the location area, requesting (112) an actual location of the device (2) and determining (114) whether the actual location is within the location area.

4. Method according to any one of the preceding claims, including the step of updating in the database (12) location information of at least one device (2) of at least the group of devices.

5. Method according to any one of the preceding claims, wherein the event is an alarm situation, and the receiving entity (26) is associated with a public service and/or an emergency service.

6. Method according to any one of the preceding claims, wherein the step of storing in the database (12) includes:

storing (104), by a group of two or more storing units (6), device information in a single database.

7. Method according to any one of the preceding claims, further including transmitting (120) a message related to the event to one or more devices (2) of the group of devices having location information indicating a location of that device within the location area.

8. Network entity (16) including:

a receiver (18) arranged for receiving, from a triggering device (4), an event message including information associated with a location of the event; a processing unit (20) arranged for determining, on the basis of the location of the event, a location area associated with the location of the event;

a retrieval unit (22) arranged for retrieving device information of devices of the group of devices having location information indicating a location of that device within the location area; and

a transmitter (24) arranged for transmitting the retrieved device information to a receiving entity (26).

9. Network entity (16) according to claim 8, further including a location comparator (15) arranged for determining for each device of the group of devices whether the location of that device is within the location area.

10. Network entity (16) according to claim 9, wherein the location comparator (15) is arranged for determining whether the location

information associated with the device stored in the database (12)

corresponds with the location area, and

if the stored location information corresponds with the location area, requesting an actual location of the device (2) and determining whether the actual location is within the location area.

11. Triggering device (4) including a detector (9) for detecting an event, a location determination unit (13) arranged for determining a location of the event, a processing unit (11) arranged for generating an event message including information associated with the location of the event, and a transmitter (14) arranged for transmitting the event message to a network entity.

12. Storing entity (6) including: a collector (8) arranged for collecting for each device (2) of at least a group of devices within a plurality of devices device information including a device identification code and location information; and

a storing unit (10) arranged for storing the device information in a database (12) associated with the storing entity (6).

13. Communications device including

a processor (25) arranged for generating device information, including a device identification code and location information, associated with that device,

a recording unit (27) arranged for recording additional information, such as photographic, audio or video information, in response to an invitation to record said additional information, and

a transmitter (29) arranged for transmitting said device information including the additional information.

14. Telecommunications network (1) including:

a triggering device according to claim 11

a network entity (16) according to claim 9, 10 or 11,

- a database storing (12) for each device (2) of at least a group of devices within a plurality of devices device information including a device identification code and location information, and

a receiving entity (26) arranged for receiving the retrieved device information from the network entity.

15. Telecommunications network (1) according to claim 14, further including one or more storing entities (6) according to claim 12, and optionally one or more communications devices according to claim 13.