Method and apparatus for providing activity-based map job

An approach is provided for validating crowd-sourced information. The approach includes processing and/or facilitating a processing of map error data to generate at least one map job and at least one activity context associated with the at least one map job, the map error data, or a combination thereof. The approach also includes determining one or more devices based, at least in part, on the at least one activity context. Further, the approach includes causing, at least in part, a transmission of the at least one map job to the one or more devices for resolving one or more map errors indicated in the at least one map job, the map error data, or a combination thereof.

BACKGROUND

Service providers and device manufacturers (e.g., wireless, cellular, etc.) are continually challenged to deliver value and convenience to consumers by, for example, providing compelling network services, such as, offering navigation and map services via various user devices. For example, a user may utilize a mobile device or a navigation system in an automobile to search for or access location-based services, navigation information, information about a point of interest (POI), or the like. However, to provide accurate and useful information or services, the maps or navigation systems have to be continuously updated to reflect any changes in the information utilized therein. For example, a map database may be updated to reflect development a new road, a new POI, changes to an existing service center, or the like. In addition to updating and verifying possible changes to information in a map database, some of the information may be erroneous or incomplete and would need to be corrected, completed, and verified. For example, information for a certain POI in a map database may include a physical address, phone number, Internet address, related media items, etc., wherein one or more of the information items may be erroneous or incomplete. However, it is a challenging and resource intensive task for the service or content providers to assure a substantially updated and error free map database. Accordingly, service providers and device manufacturers are challenged to develop new mechanisms to effectively and efficiently validate crowd-sourced information.

SOME EXAMPLE EMBODIMENTS

Therefore, there is a need for an approach for validating crowd-sourced information.

According to one embodiment, a method comprises processing and/or facilitating a processing of map error data to generate at least one map job and at least one activity context associated with the at least one map job, the map error data, or a combination thereof. The method also comprises determining one or more devices based, at least in part, on the at least one activity context. Further, the method comprises causing, at least in part, a transmission of the at least one map job to the one or more devices for resolving one or more map errors indicated in the at least one map job, the map error data, or a combination thereof.

According to another embodiment, an apparatus comprises at least one processor, and at least one memory including computer program code for one or more computer programs, the at least one memory and the computer program code configured to, with the at least one processor, cause, at least in part, the apparatus to process and/or facilitate a processing of map error data to generate at least one map job and at least one activity context associated with the at least one map job, the map error data, or a combination thereof. The apparatus is also caused to determine one or more devices based, at least in part, on the at least one activity context. Further, the apparatus is caused to cause, at least in part, a transmission of the at least one map job to the one or more devices for resolving one or more map errors indicated in the at least one map job, the map error data, or a combination thereof.

According to another embodiment, a computer-readable storage medium carries one or more sequences of one or more instructions which, when executed by one or more processors, cause, at least in part, an apparatus to process and/or facilitate a processing of map error data to generate at least one map job and at least one activity context associated with the at least one map job, the map error data, or a combination thereof. The apparatus is also caused to determine one or more devices based, at least in part, on the at least one activity context. Further, the apparatus is caused to cause, at least in part, a transmission of the at least one map job to the one or more devices for resolving one or more map errors indicated in the at least one map job, the map error data, or a combination thereof.

According to another embodiment, an apparatus comprises means for processing and/or facilitating a processing of map error data to generate at least one map job and at least one activity context associated with the at least one map job, the map error data, or a combination thereof. The apparatus also comprises means for determining one or more devices based, at least in part, on the at least one activity context. Further, the apparatus comprises means for causing, at least in part, a transmission of the at least one map job to the one or more devices for resolving one or more map errors indicated in the at least one map job, the map error data, or a combination thereof.

For various example embodiments, the following is applicable: An apparatus comprising means for performing the method of any of originally filed claims.

DESCRIPTION OF SOME EMBODIMENTS

FIG. 1is a diagram of a system capable of validating crowd-sourced information, according to one embodiment. As discussed above, data utilized by any of a number of navigation tools and map applications are often out of date or contain incomplete data, and updating such data may prove cumbersome with less than reliable results. Some traditional approaches have allowed users to report updates to the data, for example into a map database, where the reported data may be shared with other users or user communities. In some cases, such updates may not be accurate or reliable and may conflict with updates/reports provided by other users. Further, the accuracy of such data updates is dependent upon the reliability of a reporting source. However, service or content providers receiving or maintaining a database that includes crowd-sourced data may not be able to validate the crowd-sourced data in a timely and effective manner.

To address this problem, a system100ofFIG. 1introduces the capability for validating crowd-sourced information (e.g., location or POI data) across a variety of use cases and applications by maximizing data offerings by reliable sources and minimizing errant data updates. The system100introduces an approach for integrated validation of crowd-sourced data updates by managing the processes for aggregating data error reports received from users or service providers, creating one or more data update tasks (map jobs) that users or a service providers may perform, mechanisms for validating data updates that may be reported by various users or service providers, updating the database with validated data, and communicate update status and related information to users or service providers.

In one embodiment, an aggregator may receive and aggregate feedback, e.g., reports of various types of data errors, that can originate from users or user devices that participate in providing the feedback. In one scenario, an error report may be for an erroneous information item or a missing information item that is associated with an instance of data in a database. For example, the data error may be associated with a data entry for a certain location in a map or a POI in the database. In one scenario, a user device may utilize an application programming interface (API) (e.g., a map-feedback API (MFAPI)) to interface with the aggregator (e.g., in a platform). As noted, a data error may be reported by a user device or by an internal database rule that can trigger a report of a data error. For example, the error reports may include a report of a missing Internet link error associated with a POI, a request to verify certain data in the same area as the POI, an error report for location information of another POI in the same area, or the like. In one embodiment, the aggregator may use a map job (MJ) creation flow, which may include an analysis of each of a plurality of error reports and substantially automatically grouping the reports into one or more MJs. In various scenarios, the grouping of the errors may be based on an error type, geo-location associated with the error, reporting user or user device, validation threshold rating, priority, or the like. In one embodiment, for a given MJ, a validation threshold may be based on a number of agreeing submissions (votes) per user type that may render a MJ as being resolved. In one embodiment, a MJ with its common attributes and a validation threshold may be packaged and submitted for distribution, consideration, and resolution.

In one embodiment, at least one element of the system100, e.g., a distribution logic may create a list/queue of one or more MJs that can be distributed to users or service providers for consideration or completion. For example, the MJs may be distributed to navigation devices (e.g., personal, integrated in an automobile, etc.), mobile devices (e.g., phones, tablets, laptops, etc.), or the like, which may utilize an MFAPI or an application suitable for providing data updates. In one embodiment, an MJ may be associated with a geo-location attribute, wherein the system100may also determine a geo-fence attribute for the MJ. In one scenario, an MJ may indicate that for updating/validating an error in the MJ, a user/user-device is to be at the same geo-location as indicated by the MJ or be within its geo-fence attribute. In one embodiment, an MJ is presented at a user device only when location information of the user device is substantially the same as the geo-location attribute of the MJ or when the user device is located within the geo-fence attribute (e.g., within one mile) of the MJ. In one embodiment, MJs may be distributed (e.g., pushed) to one or more user devices, wherein the MJs may be queued to be resolved. For example, an MJ for a POI phone number error may be distributed to a web portal or a mobile device, which may present a visual user interface prompt on a map application. In this example, the user may interact/resolve the MJ whenever he wishes so (e.g., no requirement for the user to be in the area indicated by the MJ).

In one embodiment, the system100, e.g., a validation/threshold logic may monitor responses to an MJ that may have been received from various users or service providers. Further, the response may be compared to each other in order to determine if they match. For example, five responses to an MJ for a phone number of a certain POI are compared to see if the phone reported phone numbers match. In one scenario, if the number of matching responses meet a validation threshold, then the MJ may be considered resolved. For example, the threshold may require that at least four reported phone numbers are to match in order to qualify as a validated resolution to the associated MJ. Upon a validated resolution of the MJ, the MJ may be tagged as resolved or automatically closed and any related individual error reports may be closed as well. In one embodiment, a notification of a resolution of a reported error may be communicated to one or more users who had reported the error. In one embodiment, one or more users who provided information for resolving a reported error may be awarded with some credit points at one or more user accounts; for example, an account with the entity receiving the error correction, an online social network account, a service/content provider account, or the like. In one example, the amount of awarded points may be based on user history, reliability of reported solutions, user trust level, the type of corrected error, priority of the corrected error, or the like parameters.

As shown inFIG. 1, in one embodiment, the system100includes user equipment (UE)101a-101n(also collectively referred to as UE101and/or UEs101), which may be utilized to execute one or more applications103a-103n(also collectively referred to as applications103) including a map application, social networking, web browser, content sharing, multimedia applications, augmented reality (AR), virtual reality (VR), user interface (UI), web client, etc. In various embodiments, the applications103may be utilized to capture, process, submit, analyze, append, tag, etc. various location information, media items, POI information, or the like.

In one embodiment, a UE101may be configured with a validation manager105a-105n(also collectively referred to as validation manager105) for reporting potential data errors associated with an application or a database (e.g., a map application or database). Additionally, the validation manager may be utilized to receive, request, or to respond to an MJ, for example, by capturing and providing information related to the MJ for validating crowd-sourced information.

In one embodiment, the UEs101may include data/content collection modules107a-107n(also collectively referred to as DC module107) for determining and/or collecting data and/or content associated with the UEs101, one or more users of the UEs101, applications103, validation manager105, one or more information items (e.g., about a location, POI, etc.), or the like. In addition, the UEs101can execute an application103that is a software client for storing, processing, and/or forwarding one or more information items to other components of the system100. In one example, the validation manager105may perform some or all of its tasks in conjunction with the applications103or the DC module107.

Additionally, the applications103may facilitate communication with other UEs101, one or more service providers109a-109n(also collectively referred to as service providers109), one or more content providers111a-111n(also collectively referred to as content providers111), one or more GPS satellites113a-113n(also collectively referred to as GPS satellites113), a validation platform115, or with other components of the system100directly or via a communication network117. In addition or alternatively, the UE101has connectivity to the validation platform115via the communication network117for performing all or a portion of the validation of the crowd-sourced information.

In one embodiment, the service providers109may include and/or have access to one or more service databases119a-119n(also collectively referred to as service database119), which may include various user information, user profiles, user preferences, one or more profiles of one or more user devices (e.g., device configuration, sensors information, etc.), service providers109information, other service providers' information, and the like. In one embodiment, the service providers109may include one or more service providers offering one or more services, for example, online shopping, social networking services (e.g., blogging), content sharing, media upload, media download, media streaming, account management services, or a combination thereof. Further, the service providers109may conduct a search for content items, media items, information, coupons, and the like associated with one or more users, POIs, geo-locations, and the like. In one embodiment, a service provider109may receive and process a request/input from a user for determining status information associated with one or more elements present in one or more media items. In one embodiment, the service provider109may utilize various algorithms, software applications, modules, hardware, firmware, and the like for processing, recognizing, detecting, comparing, and the like, content items (e.g., media items) that may be associated with a user, a user device, or the like.

In one embodiment, the content providers111may include and/or have access to one or more content database121a-121n(also collectively referred to as content database121), which may store, include, and/or have access to various content items. For example, the content providers111may store content items (e.g., at the content database121) provided by various users, various service providers, crowd-sourced content, and the like. Further, the service providers109and/or the content providers111may utilize one or more service application programming interfaces (APIs)/integrated interface, through which communication, media, content, and information (e.g., associated with users, applications, services, content, etc.) may be shared, accessed and/or processed.

In various embodiments, the service providers109and/or the content providers111may include and/or have access to information associated with people, POIs, objects, etc. For example, the information may be available from various public, private, or government controlled databases, which may be accessed via the communication network117.

In one embodiment, the validation platform115may receive and process various information associated with a data error and resolution data for validating crowd-sourced information. The validation platform functions and elements are discussed in relation toFIG. 2.

The system100may also include user context data125. The user context data may include user events, user content items, location-based context data (e.g., time stamps, etc.). For example, the context data contains environment data, weather data, traffic data, event data, commuter data, etc. As an example, the user contextual data of a user interested in technology or gadgets may be associated with electronics stores, wireless hot spots in the city, computer conventions, forums of technologies, science museums, media laboratories, etc. The service providers109may collect, assemble, store, update, and/or supply the context data and user context data. In one embodiment, user context data, for example, user events may be extracted from calendars, emails, voice messages, text messages, blogs, bulletin boards, discussion forums, geographic information systems, and social network websites. In one embodiment, user content items may be used to infer context data and may be retrieved from, for instance, personal photo albums, media libraries, playlists, etc. In one embodiment, a validation platform115processes the context data or user context data of different formats and types including data derived from various forms of communication such as emails, text messages, voice messages, calls, video/audio clips, etc.

The UEs101may be any type of mobile terminal, fixed terminal, or portable terminal including a mobile handset, station, unit, device, personal navigation device, connected built-in or standalone navigation device in a vehicle, web surfing device, healthcare diagnostic and testing devices, product testing devices, multimedia computer, multimedia tablet, Internet node, communicator, desktop computer, laptop computer, notebook computer, netbook computer, tablet computer, personal communication system (PCS) device, personal navigation device, personal digital assistants (PDAs), audio/video player, digital camera/camcorder, positioning device, television receiver, loud speakers, display monitors, radio broadcast receiver, electronic book device, game device, wrist watch, or any combination thereof, including the accessories and peripherals of these devices, or any combination thereof. It is also contemplated that the UEs can support any type of interface to the user (such as “wearable” circuitry, etc.) Further, the UEs101may include various sensors for collecting data associated with a user, a user's environment, and/or with a UE101, for example, the sensors may determine and/or capture audio, video, images, atmospheric conditions, device location, user mood, ambient lighting, user physiological information, device movement speed and direction, and the like.

In one embodiment, the UE101includes a location module/sensor that can determine the UE101location (e.g., a user's location). The UE101location may be determined by a triangulation system such as a GPS, assisted GPS (A-GPS), Cell of Origin, wireless local area network triangulation, or other location extrapolation technologies. Standard GPS and A-GPS systems can use the one or more satellites113to pinpoint the location (e.g., longitude, latitude, and altitude) of the UE101. A Cell of Origin system can be used to determine the cellular tower that a cellular UE101is synchronized with. This information provides a coarse location of the UE101because the cellular tower can have a unique cellular identifier (cell-ID) that can be geographically mapped. The location module/sensor may also utilize multiple technologies to detect the location of the UE101. GPS coordinates can provide finer detail as to the location of the UE101. In another embodiment, the UE101may utilize a local area network (e.g., LAN, WLAN) connection to determine the UE101location information, for example, from an Internet source (e.g., a service provider).

In one embodiment, the UEs101, the service providers109, the content providers111, and the validation platform115may interact according to a client-server model. It is noted that the client-server model of computer process interaction is widely known and used. According to the client-server model, a client process sends a message including a request to a server process, and the server process responds by providing a service. The server process may also return a message with a response to the client process. Often the client process and server process execute on different computer devices, called hosts, and communicate via a network using one or more protocols for network communications. The term “server” is conventionally used to refer to the process that provides the service, or the host computer on which the process operates. Similarly, the term “client” is conventionally used to refer to the process that makes the request, or the host computer on which the process operates. As used herein, the terms “client” and “server” refer to the processes, rather than the host computers, unless otherwise clear from the context. In addition, the process performed by a server can be broken up to run as multiple processes on multiple hosts (sometimes called tiers) for reasons that include reliability, scalability, and redundancy, among others. It is also noted that the role of a client and a server is not fixed; in some situations a device may act both as a client and a server, which may be done simultaneously and/or the device may alternate between these roles.

FIG. 2is a diagram of the components of a validation platform115, according to one embodiment. By way of example, the validation platform115is a network component (e.g., a database managing system, servers, etc.) that includes one or more components utilized for receiving, grouping, and distribution of data error reports. Further, the validation platform can receive feedback data for updating/correcting the erroneous data. Also, the validation platform can determine a threshold level for validating the feedback data, which may then be made available for use by users, service providers, content providers, or the like. It is contemplated that the functions of these components may be combined in one or more components or performed by other components of equivalent functionality. In this embodiment, the validation platform115includes a data processing module201, an aggregation module203, a distribution module205, a validation module207, and a communication module209.

In one embodiment, the data processing module201may receive reports/feedback of various types of data errors, which may be by users or user devices that participate in providing the feedback. In one embodiment, user information may be utilized to determine a geographical area associated with the user or his device. In some embodiments, personal detail information is processed to determine reliability information associated with the user or the user device. In various scenarios, the data errors may be processed to determine the types of error, priority level, frequency of the same error reported by other users, the information that may be required to correct the error, or the like. In one embodiment, the processing module may determine location information associated with a report of data error, for example, by analyzing information or attributes associated with the data error. In one embodiment, the processing module may operate in conjunction with the validation module for processing and analyzing resolution data received from one or more users in response to an MJ. In one embodiment, the processing module may determine reliability information associated with a user reporting a data error or submitting resolution data in response to an MJ.

In one embodiment, the aggregating module203may use an MJ creation flow, which may include an analysis of each of a plurality of error reports or the data from the processing module201, to create an MJ as well as generate activity context associated with the MJ. In one embodiment, the activity context may be determined based on the data error report and one or more activities that a user or a user device should be associated with when providing feedback data for resolving a targeted MJ. In one embodiment, the aggregating module may include in an MJ an attribute that a user device should be located near the location of a POI that is indicated in MJ.

In one embodiment, the distribution module205may create a list/queue of MJs that can be distributed to users or service providers for consideration or resolution. For example, the MJs may be distributed to navigation devices (e.g., personal, integrated in an automobile, etc.), mobile devices (e.g., phones, tablets, laptops, etc.), or the like, which may utilize an MFAPI or an application suitable for providing data updates. Further, the MJs may be distributed based on the activity context, device capability, user schedule, or the like. In one embodiment, an MJ may include a geo-fencing information for triggering a presentation of the at least one map job at the one or more devices. In one scenario, an MJ may indicate that for updating/validating an error in the MJ, a user/user-device is to be at the same geo-location as indicated by the MJ or be within its geo-fence attribute. In one embodiment, an MJ is presented at a user device only when location information of the user device is substantially the same as the geo-location attribute of the MJ or when the user device is located within the geo-fence attribute (e.g., within one mile) of the MJ. In one embodiment, MJs may be distributed (e.g., pushed) to one or more user devices, wherein the MJs may be queued to be resolved. For example, an MJ for a POI phone number error may be distributed to a web portal or a mobile device, which may present a visual user interface prompt on a map application.

In one embodiment, the validation module207may receive one or more responses from various users or service providers, where the responses may include one or more information items for resolving an MJ. In one embodiment, a map resolution data include, at least in part, image data, video data, audio data, or a combination thereof to confirm that the at least one map job has been resolved. In one embodiment, the resolution data may have been submitted via a validation manager105application at a UE101, wherein the submission may have been substantially automatic via a UE101, or it may include user input.

In one embodiment, the communication module209can be used to communicate with one or more entities of the system100. Certain communications can be via methods such as an internet protocol, messaging (e.g., SMS, MMS, etc.), or any other communication method (e.g., via the communication network117). In some examples, the validation platform can receive and send information about data error reports, MJs, user queries, service provider requests, or the like.

FIG. 3is a diagram of the components of a user equipment capable of communicating with one or more entities of a communication system, according to an embodiment. By way of example, a UE101includes one or more components for receiving and transmitting communication information including media content, textual messages, location information, and the like. It is contemplated that the functions of these components may be combined in one or more components or performed by other components of equivalent functionality. In this embodiment, the UE101includes a DC module107that may include one or more location modules301, magnetometer modules303, accelerometer modules305, sensors module307, and multimedia module309. Further, the UE101may also include a runtime module311to coordinate the use of other components of the UE101, a user interface313, a communication interface315, a context processing module317, and a memory module319. The applications103and the validation manager105can execute on the runtime module311utilizing the components of the UE101.

The location module301can determine a user's location, for example, via location information associated with a UE101. The user's location can be determined by a triangulation system such as GPS, assisted GPS (A-GPS), Cell of Origin, or other location extrapolation technologies. Standard GPS and A-GPS systems can use satellites113to pinpoint the location of a UE101. A Cell of Origin system can be used to determine the cellular tower that a cellular UE101is synchronized with. This information provides a coarse location of the UE101because the cellular tower can have a unique cellular identifier (cell-ID) that can be geographically mapped. The location module301may also utilize multiple technologies to detect the location of the UE101. Location coordinates (e.g., GPS coordinates) can give finer detail as to the location of the UE101when media is captured. In one embodiment, GPS coordinates are stored as context information in the memory module319and are available to the context processing module317, DC module107, validation platform115, service providers109, or to other entities of the system100(e.g., via the communication interface315.) Moreover, in certain embodiments, the GPS coordinates can include an altitude to provide a height. In other embodiments, the altitude can be determined using another type of altimeter. In certain embodiments, the location module301can be a means for determining a location of the UE101, an image, or used to associate an object in view with a location.

The magnetometer module303can be used in finding horizontal orientation of the UE101. A magnetometer is an instrument that can measure the strength and/or direction of a magnetic field. Using the same approach as a compass, the magnetometer is capable of determining the direction of a UE101using the magnetic field of the Earth. The front of a media capture device (e.g., a camera) can be marked as a reference point in determining direction. Thus, if the magnetic field points north compared to the reference point, the angle the UE101reference point is from the magnetic field is known. Simple calculations can be made to determine the direction of the UE101. In one embodiment, horizontal directional data obtained from a magnetometer can be stored in memory module319, made available to other modules and/or applications103of the UE101, and/or transmitted via the communication interface315to one or more entities of the system100.

The accelerometer module305can be used to determine vertical orientation of the UE101. An accelerometer is an instrument that can measure acceleration. Using a three-axis accelerometer, with axes X, Y, and Z, provides the acceleration in three directions with known angles. Once again, the front of a media capture device can be marked as a reference point in determining direction. Because the acceleration due to gravity is known, when a UE101is stationary, the accelerometer module305can determine the angle the UE101is pointed as compared to Earth's gravity. In certain embodiments, the magnetometer module303and accelerometer module305can be means for ascertaining a perspective of a user. This perspective information may be stored in the memory module319, made available to other modules and/or applications103of the UE101, and/or sent to one or more entities of the system100.

In various embodiments, the sensors module307can process sensor data from various sensors (e.g., GPS, accelerometer, gyroscope, thermometer, etc.) to determine environmental (e.g., atmospheric) conditions surrounding the UE101, user mood (e.g., hungry, angry, tired, etc.), location information, and various other information from a range sensors that may be available on one or more devices. For example, the sensors module307may detect conditions including humidity, temperature, geo-location, biometric data of the user, etc. Once again, this information can be stored in the memory module319and sent to the context processing module317and/or to other entities of the system100. In certain embodiments, information collected from the DC module107can be retrieved by the runtime module311and stored in memory module319, made available to other modules and/or applications103of the UE101, or sent to one or more entities of the system100.

In one embodiment, the multimedia module309may be utilized to capture various media items, for example, graphical encoded data representations, images, video, audio, and the like, wherein the captured media may be submitted to one or more modules and applications of the UE101, a service provider, and/or a content provider for further processing, storage, sharing, and the like. For example, a captured image of a graphical encoded data representations may be submitted to a service provider and/or the context processing module317for analysis and/or decoding. In one embodiment, the multimedia module309may also be utilized to process various media items for determining location information associated with a media content item. For example, a media item may be a picture that may include images of people, POIs, objects, buildings, etc. In one embodiment, the multimedia module309may use one or more image processing algorithms for processing a media item and for identifying one or more elements present into media item.

The user interface313can include various methods of communication. For example, the user interface313can have outputs including a visual component (e.g., a screen), an audio component, a physical component (e.g., vibrations), and other methods of communication. User inputs can include a touch-screen interface, a scroll-and-click interface, a button interface, a microphone, etc. Input can be via one or more methods such as voice input, textual input, typed input, typed touch-screen input, other touch-enabled input, etc.

In one embodiment, the communication interface315can be used to communicate with one or more entities of the system100. Certain communications can be via methods such as an internet protocol, messaging (e.g., SMS, MMS, etc.), or any other communication method (e.g., via the communication network117). In some examples, the UE101can send context information associated with the UE101to the service providers109, content providers111, validation platform115, or to other entities of the system100.

The context processing module317may be utilized in determining context information from the DC module107or applications103executing on the runtime module311. This information may be caused to be transmitted, via the communication interface315, to the validation platform115, service providers109or to other entities of the system100. The context processing module317may additionally be utilized as a means for determining information related to the user, an instance of data, a value, a content item, an object, a subject, and the like. In certain embodiments, the context processing module317can infer higher level context information from the context data such as favorite locations, significant places, common activities, interests in products and services, POIs at various geo-locations, etc.

FIGS. 4 and 5are flowcharts of various processes for, at least, validating crowd-sourced information, according to various embodiments. In various embodiments, validation platform115may perform one or more portions of the processes400and600, which may be implemented in, for instance, a chip set including a processor and a memory as shown inFIG. 10. As such, the validation platform115can provide means for accomplishing various parts of the process400and500as well as means for accomplishing other processes in conjunction with other components of the system100. Further, for clarity in discussing the processes400and500, the validation platform115is referred to as completing various steps of said processes; however, said processes or example steps described therein, which may include optional steps, may be performed by one or more components of the system100in any suitable order.

Referring toFIG. 4, the process400may being at step401where the validation platform may process and/or facilitate a processing of map error data to generate at least one map job and at least one activity context associated with the at least one map job, the map error data, or a combination thereof. In one embodiment, the data processing module201may receive reports/feedback of various types of data errors that can originate from users or user devices that participate in providing the feedback. In one scenario, an error report may be for an erroneous information item or a missing information item that is associated with an instance of data in a database. For example, the data error may be associated with a data entry for a certain location in a map or a POI in the database. In one scenario, a user device may utilize MFAPI to interface with the validation platform for providing the data error feedback. Also, a data error may be reported by a user device or by an internal database rule that can trigger a report of a data error. For example, the error reports may include a report of a missing Internet link error associated with a POI, a request to verify certain data in the same area as the POI, an error report for location information of another POI in the same area, or the like. In one embodiment, the aggregating module203may use an MJ creation flow, which may include an analysis of each of a plurality of error reports, to create an MJ as well as generate activity context associated with the MJ. In one embodiment, the activity context may be determined based on the data error report and one or more activities that a user or a user device should be associated with when providing feedback data for resolving a targeted MJ. In one embodiment, the at least one activity context includes, at least in part, a mode of transport, an activity associated with at least one user of at least one device reporting the map error data, or a combination thereof. For example, an MJ may include an attribute that a user device should be located near the location of a POI that is indicated in MJ. In one example, the activity context may indicate that an MJ is to be presented to a user if the user is biking, hiking, driving, running, at a certain restaurant at dinner time, en route to an airport, travelling by train, or the like. In various embodiments, an MJ may be data for indoor or outdoor POIs and locations.

In step403, the validation platform may determine one or more devices based, at least in part, on the at least one activity context. In one embodiment, a distribution module211may create a list/queue of MJs that can be distributed to users or service providers for consideration or resolution. For example, the MJs may be distributed to navigation devices (e.g., personal, integrated in an automobile, etc.), mobile devices (e.g., phones, tablets, laptops, etc.), or the like, which may utilize an MFAPI or an application suitable for providing data updates. Further, the MJs may be distributed based on the activity context. In one embodiment, the at least one map job includes, at least in part, geo-fencing information for triggering a presentation of the at least one map job at the one or more devices. In one scenario, an MJ may indicate that for updating/validating an error in the MJ, a user/user-device is to be at the same geo-location as indicated by the MJ or be within its geo-fence attribute. In one embodiment, an MJ is presented at a user device only when location information of the user device is substantially the same as the geo-location attribute of the MJ or when the user device is located within the geo-fence attribute (e.g., within one mile) of the MJ. In one embodiment, MJs may be distributed (e.g., pushed) to one or more user devices, wherein the MJs may be queued to be resolved. For example, an MJ for a POI phone number error may be distributed to a web portal or a mobile device, which may present a visual user interface prompt on a map application. In this example, the user may interact/resolve the MJ whenever he wishes so (e.g., no requirement for the user to be in the area indicated by the MJ). For example, an MJ may be associated with an indoor shopping center where its activity context may indicate that the MJ is to be presented at a user device if it is determined that the user is shopping at the shopping center, for example, via UE sensor data.

In step405, the validation platform may cause, at least in part, a transmission of the at least one map job to the one or more devices for resolving one or more map errors indicated in the at least one map job, the map error data, or a combination thereof. In various embodiments, the distribution module may cause a communication of an MJ to one or more user devices, one or more service providers (e.g., web sites, social network sites, etc.), wherein the communication may be effectuated via a short messaging service (SMS), an Internet link, a prompt via one or more applications at a UE101(e.g., application103, validation manager105, etc.), or the like. In one scenario, an MJ may be tagged to indicate a priority level, a bonus/award level, an expiration time, or the like, wherein a user may be able to readily see the tag for a timely/quick response.

Referring toFIG. 5, the process500may being at step501wherein the map error data includes a plurality of map error reports from a plurality of reporting devices, the validation platform may cause, at least in part, a clustering of the plurality of map error reports based, at least in part, on the at least one activity context, geo-location data associated with the plurality of map error reports, or a combination thereof to generate the at least map job. In one embodiment, the aggregating module203may use an MJ creation flow, which may include an analysis of each of a plurality of error reports, to automatically group the error reports into one or more MJs. In various scenarios, the grouping of the error reports may be based on an error type, an activity context, a geo-location associated with the error, a reporting user or user device, a validation threshold rating, a priority level, or the like.

In step503, the validation platform may receive map job resolution data from the one or more devices. In one embodiment, the validation module207may receive one or more responses from various users or service providers, where the responses may include one or more information items for resolving an MJ. In one embodiment, the map resolution data include, at least in part, image data, video data, audio data, or a combination thereof to confirm that the at least one map job has been resolved. In one embodiment, the resolution data may be submitted via a validation manager105application at a UE101, wherein the submission may be substantially automatic via a UE101, or it may include user input. For example, a navigation system may determine location information of a POI in an MJ and provide an automated response that includes the location information. In one scenario, a user may interact with an MJ on a map application and provide information for resolving a missing data point associated with a POI in the MJ.

In step505, the validation platform may process and/or facilitate a processing of the map job resolution data against at least one threshold logic to determine that the at least one map job has been resolved. In one embodiment, the at least one threshold logic includes, at least in part, one or more rules, one or more criteria, or a combination thereof for determining that the at least one map job has been resolved. In one embodiment, a plurality of resolution data instances may be compared to each other in order to determine if they match. For example, 10 responses to an MJ for verifying a new hiking or bicycle trail are compared to see if information (e.g., pictures, address, trail number, etc.) in the reported responses are similar or match. For example, the threshold logic may indicate that at least four of the reported resolution data instances are to match in order to qualify as a validated resolution to the associated MJ. In one scenario, if the number of matching responses meet a validation logic, then the MJ may be considered resolved.

In step507, the validation platform may cause, at least in part, a signaling of the one or more devices that the at least one map job has been resolved. In one embodiment, the signaling initiates a removal of the at least one map job from at least one job queue of the one or more devices. In one scenario, upon a validated resolution of an MJ, the MJ may be tagged as resolved or automatically closed as well as any related individual error reports may be closed. In one embodiment, a notification of a resolution may be communicated to one or more users who had reported the error. For example, the communication may be via an SMS message, an Internet link, a prompt via one or more applications at a UE101(e.g., application103, validation manager105, etc.), or the like. In one embodiment, one or more users who provided information for resolving a reported error may be awarded with some credit points at one or more user accounts; for example, an account with the entity receiving the error correction, an online social network account, a service/content provider account, or the like. In one example, the amount of awarded points may be based on user history, reliability of reported solutions, user trust level, the type of corrected error, priority of the corrected error, or the like parameters.

In step509, the validation platform may determine the threshold logic based, at least in part, on a map error type, the at least one activity context, trust level information associated with the one or more devices, or a combination thereof. In one embodiment, the validation module207may utilize various information items for determining a threshold level, which may be utilized in validating a resolution of an MJ. In various embodiments, a threshold logic/value/level may be based on a sensitivity level of the required data for resolving an MJ, priority level of an MJ, reliability of past MJ responses provided by the user or user device reporting a new solution, user trust level, the type of data to be corrected, or the like. For example, an MJ requiring resolution data from inside a restaurant may require that a minimum number of resolution reports are to include a media item captured in the restaurant. In one example, a high priority MJ may have a lower threshold logic since there may be no other data to compare with. In one example, resolution data received from a user who has obtained a certain trust level with a service provider may be validated by itself or when compared with a minimum number of other resolution data.

FIG. 6illustrates an example process flow for resolving map data errors, according to one embodiment.

In one embodiment,FIG. 6, a process600may include various sub processes for processing and resolving data errors601a-601n(errors601) that may be received from a plurality of users or user devices603a-603nthat request or wish to participate in providing the feedback. In various examples, the errors601may be for an erroneous or a missing information item, e.g., a POI phone number error, a POI location error on a map, a POI address error, or the like. In one embodiment, the errors601may be received via MFAPI605and input into an aggregator logic607for processing. In one embodiment, the aggregator may use a MJ creation flow that may include an analysis of each of the plurality of errors601for grouping the errors into one or more MJs. In various scenarios, the grouping of the errors may be based on an error type, geo-location associated with the error, reporting user or user device, validation threshold rating, priority, or the like. In this example, a single MJ609is created, wherein the each error601is listed along with one or more attributes, e.g., latitude, longitude, threshold, and type of error.

In one embodiment, a device logic611to determine which user devices a MJ should be distributed or made available to. For example, the device or distribution logic may create a list/queue of MJs that can be distributed to users or service providers for consideration or completion. In various scenarios, an MJ may be pulled/requested by a user device613a(e.g., a mobile device) or613m(e.g., an in-car navigation system), or an MJ may be pushed/distributed to a device or website613b(e.g., a map creator). In one embodiment, an MJ may be associated with a geo-location attribute, wherein the system100may also determine a geo-fence attribute for the MJ. In one scenario, an MJ may indicate that for updating/validating an error in the MJ, a user/user-device is to be at the same geo-location as indicated by the MJ or be within its geo-fence attribute. In one embodiment, an MJ is presented at a user device only when location information of the user device is substantially the same as the geo-location attribute of the MJ or when the user device is located within the geo-fence attribute (e.g., within one mile) of the MJ. In one embodiment, MJs may be distributed (e.g., pushed) to one or more user devices, wherein the MJs may be queued to be resolved.

In one embodiment, a threshold/validation logic615may monitor or receive responses for resolving an MJ, where the responses may be received from various users devices617a-617x. In one embodiment, the threshold logic may process and compare an MJ resolution data against a threshold logic to determine that the MJ has been resolved. In one embodiment, threshold logic includes, at least in part, one or more rules, one or more criteria, or a combination thereof for determining that the at least one map job has been resolved. In one embodiment, a plurality of resolution data instances may be compared to each other in order to determine if they match. In one embodiment, the threshold logic may cause a communication to the one or more devices that the MJ has been resolved. In one embodiment, the signaling initiates a removal of the MJ619for one or more queues, wherein the MJ may be tagged as resolved or the MJ and related individual error reports may be automatically closed. In one embodiment, a notification of a resolution may be communicated to one or more users who had reported the error. For example, the communication may be via an SMS message, an Internet link, a prompt via one or more applications at a UE101(e.g., application103, validation manager105, etc.), or the like. Additionally, the corrected/updated data may be uploaded to a map database621, wherein the feedback data utilized in resolving the MJ may be stored at one or more data stores.

FIGS. 7A and 7Billustrate example user interface diagrams utilized in the processes of theFIGS. 4 through 6, according to various embodiments.

FIG. 7Aincludes diagrams700,710, and720, which may be utilized in reporting data errors. In one scenario, the diagrams700depicts a UI at a user device with a MFAPI that can be used to report an error associated with a POI or any data instance that may be available via one or more applications at a UE101. For example, diagram700illustrates a report indicating that there may be an error with a physical address of a POI (e.g., a house address). In one scenario, the diagram710illustrates a UI utilized in a map application (e.g., a map reporter) to report an error, wherein the map utility may include an API (MapAPI) for interfacing with and providing the report to a validation platform. In another scenario, the diagram720depicts an error report that was generated (e.g., substantially automatically) by a map system that captured the data error.

FIG. 7Bincludes UI diagrams730,740, and750, which may presented at different various user devices for presenting any of the MJs illustrated in the diagrams700,710, and720. For example, the UI730may be presented at a UE101, the UI740may be presented at a website, and the UI750may be presented at a navigation system of an automobile. However, any UI may be designed and presented at any device based on the device or service provider requirements and expectations. In the example UIs of730,740, and750a user may interact with the presented information or prompts, wherein the user may or may not accept to interact with a presented MJ.

FIG. 8includes illustration of a mapjob flow process, according to one embodiment. In one embodiment, process800includes receiving a data error report, at step8A, from user-X indicating that there may be an error with information on a speed limit at a given location (e.g., along a certain segment of a freeway). For example, user-X may have noticed the speed limit presented in a map application or a navigation system in his automobile. At step8B, the validation platform may log the error report and create an MJ for distribution to one or more users. At step8C, the validation platform may determine that one or more user devices UE101a-101mof one or more users 1-m is near the location801where the error report is associated with. In one example, a UE101may be a registered user device, which previously has been used to provide feedback on previous data error reports. In one scenario, the validation platform may cause a presentation of a message803via UI805of a UE101, where the message may enquire if user-1 of the UE101amay wish to help to resolve an MJ that is nearby, e.g.,801. In this example, the user-1 accepts the task to provide one or more information items or a response to a potential question. At step8D, the user-1 may be presented with a question “Is the speed limit at 40K/h?” that is related to the speed limit error reported by user-X. At step8E, a response or other information provided by user-1 is logged into the database, and steps8C-8D may be repeated as many times as necessary to meet a threshold logic, which would indicate that the resolution data provided by the users are validated. In this example, the threshold logic is set at three, and as the number of agreeing responses “YES” reach that level, the validation platform may validate the speed limit resolution at 40 K/h and update the database at step8F. At step8G, the validation platform may close the MJ and notify user-X that the data error, which user-X reported has been resolved and updated.

The processes described herein for validating crowd-sourced information may be advantageously implemented via software, hardware, firmware, or a combination of software and/or firmware and/or hardware. For example, the processes described herein, may be advantageously implemented via processor(s), Digital Signal Processing (DSP) chip, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGAs), etc. Such exemplary hardware for performing the described functions is detailed below.

FIG. 9illustrates a computer system900upon which an embodiment of the invention may be implemented. Although computer system900is depicted with respect to a particular device or equipment, it is contemplated that other devices or equipment (e.g., network elements, servers, etc.) withinFIG. 9can deploy the illustrated hardware and components of system900. Computer system900is programmed (e.g., via computer program code or instructions) to validate crowd-sourced information as described herein and includes a communication mechanism such as a bus910for passing information between other internal and external components of the computer system900. Information (also called data) is represented as a physical expression of a measurable phenomenon, typically electric voltages, but including, in other embodiments, such phenomena as magnetic, electromagnetic, pressure, chemical, biological, molecular, atomic, sub-atomic and quantum interactions. For example, north and south magnetic fields, or a zero and non-zero electric voltage, represent two states (0, 1) of a binary digit (bit). Other phenomena can represent digits of a higher base. A superposition of multiple simultaneous quantum states before measurement represents a quantum bit (qubit). A sequence of one or more digits constitutes digital data that is used to represent a number or code for a character. In some embodiments, information called analog data is represented by a near continuum of measurable values within a particular range. Computer system900, or a portion thereof, constitutes a means for performing one or more steps of validating crowd-sourced information.

A bus910includes one or more parallel conductors of information so that information is transferred quickly among devices coupled to the bus910. One or more processors902for processing information are coupled with the bus910.

Computer system900also includes a memory904coupled to bus910. The memory904, such as a random access memory (RAM) or any other dynamic storage device, stores information including processor instructions for validating crowd-sourced information. Dynamic memory allows information stored therein to be changed by the computer system900. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at neighboring addresses. The memory904is also used by the processor902to store temporary values during execution of processor instructions. The computer system900also includes a read only memory (ROM)906or any other static storage device coupled to the bus910for storing static information, including instructions, that is not changed by the computer system900. Some memory is composed of volatile storage that loses the information stored thereon when power is lost. Also coupled to bus910is a non-volatile (persistent) storage device908, such as a magnetic disk, optical disk or flash card, for storing information, including instructions, that persists even when the computer system900is turned off or otherwise loses power.

Information, including instructions for validating crowd-sourced information, is provided to the bus910for use by the processor from an external input device912, such as a keyboard containing alphanumeric keys operated by a human user, or a sensor. A sensor detects conditions in its vicinity and transforms those detections into physical expression compatible with the measurable phenomenon used to represent information in computer system900. Other external devices coupled to bus910, used primarily for interacting with humans, include a display device914, such as a cathode ray tube (CRT), a liquid crystal display (LCD), a light emitting diode (LED) display, an organic LED (OLED) display, a plasma screen, or a printer for presenting text or images, and a pointing device916, such as a mouse, a trackball, cursor direction keys, or a motion sensor, for controlling a position of a small cursor image presented on the display914and issuing commands associated with graphical elements presented on the display914. In some embodiments, for example, in embodiments in which the computer system900performs all functions automatically without human input, one or more of external input device912, display device914, and pointing device916is omitted.

Network link978typically provides information communication using transmission media through one or more networks to other devices that use or process the information. For example, network link978may provide a connection through local network980to a host computer982or to equipment984operated by an Internet Service Provider (ISP). ISP equipment984in turn provides data communication services through the public, world-wide packet-switching communication network of networks now commonly referred to as the Internet990.

A computer called a server host992connected to the Internet hosts a process that provides a service in response to information received over the Internet. For example, server host992hosts a process that provides information representing video data for presentation at display914. It is contemplated that the components of system900can be deployed in various configurations within other computer systems, e.g., host982and server992.

At least some embodiments of the invention are related to the use of computer system900for implementing some or all of the techniques described herein. According to one embodiment of the invention, those techniques are performed by computer system900in response to processor902executing one or more sequences of one or more processor instructions contained in memory904. Such instructions, also called computer instructions, software and program code, may be read into memory904from another computer-readable medium such as storage device908or network link978. Execution of the sequences of instructions contained in memory904causes processor902to perform one or more of the method steps described herein. In alternative embodiments, hardware, such as ASIC920, may be used in place of or in combination with software to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware and software, unless otherwise explicitly stated herein.

The signals transmitted over network link978and other networks through communications interface970, carry information to and from computer system900. Computer system900can send and receive information, including program code, through the networks980,990among others, through network link978and communications interface970. In an example using the Internet990, a server host992transmits program code for a particular application, requested by a message sent from computer900, through Internet990, ISP equipment984, local network980, and communications interface970. The received code may be executed by processor902as it is received, or may be stored in memory904or in storage device908or any other non-volatile storage for later execution, or both. In this manner, computer system900may obtain application program code in the form of signals on a carrier wave.

Various forms of computer readable media may be involved in carrying one or more sequence of instructions or data or both to processor902for execution. For example, instructions and data may initially be carried on a magnetic disk of a remote computer such as host982. The remote computer loads the instructions and data into its dynamic memory and sends the instructions and data over a telephone line using a modem. A modem local to the computer system900receives the instructions and data on a telephone line and uses an infra-red transmitter to convert the instructions and data to a signal on an infra-red carrier wave serving as the network link978. An infrared detector serving as communications interface970receives the instructions and data carried in the infrared signal and places information representing the instructions and data onto bus910. Bus910carries the information to memory904from which processor902retrieves and executes the instructions using some of the data sent with the instructions. The instructions and data received in memory904may optionally be stored on storage device908, either before or after execution by the processor902.

In one embodiment, the chip set or chip1000includes a communication mechanism such as a bus1001for passing information among the components of the chip set1000. A processor1003has connectivity to the bus1001to execute instructions and process information stored in, for example, a memory1005. The processor1003may include one or more processing cores with each core configured to perform independently. A multi-core processor enables multiprocessing within a single physical package. Examples of a multi-core processor include two, four, eight, or greater numbers of processing cores. Alternatively or in addition, the processor1003may include one or more microprocessors configured in tandem via the bus1001to enable independent execution of instructions, pipelining, and multithreading. The processor1003may also be accompanied with one or more specialized components to perform certain processing functions and tasks such as one or more digital signal processors (DSP)1007, or one or more application-specific integrated circuits (ASIC)1009. A DSP1007typically is configured to process real-world signals (e.g., sound) in real time independently of the processor1003. Similarly, an ASIC1009can be configured to performed specialized functions not easily performed by a more general purpose processor. Other specialized components to aid in performing the inventive functions described herein may include one or more field programmable gate arrays (FPGA), one or more controllers, or one or more other special-purpose computer chips.

In one embodiment, the chip set or chip1000includes merely one or more processors and some software and/or firmware supporting and/or relating to and/or for the one or more processors.

The processor1003and accompanying components have connectivity to the memory1005via the bus1001. The memory1005includes both dynamic memory (e.g., RAM, magnetic disk, writable optical disk, etc.) and static memory (e.g., ROM, CD-ROM, etc.) for storing executable instructions that when executed perform the inventive steps described herein to validate crowd-sourced information. The memory1005also stores the data associated with or generated by the execution of the inventive steps.

Pertinent internal components of the telephone include a Main Control Unit (MCU)1103, a Digital Signal Processor (DSP)1105, and a receiver/transmitter unit including a microphone gain control unit and a speaker gain control unit. A main display unit1107provides a display to the user in support of various applications and mobile terminal functions that perform or support the steps of validating crowd-sourced information. The display1107includes display circuitry configured to display at least a portion of a user interface of the mobile terminal (e.g., mobile telephone). Additionally, the display1107and display circuitry are configured to facilitate user control of at least some functions of the mobile terminal. An audio function circuitry1109includes a microphone1111and microphone amplifier that amplifies the speech signal output from the microphone1111. The amplified speech signal output from the microphone1111is fed to a coder/decoder (CODEC)1113.

A radio section1115amplifies power and converts frequency in order to communicate with a base station, which is included in a mobile communication system, via antenna1117. The power amplifier (PA)1119and the transmitter/modulation circuitry are operationally responsive to the MCU1103, with an output from the PA1119coupled to the duplexer1121or circulator or antenna switch, as known in the art. The PA1119also couples to a battery interface and power control unit1120.

The encoded signals are then routed to an equalizer1125for compensation of any frequency-dependent impairments that occur during transmission though the air such as phase and amplitude distortion. After equalizing the bit stream, the modulator1127combines the signal with a RF signal generated in the RF interface1129. The modulator1127generates a sine wave by way of frequency or phase modulation. In order to prepare the signal for transmission, an up-converter1131combines the sine wave output from the modulator1127with another sine wave generated by a synthesizer1133to achieve the desired frequency of transmission. The signal is then sent through a PA1119to increase the signal to an appropriate power level. In practical systems, the PA1119acts as a variable gain amplifier whose gain is controlled by the DSP1105from information received from a network base station. The signal is then filtered within the duplexer1121and optionally sent to an antenna coupler1135to match impedances to provide maximum power transfer. Finally, the signal is transmitted via antenna1117to a local base station. An automatic gain control (AGC) can be supplied to control the gain of the final stages of the receiver. The signals may be forwarded from there to a remote telephone which may be another cellular telephone, any other mobile phone or a land-line connected to a Public Switched Telephone Network (PSTN), or other telephony networks.

Voice signals transmitted to the mobile terminal1101are received via antenna1117and immediately amplified by a low noise amplifier (LNA)1137. A down-converter1139lowers the carrier frequency while the demodulator1141strips away the RF leaving only a digital bit stream. The signal then goes through the equalizer1125and is processed by the DSP1105. A Digital to Analog Converter (DAC)1143converts the signal and the resulting output is transmitted to the user through the speaker1145, all under control of a Main Control Unit (MCU)1103which can be implemented as a Central Processing Unit (CPU).

The MCU1103receives various signals including input signals from the keyboard1147. The keyboard1147and/or the MCU1103in combination with other user input components (e.g., the microphone1111) comprise a user interface circuitry for managing user input. The MCU1103runs a user interface software to facilitate user control of at least some functions of the mobile terminal1101for validating crowd-sourced information. The MCU1103also delivers a display command and a switch command to the display1107and to the speech output switching controller, respectively. Further, the MCU1103exchanges information with the DSP1105and can access an optionally incorporated SIM card1149and a memory1151. In addition, the MCU1103executes various control functions required of the terminal. The DSP1105may, depending upon the implementation, perform any of a variety of conventional digital processing functions on the voice signals. Additionally, DSP1105determines the background noise level of the local environment from the signals detected by microphone1111and sets the gain of microphone1111to a level selected to compensate for the natural tendency of the user of the mobile terminal1101.

The CODEC1113includes the ADC1123and DAC1143. The memory1151stores various data including call incoming tone data and is capable of storing other data including music data received via, e.g., the global Internet. The software module could reside in RAM memory, flash memory, registers, or any other form of writable storage medium known in the art. The memory device1151may be, but not limited to, a single memory, CD, DVD, ROM, RAM, EEPROM, optical storage, magnetic disk storage, flash memory storage, or any other non-volatile storage medium capable of storing digital data.

An optionally incorporated SIM card1149carries, for instance, important information, such as the cellular phone number, the carrier supplying service, subscription details, and security information. The SIM card1149serves primarily to identify the mobile terminal1101on a radio network. The card1149also contains a memory for storing a personal telephone number registry, text messages, and user specific mobile terminal settings.

Additionally, sensors module1153may include various sensors, for instance, a location sensor, a speed sensor, an audio sensor, an image sensor, a brightness sensor, a biometrics sensor, various physiological sensors, a directional sensor, and the like, for capturing various data associated with the mobile terminal1101(e.g., a mobile phone), a user of the mobile terminal1101, an environment of the mobile terminal1101and/or the user, or a combination thereof, wherein the data may be collected, processed, stored, and/or shared with one or more components and/or modules of the mobile terminal1101and/or with one or more entities external to the mobile terminal1101.