CN101453393A - Enterprise network system for file transmission - Google Patents
Enterprise network system for file transmission Download PDFInfo
- Publication number
- CN101453393A CN101453393A CN 200710178247 CN200710178247A CN101453393A CN 101453393 A CN101453393 A CN 101453393A CN 200710178247 CN200710178247 CN 200710178247 CN 200710178247 A CN200710178247 A CN 200710178247A CN 101453393 A CN101453393 A CN 101453393A
- Authority
- CN
- China
- Prior art keywords
- xpeer
- task
- server
- interface
- file transfer
- 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
Links
Images
Abstract
The invention provides an enterprise network system for transmitting documents. The system comprises a backbone network and a plurality of sectional networks which are connected with the backbone network through buses. Each sectional network comprises at least one xPeer server. The sectional networks transmit documents between sectors through the xPeer servers and the buses. The backbone network comprises an M-Peer server which schedules the transmission tasks of the xPeer servers. Compared with the prior art, the system has the technical advantages that the network architecture of the system allows large-capacity documents to be exchanged directly, rapidly and reasonably between the sectors in an enterprises, reduces labor cost and improves program production efficiency. In addition, the system can increase the number of systems needing document transmission through a simple registration mode and is easy to maintain.
Description
Technical field
The present invention relates to technical field of the computer network, specifically, The present invention be more particularly directed to a kind of network system that is used for big capacity documents transmission.
Background technology
At present, the operation of most of enterprises all relates to the business of multiple different in kind, therefore in the computer network of enterprises, form a plurality of service application subnets usually and satisfy these professional demands respectively, and data need need to share between each subnet or transmission.With radio, TV and film industries is example, current domestic and international radio, TV and film industries in the overall development direction aspect information-based are: networked, information-based, according to the business demand that relates to multiple different in kind in the practical business of TV station, TV station's a plurality of service application subnets of inner formation satisfy the whole TV technological process that TV station " adopts, compiles, broadcasts, deposits, manages ".Wherein, program material needs to share between the subnet or transmission, therefore, need design a kind of feasible pattern rationally to the file transfer mode.Therefore, need design a kind of feasible pattern rationally to the file transfer mode.
Traditional file transfer mode generally is point-to-point communication and transmission between two subnet different application systems, generally in this case, two systems all need to provide client and serve end program, when the system number of carrying out file transfer when needs increases, increase each system burden and operating cost.Under this kind pattern, quantity related between the system is [N (N-1)]/2, and when increasing an application system, the degree of association of system increases N (with reference to figure 1 and Fig. 2), and client and serve end program to newly-increased system need be provided respectively in associated system.
Summary of the invention
The objective of the invention is to overcome the deficiencies in the prior art, bussing technique is applied to Intranet, thereby a kind of enterprise network framework that is suitable for the Large Volume Data transmission is provided.
For achieving the above object, the enterprise network system that is used for file transfer provided by the invention comprises: by the backbone network and the plate net of bus connection; Each described plate net comprises at least one xPeer server, and the xPeer server is crossed by described each plate Netcom and bus is carried out file transfer between plate; Described backbone network comprises the M-Peer server, and described M-Peer server is dispatched the transformation task of each xPeer server.
In the technique scheme, described backbone network also comprises message flow server (MFS); Described M-Peer server has external interface and to inner joint, described external interface is used for carrying out alternately with message flow server (MFS); Described inner joint is used for carrying out alternately with described xPeer server.
In the technique scheme, the external interface of described M-Peer server comprises task initiation interface, task suspension interface, task termination interface and priority of task interface.
In the technique scheme, described M-Peer server inner joint is comprised that xPeer registration interface, xPeer state report interface, xPeer Task Progress interface and xPeer task status and report interface.
In the technique scheme, described backbone network also comprises Cache dish battle array, and this Cache dish battle array is used to be buffered in the file that transmits between each xPeer server.
Compared with prior art, the present invention can reach following technique effect:
Network architecture of the present invention can allow big capacity documents (as media file) directly carry out fast, rationally exchange between inner each plate of enterprise (as TV station), reduces labour cost, improves program production efficiency.In addition, the present invention can need carry out system's number of file transfer by simple logon mode increase, and is easy to maintenance.
Description of drawings
Fig. 1 is traditional file transfer network architecture schematic diagram;
Fig. 2 is the schematic diagram that traditional file transfer network architecture is expanded;
Fig. 3 is a network architecture schematic diagram of the present invention;
Fig. 4 is the M-Peer system flow chart;
Fig. 5 is M-Peer scheduling flow figure;
Fig. 6 is the present invention carries out file transfer between each application system a schematic diagram;
Fig. 7 is that the present invention is at the schematic diagram that carries out the application system expansion.
Embodiment
Basic design of the present invention is to utilize bus form that each plate net of enterprises is interconnected, and the file transfer services of straddle piece is encapsulated in the xPeer server of each plate net, utilizes the xPeer server to realize interplate big capacity documents transmission.In addition, the present invention also provides backbone network, disposes the M-Peer server in the backbone network, and the transformation task of each xPeer server is dispatched.
Below in conjunction with the drawings and specific embodiments the present invention is described in further detail:
Embodiment 1
With the TV station is example, and each details of enterprise network framework is described in detail.The file that is transmitted in the present embodiment mainly is meant enterprise's media file.With reference to figure 3, the network architecture of present embodiment comprises: by enterprise's media bus (Enterprise Media Bus, EMB) backbone network of Lian Jieing and a plurality of plate net; Each described plate net comprises at least one xPeer server (hereinafter to be referred as xPeer), and xPeer crosses in described each plate Netcom and bus is carried out file transfer between plate; Described backbone network comprises M-Peer server (hereinafter to be referred as M-Peer), and described M-Peer dispatches the transformation task of each xPeer.The system that to utilize M-Peer and xPeer to carry out file transfer in the present embodiment is called Xfer.Outside two, described backbone network message flow server (MFS).
In the present embodiment, the file transmission task scheduling is finished by M-Peer, M-Peer is as the operating part of xPeer and scheduling transmission task, except that play Xfer and MFS alternately, finish simultaneously the source between a plurality of xPeer of purpose and the scheduling effect between a plurality of transformation tasks.
The major function of M-Peer comprises:
When MFS initiated a task, the M-Peer readjustment obtained transformation task;
The xPeer end is dispatched according to strategy, realized the transmission of file;
For xPeer provides concrete transformation task, receive xPeer transmission information;
Return progress status to MFS;
Transformation task processed, the just scheduling of task;
To the intervention of transformation task, as suspended task, stop task;
The monitoring of transformation task, the initial stage can not realized management (such as retry etc.) function;
System is configured.
In this enforcement, scheduling strategy is as follows:
1, task scheduling
Calling on the Xfer when MFS goes up task of initiation of task is initiated interface, and the expected time (preStartTime) is Task Distribution different stage (priority) in the Xfer parsing task.M-Peer goes to find according to the dispatch interval time in the system configuration which task needs is activated among the Xfer, and time of implementation and priority initiating task respectively according to expectation.At first being the fundamental of initiating task with the time of implementation, if on the same time of implementation, just is judgment standard with priority.
2, the scheduling of the xPeer behind the task start
Behind the task start, source end and destination information in the Xfer parsing task, by source end place application system and the destination place application system that comprises in the task, if source end and destination be not in same application system, respectively query source end and destination place application system are carried out the Task Distribution of xPeer at the state of the xPeer of M-Peer registration according to following strategy:
Judgement source end (transmitting terminal, service end) state is the service end maximum number of connections that the linking number of " service end free time " or service end is provided with less than system, then connects the xPeer of for several times little selective sequential as service end according to service end free time, service end linking number minimum, service end successively;
Judge that destination (receiving terminal, client) state is that the xPeer of " client free time " is as client xPeer, if a plurality of states are the xPeer of " client free time ", client linking number when checking it as server end, select xPeer (lowering xPeer pressure) successively according to the order from low to high of this quantity, if the xPeer that this numerical value equates then selects one of them as client xPeer at random;
After having selected to be the xPeer of transmission, promptly begin file transfer.
(annotating:, improve file efficiency of transmission in the whole system framework) if the same application system of source end and destination place does not then adopt by the xPeer transmission but adopts document copying pattern in the same subnet
In the present embodiment, M-Peer has external interface and to inner joint.
The M-Peer external interface mainly provides the startup transformation task, suspends transmission, stops transmission, priority of task for the MFS readjustment.Introduce each external interface below one by one.
Task is initiated interface (following code all is to represent with the java style):
public?String?startTransfer(String?taskInformation)；
Calling on the Xfer during task of the last initiation of function: MFS of task is initiated interface.
Parameter: the taskInformation mission bit stream comprises this task in the example ID of mfs, time, transmit leg place application system, reciever place application system, source end filename, source end routing information, destination end store path, the expected time that this task is created on mfs
Parametric t askInformation formal definition (XSD):
<？xml?version＝＂1.0＂encoding＝＂UTF-8＂？>
<schema?xmlns＝＂http://www.w3.org/2001/XMLSchema＂
elementFormDefault＝＂qualified＂>
<element?name＝＂taskInformation＂>
<complexType>
<sequence>
<element?name＝＂mfsinstanceID＂type＝＂string＂/>
<element?name＝＂mfscreatetime＂type＝＂datetime＂/>
<element?name＝＂fromdn＂type＝＂string＂/>
<element?name＝＂todn＂type＝＂string＂/>
<element?name＝＂resourceFilename＂type＝＂string＂/>
<element?name＝＂resourceFilePath＂type＝＂string＂/>
<element?name＝＂targetStorePath＂type＝＂string＂/>
<element?name＝＂preStartTime＂type＝＂datetime＂/>
</sequence>
</complexType>
</element>
</schema>
Return value: the content of returning is the character string of an XML, the information analysis of task.
The task suspension interface:
public?String?pauseWorkitems(string?itemID)；
Function: suspend Xfer and go up the ongoing transformation task of initiating.
Parameter: itemID task ID;
Return value: then represent the suspended task success if return distance of zero mark degree character string, otherwise return the XML that comprises error message.
The task termination interface:
public?String?stopWorkitems(string?itemID)；
Function: stop Xfer and go up the transformation task of initiating.
Parameter: itemID task ID;
Return value: then represent the terminated task success if return distance of zero mark degree character string, otherwise return the XML that comprises error message.
The priority of task interface:
public?String?prioritize?Workitems(String?itemID，Int?priorityLevel)；
Function: by the mode that the priority level of task is changed, preferential certain transformation task.
Parameter: itemID task ID, the precedence information of priorityLevel task;
Return value: then represent the priority task success if return distance of zero mark degree character string, otherwise return the XML that comprises error message.
M-Peer adopts Web Service issue to inner joint, mainly refers to the interactive portion with xPeer; Provided by M-peer, xPeer calls, and registration, the xPeer state that mainly contains xPeer reported, xPeer file transfer progress is reported and task status is reported.Introduce each below one by one to inner joint
XPeer registers interface:
public?String?peerRegister(String?hostIP)；
Function: to the state of M-Peer registration xPeer own.
Parameter: hostIP represents xPeer place IP.
Return value:, otherwise return the XML that comprises error message if returning distance of zero mark degree character string then represents to succeed in registration.
The xPeer state is reported interface:
public?String?reportPeerstatus(String?hostIP，String?peerStatus)；
Function: xPeer reports oneself state information to Xfer;
Parameter: hostIP represents IP address, xPeer place, and peerStatus represents the state of present xPeer;
Return value:, otherwise return the XML that comprises error message if returning distance of zero mark degree character string then represents to report successfully.
XPeer Task Progress interface:
public?String?postProcess(String?itemID)；
Function: xPeer reports the file transfer progress to M-Peer;
Parameter: itemID represents task ID;
Return value: return the transmission progress value that this Peer goes up certain transformation task.
The xPeer task status is reported interface:
public?String?reportTaskStatus(String?itemID)；
Function: each xPeer reports the file transfer progress by the mode of WebService to Xfer.
Parameter: itemID represents task ID;
Return value: return the state that this Peer goes up certain transformation task.
In the present embodiment, (with reference to figure 4) is as follows for the system flow of M-Peer:
1) after Xfer starts, accepts the registration and unregistration of transmission service end xPeer;
2) M-Peer monitors task immediately, if task is not stopped, executes the task, and reports task status.
In the present embodiment, (with reference to figure 5) is as follows for the scheduling flow of M-Peer:
1) when M-Peer listens to task, initiates transformation task according to task priority;
2) judge the position of task xPeer, obtain the state of the xPeer that carries out this transformation task, if xPeer is ready, the transmission task is to this xPeer;
3) when task arrives xPeer, judged whether intervention instruction, if there is instruction (suspend, recover, stop) carrying out relevant intervention action; As if not having intervention instruction, M-Peer to accept xPeer state and progress report, judgement has no abnormal, if having unusually, returns unusually, ends task; If no abnormal, accept xPeer in real time and report state and progress data, judge whether task is finished, if finish, end task, return the transmission result; If do not finish the return instruction mistake;
4) if judge the position of task xPeer, when obtaining the state of the xPeer that carries out this transformation task, xPeer prepares not ready, judge the number of retries of this task,, return unusual if surpass the maximum reattempt times of system configuration, end task, if do not reach number of retries, obtain task xPeer state, continue transfer process.
The file transfer mode based on bus of present embodiment adopts the encapsulation of file transfer order in Xfer, and simple interface externally is provided; Transmission is to be finished by Xfer oneself, and application system only need pass to Xfer with relevant information, and Xfer dispatches transformation task and Transport endpoint (xPeer), finishes transmission.As shown in Figure 6, this figure is that the Xfer dispatch application B of system transfer files is to application system C.
If continue to increase application system, only need the transmission ends on the application system to register once to Xfer, can finish the seamless insertion of system, embody architecture mode based on bus type, its advantage is need not increase client and serve end program in application system; When increasing system applies, do not influence the work of other application systems, can not increase the operation burden and the operating cost (as shown in Figure 7) of whole system yet.
Because the data volume of enterprise's media data is bigger,, still to expend a large amount of time even therefore under the broadband network environment, transmit.Therefore, in the present embodiment, can also set up interplate many transmission channels, to satisfy the big data quantity transmission requirements by in the plate network, disposing the mode of a plurality of xPeer.
In addition, the backbone network in the present embodiment also comprises a built-in Small-sized C ache dish battle array.Be used to support the asynchronous transmission of file data.When being the task initiation, the scheduler module of M-Peer is found goal systems off-line, enterprise's media file can be transferred to buffer memory among the Cache, after objective network resumes connections, enterprise's media file with buffer memory is transferred to destination again, to reduce between plate because the growth of load that network failure causes.Certainly, if when source network and purpose network are active state, file data will directly transmit between two plates.
Current domestic and international radio, TV and film industries in the overall development direction aspect information-based are: networked, information-based, enterprise's media bus (Enterprise Media Bus, the mentality of designing of the exchange transmission of realization media file in the full court network that EMB) to be Xin Aote company propose in full court networking scheme.Present embodiment adopts enterprise's media bus, can allow media file directly can carry out fast, rationally exchange, reduce labour cost, improve program production efficiency at inner each plate of TV station, guarantee that program fast, on time, broadcast accurately, improves program production and broadcasts fail safe.
It should be noted last that above embodiment is only unrestricted in order to technical scheme of the present invention to be described.Although the present invention is had been described in detail with reference to embodiment, those of ordinary skill in the art is to be understood that, technical scheme of the present invention is made amendment or is equal to replacement, do not break away from the spirit and scope of technical solution of the present invention, it all should be encompassed in the middle of the claim scope of the present invention.
Claims (5)
1. an enterprise network system that is used for file transfer comprises: by the backbone network and the plate net of bus connection; Each described plate net comprises at least one xPeer server, and the xPeer server is crossed by described each plate Netcom and bus is carried out file transfer between plate; Described backbone network comprises the M-Peer server, and described M-Peer server is dispatched the transformation task of each xPeer server.
2. the enterprise network system that is used for file transfer according to claim 1 is characterized in that described backbone network also comprises the message flow server; Described M-Peer server has external interface and to inner joint, described external interface is used for carrying out alternately with the message flow server; Described inner joint is used for carrying out alternately with described xPeer server.
3. the enterprise network system that is used for file transfer according to claim 2 is characterized in that, the external interface of described M-Peer server comprises task initiation interface, task suspension interface, task termination interface and priority of task interface.
4. the enterprise network system that is used for file transfer according to claim 2, it is characterized in that, described M-Peer server inner joint is comprised that xPeer registration interface, xPeer state report interface, xPeer Task Progress interface and xPeer task status and report interface.
5. the enterprise network system that is used for file transfer according to claim 1 is characterized in that, described backbone network also comprises Cache dish battle array, and this Cache dish battle array is used for the file that transmits between the buffer memory xPeer server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200710178247 CN101453393B (en) | 2007-11-28 | 2007-11-28 | Enterprise network system for file transmission |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200710178247 CN101453393B (en) | 2007-11-28 | 2007-11-28 | Enterprise network system for file transmission |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101453393A true CN101453393A (en) | 2009-06-10 |
| CN101453393B CN101453393B (en) | 2013-09-18 |
Family
ID=40735422
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200710178247 Expired - Fee Related CN101453393B (en) | 2007-11-28 | 2007-11-28 | Enterprise network system for file transmission |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101453393B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102855236A (en) * | 2011-06-27 | 2013-01-02 | 北京东方通科技股份有限公司 | File transmitting system and file transmitting method |
| CN103136143A (en) * | 2011-11-23 | 2013-06-05 | 中兴通讯股份有限公司 | Enterprise message bus data transmission method and enterprise message bus data transmission system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1363907A (en) * | 2001-09-25 | 2002-08-14 | 郑肖惺 | Distributed universal network system for acquiring and controlling analog and digital information |
| CN1901453A (en) * | 2005-07-21 | 2007-01-24 | 北京交大网通信息技术有限公司 | Embedded far remote central maintenance device and method |
-
2007
- 2007-11-28 CN CN 200710178247 patent/CN101453393B/en not_active Expired - Fee Related
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102855236A (en) * | 2011-06-27 | 2013-01-02 | 北京东方通科技股份有限公司 | File transmitting system and file transmitting method |
| CN102855236B (en) * | 2011-06-27 | 2015-04-29 | 北京东方通科技股份有限公司 | File transmitting system and file transmitting method |
| CN103136143A (en) * | 2011-11-23 | 2013-06-05 | 中兴通讯股份有限公司 | Enterprise message bus data transmission method and enterprise message bus data transmission system |
| CN103136143B (en) * | 2011-11-23 | 2015-12-16 | 中兴通讯股份有限公司 | The method and system of enterprise message bus transfer data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101453393B (en) | 2013-09-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102571550B (en) | A kind of general information exchange platform and method | |
| CN101447856A (en) | High-capacity file transmission method | |
| CN101022431B (en) | Interface gateway and interface gateway data processing method | |
| CN102035828B (en) | Method of using nodes in a home communication network | |
| CN100438456C (en) | Hop-by-hop transferred distributed flow media transmission performance test method and device | |
| CN102387075B (en) | Dynamic service routing method and device for enterprise service bus | |
| US20090135762A1 (en) | Point-to-point communication within a mesh network | |
| CN101499995B (en) | Service scheduling method, system and apparatus for service scheduling | |
| CN101184056A (en) | Distributed enterprise service bus message switching method | |
| CN102006245B (en) | Date exchanging and sharing platform | |
| CN101383839A (en) | Data distribution system based on data server and implementation method | |
| CN102025616A (en) | Method, device and switch for realizing BFD (Bidirectional Forwarding Detection) | |
| CN101159611A (en) | Batch system disposing method and device | |
| CN114401284A (en) | Real-time data acquisition and transmission system and method for fixed pollution source treatment working condition | |
| CN101453393B (en) | Enterprise network system for file transmission | |
| CN101527732A (en) | Method and system for media data remote transmission service management control | |
| CN100466614C (en) | Multi-cast broadcasting business realizing method | |
| EP2439881B1 (en) | Cluster system and request message distribution method for processing multi-node transaction | |
| CN101009669B (en) | A method and system and route device for transmitting the multicast message | |
| US10254127B2 (en) | Method for remotely reading electric meters | |
| CN101651823B (en) | Streaming media server system and relevant method thereof | |
| CN102196157A (en) | Program publishing system of TV (television) station | |
| CN101938383A (en) | On-line monitoring method and system of user account with multiple services as well as monitoring service system | |
| CN105376155B (en) | A kind of Intelligent routing system and method based on distributed type assemblies framework | |
| CN101572635B (en) | Data transmission scheduling method based on channel configuration |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130918 Termination date: 20161128 |