CN104717258A - Data transmitting method and system - Google Patents

Data transmitting method and system Download PDF

Info

Publication number
CN104717258A
CN104717258A CN201310689192.7A CN201310689192A CN104717258A CN 104717258 A CN104717258 A CN 104717258A CN 201310689192 A CN201310689192 A CN 201310689192A CN 104717258 A CN104717258 A CN 104717258A
Authority
CN
China
Prior art keywords
accessor
connection device
message
management equipment
operation requests
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.)
Granted
Application number
CN201310689192.7A
Other languages
Chinese (zh)
Other versions
CN104717258B (en
Inventor
朱旭琪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Cloud Computing Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201310689192.7A priority Critical patent/CN104717258B/en
Publication of CN104717258A publication Critical patent/CN104717258A/en
Application granted granted Critical
Publication of CN104717258B publication Critical patent/CN104717258B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/20Network architectures or network communication protocols for network security for managing network security; network security policies in general

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Small-Scale Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

The embodiment of the invention provides a data transmitting method and system, and relates to the field of communication. The data transmitting method and system are used for reducing potential safety hazards of an SDN and improving the safety of the SDN. The system comprises a first accessor, management equipment and a second accessor, wherein the first accessor is used for receiving operation request information transmitted by an application server and forwarding the operation request information when target connecting equipment is not connecting equipment corresponding to the first accessor, the management equipment is used for determining that the accessor corresponding to the target connecting equipment is the second accessor according to the prestored corresponding relation between equipment identification of the target connecting equipment and the accessor and transmitting the operation request information to the second accessor, and the second accessor is used for transmitting the operation request information to the target connecting equipment. The data transmitting method and system are suitable for the scene of transmitting an operation request to the corresponding connecting equipment in the distributed SDN.

Description

A kind of data transmission method for uplink and system
Technical field
The present invention relates to the communications field, particularly relate to a kind of data transmission method for uplink and system.
Background technology
A SDN(Software Defined Network, software defined network) network forms primarily of two kinds of equipment, comprises switch and SDN controller.Wherein, switch primary responsibility is based on the data processing of stream table, forwarding and state collection; SDN controller mainly carrys out the distribution of deal with data resource according to application program, maintaining network topological sum state information etc.Wherein, application program can be local application, also can be remote application.SDN controller is the core devices that SDN realizes, the OS(OperatingSystem in the effect of SDN controller and computer, operating system) similar, NOS(Network OperatingSystem can be referred to as, network operating system).
When the switch network scale of SDN controller management is too large, the processing expenditure of single SDN controller is very large, so introduce the thought of distributed SDN, namely the switch in supervising the network is carried out by deployment multiple stage SDN controller, whole network is divided into different territories, in each territory, dispose one or more NOS, make the load on each NOS suitable, also the service response of whole network is controlled simultaneously.
In the technology that data send under existing distributed SDN scene, when a certain application program that a certain equipment runs needs switch transmit operation request, first, this equipment needs the NOS known in advance belonging to switch, then, the NOS of access control switch, and then this operation requests is sent to switch by NOS thus.Namely equipment needs the division information first knowing SDN for this reason.After can pre-setting the division information of SDN, the division information of SDN is informed this equipment in advance in the art existing, thus ensure this equipment the most at last operation requests be sent to switch.
State in the process that data send under distributed SDN scene in realization, the division information of SDN need inform the equipment running a certain application program in advance, if this application program is developed by incredible third party, then cause the division information of SDN may be known by incredible third party's exploitation, thus make SDN there is certain potential safety hazard, reduce the fail safe of SDN.
Summary of the invention
The embodiment provides a kind of data transmission method for uplink and system, for reducing the potential safety hazard of SDN, improving the fail safe of SDN.
For achieving the above object, embodiments of the invention adopt following technical scheme:
First aspect, embodiments provide a kind of distributed software define grid SDN system, described system comprises the first accessor, management equipment and the second accessor, and wherein, described first accessor, for receiving the operation requests message that application server sends; Wherein, the device identification of target connection device is carried in described operation requests message; Described first accessor, time also for not being connection device corresponding to described first accessor at described target connection device, forwards described operation requests message to described management equipment; Described management equipment, for according to the corresponding relation between the device identification of the described target connection device preserved in advance and described accessor, determines that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is sent to described second accessor; Described second accessor, for sending to described target connection device by described operation requests message; Wherein, described second accessor is the controller managing described target connection device.
In the first possible implementation of first aspect, described first accessor comprises: the first controller.
In conjunction with first aspect, in the implementation that the second of first aspect is possible, described first accessor comprises: load equalizer.
In conjunction with first aspect, or the first to the second of first aspect any one the possible implementation, in the third possible implementation of first aspect, described first accessor, specifically for obtaining the corresponding relation between the device identification of the described target connection device preserved in advance in described management equipment and accessor, and according to described corresponding relation, determine that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is added in the request list of described second accessor stored in described management equipment.
In conjunction with the third possible implementation of first aspect, in the 4th kind of possible implementation of first aspect, whether described management equipment, change specifically for the request list detecting described second accessor; If detect, the request list of described second accessor changes, then to described second accessor transmit operation request message.
In conjunction with first aspect, or the first to the second of first aspect any one the possible implementation, in the 5th kind of possible implementation of first aspect, described first accessor, specifically for the device identification according to described target connection device, described operation requests message is added into the request list of the described target connection device stored in management equipment.
In conjunction with the 5th kind of possible implementation of first aspect, in the 6th kind of possible implementation of first aspect, whether described management equipment, change specifically for the request list detecting described target connection device; If detect, the request list of described target connection device changes, then to described second accessor transmit operation request message.
In conjunction with the 3rd to the 6th any one possible implementation of first aspect, in the 7th kind of possible implementation of first aspect, described management equipment, specifically for sending the first Trigger message to described second accessor; Described second accessor, specifically for receiving described first Trigger message that described management equipment sends, and determines whether carry described operation requests message in described first Trigger message; When determining not carry described operation requests message in described first Trigger message, send the first request message to described management equipment; Wherein, described first request message is the message for obtaining described operation requests message; Described management equipment receives the first request message that described second accessor sends; And described operation requests message is sent to described second accessor; When determining to carry described operation requests message in described first Trigger message, obtain in described first Trigger message the described operation requests message of carrying.
Second aspect, embodiments provide a kind of data transmission method for uplink, described method is applied in distributed software define grid SDN system, described system comprises multiple accessor and at least one management equipment, wherein, the corresponding multiple connection device of each accessor, described method comprises: the first accessor receives the operation requests message that application server sends; When target connection device is not connection device corresponding to described first accessor, forward described operation requests message to described management equipment; Wherein, the device identification of target connection device is carried in described operation requests message; Described management equipment, according to the corresponding relation between the device identification of the described target connection device preserved in advance and described accessor, determines that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is sent to described second accessor; Described operation requests message is sent to described target connection device by described second accessor; Wherein, described second accessor is the controller managing described target connection device.
In the first possible implementation of second aspect, described first accessor forwards described operation requests message to described management equipment and comprises: described first accessor obtains the corresponding relation between the device identification of the described target connection device preserved in advance in described management equipment and accessor, and according to described corresponding relation, determine that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is added in the request list of described second accessor stored in described management equipment.
In conjunction with the first possible implementation of second aspect, in the implementation that the second of second aspect is possible, described operation requests message sends to described second accessor to comprise by described management equipment: whether the request list that described management equipment detects described second accessor changes; If described management equipment detects that the request list of described second accessor changes, then described management equipment is to described second accessor transmit operation request message.
In conjunction with the first possible implementation of second aspect, in the third possible implementation of second aspect, described first accessor forwards described operation requests message to described management equipment and comprises: described operation requests message, according to the device identification of described target connection device, is added into the request list of the described target connection device stored in management equipment by described first accessor.
In conjunction with the third possible implementation of second aspect, in the 4th kind of possible implementation of second aspect, described operation requests message sends to described second accessor to comprise by described management equipment: whether the request list that described management equipment detects described target connection device changes; If described management equipment detects that the request list of described target connection device changes, then described management equipment is to described second accessor transmit operation request message.
In conjunction with second aspect, or first to fourth of second aspect any one possible implementation, in the 5th kind of possible implementation of second aspect, described management equipment comprises to described second accessor transmit operation request message: described management equipment sends the first Trigger message to described second accessor; Described second accessor receives described first Trigger message that described management equipment sends, and determines whether carry described operation requests message in described first Trigger message; If described second accessor is determined not carry described operation requests message in described first Trigger message, described second accessor sends the first request message to described management equipment; Wherein, described first request message is the message for obtaining described operation requests message; Described management equipment receives the first request message that described second accessor sends; And described operation requests message is sent to described second accessor; If described second accessor is determined to carry described operation requests message in described first Trigger message, described second accessor obtains the described operation requests message of carrying in described first Trigger message.
Embodiments provide a kind of data transmission method for uplink and system, first accessor is after the operation requests message receiving application server transmission, when determining that target connection device is not connection device corresponding to the first accessor, operation requests message is forwarded to management equipment, now, management equipment is according to the corresponding relation between the device identification of the target connection device preserved in advance and accessor, determine that the accessor that target connection device is corresponding is the second accessor, and operation requests message is sent to the second accessor, and then second accessor the operation requests message received is sent in target connection device.Like this, in SDN system, can by the corresponding relation between the equipment identification information of target connection device and accessor, be the division information of SDN, be kept in management equipment, operation requests message is forwarded according to the division information of this SDN by management equipment, thus complete application server and be the equipment run application, to the operation of target connection device, and without the need to the division information of SDN being informed in advance the equipment run application in process operation requests message being sent to target connection device, and then decrease the potential safety hazard of SDN, improve the fail safe of SDN.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme of the embodiment of the present invention, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
The structural representation of a kind of distributed software define grid SDN system that Fig. 1 provides for the embodiment of the present invention;
The schematic flow sheet of a kind of data transmission method for uplink that Fig. 2 provides for the embodiment of the present invention;
The schematic flow sheet of the another kind of data transmission method for uplink that Fig. 3 provides for the embodiment of the present invention.
The example schematic of a kind of data transmission method for uplink that Fig. 4 provides for the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
Embodiments provide a kind of distributed SDN(Software DefinedNetworking, software defined network) system, as shown in Figure 1, described system comprises the first accessor 101, management equipment 102, the second accessor 103.Wherein,
Described first accessor 101, for receiving the operation requests message that application server sends.
Wherein, the device identification of target connection device is carried in described operation requests message.
Described first accessor 101, time also for not being the connection device of described first accessor 101 correspondence at described target connection device, forwards described operation requests message to described management equipment 102.
It should be noted that, the application program that application server runs needs to operate target connection device, the application server transmit operation request message now run application.For the first accessor 101, application program can be divided into local application and remote application.Wherein, local application refers to the application program run by the first accessor 101 oneself, and now the first accessor 101 is application server.Remote application refers to the application program run by the equipment except the first accessor 101, and now, the equipment run application is application server, can be called far-end application server.
Concrete, if when application program operates in the first accessor 101, now the first accessor 101 is application server, the operation requests message that first accessor 101 receives application server transmission refers to, the first accessor 101 receives the operation requests message of the module transmission himself run application.Now, the first accessor 101 can be the first controller.
If when application program operates in the equipment except the first accessor 101, now relative to the first accessor 101, application server is far-end application server, then the first accessor 101 receives the operation requests message that application server sends.Now, the first accessor 101 can be that load equalizer may also be the first controller.
Wherein, load equalizer is independently equipment, for managing at least one controller in SDN controller cluster.First controller can be a controller at least one controller in SDN controller cluster.First controller can manage other controllers in SDN controller cluster, now the first controller is called Master NOS(Master Network OperatingSystem, master network operating system).Certainly, the first controller also can not have the function of other controllers in management SDN controller cluster.
It should be noted that, when the first controller does not have the function of other controllers in management SDN controller cluster, illustrate in SDN controller cluster, not there is the controller of other controllers in management SDN controller cluster.If in SDN controller cluster, have the controller of other controllers in management SDN controller cluster, then namely the first controller has the controller of other controller functions in management SDN controller cluster for this reason.
It should be noted that, load equalizer, only for managing at least one controller in SDN controller cluster, does not have the function run application.Be when the first accessor 101 is application server, the first accessor 101 can only be the first controller.
It should be noted that, in embodiments of the present invention, a SDN controller cluster comprises at least one and has run NOS(Network Operating System, network operating system) controller.Can by run NOS controller referred to as NOS or controller.
If application server is far-end application server, and described first accessor 101 comprises: load equalizer, then load equalizer, for receiving the operation requests message carrying the device identification of target connection device that far-end application server sends, and because load equalizer does not have corresponding connection device, so application server needs the target connection device of operation not to be the connection device that load equalizer is corresponding, then load equalizer, also for the operation requests received message being forwarded in management equipment 102.
If application server is far-end application server, and described first accessor 101 comprises: the first controller, then the first controller, for receiving the operation requests message carrying the device identification of target connection device that far-end application server sends, and when target connection device is not connection device corresponding to the first controller, the first controller is also for being sent to the operation requests received message in management equipment.
It should be noted that, if load equalizer and Master NOS exist simultaneously, preferably, the first accessor 101 is load equalizer.Now, the operation requests message carrying the device identification of target connection device of application server transmission is received by load equalizer.
Concrete, the method that described first accessor 101 forwards described operation requests message to described management equipment 102 is as follows:
First method, described first accessor 101, specifically for obtaining the corresponding relation between the device identification of the described target connection device preserved in advance in described management equipment 102 and accessor, and according to described corresponding relation, determine that the accessor that described target connection device is corresponding is described second accessor 103, and described operation requests message is added in the request list of described second accessor 103 stored in described management equipment 102.
Wherein, the request list of the second accessor 103 refers to the list of each request message that the storage of setting up in management equipment is relevant to the second accessor, and request message comprises: the device identification of target connection device and corresponding operation requests message.
Concrete, described first accessor 101, specifically for obtaining the device identification of target connection device in operation requests message, and according to the device identification searching and managing equipment 102 of target connection device, the corresponding relation of the second accessor 103 recording target connection device and manage this target connection device is found in management equipment 102, and in corresponding relation, determine the second accessor 103, be the identification information obtaining this second accessor 103.And according to the identification information of the second accessor 103 obtained, in the request list of each accessor stored in management equipment 102, determine the request list of the second accessor 103, and operation requests message is added into the request list of the second accessor 103.
Second method, described first accessor 101, specifically for the device identification according to described target connection device, is added into the request list of the target connection device stored in management equipment 102 by described operation requests message.
Wherein, the request list of target connection device refers to the list of each request message that the storage of setting up in management equipment is relevant to target connection device, and request message comprises: the device identification of target connection device and corresponding operation requests message.
Concrete, described first accessor 101, specifically for obtaining the device identification of target connection device in operation requests message, and according to the device identification searching and managing equipment 102 of target connection device, find target connection device in management equipment 102 after, operation requests message is added in the request list of target connection device.
It should be noted that, operation requests message is forwarded to the method for management equipment by the first accessor 101, and can also be additive method, the present invention limit at this.
Described management equipment 102, for according to the corresponding relation between the device identification of the described target connection device preserved in advance and described accessor, determines that the accessor that described target connection device is corresponding is described second accessor 103; And described operation requests message is sent to described second accessor 103.
Concrete, the method that operation requests message is forwarded in management equipment 102 according to the first accessor by management equipment 102 is different, and the method whether detection request list changes is also different, specific as follows:
Described management equipment 102, during specifically at the first accessor 101 operation requests message being added into the request list of the second accessor 103 stored in management equipment 102, whether the request list detecting described second accessor 103 changes; If detect, the request list of described second accessor 103 changes, then to described second accessor 103 transmit operation request message.
That is, described management equipment 102, specifically for the corresponding relation between the device identification and described accessor of the described target connection device according to preservation in advance, determine that the accessor that described target connection device is corresponding is after described second accessor 103, the request list of the request list of the second accessor 103 preserved in advance and the second accessor 103 of renewal is compared, determines whether the request list of the second accessor 103 changes.If compare with the request list of the second accessor 103 of renewal the request list of the second accessor 103 preserved in advance, determine that the data in its request list have increase or delete, then determine that the request list of the second accessor 103 changes, and to the second accessor 103 transmit operation request message.
Or, described management equipment 102, during specifically at the first accessor 101 operation requests message being added into the request list of the target connection device stored in management equipment 102, whether the request list detecting described target connection device changes; If detect, the request list of described target connection device changes, then to described second accessor 103 transmit operation request message.
That is, management equipment 102, specifically for the corresponding relation between the device identification and described accessor of the described target connection device according to preservation in advance, determine that the accessor that described target connection device is corresponding is after described second accessor 103, to the request list of target connection device preserved in advance compared with the request list of the target connection device of renewal, determine that the data in its request list have increase or delete, then determine that the request list of target connection device changes, and to the second accessor transmit operation request message.
Further, described management equipment 102 is as follows to the method for the second accessor 103 transmit operation request message:
Described management equipment 102, specifically for sending the first Trigger message to described second accessor 103.Described second accessor 103, specifically for receiving described first Trigger message that described management equipment 102 sends, and determine whether carry described operation requests message in described first Trigger message, when determining not carry described operation requests message in described first Trigger message, send the first request message to described management equipment 102; Described management equipment 102 receives the first request message that described second accessor 103 sends; And described operation requests message is sent to described second accessor 103.
Wherein, the device identification of target connection device is carried in described operation requests message; Described first request message is the message for obtaining described operation requests message.
Optionally, the device identification of target connection device is carried in the first Trigger message.
It should be noted that, pre-setting in management equipment 102 when determining that request list changes, send the Trigger Function of the first Trigger message from the accessor that trend is corresponding with the request list changed.So when management equipment 102 detects that the request list of the request list that the second accessor 103 is relevant or target connection device changes, then management equipment 102 sends the first Trigger message according to the Trigger Function pre-set to the second accessor 103.
It should be noted that, the first Trigger message be management equipment 102 for notifying accessor, the request list that accessor is corresponding therewith there occurs the message of change.
Concrete, described management equipment 102, specifically for when determining that the request list of the request list relevant to the second accessor 103 or target connection device changes, send the Trigger Function of the first Trigger message according to the accessor corresponding with the request list changed from trend, send the first Trigger message to the second accessor 103.Now, the second accessor 103, for the first Trigger message that receiving management equipment 102 sends, and determines whether carry operation requests message in the first Trigger message.Operation requests message is not carried in first Trigger message if determine, the request obtaining operation requests message is then sent to management equipment 102, namely the first request message is sent to management equipment 102, now, management equipment 102, specifically for receiving the first request message that the second accessor 103 sends, and the operation requests message carrying the device identification of target connection device is sent to the second accessor 103, second accessor 103, specifically for the operation requests message carrying the device identification of target connection device that receiving management equipment 102 sends.
Described second accessor 103, specifically for when determining to carry described operation requests message in described first Trigger message, obtains in described first Trigger message the described operation requests message of carrying.
Concrete, the second accessor 103, specifically for when receiving the first Trigger message carrying operation requests message, by resolving the first Trigger message, thus obtains the operation requests message of carrying in the first Trigger message.
It should be noted that, management equipment 102 can be run the equipment of distributed management system, and also can be the equipment running shared data bank system, the present invention limit this.
Described second accessor 103, for sending to described target connection device by described operation requests message.
Wherein, described second accessor 103 is the controllers managing described target connection device.
Concrete, second accessor 103, specifically for after the operation requests message receiving management equipment 102 transmission, the device identification of target connection device can be obtained, according to the device identification of target connection device to target connection device transmit operation request message according to the first Trigger message received.Also according to resolving the operation requests message that receive, thus the device identification of the target connection device carried in operation requests message can be obtained, and then according to the device identification of target connection device to target connection device transmit operation request message.
Further, described first accessor 101, also for determining that whether described target connection device is the connection device of described first accessor 101 correspondence.
Concrete, now, first accessor 101 is the first controller, then the first controller, specifically for the device identification according to the target connection device carried in the operation requests message received, in the connection device list self managed, search the device identification whether having this target connection device, and then can determine that whether target connection device is the connection device of the first accessor 101 correspondence.
If according to the device identification of the target connection device carried in the operation requests message received, find the device identification of target connection device in the list of devices self managed, then determine that target connection device is the connection device of the first accessor 101 correspondence.
If according to the device identification of the target connection device carried in the operation requests message received, in the list of devices self managed, do not find the device identification of target connection device, then determine that target connection device is not the connection device of the first accessor 101 correspondence.
Described first accessor 101, also for when determining that described target connection device is connection device corresponding to described first accessor, sends described operation requests message to described target connection device.
Concrete, now, the first accessor 101 is the first controller, then, when the first controller determination target connection device is connection device corresponding to the first controller, the first controller, specifically for being sent to target connection device by the operation requests received message.
Embodiments provide a kind of distributed software define grid SDN system, first accessor is after the operation requests message receiving application server transmission, when determining that target connection device is not connection device corresponding to the first accessor, operation requests message is forwarded to management equipment, now, management equipment is according to the corresponding relation between the device identification of the target connection device preserved in advance and accessor, determine that the accessor that target connection device is corresponding is the second accessor, and operation requests message is sent to the second accessor, and then second accessor the operation requests message received is sent in target connection device.Like this, in SDN system, can by the corresponding relation between the equipment identification information of target connection device and accessor, be the division information of SDN, be kept in management equipment, operation requests message is forwarded according to the division information of this SDN by management equipment, thus complete application server and be the equipment run application, to the operation of target connection device, and without the need to the division information of SDN being informed in advance the equipment run application in process operation requests message being sent to target connection device, and then decrease the potential safety hazard of SDN, improve the fail safe of SDN.
Embodiments provide a kind of data transmission method for uplink, described method is applied in SDN system, and described system comprises multiple accessor and at least one management equipment, and wherein, the corresponding multiple connection device of each accessor, as shown in Figure 2, comprising:
201, the first accessor receives the operation requests message that application server sends; When target connection device is not connection device corresponding to described first accessor, forward described operation requests message to described management equipment.
Wherein, the device identification of target connection device is carried in described operation requests message.
It should be noted that, when the corresponding multiple connection device of each accessor refers to that each accessor in SDN is controller, each controller all manages multiple target connection device.Such as, in the diagram, the target connection device that controller NOS-1 manages is target connection device 1 and target connection device 2; The target connection device that controller NOS-2 manages is target connection device 3 and target connection device 4; The target connection device that controller NOS-3 manages is target connection device 5.
It should be noted that, the application program that application server runs needs to operate target connection device, the application server transmit operation request message now run application.For the first accessor, application program can be divided into local application and remote application.Wherein, local application refers to the application program run by the first accessor oneself, and now the first accessor is application server.Remote application refers to the application program run by the equipment except the first accessor, and now, the equipment run application is application server, can be called far-end application server.
Concrete, if when application program operates in the first accessor, now the first accessor is application server, and the operation requests message that the first accessor receives application server transmission refers to, the first accessor receives the operation requests message of the module transmission himself run application.Now, the first accessor can be the first controller.
If when application program operates in the equipment except the first accessor, now relative to the first accessor, application server is far-end application server, then the first accessor receives the operation requests message that application server sends.Now, the first accessor can be that load equalizer may also be the first controller.
Wherein, load equalizer is independently equipment, for managing at least one controller in SDN controller cluster.First controller can be a controller at least one controller in SDN controller cluster.First controller can manage other controllers in SDN controller cluster, now the first controller is called Master NOS(Master Network OperatingSystem, master network operating system).Certainly, the first controller also can not have the function of other controllers in management SDN controller cluster.
It should be noted that, when the first controller does not have the function of other controllers in management SDN controller cluster, illustrate in SDN controller cluster, not there is the controller of other controllers in management SDN controller cluster.If in SDN controller cluster, have the controller of other controllers in management SDN controller cluster, then namely the first controller has the controller of other controller functions in management SDN controller cluster for this reason.
It should be noted that, load equalizer, only for managing at least one controller in SDN controller cluster, does not have the function run application.Be when the first accessor is application server, the first accessor can only be the first controller.
It should be noted that, in embodiments of the present invention, a SDN controller cluster comprises at least one and has run NOS(Network Operating System, network operating system) controller.Can by run NOS controller referred to as NOS or controller.
If application server is far-end application server, and described first accessor comprises: load equalizer, then load equalizer receives the operation requests message carrying the device identification of target connection device that far-end application server sends, and because load equalizer does not have corresponding connection device, so application server needs the target connection device of operation not to be the connection device that load equalizer is corresponding, then the operation requests message received is forwarded in management equipment by load equalizer.
If application server is far-end application server, and described first accessor comprises: the first controller, then the first controller receives the operation requests message carrying the device identification of target connection device that far-end application server sends, and when target connection device is not connection device corresponding to the first controller, the operation requests message received is sent in management equipment by the first controller.
It should be noted that, if load equalizer and Master NOS exist simultaneously, preferably, the first accessor is load equalizer.Now, the operation requests message carrying the device identification of target connection device of application server transmission is received by load equalizer.
Concrete, the method that described first accessor forwards described operation requests message to described management equipment is as follows:
First method, described first accessor obtains the corresponding relation between the device identification of the described target connection device preserved in advance in described management equipment and accessor, and according to described corresponding relation, determine that the accessor that described target connection device is corresponding is described second accessor, and described operation requests message is added in the request list of described second accessor stored in described management equipment.
Wherein, the request list of the second accessor refers to the list of each request message that the storage of setting up in management equipment is relevant to the second accessor, and request message comprises: the device identification of target connection device and corresponding operation requests message.
Concrete, first accessor can obtain the device identification of target connection device in operation requests message, and according to the device identification searching and managing equipment of target connection device, the corresponding relation of the second accessor recording target connection device and manage this target connection device is found in management equipment, and in corresponding relation, determine the second accessor, be the identification information obtaining this second accessor.First accessor, according to the identification information of the second accessor obtained, in the request list of each accessor stored in management equipment, is determined the request list of the second accessor, and operation requests message is added into the request list of the second accessor.
Second method, described operation requests message, according to the device identification of described target connection device, is added into the request list of the target connection device stored in management equipment by described first accessor.
Wherein, the request list of target connection device refers to the list of each request message that the storage of setting up in management equipment is relevant to target connection device, and request message comprises: the device identification of target connection device and corresponding operation requests message.
Concrete, first accessor can obtain the device identification of target connection device in operation requests message, and according to the device identification searching and managing equipment of target connection device, find target connection device in management equipment after, operation requests message is added in the request list of target connection device.
It should be noted that, operation requests message is forwarded to the method in management equipment by the first accessor, and can also be additive method, the present invention limit at this.
202, described management equipment is according to the corresponding relation between the device identification of the described target connection device preserved in advance and described accessor, determines that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is sent to described second accessor.
Concrete, the method that operation requests message is forwarded in management equipment according to the first accessor by management equipment is different, and the method whether detection request list changes is also different, specific as follows:
When operation requests message to be added into the request list of the second accessor stored in management equipment by the first accessor, whether the request list that described management equipment detects described second accessor changes; If described management equipment detects that the request list of described second accessor changes, then described management equipment is to described second accessor transmit operation request message.
That is, the corresponding relation of management equipment between the device identification and described accessor of the described target connection device according to preservation in advance, determine that the accessor that described target connection device is corresponding is after described second accessor, the request list of the request list of the second accessor preserved in advance and the second accessor of renewal is compared, determines whether the request list of the second accessor changes.If management equipment is compared with the request list of the second accessor of renewal the request list of the second accessor preserved in advance, determine that the data in its request list have increase or delete, then management equipment determines that the request list of the second accessor changes, now, management equipment is to the second accessor transmit operation request message.
When operation requests message to be added into the request list of the target connection device stored in management equipment by the first accessor, whether the request list that described management equipment detects described target connection device changes; If described management equipment detects that the request list of described target connection device changes, then described management equipment is to described second accessor transmit operation request message.
That is, the corresponding relation of management equipment between the device identification and described accessor of the described target connection device according to preservation in advance, determine that the accessor that described target connection device is corresponding is after described second accessor, the request list of the request list of target connection device preserved in advance and the target connection device of renewal is compared, determines whether the request list of target connection device changes.If management equipment is compared with the request list of the target connection device of renewal the request list of target connection device preserved in advance, determine that the data in its request list have increase or delete, then management equipment determines that the request list of target connection device changes, now, management equipment is to the second accessor transmit operation request message.
Further, management equipment is as follows to the method for the second accessor transmit operation request message:
Described management equipment sends the first Trigger message to described second accessor, described second accessor receives described first Trigger message that described management equipment sends, and determine whether carry described operation requests message in described first Trigger message, if described second accessor is determined not carry described operation requests message in described first Trigger message, described second accessor sends the first request message to described management equipment; Described management equipment receives the first request message that described second accessor sends; And described operation requests message is sent to described second accessor.
Wherein, the device identification of target connection device is carried in described operation requests message; Described first request message is the message for obtaining described operation requests message.
Optionally, the device identification of target connection device is carried in the first Trigger message.
It should be noted that, pre-setting when determining that request list changes in management equipment, send the Trigger Function of the first Trigger message from the accessor that trend is corresponding with the request list changed.So when management equipment detects the request list of the second accessor or the request list of target connection device changes, then management equipment sends the first Trigger message according to the Trigger Function pre-set to the second accessor.
It should be noted that, the first Trigger message be management equipment for notifying accessor, the request list that accessor is corresponding therewith there occurs the message of change.
Concrete, management equipment is when the request list of the request list or target connection device of determining the second accessor changes, send the Trigger Function of the first Trigger message according to the accessor corresponding with the request list changed from trend, send the first Trigger message to the second accessor.Now, the first Trigger message that the second accessor receiving management equipment sends, and determine whether carry operation requests message in the first Trigger message.If the second accessor is determined not carry operation requests message in the first Trigger message, then the second accessor sends the request obtaining operation requests message to management equipment, namely the first request message is sent to management equipment, now, management equipment receives the first request message that the second accessor sends, and the operation requests message carrying the device identification of target connection device is sent to the second accessor, the operation requests message carrying the device identification of target connection device that the second accessor receiving management equipment sends.
If described second accessor is determined to carry described operation requests message in described first Trigger message, described second accessor obtains the described operation requests message of carrying in described first Trigger message.
Concrete, the second accessor, when receiving the first Trigger message carrying operation requests message, by resolving the first Trigger message, thus obtains the operation requests message of carrying in the first Trigger message.
It should be noted that, management equipment can be run the equipment of distributed management system, and also can be the equipment running shared data bank system, the present invention limit this.
203, described operation requests message is sent to described target connection device by described second accessor.
Wherein, described second accessor is the controller managing described target connection device.
Concrete, second accessor is after the operation requests message receiving management equipment transmission, second accessor can obtain the device identification of target connection device according to the first Trigger message received, according to the device identification of target connection device to target connection device transmit operation request message.Second accessor also according to resolving the operation requests message that receive, thus can obtain the device identification of the target connection device carried in operation requests message, and then according to the device identification of target connection device to target connection device transmit operation request message.
Embodiments provide a kind of data transmission method for uplink, first accessor is after the operation requests message receiving application server transmission, when determining that target connection device is not connection device corresponding to the first accessor, operation requests message is forwarded to management equipment, now, management equipment is according to the corresponding relation between the device identification of the target connection device preserved in advance and accessor, determine that the accessor that target connection device is corresponding is the second accessor, and operation requests message is sent to the second accessor, and then second accessor the operation requests message received is sent in target connection device.Like this, in SDN system, can by the corresponding relation between the equipment identification information of target connection device and accessor, be the division information of SDN, be kept in management equipment, operation requests message is forwarded according to the division information of this SDN by management equipment, thus complete application server and be the equipment run application, to the operation of target connection device, and without the need to the division information of SDN being informed in advance the equipment run application in process operation requests message being sent to target connection device, and then decrease the potential safety hazard of SDN, improve the fail safe of SDN.
Embodiments provide a kind of data transmission method for uplink, as shown in Figure 3, comprising:
301, application server obtains the reference address information of the first accessor.
Concrete, if application server is far-end application server, and the first accessor is when being load equalizer, then application server needs the reference address information obtaining load equalizer, namely the reference address information that application server obtains is the address information of load equalizer, now can the address information of configuration load equalizer in the application server in advance.
If application server is far-end application server, and the first accessor is the first controller, now, first controller is Master NOS, then application server needs the reference address information obtaining Master NOS, namely the reference address information that application server obtains is the address information of the first controller, now can configure the address information of the first controller in advance in the application server.
If application server is far-end application server, and the first accessor is the first controller, now, first controller is any one NOS in NOS list, then application server can also according to one group of NOS address list pre-setting, random or choose the reference address information of address information as application server of a NOS in NOS list according to specific rule.
Wherein, specific rule refers to that the reference address information of address information as application server of a NOS chosen by application server according to concrete standard.Such as, application server, according to the CPU/ internal memory occupation rate order from low to high of NOS each in NOS address list, chooses the reference address information of address information as application server of the low NOS of the CPU/ internal memory occupation rate of NOS.
It should be noted that, the reference address information that application server obtains described first accessor also has additive method, and the present invention does not limit at this.
It should be noted that, if application server is the first accessor, now, application server, without the need to obtaining the reference address information of the first accessor, is and does not now perform step 301, and directly perform step 302.
302, described application server is to described first accessor transmit operation request message, and described first accessor receives the operation requests message that described application server sends.
Wherein, the device identification of target connection device is carried in described operation requests message.
Concrete, application server, according to the reference address information obtained, finds out first accessor corresponding with reference address information, thus the operation requests message carrying the device identification of target connection device is sent to the first accessor.
Concrete, the first accessor receives the method for the operation requests message that application server sends, can refer step 201, does not repeat them here.
It should be noted that, when the first accessor is load equalizer, because load equalizer is independently equipment, for managing at least one controller in SDN controller cluster.Load equalizer not Management Application Server needs the equipment of operation, and that is, application server needs the target connection device of operation to be the connection device that load equalizer is corresponding scarcely, now, performs step 305-308.When the first accessor is the first controller, because the first controller can be a controller at least one controller in SDN controller cluster.So can manage the equipment that at least one application server needs operation in the first controller, that is, application server needs the target connection device of operation may be the connection device that the first accessor is corresponding, now, performs step 303-308.
303, described first accessor determines whether described target connection device is the connection device that described first accessor is corresponding.
Concrete, now, first accessor is the first controller, then the first controller is according to the device identification of the target connection device carried in the operation requests message received, in the connection device list self managed, search the device identification whether having this target connection device, and then can determine whether target connection device is the connection device that the first accessor is corresponding.
If the first controller is according to the device identification of the target connection device carried in the operation requests message received, in the list of devices self managed, find the device identification of target connection device, then determine that target connection device is the connection device that the first accessor is corresponding.
If the first controller is according to the device identification of the target connection device carried in the operation requests message received, in the list of devices self managed, do not find the device identification of target connection device, then determine that target connection device is not the connection device that the first accessor is corresponding.
It should be noted that, the first accessor is different according to the result determined, and the step of following execution is different, if during the first accessor determination target connection device connection device that to be the first accessor corresponding, then perform step 304.If during the first accessor determination target connection device connection device that not to be the first accessor corresponding, then perform step 305-308.
304, when described first accessor determines that described target connection device is connection device corresponding to described first accessor, described first accessor sends described operation requests message to described target connection device.
Concrete, now, the first accessor is the first controller, then, when the first controller determination target connection device is connection device corresponding to the first controller, the operation requests message received is sent to target connection device by the first controller.
305, when described target connection device is not connection device corresponding to described first accessor, the first accessor forwards described operation requests message to described management equipment.
Concrete, can refer step 201, the present invention does not repeat them here.
306, described first accessor is to described application server transmit operation request response.Described application server receives the operation requests response message that described first accessor sends.
Concrete, if application server is far-end application server, when first accessor is load equalizer, then load equalizer distally application server transmit operation request response, i.e. the load equalizer distally successful message of application server transmit operation request.
If application server is far-end application server, when the first accessor is the first controller, then the first controller distally application server transmit operation request response, i.e. the first controller distally successful message of application server transmit operation request.
If application server is the first accessor, now, first accessor is the first controller, then the first controller is to the module transmit operation request response of self-operating application program, and namely the first controller is to the successful message of module transmit operation request of self-operating application program.
It should be noted that, if the first accessor determination target connection device is not the connection device that the first accessor is corresponding, then after operation requests message is forwarded to management equipment by the first accessor, the first accessor is to application server transmit operation request response.If the first accessor determination target connection device is the connection device that the first accessor is corresponding, then, after operation requests message is sent to target connection device by the first accessor, the first accessor is to application server transmit operation request response.
307, described management equipment is according to the corresponding relation between the device identification of the described target connection device preserved in advance and described accessor, determines that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is sent to described second accessor.
Concrete, can refer step 202, the present invention does not repeat them here.
308, described operation requests message is sent to described target connection device by described second accessor.
Wherein, described second accessor is the controller managing described target connection device.
Concrete, can refer step 203, the present invention does not repeat them here.
Exemplary, as shown in Figure 4, suppose that management equipment is run the equipment of distributed management system, such as, management equipment be run ZooKeeper(distributed service framework) equipment, the first accessor is the controller of operation NOS.In ZooKeeper, then create the SDN cluster catalogue be made up of node, each node on behalf NOS or target connection device.Then all nodes combine according to the corresponding relation between NOS and target connection device, like this, each node can both determine unique path, so that the first accessor, when searching for the controller NOS of target connection device or management objectives connection device, uniquely can determine the controller NOS of target connection device or management objectives connection device.Under can seeing in Fig. 4 that target connection device that each NOS manages self and self is created in event distribution catalogue with the form of node, and using the child node of the node of target connection device as the controller of management objectives connection device.Such as, the node of target connection device 4 is as the child node of the node of NOS-2, like this, first accessor just can according to the corresponding relation between node and its child node, determine the exclusive path at target connection device 4 place, namely the exclusive path at target connection device 4 place is/event distribution/NOS-2/ target connection device 4.
If the first accessor determination target connection device is not the connection device that the first accessor is corresponding, with the first accessor shown in Fig. 4 for NOS-1, target connection device is target connection device 4 is example, if NOS-1 needs the operation requests message by application server sends to be sent in target connection device 4, then first NOS-1 searches for the path of target connection device 4 under ZooKeeper catalogue, after the path obtaining target connection device 4, NOS-1 in ZooKeeper/event distribution/NOS-2/ target connection device 4 node under, the interface of node is created by calling Zookeeper, create a sub-Node Events 1, and operation requests message is added in the data of child node event 1 relevant to target connection device 4 in ZooKeeper.Now, ZooKeeper sends the first Trigger message to the second accessor NOS-2 of management objectives connection device 4, and operation requests message is carried in the first Trigger message, second accessor NOS-2 receives the first Trigger message that ZooKeeper sends, and obtains the operation requests message of carrying in the first Trigger message.
Operation requests message can be sent to target connection device 4 according to the device identification of target connection device 4 by the second accessor NOS-2.
If the first accessor determination target connection device is the connection device that the first accessor is corresponding, with the first accessor shown in Fig. 4 for NOS-1, target connection device is target connection device 2 is example, and now, NOS-1 is the controller of direct management objectives connection device 2.Then the operation requests message that application server sends directly is sent in target connection device 2 by NOS-1.
Embodiments provide a kind of data transmission method for uplink, first accessor is after the operation requests message receiving application server transmission, when determining that target connection device is not connection device corresponding to the first accessor, operation requests message is forwarded to management equipment, now, management equipment is according to the corresponding relation between the device identification of the target connection device preserved in advance and accessor, determine that the accessor that target connection device is corresponding is the second accessor, and operation requests message is sent to the second accessor, and then second accessor the operation requests message received is sent in target connection device.Like this, in SDN system, can by the corresponding relation between the equipment identification information of target connection device and accessor, be the division information of SDN, be kept in management equipment, operation requests message is forwarded according to the division information of this SDN by management equipment, thus complete application server and be the equipment run application, to the operation of target connection device, and without the need to the division information of SDN being informed in advance the equipment run application in process operation requests message being sent to target connection device, and then decrease the potential safety hazard of SDN, improve the fail safe of SDN.
In several embodiments that the application provides, should be understood that, disclosed system, apparatus and method, can realize by another way.Such as, device embodiment described above is only schematic, such as, the division of described unit, be only a kind of logic function to divide, actual can have other dividing mode when realizing, such as multiple unit or assembly can in conjunction with or another system can be integrated into, or some features can be ignored, or do not perform.Another point, shown or discussed coupling each other or direct-coupling or communication connection can be by some interfaces, and the indirect coupling of device or unit or communication connection can be electrical, machinery or other form.
The described unit illustrated as separating component or can may not be and physically separates, and the parts as unit display can be or may not be physical location, namely can be positioned at a place, or also can be distributed in multiple network element.Some or all of unit wherein can be selected according to the actual needs to realize the object of the present embodiment scheme.
In addition, each functional unit in each embodiment of the present invention can be integrated in a processing unit, also can be that the independent physics of unit comprises, also can two or more unit in a unit integrated.Above-mentioned integrated unit both can adopt the form of hardware to realize, and the form that hardware also can be adopted to add SFU software functional unit realizes.
The above-mentioned integrated unit realized with the form of SFU software functional unit, can be stored in a computer read/write memory medium.Above-mentioned SFU software functional unit is stored in a storage medium, comprises the part steps of some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) perform method described in each embodiment of the present invention.And aforesaid storage medium comprises: USB flash disk, portable hard drive, read-only memory (Read-Only Memory, be called for short ROM), random access memory (Random Access Memory, be called for short RAM), magnetic disc or CD etc. various can be program code stored medium.
Last it is noted that above embodiment is only in order to illustrate technical scheme of the present invention, be not intended to limit; Although with reference to previous embodiment to invention has been detailed description, those of ordinary skill in the art is to be understood that: it still can be modified to the technical scheme described in foregoing embodiments, or carries out equivalent replacement to wherein portion of techniques feature; And these amendments or replacement, do not make the essence of appropriate technical solution depart from the spirit and scope of various embodiments of the present invention technical scheme.

