CN112306690A - Scheduling method and device - Google Patents
Scheduling method and device Download PDFInfo
- Publication number
- CN112306690A CN112306690A CN202011203403.8A CN202011203403A CN112306690A CN 112306690 A CN112306690 A CN 112306690A CN 202011203403 A CN202011203403 A CN 202011203403A CN 112306690 A CN112306690 A CN 112306690A
- Authority
- CN
- China
- Prior art keywords
- component
- service request
- distribution
- service
- components
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 24
- 239000000306 component Substances 0.000 claims description 263
- 238000012216 screening Methods 0.000 claims description 19
- 239000008358 core component Substances 0.000 claims description 18
- 238000012545 processing Methods 0.000 claims description 14
- 230000007246 mechanism Effects 0.000 abstract description 4
- 230000005540 biological transmission Effects 0.000 description 6
- 230000002265 prevention Effects 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 4
- 238000013079 data visualisation Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004888 barrier function Effects 0.000 description 1
- 230000001149 cognitive effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012502 risk assessment Methods 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present disclosure provides a scheduling method and apparatus, the method including: receiving a service request of a user; determining a distribution component corresponding to the service request according to a preset routing rule, wherein the routing rule is acquired from a configuration center; distributing the service request to the distribution component. And a multi-component cooperative working mechanism is constructed, a reproducible and automatic service providing mode is created, and the rapid service deployment is realized.
Description
Technical Field
The disclosure belongs to the technical field of communication, and particularly relates to a scheduling method and device.
Background
The components are simple packages of data and methods. The components include software information systems, libraries, plug-ins, frameworks, etc., and are of a wide variety and complexity. A component generally refers to a portion of a software system that assumes specific responsibilities and can be developed and tested independently of the overall system.
With the increasing complexity of the system, to establish a typical service, various resources are often involved, such as: storage resources, computing resources, operating systems, and application software, and connect the physical entities of these resources through a network. This makes the establishment of services a great technical barrier, making rapid deployment of services extremely difficult.
Disclosure of Invention
In view of the above-mentioned shortcomings in the prior art, the present disclosure provides a scheduling method and apparatus.
As a first aspect of the present disclosure, there is provided a scheduling method, including:
receiving a service request of a user;
determining a distribution component corresponding to the service request according to a preset routing rule, wherein the routing rule is acquired from a configuration center;
distributing the service request to the distribution component.
Preferably, the routing rule includes a component type, a component message source address, and a component message destination address, and the determining, according to the preset routing rule, the distribution component corresponding to the service request includes:
determining a component type matching the type of the service request;
and screening out corresponding distribution components from the components of the component types according to the addresses of the component message sources and the component message destination addresses.
Preferably, the screening out the corresponding distribution component from the components of the component type according to the address of the component message source and the address of the component message destination includes:
screening out distribution components meeting preset conditions from the components of the component types, wherein the distribution components comprise a first component and a second component;
the preset conditions include: the component message source address of the first component is the same as the component message destination address of the second component.
Preferably, the component types include: the system comprises a platform service layer supporting component, a data service layer core component and a software service layer core component.
Preferably, before distributing the service request to the distributing component, the method further comprises:
processing the service request to obtain service parameters;
the distributing the service request to the distributing component, comprising:
and distributing the service request carrying the service parameters to the distribution component.
As a second aspect of the present disclosure, there is provided a scheduling apparatus comprising:
the receiving module is used for receiving a service request of a user;
the determining module is used for determining a distribution component corresponding to the service request according to a preset routing rule, wherein the routing rule is acquired from a configuration center;
a sending module for distributing the service request to the distribution component.
Preferably, the routing rule includes a component type, a component message source address, and a component message destination address, and the determining module includes:
the determining submodule is used for determining a component type matched with the type of the service request;
and the screening submodule is used for screening out a corresponding distribution component from the components of the component type according to the address of the component message source and the address of the component message destination.
Preferably, the screening submodule is specifically configured to:
screening out distribution components meeting preset conditions from the components of the component types, wherein the distribution components comprise a first component and a second component;
the preset conditions include: the component message source address of the first component is the same as the component message destination address of the second component.
Preferably, the component types include: the system comprises a platform service layer supporting component, a data service layer core component and a software service layer core component.
Preferably, the apparatus further comprises:
the processing module is used for processing the service request to obtain service parameters;
the sending module is specifically configured to:
and distributing the service request carrying the service parameters to the distribution component.
In the embodiment of the disclosure, the scheduling device receives a service request of a user, determines a distribution component corresponding to the service request according to a preset routing rule, distributes the service request to the distribution component, constructs a multi-component cooperative working mechanism, creates a reproducible and automatic service providing mode, and realizes rapid service deployment.
Drawings
Fig. 1 is a flowchart of a scheduling method according to an embodiment of the present disclosure;
fig. 2 is another flowchart of a scheduling method according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a scheduling apparatus according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions of the present invention better understood, the present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
In order to rapidly deploy services, the disclosure provides a scheduling method and a scheduling device. The following detailed description is made with reference to the accompanying drawings which respectively illustrate embodiments provided by the present disclosure.
The community is a basic building unit of a city, the safety of the community is closely related to the life of people, and the important significance is achieved by collecting basic data through a monitoring means and analyzing and predicting various possible risks. The community risk prevention component generally comprises service components such as community equipment facility real-time monitoring management, major/special crowd behavior rule mining and monitoring early warning, and grid cooperative management of community risk prevention. The embodiments of the present disclosure take the deployment of services in a community risk prevention component as an example, as discussed below.
Fig. 1 shows a flowchart of a scheduling method provided by an embodiment of the present disclosure. The scheduling method can be applied to a scheduling device, and the scheduling device is a message queue. As shown in fig. 1, the scheduling method provided by this embodiment includes the following steps.
Step 101, receiving a service request of a user.
In this step, the message queue receives a service request of a user.
And 102, determining a distribution component corresponding to the service request according to a preset routing rule.
Wherein the routing rule is obtained from a configuration center. The configuration center pre-configures routing rules, where the routing rules include routing models, Access Control List (ACL) configuration tables, and pre-defined component models.
In this step, the message queue combines and arranges the components according to a certain arrangement mode according to the component model in the routing rule, and determines the distribution component corresponding to the service request. The well-defined component model will become an essential element of service orchestration. The arrangement refers to reasonably arranging and organizing various services and key points according to the user requirements as guidance, and is the key for mutually cooperating all parts (components) forming the services and finally generating the services capable of meeting the user requirements.
Step 103, distributing the service request to the distribution component.
In this step, the message queue distributes the service request to all distribution components of the orchestration row. And meanwhile, the message queue responds to the service request according to specific parameters in the routing rule, and forms a service (carried in the service request) which can be used by the user and distributes the service to the distribution component. The specific parameters in the routing rule are information such as an Internet Protocol (IP) address and a route that need to be determined based on an actual network.
And finally, the message queue acquires service request feedback information, and when response messages returned by all the distribution components are received, different components work cooperatively to complete the calling of different components.
In the embodiment of the disclosure, the scheduling device receives a service request of a user, determines a distribution component corresponding to the service request according to a preset routing rule, distributes the service request to the distribution component, constructs a multi-component cooperative working mechanism, creates a reproducible and automatic service providing mode, and realizes rapid service deployment.
Further, the routing rule includes a component type, a component message source address, and a component message destination address.
Specifically, a routing rule is configured in advance in the configuration center, and the routing rule includes a routing model, an ACL configuration table, each predefined component model, and the like. The configuration center connects each component to the network and configures routing rules. The configuration center selects the infrastructure functional models that the components need to use, including the network model and the service computing model. Specifically, the Network model includes a Network access model, an IP routing model, a Network interconnection quality model, and a Virtual Private Network (VPN) service model. The configuration center allocates software and hardware resources (hardware resources include various switching devices, etc.) to each service model. The configuration center sets various configuration parameters and component models in the service model, and the various configuration parameters include Virtual Local Area Network (VLAN), IDentification (ID), ACL configuration, user authentication configuration parameters, and the like.
The component model is defined based on the container, and the component model comprises a component type, a component message source address and a component message destination address. Defining a component model, expressed in terms of components, which is a triple: component { [ type, in, out }. Wherein type is a component type. in, denotes the address of the message flowing into the current component, i.e., the component message source address, which may be a plurality of addresses. The source of the message may be other components or a service. out, represents the sending address of the message, i.e. the component message destination address, which may be a plurality of destination addresses. The purpose of the message may be other components or a service.
As can be seen from the above definition, information can be transmitted between multiple components. The components can be divided into data source components, data processing analysis components and data visualization components according to the information transmission sequence, wherein the data source components collect data, the data processing analysis components process data/messages, and the data visualization components transmit data analysis results/messages to service destinations. And defining in and out of each component according to the information transmission sequence, and ensuring that the defined in and out can enable each component to transmit according to the information transmission sequence.
After the configuration center connects the network for each component and configures the routing rule, the instantiation work of the component model is completed, and the component model is converted into distributable service.
Fig. 2 shows another flowchart of a scheduling method provided by the embodiment of the present disclosure. Accordingly, as shown in fig. 2, the determining the distribution component corresponding to the service request according to the preset routing rule (i.e. step 102) includes:
in step 201, a component type matching the type of the service request is determined.
In this step, what the type of service request is, i.e. what the purpose of the service request is, is determined what the matching component type is. For example, the type of service request is a compute type, then the matching component type is a compute type component.
Further, the component types include: the system comprises a platform service layer supporting component, a data service layer core component and a software service layer core component.
The community risk prevention component provided by the embodiment of the disclosure has three types: the system comprises a platform service layer supporting component, a data service layer core component and a software service layer core component. The platform services layer support component includes a cognitive computation operator component for risk perception, understanding, and prediction. The data service layer core component comprises community multi-source heterogeneous data acquisition, processing, application and a shared data bus. The software service layer core component comprises a community equipment facility intelligent risk analysis and early warning service component and a community risk prevention grid collaborative management service component.
It should be noted that, the platform service layer supporting component, the data service layer core component and the software service layer core component are in a many-to-one or one-to-many relationship with the data source component, the data processing analysis component and the data visualization component according to the information transmission sequence, and the two are two different classification methods.
Step 202, according to the address of the component message source and the address of the component message destination, selecting a corresponding distribution component from the components of the component type.
Further, the screening out the corresponding distribution component from the components of the component type according to the address of the component message source and the component message destination address (i.e. step 202), includes: and screening out the distribution components meeting the preset conditions from the components of the component types.
Wherein the dispensing assembly comprises a first assembly and a second assembly; the preset conditions include: the component message source address of the first component is the same as the component message destination address of the second component.
The first and second components may each refer to different components. In of the first component is the same as out of the second component, the first component and the second component can carry out information transmission, and the second component sends information to the first component. That is, in step 202, components capable of mutually transmitting information are screened out from the components of the component types as corresponding distribution components. The corresponding dispensing component is selected as a minimum of two components.
It should be noted that, active acquisition is required for information transmission between different components working in cooperation. For example, if a first component (e.g., the first component is a data processing analysis class component) needs to obtain information of a second component (e.g., the second component is a data source class component), the first component sends a request for obtaining to the second component, and the second component sends the information to the first component.
It should be noted that there are a plurality of components in one container. The respective dispensing components that are screened out may be different components in a plurality of containers.
Further, before the distributing the service request to the distributing component (i.e. step 103), the method further includes: and processing the service request to obtain service parameters.
In this step, the message queue performs parsing, filtering, converting, calculating, and forwarding on the service request to obtain the service parameters. Accordingly, the distributing the service request to the distributing component (i.e., step 103) includes: and distributing the service request carrying the service parameters to a distribution component.
In the embodiment of the disclosure, a component model is defined, the actual component cooperation requirements are combined for arrangement, a multi-component cooperation working mechanism is constructed, a reproducible and automatic service providing mode is created, and a community risk prevention service is provided for the outside.
Fig. 3 shows a schematic structural diagram of a scheduling apparatus provided in an embodiment of the present disclosure. Based on the same technical concept as the embodiment corresponding to fig. 1, as shown in fig. 3, the scheduling apparatus provided by the embodiment of the present disclosure includes the following modules.
The receiving module 11 is configured to receive a service request of a user.
A determining module 12, configured to determine a distribution component corresponding to the service request according to a preset routing rule, where the routing rule is obtained from a configuration center.
A sending module 13, configured to distribute the service request to the distribution component.
Preferably, the routing rule includes a component type, a component message source address, and a component message destination address, and the determining module includes:
and the determining submodule is used for determining the component type matched with the type of the service request.
And the screening submodule is used for screening out a corresponding distribution component from the components of the component type according to the address of the component message source and the address of the component message destination.
Preferably, the screening submodule is specifically configured to:
and screening out distribution components meeting preset conditions from the components of the component types, wherein the distribution components comprise a first component and a second component.
The preset conditions include: the component message source address of the first component is the same as the component message destination address of the second component.
Preferably, the component types include: the system comprises a platform service layer supporting component, a data service layer core component and a software service layer core component.
Preferably, the apparatus further comprises:
and the processing module is used for processing the service request to obtain the service parameters.
The sending module is specifically configured to:
and distributing the service request carrying the service parameters to the distribution component.
It will be understood that the above embodiments are merely exemplary embodiments taken to illustrate the principles of the present invention, which is not limited thereto. It will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the spirit and substance of the invention, and these modifications and improvements are also considered to be within the scope of the invention.
Claims (10)
1. A method of scheduling, comprising:
receiving a service request of a user;
determining a distribution component corresponding to the service request according to a preset routing rule, wherein the routing rule is acquired from a configuration center;
distributing the service request to the distribution component.
2. The scheduling method according to claim 1, wherein the routing rule includes a component type, a component message source address, and a component message destination address, and the determining a distribution component corresponding to the service request according to a preset routing rule includes:
determining a component type matching the type of the service request;
and screening out corresponding distribution components from the components of the component types according to the addresses of the component message sources and the component message destination addresses.
3. The scheduling method of claim 2, wherein the screening out corresponding distribution components from the components of the component type according to the addresses of the component message sources and the component message destination addresses comprises:
screening out distribution components meeting preset conditions from the components of the component types, wherein the distribution components comprise a first component and a second component;
the preset conditions include: the component message source address of the first component is the same as the component message destination address of the second component.
4. The scheduling method of claim 2, wherein the component type comprises: the system comprises a platform service layer supporting component, a data service layer core component and a software service layer core component.
5. The scheduling method of claim 1, wherein said distributing the service request to the distributing component further comprises:
processing the service request to obtain service parameters;
the distributing the service request to the distributing component, comprising:
and distributing the service request carrying the service parameters to the distribution component.
6. A scheduling apparatus, comprising:
the receiving module is used for receiving a service request of a user;
the determining module is used for determining a distribution component corresponding to the service request according to a preset routing rule, wherein the routing rule is acquired from a configuration center;
a sending module for distributing the service request to the distribution component.
7. The scheduler of claim 6, wherein the routing rules include a component type, a component message source address, and a component message destination address, and wherein the determining module comprises:
the determining submodule is used for determining a component type matched with the type of the service request;
and the screening submodule is used for screening out a corresponding distribution component from the components of the component type according to the address of the component message source and the address of the component message destination.
8. The scheduling device of claim 7, wherein the filter submodule is specifically configured to:
screening out distribution components meeting preset conditions from the components of the component types, wherein the distribution components comprise a first component and a second component;
the preset conditions include: the component message source address of the first component is the same as the component message destination address of the second component.
9. The scheduling apparatus of claim 7, wherein the component type comprises: the system comprises a platform service layer supporting component, a data service layer core component and a software service layer core component.
10. The scheduling apparatus of claim 6, wherein the apparatus further comprises:
the processing module is used for processing the service request to obtain service parameters;
the sending module is specifically configured to:
and distributing the service request carrying the service parameters to the distribution component.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011203403.8A CN112306690A (en) | 2020-11-02 | 2020-11-02 | Scheduling method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011203403.8A CN112306690A (en) | 2020-11-02 | 2020-11-02 | Scheduling method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112306690A true CN112306690A (en) | 2021-02-02 |
Family
ID=74333618
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011203403.8A Pending CN112306690A (en) | 2020-11-02 | 2020-11-02 | Scheduling method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112306690A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101075201A (en) * | 2007-06-26 | 2007-11-21 | 北京邮电大学 | Method for realizing unified universal message bus between different assembly process |
| CN103841090A (en) * | 2012-11-26 | 2014-06-04 | 中兴通讯股份有限公司 | Method, device and system for realizing multi-service-server distribution of session initiation protocol (SIP) |
| CN104243611A (en) * | 2014-09-30 | 2014-12-24 | 浪潮软件股份有限公司 | Distribution thought based message service middleware system |
| CN108259605A (en) * | 2018-01-17 | 2018-07-06 | 深圳市和讯华谷信息技术有限公司 | A kind of data calling system and method based on multiple data centers |
| CN109618119A (en) * | 2018-10-31 | 2019-04-12 | 视联动力信息技术股份有限公司 | Method and device for business processing |
-
2020
- 2020-11-02 CN CN202011203403.8A patent/CN112306690A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101075201A (en) * | 2007-06-26 | 2007-11-21 | 北京邮电大学 | Method for realizing unified universal message bus between different assembly process |
| CN103841090A (en) * | 2012-11-26 | 2014-06-04 | 中兴通讯股份有限公司 | Method, device and system for realizing multi-service-server distribution of session initiation protocol (SIP) |
| CN104243611A (en) * | 2014-09-30 | 2014-12-24 | 浪潮软件股份有限公司 | Distribution thought based message service middleware system |
| CN108259605A (en) * | 2018-01-17 | 2018-07-06 | 深圳市和讯华谷信息技术有限公司 | A kind of data calling system and method based on multiple data centers |
| CN109618119A (en) * | 2018-10-31 | 2019-04-12 | 视联动力信息技术股份有限公司 | Method and device for business processing |
Non-Patent Citations (2)
| Title |
|---|
| 传智播客高教产品研发部: "《PHP程序设计高级教程》", vol. 1, 31 January 2015, 中国铁中国铁道出版社道出版社, pages: 232 - 237 * |
| 王璐欢等: "《工业互联网与机器人技术应用初级教程》", vol. 1, 30 June 2020, 哈尔滨工业大学出版社, pages: 55 - 57 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114095579B (en) | Network system for computing power processing, service processing method and equipment | |
| CN112751826B (en) | Method and device for forwarding flow of computing force application | |
| Gundall et al. | Introduction of a 5G-enabled architecture for the realization of industry 4.0 use cases | |
| Medhat et al. | Service function chaining in next generation networks: State of the art and research challenges | |
| Cheng et al. | FogFlow: Easy programming of IoT services over cloud and edges for smart cities | |
| CN109600246B (en) | Network slice management method and device | |
| US5974237A (en) | Communications network monitoring | |
| CN113448721A (en) | Network system for computing power processing and computing power processing method | |
| CN105103493B (en) | The method and relevant apparatus and communication system of realization network virtualization | |
| EP0849912A2 (en) | Communications network monitoring | |
| WO2022184094A1 (en) | Network system for processing hash power, and service processing method and hash power network element node | |
| Müller et al. | 5G as key technology for networked factories: Application of vertical-specific network services for enabling flexible smart manufacturing | |
| CN1906902B (en) | Method for transferring packets in networks comprising a plurality of linked intermediate networks | |
| Figuerola et al. | PHOSPHORUS: Single-step on-demand services across multi-domain networks for e-science | |
| CN110958306B (en) | Data request unified exchange mechanism based on micro-service | |
| CN113839995A (en) | Cross-domain resource management system, method, device and storage medium | |
| CN112911001A (en) | Cloud VPN and enterprise network automatic networking scheme | |
| CN106850803B (en) | SDN-based weighted polling system and algorithm | |
| US20130138793A1 (en) | Network information processing system, a network information processing apparatus and a data processing method | |
| CN107819596B (en) | SDN network fault diagnosis method, device and system | |
| EP0849911A2 (en) | Communications network monitoring | |
| EP0849910A2 (en) | Communications network monitoring | |
| CN112306690A (en) | Scheduling method and device | |
| CN110351204A (en) | The method and system that cloud data center Internet resources dynamically distribute | |
| Chung et al. | Novel network services for supporting big data science research |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |