Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
  • G06Q50/10—Services
  • G06Q50/26—Government or public services
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/10—Office automation; Time management

Definitions

• the invention relates to a system for exchanging information between different users and different authorities.
• the scope of the invention relates to the exchange of information between users and different authorities, for example between citizens and local authorities allowing citizens to report events occurring in their communities ("a Event "), and communities to issue alerts to citizens in a relevant geographic area, related to
• the driver assistance systems allow users to declare events, such as the occurrence of a traffic accident or a slowdown, via a network. navigation device or an application downloaded to their Smartphone, so that this Event is reported to users in the area where the Event occurred.
• events such as the occurrence of a traffic accident or a slowdown
• a network. navigation device or an application downloaded to their Smartphone so that this Event is reported to users in the area where the Event occurred.
• this system actually allows the declaration of the annoying event or a problem, it does not allow the resolution, the events declared by users. remaining to the sole knowledge of those users who are not yet able to provide a solution to the inconvenience caused by the Event.
• the invention aims to solve the problems mentioned above by allowing a bilateral exchange of information between on the one hand different users of the system and on the other hand different authorities, which will cooperate to provide virtually real-time information on a particular fact, and allow a treatment of this fact by the competent authorities, either by solving the problem caused by this fact or by disseminating to the largest number of users information on this fact.
• the invention relates to a technical solution and software for reporting an event by means of mobile or fixed terminals, processing these events by means of business portals by authorities and dissemination of alerts from these business portals. with these mobile or fixed terminals at the scale of a territory from a clean site (industrial site, building) to the national territory of a country or state.
• the present invention relates to a system for exchanging information between different users registered in the system and different authorities associated with geographical areas such as local authorities, including:
• the system further comprising:
• the geolocation means of the users' terminals are formed of GPS points provided by a device internal to the terminal or by GPS points provided by triangulation of cellular antennas (BTS), or are determined by attachment to a code previously deployed and parameterized in a particular spatial zone and recorded by the user on his terminal during a need for geolocation ("tags" in an uncovered area, inside buildings or buried environments), or are defined by selection by the user of a point on a map displayed in the signaling interface of his terminal,
• BTS triangulation of cellular antennas
• the system comprises means for automatically triggering transmission to the platform of the current geolocation location of a user's terminal,
• the automatic triggering of the transmission to the platform of the current geolocation location of a user's terminal is periodically carried out with a period corresponding to a predefined information feedback time
• the information feedback time is adapted according to a load level of the user's terminal, the rise time being all the more important that the load is low,
• a user's terminal interface includes a list of event types that may be reported based on the current location of the user geolocation of the terminal (according to the processing capacity of the authority covering the territory and its proposals),
• the platform comprises means for identifying a secondary event signaled by a user, that is to say an event identified as similar to an event already reported and stored in the platform,
• the identification of a Secondary Event is made by comparing parameters specific to an Event already reported and stored and including geolocation and time of the Event, to parameters defined by an authority and including a perimeter around an Event, a period of time around the occurrence of an Event and an indication of a relative spatial orientation between the user's terminal and the Event, a new Event being identified as secondary to the Event; an Event already reported and stored, if it occurs within the perimeter, the period of time and the direction defined by the authority
• the platform is able to link, according to the various rules raised, one Event to another and thus perform a de-duplication of all events received.
• the indication on the relative spatial orientation between the user's terminal and the Event takes the form of a compass appearing on the image or video explicitly (marking) or implicitly (internal data),
• the platform includes means to ignore a Secondary Event by not storing it
• the system comprises means for requesting a user who has signaled an Event, or any user found in a predefined geographical area around the reported Event, additional information about the Event, such as images or confirmation that the Event continues,
• the system comprises means for transmitting the signaling of an event generated by a user to other users located in a predefined geographical area around the reported event.
• the means for transmitting the signaling of an event generated by a user to other users are managed by the terminals of the authorities
• the signaling of an Event by a user can be realized following a voluntary action of the user or automatically ie without any action on his part.
• This last case concerns facts, such as a shock suffered by a user in his vehicle, likely to generate information interpretable by the platform, in this case in the example considered, a discontinuity in the data provided by an accelerometer content in the user terminal disposed in the vehicle.
• the automatic transmission of such an event can be set beforehand by the user who will choose the type of fact that can be automatically reported as an Event to the platform, without any specific action on his part,
• the terminals of the users are mobile or fixed terminals.
• the invention also relates to a method of exchanging information between different users registered in an information exchange system and different authorities associated with geographical areas such as territorial communities, comprising:
• each terminal comprising a current geolocation means of the terminal, a "signaling" interface enabling the user to signal a geolocated event within a authority, and means of transmission to the platform that stores them, the current location of geolocation of the terminal and the reported event,
• the method further comprising:
• the method further comprises a step of transmitting the events stored in the platform to each service of an authority or each user having chosen, by explicit membership to automatically receive information on certain events according to their nature.
• FIG. 1 schematically represents the operation of the system according to the invention for the processing of events reported by a user
• FIG. 2 schematically represents the operation of the system according to the invention for the communication of Alerts issued by an authority, for the attention of users subscribing to this authority.
• FIG. 3 schematically illustrates the entire information exchange process
• FIGS. 4 to 6 schematically represent the process of identifying a primary event and a secondary event
• FIGS. 7 to 9 schematically illustrate the identification of citizens present in a broadcast zone of an Alert
• Figures 10 and 1 1 show a diagram illustrating the display of event mapping on the consumer area of the website of the system according to the invention.
• This system provides mainly two types of information exchange, which can interact with each other:
• Users access the information exchange method according to the invention either via a free application previously downloaded to their smart mobile phone, or via a portal-type web application, local authorities via a website and the Global administrator also via a website.
• the Administrators of the service "the Administrator” represented by persons in charge of the management of the system of exchange of information between the different users and the different authorities object of the invention.
• An equipment corresponds to a mobile terminal on which is installed the application or a fixed terminal having access to the website dedicated to this application.
• the equipment will be identified as such and linked to a Citizen.
• the Citizen will be able to associate as many equipments as he wishes.
• the Event must be geolocated:
• the Event is automatically geolocated by one or both of the following methods:
• the "QRCode” is a tag supporting a known TAG of the system according to the invention: Each "QRCode” corresponds to a geographical position (real map point or a position on a plane for example). The "QRCode” is previously deployed and configured. (Principle of geolocation on "indoor” type sites: buildings, industrial sites, etc.).
• the "QRCode” is a label supporting a known TAG Alert-Phone service: Each "QRCode” corresponds to a geographical position (real map point or a position on a plane for example).
• the location is defined by the pair of values:
• the diagram illustrated in Figure 1 generally shows the state changes associated with an event.
• the Event object has many properties:
• a severity rate (from 1 to 5)
• the event object is attached to a level in the tree.
• a category (level 1 of the nomenclature).
• a type of event and sub type (function of the number of level).
• This text information, entered by the citizen is optional.
• the citizen can associate for example from 0 to 3 photos.
• Size of the images in order not to penalize the loading time of the files (from mobile equipment to the server), the size of the files must be modified before sending.
• the chosen resolution is: 800 * 450 with a weight between 50 and 100 KB.
• Each of the associated photos has a property:
• o NULL no associated information. (For example, if the user selects existing photos, or uses the website form).
• This information is available and will be displayed to the authority operator in the tab that shows the photos of the event.
• the citizen will be able to associate from 0 to 3 videos.
• OPEN This is the default status: the event is created in the system, but the de-doubling algorithm did not specify the type of the event.
• TAKEN INTO ACCOUNT The user of the authority indicates that the event is taken into account, and therefore being processed.
• PROCESS The event is processed, the authority user indicates the change of state.
• This function is to not overload the Operator when processing events, by the multiple storage of similar or identical information relating to a single event.
• the Primary Event is the first declaration by a Citizen of an Event for a given type. This must be processed by the Operator and will follow a status change process as shown in the diagram in Figure 1.
• the Secondary Event is the same Event (same type) as the primary event, but it was subsequently declared. In this case, this Event is attached to the Primary Event and will not be processed by the Operator. This Secondary Event will follow the status of the Primary Event. The Operator may access the information of the Secondary Events at his request in order to obtain, for example, additional information about the Event.
• the Primary Event will be all the more important as there will be Secondary Events that will relate to it.
• (C) Orientation (when taking the picture or video).
• the Administrator Operator can implicitly and simply change the values (A) and (B) by type of Event.
• Data (C) is used by the system to separate residual ambiguities. Other data may be used to separate the latter such as a degree of urgency provided by the Citizen.
• the Event is of "Secondary" class and will be attached to the Primary Event.
• the orientation when taking a photo or video, will in certain cases make it possible to detect whether secondary events are duplicates of the primary event, or if a doubt remains.
• the Event may be presented as primary.
• the 2nd Event (point near the edge of the circle) will be defined as "secondary" because the orientation recorded when shooting is compatible with that of the primary event.
• the system according to the invention thus provides the Operator with the means for setting the de-doubling function.
• the system further includes an algorithm for grouping Events occurring after a Primary Event and outside the ranges of parameter values expected to qualify a Secondary Event, and assigning them to the Primary Event.
• this algorithm uses in addition to the initial parameters defined to qualify a secondary event (geographical perimeter A and period B according to the preceding example), a weighting for each of these parameters, for example between 1 and 10 and allowing assign a score to assess for the parameter considered the probability that it is really secondary (the score "1" representing a very low probability, for example, an event occurring more than 100 m from an Event of the same type, and the score of "10", a very important probability, this score of 10 being reserved for Events occurring within the tolerance provided for qualifying a Secondary Event).
• the score assigned to the geographical parameter A will be relatively high (for example 9/10) and that attributed to the parameter time B, also high (for example 9/10 also) as the probabilities are large that this event located certainly outside the perimeter and of the period defined to be identified as secondary, which is actually a Secondary Event of the previously reported Event.
• a mathematical algorithm can be provided for assigning a weighting to each parameter making it possible to qualify a secondary event as a function of the difference observed for an event of the same category as a previous event, between the parameter recorded for the event considered, and the beach of values set for this parameter to qualify a Secondary Event. It may be possible to calculate an average of the scores awarded for all the qualification parameters of a Secondary Event.
• An example of the algorithm for calculating such a grouping note is given below:
• Each of these scores will then be weighted to calculate a final score between 0 and 100.
• Step 1 Find out if there are any potential "Primary" events:
• the Administrator of Authority will be able to define his own thresholds, and thus choose his mode of management for his authority:
• the assignment of a secondary type is automatic if the final score is greater than or equal to a threshold value (for example 70/100)
• the event is automatically identified as primary, greater than a second threshold value (for example 70/100), it is automatically identified as secondary, and when it falls within the range defined by these two threshold values (in this case between 65/100 and 70/100), a validation is requested from the Authority's operator who identifies by his / her assessment event as primary or secondary by clicking on a corresponding active area of the screen of its terminal,
• a first threshold value for example 65/100
• a second threshold value for example 70/100
• a primary event can be linked to 0 or more events secondary.
• o Information is kept about whether an operator changes the type of this event.
• This feature allows for a particular event, to send on identified equipment (user terminals for example) a request for additional information.
• the Administrator defines a department for which he wishes to reach the equipment.
• the system tells him the number of devices that are potentially in the zone.
• STEP 1 SEARCH FOR "POTENTIAL PRIMARY EVENTS" For an event declaration, one searches in the database if there exists a list of events of the type "Primary" having as characteristics:
• Result of the query is empty: Result of the query not empty:
• Warning if a result exists, it must be unique. In the opposite case, there is an inconsistency in the data: the Administrator must be informed immediately (email).
• the Authority Administrator will provide values to define the reliability of Geolocation based on the type.
• the note will be fixed at 100. ⁇ and possibly, a note on the orientation of the shots (photos).
• the Primary event must have photos and values regarding the orientation of these photos.
• the event to be classified must also have photos and associated values on the orientation.
• the implicit reliability rate therefore corresponds to the average of the 2 notes previously described: Orient tilote. Photo + '' Liver Geoksc type
• the administrator of the authority defines coefficients for each of its 2 rates: Then we calculate the final score according to these 2 values:
• a representation of this delay will be displayed on the Authority's terminal with the time remaining, or conversely, the time passed after the delay.
• this Event may appear with a color depending on the severity assigned to it, with a visual signal (flashing event display) or sound (alarm).
• a computer object will declare an event to a national security service such as National police, Samu, Fire Department, or City-type Municipal police Station. Citizen at the origin of the declaration
• a citizen can use several equipment.
• An event is created by a citizen, from:
• a history of events reported by each user allows to know for each its seniority, the number of reports of events that have been confirmed by other users, the nature of the events reported (dangerousness) ...
• a user is assigned a degree of confidence, or points of credibility for example calculated by an algorithm, and noted from 1 to 10.
• a global setting by authority will define the number of points for a declared event of type Primary and Secondary type.
• the user of the entity can, on a case-by-case basis, add or remove points to the event.
• This degree of confidence may be taken into account in the calculation of the severity of a reported Event (see above) and thus to assess the priority of the reported Event.
• This degree of confidence, or these points of credibility may allow the issuance of rewards, such as gift vouchers, in connection with the Authority to which the User is subscribed (for example, a reduction on the amount of the annual subscription at the municipal swimming pool).
• the reward may take the form of a benefit attributed to a third party (for example a check to the attention of an association of the municipality) and not to the user himself.
• a third party for example a check to the attention of an association of the municipality
• a User proves detrimental to the proper functioning of the service, according to for example the far-fetched nature of the Events or the content of the messages it associates with these events (racist, pornographic, contrary to public order.)
• a message may be issued by an Authority to invite it to improve the quality of its reports. Otherwise, this User may be banned from the community.
• Registering an identifier for the user's banned terminal will prevent him from creating another account on the same terminal after being banned.
• a computer recognition tool may be provided to analyze the image captures or videos accompanying the report of an Event and delete those representing an individual in a manner allowing its identification. A message may be sent to the user reminding him that no data of this type is accepted by the service.
• An alternative will be the use of a computer tool to scramble any identified face on an image capture or video.
• Each Event is recorded locally on the User's terminal, and when the User is able to communicate with the server, also on that server.
• the synchronization of events to report and stored on the user's terminal, and Alerts stored on the server and to be transmitted to the user's terminal is done as soon as the terminal is connected to a network.
• the application downloaded to the terminal may allow the sending of a notification when a network absence is detected with the geolocation of the loss of the network, to warn an Authority of the presence in its perimeter of a zone d the absence of a network, or the occurrence of a network problem, which problem may be transmitted to the competent department of the Authority, or to a service external to it, such as the service of a national network provider.
• the events reported are grouped by sub-group according to the services of the Authority and communicated automatically to the service in question.
• the terminal of a User communicates at a given frequency its geolocation to the server (for example every 15 minutes) and receives the Alerts from the Authority concerned, as long as the last position of geolocation is within the perimeter of the Authority considered.
• a history of Events reported in the perimeter of an Authority will make it possible to propose to a User wishing to report a new Event in the Authority concerned, to be offered, in the interface for entering a new Event, a list of the different Event already reported.
• the citizen can modify or delete certain information associated with the event.
• the Citizen can:
• this event will always appear in the table events, but it will be represented with a peculiarity (specific color of the line for example) so that the user immediately identifies that the Citizen to delete this event.
• the authority user will have the choice to process this event or close it if it is no longer relevant.
• the Global Administrator is dedicated to the management of different authorities and different users. It has a terminal with a management interface of these authorities.
• This interface allows access to the interface of each Authority and to intervene as the Authority itself, and create a new account for a new Authority.
• This interface also allows the visualization of different maps of different authorities on which the events reported are marked by sign, clickable to know the details of the event considered.
• This interface is linked to a source of information on the cadastres of the various cities or townships of a territory, updated regularly, and allows, when a new Authority wants to subscribe to the service, to delimit automatically from the code postal of the city or township, of a perimeter on a map.
• a city wants to subscribe it informs the different Events that it authorizes a User to declare, informs the identifiers for the different services that can handle these Events, and email addresses or links to them to push them Events reported, as well as the various system parameters (grouping parameters, degree of confidence).
• This interface allows not only the introduction of a new Authority in the system but also that of an external information system, such as a government information system (for example: National police for Abduction Alerts).
• an external information system such as a government information system (for example: National police for Abduction Alerts).
• the Alert is necessarily associated with a geographical perimeter and disseminated to citizens present in this area.
• the geographical scope of broadcast of the alert is independent of the current location of the terminal of the Authority through which are issued Alerts.
• the Alert is distributed only to citizens present in the perimeter defined for the Alert.
• the list of citizens (and therefore their equipment) impacted by the dissemination of an Alert will be calculated by the system through a Geo-Spatial type query that overlay the two geographic information (perimeter of the alert and positions of the different equipment) will deduce the group of citizens to reach.
• the Citizen may choose to subscribe to alerts from one or more Communities. It will receive the corresponding Alerts even if it is not located in the broadcast area of the Alert.
• a system of obtaining points will be set up to make the service attractive and reward the Active Citizen.
• the basic principle is that for any new event declared, the user receives points.
• the latter will have the opportunity to issue a request for additional information to all users who have reported the Event.
• the request for additional information will be based on the function of issuing Alert by selection of citizens who transmitted the event (primary or secondary).
• the provision of additional information may be subject to the gain of points.
• the concept of service corresponds to a compartmentalization necessary for the management of created events.
• the Administrator of the Authority has the ability to report services.
• An Authority has at least one Service. It will therefore be necessary to create a Default Service when the INEO Administrator creates an Authority: it will be the "Authority Authority” Service which will contain at least one user: the Administrator of the Authority.
• a user of the authority belongs to one or more services.
• An event type is associated with one or more services. As a result, a user will see in the different functionalities (management board, on the map, etc.) all the events whose types are associated with the services to which he belongs.
• the Alert-Phone information exchange system and method is a software as a service (SaaS) software solution that includes the following applications:
• ALERT-PHONE-SMART Free client application dedicated to Smartphones (for the Citizen).
• ALERT-PHONE Portal-type WEB application for users of all types.
• ALERT-PHONE-COMMUNITY Web application for communities (configuration, management, information processing and associated services).
• ALERT-PHONE-ADMIN Global Administration WEB application for Service Administrators (depositor's personal).
• ALERT-PHONE-WEBSERVICE Web Methods Interoperability service that will be consumed by external applications.
• the Alert-Phone service is composed at the FrontOffice level of the following interfaces:
• the backoffice is composed of Web Application servers that will support the following components:
• WebServices An interoperability layer (WebServices) that will be used by the FrontOffice of the Alert-Phone Service. This same layer of WebServices can be used by external applications.
• One or more web application servers that will be parallelized according to the overall load (solicitation of the system).
• a database management and file storage system (Photos, Videos).
• the mobile terminal application will allow the Citizen to identify himself by creating a profile, to subscribe to the service, to select cities from which he wishes to receive Alerts, to select the type of Alerts that the Interested (weather alert, traffic accident, school closure ...), to report Events and receive Alerts.
• the Citizen can declare an Event and its associated data: Choice of the type of Event
• the Operator that is to say the community collecting the report, can activate or not the masking when viewing the associated media (or according to rights associated with the Operator)
• the citizen can also delete:
• the Citizen must be declared as a user of the service ⁇ The Citizen must authenticate and declare his equipment to access the features of the application.
• This form can potentially be relatively short (at least shorter than the web portal ALERT-PHONE detailed later). The user can later add other information about his account.
• the registration process requires the user to enter a code received by SMS, in order to validate the creation and activation of the account.
• a citizen can have several phones or tablets. In this case, a form allows him to declare several pieces of equipment. It will therefore be recognized as a single citizen regardless of the mobile terminal used.
• connection is required to access the features of the service after filling the login form.
• the disconnection of the user is done through the form disconnection which, once validated, will no longer allow it to access the features.
• the application is personalized (Logo, name of the community, graphic charter, etc.).
• the application notifies that situation, and the home page will be a default page. In this case, it may be provided an action button that will ask the Citizen to send a message to the municipality: "Do you want to notify the municipality of the existence of the Alert-Phone service? "
• the feedback of this information will be between 1 minute and 1 hour.
• Local processing (a function of the ALERT-PHONE-SMART application) consumes energy. This should not be done at the expense of using the equipment itself by the Citizen.
• the application ALERT-PHONE-SMART automatically adapt the sending period of the position of the equipment to not solicit the battery in this context.
• the feedback of the position information is automatically activated on a short cycle (every 5 minutes for example).
• the main function is that the user goes back Events. A whole list of Events (depending on the services available and set by the community) will be presented.
• Alpha information text, type, date, etc.
• the community may ask the users for additional information.
• a user at the initiative of a "Secondary" Event may also be awarded points if the information provided (photo, video) is relevant.
• the Citizen may "subscribe” to receive the Alerts and address Events of one or more community (s) adherent (s) to the service of the invention.
• This feature is transparent to the Citizen, in the sense that he will receive Alerts from the Alert-Phone Service generated by the community in which he is currently located.
• the Citizen is in the dissemination perimeter of the Alert • Not mandatory, the Citizen has validated in his preferences, the desire to receive Alerts of this type.
• the Citizen consults the active Alerts in the area where it is located.
• This event sends the geolocation of the person for a more accurate identification of the situation.
• VEHICLE mode allowing the Citizen to activate the automatic return of SOS if a shock is identified by the terminal. In this mode, the Citizen participates in the generation of traffic data. In mode “VEHICLE”, the emission of "SOS” can be triggered automatically without action of the Citizen for example in case of shock of a user in the vehicle. The purpose is to send as soon as possible an Event to alert the competent services (Firefighter,
• this function exploits the accelerometer data provided by a device internal to the terminal in order to transmit the event. Thanks to the countdown available when issuing an "SOS", the Citizen can cancel a false alarm before it is actually issued.
• the terminal moves at a speed greater than a threshold (30 km / h for example), the terminal is automatically identified in "VEHICLE” mode to consolidate traffic data.
• a threshold (30 km / h for example)
• the terminal is automatically identified in "VEHICLE” mode to consolidate traffic data.
• the platform identifies terminals on predefined motorway areas (highways for example), the terminals are implicitly switched to "VEHICLE” mode.
• the speed of movement of a Citizen is determined by internal equipment terminal or calculation from the platform according to geolocation points, the timestamp of these points and the urban topology of the place.
• the traffic data and the damage thus collected on the roadways can be used by the Collect Supreme and / or the competent services to remedy situations and to inform the citizens.
• the application available on the website will include the features described above for the application for mobile phone, and will present the overall process.
• the homepage is therefore global (there is no differentiation at this stage of local authorities who join the service, and the general public).
• the first page may contain, for example:
• links will display specific pages (in terms of presentation and informative content) to each community and associated services.
• the pages associated with the communities may be presented according to:
• This function gathers all the Alerts issued by the communities to which the user adheres. The user can access all the Alerts issued.
• a "community" could be of national type and thus spread the Alerts that impact the national territory.
• a community that broadcasts an alert on its territory could also broadcast on adjacent territories if the risk comes out of its own original territory. In this case, even if the user has not explicitly joined the community, he still receives the Alert.
• This function allows the user to select the communities members of the Service, for which he wishes to receive Alerts or issue Events. The choice will be made only among the communities that subscribe to the Alert-Phone Service. In the case of a dynamic membership from his smartphone, the community will find the list of memberships.
• the user visualizes on the map his own Events. It can therefore access it by direct selection on the map.
• the site must highlight the dynamic side and real-time acquisition of the service (number of events reported per day, per week, number of events treated by the communities, satisfaction index, etc.) and the importance of the adherent community (users and collectivists). It proposes indicators for the general public and operators.
• This form allows a community to join the Alert-Phone Service. As a first step, this form may not exist, but would allow the community to contact the Administrator to finalize the contractual part. The addition of a new community and its setting will be done in the application ALERT-PHONE-ADMIN.
• the communities in turn access the system according to the invention via a web application for configuration, management, processing of information and associated services.
• the website of the system according to the invention thus has "private" pages accessible only to the declared citizens, as well as to the users of the communities and of two different types:
• the "community” application has two main goals:
• the system according to the invention proposes by default a library of type of Events to the community, and the Operator (by simple configuration) will select among these types of Events, those he wishes to collect a report, and who will appear in the list available on the Citizen's mobile phone or the Citizen interface of the website.
• the community in charge of this Event accesses all the information of this Event declared by the user.
• the Operator will also be able to enrich this library with its own Alert types. All these types of Alerts will be proposed to the community, and the Operator can create an Alert (dissemination of the Alert to the Citizen) from this library.
• Activation period start date, end date.
• the end date is optional, which means the Alert is Active with no time limit. In this case, the Operator will have to "manually" deactivate the Alert when it is finished.
• the area concerned by the Alert will correspond to the surface of the community concerned. Then the Operator, if he wishes, can define (digitize) himself a more precise geographical area that corresponds to the actual area of the Alert (the impact zone).
• Another "climbing management” feature will allow it to broadcast this Alert on territories adjacent to its own territory.
• a workflow will allow each Operator of the concerned territories to validate the diffusion of this Alert.
• This function allows a community to define geographically the perimeter in which:
• digitalization tools will allow other types of authorities or authorities to graphically define their own geographical area in which their Alert-Phone Service will be operational.
• Definition of Workflow in the management of the taking into account of a fact definition of the states and the associated actors for each of the states.
• the Operator will pay the Events that are intended for him and process them. This acquittal is important because it will be reported to the Citizen who declared the Event.
• the Operator has the ability to define his own types of Preformatted Alert. For example, for a specific type of Alert, the list of setpoints would already be defined.
• the application Alerts system allows interoperability with external systems such as a centralized state service, or a private service (eg a territory-wide weather information service, which may provide an Authority with meteorological information concerning its perimeter.
• external systems such as a centralized state service, or a private service (eg a territory-wide weather information service, which may provide an Authority with meteorological information concerning its perimeter.
• An alert issued from an external source will be declared in the system via WebServices made available by the solution. This Alert can then be disseminated by notification to all citizens with the application.
• the operator visualizes in the Backoffice application the External Alerts, then, it validates if necessary Alerts that will be reflected in the solution according to the invention through the platform.
• the alert will be automatically associated with an authority, it is issued for the authority's perimeter (in our example, this corresponds to the outline of the municipality).
• the notification form of an Alert allows you to enter or modify all the information relating to an Alert.
• the operator can himself define a specific area for the alert, whether issued by the Authority on which it depends, or by an external service.
• a digitized area on the map rectangle, circle, polygon.
• the operator can therefore define temporary zones or that will be saved in the system. These zones will have at least one name, which will allow you to select it when the operator creates the Alert. These zone names can be "sorted” or categorized into a functional tree.
• a function will create an alert zone:
• the location of Events attached to the community is displayed on a map.
• Event Status (To be processed, processed, etc.).
• This database will allow the creation and display of reports, indicators on the use of the Alert-Phone Service.

Landscapes

• Business, Economics & Management (AREA)
• Engineering & Computer Science (AREA)
• Tourism & Hospitality (AREA)
• Human Resources & Organizations (AREA)
• Strategic Management (AREA)
• General Business, Economics & Management (AREA)
• Entrepreneurship & Innovation (AREA)
• Theoretical Computer Science (AREA)
• Economics (AREA)
• Marketing (AREA)
• General Physics & Mathematics (AREA)
• Physics & Mathematics (AREA)
• General Health & Medical Sciences (AREA)
• Primary Health Care (AREA)
• Health & Medical Sciences (AREA)
• Educational Administration (AREA)
• Data Mining & Analysis (AREA)
• Development Economics (AREA)
• Operations Research (AREA)
• Quality & Reliability (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Telephonic Communication Services (AREA)
• Alarm Systems (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=50424352

Family Applications (1)

Country Status (4)

Family Cites Families (3)

• 2013
  • 2013-10-18 FR FR1360196A patent/FR3012240B1/fr not_active Expired - Fee Related
• 2014
  • 2014-10-20 WO PCT/FR2014/052661 patent/WO2015055970A1/fr active Application Filing
  • 2014-10-20 EP EP14798919.8A patent/EP3058543A1/de not_active Withdrawn
  • 2014-10-20 MA MA38979A patent/MA38979A1/fr unknown

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events