Claims (14)

1. a distributed software define grid SDN system, is characterized in that, described system comprises the first accessor, management equipment and the second accessor, wherein,
Described first accessor, for receiving the operation requests message that application server sends; Wherein, the device identification of target connection device is carried in described operation requests message;
Described first accessor, time also for not being connection device corresponding to described first accessor at described target connection device, forwards described operation requests message to described management equipment;
Described management equipment, for according to the corresponding relation between the device identification of the described target connection device preserved in advance and described accessor, determines that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is sent to described second accessor;
Described second accessor, for sending to described target connection device by described operation requests message; Wherein, described second accessor is the controller managing described target connection device.
2. system according to claim 1, is characterized in that, described first accessor comprises: the first controller.
3. system according to claim 1, is characterized in that, described first accessor comprises: load equalizer.
4. the system according to any one of claim 1-3, is characterized in that,
Described first accessor, specifically for obtaining the corresponding relation between the device identification of the described target connection device preserved in advance in described management equipment and accessor, and according to described corresponding relation, determine that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is added in the request list of described second accessor stored in described management equipment.
5. system according to claim 4, is characterized in that,
Whether described management equipment, change specifically for the request list detecting described second accessor; If detect, the request list of described second accessor changes, then to described second accessor transmit operation request message.
6. the system according to any one of claim 1-3, is characterized in that,
Described first accessor, specifically for the device identification according to described target connection device, is added into the request list of the described target connection device stored in management equipment by described operation requests message.
7. system according to claim 6, is characterized in that,
Whether described management equipment, change specifically for the request list detecting described target connection device; If detect, the request list of described target connection device changes, then to described second accessor transmit operation request message.
8. the system according to any one of claim 4-7, is characterized in that,
Described management equipment, specifically for sending the first Trigger message to described second accessor;
Described second accessor, specifically for receiving described first Trigger message that described management equipment sends, and determines whether carry described operation requests message in described first Trigger message; When determining not carry described operation requests message in described first Trigger message, send the first request message to described management equipment; Wherein, described first request message is the message for obtaining described operation requests message;
Described management equipment receives the first request message that described second accessor sends; And described operation requests message is sent to described second accessor;
Described second accessor, also for when determining to carry described operation requests message in described first Trigger message, obtains in described first Trigger message the described operation requests message of carrying.
9. a data transmission method for uplink, is characterized in that, described method is applied in distributed software define grid SDN system, and described system comprises multiple accessor and at least one management equipment, wherein, the corresponding multiple connection device of each accessor, described method comprises:
First accessor receives the operation requests message that application server sends; When target connection device is not connection device corresponding to described first accessor, forward described operation requests message to described management equipment; Wherein, the device identification of target connection device is carried in described operation requests message;
Described management equipment, according to the corresponding relation between the device identification of the described target connection device preserved in advance and described accessor, determines that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is sent to described second accessor;
Described operation requests message is sent to described target connection device by described second accessor; Wherein, described second accessor is the controller managing described target connection device.
10. method according to claim 9, is characterized in that, described first accessor forwards described operation requests message to described management equipment and comprises:
Described first accessor obtains the corresponding relation between the device identification of the described target connection device preserved in advance in described management equipment and accessor, and according to described corresponding relation, determine that the accessor that described target connection device is corresponding is described second accessor; And described operation requests message is added in the request list of described second accessor stored in described management equipment.
11. methods according to claim 10, is characterized in that, described operation requests message sends to described second accessor to comprise by described management equipment:
Whether the request list that described management equipment detects described second accessor changes; If described management equipment detects that the request list of described second accessor changes, then described management equipment is to described second accessor transmit operation request message.
12. methods according to claim 9, is characterized in that, described first accessor forwards described operation requests message to described management equipment and comprises:
Described operation requests message, according to the device identification of described target connection device, is added into the request list of the described target connection device stored in management equipment by described first accessor.
13. methods according to claim 12, is characterized in that, described operation requests message sends to described second accessor to comprise by described management equipment:
Whether the request list that described management equipment detects described target connection device changes; If described management equipment detects that the request list of described target connection device changes, then described management equipment is to described second accessor transmit operation request message.
14. methods according to any one of claim 10-13, it is characterized in that, described management equipment comprises to described second accessor transmit operation request message:
Described management equipment sends the first Trigger message to described second accessor;
Described second accessor receives described first Trigger message that described management equipment sends, and determines whether carry described operation requests message in described first Trigger message;
If described second accessor is determined not carry described operation requests message in described first Trigger message, described second accessor sends the first request message to described management equipment; Wherein, the identification information obtaining described operation requests message is carried in described first request message;
Described management equipment receives the first request message that described second accessor sends; And described operation requests message is sent to described second accessor;
If described second accessor is determined to carry described operation requests message in described first Trigger message, described second accessor obtains the described operation requests message of carrying in described first Trigger message.
CN201310689192.7A 2013-12-16 2013-12-16 A kind of data transmission method for uplink and system Active CN104717258B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201310689192.7A CN104717258B (en) 2013-12-16 2013-12-16 A kind of data transmission method for uplink and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201310689192.7A CN104717258B (en) 2013-12-16 2013-12-16 A kind of data transmission method for uplink and system

