CN109522110B

CN109522110B - Multitask management system and method based on video networking

Info

Publication number: CN109522110B
Application number: CN201811378335.1A
Authority: CN
Inventors: 陈婷; 亓娜; 史兴宇; 王艳辉
Original assignee: Visionvera Information Technology Co Ltd
Current assignee: Hainan Qiantang Shilian Information Technology Co.,Ltd.
Priority date: 2018-11-19
Filing date: 2018-11-19
Publication date: 2020-03-31
Anticipated expiration: 2038-11-19
Also published as: CN109522110A

Abstract

The embodiment of the application provides a multitask management system and a multitask management method based on a video network, wherein the multitask management system and the multitask management method are applied to the video network, a video network server comprises a thread management module, a task management module and a magnetic disk, and the thread management module is connected with the task management module and is internally provided with a plurality of thread units; the task management module is connected with the thread management module and the disk at the same time, and is internally provided with a task set area, and task units corresponding to the thread units are arranged in the task set area; the disk is connected with the task management module and used for storing the task data written in the task unit by the task set area; the embodiment of the application can carry out unified task management on the task operations of all current users, and the managed tasks can be executed concurrently; and the safety of task data can be guaranteed, and the use experience of a user is improved.

Description

Multitask management system and method based on video networking

Technical Field

The application relates to the technical field of video networking, in particular to a multitask management system and a multitask management method based on the video networking.

Background

The video networking is an important milestone for network development, is a higher-level form of the Internet, is a real-time network, can realize the real-time transmission of full-network high-definition videos which cannot be realized by the existing Internet, and pushes a plurality of Internet applications to high-definition video, and high definition faces each other. Finally, world no-distance is realized, and the distance between people in the world is only the distance of one screen.

The current video network is provided with a video network server which is connected with a plurality of user terminals of the local area network, and a user manages tasks sent by the user terminals.

However, the task management system in the existing video network server has dispersed management on each task, the management interfaces between each task are inconsistent, and the management difficulty is high. And the tasks in the system do not have the power-off protection function, and the persistence of data cannot be realized.

Disclosure of Invention

In view of the above, embodiments of the present application are proposed to provide a system and a corresponding method for managing multiple tasks based on a video network, which overcome or at least partially solve the above problems.

In order to solve the above problem, an embodiment of the present application discloses a multitask management system based on a video network, the system is applied to the video network, the video network includes a video network server, the video network server includes a thread management module, a task management module and a disk, wherein:

the thread management module is connected with the task management module and is internally provided with a plurality of thread units;

the task management module is connected with the thread management module and the disk at the same time, and is internally provided with a task set area, and task units corresponding to the thread units are arranged in the task set area;

and the disk is connected with the task management module and is used for storing the task data written in the task unit by the task set area.

In a preferred embodiment of the present application, the video network further includes a plurality of user terminals, the user terminals are communicatively connected to the thread management module, and the thread management module includes the following sub-modules:

the user task docking sub-module is used for receiving a task operation command sent by the user terminal; the task operation command is generated by the user terminal when the triggering operation of the task is received;

and the thread unit creating submodule is used for creating a thread unit corresponding to the task according to the task operation command.

In a preferred embodiment of the present application, the task management module includes the following sub-modules:

the task receiving submodule is used for receiving the task data sent by the thread management module; the task data is data in a thread unit corresponding to the task, which is called by the thread management module according to the received task operation command;

the task operation submodule is used for calling the task data into the task set area and adding the task data into a task unit corresponding to the thread unit;

and the task writing submodule is used for writing the task data in the task unit into the disk.

In a preferred embodiment of the present application, the task receiving submodule includes an interface for adding, deleting, modifying, and canceling the task.

In a preferred embodiment of the present application, the task unit in the task aggregation area further carries a task type execution identifier, where the task type execution identifier includes:

first type identification: the task data is immediately executed after being added to the task unit;

the second type identification: after the task data is added to the task unit, the task data is executed after delaying preset time;

the third type identification: the task data is added to the task unit and then executed at the appointed date and time;

the fourth type identification: and repeatedly executing the task data at fixed time intervals after the task data is added to the task unit.

In a preferred embodiment of the present application, the task data includes service data corresponding to the task, and data for the task to execute the service.

In a preferred embodiment of the present application, the task unit in the task aggregation area carries a task state identifier, where the task state identifier includes a task waiting identifier and a task executing identifier.

In a preferred embodiment of the present application, the task management module further includes the following sub-modules:

and the task reading submodule is used for reading the task data in the disk after receiving a triggering signal for restarting the system.

In order to solve the above problem, based on the multitask management system of the embodiment of the present application, the embodiment of the present application further discloses a multitask management method based on a video network, where the method is applied to the video network, the video network includes a video network server and a user terminal in communication connection with the video network server, and the method includes:

the video network server receives a task operation command sent by a user terminal; the task operation command is generated by the user terminal when the triggering operation of the task is received;

the video network server creates a thread unit corresponding to the task according to the task operation command;

the video network server calls the task data in the thread unit into the task set area and adds the task data into the task unit corresponding to the thread unit;

and the video network server writes the task data in the task unit into the disk.

In a preferred embodiment of the present application, the task operation command includes:

adding the task command;

and/or, deleting the task command;

and/or, modifying the task command;

and/or, cancel the task command.

The embodiment of the application has the following advantages:

the method comprises the steps that characteristics of the video network are applied, a thread management module and a task management module are arranged in a video network server, the thread management module establishes a thread unit corresponding to a task according to current task operation of a user, and the task management module calls task data in the thread unit into a task set area in the task set area and adds the task data into the task unit corresponding to the thread unit; the task operation of all current users can be uniformly managed by using the mode that the task aggregation area is used for aggregating all current tasks together, and the managed tasks can be executed concurrently;

according to the embodiment of the application, the task data in each thread unit in the thread management module can be transferred into the task collection area through the adding, deleting, modifying and canceling interfaces and added into the task unit corresponding to the thread unit, and the task data is classified and managed by the adding, deleting, modifying and canceling interfaces and the like, so that the method has the advantages of high flexibility, more comprehensive generalization and the like, the management interfaces of the tasks are unified, and the management difficulty is greatly reduced;

according to the embodiment of the application, the disk is added in the video network server, the task management module can call part or all of task data in the task collection area and write the task data into the disk, so that when the system is restarted, the saved task data are still effective, the task safety can be guaranteed, and the user experience is improved.

Drawings

FIG. 1 is a networking schematic of a video network of the present application;

FIG. 2 is a schematic diagram of a hardware architecture of a node server according to the present application;

fig. 3 is a schematic diagram of a hardware architecture of an access switch of the present application;

fig. 4 is a schematic diagram of a hardware structure of an ethernet protocol conversion gateway according to the present application;

FIG. 5 is a block diagram of a multitask management system based on video network according to an embodiment of the present application;

fig. 6 is a flowchart illustrating steps of a method for multitask management based on the internet of view according to an embodiment of the present application.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.

The video networking is an important milestone for network development, is a real-time network, can realize high-definition video real-time transmission, and pushes a plurality of internet applications to high-definition video, and high-definition faces each other.

The video networking adopts a real-time high-definition video exchange technology, can integrate required services such as dozens of services of video, voice, pictures, characters, communication, data and the like on a system platform on a network platform, such as high-definition video conference, video monitoring, intelligent monitoring analysis, emergency command, digital broadcast television, delayed television, network teaching, live broadcast, VOD on demand, television mail, Personal Video Recorder (PVR), intranet (self-office) channels, intelligent video broadcast control, information distribution and the like, and realizes high-definition quality video broadcast through a television or a computer.

To better understand the embodiments of the present application, the following description refers to the internet of view:

some of the technologies applied in the video networking are as follows:

network Technology (Network Technology)

Network technology innovation in video networking has improved over traditional Ethernet (Ethernet) to face the potentially enormous video traffic on the network. Unlike pure network Packet Switching (Packet Switching) or network circuit Switching (circuit Switching), the Packet Switching is adopted by the technology of the video networking to meet the Streaming requirement. The video networking technology has the advantages of flexibility, simplicity and low price of packet switching, and simultaneously has the quality and safety guarantee of circuit switching, thereby realizing the seamless connection of the whole network switching type virtual circuit and the data format.

Switching Technology (Switching Technology)

The video network adopts two advantages of asynchronism and packet switching of the Ethernet, eliminates the defects of the Ethernet on the premise of full compatibility, has end-to-end seamless connection of the whole network, is directly communicated with a user terminal, and directly bears an IP data packet. The user data does not require any format conversion across the entire network. The video networking is a higher-level form of the Ethernet, is a real-time exchange platform, can realize the real-time transmission of the whole-network large-scale high-definition video which cannot be realized by the existing Internet, and pushes a plurality of network video applications to high-definition and unification.

Server Technology (Server Technology)

The server technology on the video networking and unified video platform is different from the traditional server, the streaming media transmission of the video networking and unified video platform is established on the basis of connection orientation, the data processing capacity of the video networking and unified video platform is independent of flow and communication time, and a single network layer can contain signaling and data transmission. For voice and video services, the complexity of video networking and unified video platform streaming media processing is much simpler than that of data processing, and the efficiency is greatly improved by more than one hundred times compared with that of a traditional server.

Storage Technology (Storage Technology)

The super-high speed storage technology of the unified video platform adopts the most advanced real-time operating system in order to adapt to the media content with super-large capacity and super-large flow, the program information in the server instruction is mapped to the specific hard disk space, the media content is not passed through the server any more, and is directly sent to the user terminal instantly, and the general waiting time of the user is less than 0.2 second. The optimized sector distribution greatly reduces the mechanical motion of the magnetic head track seeking of the hard disk, the resource consumption only accounts for 20% of that of the IP internet of the same grade, but concurrent flow which is 3 times larger than that of the traditional hard disk array is generated, and the comprehensive efficiency is improved by more than 10 times.

Network Security Technology (Network Security Technology)

The structural design of the video network completely eliminates the network security problem troubling the internet structurally by the modes of independent service permission control each time, complete isolation of equipment and user data and the like, generally does not need antivirus programs and firewalls, avoids the attack of hackers and viruses, and provides a structural carefree security network for users.

Service Innovation Technology (Service Innovation Technology)

The unified video platform integrates services and transmission, and is not only automatically connected once whether a single user, a private network user or a network aggregate. The user terminal, the set-top box or the PC are directly connected to the unified video platform to obtain various multimedia video services in various forms. The unified video platform adopts a menu type configuration table mode to replace the traditional complex application programming, can realize complex application by using very few codes, and realizes infinite new service innovation.

Networking of the video network is as follows:

the video network is a centralized control network structure, and the network can be a tree network, a star network, a ring network and the like, but on the basis of the centralized control node, the whole network is controlled by the centralized control node in the network.

As shown in fig. 1, the video network is divided into an access network and a metropolitan network.

The devices of the access network part can be mainly classified into 3 types: node server, access switch, terminal (including various set-top boxes, coding boards, memories, etc.). The node server is connected to an access switch, which may be connected to a plurality of terminals and may be connected to an ethernet network.

The node server is a node which plays a centralized control function in the access network and can control the access switch and the terminal. The node server can be directly connected with the access switch or directly connected with the terminal.

Similarly, devices of the metropolitan network portion may also be classified into 3 types: a metropolitan area server, a node switch and a node server. The metro server is connected to a node switch, which may be connected to a plurality of node servers.

The node server is a node server of the access network part, namely the node server belongs to both the access network part and the metropolitan area network part.

The metropolitan area server is a node which plays a centralized control function in the metropolitan area network and can control a node switch and a node server. The metropolitan area server can be directly connected with the node switch or directly connected with the node server.

Therefore, the whole video network is a network structure with layered centralized control, and the network controlled by the node server and the metropolitan area server can be in various structures such as tree, star and ring.

The access network part can form a unified video platform (the part in the dotted circle), and a plurality of unified video platforms can form a video network; each unified video platform may be interconnected via metropolitan area and wide area video networking.

Video networking device classification

1.1 devices in the video network of the embodiment of the present application can be mainly classified into 3 types: servers, switches (including ethernet gateways), terminals (including various set-top boxes, code boards, memories, etc.). The video network as a whole can be divided into a metropolitan area network (or national network, global network, etc.) and an access network.

1.2 wherein the devices of the access network part can be mainly classified into 3 types: node servers, access switches (including ethernet gateways), terminals (including various set-top boxes, code boards, memories, etc.).

The specific hardware structure of each access network device is as follows:

a node server:

as shown in fig. 2, the system mainly includes a network interface module 201, a switching engine module 202, a CPU module 203, and a disk array module 204;

the network interface module 201, the CPU module 203, and the disk array module 204 all enter the switching engine module 202; the switching engine module 202 performs an operation of looking up the address table 205 on the incoming packet, thereby obtaining the direction information of the packet; and stores the packet in a queue of the corresponding packet buffer 206 based on the packet's steering information; if the queue of the packet buffer 206 is nearly full, it is discarded; the switching engine module 202 polls all packet buffer queues for forwarding if the following conditions are met: 1) the port send buffer is not full; 2) the queue packet counter is greater than zero. The disk array module 204 mainly implements control over the hard disk, including initialization, read-write, and other operations on the hard disk; the CPU module 203 is mainly responsible for protocol processing with an access switch and a terminal (not shown in the figure), configuring an address table 205 (including a downlink protocol packet address table, an uplink protocol packet address table, and a data packet address table), and configuring the disk array module 204.

The access switch:

as shown in fig. 3, the network interface module mainly includes a network interface module (a downlink network interface module 301 and an uplink network interface module 302), a switching engine module 303 and a CPU module 304;

wherein, the packet (uplink data) coming from the downlink network interface module 301 enters the packet detection module 305; the packet detection module 305 detects whether the Destination Address (DA), the Source Address (SA), the packet type, and the packet length of the packet meet the requirements, and if so, allocates a corresponding stream identifier (stream-id) and enters the switching engine module 303, otherwise, discards the stream identifier; the packet (downstream data) coming from the upstream network interface module 302 enters the switching engine module 303; the incoming data packet of the CPU module 304 enters the switching engine module 303; the switching engine module 303 performs an operation of looking up the address table 306 on the incoming packet, thereby obtaining the direction information of the packet; if the packet entering the switching engine module 303 is from the downstream network interface to the upstream network interface, the packet is stored in the queue of the corresponding packet buffer 307 in association with the stream-id; if the queue of the packet buffer 307 is nearly full, it is discarded; if the packet entering the switching engine module 303 is not from the downlink network interface to the uplink network interface, the data packet is stored in the queue of the corresponding packet buffer 307 according to the guiding information of the packet; if the queue of the packet buffer 307 is nearly full, it is discarded.

The switching engine module 303 polls all packet buffer queues, which in this embodiment is divided into two cases:

if the queue is from the downlink network interface to the uplink network interface, the following conditions are met for forwarding: 1) the port send buffer is not full; 2) the queued packet counter is greater than zero; 3) obtaining a token generated by a code rate control module;

if the queue is not from the downlink network interface to the uplink network interface, the following conditions are met for forwarding: 1) the port send buffer is not full; 2) the queue packet counter is greater than zero.

The rate control module 308 is configured by the CPU module 304, and generates tokens for packet buffer queues from all downstream network interfaces to upstream network interfaces at programmable intervals to control the rate of upstream forwarding.

The CPU module 304 is mainly responsible for protocol processing with the node server, configuration of the address table 306, and configuration of the code rate control module 308.

Ethernet protocol conversion gateway：

As shown in fig. 4, the apparatus mainly includes a network interface module (a downlink network interface module 401 and an uplink network interface module 402), a switching engine module 403, a CPU module 404, a packet detection module 405, a rate control module 408, an address table 406, a packet buffer 407, a MAC adding module 409, and a MAC deleting module 410.

Wherein, the data packet coming from the downlink network interface module 401 enters the packet detection module 405; the packet detection module 405 detects whether the ethernet MAC DA, the ethernet MAC SA, the ethernet length or frame type, the video network destination address DA, the video network source address SA, the video network packet type, and the packet length of the packet meet the requirements, and if so, allocates a corresponding stream identifier (stream-id); then, the MAC deletion module 410 subtracts MAC DA, MAC SA, length or frame type (2byte) and enters the corresponding receiving buffer, otherwise, discards it;

the downlink network interface module 401 detects the sending buffer of the port, and if there is a packet, obtains the ethernet MAC DA of the corresponding terminal according to the destination address DA of the packet, adds the ethernet MAC DA of the terminal, the MACSA of the ethernet coordination gateway, and the ethernet length or frame type, and sends the packet.

The other modules in the ethernet protocol gateway function similarly to the access switch.

A terminal:

the system mainly comprises a network interface module, a service processing module and a CPU module; for example, the set-top box mainly comprises a network interface module, a video and audio coding and decoding engine module and a CPU module; the coding board mainly comprises a network interface module, a video and audio coding engine module and a CPU module; the memory mainly comprises a network interface module, a CPU module and a disk array module.

1.3 devices of the metropolitan area network part can be mainly classified into 2 types: node server, node exchanger, metropolitan area server. The node switch mainly comprises a network interface module, a switching engine module and a CPU module; the metropolitan area server mainly comprises a network interface module, a switching engine module and a CPU module.

2. Video networking packet definition

2.1 Access network packet definition

The data packet of the access network mainly comprises the following parts: destination Address (DA), Source Address (SA), reserved bytes, payload (pdu), CRC.

As shown in the following table, the data packet of the access network mainly includes the following parts:

DA

SA

Reserved

Payload

CRC

wherein:

the Destination Address (DA) is composed of 8 bytes (byte), the first byte represents the type of the data packet (such as various protocol packets, multicast data packets, unicast data packets, etc.), there are 256 possibilities at most, the second byte to the sixth byte are metropolitan area network addresses, and the seventh byte and the eighth byte are access network addresses;

the Source Address (SA) is also composed of 8 bytes (byte), defined as the same as the Destination Address (DA);

the reserved byte consists of 2 bytes;

the payload part has different lengths according to different types of datagrams, and is 64 bytes if the datagram is various types of protocol packets, and is 32+1024 or 1056 bytes if the datagram is a unicast packet, of course, the length is not limited to the above 2 types;

the CRC consists of 4 bytes and is calculated in accordance with the standard ethernet CRC algorithm.

2.2 metropolitan area network packet definition

The topology of a metropolitan area network is a graph and there may be 2, or even more than 2, connections between two devices, i.e., there may be more than 2 connections between a node switch and a node server, a node switch and a node switch, and a node switch and a node server. However, the metro network address of the metro network device is unique, and in order to accurately describe the connection relationship between the metro network devices, parameters are introduced in the embodiment of the present application: a label to uniquely describe a metropolitan area network device.

In this specification, the definition of the Label is similar to that of the Label of MPLS (Multi-Protocol Label Switch), and assuming that there are two connections between the device a and the device B, there are 2 labels for the packet from the device a to the device B, and 2 labels for the packet from the device B to the device a. The label is classified into an incoming label and an outgoing label, and assuming that the label (incoming label) of the packet entering the device a is 0x0000, the label (outgoing label) of the packet leaving the device a may become 0x 0001. The network access process of the metro network is a network access process under centralized control, that is, address allocation and label allocation of the metro network are both dominated by the metro server, and the node switch and the node server are both passively executed, which is different from label allocation of MPLS, and label allocation of MPLS is a result of mutual negotiation between the switch and the server.

As shown in the following table, the data packet of the metro network mainly includes the following parts:

DA

SA

Reserved

label (R)

Payload

CRC

Namely Destination Address (DA), Source Address (SA), Reserved byte (Reserved), tag, payload (pdu), CRC. The format of the tag may be defined by reference to the following: the tag is 32 bits with the upper 16 bits reserved and only the lower 16 bits used, and its position is between the reserved bytes and payload of the packet.

Based on the characteristics of the video network, one of the core concepts of the embodiment of the application is provided, a thread management module and a task management module are arranged in a video network server according to a protocol of the video network, the thread management module establishes a thread unit corresponding to a task according to the current task operation of a user, the task management module calls task data in the thread unit into a task set area in the task management module through adding, deleting, modifying and canceling interfaces and adds the task data into the task set area corresponding to the thread unit.

Meanwhile, the disk is further arranged in the video networking server, the disk can store task data written in the task unit by the task set area, and persistence of the data is achieved, so that the safety of the task can be guaranteed.

Example 1:

as shown in fig. 5, a block diagram of a multitask management system based on a video network according to an embodiment of the present application is shown, where the multitask management system may be applied to a video network, the video network may include a video network server 01, and the video network server 01 may specifically include a thread management module 501, a task management module 502, and a disk 503, where:

the thread management module 501 is connected with the task management module 502, and a plurality of thread units 504 are arranged in the thread management module;

the task management module 502 is connected to the thread management module 501 and the disk 503, and a task set area 505 is provided in the task management module, and task units 506 corresponding to the thread units 504 are provided in the task set area 505;

the disk 503 is connected to the task management module 502, and is configured to store task data written in the task unit 506 by the task aggregation area 505.

The video network server 01 in the embodiment of the application has the aspects of high-speed computing capability, long-time reliable operation, strong external data throughput capability and the like, is a central and informatization core of a video network local area network, and can support multi-user multitask operation.

The thread management module 501 is located in the video network server 01, and can communicate with a plurality of user terminals 02 through the video network based on the video network protocol. The thread unit 504 in the thread management module 501 is created according to a task operation command sent by the user terminal 02, corresponds to a task operation command, belongs to a background thread, and is invisible to a user. The thread management module 501 may receive task operation commands sent by a plurality of user terminals 02 at the same time, create corresponding thread units 504 at the same time, and execute corresponding tasks through one or more thread units 504, so as to satisfy the user operations.

The embodiment of the application also creates a task management module 502, and a task set area 505 is set in the task management module 502, and the task management module 502 can call the task data in each thread unit 504 into the task set area 505 and add the task data into the task unit 506 corresponding to the thread unit 504, so that all current tasks are collected together by using the task set area 505, and unified task management can be performed on task operations of all current users, and the managed tasks can be executed concurrently, thereby solving the problems that the management of each task is more dispersed and the management difficulty is higher in the existing management system.

In order to avoid the problem that the task data temporarily stored in the task aggregation area 505 is lost due to power failure, in the embodiment of the present application, a disk 503 is further added to the video network server 01, and the task management module 502 can fetch some or all of the task data in the task aggregation area 505 and write the task data into the disk 503, so that the saved task data is still valid when the system is restarted. Task data written to disk 503 may also be stored in the form of task unit 506. The task management module 502 may read task data corresponding to the recovery operation according to the recovery operation of the user, or may automatically read all task data in the disk 503 by a preset program and then execute the task.

The task management module 502 of the embodiment of the present application may use a thread pool provided by an open source framework Spring and a Java language software development kit jdk thread security set Map to manage tasks.

The disk 503 may employ a storage system redis. Redis is an open source log-type and Key-Value Key-Value database which is written by using ANSI C language, supports network, can be based on memory and can also be persistent, and provides application programming interface API of multiple languages.

In a preferred embodiment of the present application, the video network further includes a plurality of user terminals 02, the plurality of user terminals 02 are communicatively connected to the thread management module 501, and the thread management module 501 includes the following sub-modules:

the user task docking sub-module is used for receiving a task operation command sent by the user terminal 02; wherein the task operation command is generated by the user terminal 02 when receiving a trigger operation of the task;

and the thread unit creating submodule is used for creating a thread unit 504 corresponding to the task according to the task operation command.

The thread management module 501 in the embodiment of the present application may specifically include a user task interfacing sub-module and a thread unit creating sub-module.

In practice, there are a plurality of user terminals 02 in the video network, a user operates on the user terminal 02, the user terminal 02 generates a task operation command according to the operation of the user and sends the task operation command to the video network server 01, and after receiving the task operation command, the thread management module 501 in the video network server 01 creates a thread unit 504 corresponding to the task according to the task command.

The user terminal 02 of the embodiment of the application may be a video network terminal with an access function, and may communicate with various external devices, such as a mobile phone, a tablet, a desktop, a notebook, a network camera, and the like; the system can also be a software client which can be installed on a mobile phone, a tablet, a desktop or a notebook.

In a preferred embodiment of the present application, the task management module 502 includes the following sub-modules:

the task receiving submodule is configured to receive task data sent by the thread management module 501; the task data is data in the thread unit 504 corresponding to the task, which is called by the thread management module 501 according to the received task operation command;

a task operation sub-module, configured to call the task data into the task aggregation area 505, and add the task data to a task unit 506 corresponding to the thread unit 504;

and the task writing submodule is used for writing the task data in the task unit 506 into the disk 503.

The embodiment of the present application further describes a specific structure of the thread management module 501, which may specifically include a task receiving submodule, a task operating submodule, and a task writing submodule.

The task receiving submodule is a uniform data interface, can specifically comprise several types of adding, deleting, modifying and canceling, can add, delete and modify timed and non-timed tasks of the system, can meet the requirements of a user on monitoring the adding, deleting, checking and modifying operations of recording tasks, and simultaneously provides a management function for other timed tasks of the system, and the managed tasks are executed concurrently. The task receiving submodule may receive the task data sent by the thread management module 501 through the above type of interface. Compared with the prior art, the task classification method and the task classification device have the advantages that the task classification mode is flexible through the specific task types (including addition, deletion, modification and cancellation), the summary is comprehensive, the management interfaces of the tasks are unified, the centralized management of the distributed tasks can be realized, and the management difficulty is greatly reduced.

The task operation submodule has a calling function, and can call the task data received by the task receiving submodule into the task set area 505 and add the task data into the task unit 506 corresponding to the thread unit 504.

The task writing sub-module is an execution module, and can write task data in part or all of the task units 506 in the task collection area 505 into the disk 503 according to a command of the video network server 01, so as to implement data persistence.

In a specific example of the embodiment of the present application, task data in the task aggregation area 505 or the disk 503 may be stored in a key-value mapping relationship, because the java development program provides a HashMap hash-hilgarh graph with efficient thread security, and the key is unique, and a corresponding value can be found by the value.

And taking a character string of 'server number identification GUID-task type-task address ID' as a key, and taking an object of a specific processing task as a value. The server GUDI is a unique identifier of the user terminal 02 in the internet of view server 01, the task type indicates which kind of task is (such as adding, deleting, modifying and canceling), and the ID is a unique identifier of a certain task under this kind.

In a specific application of the embodiment of the present application, the task receiving sub-module may include an interface for adding, deleting, modifying, and canceling the task.

Specifically, the interface for adding the task is mainly used for adding the task type execution identifier to the task data according to the specific content of the task data, and then adding the task type execution identifier to the corresponding task unit 506.

And deleting and canceling the interfaces of the tasks, and removing the tasks from execution. The difference is that the former checks that if the task is executed, the task is directly interrupted forcibly, and the latter waits for the execution to be finished.

And modifying the interface of the task, and setting the parameters of the task executor to the added task.

Receiving the application, the task unit 506 in the task collection area 505 further carries a task type execution identifier, and the task type execution identifier may include the following identifiers:

first type identification: the task data is executed immediately after being added to the task unit 506;

the second type identification: the task data is added to the task unit 506 and then is executed after a preset time delay;

the third type identification: the task data is added to the task unit 506 and then executed at a specified date and time;

the fourth type identification: the task data is added to the task unit 506 and then repeatedly executed at fixed time intervals.

For all the task data mentioned above, the task data of the embodiment of the present application may include service data corresponding to the task and data for the task to execute the service.

In addition, the task unit 506 in the task aggregation area 505 in the embodiment of the present application further carries a task state identifier, where the task state identifier may include a task waiting identifier and a task executing identifier.

The task waiting flag indicates that the current task unit 506 is in a task waiting state, and the task execution flag indicates that the current task unit 506 is in a task execution state.

In specific implementation, after adding the task type execution identifier to the task data according to the specific content of the task data, the task management module 502 may place the task type execution identifier into the task unit 506 having the task waiting identifier or into the task unit 506 having the task execution identifier according to the task type execution identifier. Such as adding task data with a first type identifier and a fourth type identifier of a task type execution identifier to a task unit 506 having a task execution identifier; task data with a second type identification and a third type identification of the task type execution identification is added to the task unit 506 with the task waiting identification.

The preferred embodiment of the present application further provides a specific implementation sub-module, after the system is restarted, where the task management module 502 may read the task data corresponding to the recovery operation according to the recovery operation of the user, and may also automatically read all task data in the disk 503 by a preset program, that is:

and the task reading submodule is configured to read task data in the disk 503 after receiving a trigger signal for restarting the system.

After the task data is read by the task reading sub-module, the task management module 502 executes the task according to the task data, so that the problem that the task is easily lost after power-off initialization in the prior art can be solved.

Example 2:

as shown in fig. 6, a flowchart of steps of a multitask management method based on a video network according to an embodiment of the present application is shown, where the method may be applied to a video network, where the video network includes a video network server 01 and a user terminal 02 communicatively connected to the video network server 01, and the method may specifically include the following steps:

step S601: the video network server 01 receives a task operation command sent by the user terminal 02; wherein the task operation command is generated by the user terminal 02 when receiving a trigger operation of the task;

step S602: the video network server 01 creates a thread unit 504 corresponding to the task according to the task operation command;

step S603: the video network server 01 calls the task data in the thread unit 504 into the task collection area 505 and adds the task data into the task unit 506 corresponding to the thread unit 504;

step S604: the video network server 01 writes the task data in the task unit 506 into the disk 503.

Steps S601 to S604 in the embodiment of the present application are system structures corresponding to embodiment 1, and describe steps that may be executed by the system to complete its function, and reference is made to embodiment 1 for specific implementation principles.

According to the embodiment of the application, all current tasks are uniformly integrated into the task integration area 505, the task operation of all current users can be uniformly managed, the managed tasks can be executed concurrently, and the problems that the management of each task is dispersed and the management difficulty is high in the current video network server 01 are solved.

Meanwhile, the disk is used for storing the task data written in the task unit 506 in the task set area, so that the persistence of the data is realized, the safety of the task can be guaranteed, the task is still available after the next system restart under the condition of system restart or equipment power failure, and the problem that the task is automatically lost after the power failure initialization in the prior art is solved.

In a preferred embodiment of the present application, the task operation command may specifically include:

adding the task command;

and/or, deleting the task command;

and/or, modifying the task command;

and/or, cancel the task command.

The task operation command of the embodiment of the application provides an interface type source for the task receiving submodule in the system of the embodiment of the application, namely, the interfaces for adding, deleting, modifying and canceling the tasks included by the task receiving submodule correspond to the task command for adding, deleting, modifying and canceling one by one, so that the embodiment of the application can meet all operations of a user, and the unified management of task data corresponding to the user operations is completed.

It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.

As for the method embodiment, since it is basically similar to the system embodiment, the description is simple, and the relevant points can be referred to the partial description of the system embodiment.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

As will be appreciated by one of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.

The present application provides a multitask management system based on video networking and a multitask management method based on video networking, which are introduced in detail above, and specific examples are applied in this text to explain the principle and the implementation of the present application, and the description of the above embodiments is only used to help understanding the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. The multitask management system based on the video network is characterized in that the multitask management system is applied to the video network, the video network comprises a video network server, the video network server comprises a thread management module, a task management module and a disk, wherein:

the disk is connected with the task management module and used for storing the task data written in the task unit by the task set area; the task data is data in a thread unit corresponding to the task, which is called by the thread management module according to the received task operation command.

2. The system of claim 1, wherein the video network further comprises a plurality of user terminals communicatively coupled to the thread management module, wherein the thread management module comprises the following sub-modules:

3. The system of claim 2, wherein the task management module comprises the following sub-modules:

the task receiving submodule is used for receiving the task data sent by the thread management module;

4. The system of claim 3, wherein the task receiving submodule includes interfaces for adding, deleting, modifying, and canceling the task.

5. The system according to claim 3, wherein the task units in the task aggregation area further carry task type execution identifiers, and the task type execution identifiers include:

6. The system according to claim 1 or 3, wherein the task data comprises business data corresponding to the task, and data for the task to execute the business.

7. The system according to claim 1 or 3, wherein the task units in the task aggregation area carry task state identifiers, and the task state identifiers include a task waiting identifier and a task executing identifier.

8. The system of claim 1, wherein the task management module further comprises the following sub-modules:

9. A multitask management method based on video network is characterized in that the method is applied to the video network, the video network comprises a video network server and a user terminal which is in communication connection with the video network server, and the method comprises the following steps:

the video network server transfers the task data in the thread unit to a task set area and adds the task data to a task unit corresponding to the thread unit; the task data is data in a thread unit corresponding to the task, which is called by a thread management module in the video network server according to the received task operation command;

and the video network server writes the task data in the task unit into a disk.

10. The method of claim 9, wherein the task operation command comprises:

adding a task command;

and/or, delete task commands;

and/or, modifying the task command;

and/or cancel task commands.