WO2017010679A1 - Dispositif et procédé de transfert de témoins de connexion - Google Patents

Dispositif et procédé de transfert de témoins de connexion Download PDF

Info

Publication number
WO2017010679A1
WO2017010679A1 PCT/KR2016/005679 KR2016005679W WO2017010679A1 WO 2017010679 A1 WO2017010679 A1 WO 2017010679A1 KR 2016005679 W KR2016005679 W KR 2016005679W WO 2017010679 A1 WO2017010679 A1 WO 2017010679A1
Authority
WO
WIPO (PCT)
Prior art keywords
time
client
bridge
server
cookies
Prior art date
Application number
PCT/KR2016/005679
Other languages
English (en)
Korean (ko)
Inventor
박형배
전선민
이윤석
공경필
Original Assignee
주식회사 수산아이앤티
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 주식회사 수산아이앤티 filed Critical 주식회사 수산아이앤티
Publication of WO2017010679A1 publication Critical patent/WO2017010679A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the following embodiments are directed to an apparatus and method for storing the same cookie in different web browsers when using different web browsers in one client.
  • HTTP hyper? Text? Transfer? Protocol
  • HTTP is a request and response method that does not maintain a connection. For example, if you log in to a shopping mall at the login screen and do the next action (for example, clicking on a particular product), an http request for this action is sent back to the server, which is the same as the previous communication. It is not known whether the communication is a communication connection from the same terminal. Therefore, the web server uses a cookie (including a flash cookie) for managing the login status.
  • Web servers use cookies to maintain information about users who have previously accessed them and to provide services using them. Web serving does not distinguish between the same users using different browsers. It is difficult for users to provide continuous services between different browsers through cookies.
  • Korean Patent No. 0960152 has been proposed, "a method for allowing and blocking the Internet by detecting a plurality of terminals on a network".
  • a method for allowing and blocking the Internet by detecting a plurality of terminals on a network by analyzing a TCP / IP packet and redirecting a session connecting to the web, using a cookie in a private network sharing a plurality of terminals to determine the number of a plurality of PC terminals of the client, Users who use the Internet to detect and DB the number of PC terminals of clients using the Internet, and use the DB pooled cookie pool information and jobs to construct a private network.
  • a technology for selectively allowing or blocking access based on TCP / IP when accessing the Internet has been disclosed.
  • the above-mentioned prior art also uses a cookie, so it is not possible to distinguish a case of using different browsers in one terminal, and the cookie may be deleted or changed by the user.
  • the present invention has been made to solve the above problems of the prior art, and an object of the present invention is to provide a method for storing the same cookie value in another web browser through a cookie bridge even when a different client uses a different web browser. It is done.
  • the present invention measures the server-side time and client-side time, classifies the clients using a time marker indicating the difference between the server-side time and the client-side time, and if the classification results in the same client, even if the web browser is different Its purpose is to provide a way to store cookie values.
  • a method of bridging a cookie in a bridge server mirrors the packet transmitted from the client to detect the occurrence of traffic, the server side time of the traffic and the client Measuring side time; Calculating a timemarker indicating a difference between the server side time and the client side time; Classifying clients using the timemarker; Checking authentication information of the classified client; And storing the authentication information as a cookie value of the client.
  • the measuring of the server side time and the client side time may include: receiving a packet transmitted from a client when the traffic occurs; Generating a fake response packet for the packet and transmitting it to the client; Storing a time when transmitting the fake response packet as a start time included in the server side time; And receiving the client side time from the client receiving the fake response packet.
  • the fake response packet may check the time of the client to respond to the bridge server specified in the fake response packet.
  • the measuring of the server side time and the client side time may include a server time when the client side time is received from the client receiving the fake response packet as an end time included in the server side time.
  • the method may further include storing.
  • the calculating of the time marker may be performed by calculating the difference between the end time and the client side time or by the difference between the start time and the client side time.
  • the classifying the client using the time marker may include: comparing the time markers of the traffic and classifying the traffic whose one time difference is within a predetermined variation error into one subset; And classifying each of the subsets into one client.
  • NTP Network Time Protocol
  • the classifying the client by using the time marker may include: when the difference between the earliest time and the latest time among server-side times of the traffic included in the subset is less than a predetermined reference time, classifying the subset from the client classification. Can be excluded.
  • the subset in the step of classifying a client by using the time marker, may be excluded from the client classification when a preset threshold time since the last traffic included in the subset is exceeded.
  • classifying a client by using the time marker may include: calculating a response time of each of the traffic before classifying the subset; And excluding traffic having a response time exceeding a preset overrun time without classifying the subset.
  • the number of clients may be counted using additional information together with the time marker.
  • the additional information may be at least one of an Internet cookie, a flash cookie, user agent information, screen resolution information, or browser finger print information.
  • the checking of the authentication information of the classified client includes checking whether the authentication information corresponding to the time marker exists and if so, confirming the confirmed authentication information as the authentication information of the classified client, and checking the time marker. If the corresponding authentication information does not exist, the authentication information corresponding to the time marker may be generated and stored and confirmed as authentication information of the classified client.
  • the authentication information is generated using the time marker or the authentication information is generated using the time marker and additional information, wherein the additional information is an internet cookie, a flash cookie, a user agent. ) Information, screen resolution information, or browser finger print information.
  • the present invention measures server-side time and client-side time, classifies clients using time markers representing the difference between server-side time and client-side time.
  • the present invention relates to a technology for storing the same cookie value even if the agreed client uses different web browsers.
  • FIG. 1 is a diagram illustrating a schematic configuration of a system for performing a cookie bridge through mirroring according to an embodiment.
  • FIG. 2 is a flowchart illustrating a schematic process of cookie bridge in a bridge device according to an embodiment.
  • FIG. 3 is a flowchart illustrating a process of measuring a server side time and a client side time in a bridge device according to an embodiment.
  • FIG. 4 is a flowchart illustrating a process of classifying a client in a bridge device according to an exemplary embodiment.
  • FIG. 5 illustrates an example of JavaScript included in a fake response packet according to an exemplary embodiment.
  • FIG. 6 is a diagram illustrating an example of calculating a time marker according to an embodiment.
  • FIG. 7 is a diagram illustrating an example of storing a server side time and a client side time of traffic according to an exemplary embodiment.
  • FIG. 8 is a diagram illustrating an example of authentication information generated using a time marker and additional information according to an embodiment.
  • FIG. 1 is a diagram illustrating a schematic configuration of a system for performing a cookie bridge through mirroring according to an embodiment.
  • a system for bridging cookies may include a cookie bridge device 110, clients 122, 124, and 126, and a router 130.
  • the cookie bridge device 110 may be configured to include a bridge server 112 and a key management server 114.
  • the bridge server 112 may be a cookie authentication server (CAS).
  • the clients 122, 124, and 126 may be connected to the router 130 or the router when accessing the Internet 100.
  • the clients 122, 124, and 126 may be connected to the router 130 or the router to enable network connection and data transmission.
  • the plurality of clients 122, 124, and 126 may be connected to the Internet.
  • the client may be a terminal such as a PC or a smart phone.
  • the router 130 may be used as a network address translation (NAT).
  • the bridge server 112 mirrors and receives the packets transmitted from the clients 122, 124, and 126, and generates a fake response packet for the mirrored packets and transmits them to the client.
  • the fake response packet may include a java script for checking the time of the client as shown in FIG. 5 below, and may check the client side time to respond to the server specified in the fake response packet.
  • the clients 122, 124, and 126 When the clients 122, 124, and 126 receive the fake response packet, they check the client side time, respond to the server specified in the fake response packet, and redirect the packet corresponding to the traffic. At this time, the bridge server 112 does not generate a fake response packet for the redirected packet.
  • the bridge server 112 stores the time when the fake response packet is transmitted as a start server time (ST), and the client side time (from the clients 122, 124, and 126 that received the fake response packet).
  • ST start server time
  • client side time from the clients 122, 124, and 126 that received the fake response packet.
  • CT start server time
  • ET End Server Time
  • the start time and end time correspond to the server side time.
  • FIG. 5 illustrates an example of JavaScript included in a fake response packet according to an exemplary embodiment.
  • the JavaScript included in the fake response packet sets the client-side time in years, months, days, hours, minutes, seconds, and milliseconds. Check up to millisecond units.
  • bridge server 112 calculates a time marker indicating the difference between the server side time and the client side time.
  • the server-side time may include a start time (ST) and an end time (ET)
  • the bridge server 112 calculates the time marker as the difference between the end time and the client-side time, or the difference between the start time and the client-side time. Can be calculated
  • FIG. 6 is a diagram illustrating an example of calculating a time marker according to an embodiment.
  • the bridge server 112 and the clients 122, 124, and 126 have different times.
  • NTP Network Time Protocol
  • the bridge server 112 and the clients 122, 124, and 126 have different times set.
  • the server side time of the bridge server 112 is 11:00
  • the client side time of the client 122 is 11:01
  • the client side time of the client 124 is 11:05
  • the client side time of client 126 is 11:08.
  • the time difference corresponding to the time marker of the bridge server 112 and the client 122 is 1 minute, and the bridge server 112 and the client 124 are different. It can be seen that the time difference corresponding to the time marker of 5 minutes, the time difference corresponding to the time markers of the bridge server 112 and the client 128 is 8 minutes.
  • the time marker is expressed in minutes to help understand the description. However, in the actual embodiment of the present invention, the time marker is divided into milliseconds.
  • the bridge server 112 sends a fake response time to the client and calculates the response time, which is the time taken to receive the client side time response from the client.
  • the bridge server 112 may calculate the response time by subtracting the start time from the end time.
  • the bridge server 112 determines that traffic having a response time exceeding a preset overrun time is traffic when the communication state of the network is not smooth, and excludes it from data counting the number of clients. do.
  • the preset overrun may be set by the following method.
  • the network collects data for a certain period of time, calculates an average of response times for data within a 95% confidence level, and sets the calculated average response time to a preset overrun.
  • the average response time for the data within the 95% confidence level can be calculated, and the calculated average response time can be set to a preset overrun.
  • the bridge server 112 compares the time markers of the traffic, classifies the traffic whose time marker difference is within a predetermined variation error into one subset, and classifies each subset as one client.
  • the variation error may measure the client side time for a certain period (for example, one day) with respect to the same client, and select the maximum value among the error values of the change amount of the client side time per hour as the “variation error”.
  • the bridge server 112 may measure the client side time in units of 1 hour, calculate the difference between the measured client side times, and select the maximum value as the variation error.
  • the variation error was appropriate for 200 milliseconds. However, since the variation error may vary from device to device, it may vary.
  • FIG. 7 is a diagram illustrating an example of storing a server side time and a client side time of traffic according to an exemplary embodiment.
  • FIG. 7 illustrates an example of data stored by the bridge server 112 in order to count the number of clients according to traffic.
  • the bridge server 112 receives a packet from the client, the request URL is shown. 710 and IP 720 are stored, a fake response packet is generated and transmitted, and a start time (ST) 760 which is a time designated in the fake response packet is stored.
  • ST start time
  • the client side time (CT) 750 is received from the client and stored, and the end time (ET) 770 which is the time of the bridge server 112 at the time of receiving the client side time (CT) 750 is stored. Save it.
  • the difference between the start time (ST) 760 and the client side time (CT) 750 or the difference between the client side time (CT) 750 and the end time (ET) 770 is calculated to calculate the time marker.
  • the difference between the end time (ET) 770 and the side time (CT) 750 may be calculated and stored as the response time (RT) 740.
  • traffic whose value of the response time (RT) 740 of FIG. 7 exceeds 100 may be excluded from the data for classifying the client.
  • the clients 122, 124, and 126 may perform NTP (Network Time Protocol) to reset the client's time at regular intervals (for example, once a week).
  • NTP Network Time Protocol
  • Time marker values before and after NTP synchronization may be different for the same client. In general, time marker values tend to increase after NTP synchronization.
  • the bridge server 112 may consider a case where the time setting of the client is changed by NTP (Network Time Protocol).
  • NTP Network Time Protocol
  • the bridge server 112 calculates a subset by calculating time markers before and after NTP synchronization, and compares the time markers between the subsets to determine a subset having changed time setting. This can be considered when classifying clients.
  • the bridge server 112 may monitor the NTP packet transmitted by the clients 122, 124, and 126 to confirm the occurrence of NTP synchronization of the client, and if the destination port number is 123 through UDP, NTP Can be determined by the packet.
  • the bridge server 112 classifies traffic within a predetermined variation error into a subset, and then selects the fastest time among server-side times of the traffic included in the subset. If the difference in the latest time is less than the preset reference time, the subset can be excluded from the count. This is to classify only clients that have operated over a predetermined reference time.
  • the bridge server 112 may classify the traffic within a predetermined variation error into one subset, and then exclude the subset when the predetermined threshold time has been exceeded since the last traffic included in the subset. . This is to exclude clients that have not communicated for longer than a threshold (i.e. have not communicated for a long time).
  • the bridge server 112 may determine the client using additional information together with the time marker as another method of improving the accuracy of classifying the clients.
  • the additional information may include at least one of an internet cookie, a flash cookie, user agent information, screen resolution information, or browser finger print information.
  • the bridge server 112 confirms the authentication information (AI) of the classified client and stores the authentication information as a cookie value of the client. Since the bridge server 112 stores the authentication information corresponding to each client classified by the time marker as a cookie value, using the stored authentication information, the bridge server 112 may maintain the same cookie value even if different browsers are used by the same client. .
  • the bridge server 112 inquires of the key management server 124 whether authentication information corresponding to the time marker exists, and if authentication information corresponding to the time marker exists, the verified authentication information is used as the authentication information of the classified client. Check it.
  • the bridge server 112 generates authentication information corresponding to the time marker and provides it to the key management server 124 for storage. Then, the generated authentication information is confirmed as the authentication information of the classified client.
  • the bridge server 112 may generate the authentication information using the time marker or generate the authentication information using the time marker and additional information.
  • the additional information may be at least one of an internet cookie, a flash cookie, user agent information, screen resolution information, or browser finger print information.
  • FIG. 1 illustrates the key management server 114 and the bridge server 112 separately, the key management server 114 may be configured to be included in the bridge server 112.
  • the bridge server 112 may also perform all operations of the key management server 114.
  • FIG. 2 is a flowchart illustrating a schematic process of cookie bridging in a bridge server according to an exemplary embodiment.
  • the bridge server mirrors the packet transmitted from the client, detects the occurrence of traffic, and measures the server side time and the client side time (210). A detailed method of measuring the server side time and the client side time will be described later with reference to FIG. 3.
  • the bridge server then calculates 220 a time marker representing the difference between the server side time and the client side time.
  • the bridge server classifies the client using the time marker (230). A detailed method of classifying clients using the time marker will be described later with reference to FIG. 4.
  • the bridge server checks the authentication information of the classified client (240).
  • the bridge server checks whether the authentication information corresponding to the time marker exists and if the authentication information exists, confirms the verified authentication information as the authentication information of the classified client.
  • the bridge server generates and stores authentication information corresponding to the time marker, and confirms the generated authentication information as the authentication information of the classified client.
  • the bridge server may generate the authentication information using the time marker or generate the authentication information using the time marker and additional information as shown in FIG. 8 below.
  • FIG. 8 is a diagram illustrating an example of authentication information generated using a time marker and additional information according to an embodiment.
  • the authentication information 800 generated by the bridge server may be generated using only a time marker 810, but may be generated by further including additional information as in the example of FIG. 8. .
  • the additional information may be selected from among Internet cookie 820, flash cookie, user agent (UA) information 830, screen resolution information 840, or browser finger print 850 information. There may be at least one.
  • the bridge server stores the authentication information as a cookie value (250). Since the bridge server stores the authentication information corresponding to each client classified by the time marker as the cookie value, the stored authentication information may maintain the same cookie value even if different browsers are used by the same client.
  • FIG. 3 is a flowchart illustrating a process of measuring a server side time and a client side time in a bridge server according to an exemplary embodiment.
  • the bridge server when traffic is generated, the bridge server mirrors and receives a packet transmitted from a client (310).
  • the bridge server When the bridge server receives the packet, the bridge server generates a fake response packet for the packet and transmits it to the client (320). At this time, the fake response packet checks the time of the client to respond to the bridge server specified in the fake response packet.
  • the client After receiving the fake response packet, the client checks the client side time, responds to the server specified in the fake response packet, and redirects the packet corresponding to the traffic. At this time, the server does not generate a fake response packet for the redirecting packet.
  • the bridge server stores the time when the fake response packet is transmitted as a start time included in the server side time (330).
  • the bridge server receives the client-side time from the client receiving the fake response packet (340).
  • the bridge server stores the time of the server when receiving the client-side time from the client receiving the fake response packet as the end time included in the server-side time (350).
  • the server side time may include a start time and an end time. Therefore, the time marker calculated as the difference between the server side time and the client side time may be calculated as the difference between the end time and the client side time, or may be calculated as the difference between the start time and the client side time.
  • FIG. 4 is a flowchart illustrating a process of classifying a client in a bridge server according to an exemplary embodiment.
  • the bridge server calculates a response time of each traffic (410).
  • the response time may be calculated by subtracting the start time from the end time included in the server side time.
  • the bridge server excludes traffic having a response time exceeding a preset overrun time without classifying it into a subset (420). If the overrun time is exceeded, it is determined that a delay has occurred because the communication status of the network is not smooth, and the corresponding traffic is excluded from the data for counting the number of clients.
  • the bridge server compares the time markers of the traffic and classifies the traffic whose time marker difference is within a predetermined variation error into one subset (430).
  • the bridge server then classifies each subset into one client (440).
  • the client may perform the Network Time Protocol (NTP) to reset the time of the client at regular intervals (for example, once a week).
  • NTP Network Time Protocol
  • Time marker values before and after NTP synchronization may be different for the same client. In general, time marker values tend to increase after NTP synchronization.
  • the bridge server when classifying a client, the bridge server preferably considers a case where the client's time setting is changed by NTP (Network Time Protocol).
  • NTP Network Time Protocol
  • the bridge server calculates the time marker before and after NTP synchronization to obtain a subset by considering the case where the time setting is changed, compares the time markers between the subsets, determines the subset that has changed the time setting, and classifies the clients. Can be considered when
  • the bridge server may monitor the NTP packet transmitted by the client to check the occurrence of NTP synchronization of the client, and may determine the NTP packet when the destination port number is 123 through UDP.
  • the bridge server excludes the subset from the client classification if the difference between the fastest time and the latest time among the server-side time of the traffic included in the subset is less than the predetermined reference time. can do.
  • the bridge server may exclude the subset from the client classification when the predetermined threshold time has been exceeded since the last traffic included in the subset.
  • the client may be classified using additional information together with a time marker.
  • the additional information may include at least one of an internet cookie, a flash cookie, user agent information, screen resolution information, or browser finger print information.
  • the cookie bridge method may be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer readable medium.
  • the computer readable medium may include program instructions, data files, data structures, etc. alone or in combination.
  • Program instructions recorded on the media may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts.
  • Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks.
  • Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.
  • the hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)

Abstract

La présente invention concerne un dispositif et un procédé de transfert de témoins de connexion, caractérisés en ce que le temps d'un côté serveur et le temps d'un côté client sont mesurés lorsqu'un trafic a lieu, des clients sont classifiés au moyen d'un marqueur de temps indiquant le différentiel entre le temps du côté serveur et le temps du côté client et, si le résultat de classification indique que les clients sont les mêmes, une valeur identique de témoin de connexion est mémorisée même si les navigateurs de la toile diffèrent.
PCT/KR2016/005679 2015-07-15 2016-05-30 Dispositif et procédé de transfert de témoins de connexion WO2017010679A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020150100580A KR101661858B1 (ko) 2015-07-15 2015-07-15 쿠키 브리지 장치 및 방법
KR10-2015-0100580 2015-07-15

Publications (1)

Publication Number Publication Date
WO2017010679A1 true WO2017010679A1 (fr) 2017-01-19

Family

ID=57079566

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/005679 WO2017010679A1 (fr) 2015-07-15 2016-05-30 Dispositif et procédé de transfert de témoins de connexion

Country Status (2)

Country Link
KR (1) KR101661858B1 (fr)
WO (1) WO2017010679A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019017544A1 (fr) * 2017-07-17 2019-01-24 비씨카드(주) Procédé de fourniture de service d'authentification d'utilisateur, serveur web et terminal utilisateur
CN111031086A (zh) * 2019-10-08 2020-04-17 安徽华博胜讯信息科技股份有限公司 一种区块链数据存储方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100088411A1 (en) * 2006-10-27 2010-04-08 Cyscape, Inc. Method and apparatus for determining application responsiveness over a network
KR101018817B1 (ko) * 2008-06-24 2011-03-04 주식회사 이베이지마켓 웹페이지 표시를 위한 클라이언트 단말, 유무선망을 통한 클라이언트 단말의 웹페이지 표시 방법
US20140101236A1 (en) * 2012-10-04 2014-04-10 International Business Machines Corporation Method and system for correlation of session activities to a browser window in a client-server environment
US20140108092A1 (en) * 2012-07-13 2014-04-17 Trueffect, Inc. Enhanced adserving metric determination
US20150046562A1 (en) * 2013-08-07 2015-02-12 Convergent Development Limited Web browser orchestration

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050187934A1 (en) * 2004-02-24 2005-08-25 Covelight Systems, Inc. Methods, systems and computer program products for geography and time monitoring of a server application user
KR100960152B1 (ko) * 2007-10-24 2010-05-28 플러스기술주식회사 네트워크상의 복수 단말을 검출하여 인터넷을 허용 및차단하는 방법
KR101616402B1 (ko) * 2015-03-23 2016-04-28 주식회사 제이넷 회선공유단말 구별 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100088411A1 (en) * 2006-10-27 2010-04-08 Cyscape, Inc. Method and apparatus for determining application responsiveness over a network
KR101018817B1 (ko) * 2008-06-24 2011-03-04 주식회사 이베이지마켓 웹페이지 표시를 위한 클라이언트 단말, 유무선망을 통한 클라이언트 단말의 웹페이지 표시 방법
US20140108092A1 (en) * 2012-07-13 2014-04-17 Trueffect, Inc. Enhanced adserving metric determination
US20140101236A1 (en) * 2012-10-04 2014-04-10 International Business Machines Corporation Method and system for correlation of session activities to a browser window in a client-server environment
US20150046562A1 (en) * 2013-08-07 2015-02-12 Convergent Development Limited Web browser orchestration

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019017544A1 (fr) * 2017-07-17 2019-01-24 비씨카드(주) Procédé de fourniture de service d'authentification d'utilisateur, serveur web et terminal utilisateur
CN111031086A (zh) * 2019-10-08 2020-04-17 安徽华博胜讯信息科技股份有限公司 一种区块链数据存储方法及系统

Also Published As

Publication number Publication date
KR101661858B1 (ko) 2016-09-30

Similar Documents

Publication Publication Date Title
US8176178B2 (en) Method for tracking machines on a network using multivariable fingerprinting of passively available information
WO2015194829A2 (fr) Procédé de détection d'un certain nombre de dispositifs sélectionnés parmi une pluralité de terminaux clients dans un réseau privé à l'aide du même ip public par un serveur web doté d'un nom de domaine non spécifié supplémentaire à partir d'un trafic de demandes d'accès à l'internet du terminal client faisant une demande d'accès à l'internet, et système de détection sélective pour un dispositif dans un état dans lequel un ip public est partagé
WO2016006520A1 (fr) Dispositif de détection, procédé de détection et programme de détection
US20060198313A1 (en) Method and device for detecting and blocking unauthorized access
WO2013002538A2 (fr) Procédé et appareil destinés à empêcher une attaque de déni de service distribuée
US20050044213A1 (en) Network traffic measurement system
WO2018090544A1 (fr) Procédé et dispositif de détection d'une attaque dos/ddos, serveur et support de stockage
WO2015102446A1 (fr) Procédé de détection de connexion de dérivation par l'intermédiaire d'un réseau anonyme à l'aide des changements dans les temps de propagation aller-retour
KR20090041752A (ko) 네트워크상의 복수 단말을 검출하여 인터넷을 허용 및차단하는 방법
JP5593944B2 (ja) 判定装置、判定方法及びコンピュータプログラム
WO2017010679A1 (fr) Dispositif et procédé de transfert de témoins de connexion
WO2011065692A2 (fr) Système de mesure du temps de réponse d'un serveur au moyen d'étiquettes de demande fictive et procédé pour ce système
KR101087291B1 (ko) 인터넷을 사용하는 모든 단말을 구분하는 방법 및 시스템
CN110838949A (zh) 一种网络流量日志记录方法及装置
KR101518470B1 (ko) 인터넷 접속 요청을 하는 클라이언트 단말의 인터넷 접속 요청 트래픽으로부터 동일한 공인 ip를 이용하는 사설 네트워크상의 복수개의 클라이언트 단말 중에서 웹서버에 의해 선별된 디바이스의 대수를 검출하는 방법 및 공인 ip 공유 상태의 디바이스의 선별적인 검출 시스템
WO2017010678A1 (fr) Procédé pour compter des clients utilisant une adresse ip partagée
US20040233849A1 (en) Methodologies, systems and computer readable media for identifying candidate relay nodes on a network architecture
WO2015174742A1 (fr) Procédé de détection de nombre de dispositifs utilisant le même ip public parmi de multiples terminaux clients d'un réseau privé, à partir d'un trafic de demande d'accès à internet depuis des terminaux clients demandant un accès à internet, et système de détection d'état de partage d'ip public
KR102119636B1 (ko) 수동 핑거프린팅을 이용한 익명 네트워크 분석 시스템 및 방법
US10735293B2 (en) Method and network monitoring device for estimating web page download time on a user device
KR101518469B1 (ko) 인터넷 접속 요청을 하는 클라이언트 단말의 인터넷 접속 요청 트래픽으로부터 동일한 공인 ip를 이용하는 사설 네트워크상의 복수개의 클라이언트 단말 중에서 선별된 디바이스의 대수를 검출하는 방법 및 공인 ip 공유 상태의 디바이스의 선별적인 검출 시스템
WO2011126254A2 (fr) Dispositif de terminal et procédé de confirmation de distributeur de fichier dudit dispositif de terminal
WO2015174644A1 (fr) Système d'envoi de publicité à un terminal d'utilisateur via un routeur sans fil, et serveur de fourniture de service de publicité
WO2021002485A1 (fr) Dispositif de sécurité de base de données basé sur une identification d'utilisateur par le biais d'un serveur d'application web
WO2019221346A1 (fr) Procédé d'inspection de réseau effectuant un stockage de paquets et système permettant de mettre en œuvre ce procédé

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: 16824596

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16824596

Country of ref document: EP

Kind code of ref document: A1