Publications (2)

Publication Number Publication Date
CN104717258A true CN104717258A (en) 2015-06-17
CN104717258B CN104717258B (en) 2018-09-28

Family

ID=53416215

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201310689192.7A Active CN104717258B (en) 2013-12-16 2013-12-16 A kind of data transmission method for uplink and system

Country Status (1)

Country Link
CN (1) CN104717258B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106815012A (en) * 2016-12-14 2017-06-09 深圳中顺易金融服务有限公司 Decentralized configuration Explore of Unified Management Ideas and system based on Zookeeper
WO2019238132A1 (en) * 2018-06-15 2019-12-19 华为技术有限公司 Data management method and device
CN111314105A (en) * 2019-11-22 2020-06-19 深圳市信锐网科技术有限公司 Method, device and system for matching connection of equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047552A (en) * 2006-04-28 2007-10-03 华为技术有限公司 Distribution service management method, system and distribution authorization capacibility discrimination and authorization method, system
CN101047563A (en) * 2007-04-20 2007-10-03 北京航空航天大学 System, method and loading uniform method for implementing network resource adaptive
CN101247370A (en) * 2008-03-14 2008-08-20 中国网通集团宽带业务应用国家工程实验室有限公司 Method and system for implementing message presentation service
CN101426024A (en) * 2008-12-15 2009-05-06 深圳市迅雷网络技术有限公司 Data flow controlling method, system and apparatus
JP2012524307A (en) * 2009-04-17 2012-10-11 中国科学院声学研究所 CDN network system coding based on geolocation information and method of distributing data

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047552A (en) * 2006-04-28 2007-10-03 华为技术有限公司 Distribution service management method, system and distribution authorization capacibility discrimination and authorization method, system
CN101047563A (en) * 2007-04-20 2007-10-03 北京航空航天大学 System, method and loading uniform method for implementing network resource adaptive
CN101247370A (en) * 2008-03-14 2008-08-20 中国网通集团宽带业务应用国家工程实验室有限公司 Method and system for implementing message presentation service
CN101426024A (en) * 2008-12-15 2009-05-06 深圳市迅雷网络技术有限公司 Data flow controlling method, system and apparatus
JP2012524307A (en) * 2009-04-17 2012-10-11 中国科学院声学研究所 CDN network system coding based on geolocation information and method of distributing data

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106815012A (en) * 2016-12-14 2017-06-09 深圳中顺易金融服务有限公司 Decentralized configuration Explore of Unified Management Ideas and system based on Zookeeper
WO2019238132A1 (en) * 2018-06-15 2019-12-19 华为技术有限公司 Data management method and device
US11706107B2 (en) 2018-06-15 2023-07-18 Huawei Technologies Co., Ltd. Data management method and apparatus
CN111314105A (en) * 2019-11-22 2020-06-19 深圳市信锐网科技术有限公司 Method, device and system for matching connection of equipment

