WO2017067045A1 - 一种联动控制权管理装置及方法 - Google Patents

一种联动控制权管理装置及方法 Download PDF

Info

Publication number
WO2017067045A1
WO2017067045A1 PCT/CN2015/096606 CN2015096606W WO2017067045A1 WO 2017067045 A1 WO2017067045 A1 WO 2017067045A1 CN 2015096606 W CN2015096606 W CN 2015096606W WO 2017067045 A1 WO2017067045 A1 WO 2017067045A1
Authority
WO
WIPO (PCT)
Prior art keywords
linkage
terminal
service system
token
control
Prior art date
Application number
PCT/CN2015/096606
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 EP15906561.4A priority Critical patent/EP3349409A4/en
Priority to US15/756,070 priority patent/US20180343267A1/en
Publication of WO2017067045A1 publication Critical patent/WO2017067045A1/zh

Links

Images

Classifications

    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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/105—Multiple levels of security
    • 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/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/407—Bus networks with decentralised control
    • H04L12/417—Bus networks with decentralised control with deterministic access, e.g. token passing
    • 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/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • 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/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • 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/14—Session management
    • H04L67/148—Migration or transfer of sessions
    • 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
    • H04L9/3234—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 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token

Definitions

  • the present invention relates to a multi-terminal linkage technology, and in particular, to a linkage control right management apparatus and method.
  • the object of the present invention is to overcome the shortcomings of the prior art method for effectively managing multi-terminal linkage operation, and to provide a linkage control right management apparatus and method capable of improving the friendliness of operation of multi-terminal linkage.
  • the present invention provides a linkage control right management apparatus, including a linkage service system 102 and a linkage terminal.
  • the linkage terminal has multiple, in the same service instance, and one linkage terminal is in the same time. It can only serve as a role: the control terminal 101 or the controlled terminal 103; the control terminal 101 acquires the authority token of the controlled terminal 103, and then performs linkage control on the controlled terminal 103; the linkage service system 102 is used for Maintain the linkage terminal role, maintain the authority token status, process or transfer the permission token request, initiate or transfer the permission token.
  • the linkage service system 102 configures a role for the linkage terminal; when the linkage terminal is configured as the role of the control terminal, the linkage service system 102 A unique linkage control authority token corresponding to the role of the controlled terminal is generated, that is, the linkage service token is issued by the linkage service system 102; when the linkage terminal is modified by the controlled terminal role into the control role, or After the offline, the linkage service system 102 revokes the privilege token.
  • a privilege token controlled by the control terminal 103 can only be held by one control terminal 101 at the same time; and a control terminal 101 can apply for or hold a plurality of privilege tokens of the controlled terminal 103.
  • the control terminal 101 applies for the linkage authority token to the linkage service system 102, the authority token is allocated or rejected according to the rule; wherein the rules for allocating or rejecting the assignment token include:
  • the authority token is allocated by the arbitrator, and the arbitrator is served by the linkage service system 12 or by the control terminal 13;
  • the arbitrator is the linkage service system 12, when the application for the privilege token is received by the control terminal 11, it is directly processed; if the arbitrator is the controlled terminal 13, the linkage service system 12 receives the application request for the privilege token. Transmitting the request to the controlled terminal 13 and processing it by the controlled terminal 13;
  • the arbitrator can recover the privilege token according to the state of the control terminal 11, and the state of the control terminal includes, without limitation, an online state, a session state, an interaction frequency, and whether the linkage control is over-authorized;
  • the linkage service system 12 actively notifies whether the control terminal 11 that has rejected the authority token request performs linkage control.
  • the role application command of the linkage terminal, the application, distribution, and collection instruction of the authority token are all passed through the linkage service system 102.
  • the present invention also provides a method for managing a coordinated control right based on the linkage control right management device, which includes an application for a rights token, and specifically includes:
  • Step 201 the control terminal 101 applies to the linkage service system 102 for a permission token
  • Step 202 after receiving the request, the linkage service system 102 determines whether the control terminal 101 has been rejected within a predetermined time, if it is rejected, step 203); otherwise, step 205);
  • Step 203 the linkage service system 102 determines whether the privilege token has been allocated, if it is assigned, step 204); otherwise, step 205);
  • Step 204 the linkage service system 102 rejects the linkage request, and restarts the timing; then performs step 212);
  • Step 205 the linkage service system 102 forwards the request to the corresponding arbitrator according to the configuration, and proceeds to 206);
  • Step 206 the arbitrator decides whether to accept the application, and notifies the linkage service system 102 of the arbitration result. Then performing step 207);
  • Step 207 the linkage service system 102 determines whether the result is rejected, if rejected, step 204), if accepted, step 208);
  • Step 208) the linkage service system 102 determines whether the permission token is assigned, if it is assigned, step 209); otherwise, step 210);
  • Step 209 the linkage service system 102 notifies the linkage terminal that originally held the authority token to regain control, and then performs step 210);
  • Step 210 the linkage service system 102 notifies the control terminal 101 to accept the request, and then performs step 211);
  • Step 211 the linkage service system 102 notifies the controlled terminal 103 that its corresponding authority token is assigned to the control terminal 101, and then performs step 212).
  • Step 212 the process ends.
  • the method further includes: releasing the permission token; specifically:
  • Step 301 the control terminal 101 initiates the exit linkage request, and then performs step 302);
  • Step 302 the linkage service system 102 reclaims the permission token, and then performs step 303);
  • Step 303 the linkage service system 102 notifies the controlled end 103 that the last linkage has been released, and then proceeds to step 304);
  • Step 304 the linkage service system 102 updates the linkage state, and then performs step 305);
  • Step 305 the linkage service system 102 notifies that the rejected control terminal 101 can re-initiate the application authority token request, and then performs step 306);
  • Step 306 the previously rejected control terminal 101 re-applies for the privilege token.
  • the invention realizes that a plurality of control terminals perform an ascending operation on a controlled terminal in an orderly manner, including orderly issuance, distribution, recovery and transfer of authority tokens;
  • the present invention sets a time window in which, when the control terminal initiates the acquisition of the permission token request again within a predetermined time window, it will be rejected, thereby improving the service efficiency of the device.
  • FIG. 1 is a schematic diagram of a linkage control right management apparatus of the present invention
  • FIG. 3 is a flow chart of releasing a rights token in the coordinated control right management method of the present invention.
  • Linkage refers to the operation of multiple linkage terminals to perform instruction and data synchronization interaction within the same service instance of the service system.
  • Linkage control right refers to the permission of a linkage terminal to perform linkage control on other linkage terminals.
  • the linkage control authority is used to identify and manage linkage control rights.
  • the linkage control right management apparatus of the present invention includes: a linkage service system 102 and a linkage terminal; wherein, there are multiple linkage terminals, and the linkage terminal can only serve as one type in the same service instance at the same time.
  • Role the control terminal 101 or the controlled terminal 103; the control terminal 101 acquires the authority token of the controlled terminal 103, and further performs linkage control on the controlled terminal 103.
  • the linkage service system 102 is configured to maintain a linkage terminal role, maintain a privilege token status, process or transit a privilege token application, and initiate or transfer a privilege token.
  • the linkage control right management device of the present invention will be further described below.
  • the role is applied to the linkage service system 102, and the linkage service system 102 configures the role for the linkage terminal.
  • the linkage service system 102 When the linkage terminal is configured as the role of the console, the linkage service system 102 will generate a unique linkage control authority token corresponding to the role of the controlled terminal, that is, the linkage token is issued by the linkage service system 102. When the linkage terminal is modified by the controlled terminal role to the console role, or after the line is offline, the linkage service system revokes the permission token.
  • a permission token of a controlled terminal can only be held by one control terminal at a time; and a control terminal can apply for or hold multiple permission tokens of the controlled terminal.
  • the role application command of the linkage terminal, the application, distribution, and collection instruction of the authority token are all passed through the linkage service system 102.
  • the rules for assigning or refusing to assign a privilege token include:
  • the arbitrator realizes the privilege token allocation.
  • the linkage service system 12 or the controlled terminal 13 can be selected as the arbitrator according to the service design requirement; the arbitrator selection rule is not limited to the static configuration and the dynamic application;
  • the arbitrator is the linkage service system 12, when the application for the privilege token is received by the control terminal 11, it is directly processed; if the arbitrator is the controlled terminal 13, the linkage service system 12 receives the application request for the privilege token. Transmitting the request to the controlled terminal 13 and processing it by the controlled terminal 13;
  • the arbitrator When the arbitrator receives the request for the privilege token from the control terminal 11, and determines that the privilege token is not held by the other control terminal 11, the arbitrator may directly assign the privilege token to the control terminal 11; The token has been used by others When the control terminal 11 is held, the arbitrator can reclaim the privilege token and reassign it to the control terminal 11, and likewise, the request can be rejected;
  • the arbitrator may reclaim the privilege token according to the state of the control terminal 11, and the state of the control terminal includes, without limitation, an online state, a session state, an interaction frequency, and whether the linkage control is over-authorized;
  • the linkage service system 12 actively notifies whether the control terminal 11 that has rejected the authority token request performs linkage control.
  • FIG. 2 is a flow chart of a rights token application, the application process includes:
  • Step 201 the control terminal 101 applies to the linkage service system 102 for a permission token
  • Step 202 after receiving the request, the linkage service system 102 determines whether the control terminal 101 has been rejected within a predetermined time, if it is rejected, step 203); otherwise, step 205);
  • Step 203 the linkage service system 102 determines whether the privilege token has been allocated, if it is assigned, step 204); otherwise, step 205);
  • Step 204 the linkage service system 102 rejects the linkage request, and restarts the timing; then performs step 212);
  • Step 205 the linkage service system 102 forwards the request to the corresponding arbitrator according to the configuration, and proceeds to 206);
  • Step 206 the arbitrator decides whether to accept the application, and notifies the linkage service system 102 of the arbitration result, and then performs step 207);
  • Step 207 the linkage service system 102 determines whether the result is rejected, if rejected, step 204), if accepted, step 208);
  • Step 208) the linkage service system 102 determines whether the permission token is assigned, if it is assigned, step 209); otherwise, step 210);
  • Step 209 the linkage service system 102 notifies the linkage terminal that originally held the authority token to regain control, and then performs step 210);
  • Step 210 the linkage service system 102 notifies the control terminal 101 to accept the request, and then performs step 211);
  • Step 211 the linkage service system 102 notifies the controlled terminal 103 that its corresponding authority token is assigned to the control terminal 101, and then performs step 212).
  • Step 212 the entire process ends.
  • 3 is a flow chart of the release of a privilege token, the release process including:
  • Step 301 the control terminal 101 initiates the exit linkage request, and then performs step 302);
  • Step 302 the linkage service system 102 reclaims the permission token, and then performs step 303);
  • Step 303 the linkage service system 102 notifies the controlled end 103 that the last linkage has been released, and then proceeds to step 304);
  • Step 304 the linkage service system 102 updates the linkage state, and then performs step 305);
  • Step 305 the linkage service system 102 notifies that the rejected control terminal 101 can re-initiate the application authority token request, and then performs step 306);
  • Step 306 the previously rejected control terminal 101 re-applies for the privilege token.
  • Step 306 the previously rejected control terminal 101 re-applies for the privilege token.
  • this step refer to the rights token application process described in FIG. 2.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明涉及一种联动控制权管理装置，包括联动服务系统、联动终端；其中，所述联动终端有多个，在同一个业务实例内、一个联动终端在同一时间内只能充当一种角色：控制端或被控制端；所述控制端获取被控制端的权限令牌，进而对该被控制端进行联动控制；所述联动服务系统用于维护联动终端角色，维护权限令牌状态，处理或中转权限令牌的申请，发起或中转权限令牌的回收。本发明实现了多个控制端有序对一台被控制端进行联动操作，包括权限令牌有序发放、分配、回收和转移。

