[go: up one dir, main page]

WO2019115842A1 - Système et procédé d'identification unique de dispositifs électroniques - Google Patents

Système et procédé d'identification unique de dispositifs électroniques Download PDF

Info

Publication number
WO2019115842A1
WO2019115842A1 PCT/ES2017/070809 ES2017070809W WO2019115842A1 WO 2019115842 A1 WO2019115842 A1 WO 2019115842A1 ES 2017070809 W ES2017070809 W ES 2017070809W WO 2019115842 A1 WO2019115842 A1 WO 2019115842A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
ooid
time
uts
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/ES2017/070809
Other languages
English (en)
Spanish (es)
Inventor
Isidoro PÉREZ GARCÍA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Moxible SL
Moxible SL
Original Assignee
Moxible SL
Moxible SL
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Moxible SL, Moxible SL filed Critical Moxible SL
Priority to ES202090021A priority Critical patent/ES2855199B2/es
Priority to PCT/ES2017/070809 priority patent/WO2019115842A1/fr
Publication of WO2019115842A1 publication Critical patent/WO2019115842A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q30/00—Commerce
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor

Definitions

  • the object of the invention is part of the technical field of information technology and telecommunications.
  • the object of the invention is directed to the management of association and identification of electronic devices such as terminals in communication networks.
  • user terminal or user terminal by its acronym in English UT
  • user terminal by its acronym in English UT
  • offline when we visit different physical sites with the phone in the pocket turned on but not active
  • our life or online entity when we visit online sites through web pages or visit mobile applications through that terminal.
  • WiFi tracking techniques based on the detection of the MAC address of the device are designed exclusively to identify the UTs in a physical area, ie for the analysis of offiine behavior, without the possibility of linking it to the user's online behavior, example, the communication of push messages to the mobile application when a user terminal is detected in a physical space is not intended or permitted in all OSs
  • Another known problem is to have a unique identifier of the user terminal and the user in offiine and online, both for Android and for iOS, is another problem that is not resolved, since from some operating systems of wide use (such as iOS 10 ) it is not allowed through an APP (including the Navigator) the access via software to the permanent identifiers of the device such as the MAC address or the access address to the medium of your network cards.
  • APP including the Navigator
  • the online advertising identifier of the user terminal could be accessed, but the browser, in turn, does not have access to the advertising identifier, and on the other hand, when the telephone is not in use (ie, it is offiine) the online advertising identifier is not issued or share in any way, so it can not be used to cross it with the detection of the address of access to the medium of your network cards.
  • the term system to describe any number of components, elements, subsystems, devices, packet switching elements, packet switches, access switches, routers, networks, devices or computer and / or communication mechanisms, or combinations of components of the same.
  • the term "computer” includes a processor, memory and buses capable of executing an instruction in which the computer refers to one or a group of computers, personal computers, workstations, mainframes or combinations of computers thereof, such as a network . It also has that as users any physical person or any system / machine / robot software or physical that access or are present in any type of:
  • offiine space stores, cities, shopping centers, airports, etc.
  • offiine space stores, cities, shopping centers, airports, etc.
  • NS Server Node It makes the device of a centralized architecture for storage, processing and distribution of information to the rest of the elements.
  • Signatures Succession or array of fingerprints hashed (encoded) that generates the same device, according to ios and / or the SSiDs received, according to the capabilities via APP or via WEB.
  • Each firm has a position, the first ones are called base signatures, and they are obtained when their deviceID has been approved and validated, the rest are additional signatures that will contribute value as a whole.
  • Visitor person or any type of device (things machines, physical robots or software) different from others that access a space (physical or digital) generating events in that space.
  • Visit short continuous presence considered by the continuous grouping of events of a visitor in a physical or digital space.
  • Visit grouped presence of a visitor in a period considering the discontinuous grouping of events of a visitor in a physical or digital space.
  • - User terminal any device carried by a person, active / robot habitually in his offline life, and which is also used as a person access device! to online media (website, applications, services, queries, internet, etc ... telephone, voice, audio, data, etc. ..) that supports multiple applications, sensors, actuators, screens, buttons, keyboards, etc.
  • the user terminals can be personal or non-personal. Personal devices can do all their functions even if they are not under the control of the human, that is, when they are at rest or not active. But it is considered personal since its physical entity is still linked to the physical person.
  • the object of the invention is based on the daily use of mobile devices that we use in our day to day (smart phone, tablets, smart watches) that act as an interface between our offline life (when we move to various physical sites with the phone in your pocket) and our online life (when we move around visiting websites or using mobile apps).
  • the invention described below is based on an intelligent device, which we will call Node, mainly dedicated to the listening and processing of radio information of the UTs.
  • this intelligent device Node By locating this intelligent device Node in a physical space, it will receive and demodulate and decode the signals in the public frequency bands of (2.4 -3.6 and 5Gbz) in which other mobile terminals broadcast frequently due to communication protocols. using radio (W ⁇ Fi, Bluetooth, others), so analyzing the received frames can detect the presence of mobile devices in a physical area (offline space) anonymously without any intervention.
  • radio W ⁇ Fi, Bluetooth, others
  • OOID information contained in the OOID to the different elements of the architecture (Node, APPs, Browsers, Server). Said OOID will persist and will be updated in the user terminal also when the user terminal is on but not used (offline).
  • This device and methods are applied not only to the generation of OOiD identifiers, but also to achieve multicai proximity messages, achieving a high number of UTs that without any gesture from the user receive information associated with their profile in their user terminal by proximity in physical areas (provided they have authorized it legally).
  • Mechanisms are designed that allow, in a transparent manner to the user, when the user terminal passes close to the Node, a communication is established between both, for the exchange of GGID information or the direct sending of messages to the user terminal.
  • Methods are designed to maximize the number of UTs that are uniquely identified in the physical space by proximity even if they use random MAC addresses or Virtual MAC addresses, in order to improve the unique identification of their cross-online and offline behavior and be able to send message by proximity to more UTs.
  • the invention object and associated systems are achieved by means of impiementations. 60 to 80%.
  • the device and associated components allow to have a system with many industrial applications nowadays, thanks to having an OOID, especially useful in the field of marketing.
  • OOID especially useful in the field of marketing.
  • these marketing applications it is not necessary to guarantee 100% unique identification of the UTs at all times and in all environments, but only to try to communicate with as many people as possible at the appropriate time and place, with messages relevant to the consumer that can be chosen by analyzing their behavior in various media or channels.
  • the online and anonymous behavior information collected by the system is anonymous, it is impossible to identify the person who carries it, but with the user's consent it can be linked to personal or other information provided by the user or available in other systems ( CRM, POS, etc ..), the design includes a new profile creation system that allows the incorporation of personal and non-personal information ⁇ psycho-socio-demographic, and transactional) mixed information of anonymous behavior oniine and ofline (in App, Web and physical location) obtained 24/7 and in real time.
  • Figure 1 shows a diagram showing a possible architecture model and the enumeration of the elements considered and the direction of the main flows of messages or information between them.
  • Figure 2. It shows an example of an event table where the structure and functions necessary in the events between elements of the system are detailed.
  • Figure 3. Shows an implementation of the OOID in which the structure and functions necessary in the oniine and offline identifier are detailed.
  • Figure 4. Shows a diagram showing the processes for the verification of the OOID.
  • Figure 5. Shows a diagram showing the processes dedicated to the propagation of the OOiD.
  • Figure 6.1 Shows a descriptive table of the Node Device.
  • Figure 6.2 -- It shows a scheme of the system of direct notifications of node
  • Figure 7. Shows a tabia in which the main functions of the APP SDK are appraised.
  • Figure 8.- Shows a tabia in which the main functions of the WEB SDK are appreciated.
  • Figure 9 1 It shows a table in which the main functions Server Node or Server are appreciated.
  • Figure 9.2. Shows a diagram showing the performance of the behavior analysis, detailing the management module of on-line and offline behavior.
  • Figure 9.3. It shows a scheme where the parameters of the calculation of visitors, visits and visit are described, describing the techniques of analysis of online and offline behavior.
  • Figure 9.4. Shows a diagram showing the interaction between systems, detailing the operations between modules and subsystems. PREFERRED EMBODIMENT OF THE INVENTION
  • configurations of the architecture described below could be varied, and that has been considered as the best alternative in the current state of technology, thinking of using a central element or server and a large number of low-cost devices ( nodes) forming an extensive network, although you could also use a model where the server functions are distributed in the nodes having a distributed network scenario.
  • An intelligent hardware device or Node comprising among others a radio frequency listening module.
  • a series of electronic devices (102) such as user terminal equipment (102), referred to in parts of this document as UTs (102), capable of running mobile applications where an SDK APP (104) is integrated for mobile applications or APPs, and where a web browser runs which in turn have a web SDK (105) integrated, preferably under HTML5 for web pages.
  • NS or Server Node (103) with subsystems or modules - preferably implemented in software hardware - analysis and propagation of oniine and offiine identifiers (108), behavior management module (107) offiine and oniine and a campaign management module that includes a module of analysis of profiles and results (108), all with different connections between them.
  • the Server Node (103) acts as a centralizer.
  • NS or Server Node (103) preferably implemented in hardware, which includes among other subsystems or modules-: a) software- analysis and propagation of oniine and offline identifiers (106) b) module management of! behavior (107) off ⁇ ine and oniine c) a campaign manager module that includes a profile and results analysis module (108), all with different connections between them.
  • the Server Node (103) acts as a centraliser.
  • Behavior (107) can obtain information of offine detections (node events), which are analyzed to calculate visitors, visits and visits, and update data from an Online Offline Identifier, called OOID for its acronym in English, to the rest of elements.
  • OOID Online Offline Identifier
  • behavior analysis module (107) information (SDK events) of the online use of mobile applications of the SDK APP (104) and browsers by visiting web pages through the WEB SDK (105) is obtained in order to analyze the behavior crossed oniine in the profiles and results analysis module (108).
  • a communication subsystem is designed based on events (discrete pieces or pieces of information) from the UTs (102) and Node / s (101) to a server (SETS, Send Events to Server) and a communication protocol from the server to the Node and UTs (REFS: Receive Element from Server).
  • Node events such as traveling between the Node (101) and the server node (103) or SDK events (those traveling between the SDK and the serving node (103), with the following elements among others:
  • NodeJD identify a node or a physical zone.
  • Type event or information that is sent and its specific parameters.
  • the OOID identifier can include, among others, the elements shown in figure 3.
  • dID device identifier
  • dID device identifier
  • the dID would always be present in the OOID even if it is a random, non-approved value, in turn the dID could be updated by the process of propagation of OOID by the SDKs (104, 105), the server node (103) or the Node (101) at the time the approved OOID is known.
  • the OOID can comprise an OUI, which corresponds to the first three bytes of the address of the access layer. middle of! ends! of user (102) and will be used in the process of approval of! QOID
  • the object of the invention contemplates the implantation of a succession of signatures that we denominate by its term in English array or in Spanish succession of Signatures, which allow to add signatures to it, understood said signatures as characteristics of the user terminal (102) or of its behavior, which can be obtained and propagated by Nodes (101), Server Node (103), SDK APP (104) and WEB SDK (105) in combination. That is, they are obtained by combining online and offline information sources.
  • the object of the invention makes use of processes of homologation, unification, acceptance and propagation of OOIDs.
  • the following processes could be performed in any of the architecture components that receive events with OOIDs from UTs (102), especially in the Server Node (103); for this, in the homologation, those OOIDs can be marked with the status of Approved, which by any method has proven that their dID comes from a real and non-random address of the access layer to the middle of the user terminal (102). They are used to determine the number of unique visitors and to have unique identification in the message delivery system.
  • the Approved OOIDs can be obtained directly:
  • IOS up to iGS9 by software from the address of the access layer to! medium.
  • OS 10.3 different techniques are combined, such as the direct connection to the access point - the hidden AP of the Proximity Node or the propagation of the OOID between the different elements of the architecture.
  • the OOID could be homologated to generate the dID in the SDKs (104, 105) and Nodes, or later in the Server Node only with the OUI without the need to store or send the complete real address to the server node (103). (for privacy), for this could be contrasted against the list of OUI of official manufacturers, against a history of real OUIs (used by Chinese manufacturers that do not use the official list) available before the processes of aieatorlzaconstruissus, and against a list of virtual or false OUIs, which have been detected as such, since they appear with unnatural behavior, even at night, and checked with the different models of UTs (102) in different locations.
  • the Unified status of a non-approved OOID can be marked when there is a high degree of coincidence or small distance between the set of signatures with another Approved OOID (which has been received through the propagation process. can create a record of unified OOIDs among them that would be used among other tasks to determine the number of unique visitors and visits in the offline behavior analysis process.
  • the matching signatures between the OOID approved and the OOID not approved and thus propagate a unified OOID in signatures
  • this process of unification could be removed repeated signatures or contained in others to optimize the process, and could be ordered so that the coincidence measurement could be implemented nimbly in the case of many firms, assigning a greater weight to the first firms that allow better identification of e unique form to a user terminal (102).
  • n is the number of matching signatures available between both OOIDs.
  • the Accepted status of a non-approved and non-unified OOID can be marked when there is a degree of overlap between the set of signatures with another Approved OOID.
  • a record of unified OOIDs could be created among them that could be used in the behavior system to determine the presence time the number of visits. In this case, the concatenation of signatures or propagation would not have to occur.
  • a unified OOID record could also be created between them.
  • a part of the method object of the invention is based on the online and offline identification from the propagation of the OOIDs obtained for the UTs (102), by several ways (such as events or silent push notifications) and is applied, not only to the server node (103) but to all the elements of the architecture, impiementing at least the functions that are appreciated in figure 5.
  • the server node (103) can broadcast the approved OOIDs to other applications and browsers, mini-browser (which is launched automatically in some operating systems of UTs (102) when accessing a captive portal) and embedded browsers (webviews) through various techniques among others:
  • the number of the propagation status can be encoded, to know if it has been broadcast several times to all the elements of the architecture. Only the approved / unified and validated OOIDs are propagated, updated in real time.
  • the server node (103) can update the status of the OOIDs that do not are Homologated to Approved and also update their value in the historical data associated with UTs (102), or only store the historical relationship between OOIDs from the date of approval without altering the OOID of past data.
  • Said architecture corresponding to a preferential embodiment of the object of the invention comprises the device Node (101), which responds to a structure as shown in Figure 6.1 and which according to implementations may include among others the following functionalities labeled in said figure 6.1 , having in this way the following functionalities:
  • SETS Listen and process frames that emit UTs (102) both when they are and when they are not associated with wireless networks that use Wi-Fi, ie WLAN type. From the information of said frames they could generate at the time of execution an OOID, process it among others with the approval, unification, acceptance and validation systems described above, and generate one or more Node events (101). They could listen and process frames that emit UTs (102) when they have b! Uetooth (BT) communications. From the information of said frames they can generate an OOID in execution time, process it among others with the approval, unification, acceptance and validation systems described above, and generate one or several Node events (101).
  • BT Uetooth
  • VPN virtual private network
  • the generated Node events can be stored until the connection to the server is available.
  • a single node event which also contains the OOID only the information of the number of detections and the average detection power. Therefore, Events may contain information from a single detection or several in a short space of time. Additionally, in each node event it could include, among other data, more information useful for remote maintenance (such as its IP address, GPS coordinates, list of nearby SSiDs).
  • REFS Node Among other information, it could receive, in real time from the server, information from approved OOiDs, for the execution of the unification process. Among other information to support all the functionality of the system could receive in real time from the server, information of events of other Nodes (101), OOIDs of UTs (102) that enter the Node Virtual geofence with their SSIDs, campaigns, profiles, communication tokens with the user terminals (102), the manufacturers GUI list, a history of OUIs available before the randomization processes existed, a list of virtual or false GUIs and the list of validated OUi.
  • a hidden access point (AP) can be generated only known by the UTs (102) where the APP SDK (104) has been integrated, allowing WLAN connections with said UTs (102). It can also generate a BT point visible mode to pair with other user terminals (102) that know a link number (PIN) only available in the UTs (102) where the SDK APP (104) has been integrated, allowing BT connections with said UTs (102). In some implementations it could be by means of socket and that could, among other information, send its Approved OOID to the connected UTs (102), since it would have in the level 2 connection enough information to Homologate the OOID.
  • a Captive Portal Node is responsible for generating an access point, an AP, visible in open mode with a captive portal, to allow connections with any user who wants it (for example, because he is trying to register in a fideiizaissus program, validate a coupon received by email, or because you are looking for free internet access).
  • Node (101) would identify and access the frames sent for the connection to the captive portal, could among other methods homologate the OOID and through the WEB SDK (105) store it in a local storage device! which we call by its English name! oca! storage or in the form of cookies associated to said predetermined domain ..
  • An unauthorized Bogue-type node that demotes Rogue Node can be responsible for generating WLAN beacon frames to announce an available SSID and force nearby user terminals (102) to send association frames if they have said SSID in their list of connected networks .
  • the list of SSIDs to be announced could come from the one received from the server and previously obtained by the SDKs installed in the PTSs of the UTs, of the most popular SSIDs but not detected in the vicinity by the Rogue Node (since these are already announce) or of the SSID history announced in the WLAN discovery frames of the UTs that are included in the signatures of the OOID exchanged with the Server Node (103) (coming from other nodes).
  • the mechanism to prioritize, optimize and trigger the announcement of SSIDs could be among others announce first and periodically, until receiving the response of the user terminal (102) in a configurable time frame, those SSIDs coming from the SDK APP (104) of UTs (102) that known by geo-location (which we can call Virtual Node) have entered some coordinates within a configurable radius around the Node (for example 0.5km).
  • a Beacon Node can be responsible for issuing frames by bluetooth according to the protocols Beacon TM and EddyStone TM that through an APP or the Navigator could be detected and through! SDK APP (104) and could generate a Node event (even if it was not generated by the node but by the UT (102) with the information of the Approved OOID if it was known by the UT (102).
  • a direct Push node that allows to include a campaign manager within the node itself (101), avoiding delays in sending messages from the server, and making it the own node (101) e! that manages the sending of messages to the user terminal (102), or even when it has direct communication with the user terminal (102) by proximity through the system designed for that purpose, can call direct functions of the SDK (104, 105) to show the user the message directly (through among other techniques such as local push notifications, PopUps, etc.) without using the available channels of the user terminal (SMS, Push, Email, ..).
  • the Node would receive to the Server Node (103) the tokens of the approved OOIDs as well as any other information related to the campaigns.
  • the node (101) can generate in real time or execution frames of discovery of the WLAN or BT networks, which are normally emitted by the UTs (102), using for this the same addresses of the medium access layer of the recently heard UTs (102), or of those heard by other nodes and that have been received by the propagation process, and also generated randomly with different common patterns similar to those usually received.
  • SDK APP events could be generated (104) to the Server Node (103).
  • the APP SDK (104) could access the address of the middle access layer of the user terminal (102) and, if it is not accessible, a random dID and an uncertified OOIDs would be generated.
  • the OOID is updated with the OOID approved in iocalsiorage, cookies or other means to ensure the persistence of the information accessible to the SDK APP
  • data can be sent to the Server Node - personal or non-personal - that has been provided by the user and collected through the functionality of monitoring the behavior and interaction available, which can serve as communication idols ( ie identifiers in a communication system) among other data such as phone number or email, or social ogin that could serve as tokens for the sending of messages.
  • communication idols ie identifiers in a communication system
  • social ogin ie identifiers in a communication system
  • the Server Node (103) definition information of geo-limited areas or geofence by its name in English, information on campaigns such as its elements and objects, the OUI list of manufacturers, a history of OUIs available before there were randomization processes, and a list of virtual or false OUIs, the list of validated OUIs.
  • Ai receiving external push notifications could manage the collection of notification parameters, so that automatically according to the programming of the campaign could open browsers embedded in the APP or external browsers.
  • a node-type event can be generated (as if a node had detected it by proximity), to have a virtual node at any physical point, and for the activation of the rogue node functionality in the node (101). interrogation:
  • IDFA / GAID signature could be generated, since this is a unique identifier per device accessible only via software from a mobile application. All mobile applications of the same device have the same GAID / IDFA provided by the manufacturer, for advertising use. Likewise, they could be used among other Gender, Date of birth or Zip Code provided by the user directly in the interaction with the APP, to generate a signature based on personal data PiIS ⁇ Signature of Personal Information Identifl cable). This information will be provided and processed by the system in accordance with current legislation. That is, for example, these signatures will not be generated without the prior informed consent of the user, and may be eliminated.
  • MDIA-S multimedia events which include the configuration of activity with players, for example if you have finished watching a video, etc.
  • a WEB-S signature can be obtained in the form of an array of signatures in turn from collecting information from the user terminal (102) according to the capabilities obtained from the WEB, such as, among others, UserAgent, http accept header, or the resolution of screen and depth of color among others.
  • Said information will be supplied and processed by the system according to current legislation. That is, for example, these signatures are not generated without the prior informed consent of the user.
  • non-personal data provided by the user can be used directly in the interaction with the website, to generate a signature based on non-personal data NPI-S (Signature of Non-Personal Information). This information will be provided and processed by the system in accordance with current legislation.
  • NPI-S Signature of Non-Personal Information
  • the WEB SDK (105) could be loaded and techniques for passing parameters in the URL or other techniques , the Approved OOID would be exchanged with the NS.
  • Ei OOi is stored in the / ocalstorage of the browser or in cookies if possible, among other methods.
  • the embedded browser type WebView
  • the OOID homologated with the APP is exchanged.
  • the OOI is stored in the browser's ocalstorage or in cookies if possible, among other methods.
  • the external browser configured by default in the user terminal (102) and pass it as parameters in the URL the approved OOID.
  • the OOI is stored in the! Oca! Storage of the browser or in cookies if possible, among other methods.
  • the server node (103), whose main functions are shown in Figure 9.1, has the following functionalities:
  • the events of the SDK (104, 105) and nodes (101) can be received, stored and processed, using web servers, databases and / or applications.
  • Said behavior analysis system has a series of functionalities that allow, from the events of Node (101) and SDK (104,105) in the server node (103) to calculate or compute visitors, visits and visit is [ 9301], as well as any other indicator or ratio considered of interest from these to obtain the cross-online and offline behavior of the UTs.
  • the nodes (101) Normally the nodes (101) generate events of type Node and the SDK (104,105) of type SDK; but the SDK (104,105) could generate node-type events, when the detection is done by beacon.
  • the nodes (101) could generate SDK type events when the detection is made to connect to a captive portal (an SDK type event is generated). This information will be treated by the behavioral system as if it came from the type of event received.
  • time of the visits analysis windows it is possible to configure the time of the gaps between the so-called visits is (concept analogous to sessions on a website, but applicable to offline and online).
  • the purpose of the analysis window is to decide if an event of type Accepted for the same OOID extends the time of visit or visit of the same visitor.
  • the analysis of events includes configuring: a time of the windows of analysis of visits, where a window of analysis includes a decision on whether an event of type Accepted for the same OOID extends the time of visit or visit of the same visitor , and a time between visits, where said time is defined as elapsed between visits by the same visitor.
  • the analysis window is smaller than the gap and this smaller than a full day. After the time of the gap between visits is, the events are part of a new visit. After the visit or session gap, only the approved or unified events start the period of the analysis window.
  • the validated, unified or accepted valid events received within the period of the analysis window would be grouped in the same visit, and therefore are associated with the same visitor, and therefore of the same visit.
  • the accepted events allow to extend the time of presence of a visit of the same visitor, and therefore also extend the presence of a visit.
  • visits will be extended dynamically as more events arrive within a period of time, thus obtaining the times of presence of a visit in a given area, and analysis of Online or offline behavior could be performed in real time. considering with the data of previously received events, and not in real time analysis with the data of a whole day or a month.
  • a field of application of specific interest for the implementation of the object of the invention is that in which the method described here is complemented by a manager of profiles, campaigns and results such as that shown in Figure 9.4 where the interaction between components is shown. minus the following functions that provide the following functionalities:
  • a profile manager which has among other tasks, calculate profiles or user groups that should receive messages from the server or by proximity when detected by the node (101), based on certain criteria of segmentation or behavior grouping, or You can also import / upload ios 00! D of the UTs (102) from an external behavior analysis platform.
  • the profile management system could calculate or compute which UTs (102) have the same cross-online and offline behavior profile, as well as any other marketing indicator such as a key performance indieator (KPI) that is considered of interest from these data, an example of KPI can be the number of times that on average, visitors with a family profile repeat visits in a month.
  • KPI key performance indieator
  • a profile that could be called family type would be those devices that yesterday generated a visit to the website of a children's store in the shopping center, today they have opened the APP of the shopping center to visit the cinema billboard looking for a children's movie and they have also been detected by a node with a visit presence of more than 5 minutes in the shopping area of the shopping center.
  • Another example of crossed profile definition online and offline would be those who usually arrive at the office more than 10 minutes before the time of entry and have ever used the corporate APP of the company to reserve meeting rooms.
  • responses to the messages received may be included, for example, a profile of employees in active training would be those employees who receive messages when they receive messages. Inviting them to attend face-to-face courses, they finally go to the classroom where this in-person course is held.
  • a system for triggering messages by physical or digital proximity based on when a device is detected through a Node event (101) in addition to generating a valid and homologated visit in real time by the behavior system, at this time it is checked if the OOID is included in an active profile and an active campaign, and a message is sent immediately through the campaign manager so that it can be read in real time to the user terminal (102) by any of the channels available
  • This system could, among other functions, send the messages to the UTs (102) programmed at the opportune moment according to the information programmed in the campaign manager when receiving Node (101), Virtual Node (103) or SDK (104,105) events. ) among other trigger events. That is, by proximity or visit a physical site or a digital site.
  • the Approved or Non-Approved OOIDs can be linked to each User entity (that is, the entity that stores said communication idols and other personal data) in the server Node (103). Although a user terminal (102) does not have an approved OOID, it can receive messages from the server node (103), but it would need the validated and validated OOID to push messages by proximity to the node (101).
  • the campaign manager could generate or pre-load the contents and formats of the messages for the different channels chosen, as well as dates, zones, online sites, and any other variable useful for the definition of the campaign. It is planned to launch the campaigns and messages in the moment programmed in e! campaign manager the messages to the programmed UTs (102). That is, by time and profile; It is also planned to import campaigns and messages from third parties through webservices or other procedures, to complete the functionality of the campaign manager.
  • the results manager collects the confirmation information in sending messages from the proxies of each channel, the answers associated with the digital spaces that have been used in the communication (filling in the form, personal data, surveys, subscriptions, etc ..), as well as its behavior in the physical and digital space after the sending of coupons, offers, information, surveys, other ways to suggest visiting physical or digital sites, etc ... Therefore, it would be able to calculate for example how many users who have received an offer by email on Friday afternoon, have been detected in the supermarket during Saturday morning.
  • the information of the campaign manager can be updated.
  • the results manager in addition to reporting efficiency data, can act as a feedback loop to modify profiles and campaigns in real time, achieving a dynamic optimization based on the user's response
  • the system makes it possible to do what is known as remarketing but offline, which consists of sending a message to the user terminal (102) by proximity or offline presence, knowing previously their tastes or interests through digital behavior analyzed, for example in the APPs or WEB sites that have the SDK integrated, or through the physical behavior analyzed in the areas where there are nodes, and even based on responses to previously sent communications.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Finance (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un système et un procédé destinés à réaliser la détermination et l'attribution d'un identificateur unique de dispositifs électroniques, tels que des terminaux mobiles ou des smartphones. Ledit procédé permet de déterminer et d'attribuer l'identificateur unique de dispositifs électroniques au moyen d'un système qui met en oeuvre, dans son architecture, une série de dispositifs appelés noeuds qui agissent de manière à leur faire écouter certaines bandes des émissions radio générées par les terminaux mobiles voisins et situés dans une zone précise. À partir de ces écoutes, ils peuvent générer ledit identificateur unique et, une fois ce dernier homologué, le propager dans le système.
PCT/ES2017/070809 2017-12-12 2017-12-12 Système et procédé d'identification unique de dispositifs électroniques Ceased WO2019115842A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
ES202090021A ES2855199B2 (es) 2017-12-12 2017-12-12 Sistema y metodo de identificacion unica de dispositivos electronicos
PCT/ES2017/070809 WO2019115842A1 (fr) 2017-12-12 2017-12-12 Système et procédé d'identification unique de dispositifs électroniques

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/ES2017/070809 WO2019115842A1 (fr) 2017-12-12 2017-12-12 Système et procédé d'identification unique de dispositifs électroniques

Publications (1)

Publication Number Publication Date
WO2019115842A1 true WO2019115842A1 (fr) 2019-06-20

Family

ID=66819574

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/ES2017/070809 Ceased WO2019115842A1 (fr) 2017-12-12 2017-12-12 Système et procédé d'identification unique de dispositifs électroniques

Country Status (2)

Country Link
ES (1) ES2855199B2 (fr)
WO (1) WO2019115842A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060221846A1 (en) * 2005-03-18 2006-10-05 Dyck Jeffrey A Dynamic media access control (MAC) address assignment
US20140244386A1 (en) * 2013-02-26 2014-08-28 Facebook, Inc. Targeting advertisements to logged out users of an online system
WO2014205262A2 (fr) * 2013-06-20 2014-12-24 Aol Advertising Inc. Systèmes et procédés de synchronisation d'identifiants (id) de publicité entre navigateurs
US20150324635A1 (en) * 2014-04-30 2015-11-12 Eye Stalks Corporation Dba Bay Sensors Methods, systems, and apparatuses for visitor monitoring
US20160225009A1 (en) * 2015-01-29 2016-08-04 Yext, Inc. Permitting a business with physical locations to connect with their customers on their mobile devices (retap)
US20170140434A1 (en) * 2015-11-18 2017-05-18 Yu-Shun Lin Advertisement and message pushing system
US20170149741A1 (en) * 2014-04-18 2017-05-25 Locality Systems Inc. Source Based Anonymity and Segmentation for Visitors

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060221846A1 (en) * 2005-03-18 2006-10-05 Dyck Jeffrey A Dynamic media access control (MAC) address assignment
US20140244386A1 (en) * 2013-02-26 2014-08-28 Facebook, Inc. Targeting advertisements to logged out users of an online system
WO2014205262A2 (fr) * 2013-06-20 2014-12-24 Aol Advertising Inc. Systèmes et procédés de synchronisation d'identifiants (id) de publicité entre navigateurs
US20170149741A1 (en) * 2014-04-18 2017-05-25 Locality Systems Inc. Source Based Anonymity and Segmentation for Visitors
US20150324635A1 (en) * 2014-04-30 2015-11-12 Eye Stalks Corporation Dba Bay Sensors Methods, systems, and apparatuses for visitor monitoring
US20160225009A1 (en) * 2015-01-29 2016-08-04 Yext, Inc. Permitting a business with physical locations to connect with their customers on their mobile devices (retap)
US20170140434A1 (en) * 2015-11-18 2017-05-18 Yu-Shun Lin Advertisement and message pushing system

Also Published As

Publication number Publication date
ES2855199B2 (es) 2024-11-15
ES2855199A1 (es) 2021-09-23

Similar Documents

Publication Publication Date Title
US10972888B2 (en) IOT devices based messaging systems and methods
KR102098428B1 (ko) 네트워크 결정식 위치에 기초한 그룹 연관
US8989094B2 (en) Systems and methods for generating and displaying application information on a wireless station
CN104113861B (zh) 用于管理无线网络中的内容互换的方法及系统
US10506367B2 (en) IOT messaging communications systems and methods
Barsocchi et al. COVID-19 & privacy: Enhancing of indoor localization architectures towards effective social distancing
US11706184B2 (en) Space time region based communications
US10057302B2 (en) Context-based selection of instruction sets for connecting through captive portals
CN107454126A (zh) 一种消息推送方法、服务器及终端
ES2855199B2 (es) Sistema y metodo de identificacion unica de dispositivos electronicos
Almathami et al. An Analytical Approach to Using and Implementing Beacons: Opportunities and Challenges.
Wu et al. A CICO system based on BLE proximity
Mndebele et al. IoT based proximity marketing
US20170063754A1 (en) Method and system for anonymous and secure social linking during an event
da Silva A tourism overcrowding sensor using multiple radio techniques detection
Namiot et al. Social streams based on network proximity
Gong et al. LBSLab: a user data collection system in mobile environments
dos Santos Smart Tourism Toolkit for Crowd-Monitoring Solutions
Borić et al. Space occupancy through ble dynamic broadcasting
Armando et al. Exploring approaches to the management of physical, virtual, and social sensors
Delzanno et al. Physical Web for Smart Campus Management.
Namiot et al. On hyper-local web pages
Weliwita RSSI Based Real-time and Secure Parking Management System
Ruiz et al. Evaluation of cloud platforms for managing IoT devices
Bucur¹ et al. Taxi Application over Peer-to-Peer

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17934847

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 13.10.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17934847

Country of ref document: EP

Kind code of ref document: A1