WO2016206209A1 - 请求处理方法及装置 - Google Patents

请求处理方法及装置 Download PDF

Info

Publication number
WO2016206209A1
WO2016206209A1 PCT/CN2015/090604 CN2015090604W WO2016206209A1 WO 2016206209 A1 WO2016206209 A1 WO 2016206209A1 CN 2015090604 W CN2015090604 W CN 2015090604W WO 2016206209 A1 WO2016206209 A1 WO 2016206209A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
camera
account corresponding
data collected
request
Prior art date
Application number
PCT/CN2015/090604
Other languages
English (en)
French (fr)
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 小米科技有限责任公司
Priority to MX2016006176A priority Critical patent/MX358468B/es
Priority to KR1020167012301A priority patent/KR101797416B1/ko
Priority to RU2016121598A priority patent/RU2660625C2/ru
Priority to JP2016518074A priority patent/JP6268282B2/ja
Publication of WO2016206209A1 publication Critical patent/WO2016206209A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/51—Indexing; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101—Access control lists [ACL]
    • 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/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N23/00—Cameras or camera modules comprising electronic image sensors; Control thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
    • H04N7/183—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast for receiving images from a single remote source
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security

Definitions

  • the present disclosure relates to the field of smart homes, and in particular, to a request processing method and apparatus.
  • the smart camera is one of the important components in the smart home.
  • the camera data collected by the smart camera can be pushed to the monitoring terminal such as the user's smart phone for the user to view.
  • the smart camera owner account can share the usage rights of the camera to the designated account through the mobile phone client.
  • the server After being shared to obtain the permission, the server initiates a request to watch the live video recording of the camera. After the verification is passed, the camera will send the compressed real-time video stream data to the mobile phone client that logs in to the account, and the client software can display the video content after decompressing.
  • the present disclosure provides a request processing method and apparatus.
  • the technical solution is as follows:
  • a request processing method comprising:
  • the first prompt information is pushed to the second terminal bound to the camera, where the first prompt information is used to prompt the The camera data is accessed abnormally.
  • the method further includes:
  • the second prompt information is pushed to the third terminal; the third terminal performs maintenance and management on the camera data collected by the camera.
  • the second prompt information is used to prompt whether to track the first terminal.
  • the query request includes an account corresponding to the first terminal; and the request is according to the query. Determining whether the account corresponding to the first terminal has the right to acquire the camera data collected by the camera, including:
  • the access permission list includes an account corresponding to each terminal having the right to acquire data collected by the camera;
  • the account corresponding to the first terminal does not exist in the access permission list, it is determined that the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera.
  • the method before receiving the query request sent by the first terminal, the method further includes:
  • the method further includes:
  • a request processing apparatus comprising:
  • a query request receiving module configured to receive a query request sent by the first terminal, where the query request is used to request to query camera data collected by the camera, where the image data includes image data and/or video data;
  • a determining module configured to determine, according to the query request, whether an account corresponding to the first terminal has the right to acquire camera data collected by the camera;
  • the first prompting module is configured to: if the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera, push the first prompt information to the second terminal bound to the camera, where the A prompt message is used to prompt the camera data to be accessed abnormally.
  • the device further includes:
  • a second prompting module configured to: if the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera, push the second prompt information to the third terminal; the third terminal is the camera The collected camera data is used for maintenance management, and the second prompt information is used to prompt whether to track the first terminal.
  • the query request includes an account corresponding to the first terminal
  • the determining module includes:
  • a detecting sub-module configured to detect whether an account corresponding to the first terminal exists in an access permission list corresponding to the camera; and the access permission list includes each terminal corresponding to the permission to acquire the camera data collected by the camera Account number;
  • a first determining submodule configured to: if the account corresponding to the first terminal exists in the access permission list, determine that the account corresponding to the first terminal has the right to acquire the camera data collected by the camera;
  • the second determining sub-module is configured to determine that the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera, if the account corresponding to the first terminal does not exist in the access permission list.
  • the device further includes:
  • a binding request receiving module configured to receive, before the query request receiving module receives the query request sent by the first terminal, a binding request sent by the second terminal or the camera, where the binding request includes the The account corresponding to the second terminal;
  • the first adding module is configured to add an account corresponding to the second terminal to the access permission list.
  • the device further includes:
  • a sharing request receiving module configured to receive a sharing request sent by the second terminal, where the sharing request includes an account corresponding to the fourth terminal;
  • a second adding module configured to add an account corresponding to the fourth terminal to the access permission list.
  • a request processing apparatus comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the first prompt information is pushed to the second terminal bound to the camera, where the first prompt information is used to prompt the The camera data is accessed abnormally.
  • the prompt information is used to prompt that the camera data is abnormally accessed, and when the user who does not have the right to acquire the camera data requests to access the camera data, the alarm of abnormal access can be issued in time, thereby achieving the effect of improving the security of the camera data.
  • FIG. 1 is a schematic diagram of an implementation environment involved in a request processing method according to some exemplary embodiments
  • FIG. 2 is a flowchart of a request processing method according to an exemplary embodiment
  • FIG. 3 is a flowchart of a request processing method according to another exemplary embodiment
  • FIG. 4 is a flowchart of an account adding method according to an exemplary embodiment
  • FIG. 5 is a block diagram of a request processing apparatus according to an exemplary embodiment
  • FIG. 6 is a block diagram of a request processing apparatus according to another exemplary embodiment
  • FIG. 7 is a block diagram of an apparatus, according to an exemplary embodiment.
  • FIG. 1 is a schematic diagram of an implementation environment involved in a request processing method, according to some exemplary embodiments of the present disclosure.
  • the implementation environment includes a camera 110, a server 120, a first terminal 130, a second terminal 140, and a third terminal 150.
  • the picture data or video data collected by the camera 110 is stored in the server 120, and the server 120 provides a video data push service to each user terminal.
  • the first terminal 130 and the second terminal 140 are user terminals such as a smart phone, a tablet computer, an e-book reader, and a personal computer, respectively.
  • the third terminal 150 is a terminal that performs maintenance and management of data in the server 120 and the server 120 by an administrator of the server 120.
  • the camera 110, the first terminal 130, the second terminal 140, and the third terminal 150 are respectively connected to the server 120 through a wired or wireless network.
  • FIG. 2 is a flowchart of a request processing method according to an exemplary embodiment.
  • Request processing method It is used in the server 120 of the implementation environment as shown in FIG. As shown in FIG. 2, the request processing method may include the following steps.
  • step 202 a query request sent by the first terminal is received, and the query request is used to request to query the camera data collected by the camera.
  • the image data includes image data, or the image data includes video data, or the image data includes image data and video data.
  • step 204 it is determined according to the query request whether the account corresponding to the first terminal has the right to acquire the camera data collected by the camera.
  • step 206 if the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera, the first prompt information is pushed to the second terminal bound to the camera, and the first prompt information is used for prompting.
  • the camera data is accessed abnormally.
  • the method further includes:
  • the second prompt information is pushed to the third terminal;
  • the third terminal is a terminal that performs maintenance management on the camera data collected by the camera.
  • the second prompt information is used to prompt whether to track the first terminal.
  • the query request includes an account corresponding to the first terminal, and determining, according to the query request, whether the account corresponding to the first terminal has the right to obtain the camera data collected by the camera, including:
  • the access permission list includes an account corresponding to each terminal having the right to acquire the camera data collected by the camera;
  • the account corresponding to the first terminal does not exist in the access permission list, it is determined that the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera.
  • the method before receiving the query request sent by the first terminal, the method further includes:
  • the method further includes:
  • the request processing method shown in the embodiment of the present disclosure after receiving the query request sent by the first terminal, determines, according to the query request, whether the account corresponding to the first terminal has acquired the camera captured by the camera.
  • the permission of the data if not, sending a prompt message to the second terminal bound to the camera to prompt the camera data to be accessed abnormally, and when the user who does not have the right to acquire the camera data requests access to the camera data, Send a reminder of abnormal access to improve the security of camera data.
  • FIG. 3 is a flowchart of a request processing method according to another exemplary embodiment. This request processing method is used in the server 120 of the implementation environment as shown in FIG. As shown in FIG. 3, the request processing method may include the following steps.
  • step 302 the first terminal sends a query request to the server.
  • the query request includes an account corresponding to the first terminal, and the query request is used to request to query the camera data collected by the camera.
  • the first terminal may send a query request to the server. For example, after the first terminal accesses the local area network where the camera is located, the camera file list obtained by the camera is acquired. And displaying to the user, after the user selects one of the camera files in the camera file list, the first terminal sends a request for querying the camera data corresponding to the camera file to the server, where the request may include the account of the user corresponding to the first terminal, and the request The logo of the camera file and the logo of the camera.
  • step 304 the server determines whether the account corresponding to the first terminal exists in the access permission list.
  • the server may query the access permission list corresponding to the camera according to the identifier of the camera included in the query request, and determine whether the account corresponding to the first terminal exists in the access permission list. If yes, determining that the account corresponding to the first terminal has the right to obtain the camera data collected by the camera, and proceeding to step 306; if the account corresponding to the first terminal does not exist in the access permission list, determining that the first terminal corresponds to The account does not have the right to acquire the camera data collected by the camera, and proceeds to step 308 and step 310.
  • step 306 if the account corresponding to the first terminal exists in the access permission list, the camera data is pushed to the first terminal.
  • the server may send according to the first terminal.
  • the image of the camera file carried in the query is queried for the corresponding camera data, and the advertised camera data is sent to the first terminal.
  • step 308 if the account corresponding to the first terminal does not exist in the access permission list, the first prompt information is pushed to the second terminal.
  • the first prompt information is used to prompt the camera data to be accessed abnormally.
  • the user corresponding to the second terminal is specified.
  • the camera does not share the camera data collected by the camera with the corresponding account of the first terminal, and determines that the first terminal illegally accesses the camera file.
  • the server may push the prompt message to the second terminal to prompt the user corresponding to the second terminal to illegally access the file.
  • the camera file captured by the camera reminds the user to pay attention to the security of the camera data.
  • step 310 if the account corresponding to the first terminal does not exist in the access permission list, the second prompt information is pushed to the third terminal.
  • the second prompt information is used to prompt whether to track the first terminal.
  • the server may further send a prompt message to the third terminal corresponding to the manager of the server, and prompt the management personnel to determine whether to track the first terminal.
  • the request processing method shown in the embodiment of the present disclosure after receiving the query request sent by the first terminal, determines, according to the query request, whether the account corresponding to the first terminal has the right to acquire the camera data collected by the camera. If yes, the first terminal is pushed to the first terminal; otherwise, the prompt information is sent to the second terminal bound to the camera to prompt the camera data to be accessed abnormally, and only the user having the authority to acquire the camera data The image or video data captured by the camera can be viewed, and when the user who does not have the permission to acquire the camera data requests to access the camera data, the alarm of abnormal access can be issued in time, thereby achieving the effect of improving the security of the camera data.
  • the request processing method shown in the embodiment of the present disclosure prompts the management personnel to determine whether to track the illegally accessed terminal by determining whether the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera.
  • the security of the image data is further improved.
  • FIG. 4 is a flowchart of an account adding method according to an embodiment of the present disclosure.
  • the account adding method is used in the corresponding embodiment of FIG. 3 above.
  • An account with access to camera data is added to the access list so that the owner or the sharer of the camera can view the captured camera data.
  • the account addition method may include the following steps.
  • step 301a the second terminal sends a binding request to the server.
  • the binding request includes an account corresponding to the second terminal and an identifier of the camera.
  • the terminal for controlling the camera needs to be bound to the camera, and the terminal can have the control right to the camera.
  • the user can send a binding request to the server through the second terminal, or can also send a binding request to the server through the camera.
  • step 301b the server binds the second terminal to the camera, and adds the identifier of the second terminal to the access permission list corresponding to the camera.
  • the server After receiving the binding request sent by the second terminal, the server establishes a correspondence between the account corresponding to the second terminal and the identifier of the camera, so as to bind the second terminal to the control terminal of the camera, and thereafter, the second The terminal can have full control of the camera. Other unbound terminals cannot control the camera, or other terminals can only control some functions of the camera.
  • the account corresponding to the second terminal may be added to the access permission list corresponding to the camera.
  • step 301c the second terminal displays the sharing interface and receives the sharing operation of the user in the sharing interface.
  • the sharing operation is an operation of sharing the camera data collected by the camera to the fourth terminal.
  • the user corresponding to the second terminal can share the acquisition right of the camera data collected by the camera to the other terminal through the second terminal.
  • the second terminal may display a sharing interface of the camera data collected by the camera to the user.
  • the sharing interface includes a sharing control. After the user clicks the sharing control, a terminal selection box is popped up, and the user may select a desired box in the terminal selection box.
  • the account corresponding to the fourth terminal to be shared such as the user name or email address.
  • step 301d the second terminal sends a sharing request to the server.
  • the sharing request includes an account corresponding to the fourth terminal.
  • the second terminal may send a sharing request including the account corresponding to the fourth terminal to the server.
  • step 301e the server adds the identity of the fourth terminal to the access rights list.
  • the server After the server receives the sharing request and verifies that the second terminal is a terminal bound to the camera, the account corresponding to the fourth terminal is also added to the access permission list.
  • the account adding method shown in the embodiment of the present disclosure adds the account carried in the received binding request and the sharing request to the access permission list, and thereafter only allows the terminal corresponding to the account bound to the camera and The terminal corresponding to the shared account acquires the camera data of the camera, thereby ensuring the security of the camera data.
  • FIG. 5 is a block diagram of a request processing apparatus, which may be used in the server 120 of the implementation environment shown in FIG. 1 to perform all or part of the steps shown in FIG. 2, according to an exemplary embodiment. Or perform all or part of the steps corresponding to the server in the method shown in FIG. 3 or FIG. 4.
  • the request processing device includes, but is not limited to, a query request receiving module 501, a determining module 502, a pushing module 503, and a first prompting module 504;
  • the query request receiving module 501 is configured to receive a query request sent by the first terminal, where the query request is used to request querying the camera data collected by the camera;
  • the determining module 502 is configured to determine, according to the query request, whether the first terminal has obtained Taking the permission of the camera data collected by the camera;
  • the pushing module 503 is configured to: if the first terminal has the right to acquire data collected by the camera, push the camera data to the first terminal;
  • the first prompting module 504 is configured to: if the first terminal does not have the right to acquire the camera data collected by the camera, push the first prompt information to the second terminal;
  • the second terminal is a terminal that is bound to the camera, and the first prompt information is used to indicate that the first terminal does not normally access the camera data collected by the camera.
  • the request processing apparatus after receiving the query request sent by the first terminal, determines, according to the query request, whether the account corresponding to the first terminal has the right to acquire the camera data collected by the camera. If yes, the first terminal is pushed to the first terminal; otherwise, the prompt information is sent to the second terminal bound to the camera to prompt the camera data to be accessed abnormally, and when there is no permission to acquire camera data When the user requests access to the camera data, the user can promptly issue a reminder of abnormal access, thereby achieving the effect of improving the security of the camera data.
  • FIG. 6 is a block diagram of a request processing apparatus, which may be used in the server 120 of the implementation environment shown in FIG. 1 to perform all or part of the steps shown in FIG. 2, according to another exemplary embodiment. Or perform all or part of the steps corresponding to the server in the method shown in FIG. 3 or FIG. 4.
  • the request processing device includes, but is not limited to, a query request receiving module 501, a determining module 502, a pushing module 503, and a first prompting module 504;
  • the query request receiving module 501 is configured to receive a query request sent by the first terminal, where the query request is used to request to query camera data collected by the camera, where the image data includes image data and/or video data;
  • the determining module 502 is configured to determine, according to the query request, whether an account corresponding to the first terminal has the right to acquire camera data collected by the camera;
  • the pushing module 503 is configured to: if the account corresponding to the first terminal has the right to acquire data collected by the camera, push the camera data to the first terminal;
  • the first prompting module 504 is configured to: if the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera, push the first prompt to the second terminal bound to the camera Information, the first prompt information is used to prompt the camera data to be accessed abnormally.
  • the device further includes: a second prompt module 505;
  • the second prompting module 505 is configured to: if the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera, push the second prompt information to the third terminal; the third terminal is true
  • the terminal captured by the camera performs maintenance management, and the second prompt information is used to prompt whether to track the first terminal.
  • the query request includes an account corresponding to the first terminal;
  • the determining module 502 includes: a detecting submodule 502a, a first determining submodule 502b, and a second determining submodule 502c;
  • the detecting sub-module 502a is configured to detect whether an account corresponding to the first terminal exists in an access permission list corresponding to the camera; and the access permission list includes acquiring image data collected by the camera.
  • the first determining sub-module 502b is configured to: if the account corresponding to the first terminal exists in the access permission list, determine that the account corresponding to the first terminal has acquired the camera data collected by the camera. permission;
  • the second determining sub-module 502c is configured to: if the account corresponding to the first terminal does not exist in the access permission list, determine that the account corresponding to the first terminal does not have the acquired camera acquisition Permission to capture data.
  • the device further includes: a binding request receiving module 506 and a first adding module 507;
  • the binding request receiving module 506 is configured to receive, before the query request receiving module receives the query request sent by the first terminal, a binding request sent by the second terminal or the camera, the binding The request includes an account corresponding to the second terminal;
  • the first adding module 507 is configured to add an account corresponding to the second terminal to the access permission list.
  • the device further includes: a sharing request receiving module 508 and a second adding module 509;
  • the sharing request receiving module 508 is configured to receive a sharing request sent by the second terminal, where the sharing request includes an account corresponding to the fourth terminal;
  • the second adding module 509 is configured to add an account corresponding to the fourth terminal to the access permission list.
  • the request processing apparatus after receiving the query request sent by the first terminal, determines, according to the query request, whether the account corresponding to the first terminal has the right to acquire the camera data collected by the camera. If yes, the first terminal is pushed to the first terminal; otherwise, the prompt information is sent to the second terminal bound to the camera to prompt the camera data to be accessed abnormally, and when there is no permission to acquire camera data When the user requests access to the camera data, the user can promptly issue a reminder of abnormal access, thereby achieving the effect of improving the security of the camera data.
  • the request processing apparatus shown in the embodiment of the present disclosure when determining that the account corresponding to the first terminal does not have the right to acquire the camera data collected by the camera, prompts the management personnel to decide whether to illegally access the user.
  • the terminal is tracked to further improve the security of the camera data.
  • FIG. 7 is a block diagram of an apparatus 700, according to an exemplary embodiment.
  • the apparatus 700 can vary considerably depending on configuration or performance, and can include one or more central processing units (CPU) 722 (eg, one or more processors) and memory 732, one or one
  • the storage medium 730 (for example, one or one of the Shanghai quantity storage devices) storing the application 742 or the data 744 above.
  • the memory 732 and the storage medium 730 may be short-term storage or persistent storage.
  • the program stored on the storage medium 730 may include one or more modules (not shown), each of which may include a series of instruction operations in the device, which may be used to implement the operation of FIG. All of the steps shown, or all or part of the steps performed by the server in Figure 3 or Figure 4 are implemented.
  • central processor 722 can be arranged to communicate with storage medium 730, on which a series of instruction operations in storage medium 730 are performed.
  • Device 700 may also include one or more power sources 726, one or more wired or wireless network interfaces 750, one or more input and output interfaces 758, one or more keyboards 756, and/or one or more operating systems 741 For example, Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Hardware Design (AREA)
  • Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Tourism & Hospitality (AREA)
  • Computational Linguistics (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Health & Medical Sciences (AREA)
  • Strategic Management (AREA)
  • Primary Health Care (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • General Health & Medical Sciences (AREA)
  • Information Transfer Between Computers (AREA)
  • Studio Devices (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

本公开揭示了一种请求处理方法及装置，属于智能家居领域。所述方法包括：接收第一终端发送的查询请求；根据查询请求判断第一终端对应的账号是否具有获取摄像机采集的数据的权限；若否，则向与摄像机绑定的第二终端推送第一提示信息，提示摄像数据被非正常访问。本公开通过接收第一终端发送的查询请求后，根据该查询请求判断该第一终端对应的账号是否具有获取该摄像机采集的摄像数据的权限，若否，则向与该摄像机绑定的第二终端发送提示信息，以提示该摄像数据被非正常访问，当不具有获取摄像数据权限的用户请求访问摄像数据时，能够及时发出非正常访问的提醒，从而达到提高摄像数据安全性的效果。

Description

请求处理方法及装置
本申请基于申请号为201510369410.8、申请日为2015/6/26的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及智能家居领域，特别涉及一种请求处理方法及装置。
背景技术
智能摄像机是智能家居中重要的组成部分之一，智能摄像机采集到的摄像数据可以推送至用户的智能手机等监控终端，以便用户查看。
在相关技术中，智能摄像机所有者账号可以通过手机客户端向指定账号分享摄像机的使用权限。被分享着获取该权限后，向服务器发起观看摄像机实时录像的请求。验证通过后，摄像头将向登陆该账号的手机客户端发送压缩后的实时视频流数据，客户端软件解压后就可以显示视频内容了。
发明内容
本公开提供了一种请求处理方法及装置。所述技术方案如下：
根据本公开的第一方面，提供一种请求处理方法，所述方法包括：
接收第一终端发送的查询请求，所述查询请求用于请求查询摄像机采集的摄像数据，所述摄像数据包括图片数据和/或视频数据；
根据所述查询请求判断所述第一终端对应的账号是否具有获取所述摄像机采集的数据的权限；
若所述第一终端对应的账号不具有获取所述摄像机采集的数据的权限，则向与所述摄像机绑定的第二终端推送第一提示信息，所述第一提示信息用于提示所述摄像数据被非正常访问。
可选的，所述方法还包括：
若所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限，则向第三终端推送第二提示信息；所述第三终端是对所述摄像机采集的摄像数据进行维护管理的终端，所述第二提示信息用于提示是否对所述第一终端进行追踪。
可选的，所述查询请求中包含所述第一终端对应的账号；所述根据所述查询请求 判断所述第一终端对应的账号是否具有获取所述摄像机采集的摄像数据的权限，包括：
检测所述第一终端对应的账号是否存在于所述摄像机对应的访问权限列表中；所述访问权限列表中包含具有获取所述摄像机采集的数据的权限的各个终端对应的账号；
若所述第一终端对应的账号存在于所述访问权限列表中，则确定所述第一终端对应的账号具有获取所述摄像机采集的摄像数据的权限；
若所述第一终端对应的账号不存在于所述访问权限列表中，则确定所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限。
可选的，所述接收第一终端发送的查询请求之前，还包括：
接收所述第二终端或者所述摄像机发送的绑定请求，所述绑定请求中包含所述第二终端对应的账号；
将所述第二终端对应的账号添加入所述访问权限列表。
可选的，所述方法还包括：
接收所述第二终端发送的分享请求，所述分享请求中包含第四终端对应的账号；
将所述第四终端对应的账号添加入所述访问权限列表。
根据本公开的第二方面，提供一种请求处理装置，所述装置包括：
查询请求接收模块，用于接收第一终端发送的查询请求，所述查询请求用于请求查询所述摄像机采集的摄像数据，所述摄像数据包括图片数据和/或视频数据；
判断模块，用于根据所述查询请求判断所述第一终端对应的账号是否具有获取所述摄像机采集的摄像数据的权限；
第一提示模块，用于若所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限，则向与所述摄像机绑定的第二终端推送第一提示信息，所述第一提示信息用于提示所述摄像数据被非正常访问。
可选的，所述装置还包括：
第二提示模块，用于若所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限，则向第三终端推送第二提示信息；所述第三终端是对所述摄像机采集的摄像数据进行维护管理的终端，所述第二提示信息用于提示是否对所述第一终端进行追踪。
可选的，所述查询请求中包含所述第一终端对应的账号；所述判断模块，包括：
检测子模块，用于检测所述第一终端对应的账号是否存在于所述摄像机对应的访问权限列表中；所述访问权限列表中包含具有获取所述摄像机采集的摄像数据的权限的各个终端对应的账号；
第一确定子模块，用于若所述第一终端对应的账号存在于所述访问权限列表中，则确定所述第一终端对应的账号具有获取所述摄像机采集的摄像数据的权限；
第二确定子模块，用于若所述第一终端对应的账号不存在于所述访问权限列表中，则确定所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限。
可选的，所述装置还包括：
绑定请求接收模块，用于在所述查询请求接收模块接收第一终端发送的查询请求之前，接收所述第二终端或者所述摄像机发送的绑定请求，所述绑定请求中包含所述第二终端对应的账号；
第一添加模块，用于将所述第二终端对应的账号添加入所述访问权限列表。
可选的，所述装置还包括：
分享请求接收模块，用于接收所述第二终端发送的分享请求，所述分享请求中包含第四终端对应的账号；
第二添加模块，用于将所述第四终端对应的账号添加入所述访问权限列表。
根据本公开的第三方面，提供一种请求处理装置，所述装置包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收第一终端发送的查询请求，所述查询请求用于请求查询所述摄像机采集的摄像数据，所述摄像数据包括图片数据和/或视频数据；
根据所述查询请求判断所述第一终端对应的账号是否具有获取所述摄像机采集的摄像数据的权限；
若所述第一终端对应的账号不具有获取所述摄像机采集的数据的权限，则向与所述摄像机绑定的第二终端推送第一提示信息，所述第一提示信息用于提示所述摄像数据被非正常访问。
本公开的实施例提供的技术方案可以包括以下有益效果：
通过接收第一终端发送的查询请求后，根据该查询请求判断该第一终端对应的账号是否具有获取该摄像机采集的摄像数据的权限，若否，则向与该摄像机绑定的第二终端发送提示信息，以提示该摄像数据被非正常访问，且当不具有获取摄像数据权限的用户请求访问摄像数据时，能够及时发出非正常访问的提醒，从而达到提高摄像数据安全性的效果。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并于说明书一起用于解释本发明的原理。
图1是根据部分示例性实施例示出的一种请求处理方法所涉及的实施环境的示意图；
图2是根据一示例性实施例示出的一种请求处理方法的流程图；
图3是根据另一示例性实施例示出的一种请求处理方法的流程图；
图4是根据一示例性实施例示出的一种账号添加方法的流程图；
图5是根据一示例性实施例示出的一种请求处理装置的框图；
图6是根据另一示例性实施例示出的一种请求处理装置的框图；
图7是根据一示例性实施例示出的一种装置的框图。
具体实施方式
这里将详细地对示例性实施例执行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明的一些方面相一致的装置和方法的例子。
图1是根据本公开部分示例性实施例示出的请求处理方法所涉及的实施环境的示意图。该实施环境包括：摄像机110、服务器120、第一终端130、第二终端140以及第三终端150。
摄像机110采集到的图片数据或者视频数据存储在服务器120中，服务器120向各个用户终端提供视频数据推送服务。
第一终端130和第二终端140分别为智能手机、平板电脑、电子书阅读器以及个人电脑等用户终端。
第三终端150是服务器120的管理人员对服务器120以及服务器120中的数据进行维护管理的终端。
摄像机110、第一终端130、第二终端140以及第三终端150分别通过有线或者无线网络与服务器120相连接。
图2是根据一示例性实施例示出的一种请求处理方法的流程图。该请求处理方法 用于如图1所示实施环境的服务器120中。如图2所示，该请求处理方法可以包括以下步骤。
在步骤202中，接收第一终端发送的查询请求，该查询请求用于请求查询该摄像机采集的摄像数据。
其中，该摄像数据包括图片数据，或者，该摄像数据包括视频数据，或者，该摄像数据包括图片数据和视频数据。
在步骤204中，根据该查询请求判断该第一终端对应的账号是否具有获取该摄像机采集的摄像数据的权限。
在步骤206中，若该第一终端对应的账号不具有获取该摄像机采集的摄像数据的权限，则向与该摄像机绑定的第二终端推送第一提示信息，该第一提示信息用于提示该摄像数据被非正常访问。
可选的，该方法还包括：
若该第一终端对应的账号不具有获取该摄像机采集的摄像数据的权限，则向第三终端推送第二提示信息；第三终端是对该摄像机采集的摄像数据进行维护管理的终端。该第二提示信息用于提示是否对该第一终端进行追踪。
可选的，该查询请求中包含该第一终端对应的账号；该根据该查询请求判断该第一终端对应的账号是否具有获取该摄像机采集的摄像数据的权限，包括：
检测该第一终端对应的账号是否存在于该摄像机对应的访问权限列表中；该访问权限列表中包含具有获取该摄像机采集的摄像数据的权限的各个终端对应的账号；
若该第一终端对应的账号存在于该访问权限列表中，则确定该第一终端对应的账号具有获取该摄像机采集的摄像数据的权限；
若该第一终端对应的账号不存在于该访问权限列表中，则确定该第一终端对应的账号不具有获取该摄像机采集的摄像数据的权限。
可选的，该接收第一终端发送的查询请求之前，还包括：
接收该第二终端或者该摄像机发送的绑定请求，该绑定请求中包含该第二终端对应的账号；
将该第二终端对应的账号添加入该访问权限列表。
可选的，该方法还包括：
接收该第二终端发送的分享请求，该分享请求中包含第四终端对应的账号；
将该第四终端对应的账号添加入该访问权限列表。
综上所述，本公开实施例所示的请求处理方法，通过接收第一终端发送的查询请求后，根据该查询请求判断该第一终端对应的账号是否具有获取该摄像机采集的摄像 数据的权限，若否，则向与该摄像机绑定的第二终端发送提示信息，以提示该摄像数据被非正常访问，且当不具有获取摄像数据权限的用户请求访问摄像数据时，能够及时发出非正常访问的提醒，从而达到提高摄像数据安全性的效果。
图3是根据另一示例性实施例示出的一种请求处理方法的流程图。该请求处理方法用于如图1所示实施环境的服务器120中。如图3所示，该请求处理方法可以包括以下步骤。
在步骤302中，第一终端向服务器发送查询请求。
其中，该查询请求中包含第一终端对应的账号，该查询请求用于请求查询该摄像机采集到的摄像数据。
当第一终端对应的用户想要查看摄像头采集到的摄像数据时，可以通过第一终端向服务器发送查询请求，比如，第一终端接入摄像机所在的局域网后，获取摄像机采集到的摄像文件列表并展示给用户，用户选择摄像文件列表中的某一个摄像文件后，第一终端向服务器发送查询该摄像文件对应的摄像数据的请求，该请求中可以包含第一终端对应的用户的账号、该摄像文件的标识以及该摄像机的标识等。
在步骤304中，服务器判断该第一终端对应的账号是否存在于该访问权限列表中。
服务器接收到第一终端发送的查询请求后，可以根据该查询请求中包含的该摄像机的标识查询该摄像机对应的访问权限列表，并判断该第一终端对应的账号是否存在与该访问权限列表中，如果是，则确定该第一终端对应的账号具有获取该摄像机采集的摄像数据的权限，进入步骤306；如果第一终端对应的账号不存在与该访问权限列表中，则确定第一终端对应的账号不具有获取该摄像机采集的摄像数据的权限，进入步骤308和步骤310。
在步骤306中，若该第一终端对应的账号存在于该访问权限列表中，则向该第一终端推送该摄像数据。
若第一终端对应的账号存在于该访问权限列表，则说明第二终端对应的用户已经向第一终端对应的账号分享了摄像机采集到的摄像数据，此时，服务器可以根据第一终端发送的查询请求中携带的摄像文件的标识查询对应的摄像数据，并将查询到的摄像数据发送给第一终端。
在步骤308中，若该第一终端对应的账号不存在于该访问权限列表中，则向第二终端推送第一提示信息。
该第一提示信息用于提示该摄像数据被非正常访问。
如果第一终端对应的账号不存在于该访问权限列表，则说明第二终端对应的用户 并未向第一终端对应的账号分享摄像机采集到的摄像数据，确定第一终端非法访问摄像文件，此时，服务器可以向第二终端推送提示信息，以提示第二终端对应的用户有人非法访问摄像机采集到的摄像文件，提醒用户注意摄像数据的安全。
在步骤310中，若该第一终端对应的账号不存在于该访问权限列表中，则向第三终端推送第二提示信息。
该第二提示信息用于提示是否对该第一终端进行追踪。
可选的，在确定第一终端非法访问摄像文件后，服务器还可以向服务器的管理人员对应的第三终端推送提示信息，提示管理人员自行决定是否对第一终端进行追踪。
综上所述，本公开实施例所示的请求处理方法，通过接收第一终端发送的查询请求后，根据该查询请求判断该第一终端对应的账号是否具有获取该摄像机采集的摄像数据的权限，若是，则向该第一终端推送该第一终端，否则，向与该摄像机绑定的第二终端发送提示信息，以提示该摄像数据被非正常访问，只有具有获取摄像数据的权限的用户才可以查看摄像机拍摄的图像或视频数据，且当不具有获取摄像数据权限的用户请求访问摄像数据时，能够及时发出非正常访问的提醒，从而达到提高摄像数据安全性的效果。
此外，本公开实施例所示的请求处理方法，通过在判断出第一终端对应的账号不具有获取该摄像机采集的摄像数据的权限时，提示管理人员自行决定是否对非法访问的终端进行追踪，进一步提高了摄像数据的安全性。
基于上述图3所示的请求处理方法，请参考图4，其示出了本公开一个实施例提供的账号添加方法的流程图，该账号添加方法用于在上述图3对应实施例所涉及的访问权限列表中添加具有访问摄像数据的权限的账号，以便该摄像机的拥有者或者被分享者能够查看其采集的摄像数据。该账号添加方法可以包括以下步骤。
在步骤301a中，第二终端向服务器发送绑定请求。
其中，该绑定请求中包含第二终端对应的账号以及摄像机的标识。
在智能家居中，摄像机首次安装后，需要将用于控制摄像机的终端与该摄像机进行绑定后，该终端才能够拥有对摄像机的控制权限。在绑定时，用户可以通过第二终端向服务器发送绑定请求，或者，也可以通过摄像机向服务器发送绑定请求。
在步骤301b中，服务器将第二终端和摄像机进行绑定，并将第二终端的标识添加入摄像机对应的访问权限列表。
服务器接收到第二终端发送的绑定请求后，建立第二终端对应的账号以及摄像机的标识之间的对应关系，以将该第二终端绑定为该摄像机的控制终端，此后，该第二 终端即可以拥有对该摄像机的完全控制权限，其它未绑定的终端则无法对摄像机进行控制，或者，其它终端只能对摄像机进行部分功能的控制。
服务器将第二终端进行绑定后，还可以将第二终端对应的账号添加入该摄像机对应的访问权限列表中。
在步骤301c中，第二终端展示分享界面，接收用户在分享界面中的分享操作。
其中，该分享操作是向第四终端分享摄像头采集到的摄像数据的操作。
第二终端与摄像机绑定后，第二终端对应的用户还可以通过第二终端向其他终端分享摄像头采集到的摄像数据的获取权限。比如，第二终端可以向用户展示该摄像机采集到的摄像数据的分享界面，该分享界面中包含一个分享控件，用户点击该分享控件后，弹出终端选择框，用户可以在终端选择框中选择想要分享的第四终端对应的账号，比如用户名或者邮箱等。
在步骤301d中，第二终端向服务器发送分享请求。
该分享请求中包含第四终端对应的账号。
用户在终端选择框中选择第四终端并确定分享后，第二终端即可以向服务器发送包含该第四终端对应的账号的分享请求。
在步骤301e中，服务器将第四终端的标识添加入该访问权限列表。
服务器接收到该分享请求，并验证该第二终端是与该摄像机绑定的终端后，将该第四终端对应的账号也添加入访问权限列表。
综上所述，本公开实施例所示的账号添加方法，通过将接收到的绑定请求和分享请求中携带的账号添加入访问权限列表，此后仅允许与摄像机绑定的账号对应的终端以及被分享的账号对应的终端获取该摄像机的摄像数据，从而保证摄像数据的安全性。
下述为本公开装置实施例，可以用于执行本公开方法实施例。对于本公开装置实施例中未披露的细节，请参照本公开方法实施例。
图5是根据一示例性实施例示出的一种请求处理装置的框图，该请求处理装置可以用于如图1所示实施环境的服务器120中，执行如图2所示的全部或部分步骤，或者执行如图3或图4所示方法中服务器对应的全部或部分步骤。如图5所示，该请求处理装置包括但不限于：查询请求接收模块501、判断模块502、推送模块503以及第一提示模块504；
所述查询请求接收模块501被设置为用于接收第一终端发送的查询请求，所述查询请求用于请求查询所述摄像机采集的摄像数据；
所述判断模块502被设置为用于根据所述查询请求判断所述第一终端是否具有获 取所述摄像机采集的摄像数据的权限；
所述推送模块503被设置为用于若所述第一终端具有获取所述摄像机采集的数据的权限，则向所述第一终端推送所述摄像数据；
所述第一提示模块504被设置为用于若所述第一终端不具有获取所述摄像机采集的摄像数据的权限，则向第二终端推送第一提示信息；
所述第二终端为与所述摄像机绑定的终端，所述第一提示信息用于指示所述第一终端非正常访问所述摄像机采集的摄像数据。
综上所述，本公开实施例所示的请求处理装置，通过接收第一终端发送的查询请求后，根据该查询请求判断该第一终端对应的账号是否具有获取该摄像机采集的摄像数据的权限，若是，则向该第一终端推送该第一终端，否则，向与该摄像机绑定的第二终端发送提示信息，以提示该摄像数据被非正常访问，且当不具有获取摄像数据权限的用户请求访问摄像数据时，能够及时发出非正常访问的提醒，从而达到提高摄像数据安全性的效果。
图6是根据另一示例性实施例示出的一种请求处理装置的框图，该请求处理装置可以用于如图1所示实施环境的服务器120中，执行如图2所示的全部或部分步骤，或者执行如图3或图4所示方法中服务器对应的全部或部分步骤。如图6所示，该请求处理装置包括但不限于：查询请求接收模块501、判断模块502、推送模块503以及第一提示模块504；
所述查询请求接收模块501被设置为用于接收第一终端发送的查询请求，所述查询请求用于请求查询所述摄像机采集的摄像数据，所述摄像数据包括图片数据和/或视频数据；
所述判断模块502被设置为用于根据所述查询请求判断所述第一终端对应的账号是否具有获取所述摄像机采集的摄像数据的权限；
所述推送模块503被设置为用于若所述第一终端对应的账号具有获取所述摄像机采集的数据的权限，则向所述第一终端推送所述摄像数据；
所述第一提示模块504被设置为用于若所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限，则向与所述摄像机绑定的第二终端推送第一提示信息，所述第一提示信息用于提示所述摄像数据被非正常访问。
可选的，所述装置还包括：第二提示模块505；
所述第二提示模块505被设置为用于若所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限，则向第三终端推送第二提示信息；所述第三终端是对 所述摄像机采集的摄像数据进行维护管理的终端，所述第二提示信息用于提示是否对所述第一终端进行追踪。
可选的，所述查询请求中包含所述第一终端对应的账号；所述判断模块502，包括：检测子模块502a、第一确定子模块502b以及第二确定子模块502c；
所述检测子模块502a被设置为用于检测所述第一终端对应的账号是否存在于所述摄像机对应的访问权限列表中；所述访问权限列表中包含具有获取所述摄像机采集的摄像数据的权限的各个终端对应的账号；
所述第一确定子模块502b被设置为用于若所述第一终端对应的账号存在于所述访问权限列表中，则确定所述第一终端对应的账号具有获取所述摄像机采集的摄像数据的权限；
所述第二确定子模块502c被设置为用于若所述第一终端对应的账号不存在于所述访问权限列表中，则确定所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限。
可选的，所述装置还包括：绑定请求接收模块506以及第一添加模块507；
所述绑定请求接收模块506被设置为用于在所述查询请求接收模块接收第一终端发送的查询请求之前，接收所述第二终端或者所述摄像机发送的绑定请求，所述绑定请求中包含所述第二终端对应的账号；
所述第一添加模块507被设置为用于将所述第二终端对应的账号添加入所述访问权限列表。
可选的，所述装置还包括：分享请求接收模块508以及第二添加模块509；
所述分享请求接收模块508被设置为用于接收所述第二终端发送的分享请求，所述分享请求中包含第四终端对应的账号；
所述第二添加模块509被设置为用于将所述第四终端对应的账号添加入所述访问权限列表。
综上所述，本公开实施例所示的请求处理装置，通过接收第一终端发送的查询请求后，根据该查询请求判断该第一终端对应的账号是否具有获取该摄像机采集的摄像数据的权限，若是，则向该第一终端推送该第一终端，否则，向与该摄像机绑定的第二终端发送提示信息，以提示该摄像数据被非正常访问，且当不具有获取摄像数据权限的用户请求访问摄像数据时，能够及时发出非正常访问的提醒，从而达到提高摄像数据安全性的效果。
此外，本公开实施例所示的请求处理装置，通过在判断出第一终端对应的账号不具有获取该摄像机采集的摄像数据的权限时，提醒管理人员自行决定是否对非法访问 的终端进行追踪，进一步提高了摄像数据的安全性。
图7是根据一示例性实施例示出的一种装置700的框图。该装置700可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器(central processing units，CPU)722(例如，一个或一个以上处理器)和存储器732，一个或一个以上存储应用程序742或数据744的存储介质730(例如一个或一个以上海量存储设备)。其中，存储器732和存储介质730可以是短暂存储或持久存储。存储在存储介质730的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对装置中的一系列指令操作，这一系列的指令操作可以用于实现如图2所示的全部步骤，或者实现如图3或图4中由服务器所执行的全部或者部分步骤。更进一步地，中央处理器722可以设置为与存储介质730通信，在装置700上执行存储介质730中的一系列指令操作。
装置700还可以包括一个或一个以上电源726，一个或一个以上有线或无线网络接口750，一个或一个以上输入输出接口758，一个或一个以上键盘756，和/或，一个或一个以上操作系统741，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM等等。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中执行了详细描述，此处将不做详细阐述说明。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围执行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (11)

  1. 一种请求处理方法，其特征在于，所述方法包括：
    接收第一终端发送的查询请求，所述查询请求用于请求查询摄像机采集的摄像数据，所述摄像数据包括图片数据和/或视频数据；
    根据所述查询请求判断所述第一终端对应的账号是否具有获取所述摄像机采集的数据的权限；
    若所述第一终端对应的账号不具有获取所述摄像机采集的数据的权限，则向与所述摄像机绑定的第二终端推送第一提示信息，所述第一提示信息用于提示所述摄像数据被非正常访问。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    若所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限，则向第三终端推送第二提示信息；所述第三终端是对所述摄像机采集的摄像数据进行维护管理的终端，所述第二提示信息用于提示是否对所述第一终端进行追踪。
  3. 根据权利要求1所述的方法，其特征在于，所述查询请求中包含所述第一终端对应的账号；所述根据所述查询请求判断所述第一终端对应的账号是否具有获取所述摄像机采集的摄像数据的权限，包括：
    检测所述第一终端对应的账号是否存在于所述摄像机对应的访问权限列表中；所述访问权限列表中包含具有获取所述摄像机采集的数据的权限的各个终端对应的账号；
    若所述第一终端对应的账号存在于所述访问权限列表中，则确定所述第一终端对应的账号具有获取所述摄像机采集的摄像数据的权限；
    若所述第一终端对应的账号不存在于所述访问权限列表中，则确定所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限。
  4. 根据权利要求3所述的方法，其特征在于，所述接收第一终端发送的查询请求之前，还包括：
    接收所述第二终端或者所述摄像机发送的绑定请求，所述绑定请求中包含所述第二终端对应的账号；
    将所述第二终端对应的账号添加入所述访问权限列表。
  5. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    接收所述第二终端发送的分享请求，所述分享请求中包含第四终端对应的账号；
    将所述第四终端对应的账号添加入所述访问权限列表。
  6. 一种请求处理装置，其特征在于，所述装置包括：
    查询请求接收模块，用于接收第一终端发送的查询请求，所述查询请求用于请求查询所述摄像机采集的摄像数据，所述摄像数据包括图片数据和/或视频数据；
    判断模块，用于根据所述查询请求判断所述第一终端对应的账号是否具有获取所述摄像机采集的摄像数据的权限；
    第一提示模块，用于若所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限，则向与所述摄像机绑定的第二终端推送第一提示信息，所述第一提示信息用于提示所述摄像数据被非正常访问。
  7. 根据权利要求6所述的装置，其特征在于，所述装置还包括：
    第二提示模块，用于若所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限，则向第三终端推送第二提示信息；所述第三终端是对所述摄像机采集的摄像数据进行维护管理的终端，所述第二提示信息用于提示是否对所述第一终端进行追踪。
  8. 根据权利要求6所述的装置，其特征在于，所述查询请求中包含所述第一终端对应的账号；所述判断模块，包括：
    检测子模块，用于检测所述第一终端对应的账号是否存在于所述摄像机对应的访问权限列表中；所述访问权限列表中包含具有获取所述摄像机采集的摄像数据的权限的各个终端对应的账号；
    第一确定子模块，用于若所述第一终端对应的账号存在于所述访问权限列表中，则确定所述第一终端对应的账号具有获取所述摄像机采集的摄像数据的权限；
    第二确定子模块，用于若所述第一终端对应的账号不存在于所述访问权限列表中，则确定所述第一终端对应的账号不具有获取所述摄像机采集的摄像数据的权限。
  9. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    绑定请求接收模块，用于在所述查询请求接收模块接收第一终端发送的查询请求 之前，接收所述第二终端或者所述摄像机发送的绑定请求，所述绑定请求中包含所述第二终端对应的账号；
    第一添加模块，用于将所述第二终端对应的账号添加入所述访问权限列表。
  10. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    分享请求接收模块，用于接收所述第二终端发送的分享请求，所述分享请求中包含第四终端对应的账号；
    第二添加模块，用于将所述第四终端对应的账号添加入所述访问权限列表。
  11. 一种请求处理装置，其特征在于，所述装置包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收第一终端发送的查询请求，所述查询请求用于请求查询所述摄像机采集的摄像数据，所述摄像数据包括图片数据和/或视频数据；
    根据所述查询请求判断所述第一终端对应的账号是否具有获取所述摄像机采集的摄像数据的权限；
    若所述第一终端对应的账号不具有获取所述摄像机采集的数据的权限，则向与所述摄像机绑定的第二终端推送第一提示信息，所述第一提示信息用于提示所述摄像数据被非正常访问。
PCT/CN2015/090604 2015-06-26 2015-09-24 请求处理方法及装置 WO2016206209A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
MX2016006176A MX358468B (es) 2015-06-26 2015-09-24 Metodo y dispositivo para procesar solicitud.
KR1020167012301A KR101797416B1 (ko) 2015-06-26 2015-09-24 요청 처리 방법 및 디바이스
RU2016121598A RU2660625C2 (ru) 2015-06-26 2015-09-24 Способ и устройство для обработки требования
JP2016518074A JP6268282B2 (ja) 2015-06-26 2015-09-24 リクエスト処理方法および装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510369410.8A CN105100708B (zh) 2015-06-26 2015-06-26 请求处理方法及装置
CN201510369410.8 2015-06-26

Publications (1)

Publication Number Publication Date
WO2016206209A1 true WO2016206209A1 (zh) 2016-12-29

Family

ID=54580128

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/090604 WO2016206209A1 (zh) 2015-06-26 2015-09-24 请求处理方法及装置

Country Status (8)

Country Link
US (1) US10021355B2 (zh)
EP (2) EP3905671B1 (zh)
JP (1) JP6268282B2 (zh)
KR (1) KR101797416B1 (zh)
CN (1) CN105100708B (zh)
MX (1) MX358468B (zh)
RU (1) RU2660625C2 (zh)
WO (1) WO2016206209A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108093216A (zh) * 2017-12-21 2018-05-29 北京时代网星科技有限公司 云监控移动终端

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AT518247B1 (de) 2016-05-13 2017-09-15 Tyrolit - Schleifmittelwerke Swarovski K G Schleifscheibe
CN106066967A (zh) * 2016-05-26 2016-11-02 北京金山安全软件有限公司 一种权限设置方法及装置
CN107948592B (zh) * 2017-11-22 2019-03-15 珠海格力电器股份有限公司 一种共享摄像头的方法、装置和智能终端
CN108737395A (zh) * 2018-05-08 2018-11-02 北京小米移动软件有限公司 访问摄像头的方法、装置、存储介质及摄像头
CN108632391B (zh) * 2018-05-21 2022-03-11 北京小米移动软件有限公司 信息共享方法及装置
CN110609480B (zh) * 2018-06-15 2022-05-06 青岛海尔洗衣机有限公司 家用电器的安全控制方法和系统
CN109145560B (zh) * 2018-08-08 2022-03-25 北京小米移动软件有限公司 访问监控设备的方法及装置
US10769101B2 (en) * 2018-08-23 2020-09-08 Oath Inc. Selective data migration and sharing
CN109407528A (zh) * 2018-09-19 2019-03-01 北京小米移动软件有限公司 安全访问方法、装置、服务器及存储介质
CN109379190B (zh) * 2018-12-19 2021-09-21 世纪龙信息网络有限责任公司 密钥分配方法、装置、计算机设备及存储介质
CN109495258B (zh) * 2018-12-19 2022-05-13 天翼数字生活科技有限公司 监控数据解密的方法、装置、计算机设备及存储介质
CN111159735A (zh) * 2019-12-24 2020-05-15 珠海荣邦智能科技有限公司 应用程序的数据访问方法及装置
CN111339513B (zh) * 2020-01-23 2023-05-09 华为技术有限公司 数据分享的方法和装置
CN111491188A (zh) * 2020-03-09 2020-08-04 西安万像电子科技有限公司 权限管理方法、路由装置及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009149466A1 (en) * 2008-06-06 2009-12-10 Meebo, Inc. System and method for sharing content in an instant messaging application
CN103095658A (zh) * 2011-11-03 2013-05-08 北京神州泰岳软件股份有限公司 一种账户登录的方法和系统
CN103338188A (zh) * 2013-06-08 2013-10-02 北京大学 一种适用于移动云的客户端动态认证方法
CN104660480A (zh) * 2013-11-18 2015-05-27 深圳市腾讯计算机系统有限公司 一种帐号异常处理的方法、装置及系统

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7079177B2 (en) * 1995-02-27 2006-07-18 Canon Kabushiki Kaisha Remote control system and access control method for information input apparatus with limitation by user for image access and camemremote control
US6335927B1 (en) * 1996-11-18 2002-01-01 Mci Communications Corporation System and method for providing requested quality of service in a hybrid network
AUPQ217399A0 (en) * 1999-08-12 1999-09-02 Honeywell Limited Realtime digital video server
WO2001099375A1 (en) * 2000-06-22 2001-12-27 Steven Low Method and system for communicating visual information
JP2003296193A (ja) * 2002-04-02 2003-10-17 Seiko Instruments Inc 不正アクセス監視装置及び方法、並びに不正アクセス監視プログラム
JP2004320513A (ja) * 2003-04-17 2004-11-11 Casio Comput Co Ltd 情報管理システムおよびプログラム
KR100543670B1 (ko) * 2003-07-04 2006-01-20 주식회사유진로보틱스 로봇을 이용한 홈 시큐리티 서비스 방법 및 그 로봇
CN1558611A (zh) * 2004-02-12 2004-12-29 上海交通大学 基于管理中心的网络视频监控的多点交互方法
RU2271074C1 (ru) * 2004-08-09 2006-02-27 ООО "НИИР-Радионет" Многофункциональная система интеграции и передачи данных видеоинформационных услуг
KR100656520B1 (ko) 2004-11-24 2006-12-11 삼성전자주식회사 홈 네트워크의 레벨별 인증 시스템 및 그 방법
US8059551B2 (en) * 2005-02-15 2011-11-15 Raytheon Bbn Technologies Corp. Method for source-spoofed IP packet traceback
CN100456705C (zh) * 2005-09-09 2009-01-28 刘红健 一种互联网多媒体通讯的监视系统及监视方法
KR100754379B1 (ko) 2006-09-04 2007-08-31 삼성에스디아이 주식회사 이성분성 또는 다성분성 전극촉매, 그 제조방법 및 상기전극촉매를 채용한 연료전지
JP4290185B2 (ja) * 2006-09-05 2009-07-01 キヤノン株式会社 撮影システム、撮像装置、監視装置及びプログラム
US8087072B2 (en) * 2007-01-18 2011-12-27 Microsoft Corporation Provisioning of digital identity representations
CN101075929B (zh) * 2007-03-02 2010-11-24 腾讯科技（深圳）有限公司 信息查询系统、信息查询服务器及信息查询方法
CN101119384A (zh) * 2007-07-30 2008-02-06 深圳市融合视讯科技有限公司 一种动态ip摄像终端的控制方法
US8223205B2 (en) * 2007-10-24 2012-07-17 Waterfall Solutions Ltd. Secure implementation of network-based sensors
CN101577685B (zh) * 2008-05-09 2012-05-23 中国电信股份有限公司 信息查询方法及系统
CN101552804A (zh) * 2008-12-22 2009-10-07 北京大学深圳研究生院 网络视频发布系统及其网络视频访问方法
US20120092439A1 (en) * 2010-10-19 2012-04-19 Cisco Technology, Inc. System and method for providing connectivity in a network environment
KR20120041571A (ko) * 2010-10-21 2012-05-02 주식회사트레디오 유에스비형 무선식별리더기를 이용한 데이터 모니터링시스템
CN102025977A (zh) * 2010-11-25 2011-04-20 曹峰华 一种视频监控方法及移动终端
KR20150000230A (ko) * 2013-06-24 2015-01-02 한국전자통신연구원 네트워크 카메라 분산 시스템 및 방법
US9953386B2 (en) * 2013-11-16 2018-04-24 At&T Intellectual Property I, L.P. Method and system for controlling distribution of composite data of user by aggregation server
CN103581622A (zh) * 2013-12-10 2014-02-12 安徽省徽商集团有限公司 智能终端远程视频监控方法及其系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009149466A1 (en) * 2008-06-06 2009-12-10 Meebo, Inc. System and method for sharing content in an instant messaging application
CN103095658A (zh) * 2011-11-03 2013-05-08 北京神州泰岳软件股份有限公司 一种账户登录的方法和系统
CN103338188A (zh) * 2013-06-08 2013-10-02 北京大学 一种适用于移动云的客户端动态认证方法
CN104660480A (zh) * 2013-11-18 2015-05-27 深圳市腾讯计算机系统有限公司 一种帐号异常处理的方法、装置及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108093216A (zh) * 2017-12-21 2018-05-29 北京时代网星科技有限公司 云监控移动终端
CN108093216B (zh) * 2017-12-21 2023-09-12 北京时代网星科技有限公司 一种施工现场监控小车

Also Published As

Publication number Publication date
MX358468B (es) 2018-08-22
RU2016121598A (ru) 2017-12-06
EP3905671B1 (en) 2023-07-12
KR101797416B1 (ko) 2017-11-13
US20160381324A1 (en) 2016-12-29
EP3905671A1 (en) 2021-11-03
JP2017522620A (ja) 2017-08-10
MX2016006176A (es) 2017-02-23
JP6268282B2 (ja) 2018-01-24
RU2660625C2 (ru) 2018-07-06
CN105100708A (zh) 2015-11-25
US10021355B2 (en) 2018-07-10
CN105100708B (zh) 2018-12-25
EP3110147A1 (en) 2016-12-28

Similar Documents

Publication Publication Date Title
WO2016206209A1 (zh) 请求处理方法及装置
US10348505B1 (en) Systems and techniques for validation of media data
US11038674B2 (en) Trustworthy data exchange using distributed databases
CN108174248B (zh) 视频播放方法、视频播放控制方法、装置、及存储介质
US8824750B2 (en) Distributive facial matching and notification system
WO2017000820A1 (zh) 基于云端存储的文件分享方法、装置与系统
US10084995B2 (en) Systems and methods for an automated cloud-based video surveillance system
JP2016534607A (ja) 拡張可能なビデオクラウドサービスのためのシステムおよび方法
US20150046830A1 (en) Methods, Device and Social Network Manager for Enabling Interaction with Another Device
US11093545B2 (en) Systems and methods for an automated cloud-based video surveillance system
WO2014111022A1 (zh) 一种移动终端用户信息的显示方法、移动终端和服务系统
US8813173B2 (en) Mobile communication device surveillance system
US20150127942A1 (en) Security key device for secure cloud service, and system and method for providing secure cloud service
US20190108097A1 (en) Systems and methods for backing up files
JP2017526995A (ja) デュアルチャネル識別認証
WO2014201969A1 (en) Method and system for controlling media information display on multiple terminals
CN110677682A (zh) 直播检测与数据处理方法、设备、系统及存储介质
TW201520917A (zh) 操作處理方法和裝置
WO2016011739A1 (zh) 防伪验证方法、装置和系统
US20160110531A1 (en) Information processing apparatus, terminal apparatus and information processing method
JP5596194B2 (ja) 認証装置、認証装置の制御方法、通信装置、認証システム、制御プログラム、および記録媒体
TW201039640A (en) Network monitoring system and method
TWI659399B (zh) 威脅檢測資訊分配系統及方法
CN107566809B (zh) 一种视频监控报警方法、装置及系统
US20190037612A1 (en) Connecting method to an information capture device

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2016518074

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/006176

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016121598

Country of ref document: RU

Kind code of ref document: A

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

Ref document number: 15896104

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112016012434

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112016012434

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20160531

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15896104

Country of ref document: EP

Kind code of ref document: A1