WO2016029545A1 - 一种硬件通信装置的共享方法及终端 - Google Patents

一种硬件通信装置的共享方法及终端 Download PDF

Info

Publication number
WO2016029545A1
WO2016029545A1 PCT/CN2014/090120 CN2014090120W WO2016029545A1 WO 2016029545 A1 WO2016029545 A1 WO 2016029545A1 CN 2014090120 W CN2014090120 W CN 2014090120W WO 2016029545 A1 WO2016029545 A1 WO 2016029545A1
Authority
WO
WIPO (PCT)
Prior art keywords
hardware communication
data
communication device
queued
hardware
Prior art date
Application number
PCT/CN2014/090120
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 EP14900615.7A priority Critical patent/EP3196762A1/en
Publication of WO2016029545A1 publication Critical patent/WO2016029545A1/zh
Priority to US15/439,827 priority patent/US20170161115A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • 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/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
    • G06F21/74—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information operating in dual or compartmented mode, i.e. at least one secure mode
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5044—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering hardware capabilities
    • 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/60—Protecting data
    • G06F21/606—Protecting data by securing the transmission between two devices or processes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/542—Intercept
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/548—Queue

Definitions

  • the present invention relates to the field of terminal technologies, and in particular, to a method and a terminal for sharing a hardware communication device based on multiple systems.
  • the hardware communication device configured in the terminal such as a wireless communication device, may specifically be a device such as Near Field Communication (NFC), WIFI, Bluetooth, or infrared.
  • NFC Near Field Communication
  • WIFI Wireless Fidelity
  • Bluetooth Wireless Fidelity
  • infrared Infrared
  • the above hardware communication device is a device other than the main chip of the terminal.
  • each operating system exclusively uses the hardware communication device, that is, when one of the systems occupies the hardware communication device, another system can only be processed.
  • the stop state affects the user experience.
  • the present invention provides a sharing method and terminal of a hardware communication device, so as to enable multiple systems to be enabled Sharing the hardware communication device to enhance the user experience.
  • a hardware communication device sharing method the hardware communication device sharing method being applied to a multi-operating system terminal, the hardware communication device sharing method comprising the steps of:
  • the system that takes over the hardware communication device transmits the queued pending data to the hardware communication device
  • the hardware communication device processes the to-be-processed data in a queued order.
  • the queuing mechanism queues in the chronological order in which the data processing requests are initiated by each system.
  • the multi-system includes a security system and a general system, and the system that takes over the hardware communication device is a security system.
  • the priority of the data processing request of the security system is greater than the priority of the data processing of the common system, and the data processing request sent by the security system is sent to the data processing request sent by the common system. prior to.
  • an arbitration mechanism is further provided, the arbitration mechanism sets a maximum value of the processed data to be queued, and the total amount of data processed by the hardware communication device in the multiple systems reaches the hardware.
  • the communication device processes the maximum value of the data, it will no longer receive the data transmission request from each system.
  • the method further includes:
  • the method for sharing the hardware communication device further includes:
  • the results of processing the data by the hardware communication device are fed back to each system.
  • a takeover module configured to take over the hardware communication module by using one of the multiple systems
  • a setting module configured to set a queuing mechanism in a system that takes over the hardware communication device
  • a request receiving module configured to receive, according to the queuing mechanism, a data processing request sent by multiple systems
  • a data processing module configured to receive data corresponding to the queued processing data request sent by the multiple system, and send the data corresponding to the queued processing data request to the hardware communication module;
  • the hardware communication module is configured to perform communication processing on data according to a queue order.
  • the terminal further includes a feedback module, and the feedback module is configured to feed back, to each system, a result of processing the data by the hardware communication device.
  • the setting module is further configured to set an arbitration mechanism, where the arbitration mechanism sets a maximum value of the processed data to be queued, and the total amount of data processed by the hardware communication device in the multiple systems reaches the hardware communication device processing data. The maximum value will no longer receive data processing requests from each system.
  • the shared method machine terminal of the hardware communication device provided by the technical solution can be applied to a multi-system shared hardware communication device, and a queuing mechanism is set in a system that takes over the hardware communication device by adopting a system to take over the hardware communication device. And receiving the processing data request sent by each system to be queued, and sending the data of the queued data processing request to the system that takes over the hardware communication device, so that the hardware communication device can perform the data to be processed according to the queued order. deal with. Further, the multi-system sharing of the hardware communication device can be realized, and the problem that the multi-system user's use experience is improved in the prior art, because one system monopolizes the hardware communication device, and other systems cannot apply the hardware communication device.
  • FIG. 1 is a flowchart of a method for sharing a hardware communication device according to an embodiment of the present invention
  • FIG. 2 is a structural block diagram of a terminal according to an embodiment of the present invention.
  • a first embodiment of the technical solution provides a hardware communication device sharing method.
  • the hardware communication device sharing method of the embodiment of the present invention is applied to a terminal having two or more operating systems, and may be, for example, a mobile phone having dual systems.
  • the two operating systems are defined as a first system and a second system, respectively.
  • one of the first system and the second system may be a security system, and the other one may be a general system.
  • the terminal has a hardware communication device independent of the terminal main chip, and the hardware communication device may be a communication device such as NFC, WIFI, Bluetooth, and infrared equipped with the terminal.
  • the hardware communication device sharing method includes the steps of:
  • the hardware communication device can be associated with a designated operating system such that the developed operating system takes over the hardware communication device.
  • the first system is used to take over the hardware communication device.
  • the first system can be a security system.
  • a queuing mechanism for processing to be processed by the hardware communication device is set in the first system. Specifically, the order and rules of data to be processed by the hardware communication device in the first system and the second system are set. If you can queue according to the time sequence in which each system initiates a data processing request, you can also queue according to the limited level of the two systems. If the priority of the data processing request of the security system can be set to be greater than the priority level of the data processing of the common system, the data processing request initiated by the security system can be preferentially processed, and the data processing request sent by the security system is ranked in the Before the data processing request sent by the normal system.
  • the arbitration mechanism can be set at the same time. If set to queue When the maximum value of the processed data, that is, the total amount of data to be processed by the hardware communication device in the two systems reaches this number, the maximum value of the data processed by the hardware communication device has been reached, and no more data processing can be performed. The first system and the second system will no longer accept data processing requests.
  • the arbitration mechanism may further include an adjustment to the queuing order when the urgency of the data request sent by the first system and the second system. For example, the user can set the urgency of different data requests according to the urgency of processing data. For data processing requests with higher urgency, priority can be given during queuing to be arranged at a higher position so that the hardware communication device can prioritize processing.
  • the first system receives the data processing request sent by each system according to the queuing mechanism, and after receiving the data processing request sent by each system, determines whether the queuing of the currently pending data request is full. That is, whether the data to be processed currently queued has reached the maximum value of the data that can be queued, and if the request for the currently scheduled data to be processed has reached the maximum value, the data processing request received subsequently is rejected. If the currently scheduled data to be queued does not reach the maximum value, the data processing request is accepted, that is, the data processing request is queued.
  • the first system receives data corresponding to the queued data processing request.
  • the second system may send data corresponding to the queued data processing request to the first system by using a system channel between the first system and the second system.
  • the data to be processed in each system can be sent to the system that takes over the hardware communication device in the same manner.
  • the first system takes over the hardware communication device, and the first system may send the received data to be processed by each system to the hardware communication device.
  • the hardware communication device processes the to-be-processed data according to a queuing sequence.
  • the hardware communication device may process the data to be processed received by the hardware communication device in the order of queuing, such as using NFC, WIFI, Bluetooth, or infrared communication methods for data exchange. mutual.
  • the hardware communication device sharing method may further include:
  • the hardware communication device processes the queued data, the processing result is fed back to the system corresponding to the processed data.
  • the sharing method of the hardware communication device provided by the technical solution can be applied to a multi-system shared hardware communication device, and a queuing mechanism is set in the system that takes over the hardware communication device by using a system to take over the hardware communication device, and receiving The processing data requests sent by the systems are queued, and the data of the queued data processing requests are sent to the system that takes over the hardware communication device, so that the hardware communication device can process the data to be processed in the queued order.
  • the multi-system sharing of the hardware communication device can be realized, and the problem that the multi-system user's use experience is improved in the prior art, because one system monopolizes the hardware communication device, and other systems cannot apply the hardware communication device.
  • the technical solution further provides a terminal 100.
  • the terminal 100 has two or more multi-system terminals, and the multi-system includes a security system and a general system.
  • the terminal 100 can be a dual system mobile phone.
  • the terminal 100 includes a hardware communication module 110, a takeover module 120, a setting module 130, a request receiving module 140, a data processing module 150, and a feedback module 160.
  • the hardware communication module 110 is configured to perform communication processing on data.
  • the hardware communication module 110 may be a hardware communication device independent of the terminal main chip, and the hardware communication device may be a communication device such as NFC, WIFI, Bluetooth, infrared, etc. equipped with the terminal.
  • the takeover module 120 is configured to take over the hardware communication module 110 by using one of the multiple systems.
  • the hardware communication module 110 can be associated with a designated operating system such that the developed operating system takes over the hardware communication module 110.
  • the hardware communication module 110 is taken over by a security system.
  • the setting module 130 is configured to set a queuing mechanism in a system that takes over the hardware communication device.
  • the setting module 130 is configured to set the hardware to be used in the security system.
  • the queuing mechanism of the data processed by the letter module Specifically, the order and rules of the data to be processed by the hardware communication device are set. If you can queue in the order in which the data processing requests are initiated, you can also queue them according to the limited levels of the two systems. If the priority of the data processing request of the security system can be set to be greater than the priority of the data processing of the common system, the data processing request initiated by the security system can be preferentially processed.
  • the setting module 130 can also set an arbitration mechanism. If the total amount of processing data to be queued is set, that is, the total amount of data to be processed by the hardware communication device in the two systems reaches this number, the maximum value of the data processed by the hardware communication device has been reached, and no further can be performed. Multi-data processing, at this time, the first system and the second system will no longer receive the data processing request.
  • the arbitration mechanism may further include an adjustment to the queuing order when the urgency of the data request sent by the first system and the second system. For example, the user can set the urgency of different data requests according to the urgency of processing data. For data processing requests with higher urgency, priority can be given during queuing to be arranged at a higher position so that the hardware communication device can prioritize processing.
  • the request receiving module 140 is configured to receive a data processing request sent by multiple systems according to the queuing mechanism.
  • the receiving module 140 receives the data processing request sent by each system according to the queuing mechanism, and after receiving the data processing request sent by each system, determines whether the queuing of the currently pending data request is full. That is, whether the data to be processed currently queued has reached the maximum value of the data that can be queued, and if the request for the currently queued data to be processed has reached the maximum value, the subsequent received data processing request is rejected. If the currently scheduled data to be queued does not reach the maximum value, the data processing request is accepted, that is, the data processing request is queued.
  • the data processing module 150 is configured to receive data corresponding to the queued processing data request sent by the multiple systems, and send data corresponding to the queued processing data request to the hardware communication module 110, so that the hardware communication module 110 Queued to process data for processing.
  • the data processing module 150 may pass a system channel between the first system and the second system, and other systems may send data corresponding to the queued data processing request to the hardware communication module 110. system.
  • the feedback module 160 is configured to feed back the results of the hardware communication device processing data to each system.
  • the feedback module 160 feeds back the processing result to the system corresponding to the processed data.
  • the terminal provided by the technical solution can implement a multi-system shared hardware communication module, and adopts a system to take over the hardware communication device, set a queuing mechanism in a system that takes over the hardware communication device, and receive processing data sent by each system.
  • the request is queued, and the data of the queued data processing request is sent to the system that takes over the hardware communication device, so that the hardware communication device can process the data to be processed in the queued order.
  • the multi-system sharing hardware communication module can be implemented, and the problem that the multi-system user's use experience is improved in the prior art is that the system monopolizes the hardware communication device and the other system cannot apply the hardware communication device.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Mathematical Physics (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种硬件通信装置共享方法，硬件通信装置共享方法应用于具有多操作系统终端中，硬件通信装置共享方法包括步骤：采用多系统中的其中一个系统接管硬件通信装置；在接管硬件通信装置的系统中设置排队机制；按照排队机制接收多系统发送的数据处理请求；接收多系统发送的进行排队处理数据请求对应的数据；所述接管所述硬件通信装置的系统发送排队的待处理数据至硬件通信装置；以及所述硬件通信装置按照排队顺序对所述待处理数据进行处理。本发明还对应提供一种终端。本发明能够解决现有技术中在在多系统终端中，其中一个系统在占用所述硬件通信装置时，另外的系统地处理只能处于停止状态，影响另外系统的用户使用体验的问题。

Description

一种硬件通信装置的共享方法及终端 技术领域
本发明涉及终端技术领域，具体而言涉及一种基于多系统的硬件通信装置的共享方法及终端。
背景技术
目前，智能手机的一个重要特点是使用开放性的操作系统，如iOS、Android等。在这样的操作系统平台上可以安装很多第三方应用程序，使得手机的功能得到扩展，但是同时使得病毒和恶意软件等容易入侵，造成用户的通话、短信、联系人等隐私数据泄漏。为了提高手机的安全性，目前出现了具有双操作系统的手机，其具有两个操作系统，其中一个操作系统可以用于处理普通事务，一般称为普通系统；另一个操作系统则用于处理涉密或隐私的事务，一般称为安全系统。当然，终端中还可以具有更多的操作系统。
但是，终端中配置的硬件通信装置如无线通信装置，具体可以为近场通信(Near Field Communication，NFC)、WIFI、蓝牙或者红外等装置。上述硬件通信装置是独立于终端的主芯片之外的设备。现有的终端在运行两个以上操作系统时，每个操作系统对所述的硬件通信装置都是独占使用，即其中一个系统在占用所述硬件通信装置时，另外的系统地处理只能处于停止状态，影响用户使用体验。
发明内容
本发明提供一种硬件通信装置的共享方法及终端，以能够使得多系统能够 共享所述硬件通信装置，提升用户的使用体验。
一种硬件通信装置共享方法，所述硬件通信装置共享方法应用于具有多操作系统终端中，所述硬件通信装置共享方法包括步骤：
采用多系统中的其中一个系统接管所述硬件通信装置；
在接管所述硬件通信装置的系统中设置排队机制；
按照所述排队机制接收多系统发送的数据处理请求；
接收多系统发送的进行排队处理数据请求对应的数据；
所述接管所述硬件通信装置的系统发送排队的待处理数据至硬件通信装置；以及
所述硬件通信装置按照排队顺序对所述待处理数据进行处理。
其中，所述排队机制按照按照各系统发起数据处理请求的时间顺序进行排队。
其中，所述多系统包括安全系统及普通系统，所述接管所述硬件通信装置的系统为安全系统。
其中，所述排队机制设置所述安全系统的数据处理请求的优先级别大于所述普通系统的数据处理的优先级别，所述安全系统发送的数据处理请求排在所述普通系统发送的数据处理请求之前。
其中，在接管所述硬件通信装置的系统中还设置有仲裁机制，所述仲裁机制设置进行排队的处理数据的最大值，多系统中需要采用硬件通信装置处理的数据的总量达到所述硬件通信装置处理数据的最大值，则将不再接收各系统发送数据处理请求。
其中，接收到所述各系统发送的数据处理请求之后，还包括：
判断当前进行排队的待处理数据请求是否已经达到能够排队的数据的最大值，若当前进行排队的待处理数据的请求已经达到最大值，则拒绝接后续收到的数据处理请求，若当前进行排队的待处理数据没有达到最大值，则接受所述数据处理请求，对所述数据处理请求进行排队。
其中，所述硬件通信装置共享方法还包括：
向各系统反馈所述硬件通信装置处理数据后的结果。
一种终端，其具有多系统并具有硬件通信模块，所述硬件通信模块为独立于所述终端主芯片的硬件通信装置，所述终端还包括：
接管模块，用于采用所述多系统中一个系统接管所述硬件通信模块；
设置模块，用于在接管所述硬件通信装置的系统中设置排队机制；
请求接收模块，用于按照所述排队机制接收多系统发送的数据处理请求；
数据处理模块，用于接收多系统发送的进行排队处理数据请求对应的数据，并将进行排队处理数据请求对应的数据发送至硬件通信模块；
所述硬件通讯模块用于按照排队顺序对数据进行通信处理。
其中，所述终端还包括反馈模块，所述反馈模块用于向各系统反馈所述硬件通信装置处理数据后的结果。
其中，所述设置模块还用于设置仲裁机制，所述仲裁机制设置进行排队的处理数据的最大值，多系统中需要采用硬件通信装置处理的数据的总量达到所述硬件通信装置处理数据的最大值，则将不再接收各系统发送数据处理请求。
本技术方案提供的硬件通信装置的共享方法机终端，可以应用于多系统的共享硬件通信装置，通过采用一个系统接管所述硬件通信装置，在接管所述硬件通信装置的系统中设置排队机制，并接收各系统发送的处理数据请求进行排队，将进行排队的数据处理请求的数据发送至接管所述硬件通信装置的系统中，从而可以使得所述硬件通信装置可以按照排队顺序对待处理的数据进行处理。进而可以实现多系统共享所述硬件通信装置，可以解决现有技术中，由于一个系统独占硬件通信装置，而其他系统不能应用硬件通信装置的问题，提高了多系统用户的使用体验。
附图说明
图1是本发明实施例的硬件通信装置共享方法的流程图；
图2是本发明实施例提供的终端的结构框图。
具体实施方式
为更进一步阐述本发明为达成预定目的所采取的技术手段及功效，以下结合附图及较佳实施例，对本发明进行详细说明如后。
请参阅图1，本技术方案的第一实施方式提供一种硬件通信装置共享方法。本发明实施例的硬件通信装置共享方法应用于具有两个以上操作系统的终端中，例如可以是具有双系统的手机。定义两个操作系统分别为第一系统和第二系统。具体的，第一系统和第二系统中的一个可以为安全系统，而另外一个可以为普通系统。所述终端具有一个独立于终端主芯片的硬件通信装置，所述硬件通信装置可以为所述终端配备的NFC、WIFI、蓝牙、以及红外等通信装置。所述硬件通信装置共享方法包括步骤：
S101，采用多系统中的其中一个系统接管所述硬件通信装置。
由于终端中具有两个或者两个以上操作系统，可以将所述硬件通信装置与指定的操作系统相关联，从而使得所述制定的操作系统接管所述硬件通信装置。本实施方式中，采用第一系统接管所述所述硬件通信装置。所述第一系统可以为安全系统。
S102，在接管所述硬件通信装置的系统中设置排队机制。
本实施方式中，在所述第一系统中设置待所述硬件通信装置处理的处理的排队机制。具体的，设置第一系统和第二系统中待所述硬件通信装置处理的数据的排列顺序及规则。如可以按照各系统发起数据处理请求的时间顺序进行排队，也可以按照两个系统的有限级别进行排队。如可以设定安全系统的数据处理请求的优先级别大于所述普通系统的数据处理的优先级别，可以将安全系统发起的数据处理请求优先进行处理，所述安全系统发送的数据处理请求排在所述普通系统发送的数据处理请求之前。
可以理解的是，在本步骤中，同时可以设置仲裁机制。如设定进行排队的 处理数据的最大值，即两个系统中需要采用硬件通信装置处理的数据的总量达到此数量时，已经达到所述硬件通信装置处理数据的最大值，不能再进行更多数据的处理，此时则将不再接受第一系统和第二系统发送数据处理请求。
所述仲裁机制还可以进一步包括当第一系统和第二系统发送的数据请求的紧急程度而对排队顺序的调整。如用户可以根据处理数据的紧急程度设置不同数据请求的紧急程度。对于紧急程度较高的数据处理请求，可以在排队时进行优先，以排列在较靠前的位置，以使得硬件通信装置能够优先进行处理。
S103，按照所述排队机制接收多系统发送的数据处理请求。
所述第一系统按照所述排队机制，接收每个系统发送的数据处理请求，并在接收到所述各系统发送的数据处理请求之后，判断当前进行排队的待处理数据请求的排队是否已满，即当前进行排队的待处理数据是否已经达到能够排队的数据的最大值，若当前进行排队的待处理数据的请求已经达到最大值，则拒绝接受后续收到的数据处理请求。如果当前进行排队的待处理数据没有达到最大值，则接受所述数据处理请求，即对所述数据处理请求进行排队。
S104，接收多系统发送的进行排队处理数据请求对应的数据。
本实施方式中，所述第一系统接收排队的数据处理请求对应的数据。具体的，通过第一系统和第二系统之间系统通道，第二系统可以将排队的数据处理请求对应的数据发送至第一系统。当具有多个系统时，可以采用相同的方式，将各系统中的需要处理的数据发送至接管所述硬件通信装置的系统中。
S105，所述接管所述硬件通信装置的系统发送排队的待处理数据至硬件通信装置。
本实施方式中，所述第一系统接管所述硬件通信装置，所述第一系统可以将接收到的各系统待处理数据发送至硬件通信装置。
S106，所述硬件通信装置按照排队顺序对所述待处理数据进行处理。
所述硬件通信装置可以按照排队的顺序，对所述硬件通信装置接收的待处理数据进行处理，如采用NFC、WIFI、蓝牙或者红外等通信方式进行数据的交 互。
所述硬件通信装置共享方法还可以进一步包括：
S107，向各系统反馈所述硬件通信装置处理数据后的结果。
当硬件通信装置对排队的数据进行处理后，反馈处理结果给被处理数据对应的系统。
本技术方案提供的硬件通信装置的共享方法，可以应用于多系统的共享硬件通信装置，通过采用一个系统接管所述硬件通信装置，在接管所述硬件通信装置的系统中设置排队机制，并接收各系统发送的处理数据请求进行排队，将进行排队的数据处理请求的数据发送至接管所述硬件通信装置的系统中，从而可以使得所述硬件通信装置可以按照排队顺序对待处理的数据进行处理。进而可以实现多系统共享所述硬件通信装置，可以解决现有技术中，由于一个系统独占硬件通信装置，而其他系统不能应用硬件通信装置的问题，提高了多系统用户的使用体验。
请参阅图2，本技术方案还对应提供一种终端100，所述终端100具有两个或两个以上的多系统终端，所述多系统包括安全系统及普通系统。所述终端100可以为双系统手机。所述终端100包括硬件通信模块110、接管模块120、设置模块130、请求接收模块140、数据处理模块150以及反馈模块160。
所述硬件通信模块110用于对数据进行通信处理。所述硬件通信模块110可以为独立于终端主芯片的硬件通信装置，所述硬件通信装置可以为所述终端配备的NFC，WIFI，蓝牙，红外等通信装置。
所述接管模块120用于采用多系统中一个系统接管所述硬件通信模块110。
由于终端100中具有两个或者两个以上操作系统，可以将所述硬件通信模块110与指定的操作系统相关联，从而使得所述制定的操作系统接管所述硬件通信模块110。本实施方式中，采用安全系统接管所述所述硬件通信模块110。
所述设置模块130用于在接管所述硬件通信装置的系统中设置排队机制。
本实施例中，所述设置模块130用于在所述安全系统中设置待所述硬件通 信模块处理的数据的排队机制。具体的，设置待所述硬件通信装置处理的数据的排列顺序及规则。如可以按照发起数据处理请求的时间顺序进行排队，也可以按照两个系统的有限级别进行排队。如可以设定安全系统的数据处理请求的优先级别大于所述普通系统的数据处理的优先级别，可以将安全系统发起的数据处理请求优先进行处理。
可以理解的是，所述设置模块130也可以设置仲裁机制。如设定进行排队的处理数据的总量，即两个系统中需要采用硬件通信装置处理的数据的总量达到此数量时，已经达到所述硬件通信装置处理数据的最大值，不能再进行更多数据的处理，此时则将不再接收第一系统和第二系统发送数据处理请求。所述仲裁机制还可以进一步包括当第一系统和第二系统发送的数据请求的紧急程度而对排队顺序的调整。如用户可以根据处理数据的紧急程度设置不同数据请求的紧急程度。对于紧急程度较高的数据处理请求，可以在排队时进行优先，以排列在较靠前的位置，以使得硬件通信装置能够优先进行处理。
所述请求接收模块140用于按照所述排队机制接收多系统发送的数据处理请求。
所述接收模块140按照所述排队机制，接收每个系统发送的数据处理请求，并在接收到所述各系统发送的数据处理请求之后，判断当前进行排队的待处理数据请求的排队是否已满，即当前进行排队的待处理数据是否已经达到能够排队的数据的最大值，若果当前进行排队的待处理数据的请求已经达到最大值，则拒绝接后续收到的数据处理请求。如果当前进行排队的待处理数据没有达到最大值，则接受所述数据处理请求，即对所述数据处理请求进行排队。
所述数据处理模块150用于接收多系统发送的进行排队处理数据请求对应的数据，并将进行排队处理数据请求对应的数据发送至硬件通信模块110，以使得所述硬件通信模块110对所述排队处理数据进行处理。
所述数据处理模块150可以通过第一系统和第二系统之间系统通道，其它系统可以将排队的数据处理请求对应的数据发送至接管所述硬件通信模块110 的系统。
所述反馈模块160用于向各系统反馈所述硬件通信装置处理数据后的结果。
当硬件通信模块110对排队的数据进行处理后，所述反馈模块160反馈处理结果给被处理数据对应的系统。
本技术方案提供的终端，可以实现多系统的共享硬件通信模块，通过采用一个系统接管所述硬件通信装置，在接管所述硬件通信装置的系统中设置排队机制，并接收各系统发送的处理数据请求进行排队，将进行排队的数据处理请求的数据发送至接管所述硬件通信装置的系统中，从而可以使得所述硬件通信装置可以按照排队顺序对待处理的数据进行处理。进而可以实现多系统共享所述硬件通信模块，可以解决现有技术中，由于一个系统独占硬件通信装置，而其他系统不能应用硬件通信装置的问题，提高了多系统用户的使用体验。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (10)

  1. 一种硬件通信装置共享方法，所述硬件通信装置共享方法应用于具有多操作系统终端中，所述硬件通信装置共享方法包括步骤：
    采用多系统中的其中一个系统接管所述硬件通信装置；
    在接管所述硬件通信装置的系统中设置排队机制；
    按照所述排队机制接收多系统发送的数据处理请求；
    接收多系统发送的进行排队处理数据请求对应的数据；
    所述接管所述硬件通信装置的系统发送排队的待处理数据至硬件通信装置；以及
    所述硬件通信装置按照排队顺序对所述待处理数据进行处理。
  2. 如权利要求1所述的硬件通信装置共享方法，其特征在于，所述排队机制按照各系统发起数据处理请求的时间顺序进行排队。
  3. 如权利要求1所述的硬件通信装置共享方法，其特征在于，所述多系统包括安全系统及普通系统，所述接管所述硬件通信装置的系统为安全系统。
  4. 如权利要求3所述的硬件通信装置共享方法，其特征在于，所述排队机制设置所述安全系统的数据处理请求的优先级别大于所述普通系统的数据处理的优先级别，所述安全系统发送的数据处理请求排在所述普通系统发送的数据处理请求之前。
  5. 如权利要求1所述的硬件通信装置共享方法，其特征在于，在接管所述硬件通信装置的系统中还设置有仲裁机制，所述仲裁机制设置进行排队的处理数据的最大值，多系统中需要采用硬件通信装置处理的数据的总量达到所述硬件通信装置处理数据的最大值，则将不再接收各系统发送数据处理请求。
  6. 如权利要求5所述的硬件通信装置共享方法，其特征在于，接收到所述各系统发送的数据处理请求之后，还包括：
    判断当前进行排队的待处理数据请求是否已经达到能够排队的数据的最大值，若当前进行排队的待处理数据的请求已经达到最大值，则拒绝接后续收到 的数据处理请求，若当前进行排队的待处理数据没有达到最大值，则接受所述数据处理请求，对所述数据处理请求进行排队。
  7. 如权利要求1所述的硬件通信装置共享方法，其特征在于，所述硬件通信装置共享方法还包括：
    向各系统反馈所述硬件通信装置处理数据后的结果。
  8. 一种终端，其具有多系统并具有硬件通信模块，所述硬件通信模块为独立于所述终端主芯片的硬件通信装置，所述终端还包括：
    接管模块，用于采用所述多系统中一个系统接管所述硬件通信模块；
    设置模块，用于在接管所述硬件通信装置的系统中设置排队机制；
    请求接收模块，用于按照所述排队机制接收多系统发送的数据处理请求；
    数据处理模块，用于接收多系统发送的进行排队处理数据请求对应的数据，并将进行排队处理数据请求对应的数据发送至硬件通信模块；
    所述硬件通讯模块用于按照排队顺序对数据进行通信处理。
  9. 如权利要求8所述的终端，其特征在于，所述终端还包括反馈模块，所述反馈模块用于向各系统反馈所述硬件通信装置处理数据后的结果。
  10. 如权利要求8所述的终端，其特征在于，所述设置模块还用于设置仲裁机制，所述仲裁机制设置进行排队的处理数据的最大值，多系统中需要采用硬件通信装置处理的数据的总量达到所述硬件通信装置处理数据的最大值，则将不再接收各系统发送数据处理请求。
PCT/CN2014/090120 2014-08-25 2014-10-31 一种硬件通信装置的共享方法及终端 WO2016029545A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14900615.7A EP3196762A1 (en) 2014-08-25 2014-10-31 Sharing method for hardware communication apparatus and terminal
US15/439,827 US20170161115A1 (en) 2014-08-25 2017-02-22 Sharing Method for Hardware Communication Apparatus and Terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410423083.5A CN104298546A (zh) 2014-08-25 2014-08-25 一种硬件通信装置的共享方法及终端
CN201410423083.5 2014-08-25

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/439,827 Continuation-In-Part US20170161115A1 (en) 2014-08-25 2017-02-22 Sharing Method for Hardware Communication Apparatus and Terminal

Publications (1)

Publication Number Publication Date
WO2016029545A1 true WO2016029545A1 (zh) 2016-03-03

Family

ID=52318286

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/090120 WO2016029545A1 (zh) 2014-08-25 2014-10-31 一种硬件通信装置的共享方法及终端

Country Status (4)

Country Link
US (1) US20170161115A1 (zh)
EP (1) EP3196762A1 (zh)
CN (1) CN104298546A (zh)
WO (1) WO2016029545A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105744506A (zh) * 2016-03-31 2016-07-06 宇龙计算机通信科技(深圳)有限公司 硬件共享方法、硬件共享装置和终端
CN107135313A (zh) * 2017-06-19 2017-09-05 深圳市筑泰防务智能科技有限公司 硬件物理隔离双系统手机
CN108833498B (zh) * 2018-05-25 2021-06-25 上海芯爱智能科技有限公司 一种终端的通信方法、终端及存储介质
CN109714476B (zh) * 2018-12-19 2021-05-07 惠州Tcl移动通信有限公司 数据处理方法、装置、移动终端及存储介质
CN112788658B (zh) * 2019-11-11 2024-05-24 鹤壁天海电子信息系统有限公司 一种通信设备的共享数据方法、通信设备及存储介质
CN115080125A (zh) * 2021-03-12 2022-09-20 Oppo广东移动通信有限公司 共用硬件调用的方法、装置、电子设备以及存储介质
CN113727418A (zh) * 2021-09-01 2021-11-30 广州朗国电子科技股份有限公司 电子白板双系统组网系统、方法、电子白板和可读介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101383626A (zh) * 2007-09-05 2009-03-11 宏达国际电子股份有限公司 移动装置及其操作系统间共用无线通讯模块的方法
CN101989942A (zh) * 2009-08-07 2011-03-23 无锡江南计算技术研究所 仲裁控制方法、通信方法、仲裁器和通信系统
CN103377093A (zh) * 2012-04-24 2013-10-30 联想(北京)有限公司 一种多系统设备的多媒体同步方法、电子设备
CN103391374A (zh) * 2013-08-08 2013-11-13 北京邮电大学 一种支持无缝切换的双系统终端

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6971101B1 (en) * 2000-09-12 2005-11-29 Motorola, Inc. Managing asynchronous requests for user interface resources in an information system
GB0404696D0 (en) * 2004-03-02 2004-04-07 Level 5 Networks Ltd Dual driver interface
US7650471B2 (en) * 2006-01-06 2010-01-19 Hewlett-Packard Development Company, L.P. Head of queue cache for communication interfaces
US20080244122A1 (en) * 2007-03-27 2008-10-02 Rothman Michael A Providing keyboard, video, mouse switching via software
CN101853079B (zh) * 2009-03-31 2012-09-05 联想(北京)有限公司 一种多硬件系统数据处理设备及其信息输入方法
TW201042466A (en) * 2009-05-28 2010-12-01 Inst Information Industry Hybrid computer systems
WO2011039887A1 (ja) * 2009-10-01 2011-04-07 三菱電機株式会社 計算機装置
US8739177B2 (en) * 2010-06-21 2014-05-27 Intel Corporation Method for network interface sharing among multiple virtual machines
US8825927B2 (en) * 2012-09-04 2014-09-02 Advanced Micro Devices, Inc. Systems and methods for managing queues
US9258324B2 (en) * 2013-11-26 2016-02-09 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for protecting a communication network against internet enabled cyber attacks through use of screen replication from controlled internet access points
US20150269700A1 (en) * 2014-03-24 2015-09-24 Athoc, Inc. Exchange of crisis-related information amongst multiple individuals and multiple organizations

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101383626A (zh) * 2007-09-05 2009-03-11 宏达国际电子股份有限公司 移动装置及其操作系统间共用无线通讯模块的方法
CN101989942A (zh) * 2009-08-07 2011-03-23 无锡江南计算技术研究所 仲裁控制方法、通信方法、仲裁器和通信系统
CN103377093A (zh) * 2012-04-24 2013-10-30 联想(北京)有限公司 一种多系统设备的多媒体同步方法、电子设备
CN103391374A (zh) * 2013-08-08 2013-11-13 北京邮电大学 一种支持无缝切换的双系统终端

Also Published As

Publication number Publication date
CN104298546A (zh) 2015-01-21
US20170161115A1 (en) 2017-06-08
EP3196762A1 (en) 2017-07-26

Similar Documents

Publication Publication Date Title
WO2016029545A1 (zh) 一种硬件通信装置的共享方法及终端
US20220303276A1 (en) Network connection method, hotspot terminal and management terminal
US11729594B2 (en) Network access method, device, and system
US11349767B2 (en) Device and method for disabling a WLAN hotspot based on data traffic value
US10925112B2 (en) Method for applying for media transmission permission, and method and apparatus for canceling media transmission permission
US20180014189A1 (en) Voice control and telecommunications service integration
US10412227B2 (en) Voice communication processing method and system, electronic device, and storage medium
WO2016062002A1 (zh) 连接管理方法及装置、电子设备
US20160127369A1 (en) Method, device and system for user authentication
US20150235164A1 (en) Role-Based Control of Incident Response in a Secure Collaborative Environment
EP3113419B1 (en) Network accessing method and router
JP2014160942A5 (zh)
WO2015196973A1 (en) Security verification method and apparatus
US10798570B2 (en) Terminal authentication method and device
EP3557448A1 (en) Voucher information input method and apparatus, and server and storage medium
US10412585B2 (en) User identity authentication method and device
US20220038463A1 (en) Method and system of multi-channel user authorization
EP3082317A1 (en) Method of automatically setting protocol in programmable logic controller system
WO2016115833A1 (zh) 数据处理装置和数据处理方法
US10448248B2 (en) Methods and devices for controlling authorization to communication information
CN106851639B (zh) 接入WiFi的方法和接入点
JP6098283B2 (ja) 通信速度制限プログラム、通信速度制限装置、及び通信速度制限方法
WO2021072866A1 (zh) 信息验证方法、装置、计算机设备及存储介质
WO2016109996A1 (zh) 一种处理业务的方法、装置及终端
EP2251808A2 (en) Wireless communication system

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

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2014900615

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014900615

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE