CN105872097B - Expansible anycast's method and system based on rewriting in a kind of NDN - Google Patents
Expansible anycast's method and system based on rewriting in a kind of NDN Download PDFInfo
- Publication number
- CN105872097B CN105872097B CN201610388908.3A CN201610388908A CN105872097B CN 105872097 B CN105872097 B CN 105872097B CN 201610388908 A CN201610388908 A CN 201610388908A CN 105872097 B CN105872097 B CN 105872097B
- Authority
- CN
- China
- Prior art keywords
- request
- layer scheduler
- response message
- server
- layer
- 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.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Disclose a kind of expansible anycast's method based on rewriting in NDN, comprising: client sends the first request to network；Intermediate router forwarding first is requested to some first layer scheduler；First layer scheduler selects server zone, and rewrites the first request as the second request；Second layer scheduler is requested to the second layer scheduler dispatches second of selected server zone, and selects server, and rewriteeing the second request is that third is requested, and third is forwarded to request to selected server；Server returns to the first response message to second layer scheduler；It is the second response message that second layer scheduler, which rewrites the first response message, and returns to the second response message to first layer scheduler；It is third response message that first layer scheduler, which rewrites the second response message, and returns to third response message to client.Method of the invention can meet diversified anycast's demand in NDN under the premise of not destroying NDN router forwarding logic, overcome the problems, such as that anycast's is expansible.
Description
Technical field
The present invention relates to name data network (Named Data Networking, NDN) technical fields more particularly to one
Expansible anycast's method and system based on rewriting in kind NDN.
Background technique
Currently, user has switched to the access of internet based on the point-to-point communication based on content obtains.And it is traditional
TCP/IP network only transferring content, not perceived content, to cause a large amount of redundant flow transmission on network.In order to solve
Due to the content explosion that content obtains and causes, research circle proposes NDN network using content as center, realizes content and ground
The decoupling of location and sender and recipients, and ubiquitous built-in caching is provided to meet user to content with heavy-tailed feature
Asynchronous access.
Existing internet there are it is many it is large-scale with hundreds of millions service, such as Google, Facebook, wechat etc..This
A little services are usually constructed with one group of server or server cluster for being physically distributed but providing same services.For a user, this
Class service substantially belongs to Anycast service.But the transmission mode of existing NDN only provides the anycast simply based on anycast's routing
Mechanism is unable to satisfy flexible and changeable anycast's demand.Therefore, it is necessary to propose to be able to satisfy appointing for diversified demand in a kind of NDN
Technology is broadcast, especially can solve the expansible problem of anycast.
Summary of the invention
The present invention in order to solve the above technical problems, provide expansible anycast's method and system based on rewriting in a kind of NDN,
The forwarding logic of CCN content router forwarding engine can not be destroyed.The technical solution is as follows:
On the one hand, the invention proposes a kind of expansible anycast's method in NDN based on rewriting, include the following steps:
Client sends the first request to network；
Intermediate router is based on anycast's routing and the first request is forwarded to some first layer scheduler；
Server zone of the first layer scheduler according to the selection first class services request of the first preset strategy；
First request is rewritten as the second request by first layer scheduler；
Second layer scheduler is requested to the second layer scheduler dispatches second of selected server zone；
Second layer scheduler is according to a server in the second preset strategy selection bundle of services；
Second request is rewritten as third according to the agreement between second layer scheduler and server by second layer scheduler asks
It asks；
Third request is transmitted to selected server by second layer scheduler；
Server returns to the first response message to second layer scheduler；
First response message is rewritten as according to the agreement between second layer scheduler and server by second layer scheduler
Two response messages；
Second response message is returned to corresponding first layer according to the arrival port of the second request and dispatched by second layer scheduler
Device；
Second response message is rewritten as third response message by first layer scheduler；
Third response message is returned to client by first layer scheduler.
Further, the Service name of first request is an Anycast service name；First request is led to by intermediate router
The anycast's routing mechanism for crossing NDN is forwarded to some first layer scheduler.In order to guarantee the correct operation of this process, each first
Layer scheduler is all to the network notifications Anycast service name or prefix.
Further, the entitled second layer scheduler of service of second request relies on Service name；Second request is according to NDN
Routing procedure be forwarded to second layer scheduler.In order to guarantee that the process is correctly run, second layer scheduler is needed to routing system
System notice second layer scheduler relies on Service name or its prefix.
Further, the third request includes that can identify the mark of selected server.
Further, the entitled second layer identical with the Service name of the second request of the service of second response message is dispatched
Device relies on Service name；Second response message returns to first layer tune by the reverse path hop-by-hop of the second request message forward-path
Spend device.
Further, the entitled generic service identical with the Service name of the first request of the service of the third response message
Name；Third response message returns to client by the reverse path hop-by-hop of the first request message forward-path.
Further, first request can optionally include the traffic identifier of client generation, which is replicated
Into the second request, third request, the first response, the second response and third response.When first layer scheduler receive first
When request includes traffic identifier, first layer scheduler obtains the history scheduling decision with identical traffic identifier in same session first
Information, it is no using history decision scheduling result as first scheduling result requested when there are history scheduling decision information
It then, is the first request selecting server zone based on the first preset strategy.
On the other hand, the present invention proposes expansible anycast's system based on rewriting in a kind of NDN, comprising:
Client: for generating and sending the first request to network, third response message is received；
First layer scheduler: for receiving the first request, foundation from network to network notifications generic service name or its prefix
First preset strategy selects server zone, rewrites the first request for the second request, to selected second layer scheduler forwarding the
Two requests receive the second response message that second layer scheduler returns, and the second response message of rewriting is third response message, to visitor
Family end returns to third response message；
Second layer scheduler: it for relying on Service name or its prefix to network notifications second layer scheduler, receives second and asks
It asks, selects server according to the second preset strategy, rewriteeing the second request is that third is requested, and forwards third to selected server
Request receives the first response message from server, and the first response message of rewriting is the second response message, is returned to first layer scheduler
Return the second response message；
Server: for receiving third request, generate and return the first response message；
Intermediate router: establishing for the rule according to NDN and update route forwarding table, asks according to fib table forwarding first
The second request of summation, returns to the second response message and third response message according to PIT table.
The invention adopts the above technical scheme compared with prior art, has following technical effect that
Through the invention, diversified anycast's demand can be supported in NDN, especially can effectively solve scaling concern,
Server can be neatly selected according to server state.In addition, technology proposed by the invention does not destroy NDN content router
Forward the forwarding logic of engine.
The additional aspect of the present invention and advantage will be set forth in part in the description, these will become from the following description
Obviously, or practice through the invention is recognized.
Detailed description of the invention
Fig. 1 shows the Anycast service schematic diagram of a scenario of an embodiment according to the present invention.
Fig. 2 shows expansible anycast's method flow diagrams in the NDN of an embodiment according to the present invention based on rewriting.
The entity that Fig. 3 shows expansible anycast's method in the NDN of an embodiment according to the present invention based on rewriting is handed over
Mutually figure.
Fig. 4 shows the signal of expansible anycast's system deployment in the NDN of an embodiment according to the present invention based on rewriting
Figure.
Specific embodiment
Embodiments of the present invention are described below in detail, the example of the embodiment is shown in the accompanying drawings, wherein from beginning
Same or similar element or element with the same or similar functions are indicated to same or similar label eventually.Below by ginseng
The embodiment for examining attached drawing description is exemplary, and for explaining only the invention, and is not construed as limiting the claims.
Those skilled in the art of the present technique are appreciated that unless expressly stated, singular " one " used herein, " one
It is a ", " described " and "the" may also comprise plural form.It is to be further understood that being arranged used in specification of the invention
Diction " comprising " refer to that there are the feature, integer, step, operation, element and/or component, but it is not excluded that in the presence of or addition
Other one or more features, integer, step, operation, element, component and/or their group.It should be understood that when we claim member
Part is " connected " or when " coupled " to another element, it can be directly connected or coupled to other elements, or there may also be
Intermediary element.In addition, " connection " used herein or " coupling " may include being wirelessly connected or coupling.Wording used herein
"and/or" includes one or more associated any cells for listing item and all combinations.
Those skilled in the art of the present technique are appreciated that unless otherwise defined, all terms used herein (including technology art
Language and scientific term) there is meaning identical with the general understanding of those of ordinary skill in fields of the present invention.Should also
Understand, those terms such as defined in the general dictionary, which should be understood that, to be had and the meaning in the context of the prior art
The consistent meaning of justice, and unless defined as here, it will not be explained in an idealized or overly formal meaning.
Fig. 1 shows anycast's schematic diagram of a scenario of an embodiment according to the present invention.In figure, one large-scale service passes through more
A server zone being geographically spread out provides service.These M server zone Site 1, Site being geographically spread out
2 ..., Site M is connected by network.Each Site has multiple servers, such as Site k includes NkA server.Each
Server all provides identical service.The client for desiring access to service issues service request by network, finally by some clothes
The server service request being engaged in device group.The network for connecting client and each server zone is NDN network.
Expansible anycast's method and system introduces first layer scheduler and second layer scheduling in NDN proposed by the present invention
Both entities of device, as shown in Figure 3.There are multiple first layer schedulers for system, for receiving the first request of client sending,
And suitable server zone is selected for it.Purpose using multiple first layer schedulers is that first layer scheduler is avoided to become system
Performance bottleneck and single point failure.Each server zone has a second layer scheduler, for selecting one in server zone
A server.Second layer scheduler is usually located at the same network with some server zone, the shop front as server zone.
Fig. 2 shows expansible anycast's method flow diagrams in the NDN of an embodiment according to the present invention based on rewriting.Tool
Body includes the following steps:
1) client sends the first request to network.
The Virtual Service name for the entitled service of service in the first request that client is sent, such as/foo.com/
generic-service-name.Optionally, in order to support the anycast based on stream, a traffic identifier is can be generated in client
Flow-tag, and be attached to behind above-mentioned Virtual Service name, as/foo.com/generic-service-name/flow-
tag.If the first request that client generates is the subsequent request in a session based on stream, the flow- of first request
Tag directly replicates the flow-tag of the request between in the stream.
In order to enable some first layer scheduler, each first layer tune can be forwarded to the request of above-mentioned Service name prefix
Spending device after deployment need to notice to the route system of NDN with the routing entry of the entitled prefix of the Virtual Service of the service, i.e. ,/
foo.com/generic-service-name.Optionally, first layer scheduler can be by the routing entry polymerizeing to routing
System notice, such as/foo.com.The routing entry notice message, which is carried through Routing Protocol to the router of NDN network, to spread,
And inject route forwarding table FIB.Substantially, which is anycast's routing entry, and intermediate router passes through routing association
View calculates the forwarding port for suitably reaching some first layer scheduler.
2) intermediate router is based on anycast's routing and the first request is forwarded to some first layer scheduler.
After receiving the first request, intermediate router matches suitable port according to the forwarding entry in FIB, by its hop-by-hop
It is forwarded to some first layer scheduler.Since multiple first layer schedulers all have advertised identical routing entry, it is different
What client issued may be forwarded to different first layer schedulers to the request of same services, and identical client exists
What different moments issued may also can be forwarded to different first layer schedulers to the request of same services.In order to support to be based on
The Anycast service of stream, all first layer schedulers need to guarantee by certain mode that the request for belonging to the same stream is forwarded to
The same second layer scheduler.
3) server zone of the first layer scheduler according to the first preset strategy selection service request.
After the first request has been forwarded to some first layer scheduler according to anycast's routing, if first request is not wrapped
It includes traffic identifier or first request is first request in some session, then first layer scheduler is according to the first preset strategy
Select the server zone of first class services request.For this purpose, first layer scheduler at least needs to configure the information of all server zones.
Server zone can also by the state of itself periodically or Real-time Feedback give all first layer schedulers, so that its progress is more complicated
Request scheduling.First layer scheduler can randomly choose a server zone first class services using simple randomized policy and ask
It asks, scheduling can also be made requests using rotation strategy, it can also be according to state (such as real time load, remaining clothes of server zone
Business ability etc.) make requests scheduling.The first preset strategy that the present invention uses first layer scheduler is without restriction.
When the first request includes traffic identifier, first layer scheduler needs carry out the request scheduling based on stream.If this
One request is first request in a session, then first layer scheduler is based on the first preset strategy and selects server zone；Such as
Fruit first request is the subsequent request in a session, then first layer scheduler is constituted whole using all first layer schedulers
Be before body first request in the session the result that selects of progresss server zone as first selection result requested,
Will this first request be assigned to service the session in first request server zone.Since whole system uses anycast road
By the first request is routed to some first layer scheduler, therefore, multiple requests in the same session may be routed to
Different first layer schedulers, such as first first request Req in entire session1It is routed to first layer scheduler i, and
Some subsequent first request Req in the sessionrIt is routed to first layer scheduler j.At this point, first layer scheduler j needs obtain
First layer scheduler i is obtained to Req1Scheduling result, thus as to ReqrScheduling result.This need first layer scheduler it
Between carry out certain collaboration implicitly or explicitly.A kind of method is that all first layer schedulers all use same mapping algorithm,
Flow-tag is mapped, so that the request with identical flow-tag can be mapped to phase by different first layer schedulers
Same server zone, the mapping algorithm can be simple HASH algorithm, be also possible to more complex HRW (Highest
Random Weight) algorithm.The benefit of this method be it is simple, without carrying out explicit cooperation between first layer scheduler, the disadvantage is that
The dynamic load information of server group terminal is difficult to be utilized.Second method is, when some first request with traffic identifier reaches
When, it is primarily based on traffic identifier and removes inquiry stream scheduling decision table, if having had the scheduling decision as a result, i.e. in stream scheduling decision table
There is the scheduling for the request in the stream before, has then used the scheduling decision as a result, otherwise indicating that the request is in stream
First request, the scheduling decision made requests according to the first preset strategy select suitable server zone, and by scheduling decision
As a result it is saved in stream scheduling decision table.The stream scheduling decision table can store in centralized manner, can also be with distribution
The mode of formula stores, such as distribution HASH table, no matter is stored using which kind of mode, all first layer schedulers can be to it
Directly accessed.The third method is that, when some first request with traffic identifier reaches, the first layer scheduler is first
Inquire whether other first layer schedulers have the scheduling result to the traffic identifier using certain vlan query protocol VLAN, if other the
One layer of scheduler all not to the scheduling result of the traffic identifier, is then scheduled it according to the first preset strategy, otherwise, uses
The scheduling result of other first layer schedulers.The advantages of this method is that each first layer scheduler can be by scheduling decision result
It is stored in local.There is a method in which first layer scheduler and second layer scheduler can be allowed to cooperate.When first layer is dispatched
When device receives the first request with traffic identifier, the second layer scheduler dispatches inquiry request of Xiang Suoyou is asked whether
There is some second layer scheduler to be responsible for servicing the request of the traffic identifier.If nothing, scheduling is made requests using the first preset strategy,
Otherwise, then the scheduling result of front is used.No matter which kind of method is used, how the present invention knows to same first layer scheduler
The method of the schedule history knowledge of stream in session is without restriction.
4) the first request is rewritten as the second request by first layer scheduler.
After the server zone that first class services request has been determined, the first request is then rewritten as second by first layer scheduler is asked
It asks, and records the rewriting behavior.The Service name that the entitled second layer scheduler of request of second request relies on, for example, such as
Shown in Fig. 3, if first layer scheduler has selected k-th of server zone site k, the request name of corresponding second request can be with
It is /SITEk/ foo.com/generic-service-name or/SITEk/foo.com/generic-service-name/
flow-tag.The regenerative recording behavior at least will include between the Service name of the first request and the Service name of the second request
Mapping relations successfully can execute response message according to the mapping relations when continuing response upon receipt so as to first layer scheduler
Reverse overwrite.
5) the second request is transmitted to the second layer scheduler of selected server zone by first layer scheduler.
After first layer scheduler requests successfully to be rewritten as the second request by first, the forwarding based on NDN is requested by second
Logical forwarding gives selected second layer scheduler.For this purpose, the second layer scheduler should be to network notifications second layer scheduler
The Service name of dependence or its prefix, in the example shown in Fig. 3, Site k should into network notice/SITEk/foo.com/
generic-service-name,/SITEk/ foo.com or/SITEk。
6) server of the second layer scheduler according to the second preset strategy selection the second request of service.
Service after second layer scheduler receives the second request, according to the second preset strategy selection the second request of service
Device.For this purpose, second layer scheduler at least needs to configure the server info of the server zone at place.Server can also be by itself
State periodically or Real-time Feedback give second layer scheduler, so that it carries out more complicated request scheduling.Second layer scheduler can
It is requested, can also be made requests using rotation strategy with randomly choosing a server service second using simple randomized policy
Scheduling can also make requests scheduling according to the state (such as real time load, remaining service ability) of server.The present invention is to
The second preset strategy that two layers of scheduler uses is without restriction.
If including traffic identifier in the second request, show that client is desired with the scheduling based on stream.At this point, the second layer
Scheduler needs to make requests scheduling based on traffic identifier.Second layer scheduler identifies traffic identifier first, then in stream forwarding list
In search whether to have existed the dispatching record of the traffic identifier.If it does not exist, then show that second request is second layer scheduling
First request of device forwarding, then select the server service request based on the second preset strategy, while in stream forwarding list
In record the forwarding behavior, which includes at least<flow-tag, and server-ID>two, i.e. traffic identifier and service should
The server identification of traffic identifier.If having existed the dispatching record of the traffic identifier, second layer scheduler is no longer based on second
Preset strategy select the server service request, and be based on directly on the trade-off decision before recording in stream forwarding list as a result,
By the identical server service request.
7) the second request is rewritten as third according to the agreement between second layer scheduler and server by second layer scheduler
Request.
After the server that the second request of service has been determined, the second request is then rewritten as third by second layer scheduler is asked
It asks, and records the rewriting behavior.Second layer scheduler is carried out according to the agreement run between second layer scheduler and server
The rewriting of request, second layer scheduler are required to be transmitted to the request of revised third based on the agreement selected
Server.For example, request Service name can be rewritten as taking if supporting NDN agreement between second layer scheduler and server
The request Service name that business device relies on, such as/server-ID/foo.com/generic-service-name or/server-ID/
foo.com/generic-service-name/flow-tag.Wherein server-ID is the mark of selected server.Such as
Shown in Fig. 3, it is assumed that the second layer scheduler of k-th of server zone has selected j-th of server to service third request, the service
Device is identified as SNkj, then the request name of third request can be/SNkj/ foo.com/generic-service-name or/
SNkj/foo.com/generic-service-name/flow-tag.For another example, if transported between second layer scheduler and server
Capable is ICP/IP protocol, then second layer scheduler can construct an IP packet, and source address is the IP of second layer scheduler
Address, destination address is the IP address of selected server, while being determined and being taken according to Service name generic-service-name
Destination port is set corresponding port numbers by the port numbers of business, and in the other parameters information and request body in request name
Other information rewritten and encapsulated according to the consensus standard run.During rewriting, it is possible to need to be implemented and disappear
Breath integrality recalculates, such as the calculating of IP packet checksum.The present invention is between second layer scheduler and server
The agreement of operation and corresponding rewriting rule are without restriction.
8) third request is transmitted to selected server by second layer scheduler.
After second layer scheduler requests successfully to be rewritten as third request by second, third is requested to give based on protocol forward
Selected server, meanwhile, the rewriting behavior is recorded on second layer scheduler.The rewriting record behavior is at least wanted
The mapping relations of the mark of Service name and third request including the second request, ring so that second layer scheduler continues upon receipt
At once the reversed rewriting of response message can be successfully executed according to the mapping relations.
9) server is to the first response message of second layer scheduler dispatches.
After server receives third request, the request is serviced, and construct the first response message.The response message is to service
The protocol format building run between device and second layer scheduler, and second layer scheduler is given based on the protocol forward.For example, such as
What is run between fruit second layer scheduler and server is NDN agreement, then the Service name of first response message be/
Server-ID/foo.com/generic-service-name or/server-ID/foo.com/generic-service-
Name/flow-tag is /SN in the example shown in Fig. 3kj/ foo.com/generic-service-name or/SNkj/
foo.com/generic-service-name/flow-tag.The response message is returned to along the reverse path that third is requested
Second layer scheduler.For another example, if what is run between second layer scheduler and server is IP agreement, the second response message
Destination address and destination port are the source address and source port of third request, which is forwarded to the by IP agreement
Two layers of scheduler.
10) the first response message is rewritten as by second layer scheduler according to the agreement between second layer scheduler and server
Second response message.
After second layer scheduler receives the first response message, the rewriting behavior record that will be requested according to second, by first
Response message is rewritten as the second response message.For example, as shown in Figure 3, it is assumed that run between second layer scheduler and server
It is NDN agreement, then by Service name/SN of the first response messagekj/ foo.com/generic-service-name or/SNkj/
Foo.com/generic-service-name/flow-tag is rewritten as/SITEk/foo.com/generic-service-
Name or/SITEk/foo.com/generic-service-name/flow-tag.When rewriting, second layer scheduler may be used also
It can need update message signature and key information simultaneously.And if what is run between second layer scheduler and server is IP association
View, obtains the identification information of the first response message message, including<source address, destination address, source port, destination port>first,
Then the identification information of construction third request accordingly is changed according to the identification information of the Service name of the second request and third request
Write as the second response message.When executing rewriting, in addition to carrying out protocol conversion, second layer scheduler also needs to be arranged data packet
Key information and information signature information.
11) the second response message is returned to corresponding first layer scheduler by second layer scheduler.
After second layer scheduler the second response message of Successful construct, by the second response message along the forwarding of the second request
The reverse path in path returns to corresponding first layer scheduler.
12) the second response message is rewritten as third response message by first layer scheduler.
After first layer scheduler receives the second response message, the rewriting behavior record that will be requested according to first, by second
Response message is rewritten as third response message.First layer scheduler will search the first request according to the Service name of the second response message
Rewriting behavior record, to obtain the Service name of third response message.In example as shown in Figure 3, since the second response disappears
The service of breath is entitled/SITEk/ foo.com/generic-service-name or/SITEk/foo.com/generic-
Service-name/flow-tag, search request rewrite record obtain corresponding third response message Service name should be/
Foo.com/generic-service-name or/foo.com/generic-service-name/flow-tag.It is rewriting
When, first layer scheduler it may also be desirable to while update message is signed and key information.
13) third response message is returned to client by first layer scheduler.
After first layer scheduler Successful construct third response message, by third response message along the forwarding of the first request
The reverse path in path returns to client.
The entity that Fig. 3 shows expansible anycast's method in the NDN of an embodiment according to the present invention based on rewriting is handed over
Mutually figure.Wherein, step (1)-(13) respectively correspond 13 steps in Fig. 2.
Fig. 4 shows the signal of expansible anycast's system deployment in the NDN of an embodiment according to the present invention based on rewriting
Figure, comprising:
Client: for generating and sending the first request to network, third response message is received from network；
First layer scheduler: for receiving the first request, foundation from network to network notifications generic service name or its prefix
First preset strategy selects server zone, rewrites the first request for the second request, to selected second layer scheduler forwarding the
Two requests receive the second response message that second layer scheduler returns, and the second response message of rewriting is third response message, to visitor
Family end returns to third response message；
Second layer scheduler: it for relying on Service name or its prefix to network notifications second layer scheduler, receives second and asks
It asks, selects server according to the second preset strategy, rewriteeing the second request is that third is requested, and forwards third to selected server
Request receives the first response message from server, and the first response message of rewriting is the second response message, is returned to first layer scheduler
Return the second response message；
Server: for receiving third request, generate and return the first response message；
Intermediate router: establishing for the rule according to NDN and update route forwarding table, asks according to fib table forwarding first
The second request of summation, returns to the second response message and third response message according to PIT table.
The technical solution proposed through the invention can meet diversified anycast's demand, especially in NDN network
It solves the scaling concern of anycast's routing and supports the anycast based on stream.And the offer of the ability does not change the NDN network architecture
The processing logic of content naming rule and NDN forwarding engine.
Those skilled in the art of the present technique are appreciated that the present invention can be related to for executing in operation described herein
The equipment of one or more operations.The equipment can specially design and manufacture for required purpose, or also may include
Known device in general purpose computer, the general purpose computer are activated or are reconstructed with having the procedure selection being stored in it.This
The computer program of sample can be stored in equipment (for example, computer) readable medium or be stored in be referred to suitable for storage electronics
It enables and is coupled in any kind of medium of bus respectively, the computer-readable medium is including but not limited to any kind of
Disk (including floppy disk, hard disk, CD, CD-ROM and magneto-optic disk), immediately memory (RAM), read-only memory (ROM), electricity can be compiled
Journey ROM, electrically erasable ROM (EPROM), electrically erasable ROM (EEPROM), flash memory, magnetic card or light card.It is readable
Medium includes for by any mechanism of the readable form storage or transmission information of equipment (for example, computer).For example, readable
Medium include immediately memory (RAM), read-only memory (ROM), magnetic disk storage medium, optical storage medium, flash memory device, with
The signal (such as carrier wave, infrared signal, digital signal) etc. that electricity, light, sound or other forms are propagated.
Those skilled in the art of the present technique be appreciated that can be realized with computer program instructions these structure charts and/or
The combination of each frame and these structure charts and/or the frame in block diagram and/or flow graph in block diagram and/or flow graph.It can be by this
The processor that a little computer program instructions are supplied to general purpose computer, special purpose computer or other programmable data processing methods comes
Machine is generated, is used for be performed instruction by the processor of computer or other programmable data processing methods and create
Realize the method specified in the frame or multiple frames of structure chart and/or block diagram and/or flow graph.
Those skilled in the art of the present technique have been appreciated that in the present invention the various operations crossed by discussion, method, in process
Steps, measures, and schemes can be replaced, changed, combined or be deleted.Further, each with having been crossed by discussion in the present invention
Kind of operation, method, other steps, measures, and schemes in process may also be alternated, changed, rearranged, decomposed, combined or deleted.
Further, in the prior art to have and the step in various operations, method disclosed in the present invention, process, measure, scheme
It may also be alternated, changed, rearranged, decomposed, combined or deleted.
The above is only some embodiments of the invention, it is noted that for the ordinary skill people of the art
For member, various improvements and modifications may be made without departing from the principle of the present invention, these improvements and modifications are also answered
It is considered as protection scope of the present invention.
Claims (7)
1. a kind of expansible anycast's method in NDN based on rewriting, includes the following steps:
Client sends the first request to network；
Intermediate router is based on anycast's routing and the first request is forwarded to some first layer scheduler；
Server zone of the first layer scheduler according to the selection first class services request of the first preset strategy；
First request is rewritten as the second request by first layer scheduler；
Second layer scheduler is requested to the second layer scheduler dispatches second of selected server zone；
Second layer scheduler is according to a server in the second preset strategy selection bundle of services；
Second request is rewritten as third request according to the agreement between second layer scheduler and server by second layer scheduler；
Third request is transmitted to selected server by second layer scheduler；
Server returns to the first response message to second layer scheduler；
First response message is rewritten as the second sound according to the agreement between second layer scheduler and server by second layer scheduler
Answer message；
Second response message is returned to corresponding first layer scheduler according to the arrival port of the second request by second layer scheduler；
Second response message is rewritten as third response message by first layer scheduler；
Third response message is returned to client by first layer scheduler；
First request, it is characterised in that:
The Service name of first request is an Anycast service name；
Each first layer scheduler is to the network notifications Anycast service name or prefix；
First request is forwarded to some first layer scheduler by anycast's routing mechanism of NDN by intermediate router；
Wherein, the second request is transmitted to second layer scheduler by the first layer scheduler, comprising:
Second layer scheduler relies on Service name or its prefix to route system notice second layer scheduler；
The entitled second layer scheduler of service of second request relies on Service name；
Second request is forwarded to second layer scheduler according to the routing procedure of NDN.
2. the method as described in claim 1, the second request is rewritten as third by the second layer scheduler requests, and feature exists
In:
Third request includes that can identify the mark of selected server.
3. the method as described in claim 1, second response message, it is characterised in that:
The entitled second layer scheduler identical with the Service name of the second request of the service of second response message relies on Service name；
Second response message returns to first layer scheduler by the reverse path hop-by-hop of the second request message forward-path.
4. the method as described in claim 1, the third response message, it is characterised in that:
The entitled generic service name identical with the Service name of the first request of the service of third response message；
Third response message returns to client by the reverse path hop-by-hop of the first request message forward-path.
5. the method as described in claim 1, which is characterized in that first request includes the traffic identifier that client generates.
6. method as claimed in claim 5, which is characterized in that the traffic identifier is copied to the second request, third request, the
In one response, the second response and third response.
7. the method as described in claim 1, which is characterized in that when the first request that first layer scheduler receives includes failing to be sold at auction
When knowledge, comprising:
First layer scheduler obtains the history scheduling decision information with identical traffic identifier in same session；
Scheduling result when there are history scheduling decision information, using history decision scheduling result as first request；
It is the first request selecting server zone based on the first preset strategy when history scheduling decision information is not present.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610388908.3A CN105872097B (en) | 2016-06-02 | 2016-06-02 | Expansible anycast's method and system based on rewriting in a kind of NDN |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610388908.3A CN105872097B (en) | 2016-06-02 | 2016-06-02 | Expansible anycast's method and system based on rewriting in a kind of NDN |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105872097A CN105872097A (en) | 2016-08-17 |
| CN105872097B true CN105872097B (en) | 2019-04-30 |
Family
ID=56676710
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610388908.3A Active CN105872097B (en) | 2016-06-02 | 2016-06-02 | Expansible anycast's method and system based on rewriting in a kind of NDN |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105872097B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110868452B (en) * | 2019-10-23 | 2021-12-07 | 中国建设银行股份有限公司 | Data transmission method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102012931A (en) * | 2010-12-01 | 2011-04-13 | 北京瑞信在线系统技术有限公司 | Filter cache method and device, and cache system |
| CN102546774A (en) * | 2011-12-27 | 2012-07-04 | 厦门市美亚柏科信息股份有限公司 | CDN (content distribution network) routing method for secondary redirection and system |
| CN103701619A (en) * | 2013-10-22 | 2014-04-02 | 上海交通大学 | Internet content distribution method based on CDN (Content Distribution Network) and data center dynamic selection |
| CN103888999A (en) * | 2012-12-19 | 2014-06-25 | 中国移动通信集团公司 | WebCache service and CDN service fusion method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130103785A1 (en) * | 2009-06-25 | 2013-04-25 | 3Crowd Technologies, Inc. | Redirecting content requests |
-
2016
- 2016-06-02 CN CN201610388908.3A patent/CN105872097B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102012931A (en) * | 2010-12-01 | 2011-04-13 | 北京瑞信在线系统技术有限公司 | Filter cache method and device, and cache system |
| CN102546774A (en) * | 2011-12-27 | 2012-07-04 | 厦门市美亚柏科信息股份有限公司 | CDN (content distribution network) routing method for secondary redirection and system |
| CN103888999A (en) * | 2012-12-19 | 2014-06-25 | 中国移动通信集团公司 | WebCache service and CDN service fusion method and device |
| CN103701619A (en) * | 2013-10-22 | 2014-04-02 | 上海交通大学 | Internet content distribution method based on CDN (Content Distribution Network) and data center dynamic selection |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105872097A (en) | 2016-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11588886B2 (en) | Managing replication of computing nodes for provided computer networks | |
| JP6306640B2 (en) | Providing logical networking capabilities for managed computer networks | |
| JP5536362B2 (en) | Method for facilitating communication in a content-centric network | |
| US8683023B1 (en) | Managing communications involving external nodes of provided computer networks | |
| CN111612466B (en) | Consensus and resource transmission method, device and storage medium | |
| KR20160076445A (en) | System and method for efficient name-based content routing using link-state information in information-centric networks | |
| CN102833329A (en) | Distributed storage of routing information in link state protocol controlled network | |
| CN103825826B (en) | The implementation method and device of a kind of dynamic routing | |
| EP2664112B1 (en) | Method and apparatus for managing the mobility of mobile networks | |
| CN106101201B (en) | Based on the expansible anycast's method and system for redirecting and rewriteeing in a kind of NDN | |
| EP2223501B1 (en) | Publish/subscribe networks | |
| CN106130906B (en) | Expansible anycast's method and system based on redirection in a kind of NDN | |
| CN105872097B (en) | Expansible anycast's method and system based on rewriting in a kind of NDN | |
| CN102037711A (en) | Limiting storage messages in peer to peer network | |
| CN106101200B (en) | Based on routing and the anycast's method and system rewritten in a kind of NDN | |
| CN105306571B (en) | The method and system of branch held state anycast in NDN based on routing | |
| CN105915450B (en) | Anycast's method and system based on redirection in a kind of NDN | |
| CN105959381B (en) | Anycast's method and system based on rewriting in a kind of NDN | |
| CN105847448B (en) | Based on routing and the anycast's method and system redirected in a kind of NDN | |
| CN105897928B (en) | Based on the anycast's method and system for redirecting and rewriteeing in a kind of NDN | |
| CN105323317A (en) | Method and system for supporting stateful anycast in NDN based on analyzer | |
| JP6179141B2 (en) | Data transfer system and network load reducing method | |
| Ahir et al. | Content centric networking and its applications | |
| Parisis et al. | A Node Design and a Framework for Development and Experimentation for an Information-Centric Network |
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 |