APP下载

Research on logistics domain-oriented cloud resource management model and architecture①

2017-03-28ZhangXiaodong张小东ZhanDechenChuDianhui

High Technology Letters 2017年1期

Zhang Xiaodong (张小东), Zhan Dechen, Chu Dianhui

(*School of Computer Science and Technology, Harbin Institute of Technology, Harbin 150001, P.R.China) (**School of Computer Science and Technology, Harbin Institute of Technology at Weihai, Weihai 264209, P.R.China)

Research on logistics domain-oriented cloud resource management model and architecture①

Zhang Xiaodong (张小东)②***, Zhan Dechen*, Chu Dianhui**

(*School of Computer Science and Technology, Harbin Institute of Technology, Harbin 150001, P.R.China) (**School of Computer Science and Technology, Harbin Institute of Technology at Weihai, Weihai 264209, P.R.China)

To address the challenges posed by resource shortage or surplus to enterprises productivity, Internet platforms have been widely used, which can balance shortage and surplus in broader environments. However, the existing resource management models lack openness, sharing ability and scalability, which make it difficult for many heterogeneous resources to co-exist in the same system. It is also difficult to resolve the conflicts between distributed self-management and centralized scheduling in the system. This paper analyzes the characteristics of resources in the distributed environment and proposes a new resource management architecture by considering the resource aggregation capacity of cloud computing. The architecture includes a universal resource scheduling optimization model which has been applied successfully in double-district multi-ship-scheduling multi-container-yard empty containers transporting of international shipping logistics. Applications in all these domains prove that this new resource management architecture is feasible and can achieve the expected effect.

resource attribute, resource service model, resource calendar, resource management architecture, resource service optimized scheduling

0 Introduction

Cloud computing is a large shared resource pool, where tenants can choose service resources dynamically on demand[1,2]. Cloud computing can provide computing resource, including CPUs, hard disks, memories, networks, software, data and so on. Its service attributes are simple. Time or cost is usually defined as the optimization objective to construct a model based on capability or finance[3]. Besides computing resources, the application system based on cloud computing needs lots of shared domain-oriented resources, e.g. hard logistics resources including conveyers, transportation vehicles and labors, etc. Soft logistics resources includes demonstration, delivery, scheduling, integration, etc. Enterprises can introduce shareable resources to the Cloud in order to balance resource between surplus and shortage in a wider area. However, it brings great challenge to manage the resources owing to many varieties and large amounts of resources in the application system and different definitions and managing methods of the resources by resource service provider (RSP) and resource service demander (RSD). For example, it usually happens that the resources of RSP are abundant, but at the same time, RSD cannot find appropriate resources in the transportation service. The causes of this predicament are: 1) Information communication is poor. isolated information exists. 2) There are too many resources and tasks to make it difficult to find the best assignment for both RSP and RSD. The key point of the problem is that both resource management and service mode are imperfect. Therefore, this paper focuses on resource management in cloud computing, and resource management architecture is built including resource model, resource service mode, resource management architecture and an appropriate scheduling algorithm, which can be widely used for varieties of resources management and they are pretty scalable.

1 Related work

There has been a lot of related researches about resource management, as a hot issue it is, such as resource description frame (RDF)[4,5]and web ontology language (OWL)[6]. RDF describes resource by a triple consisting of resource, attribute type and attribute value. RDF schema (RDFS) is a defining language which is used to define the attribute element of metadata. People can describe any type of resources in their own words by RDFS. OWL, in contrast, defines resources with ontology which is more suitable in Internet. It can also describe the relation of different resources and the meaning of resource in certain field and has the ability of logic description and reasoning. However, if each user defines resource by RDF and OWL in their own way, there will be the problems mentioned above. Therefore, it is essential to unify specification and description.

Peng, et al.[7]found similarities of telecommunication resources after abstracting and objectifying them. They presented a concept of virtual resources and built a resource management model which could mask the difference among heterogeneous resources. Wang, et al.[8]introduced a concept of logical resource tree about heterogeneous resources in WAN and proposed a global unified hierarchical model of network resource by abstracting resource parameters. Comparing with the resource pool[9]and the global-local two-layer model[10], to some degree, the model masks the difference among heterogeneous resources and the model is extensible in some level. Keahey, et al.[11]proposed a multilevel resource management model and analyzed the heterogeneity of resource and scalability of the model. Li, et al.[12]built a meta-model of the resource and presented a unified frame of manufacturing resource management on the meta-model. The methods above can effectively mask the difference of heterogeneous resources and reduce the difficulty caused by resource diversity. It is convenient for the unified mode of expression to put the resource into the system and manage them in centralized way. However, it does not mention that it is likely that various resources need to cooperate to complete a task, that is, cooperation among different resources.

Li, et al.[13,14]proposed a cloud manufacturing framework, which combined cloud computing with network manufacturing. The virtual resource layer, in which resources are aggregated, is added into the framework. A variety of resources is accessed into it by cloud client technology where resources are also virtualized and served. It transforms the usage of resource from many-for-one service mode distributing resources in centralized way into many for many service mode. Casati, et al.[15]built a resource framework based on task demand, and presented an intuitionistic fuzzy and resource optimize algorithm to match and search resources. The above method considered user emotion, trading experience, decaying with time and other non-functional service attributes when it estimated resources. The frameworks mentioned above not only solve the problem caused by resource heterogeneity and technology variety, but also solve the cooperation of resources. These frameworks are scalable and pay more attention to theoretical research of service selection. However, resource services are dynamic, non-real-time and autonomy for RSP in Cloud, which are not mentioned in the models and frameworks above. Thus, the practicability and universality of them are insufficient.

In summary, with the characteristics of Cloud, the resource characteristics in Table 1 can be got. The resources in Cloud may be provided by different RSP, so they are wide-area distributivities, heterogeneities and dynamics. Resource management on cloud (RMC) cannot control resources completely nor predict the resource states. Further, the heterogeneities of resource complicate the resource management. That’s why it is difficult to manage the Cloud resources and tasks by previous network resource management mode. The above researches have proved that encapsulating resource in service can mask heterogeneity, distributivity, diversity and other problems caused by the different type of resources provided by RSP. Thus, the difficulty of selecting and scheduling resources algorithm is reduced efficiently. However, in practice, without considering private characteristics of resource, resource service ability cannot be fully displayed and resource view is uncompleted. Consequently, the resource optimization will not be realized completely and the ideal result cannot be reached. This paper does researches on the content in Table 1 and puts forward a scalable resource management architecture, in which RSP can choose resource attributes by their own demands, build resource models, and reduce the difficulty of management and schedule resources optimally by related algorithms.

Table 1 Analysis of resource characteristics in the cloud

2 Resource service model and resource management architecture

2.1 Resource attributes analysis

Knowing the resource attributes well in applications is the key of building a resource service model. As shown in Table 2, this paper lists attributes of several types of common resource in logistics transportation. The attribute set with abundant semantics can distinguish all characteristics of each resource, which benefits delicacy management and shows the heterogeneity of different resources. But in practice, if there are many types and a great number of resources, the complexity of management will rise up and the information extraction will become difficult. When matching resource’s ability with a service demand, it will be difficult to get result due to too many input data. Thus, this management method is only adaptive when types of resource are insufficient. It is not suitable in Cloud with a lot of resources.

In order to control the complexity of management and computation, the resource attributes are divided into different types in the paper. As shown in Table 2, every type of resource has the identification, name, position and other attributes after getting rid of some special adjunct words. Getting them as common attributes of Cloud resource can help resource to register in Cloud easily. Adding the special attributes that make resources different from others into RSP self-management system can reduce the complexity of public management. Optimization choice of resource is based on the capability attributes. Simply by controlling these attributes, services and interests of resources can be gained. It is the base of resource service and the focus of both resource sharing in RMC (the resource information opened) and self-management (the resource information not opened). As a main function of RMC, RSP should open some administrator privileges to realize resource sharing. Here resources are classified as public attribute, private attribute and capability attribute. The attribute classification is helpful for solving distributive heterogeneity resource’s involvement, sharing, resource self-management and other problems.

Table 2 Resource attribute analysis

By further processing the attributes, the Cloud resource management can be supported better, such as getting rid of the resource identification of public resource, emphasizing resource type and capability attribute, as shown in Table 3. The resource type is always described as a tree that is easy to search for. After aggregating capability attribute according to types, the rage of their value will become a continuous capability interval, such as the interval of van loading capability is 0≤w≤20t, including van loading 4t, 8t, 16t and 20t. The coordination rule of resources is easier to formulate. For example, diver+van = transport service etc.. Besides, there are more advanced resource coordination composition, e.g. transport service + loading service = distribution service. Although these compositions are not final resource scheduling or task arrangement, these rules filter out a lot of mistakes to reduce the computation cost.

2.2 Resource service model (RSM)

Although attribute classification can deduce the resource cooperative rules, it cannot resolve the conflicts between self-management and sharing. Here taking the management model of time-shared system for CPU as reference, introducing resource calendar to monitor the service time of resource for inside and outside enterprises can solve the problem above. Thus, the resource service model is defined as the following.

(1) Resource Meta Model. RMM={G, P, C, RT, RE, F}, where G is resource general model, which is a common service attribute set owned by every resource; P is the resource private model, which is the set of private attribute belonging to every different resource; C is the resource calendar, which is composed of a serious of customizable time windows and can restrain RE; RE is a resource service capability attribute set. RT is a resource type, which is a resource classification tree oriented to different fields and can restrain G and P. F can restrain and customize P and RE to ensure the content shown to outside.

(2) Resource General Model. G= {(g, fg, RID, R_Name, R_Location, R_Status, t, RSP)|g= fg(rid, R_Name, R_Location, R_Status, t, RSP), t∈T, fg∈F}。Resources are integrated into the Cloud by G, which identifies resource individual by rid including name, position, RSP, state, type and other semantics. In order to ensure that a resource can be identified, it cannot be customized but inherited. RSP can expand G according to their own demands; fgis the operating method of resource attributes.

Table 3 the regulation and collaborative model derived from attribute and classification

(3) Resource Private Model. P={(t, A, a, fp)|a=fp(A, t), a∈A, t∈T, fp∈F}, where A=(a1,a2,…, an) means that t type resource has n different private attributes. RSP can customize resource private attributes by fp. RSP should inherit and expand P.

(4) Resource Calendar. C={(cg, ai, bi, g, fc)|cird=fc(ai, bi, g), and ai

(5) Resource Type Tree. RT={(T,R,rootk,t,ft)|t=ft(rootk,T,R) and ∀i, j, i≠j, Ti∩Tj=Ø, Ri∩Rj=Ø}, where T is a set of resource types, Tiand Tjare any two partitions of T, R is the relation among type elements, Riand Rjare any two partitions (the adjacency matrix or adjacency list) of R and RT are the resource type of the domain. The resource classification is unified and non-duplicated in the same field. ftis the operation to the resource tree which can improve the efficiency of resource search.

(6) Resource Service Capability. RE={(g, E, cg, t, ec, fe)| ec=fe(g, E, cg, t), e∈RE, g∈G, c∈C, t∈T, fe∈F}, where E={E1, E2, E3,…, En}, shows that it can describe resource capability from multi-dimension. ecmeans the service ability provided by g and is obtained by fein the time window cg, where the service ability varies with time period.

Here shows the above definitions and their relations by a UML class chart. As shown in Fig.1, RMM is composed of G, P, C, RT and RE. The five parts restrain and depend on each other to form a complete resource management view, namely resource service model (RSM). Different resources have their own special attributes and service abilities. Thus RT can restrain RE and P in a certain extent and help RSD to find resources they need and help RSP to manage resources. The formation of RT is related to the field and generally a tree structure. In general, the type is defined in the xml file based on ontology analyzed by RT engine in order to provide more flexible definition way, and classified according to the system standard, for example, the ship classification in Fig.2. There is no further discussion to this point. The service provided by resource at different time may be different. Sometimes the resource provides service for inside and sometimes for outside. Even though a resource is totally rented for outside, it still needs some maintained time. Thus, the resource calendar restrains it. The basic content of RSM is shown in the left part of Fig.1.

In order to satisfy the diversity demands of tenants for resource management, RSM provides customizable and extensible functions. Tenants can expand and inherit

Fig.1 Resource service model

Fig.2 Ship classification

P and RE and customize the related attributes and operation by fp(A) and fe(E). G is the identification by which the system recognizes resource. It is the basic content, which can only be inherited and expanded but can be modified arbitrarily. In the same field, the resource management is better to be built in the united classify system. Thus, the expansion of RT mainly concentrates on the expanding and contracting of data entries and branches, but not on expansion and rebuilding of the structure and engine. C is the complementary time similar to RT. The resource does not provide service outside when the internal is busy. In other words, the resource provides service outside only when internal is free. As shown in Fig.1, the components in the C dashed rectangle is the RSM expanding region. The diverse customized and expanding technologies enrich the autonomous function of the tenant to resource. At the same time, it can also be used to improve and perfect RSM itself.

The only external interface of resource management is resource capability, which is the main aim of resource management that resource can complete its designated tasks. Since the task management is not the main focus of this paper, the task is roughly divided into two parts: task and task management. The task is the business activity satisfying certain conditions, e.g. transportation commission. The task management is to monitor the task, e.g. the implementation of task. UOB-T business reflects the implementation of the task, e.g. the assignment bill, and UOB-J management is the result of executing the task such as back to single about task. Both of two activities need the participation of resources. Besides, evaluating components Ev can be introduced into the system which can gather the task executing information to evaluate the task execution and transmit the evaluate result to RSP to improve the task management state. What’s more, RSP can also customize Ev to get the demanded data.

2.3 Resource service management architecture

RSM describes the most essential characteristics of resources. As shown in Fig.1, it shows the most basic service relation between the resource and the task. Although it deals with heterogeneous resource introduced by attribute extraction, supports resource diversity management by customizability and expansibility, and completes resource sharing and self-management, resource distribution, state tracking, non-real time scheduling and other problems by the resource classification and the calendar, however, as mentioned in Section 2.1, when the type and number of resource are large, the complexity of management is still very high and the cooperation of different resources is still difficult. The main reason why the above problems cannot be completely solved is that the resource management is underlying. Thus, the resource is encapsulated as the service based on RSM and the resource service management architecture (RSMA) can be reached, as shown in Fig.3.

(1) Resource providing layer. It is composed of the physical resources provided by RSP and it is the task execution layer. RSP can complete the five parts of information required by RSM to transform resources to virtual resource to be scheduled by RMC.

(2) Resource aggregation layer. Dividing resources in different type to form an elastic resource aggregation layer, as mentioned in Section 2.1, forms a continue service ability valued range, reduces the difficulty of selecting service, designing algorithm and coding. It can be seen from the definition of RSM that no constraint of region, RSP or RSD and permitting a lot of resources being introduced into the system, it ensures enough resource supply[18]during task assigned process. In order to cooperate with the distributed self-management, the system can regulate the resource to keep balance automatically by setting resource calendar and service ability provided outside.

(3) Resource service layer. One or more resources can be combined into an integeral with more capability by composing rules. For example, a driver and a forklift can be combined into a loading service with 1t lifting ability and 90cm lifting height and a driver and a truck can be combined into a transporting service with 10t load and 70cm loading height. Then the loading service and the transportation service can be connected to form a distribution service. The output service ability will be restrained mainly by some kind of resource. In this example, the restraint of distribution service is the load of the truck, 10t. The distribution time is equal to loading time + transporting time. However, when the transporting time is much longer than the loading time, the loading time can be ignored. The loading service is supplementary to the transportation service. The mode can reduce the complexity of computation (for details, see Section 3). Here, it is also allowed to package resource into service to enter into the system. In other words, it can access into the system crossing two different layers.

(4) Service flow layer. Resource services can be composed to form a fully functional service by the task demand. It may include non-resource service. Because of the uncertainty of tasks, it shall be formed dynamically.

(5) Service demand layer. In this layer, the user can divide a task into a serious of subtasks. On one hand, it can choose a related flow model from the service flow layer. On the other hand, it is also possible to choose resource services and compose them to form the service flow dynamically according to task demand.

Fig.3 Resource service architecture

The selection of service resource is a process across five layers and top-down: task decomposition→flow/service selection→service binding→resource binding→resource execution. The optimization of service flow layer is the optimization of service route. And the optimization of service layer is eventually the optimization of resource selection.

2.4 Resource service optimal scheduling model

After encapsulated in several levels, the scheduling resources will be simplified and the cooperation among resources will be easier. In RSMA, there are four ways to select resource services: model matching, optimal scheduling based on route, service selection, and optimal scheduling based on quality. The model matching is that the subtasks are composed to form an executive flow and then matched with the service flow in the service layer. So it can be abstracted as similarity judgment of graph. The optimal scheduling based on quality can get the information of QoS by the Ev components mentioned in RSM to optimize itself. There have been many related researches. Further discussion will not be provided due to the limitations of space. Service choices refer to finding related service from resource service layer directly when the tasks or the subtasks are relatively simple. This paper provides a general route optimization algorithm with time window (GROATW) about optimal scheduling based on route.

Suppose completing a task needs n steps and the state of every step is called a task node. The task execution forms a directed graph G which is composed of n task nodes, original node 0 and terminal node n+1. The set of task nodes is TN, N=|TN|+2. From node i to j, the standard time consumption is tijand the cost consumption is wij. Task node i has a time window [ai, bi] and s is the beginning of task time, the task requires service capability qi. According to the resource calendar, resource g has the time window like [ag,bg]. Let xijgrepresent the service provided by resource g from node i to node j. If the value is only 1 or 0, it is arrived or not. Otherwise, it represents the service capability value provided by the resource. According to the definition above, the mathematic model aiming to optimize the cost shall be:

(1)

This method is generic. When the variables are given more meanings in practice, the expression can be simplified. In the expression, Constraint Eq.(2) shows that every node can only be visited one time. The inequation (3) shows that the resources are called satisfy constraints. Eqs(4), (5) and (6) ensure that the task starts from original node, executes through every sub-node and finishes at the terminal node. The inequation (7) shows that the executing time constrains the same resource at different task nodes. In other words, the task that is incomplete at a node cannot arrive at another node. The inequation (8) shows the time that the resource executes the task should satisfy the constraint of resource time window. The inequation (9) is the time that the resource executes the task should satisfy the constraint of task time window. This model can provide for a variety of changes in practice. For example, let x denote the weight between task nodes, Eqs(2), (4), (5) can be omitted. If service demand is calculated dynamically formula (3) can be expanded. If it is used as resource scheduling algorithm for the enterprise internal, the resource time window can be removed. When all the resources are vehicles, it can be seen as vehicle routing problem with time window (VRPTW). It becomes vehicle routing problem (VRP) without the time window. If there is only one vehicle, the model will be the travelling salesman problem (TSP). Because the first two variations of this algorithm are more practical, it will be analyzed in the experimental part.

3 Experimental results and analysis

3.1 Background of experiment

In international trade, there is usual imbalance of trade between two countries because of their economic gap. There are different demands of empty containers from both sides. Therefore, empty container transportation between any two container yards (CYs) is demanded. A country is taken as a district. CYs maybe lie in the same district or in the different districts. Goods are transported between CYs in different districts by ship and in the same district by vehicle. Obviously, each transportation process is the above subtask node. To complete a task of empty container transportation, many resources are demanded to participate, such as ship, container, container truck, forklift, crane, driver, worker, sailor, etc. After they have been registered into RSMA, they can compose many services according to the rules and are placed in the resource service layer, as mentioned in Section 2. There are two ways to schedule them optimally, in which one is that field experts make the service flow in advance and then match these service flow with the task flow by the rule, the other is that the above service can be chosen to complete a subtask node directly by optimization algorithm. The latter is used as an example to discuss in the text.

Take a 20-foot container as a transmission extension unit (TEU). For the consideration of the transportation cost, the number of empty containers carried by ships is usually not the largest deadweight, but the residual load after loading the heavy containers, and it varies according to different voyages, which is expressed as ek=fe(g.rid, E, c, t), where g.rid is the voyage number, c is shipping schedule, k∈c,as shown in Table 4. Double-district is bidirectional traveling,Empty container demand is decided by the available margin/shortage amount of each voyage and each CY, as shown in Table 5.

Table 4 Shipping schedule

4 ships are divided into eight voyages. In the international marine logistics, shipping service time window is the hard time window, and can’t be changed easily. So ships are the core of the service resources, while the loading service and land carriage service in the same district serve as the assistance resource service, scheduling is comparatively flexible, as a result this experiment uses shipping schedule as the prime resource calendar.

Table 5 Available margin/shortage amount of empty container all voyages and CYs (TEU)

3.2 Optimal scheduling model on international marine logistics

Because the eastward voyage is before the westward voyage for the same voyage No., containers can be scheduled from the eastward to the westward, but the contrary case does not exist. Furthermore, due to the voyage No. increasing along with time, there is no case that scheduling container is from big voyage No. to the small voyage No.. Therefore, the voyage direction’s decision variable is a two-dimensional triangular matrix, if combined with the CY No., the decision-making variable is four-dimensional variable xijkl. xijklcan be interpreted as the number of scheduling containers from CY i in shipment date k to CY j in shipment date l. Because vehicle and human resources’ calendar is software time window, it must meet the requirements of shipping schedule. Here xijklcan also refer to land resource scheduling. This kind of design will package the loading service with the shipping and land carriage service respectively in the resource service layer, so that the resource No. does not have to appear in the decision-making variable x, but can also reflect the characteristics of multiple-resource scheduling. wijis transportation cost here, using the Yuan/TEU as standard service equivalent, then objective function changed from (1) to (10), matched with the first variation in Section 2.4, then formulas (2), (4) (5) are removed. Formula (12) shows the upper bound of scheduled empty containers in CY k. Formula (7) changes formula (13) while the former omits resource No.. The task time window matches with the shipping schedule. The vehicle and human resource time window must follow the shipping schedule, both formulas (8) and (9) are merged to (14) which explains that the total time of many scheduling containers on land is no longer than the shipment date, where K is transportation time in the same district. Eventually, the double-district multi-ship-scheduling multi-container-yard empty containers model, which is evolution of resource allocation general model, is as follows:

(10)

3.3 Solving

When solving the transportation problems with complex constraints, genetic algorithms (GA) is an ideal choice. Then let’s find the optimal solution of the above equation.

(1) GA coding

This paper uses decimal encoding. Multi-ship-scheduling and multi-container-yard require using four-dimensional matrix’s chromosome encoding, and Eq.(15) shows the allocation matrix of scheduling empty containers problem of six yards and eight shipment dates.

(15)

where Xprepresents the pth chromosome, and xijklis the corresponding decision variable.

(2) The calculation of fitness

An objective function is used to evaluate the value of Xp’s fitness, Eq.(16) is obtained by Eq.(10).

(16)

(3) The process of initialization

A group of decision variables xijkls can be obtained by generating the subscript of each xijklrandomly. Referring to the direction dijlimit (i.e., dij=0 indicates the same district, dij= 1 denotes the direction from east to west and dij=-1 from west to east), the group of xijkls can be filtered by formulas (11) to (14) in the model, and hereby the initial populations that satisfy the initial constraints can be produced.

(4) Crossover operator design

Step 1: Construct two temporary matrix D=(dijkl)mmnnand R=(rijkl)mmnn:

(17)

(18)

Matrix D is the average integer value of the parents. Matrix R judges if the average value of the parents is integer. The following is the relation between D and R:

i, j=1,2,…,m; k, l=1,2,…,n (19)

i, j=1,2,…,m; k,l=1,2,…,n (20)

Step 2: R is divided into two matrix

R=R1+R2

(21)

i, j=1,2,…,m; k,l=1,2,…,n (22)

i, j=1,2,…,m; k,l=1,2,…,n (23)

i, j=1,2,…,m; k,l=1,2,…,n (24)

i, j=1,2,…,m; k,l=1,2,…,n (25)

Step 3: generate two descendants X’1and X’2

(26)

(27)

(5) Mutation operator design

The followings are three steps of variance:

Step 1: First, construct a sub-matrix matching with the previous generation chromosomes. Second, to choose {i1,…,ir},{j1,…, js}, {k1,…,kt}, {l1,…,lo} randomly to build a sub-matrix (r×s×t×o) of Z={zijkl}, where {i1,…ir}, {j1,…, js} ({1,2,…,m}, and 2≤r, s≤m, {k1,…,kt}, {l1,…,lo}⊂{1,2,…,n}, and 2≤t, o≤n; zijklget value from element with subscript ijkl in its parent matrix.

Step 2: Reassign a sub-matrix of transporting container amount. Scheduling of empty container amount and demanding empty container amount in the sub-matrix are calculated by the following:

i=i1,…,ir; k=k1,…,kt(28)

j=j1,…,js; l=l1,…,lo(29)

Step 3: The elements of the parents-matrix are replaced by the new elements of the reassignment sub-matrix Z and then the descendants are got.

(6) The simulation of multi-ship-scheduling empty container transportation model in double-district

Assuming there are six container yards between the ship route of district M and N, where three CYs are in zone M, and the other three in zone N. Transporting empty container costs per TEU between any two CYs are shown in Table 6. Costs of the same district is mainly composed of land transportation and loading and unloading charges, the costs of transportation between different partitions are mainly composed of the inspection fee, disinfection fee, handling fee and agency fee, what’s more, importers and exporters are all to be charged.

Table 6 Transporting empty container Cost wijbetween any two CYs Yuan/TEU

The empty container transportation direction between any two CYs is as shown in Table 7(the left of ‘/’), where 0 represents two yards in one same district, and the empty container needs not to be transported by ship. 1 indicates that the CY of line-number transporting to a CY of row-number need to go through the voyage eastward. And -1 indicates that the CY of line-number transporting to a CY of row-number need to go through the voyage westward. The time cost of empty container transportation between any two CYs in the same district is as shown in Table 7(the right of ‘/’), where # represents two yards in different district, and the number represents the time cost of land transportation between two CYs.

Container margin/shortage amount of each yard in eight different shipping schedules is shown in Table 5.

Table 7 The direction matrix/ the time matrix hour

Under these input conditions above, GA parameters are set as: crossover probability is 0.8, mutation probability is 0.1, and the population size is 50. The generation of evolution is found better at around 300. During this simulation, optimal fitness appears in 283 generations, transportation cost is 156,300 Yuan. Populations’ average transportation cost is 338,631.1 Yuan. The mean-square deviation is 59048.5, as shown in generations of fitness curves in Fig.4.

Fig.4 Generations of fitness changing curve

4 Conclusion

According to the characteristics of the application resource management in Cloud, a resource model RSM is constructed. Based on it, a resource service management architecture RSMA is established, and a general resource scheduling model GROATW is introduced into the RSMA. Finally, they are applied successfully to double-district multi-ship-scheduling multi-container-yard empty containers transporting and solved by GA. The application proves the feasibility and validity of RSM. This application is related to several different CYs and shipping companies, corresponding with the characteristics of the RMC. The RSMA shows good openness and scalability and achieves a seamless integration of the distributed self-management and centralized scheduling. It can monitor and schedule application resources dynamically through the RSMA, achieve resource sharing and promote collaboration between enterprises to improve their overall competitiveness. For the next step, further study will be done to accumulate data for analyzing, and improve data analysis algorithms by means of the model’s openness and scalability, promote the further evolution of analysis and optimization models.

[1] Mell P, Grance T. The NIST definition of cloud computing. National Institute of Standards and Technology, 2009, 53(6): 50

[2] Doelitzscher F, Sulistio A, Reich C, et al. Private cloud for collaboration and e-Learning services: from IaaS to SaaS. Computing, 2011, 91(1): 23-42

[3] Buyya R. Economic-based Distributed Resource Manage-ment and Scheduling for Grid Computing: [Ph. D dissertation]. Melbourne: Monash University, 2002. 30-35

[4] Lassila O, Swick R R. WD-rdf-syntax-19981008 Resource Description Framework (RDF) Model and Syntax Specification. US: W3C, 1998

[5] McBride B. Handbook on Ontologies. Berlin: Springer Berlin Heidelberg, 2004. 51-65

[6] McCuinness D L. Ontologies come of age. In: Spinning the semantic web: bringing the World Wide Web to its full potential. Cambridge: MIT Press, 2002. 171-194

[7] Peng J, Zhang X, Lei Z, et al. Comparison of several cloud computing platforms. In: Proceedings of the 2009 IEEE International Symposium on Information Science and Engineering, Shanghai, China, 2009. 23-27

[8] Wang Z J, Xu X F. Bilateral resource integration service mode for value innovation. Computer Integrated Manufacturing Systems, 2009, 15(011): 2216-2225 (In Chinese)

[9] Buyya R, Yeo C S, Venugopal S. Market-oriented cloud computing: vision, hype, and reality for delivering it services as computing utilities. In: Proceedings of the 10th IEEE International Conference on High Performance Computing and Communications, Dalian, China, 2008. 5-13

[10] Zhang J X. Survey of research progress on cloud computing. Application Research of Computers, 2010, 27(2): 429-433 (In Chinese)

[11] Keahey K,
Figueiredo R, Fortes J, et al. Science clouds: Early experiences in cloud computing for scientific applications. Cloud computing and applications, 2008 (2008): 825-830

[12] Li Q, Zheng X. Research survey of cloud computing. Computer Science, 2011, 38(4): 32-37 (In Chinese)

[13] Li B H, Zhang L, Wang S L, et al. Cloud manufacturing: a new service-oriented networked manufacturing model. Computer Integrated Manufacturing Systems, 2010, 16(1): 1-7 (In Chinese)

[14] Li B H, Zhang L, Ren L, et al. Further discussion on cloud manufacturing. Computer Integrated Manufacturing Systems, 2011, 17(3): 449-457 (In Chinese)

[15] Casati F, Ilnicki S, Jin L J, et al. eFlow: A platform for developing and managing composition e-services. In: Proceedings of the IEEE Academia/Industry Working Conference on Research Challenges, New York, USA, 2000. 341-348

[16] Czajkowski K, Foster I, Karonis N, et al. A resource management architecture for metacomputing systems. In: Job Scheduling Strategies for Parallel Processing. Heidelberg, Germany, 1998. 62-82

[17] Raman R, Livny M, Solomon M. Matchmaking: Distributed resource management for high throughput computing. In: Proceedings of the IEEE International Symposium on High Performance Distributed Computing, Chicago, USA, 1998.140-146

[18] Xu X. From cloud computing to cloud manufacturing. Robotics and computer-integrated manufacturing, 2012, 28(1): 75-86

Zhang Xiaodong, born in 1971. He received his M.S. degree in School of Computer Science and Technology, Harbin Institute of Technology. His research focuses on software service engineering and service computing, cloud computing.

10.3772/j.issn.1006-6748.2017.01.014

①Support by the National Key Technology Research and Development Program of China (No. 2012BAA13B01, 2014BAF07B02), the National Natural Science Foundation of China (No. 61273038), Natural Science Foundation of Shandong Province (No. ZR2015FM006), Science and Technology Major Project of the Ministry of Science and Technology of Shandong Province (No. 2015ZDXX0201B02).

②To whom correspondence should be addressed. E-mail: z_xiaodong7134@163.com Received on Nov. 2, 2015