Description

一种联动控制权管理装置及方法 技术领域
本发明涉及多终端联动技术，具体涉及一种联动控制权管理装置及方法。
背景技术
目前，随着多终端设备的普及，人们在使用业务时，常常不再满足于使用不同终端单独使用业务，而是要求利用多个终端进行多终端交互操作，从而方便用户操作，提升用户体验。
在多终端联动服务系统中，往往存在多个控制端同时向一个被控制端发起联动请求的情况，如多部手机绑定一台智能电视，多部手机可能同时向智能电视进行联动操作。为了保证多终端操作的有序性及可管理性，需要对控制端的权限令牌限进行有效管理。在现有技术中尚不存在对多终端联动操作进行有效管理的方法。
发明内容
本发明的目的在于克服现有技术中尚不存在对多终端联动操作进行有效管理的方法的缺陷，从而提供一种能够提高多终端联动的操作的友好性的联动控制权管理装置及方法。
为了实现上述目的，本发明提供了一种联动控制权管理装置，包括联动服务系统102、联动终端；其中，所述联动终端有多个，在同一个业务实例内、一个联动终端在同一时间内只能充当一种角色：控制端101或被控制端103；所述控制端101获取被控制端103的权限令牌，进而对该被控制端103进行联动控制；所述联动服务系统102用于维护联动终端角色，维护权限令牌状态，处理或中转权限令牌的申请，发起或中转权限令牌的回收。
上述技术方案中，所述联动终端上线后，向联动服务系统102申请角色，所述联动服务系统102为联动终端配置角色；当联动终端被配置为被控制端角色时，所述联动服务系统102为之生成与所述被控制端角色所对应的唯一的联动控制权限令牌，即由联动服务系统102为之颁发权限令牌；当联动终端由被控制端角色修改为控制端角色时、或下线后，联动服务系统102撤销该权限令牌。
上述技术方案中，一个被控制端103的权限令牌在同一时间内只能被一个控制端101持有；而一个控制端101能够申请或持有多个被控制端103的权限令牌。
上述技术方案中，所述控制端101向联动服务系统102申请联动权限令牌时，根据规则分配或拒绝分配权限令牌；其中，分配或拒绝分配权限令牌的规则包括：
(1)由仲裁者实现权限令牌分配，所述仲裁者由联动服务系统12或被控制端13充当；
(2)如果仲裁者是联动服务系统12，接收到控制端11请求权限令牌的申请时，直接处理；如果仲裁者是被控制终端13，联动服务系统12接收到权限令牌的申请请求后，把该请求转发被控制终端13，再由被控制终端13加以处理；
(3)当仲裁者接收到控制端11请求权限令牌的申请时，判断该权限令牌未被其他控制端11持有时，仲裁者直接向控制端11分配给该权限令牌；权限令牌已被其他控制端11持有时，仲裁者收回权限令牌，重新分配给该控制端11，或拒绝该次请求；
(4)当控制端11被拒绝权限令牌申请后，在预设的时间内，且该权限令牌已被其他控制端11持有时，若该控制端11再次请求同一个权限令牌，由联动服务系统12直接拒绝该次请求；
(5)仲裁者能够根据控制端11的状态回收权限令牌，所述控制端的状态包括不限于：在线状态、会话状态、交互频率、联动控制是否越权；
(6)当原来进行联动操作的控制端11退出联动控制时，联动服务系统12主动通知被拒绝过该权限令牌请求的控制端11是否进行联动控制。
上述技术方案中，联动终端的角色申请指令、权限令牌的申请、分配及回收指令都经过联动服务系统102。
本发明还提供了基于所述的联动控制权管理装置所实现的联动控制权管理方法，该方法包括权限令牌的申请，具体包括：
步骤201)、控制端101向联动服务系统102申请权限令牌；
步骤202)、联动服务系统102接收到请求后，判断该控制端101是否在预设定的时间内被拒绝过，如果被拒绝过，执行步骤203)；否则，执行步骤205)；
步骤203)、联动服务系统102判断该权限令牌是否已经被分配，如果被分配，执行步骤204)；否则，执行步骤205)；
步骤204)、联动服务系统102拒绝该次联动请求，并重新开始计时；然后执行步骤212)；
步骤205)、联动服务系统102根据配置把请求转发给对应的仲裁者，进行206)；
步骤206)、仲裁者决定是否接受该次申请，并把仲裁结果通知给联动服务系统102， 然后执行步骤207)；
步骤207)、联动服务系统102判断结果是否被拒绝，如果被拒绝，执行步骤204)，如果被接受，执行步骤208)；
步骤208)、联动服务系统102判断该次请求时，该权限令牌是否被分配，如果被分配，执行步骤209)；否则，执行步骤210)；
步骤209)、联动服务系统102通知原来持有该权限令牌的联动终端收回控制权，然后执行步骤210)；
步骤210)、联动服务系统102通知控制端101接受该次请求，然后执行步骤211)；
步骤211)、联动服务系统102通知被控制端103其所对应的权限令牌分配给该控制端101，然后执行步骤212)。
步骤212)、流程结束。
上述技术方案中，该方法还包括权限令牌的释放；具体包括：
步骤301)、控制端101发起退出联动请求，然后执行步骤302)；
步骤302)、联动服务系统102回收权限令牌，然后执行步骤303)；
步骤303)、联动服务系统102通知被控制端103上次联动已经解除，然后执行步骤304)；
步骤304)、联动服务系统102更新联动状态，然后执行步骤305)；
步骤305)、联动服务系统102通知被拒绝过的控制端101能够重新发起申请权限令牌请求，然后执行步骤306)；
步骤306)、之前被拒绝过的控制端101重新申请权限令牌。
本发明的优点在于：
1.本发明实现了多个控制端有序对一台被控制端进行联动操作，包括权限令牌有序发放、分配、回收和转移；
2.本发明设定时间窗口，在预定的时间窗口内，控制端再次发起获取权限令牌请求时，将被拒绝，从而提高装置的服务效率。
附图说明
图1是本发明的联动控制权管理装置的示意图；
图2是本发明的联动控制权管理方法中申请权限令牌的流程图；
图3是本发明的联动控制权管理方法中释放权限令牌的流程图。
具体实施方式
现结合附图对本发明作进一步的描述。
在对本发明做详细说明之前，首先对本发明中所涉及的概念做统一描述。
联动：是指多个联动终端在业务服务系统的同一业务实例内进行指令、数据同步交互的操作。
联动控制权：是指一个联动终端对其他联动终端进行联动控制的许可，在本发明中，用权限令牌对联动控制权进行标识和管理。
参考图1，本发明的联动控制权管理装置包括：联动服务系统102、联动终端；其中，所述联动终端有多个，在同一个业务实例内、联动终端在同一时间内只能充当一种角色：控制端101或被控制端103；所述控制端101获取被控制端103的权限令牌，进而对该被控制端103进行联动控制。所述联动服务系统102用于维护联动终端角色，维护权限令牌状态，处理或中转权限令牌的申请，发起或中转权限令牌的回收。
下面对本发明的联动控制权管理装置做进一步说明。
联动终端上线后，向联动服务系统102申请角色，联动服务系统102为联动终端配置角色。
当联动终端被配置为被控制端角色时，联动服务系统102将为之生成与所述被控制端角色所对应的唯一的联动控制权限令牌，即由联动服务系统102为之颁发权限令牌；当联动终端由被控制端角色修改为控制端角色时、或下线后，联动服务系统撤销该权限令牌。
一个被控制端的权限令牌在同一时间内只能被一个控制端持有；而一个控制端可以申请或持有多个被控制端的权限令牌。
联动终端的角色申请指令、权限令牌的申请、分配及回收指令都经过联动服务系统102。
控制端101向联动服务系统102申请联动权限令牌时，根据规则分配或拒绝分配权限令牌。其中，分配或拒绝分配权限令牌的规则包括：
(1)由仲裁者实现权限令牌分配，在本发明中可以根据业务设计要求选择联动服务系统12或被控制端13充当仲裁者；仲裁者的选择规则不限于静态配置、动态申请；
(2)如果仲裁者是联动服务系统12，接收到控制端11请求权限令牌的申请时，直接处理；如果仲裁者是被控制终端13，联动服务系统12接收到权限令牌的申请请求后，把该请求转发被控制终端13，再由被控制终端13加以处理；
(3)当仲裁者接收到控制端11请求权限令牌的申请时，判断该权限令牌未被其他控制端11持有时，仲裁者可以直接向控制端11分配给该权限令牌；权限令牌已被其他 控制端11持有时，仲裁者可以收回权限令牌，重新分配给该控制端11，同样，也可以拒绝该次请求；
(4)当控制端11被拒绝权限令牌申请后，在预设的时间内，且该权限令牌已被其他控制端11持有时，若该控制端11再次请求同一个权限令牌，由联动服务系统12直接拒绝该次请求；
(5)仲裁者可以根据控制端11的状态回收权限令牌，所述控制端的状态包括不限于：在线状态、会话状态、交互频率、联动控制是否越权；
(6)当原来进行联动操作的控制端11退出联动控制时，联动服务系统12主动通知被拒绝过该权限令牌请求的控制端11是否进行联动控制。
图2是权限令牌申请的流程图，该申请过程包括：
步骤201)、控制端101向联动服务系统102申请权限令牌；
步骤202)、联动服务系统102接收到请求后，判断该控制端101是否在预设定的时间内被拒绝过，如果被拒绝过，执行步骤203)；否则，执行步骤205)；
步骤203)、联动服务系统102判断该权限令牌是否已经被分配，如果被分配，执行步骤204)；否则，执行步骤205)；
步骤204)、联动服务系统102拒绝该次联动请求，并重新开始计时；然后执行步骤212)；
步骤205)、联动服务系统102根据配置把请求转发给对应的仲裁者，进行206)；
步骤206)、仲裁者决定是否接受该次申请，并把仲裁结果通知给联动服务系统102，然后执行步骤207)；
步骤207)、联动服务系统102判断结果是否被拒绝，如果被拒绝，执行步骤204)，如果被接受，执行步骤208)；
步骤208)、联动服务系统102判断该次请求时，该权限令牌是否被分配，如果被分配，执行步骤209)；否则，执行步骤210)；
步骤209)、联动服务系统102通知原来持有该权限令牌的联动终端收回控制权，然后执行步骤210)；
步骤210)、联动服务系统102通知控制端101接受该次请求，然后执行步骤211)；
步骤211)、联动服务系统102通知被控制端103其所对应的权限令牌分配给该控制端101，然后执行步骤212)。
步骤212)、整个流程结束。
图3是权限令牌释放的流程图，该释放过程包括：
步骤301)、控制端101发起退出联动请求，然后执行步骤302)；
步骤302)、联动服务系统102回收权限令牌，然后执行步骤303)；
步骤303)、联动服务系统102通知被控制端103上次联动已经解除，然后执行步骤304)；
步骤304)、联动服务系统102更新联动状态，然后执行步骤305)；
步骤305)、联动服务系统102通知被拒绝过的控制端101可以重新发起申请权限令牌请求，然后执行步骤306)；
步骤306)、之前被拒绝过的控制端101重新申请权限令牌。本步骤的具体执行可参见图2中所描述的权限令牌申请过程。
最后所应说明的是，以上实施例仅用以说明本发明的技术方案而非限制。尽管参照实施例对本发明进行了详细说明，本领域的普通技术人员应当理解，对本发明的技术方案进行修改或者等同替换，都不脱离本发明技术方案的精神和范围，其均应涵盖在本发明的权利要求范围当中。

Claims (7)

  1. 一种联动控制权管理装置，其特征在于，包括联动服务系统(102)、联动终端；其中，所述联动终端有多个，在同一个业务实例内、一个联动终端在同一时间内只能充当一种角色：控制端(101)或被控制端(103)；所述控制端(101)获取被控制端(103)的权限令牌，进而对该被控制端(103)进行联动控制；所述联动服务系统(102)用于维护联动终端角色，维护权限令牌状态，处理或中转权限令牌的申请，发起或中转权限令牌的回收。
  2. 根据权利要求1所述的联动控制权管理装置，其特征在于，所述联动终端上线后，向联动服务系统(102)申请角色，所述联动服务系统(102)为联动终端配置角色；当联动终端被配置为被控制端角色时，所述联动服务系统(102)为之生成与所述被控制端角色所对应的唯一的联动控制权限令牌，即由联动服务系统(102)为之颁发权限令牌；当联动终端由被控制端角色修改为控制端角色时、或下线后，联动服务系统(102)撤销该权限令牌。
  3. 根据权利要求1所述的联动控制权管理装置，其特征在于，一个被控制端(103)的权限令牌在同一时间内只能被一个控制端(101)持有；而一个控制端(101)能够申请或持有多个被控制端(103)的权限令牌。
  4. 根据权利要求1所述的联动控制权管理装置，其特征在于，所述控制端(101)向联动服务系统(102)申请联动权限令牌时，根据规则分配或拒绝分配权限令牌；其中，分配或拒绝分配权限令牌的规则包括：
    (1)由仲裁者实现权限令牌分配，所述仲裁者由联动服务系统(12)或被控制端(13)充当；
    (2)如果仲裁者是联动服务系统(12)，接收到控制端(11)请求权限令牌的申请时，直接处理；如果仲裁者是被控制终端(13)，联动服务系统(12)接收到权限令牌的申请请求后，把该请求转发被控制终端(13)，再由被控制终端(13)加以处理；
    (3)当仲裁者接收到控制端(11)请求权限令牌的申请时，判断该权限令牌未被其他控制端(11)持有时，仲裁者直接向控制端(11)分配给该权限令牌；权限令牌已被其他控制端11持有时，仲裁者收回权限令牌，重新分配给该控制端(11)，或拒绝该 次请求；
    (4)当控制端(11)被拒绝权限令牌申请后，在预设的时间内，且该权限令牌已被其他控制端(11)持有时，若该控制端(11)再次请求同一个权限令牌，由联动服务系统(12)直接拒绝该次请求；
    (5)仲裁者能够根据控制端(11)的状态回收权限令牌，所述控制端的状态包括不限于：在线状态、会话状态、交互频率、联动控制是否越权；
    (6)当原来进行联动操作的控制端(11)退出联动控制时，联动服务系统(12)主动通知被拒绝过该权限令牌请求的控制端(11)是否进行联动控制。
  5. 根据权利要求1所述的联动控制权管理装置，其特征在于，联动终端的角色申请指令、权限令牌的申请、分配及回收指令都经过联动服务系统(102)。
  6. 基于权利要求1-5之一的联动控制权管理装置所实现的联动控制权管理方法，该方法包括权限令牌的申请，具体包括：
    步骤201)、控制端(101)向联动服务系统(102)申请权限令牌；
    步骤202)、联动服务系统(102)接收到请求后，判断该控制端(101)是否在预设定的时间内被拒绝过，如果被拒绝过，执行步骤203)；否则，执行步骤205)；
    步骤203)、联动服务系统(102)判断该权限令牌是否已经被分配，如果被分配，执行步骤204)；否则，执行步骤205)；
    步骤204)、联动服务系统(102)拒绝该次联动请求，并重新开始计时；然后执行步骤212)；
    步骤205)、联动服务系统(102)根据配置把请求转发给对应的仲裁者，进行206)；
    步骤206)、仲裁者决定是否接受该次申请，并把仲裁结果通知给联动服务系统(102)，然后执行步骤207)；
    步骤207)、联动服务系统(102)判断结果是否被拒绝，如果被拒绝，执行步骤204)，如果被接受，执行步骤208)；
    步骤208)、联动服务系统(102)判断该次请求时，该权限令牌是否被分配，如果 被分配，执行步骤209)；否则，执行步骤210)；
    步骤209)、联动服务系统(102)通知原来持有该权限令牌的联动终端收回控制权，然后执行步骤210)；
    步骤210)、联动服务系统(102)通知控制端(101)接受该次请求，然后执行步骤211)；
    步骤211)、联动服务系统(102)通知被控制端(103)其所对应的权限令牌分配给该控制端(101)，然后执行步骤212)。
    步骤212)、流程结束。
  7. 根据权利要求6所述的联动控制权管理方法，其特征在于，该方法还包括权限令牌的释放；具体包括：
    步骤301)、控制端(101)发起退出联动请求，然后执行步骤302)；
    步骤302)、联动服务系统(102)回收权限令牌，然后执行步骤303)；
    步骤303)、联动服务系统(102)通知被控制端(103)上次联动已经解除，然后执行步骤304)；
    步骤304)、联动服务系统(102)更新联动状态，然后执行步骤305)；
    步骤305)、联动服务系统(102)通知被拒绝过的控制端(101)能够重新发起申请权限令牌请求，然后执行步骤306)；
    步骤306)、之前被拒绝过的控制端(101)重新申请权限令牌。
PCT/CN2015/096606 2015-10-23 2015-12-08 一种联动控制权管理装置及方法 WO2017067045A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15906561.4A EP3349409A4 (en) 2015-10-23 2015-12-08 Device and method for managing linkage control privilege
US15/756,070 US20180343267A1 (en) 2015-10-23 2015-12-08 Device and method for managing linkage control privilege

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510696121.9A CN106612253B (zh) 2015-10-23 2015-10-23 一种联动控制权管理装置及方法
CN201510696121.9 2015-10-23

Publications (1)

Publication Number Publication Date
WO2017067045A1 true WO2017067045A1 (zh) 2017-04-27

Family

ID=58556631

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/096606 WO2017067045A1 (zh) 2015-10-23 2015-12-08 一种联动控制权管理装置及方法

Country Status (4)

Country Link
US (1) US20180343267A1 (zh)
EP (1) EP3349409A4 (zh)
CN (1) CN106612253B (zh)
WO (1) WO2017067045A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112295233B (zh) * 2019-08-02 2024-04-12 厦门雅基软件有限公司 一种控制权转移的方法和系统
CN111752162B (zh) * 2020-06-28 2023-09-19 青岛海尔科技有限公司 用于撤销联动操作的方法和装置及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070283414A1 (en) * 2006-05-31 2007-12-06 Canon Kabushiki Kaisha Device management system, device management apparatus, device management method, program for implementing the method, and storage medium storing the program
CN102792633A (zh) * 2010-01-29 2012-11-21 英国电讯有限公司 访问控制
CN103039050A (zh) * 2010-02-24 2013-04-10 瑞典爱立信有限公司 用于在计算机网络中管理对被保护资源的访问以及委托授权的方法
CN103413425A (zh) * 2013-08-16 2013-11-27 王金友 一种智能家居系统手持遥控终端与家居设备对码的方法

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4677614A (en) * 1983-02-15 1987-06-30 Emc Controls, Inc. Data communication system and method and communication controller and method therefor, having a data/clock synchronizer and method
US4607256A (en) * 1983-10-07 1986-08-19 Honeywell, Inc. Plant management system
US4709347A (en) * 1984-12-17 1987-11-24 Honeywell Inc. Method and apparatus for synchronizing the timing subsystems of the physical modules of a local area network
JPH01256843A (ja) * 1988-03-25 1989-10-13 Ncr Corp リンク・コントロール・システム
US5634122A (en) * 1994-12-30 1997-05-27 International Business Machines Corporation System and method for multi-level token management for distributed file systems
US5751220A (en) * 1995-07-14 1998-05-12 Sensormatic Electronics Corporation Synchronized network of electronic devices including back-up master units
JP3658896B2 (ja) * 1996-11-26 2005-06-08 ソニー株式会社 情報信号伝送システム、再生装置及び表示装置
US7225256B2 (en) * 2001-11-30 2007-05-29 Oracle International Corporation Impersonation in an access system
JP2004080400A (ja) * 2002-08-19 2004-03-11 Matsushita Electric Ind Co Ltd 自動ロール決定システム
US7502793B2 (en) * 2004-02-10 2009-03-10 International Business Machines Corporation Method and apparatus for assigning roles to devices using physical tokens
US7685206B1 (en) * 2004-02-12 2010-03-23 Microsoft Corporation Authorization and access control service for distributed network resources
US7673135B2 (en) * 2005-12-08 2010-03-02 Microsoft Corporation Request authentication token
US7925023B2 (en) * 2006-03-03 2011-04-12 Oracle International Corporation Method and apparatus for managing cryptographic keys
US8141115B2 (en) * 2008-12-17 2012-03-20 At&T Labs, Inc. Systems and methods for multiple media coordination
US9557889B2 (en) * 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
CN101977184B (zh) * 2010-09-30 2013-06-19 西本新干线电子商务有限公司 多身份选择登录装置及服务系统
EP2533477B1 (en) * 2011-06-09 2014-03-05 9Solutions Oy Bluetooth network configuration
US8474056B2 (en) * 2011-08-15 2013-06-25 Bank Of America Corporation Method and apparatus for token-based virtual machine recycling
US20140181954A1 (en) * 2012-12-26 2014-06-26 Charles Cameron Robertson System for conveying an identity and method of doing the same
CN103023917B (zh) * 2012-12-26 2016-03-16 百度在线网络技术（北京）有限公司 针对智能家电进行授权的方法、系统和装置
US9541905B2 (en) * 2013-03-15 2017-01-10 Fisher-Rosemount Systems, Inc. Context sensitive mobile control in a process plant
US9838424B2 (en) * 2014-03-20 2017-12-05 Microsoft Technology Licensing, Llc Techniques to provide network security through just-in-time provisioned accounts
US20150312111A1 (en) * 2014-04-28 2015-10-29 Motorola Solutions, Inc Apparatus and method for distributing rule ownership among devices in a system
US20150370272A1 (en) * 2014-06-23 2015-12-24 Google Inc. Intelligent configuration of a smart environment based on arrival time
CN104283745A (zh) * 2014-09-12 2015-01-14 小米科技有限责任公司 控制智能家居设备的方法、装置和系统
US9473504B2 (en) * 2014-10-15 2016-10-18 Ayla Networks, Inc. Role based access control for connected consumer devices

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070283414A1 (en) * 2006-05-31 2007-12-06 Canon Kabushiki Kaisha Device management system, device management apparatus, device management method, program for implementing the method, and storage medium storing the program
CN102792633A (zh) * 2010-01-29 2012-11-21 英国电讯有限公司 访问控制
CN103039050A (zh) * 2010-02-24 2013-04-10 瑞典爱立信有限公司 用于在计算机网络中管理对被保护资源的访问以及委托授权的方法
CN103413425A (zh) * 2013-08-16 2013-11-27 王金友 一种智能家居系统手持遥控终端与家居设备对码的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3349409A4 *

Also Published As

Publication number Publication date
EP3349409A4 (en) 2018-12-12
EP3349409A1 (en) 2018-07-18
CN106612253A (zh) 2017-05-03
US20180343267A1 (en) 2018-11-29
CN106612253B (zh) 2019-10-22

Similar Documents

Publication Publication Date Title
JP6851457B2 (ja) メディア送信許可を申請するための方法、ならびにメディア送信許可を取り消すための方法および装置
GB2587169A (en) Secure delegation of a refresh token for long-running operations
JP2016526310A5 (zh)
CN102546808B (zh) 服务端基于tcp的交互处理方法
MY189479A (en) Service implementation method and device
CN106681840A (zh) 一种云操作系统的任务调度方法及装置
US11983564B2 (en) Scheduling of a plurality of graphic processing units
WO2015043528A1 (zh) 并行多线程报文处理的方法和装置
CN104461707A (zh) 一种锁请求处理方法及装置
WO2009030135A1 (fr) Procédé, dispositif et système pour attribuer une licence
WO2017067045A1 (zh) 一种联动控制权管理装置及方法
WO2016061935A1 (zh) 一种资源调度方法、装置及计算机存储介质
WO2018107945A1 (zh) 一种实现硬件资源分配的方法、装置及存储介质
CN103813481A (zh) 一种智能终端设备及其业务处理方法
WO2016173303A1 (zh) 一种处理共享文件的方法及装置
CN109076341A (zh) 蓝牙设备配对
CN110493175B (zh) 一种信息处理方法、电子设备和存储介质
CN102521043B (zh) 一种任务处理方法及应用系统
CN109193653B (zh) 一种功率分配的方法及装置
CN106776032A (zh) 分布式块存储的io请求的处理方法和装置
CN107239328A (zh) 任务分配方法及装置
WO2015188336A1 (zh) 一种临时移动群组标识tmgi的处理方法和设备
CN107203604A (zh) 一种数据分发管理方法、平台、装置及系统
CN105721337A (zh) 软件定义网络中的分布式事务处理方法及装置
CN106656535B (zh) 用于资源调度的方法和设备

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15756070

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE