WO2016169206A1 - 事件处理方法、装置及系统 - Google Patents

事件处理方法、装置及系统 Download PDF

Info

Publication number
WO2016169206A1
WO2016169206A1 PCT/CN2015/090564 CN2015090564W WO2016169206A1 WO 2016169206 A1 WO2016169206 A1 WO 2016169206A1 CN 2015090564 W CN2015090564 W CN 2015090564W WO 2016169206 A1 WO2016169206 A1 WO 2016169206A1
Authority
WO
WIPO (PCT)
Prior art keywords
priority process
event
preset type
low
low priority
Prior art date
Application number
PCT/CN2015/090564
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 中兴通讯股份有限公司
Publication of WO2016169206A1 publication Critical patent/WO2016169206A1/zh

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/30—Arrangements for executing machine instructions, e.g. instruction decode
    • G06F9/38—Concurrent instruction execution, e.g. pipeline or look ahead

Definitions

  • the present invention relates to the field of communications, and in particular to an event processing method, apparatus, and system.
  • queues are generally used to process events of different priorities at the process level.
  • the inventor of the present invention found in the research process that although the queue mode can be used to prioritize the higher priority events in the current process at the process level, at the system level, if the process is performing queue priority scheduling, The process has a higher priority, so even low-priority events in the process are processed due to all events in the low-priority process. That is, a high-priority process may occupy a large amount of system resources for a long time, so that a process with a lower priority (that is, a process that the system does not preferentially invoke) has no system resources available, thereby causing a high-speed processing in a low-priority process. Priority events are not processed. This is especially true when the system load is already high.
  • the present invention provides an event processing method, apparatus and system.
  • an event processing method including: a high priority process sends a preset type event in a received event to a low priority process, where the high priority process is Preferentially, the process in which the low priority process is invoked by the system, the low priority process is configured to temporarily store the preset type event and send the preset type event under scheduling of the system;
  • the level process receives the preset type event sent by the low priority process; the high priority process processes the preset type event sent by the low priority process.
  • the sending, by the high priority process, the preset type event in the received event to the low priority process includes: the high priority process detecting the received event type of the event; the high priority The level process sends a preset type event in the event to the low priority process, wherein the preset type event includes: an event having a preset priority, and/or an event to be processed in a time-sharing manner.
  • the method further includes: the high priority process determining whether the preset type event is And being sent by the low-priority process; wherein the receiving, by the high-priority process, the preset type event sent by the low-priority process further includes: the high-priority process is determining whether the result is negative And sending the preset type event to the low priority process; and/or, the high priority process processing the preset type event sent by the low priority process further includes: the high The priority process processes the preset type event if the determination result is YES.
  • an event processing method including: a low priority process receives a preset type event sent by a high priority process, wherein the high priority process is prioritized by the a process in which the low priority process is called by the system; the low priority process temporarily stores the preset type event; the low priority process sends the temporarily stored event of the preset type under the scheduling of the system Giving the high priority process to trigger the high priority process to process the preset type event.
  • the preset type event includes: an event with a preset priority, and/or an event that needs to be processed in a time-sharing manner.
  • an event processing apparatus for applying to a high priority process, comprising: a high priority process sending module, configured to send a preset type event in the received event to a low priority process, wherein the high priority process is a process that is invoked by the system in preference to the low priority process, the low priority process being set to temporarily store the preset type event and in the system And sending, by the scheduling, the preset type event; the high priority process receiving module is configured to receive the preset type event sent by the low priority process; and the high priority process processing module is configured to process the low priority The preset type event sent by the process.
  • the high priority process sending module includes: a high priority process detecting unit, configured to detect an event type of the received event; and a high priority process sending unit, configured to preset the event The type event is sent to the low priority process, wherein the preset type event includes: an event having a preset priority, and/or an event to be processed in a time-sharing manner.
  • the device further includes: a high priority process judging module, configured to determine whether the preset type event is sent by the low priority process; wherein the high priority process sending module is further Set to send the preset type event to the low priority process if the determination result is no; and/or, the high priority process processing module is further set to be in the case that the determination result is yes Next, the preset type event is processed.
  • a high priority process judging module configured to determine whether the preset type event is sent by the low priority process
  • the high priority process sending module is further Set to send the preset type event to the low priority process if the determination result is no
  • the high priority process processing module is further set to be in the case that the determination result is yes Next, the preset type event is processed.
  • an event processing apparatus is further provided, which is applied to a low priority process, including: a low priority process receiving module, configured to receive a preset type event sent by a high priority process, where The high priority process is a process that is invoked by the system in preference to the low priority process; the low priority process temporary storage module is set to temporarily store the preset type event; the low priority process sending module is set to And sending, by the scheduling of the system, the temporarily stored event of the preset type to the high priority process, to trigger the high priority process to process the preset type event.
  • the preset type event includes: an event with a preset priority, and/or an event that needs to be processed in a time-sharing manner.
  • an event processing system including: a high priority process and a low priority process, wherein the high priority process is prioritized by the low priority process by the system
  • the invoked process and the high priority process includes: a high priority process sending module, configured to send a preset type event in the received event to the low priority process; a high priority process receiving module, setting Receiving the preset type event sent by the low priority process; the high priority process processing module is configured to process the preset type event sent by the low priority process; the low priority process includes a low-priority process receiving module, configured to receive a preset type event sent by the high-priority process; a low-priority process temporary storage module, configured to temporarily store the preset type event; and a low-priority process sending module, Arranging to send the temporarily stored event of the preset type to the high priority under scheduling of the system a level process to trigger the high priority process to process the preset type event.
  • a high-priority process is used to send a preset type event in the received event to a low-priority process, where the high-priority process is a process that is called by the system in preference to the low-priority process, and the low priority
  • the level process is set to temporarily store the preset type event and send a preset type event under the scheduling of the system; the high priority process receives the preset type event sent by the low priority process; the high priority process processes the sent by the low priority process
  • the method of presetting the type of event solves the problem that the related technology cannot implement the system level event priority processing, and realizes the priority processing of the system level event.
  • FIG. 1 is a flowchart 1 of an event processing method according to an embodiment of the present invention.
  • FIG. 2 is a second flowchart of an event processing method according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram 1 of an event processing apparatus according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram 1 of an optional structure of an event processing apparatus according to an alternative embodiment of the present invention.
  • FIG. 5 is a second schematic diagram of an optional structure of an event processing apparatus according to an alternative embodiment of the present invention.
  • FIG. 6 is a second schematic structural diagram of an event processing apparatus according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of an event processing system according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of intelligently processing a low priority event device interacting with other processes in accordance with an alternative embodiment of the present invention.
  • FIG. 9 is a flow diagram of an interception process for a low priority event in accordance with an alternate embodiment of the present invention.
  • FIG. 10 is a flow diagram of the operation of a low priority event intelligence processing module in accordance with an alternate embodiment of the present invention.
  • FIG. 1 is a flowchart 1 of an event processing method according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:
  • Step S102 The high priority process sends a preset type event in the received event to the low priority process, where the high priority process is a process that is called by the system in preference to the low priority process, and the low priority process is set to Temporarily storing preset type events and sending preset type events under system scheduling;
  • Step S104 The high priority process receives the preset type event sent by the low priority process.
  • Step S106 The high priority process processes the preset type event sent by the low priority process.
  • the preset type event in the high priority process can be temporarily stored in the low priority process, and the temporarily stored event is resent to the high priority process when the low priority process is scheduled, thereby making the high
  • the events in the priority process are processed after some high priority events of other low priority processes, and the processing of high priority events in the low priority processes can be implemented. It can be seen that through the above steps, the problem that the related technology cannot achieve the system level event priority processing is solved, and the priority processing of the system level event is realized.
  • the high priority process detects the event type of the received event; the high priority process sends the preset type event in the event to the low priority process, where the preset type event includes: having Pre-prioritized events, and/or events that need to be processed in a time-sharing manner.
  • the preset type event includes: having Pre-prioritized events, and/or events that need to be processed in a time-sharing manner.
  • a preset priority event in a high-priority process or an event suspension process that needs to be processed in a time-sharing manner may be implemented, so that a priority lower than the priority of the high-priority process is higher than a priority of the low-priority process.
  • Events in other priority processes have more opportunities to be allocated to system resources that handle events.
  • the method may further include: the high priority process determining whether the preset type event is sent by the low priority process; wherein the high priority process receives the low priority process
  • the preset type event sent includes: the high priority process sends the preset type event to the low priority process if the judgment result is no; and/or the high priority process processes the low priority process to send the
  • the preset type event further includes: the high priority process processes the preset type event if the judgment result is yes. In this way, the processing of the preset type event temporarily stored in the low priority process is implemented.
  • FIG. 2 is a second flowchart of an event processing method according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
  • Step S202 The low-priority process receives a preset type event sent by the high-priority process, where the high-priority process is a process that is called by the system in preference to the low-priority process;
  • Step S204 the low priority process temporarily stores the preset type event
  • Step S206 The low priority process sends the temporary preset type event to the high priority process under the scheduling of the system, so as to trigger the high priority process to process the preset type event.
  • the temporary storage and trigger processing of the high-priority process is implemented, so that the low-priority event in the high-priority process can be processed later than the high-priority event in the lower-priority process, and the related technology cannot be solved.
  • the problem of system-level event priority processing is realized, and the priority processing of system-level events is realized.
  • the preset type event includes: an event with a preset priority, and/or an event that needs to be processed in a time-sharing manner.
  • an event processing apparatus is further provided, which is applied to a high-priority process, and is used to implement the foregoing embodiment and the optional implementation manner shown in FIG.
  • the modules involved in the device are described.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • the apparatus may include: a high priority process sending module 32, a high priority process receiving module 34, and a high priority process processing module. 36.
  • the high priority process sending module 32 is configured to send a preset type event in the received event to the low priority process, where the high priority process is a process that is called by the system in preference to the low priority process.
  • the low priority process is set to temporarily store the preset type event and send the preset type event under the scheduling of the system;
  • the high priority process receiving module 34 is coupled to the high priority process sending module 32 through the low priority process, and is set to receive The preset type event sent by the low priority process;
  • the high priority process processing module 36 is coupled to the high priority process receiving module 34 and configured to process the preset type event sent by the low priority process.
  • FIG. 4 is a first schematic diagram of an optional structure of an event processing apparatus according to an alternative embodiment of the present invention.
  • the high priority process sending module 32 includes: a high priority process detecting unit 322, configured to Detecting the event type of the received event; the high priority process sending unit 324 is coupled to the high priority process detecting unit 322, and configured to send the preset type event in the event to the low priority process, where the preset type event includes: Events with preset priorities, and/or events that need to be processed in a time-sharing manner.
  • FIG. 5 is a second schematic diagram of an optional structure of an event processing apparatus according to an alternative embodiment of the present invention.
  • the apparatus further includes: a high priority process determining module 38 coupled to a high priority process respectively.
  • the sending module 32 and the high-priority process processing module 36 are configured to determine whether the preset type event is sent by the low-priority process; wherein the high-priority process sending module 32 is further configured to determine that the result is negative. Sending a preset type event to the low priority process; and/or, the high priority process processing module 36 is further configured to process the preset type event if the determination result is yes.
  • an event processing apparatus is further provided, which is applied to the low-priority process, and is used to implement the foregoing embodiment and the optional implementation manners shown in FIG. 2, which have not been described again.
  • the modules involved in the device are described.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • FIG. 6 is a schematic structural diagram of an event processing apparatus according to an embodiment of the present invention.
  • the apparatus may include: a low priority process receiving module 62, a low priority process temporary storage module 64, and a low priority process sending.
  • the module 66 wherein the low priority process receiving module 62 is configured to receive a preset type event sent by the high priority process, wherein the high priority process is a process that is invoked by the system in preference to the low priority process; the low priority process
  • the temporary storage module 64 is coupled to the low priority process receiving module 62 and configured to temporarily store the preset type event; the low priority process sending module 66 is coupled to the low priority
  • the level process temporary storage module 64 is configured to send the temporary preset type event to the high priority process under the scheduling of the system to trigger the high priority process to process the preset type event.
  • the preset type event includes: an event having a preset priority, and/or an event to be processed in a time-sharing manner.
  • the embodiment of the invention further provides an event processing system, which comprises the above-mentioned event processing device applied to a high priority process and an event processing device applied to a low priority process.
  • FIG. 7 is a schematic structural diagram of an event processing system according to an embodiment of the present invention. As shown in FIG. 7, the system includes: a high priority process 72 and a low priority process 74, wherein the high priority process 72 takes precedence over the low priority. The process that the level process 74 is called by the system, and
  • the high priority process 72 includes a high priority process sending module 32 configured to send a preset type event in the received event to the low priority process; the high priority process receiving module 34 is configured to receive the low priority process a preset type event sent; the high priority process processing module 36 is configured to process a preset type event sent by the low priority process;
  • the low priority process 74 includes: a low priority process receiving module 62 configured to receive a preset type event sent by the high priority process; a low priority process temporary storage module 64 configured to temporarily store the preset type event; The process sending module 66 is configured to send the temporary preset type event to the high priority process under the scheduling of the system to trigger the high priority process to process the preset type event.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • An optional embodiment of the present invention provides a method for intelligently processing low priority events, which aims to ensure that low priority events do not affect the system's high reliability, high real-time tasks while ensuring low Priority events can be processed as quickly as possible.
  • An intelligent processing low priority event device (corresponding to the above event processing device applied to a low priority process) provided by an optional embodiment of the present invention includes the following modules:
  • the low priority operation temporary storage module (corresponding to the low priority process temporary storage module 64 described above) is configured to temporarily store the low priority operations (corresponding to the low priority events described above) sent by the respective processes.
  • a low-priority operation triggering module (corresponding to the low-priority process sending module 66 described above): a triggering module set to a low-priority operation, for example, after the event with high real-time requirements of the current process in the system is processed, The previously stored low priority operations are sent to the corresponding processes.
  • FIG. 8 is a schematic diagram of intelligently processing a low priority event device interacting with other processes according to an alternative embodiment of the present invention.
  • each of the processes receives real time using the above device.
  • the interface provided by the low priority temporary storage module is called, and the message (which can carry the identifier of the event that needs intelligent processing) is sent to the low priority temporary storage module, and the low priority temporary storage module temporarily stores all These messages; low priority operation touch
  • the sending module sends the previously stored low-priority events to the corresponding processes.
  • step 1 the service module (ie, the high priority process described above) invokes an interface provided by the low priority operation temporary storage module, and the registration needs to process the low priority event.
  • Step 2 When the process receives the low priority event, the module of the low priority event intercepts the message and sends the message to the low priority operation processing module in the system, and the low priority operation module may have the lowest priority in the system. Process.
  • Step 3 When the lowest priority process can be scheduled, it indicates that all other high priority process events in the system have been processed, and the low priority trigger module will all the previously stored low priority. Events are sent one by one to the corresponding process, and only one can be sent at a time.
  • FIG. 9 is a flowchart of a process of intercepting a low priority event according to an alternative embodiment of the present invention.
  • an application abbreviated as APP
  • APP Application, abbreviated as APP
  • judging Whether the event received by the current APP process is a low priority event if yes and not sent by the low priority event processing module, the current event is sent to the low priority event processing module; if not, the APP process continues deal with.
  • FIG. 10 is a flowchart of a low priority event intelligent processing module according to an alternative embodiment of the present invention.
  • the low priority event intelligent processing module after receiving a low priority event, temporarily stores the identifier of the event. (id), temporarily store the process id, and when it is called by the system, take out the earliest low priority event in the current system and send it to the corresponding process.
  • the event with low real-time requirements can be postponed, and all events with high real-time requirements can be processed before the event with low real-time requirements can be processed.
  • the temporary storage processing of the preset priority event is taken as an example for description.
  • an event that needs to be processed in a time-sharing manner can be sent to a low-priority process for temporary storage, and when the system calls a low-priority process, a high-priority process is required to be executed.
  • the present invention can ensure that the event with high real-time requirements is always processed before the event with low real-time requirements, and that the low-priority event can get the maximum possible time. Processing, which can improve the system's fault tolerance, reliability and availability.
  • a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • the present invention can temporarily store a preset type event in a high priority process in a low priority process, and resend the temporarily stored event to a high priority when the low priority process is scheduled.
  • Process processing so that events in high-priority processes can be processed after some high-priority events of other low-priority processes, Implement processing of high priority events in low priority processes. It can be seen that through the above steps, the problem that the related technology cannot achieve the system level event priority processing is solved, and the priority processing of the system level event is realized.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种事件处理方法、装置及系统，其中，该方法包括：高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程，其中，高优先级进程为优先于低优先级进程被系统调用的进程，低优先级进程设置为暂存预设类型事件和在系统的调度下发送预设类型事件（S102）；高优先级进程接收低优先级进程发送的预设类型事件（S104）；高优先级进程处理低优先级进程所发送的预设类型事件（S106）。通过该方法，解决了相关技术无法实现系统级别事件优先级处理的问题，实现了系统级别事件的优先级处理。

Description

事件处理方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种事件处理方法、装置及系统。
背景技术
在系统中存在部分外部事件需要优先的及时的处理，而部分事件对于实时性的要求并不高的情况。在相关技术中在进程级别一般会采用队列方式对不同优先级的事件进行处理。
然而本发明的发明人在研究过程中发现，虽然在进程级别可以采用队列方式使得当前进程中优先级较高的事件优先处理；但是在系统级别而言，进程在进行队列优先级调度时，如果该进程优先级较高，那么即使是该进程中的低优先级事件也会由于低优先级进程中的所有事件而被处理。也即高优先级的进程可能长期占用大量的系统资源，从而使得优先级较低的进程(即系统不会优先调用的进程)没有系统资源可用，进而导致低优先级进程中需要实时处理的高优先级事件得不到处理。在系统负荷已经很高的情况下，此种情况尤为严重。
针对相关技术无法实现系统级别事件优先级处理的问题，目前没有提出有效的解决方案。
发明内容
为了解决上述技术问题，本发明提供了一种事件处理方法、装置及系统。
根据本发明实施例的一个方面，提供了一种事件处理方法，包括：高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程，所述低优先级进程设置为暂存所述预设类型事件和在所述系统的调度下发送所述预设类型事件；所述高优先级进程接收所述低优先级进程发送的所述预设类型事件；所述高优先级进程处理所述低优先级进程所发送的所述预设类型事件。
可选地，所述高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程包括：所述高优先级进程检测接收到的所述事件的事件类型；所述高优先级进程将所述事件中预设类型事件发送至所述低优先级进程，其中，所述预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
可选地，在所述高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程之前，所述方法还包括：所述高优先级进程判断所述预设类型事件是否是由所述低优先级进程发送的；其中，所述高优先级进程接收所述低优先级进程发送的所述预设类型事件还包括：所述高优先级进程在判断结果为否的情况下，将所述预设类型事件发送至所述低优先级进程；和/或，所述高优先级进程处理所述低优先级进程所发送的所述预设类型事件还包括：所述高优先级进程在判断结果为是的情况下，处理所述预设类型事件。
根据本发明实施例的另一个方面，还提供了一种事件处理方法，包括：低优先级进程接收高优先级进程发送的预设类型事件，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程；所述低优先级进程暂存所述预设类型事件；所述低优先级进程在所述系统的调度下，将暂存的所述预设类型事件发送给所述高优先级进程，以触发所述高优先级进程处理所述预设类型事件。
可选地，所述预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
根据本发明实施例的另一个方面，还提供了一种事件处理装置，应用于高优先级进程，包括：高优先级进程发送模块，设置为将接收到的事件中的预设类型事件发送至低优先级进程，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程，所述低优先级进程设置为暂存所述预设类型事件和在所述系统的调度下发送所述预设类型事件；高优先级进程接收模块，设置为接收所述低优先级进程发送的所述预设类型事件；高优先级进程处理模块，设置为处理所述低优先级进程所发送的所述预设类型事件。
可选地，所述高优先级进程发送模块包括：高优先级进程检测单元，设置为检测接收到的所述事件的事件类型；高优先级进程发送单元，设置为将所述事件中预设类型事件发送至所述低优先级进程，其中，所述预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
可选地，所述装置还包括：高优先级进程判断模块，设置为判断所述预设类型事件是否是由所述低优先级进程发送的；其中，所述高优先级进程发送模块，还设置为在判断结果为否的情况下，将所述预设类型事件发送至所述低优先级进程；和/或，所述高优先级进程处理模块，还设置为在判断结果为是的情况下，处理所述预设类型事件。
根据本发明实施例的另一个方面，还提供了一种事件处理装置，应用于低优先级进程，包括：低优先级进程接收模块，设置为接收高优先级进程发送的预设类型事件，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程；低优先级进程暂存模块，设置为暂存所述预设类型事件；低优先级进程发送模块，设置为在所述系统的调度下，将暂存的所述预设类型事件发送给所述高优先级进程，以触发所述高优先级进程处理所述预设类型事件。
可选地，所述预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
根据本发明实施例的另一个方面，还提供了一种事件处理系统，包括：高优先级进程和低优先级进程，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程，以及所述高优先级进程包括：高优先级进程发送模块，设置为将接收到的事件中的预设类型事件发送至所述低优先级进程；高优先级进程接收模块，设置为接收所述低优先级进程发送的所述预设类型事件；高优先级进程处理模块，设置为处理所述低优先级进程所发送的所述预设类型事件；所述低优先级进程包括：低优先级进程接收模块，设置为接收所述高优先级进程发送的预设类型事件；低优先级进程暂存模块，设置为暂存所述预设类型事件；低优先级进程发送模块，设置为在所述系统的调度下，将暂存的所述预设类型事件发送给所述高优先 级进程，以触发所述高优先级进程处理所述预设类型事件。
通过本发明实施例，采用高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程，其中，高优先级进程为优先于低优先级进程被系统调用的进程，低优先级进程设置为暂存预设类型事件和在系统的调度下发送预设类型事件；高优先级进程接收低优先级进程发送的预设类型事件；高优先级进程处理低优先级进程所发送的预设类型事件的方式，解决了相关技术无法实现系统级别事件优先级处理的问题，实现了系统级别事件的优先级处理。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的事件处理方法的流程图一；
图2是根据本发明实施例的事件处理方法的流程图二；
图3是根据本发明实施例的事件处理装置的结构示意图一；
图4是根据本发明可选实施例的事件处理装置的可选结构示意图一；
图5是根据本发明可选实施例的事件处理装置的可选结构示意图二；
图6是根据本发明实施例的事件处理装置的结构示意图二；
图7是根据本发明实施例的事件处理系统的结构示意图；
图8是根据本发明可选实施例的智能处理低优先级事件装置与其他进程交互的示意图；
图9是根据本发明可选实施例的低优先级事件的截取过程的流程图；
图10是根据本发明可选实施例的低优先级事件智能处理模块的工作流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本发明的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本发明而了解。本发明的目的和其他优点可通过在所写的说明书、权利要求书、以及附图中所特别指出的结构来实现和获得。
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
本发明实施例提供了一种事件处理方法，图1是根据本发明实施例的事件处理方法的流程图一，如图1所示，该流程包括如下步骤：
步骤S102，高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程，其中，高优先级进程为优先于低优先级进程被系统调用的进程，低优先级进程设置为暂存预设类型事件和在系统的调度下发送预设类型事件；
步骤S104，高优先级进程接收低优先级进程发送的预设类型事件；
步骤S106，高优先级进程处理低优先级进程所发送的预设类型事件。
通过上述步骤，可以将高优先级进程中预设类型事件暂存在低优先级进程中，并在低优先级进程被调度时将暂存的事件重新发送给高优先级进程处理，从而可以使得高优先级进程中的事件在其他低优先级进程的某些高优先级事件之后处理，可以实现低优先级进程中的高优先级事件的处理。可见，通过上述步骤，解决了相关技术无法实现系统级别事件优先级处理的问题，实现了系统级别事件的优先级处理。
可选地，在上述步骤S102中，高优先级进程检测接收到的事件的事件类型；高优先级进程将事件中预设类型事件发送至低优先级进程，其中，预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。通过上述方式可以实现高优先级进程中的预设优先级事件或者需分时处理的事件暂缓处理，从而给低于该高优先级进程的优先级而高于该低优先级进程的优先级的其他优先级进程中的事件能够有更多机会分到处理事件的系统资源。
可选地，为了避免形成闭环，在步骤S102之前，该方法还可以包括：高优先级进程判断预设类型事件是否是由低优先级进程发送的；其中，高优先级进程接收低优先级进程发送的预设类型事件还包括：高优先级进程在判断结果为否的情况下，将预设类型事件发送至低优先级进程；和/或，高优先级进程处理低优先级进程所发送的预设类型事件还包括：高优先级进程在判断结果为是的情况下，处理预设类型事件。通过该方式，实现了暂存在低优先级进程中的预设类型事件的处理。
本发明实施例还提供了一种事件处理方法，图2是根据本发明实施例的事件处理方法的流程图二，如图2所示，该流程包括如下步骤：
步骤S202，低优先级进程接收高优先级进程发送的预设类型事件，其中，高优先级进程为优先于低优先级进程被系统调用的进程；
步骤S204，低优先级进程暂存预设类型事件；
步骤S206，低优先级进程在系统的调度下，将暂存的预设类型事件发送给高优先级进程，以触发高优先级进程处理预设类型事件。
通过上述步骤，实现了高优先级进程的暂存和触发处理，从而使得高优先级进程中的低优先级事件可以晚于较低优先级进程中的高优先级事件处理，解决了相关技术无法实现系统级别事件优先级处理的问题，实现了系统级别事件的优先级处理。
可选地，上述预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
在本实施例中还提供了一种事件处理装置，应用于高优先级进程，用于实现上述图1所示的实施例及可选实施方式，已经进行过说明的不再赘述，下面对该装置中涉及到的模块进行说明。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的事件处理装置的结构示意图一，如图3所示，该装置可以包括：高优先级进程发送模块32、高优先级进程接收模块34和高优先级进程处理模块36，其中，高优先级进程发送模块32，设置为将接收到的事件中的预设类型事件发送至低优先级进程，其中，高优先级进程为优先于低优先级进程被系统调用的进程，低优先级进程设置为暂存预设类型事件和在系统的调度下发送预设类型事件；高优先级进程接收模块34，通过低优先级进程耦合至高优先级进程发送模块32，设置为接收低优先级进程发送的预设类型事件；高优先级进程处理模块36，耦合至高优先级进程接收模块34，设置为处理低优先级进程所发送的预设类型事件。
图4是根据本发明可选实施例的事件处理装置的可选结构示意图一，如图4所示，可选地，高优先级进程发送模块32包括：高优先级进程检测单元322，设置为检测接收到的事件的事件类型；高优先级进程发送单元324，耦合至高优先级进程检测单元322，设置为将事件中预设类型事件发送至低优先级进程，其中，预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
图5是根据本发明可选实施例的事件处理装置的可选结构示意图二，如图5所示，可选地，上述装置还包括：高优先级进程判断模块38，分别耦合至高优先级进程发送模块32和高优先级进程处理模块36，设置为判断预设类型事件是否是由低优先级进程发送的；其中，高优先级进程发送模块32，还设置为在判断结果为否的情况下，将预设类型事件发送至低优先级进程；和/或，高优先级进程处理模块36，还设置为在判断结果为是的情况下，处理预设类型事件。
在本实施例中还提供了一种事件处理装置，应用于低优先级进程，用于实现上述图2所示的实施例及可选实施方式，已经进行过说明的不再赘述，下面对该装置中涉及到的模块进行说明。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本发明实施例的事件处理装置的结构示意图二，如图6所示，该装置可以包括：低优先级进程接收模块62、低优先级进程暂存模块64和低优先级进程发送模块66，其中，低优先级进程接收模块62，设置为接收高优先级进程发送的预设类型事件，其中，高优先级进程为优先于低优先级进程被系统调用的进程；低优先级进程暂存模块64，耦合至低优先级进程接收模块62，设置为暂存预设类型事件；低优先级进程发送模块66，耦合至低优先 级进程暂存模块64，设置为在系统的调度下，将暂存的预设类型事件发送给高优先级进程，以触发高优先级进程处理预设类型事件。
可选地，上述的预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
本发明实施例还提供了一种事件处理系统，该系统包括上述的应用于高优先级进程的事件处理装置和应用于低优先级进程的事件处理装置。
图7是根据本发明实施例的事件处理系统的结构示意图，如图7所示，该系统包括：高优先级进程72和低优先级进程74，其中，高优先级进程72为优先于低优先级进程74被系统调用的进程，以及
高优先级进程72包括：高优先级进程发送模块32，设置为将接收到的事件中的预设类型事件发送至低优先级进程；高优先级进程接收模块34，设置为接收低优先级进程发送的预设类型事件；高优先级进程处理模块36，设置为处理低优先级进程所发送的预设类型事件；
低优先级进程74包括：低优先级进程接收模块62，设置为接收高优先级进程发送的预设类型事件；低优先级进程暂存模块64，设置为暂存预设类型事件；低优先级进程发送模块66，设置为在系统的调度下，将暂存的预设类型事件发送给高优先级进程，以触发高优先级进程处理预设类型事件。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
为了使本发明实施例的描述更加清楚，下面结合可选实施例进行描述和说明。
本发明可选实施例提供了一种智能处理低优先级事件的方法，其目的在于在系统中能够确保低优先级的事件不会影响系统的高可靠性，高实时性的任务，同时保证低优先级的事件能够尽快的处理。
本发明可选实施例提供的一种智能处理低优先级事件装置(相当于上述事件处理装置，应用于低优先级进程)包括以下模块：
低优先级操作暂存模块(相当于上述的低优先级进程暂存模块64)：设置为暂存各个进程发送过来的低优先级操作(相当于上述的低优先级事件)。
低优先级操作触发模块(相当于上述的低优先级进程发送模块66)：设置为低优先级操作的触发模块，例如，在系统中当前进程的实时性要求高的事件都处理完成后，将之前暂存的低优先级操作发送给对应的各个进程。
图8是根据本发明可选实施例的智能处理低优先级事件装置与其他进程交互的示意图，如图8所示，采用上述装置，各个进程(相当于上述高优先级进程)在收到了实时性要求不高的事件时，调用低优先级暂存模块提供的接口，发送消息(可以携带有需要智能处理的事件的标识)给低优先级暂存模块，低优先级暂存模块暂存所有的这些消息；低优先级操作触 发模块在感知到系统中所有实时性要求高的事件都已经处理完成后，将之前暂存的低优先级事件发送给对应的各个进程。
本发明可选实施例提供的智能处理低优先级事件的方法包括如下步骤：
步骤一，业务模块(即上述高优先级进程)调用低优先级操作暂存模块提供的接口，注册需要处理低优先级事件。
步骤二，在进程收到低优先级事件时，低优先级事件的模块截取此消息，并将此消息发送给系统中低优先级操作处理模块，低优先级操作模块可以是系统中优先级最低的进程。
步骤三，在低优先级最低的进程都能得到调度时，说明系统中的所有其他的高优先级进程的事件都已经处理完毕，则低优先级触发模块，将所有之前暂存的低优先级事件一个一个的发送给对应的进程，一次可以只发送一个。
图9是根据本发明可选实施例的低优先级事件的截取过程的流程图，如图9所示，在应用程序(Application，简称为APP)进程(即上述高优先级进程)中，判断当前APP进程收到的事件是否是低优先级事件，如果是且不是由低优先级事件处理模块发送过来的，则将当前事件发送给低优先级事件处理模块；如果不是，则由APP进程继续处理。
图10是根据本发明可选实施例的低优先级事件智能处理模块的工作流程图，如图10所示，低优先级事件智能处理模块接收到低优先级事件后，暂存此事件的标识(id)，暂存进程id，并可以在被系统调用时，取出当前系统中的最早的低优先级事件，发送给对应的进程。
采用上述方案，可以将当前实时性要求并不高的事件延后处理，当所有的实时性要求高的事件处理完成后，才可以处理实时性要求不高的事件。
在本发明上述可选实施例中，以预设优先级事件的暂存处理为例进行说明。然而，类似地，在针对需分时处理的事件时，可以将需分时处理的事件发送给低优先级进程暂存，并在系统调用低优先级进程时，触发高优先级进程执行需分时处理的事件中的一个分时任务；直至将该需分时处理的事件处理完毕。
综上所述，本发明通过上述实施例和实施方式，可以确保进程在实时性要求高的事件始终在实时性要求不高的事件前得到处理，并保证低优先级事件能够得到最大可能的及时的处理，从而可以提高系统的容错性，可靠性和可用性。
在另外一个实施例中，还提供了一种软件，该软件用于执行上述实施例及可选实施方式中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
工业实用性：通过上述描述可知，本发明可以将高优先级进程中预设类型事件暂存在低优先级进程中，并在低优先级进程被调度时将暂存的事件重新发送给高优先级进程处理，从而可以使得高优先级进程中的事件在其他低优先级进程的某些高优先级事件之后处理，可以 实现低优先级进程中的高优先级事件的处理。可见，通过上述步骤，解决了相关技术无法实现系统级别事件优先级处理的问题，实现了系统级别事件的优先级处理。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的对象在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的可选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (11)

  1. 一种事件处理方法，包括：
    高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程，所述低优先级进程设置为暂存所述预设类型事件和在所述系统的调度下发送所述预设类型事件；
    所述高优先级进程接收所述低优先级进程发送的所述预设类型事件；
    所述高优先级进程处理所述低优先级进程所发送的所述预设类型事件。
  2. 根据权利要求1所述的方法，其中，所述高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程包括：
    所述高优先级进程检测接收到的所述事件的事件类型；
    所述高优先级进程将所述事件中预设类型事件发送至所述低优先级进程，其中，所述预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
  3. 根据权利要求1所述的方法，其中，在所述高优先级进程将接收到的事件中的预设类型事件发送至低优先级进程之前，所述方法还包括：
    所述高优先级进程判断所述预设类型事件是否是由所述低优先级进程发送的；
    其中，所述高优先级进程接收所述低优先级进程发送的所述预设类型事件还包括：所述高优先级进程在判断结果为否的情况下，将所述预设类型事件发送至所述低优先级进程；和/或，
    所述高优先级进程处理所述低优先级进程所发送的所述预设类型事件还包括：所述高优先级进程在判断结果为是的情况下，处理所述预设类型事件。
  4. 一种事件处理方法，包括：
    低优先级进程接收高优先级进程发送的预设类型事件，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程；
    所述低优先级进程暂存所述预设类型事件；
    所述低优先级进程在所述系统的调度下，将暂存的所述预设类型事件发送给所述高优先级进程，以触发所述高优先级进程处理所述预设类型事件。
  5. 根据权利要求4所述的方法，其中，所述预设类型事件包括：
    具有预设优先级的事件，和/或，需分时处理的事件。
  6. 一种事件处理装置，应用于高优先级进程，包括：
    高优先级进程发送模块，设置为将接收到的事件中的预设类型事件发送至低优先级 进程，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程，所述低优先级进程设置为暂存所述预设类型事件和在所述系统的调度下发送所述预设类型事件；
    高优先级进程接收模块，设置为接收所述低优先级进程发送的所述预设类型事件；
    高优先级进程处理模块，设置为处理所述低优先级进程所发送的所述预设类型事件。
  7. 根据权利要求6所述的装置，其中，所述高优先级进程发送模块包括：
    高优先级进程检测单元，设置为检测接收到的所述事件的事件类型；
    高优先级进程发送单元，设置为将所述事件中预设类型事件发送至所述低优先级进程，其中，所述预设类型事件包括：具有预设优先级的事件，和/或，需分时处理的事件。
  8. 根据权利要求6所述的装置，其中，所述装置还包括：
    高优先级进程判断模块，设置为判断所述预设类型事件是否是由所述低优先级进程发送的；
    其中，所述高优先级进程发送模块，还设置为在判断结果为否的情况下，将所述预设类型事件发送至所述低优先级进程；和/或，
    所述高优先级进程处理模块，还设置为在判断结果为是的情况下，处理所述预设类型事件。
  9. 一种事件处理装置，应用于低优先级进程，包括：
    低优先级进程接收模块，设置为接收高优先级进程发送的预设类型事件，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程；
    低优先级进程暂存模块，设置为暂存所述预设类型事件；
    低优先级进程发送模块，设置为在所述系统的调度下，将暂存的所述预设类型事件发送给所述高优先级进程，以触发所述高优先级进程处理所述预设类型事件。
  10. 根据权利要求9所述的装置，其中，所述预设类型事件包括：
    具有预设优先级的事件，和/或，需分时处理的事件。
  11. 一种事件处理系统，包括：高优先级进程和低优先级进程，其中，所述高优先级进程为优先于所述低优先级进程被系统调用的进程，以及
    所述高优先级进程包括：高优先级进程发送模块，设置为将接收到的事件中的预设类型事件发送至所述低优先级进程；高优先级进程接收模块，设置为接收所述低优先级进程发送的所述预设类型事件；高优先级进程处理模块，设置为处理所述低优先级进程所发送的所述预设类型事件；
    所述低优先级进程包括：低优先级进程接收模块，设置为接收所述高优先级进程发 送的预设类型事件；低优先级进程暂存模块，设置为暂存所述预设类型事件；低优先级进程发送模块，设置为在所述系统的调度下，将暂存的所述预设类型事件发送给所述高优先级进程，以触发所述高优先级进程处理所述预设类型事件。
PCT/CN2015/090564 2015-04-23 2015-09-24 事件处理方法、装置及系统 WO2016169206A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510197957.4 2015-04-23
CN201510197957.4A CN106155774A (zh) 2015-04-23 2015-04-23 事件处理方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2016169206A1 true WO2016169206A1 (zh) 2016-10-27

Family

ID=57143758

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/090564 WO2016169206A1 (zh) 2015-04-23 2015-09-24 事件处理方法、装置及系统

Country Status (2)

Country Link
CN (1) CN106155774A (zh)
WO (1) WO2016169206A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1952898A (zh) * 2005-03-14 2007-04-25 Qnx软件操作系统公司 采用进程线程的自适应分区的进程调度程序
CN101246437A (zh) * 2008-01-28 2008-08-20 中兴通讯股份有限公司 一种嵌入式实时系统进程均衡调度方法
CN102298539A (zh) * 2011-06-07 2011-12-28 华东师范大学 一种用于分布式并行处理的共享资源调度方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7174552B2 (en) * 2002-01-12 2007-02-06 Intel Corporation Method of accessing a resource by a process based on a semaphore of another process
CN100433011C (zh) * 2006-01-17 2008-11-12 中兴通讯股份有限公司 嵌入式环境下内存数据库的一致性保护方法
CN101334766B (zh) * 2008-06-30 2011-05-11 东软飞利浦医疗设备系统有限责任公司 一种并行微处理器及其实现方法
US8589934B2 (en) * 2011-04-01 2013-11-19 Arm Limited Controlling priority levels of pending threads awaiting processing
US11321118B2 (en) * 2012-10-24 2022-05-03 Messageone, Inc. System and method for controlled sharing of consumable resources in a computer cluster

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1952898A (zh) * 2005-03-14 2007-04-25 Qnx软件操作系统公司 采用进程线程的自适应分区的进程调度程序
CN101246437A (zh) * 2008-01-28 2008-08-20 中兴通讯股份有限公司 一种嵌入式实时系统进程均衡调度方法
CN102298539A (zh) * 2011-06-07 2011-12-28 华东师范大学 一种用于分布式并行处理的共享资源调度方法及系统

Also Published As

Publication number Publication date
CN106155774A (zh) 2016-11-23

Similar Documents

Publication Publication Date Title
US10282229B2 (en) Asynchronous task management in an on-demand network code execution environment
CN108762896B (zh) 一种基于Hadoop集群任务调度方法及计算机设备
US9952896B2 (en) Asynchronous task management in an on-demand network code execution environment
CN104081736B (zh) 客户端设备上调度分组传输的系统和方法
CN107087019B (zh) 一种基于端云协同计算架构的任务调度方法及装置
CN108124003B (zh) 网络管理设备连接处理方法、装置及系统
WO2017028724A1 (zh) 一种业务请求调整方法及设备
EP2701074B1 (en) Method, device, and system for performing scheduling in multi-processor core system
US9270527B2 (en) Methods, systems, and computer readable media for enabling real-time guarantees in publish-subscribe middleware using dynamically reconfigurable networks
US9577961B2 (en) Input/output management in a distributed strict queue
US10200295B1 (en) Client selection in a distributed strict queue
US10091215B1 (en) Client isolation in a distributed queue
US9584593B2 (en) Failure management in a distributed strict queue
US9591101B2 (en) Message batching in a distributed strict queue
US20150381514A1 (en) Multi-tiered processing using a distributed strict queue
EP3475817A1 (en) Asynchronous task management in an on-demand network code execution environment
US9575820B2 (en) Client control in a distributed strict queue
WO2016197301A1 (zh) Nfv系统中的策略协调方法和装置
US20120290707A1 (en) System and method for unified polling of networked devices and services
WO2016149945A1 (zh) 一种生命周期事件的处理方法及vnfm
US20150381413A1 (en) Geographic awareness in a distributed strict queue
CN112968845A (zh) 一种带宽管理方法、装置、设备及机器可读存储介质
WO2016169206A1 (zh) 事件处理方法、装置及系统
CN111427673B (zh) 一种负载均衡方法、装置及设备
CN105721339A (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: 15889692

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15889692

Country of ref document: EP

Kind code of ref document: A1