Also Published As

Publication number Publication date
CN104717258B (en) 2018-09-28

Similar Documents

Publication Publication Date Title
CN103019960B (en) Distributed caching method and system
CN107066354B (en) Database switching method, master server and slave server
CN103493003B (en) The copy of disk image is sent from source memory to target memory
CN102932413B (en) A kind of computational resource allocation method, cloud management platform node and computational resource cluster
US10038593B2 (en) Method and system for recovering virtual network
CN109274557B (en) Intelligent CMDB management and cloud host monitoring method in cloud environment
CN105991458B (en) Load balancing method and load balancing device
US10049068B2 (en) SAS system, SAS system traversal method, and apparatus
CN109582213B (en) Data reconstruction method and device and data storage system
CN103188098B (en) A kind of disaster tolerance switching method, system and device
CN104639347A (en) Multi-cluster monitoring method and device, and system
CN105740063A (en) Data processing method and apparatus
CN105426271A (en) Lock management method and device for distributed storage system
JP2013243670A (en) Packet processing method, device and system
CN104320274A (en) Disaster tolerance method and device
CN104468521A (en) Online migration method, device and system
CN109921942B (en) Cloud platform switching control method, device and system and electronic equipment
CN103559124A (en) Fast fault detection method and device
CN104717258A (en) Data transmitting method and system
CN103326887A (en) Interface management method and system
US9300530B2 (en) Management device, management method, and medium
CN103412771A (en) Software upgrading processing method, device and system
CN102769495B (en) A kind of optical fiber access network equipment communication means, Apparatus and system
CN104536926A (en) Control method and device of serial devices
CN105022666A (en) Method, device and system for controlling MapReduce task scheduling

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20220214

Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province

Patentee after: Huawei Cloud Computing Technology Co.,Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd.