CN101447930B - Message processing method and device thereof - Google Patents
Message processing method and device thereof Download PDFInfo
- Publication number
- CN101447930B CN101447930B CN2008101891027A CN200810189102A CN101447930B CN 101447930 B CN101447930 B CN 101447930B CN 2008101891027 A CN2008101891027 A CN 2008101891027A CN 200810189102 A CN200810189102 A CN 200810189102A CN 101447930 B CN101447930 B CN 101447930B
- Authority
- CN
- China
- Prior art keywords
- message
- fragment
- fragment message
- destination
- protocol stack
- 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
Images
Landscapes
- Communication Control (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention discloses a message processing method. The message processing method comprises the following steps: receiving a fragment message and a non-fragment message which are sent by a source terminal; and sending the fragment message and the non-fragment message to a protocol stack of a target terminal APP for processing by the same path sequentially. The embodiment of the invention further discloses a message processing device. The message processing method and the device thereof are applicable to processing the fragment message and the non-fragment message in a distributed system by the target terminal.
Description
Technical field
The present invention relates to communication technical field, relate in particular to the method and apparatus that a kind of message is handled.
Background technology
At present, along with the develop rapidly of data communication technology, distributed router device has replaced centralized router device gradually, and distributed notion has also expanded to software field.The distributed handling property that can improve router to a great extent of IP stack, IP stack can distribute according to the router veneer, also can be according to APP (Application, upper layer application based on agreement) distributes, thereby accomplish that each APP independently receives and dispatches message, improve the performance of packet sending and receiving.
So-called according to the APP distribution, promptly each APP has the protocol stack of oneself.When source end APP sends message, if the length of message then needs message is carried out burst greater than the MTU (MTU) of network, when fragment message arrives destination, need recombinate to message, be assembled into a complete message up sending and give destination APP.The message that destination receives comprises fragment message and non-fragment message, and usually, destination will be delivered to the independently concentrated reorganization of protocol stack on the fragment message that receive, and the message after the reorganization is directly by the protocol stack of delivering to destination APP on the described independently protocol stack; And for non-fragment message, destination directly will be delivered to the protocol stack of destination APP on it.
In realizing process of the present invention, the inventor finds that there are the following problems at least in the prior art:
The fragment message that destination receives need be recombinated earlier, deliver to the protocol stack of destination APP again, but not fragment message is delivered to the protocol stack of destination APP on directly, because processing mode difference, the path difference of being walked, may cause fragment message between recombination phase, follow-up non-fragment message has been delivered to the protocol stack of destination APP on directly, the order that destination receives fragment message and non-fragment message with on the order delivered in the protocol stack of APP different, thereby cause destination fragment message and non-fragment message out of order problem to occur.
Summary of the invention
The method and apparatus that embodiments of the invention provide a kind of message to handle can solve the out of order problem that occurs when the destination message is recombinated in the distributed system.
For achieving the above object, embodiments of the invention adopt following technical scheme:
The method that a kind of message is handled comprises:
Fragment message and non-fragment message that the reception sources end sends;
The protocol stack that described fragment message and non-fragment message are delivered to destination APP on successively by same path is handled.
The device that a kind of message is handled comprises:
Receiving element is used for fragment message and non-fragment message that the reception sources end sends;
On send processing unit, be used for the protocol stack that fragment message that described receiving element is received and non-fragment message deliver to destination APP on successively by same path and handle.
The method and apparatus that message that the embodiment of the invention provides is handled, fragment message and non-fragment message that destination reception sources end sends are delivered to destination APP corresponding protocols stack by same path on successively with described fragment message and non-fragment message and are handled.Compared with prior art, the order that destination receives fragment message and non-fragment message with on to deliver to the order of protocol stack of destination APP identical, the out of order problem that can avoid non-fragment message and fragment message to cause owing to the path of being walked is different.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art below, conspicuous, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
The method flow diagram that Fig. 1 handles for the message that the embodiment of the invention one provides;
The method flow diagram that Fig. 2 handles for the message that the embodiment of the invention two provides;
The method flow diagram that Fig. 3 handles for the message that the embodiment of the invention three provides;
The apparatus structure schematic diagram that Fig. 4 handles for the message that the embodiment of the invention four provides;
The apparatus structure schematic diagram that Fig. 5 handles for the message that the embodiment of the invention five provides.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
The method and apparatus that embodiments of the invention provide a kind of message to handle.For the advantage that makes technical solution of the present invention is clearer, the present invention is elaborated below in conjunction with drawings and Examples.
The method that embodiments of the invention provide a kind of message to handle can solve the out of order problem that occurs when the destination message is recombinated in the distributed system.
Embodiment one
As shown in Figure 1, the method for described message processing comprises:
Fragment message and non-fragment message that S101, destination link layer reception sources end send;
S102, destination link layer deliver to by same path described fragment message and non-fragment message on successively the protocol stack of destination APP;
The protocol stack of S103, destination APP is handled the described message that receives, and the message after will handling sends to destination APP.
The method that the message that the embodiment of the invention provides is handled, fragment message and non-fragment message that destination link layer reception sources end sends, described fragment message and non-fragment message are delivered to the protocol stack of destination APP on successively by same path, protocol stack by destination APP is handled the described message that receives, and the message after will handling sends to destination APP.Compared with prior art, the destination link layer receives the order of fragment message and non-fragment message, with on to deliver to the order of protocol stack of destination APP identical, the out of order problem that can avoid non-fragment message and fragment message to cause owing to the path of being walked is different.
Embodiment two
In the present embodiment, described message is the initial IP message, the destination link layer is delivered to the protocol stack of destination APP on successively with the fragment message that receives and non-fragment message through same path, fragment message is recombinated after the last protocol stack of delivering to destination APP.
As shown in Figure 2, the method for described message processing comprises:
Fragment message and non-fragment message that S201, destination link layer reception sources end send.
Wherein, when the APP of source end sends message, if the length of message is greater than the MTU (MTU) of network, then need message is carried out burst, when fragment message arrives destination, need recombinate to message, be assembled into the APP that a complete message up sending is given destination.
For TCP (Transmission Control Protocol, transmission control protocol) and UDP (UserDatagram Protocol, User Datagram Protoco (UDP)) message, when the burst of message arrived destination, the burst of distinguishing this message according to protocol number, source IP address, purpose IP address and the IP ID (IP Identification) of message was the burst of which message.Wherein, the message fragment of same fragment message has same protocol number, source IP address, purpose IP address and IP ID, when fragment message is recombinated, all message fragments with same protocol number, source IP address, purpose IP address and IP ID are brought together recombinate, form a complete message.For protocol number, source IP address, purpose IP address and the identical situation of IP ID appear in the message fragment that prevents different fragment messages, avoid the fragment message reconstructing failure, distribute different IP ID for the message that may have same protocol number, source IP address and purpose IP address at the source end.For achieving the above object, can adopt in the following method any one:
Method one: message is divided into four types: first message of specified protocol number, second message of specified protocol number and source IP address, the 3rd message of specified protocol number and purpose IP address, and the 4th message of specified protocol number, source IP address and purpose IP address.
Because the message reorganization time is a burst of distinguishing message according to protocol number, source IP address, purpose IP address and IP ID, need create a Socket according to protocol number, source IP address, purpose IP address, source port number and destination slogan when APP sends message, therefore need guarantee agreement number, source IP address and purpose IP address may the identical IP ID scope that Socket distributed can not be identical.
Four kinds of classification according to above-mentioned message, Socket is divided into four types: a Socket of specified protocol number, the 2nd Socket of specified protocol number and source IP address, the Three S's ocket of specified protocol number and purpose IP address, and the 4th Socket of specified protocol number, source IP address and purpose IP address.
For the message that guarantees to have same protocol number, source IP address and purpose IP address distributes different IP ID, the Socket that only needs to guarantee to have same protocol number, source IP address and purpose IP address does not use same section IP ID.Concrete allocation rule is:
Socket for specified protocol number, follow following rule during distributing IP ID:
Rule one: for all Socket with same protocol number distribute different IP ID, for distributing different IPID with a Socket that the 2nd Socket, Three S's ocket and the 4th Socket have a same protocol number.
The 2nd Socket for specified protocol number and source IP address, follow following rule during distributing IP ID:
Rule two: for all have the different IP ID of the 2nd Socket distribution of same protocol number and source IP address, for distributing different IP ID, for distributing different IP ID with the 2nd Socket that the 4th Socket has same protocol number and a source IP address with the 2nd Socket that a Socket and Three S's ocket have a same protocol number.
Three S's ocket for specified protocol number and purpose IP address, follow following rule during distributing IP ID:
Rule three: for all have the different IPID of Three S's ocket distribution of same protocol number and purpose IP address, for distributing different IPID, for distributing different IPID with Three S's ocket that the 4th Socket has same protocol number and a purpose IP address with Three S's ocket that a Socket and the 2nd Socket have a same protocol number.
Three S's ocket for specified protocol number, source IP address and purpose IP address, follow following rule during distributing IP ID:
Rule four: for all the 4th Socket with same protocol number, source IP address and purpose IP address distribute different IP ID, for distributing different IPID with the 4th Socket that a Socket has a same protocol number, for distributing different IP ID, for distributing different IP ID with the 4th Socket that Three S's ocket has same protocol number and a purpose IP address with the 4th Socket that the 2nd Socket has same protocol number and a source IP address.
Wherein, after the Socket deletion, the IP ID resource that this Socket is taken reclaims, and distributes to other Socket and uses.When IP ID resource exhaustion, readjust the IP ID scope of all protocol stacks.
Method two:
Except according to the Socket distributing IP ID, can also come distributing IP ID according to protocol stack.For the protocol stack of each distribution, possess a unique sign, all use different IP ID scopes between the different protocol stacks, thereby avoid the possibility of repetition, take equally to manage concentratedly, the mode of dynamic assignment.With respect to according to Socket distributing IP ID, come distributing IP ID according to protocol stack, realize simply not needing to consider the complex situations of multiple Socket.But the IP ID in the different protocol stacks can not be multiplexing, for example, for the fragment message of reorganization, even protocol number, source IP address are identical with purpose IP ADI address incomplete, can not multiplexing same section IP ID.
Method three: when carrying out the forwarding of message flow, can also come distributing IP ID according to message flow, signs such as protocol number, source address, destination address and VPN index according to the message flow employing, when creating the transmit path of message flow, for the message flow that may have same protocol number, source address, destination address and VPN index distributes different IP ID.Specific implementation process and method one is similar, no longer sets forth at this.
S202, destination link layer deliver to by same path the fragment message that receives and non-fragment message on successively the protocol stack of destination APP.
The protocol stack of S203, destination APP is recombinated to the described fragment message that receives, and message and the described non-fragment message that receives that described reorganization finishes carried out the message decapsulation, at last, described decapsulation is intact message is sent to destination APP successively.
When fragment message arrives destination, need recombinate, and on deliver to destination APP.Because the network condition difference, load balancing or situation such as route saltus step packet-by-packet may appear in fragment message in sending the way, cause fragment message to receive up from different interfaces.Guaranteeing normally to finish reorganization, just must all be brought together all fragment messages and recombinate, also is so under the distributed protocol stack, have one independently IP stack handle the fragment message of reorganization.
Under the environment of distributed protocol stack, each protocol stack all possesses complete function, can realize the message reorganization.Therefore, the fragment message of initial IP is delivered on directly in the protocol stack of destination APP and recombinated, so just can guarantee the fragment message of initial IP and non-fragment message process be same protocol stack, walk same path, thereby avoid the generation of out of order problem.
Embodiment three
In the present embodiment, described message comprises initial IP message, TCP message and UDP message etc., different with embodiment two, the destination link layer is at first recombinated delivering to concentrated protocol stack on the fragment message that receives, the message that described reorganization is finished, and non-fragment message is then delivered to the protocol stack of destination APP on successively and is handled through same path.
As shown in Figure 3, the method for described message processing comprises:
Fragment message and non-fragment message that S301, destination link layer reception sources end send.
Equally, for protocol number, source I P address, purpose IP address and the identical situation of IP ID appear in the message fragment that prevents different fragment messages, avoid the fragment message reconstructing failure, distribute different IP ID for the message that may have same protocol number, source IP address and purpose IP address at the source end.The specific implementation process is no longer set forth at this with step S201.
S302, destination link layer are recombinated the convergence protocol stack of delivering on the fragment message that receives in the destination.
When the destination link layer receives fragment message, write down the information of this fragment message, then the convergence protocol stack of delivering on this fragment message in the destination is recombinated.
S303, destination link layer receive the message that described reorganization finishes.
Wherein, the processing of described fragment message and non-fragment message is carried out successively according to the order that the destination link layer receives.When described fragment message between recombination phase, the destination link layer receives follow-up fragment message or non-fragment message, then the destination link layer will carry out buffer memory to described subsequent packet, give on the ability after the fragment message reorganization of waiting for the front finishes.Wherein, to be subsequent packet set a Preset Time in the storage of destination link layer in system, if the cache-time of subsequent packet surpasses described Preset Time, then destination will abandon the message that the not reorganization of front finishes, proceed subsequent packet on give.
The message that S304, destination link layer finish described reorganization, and described non-fragment message is delivered to the protocol stack of destination APP on successively by same path.And then can guarantee the message that send described reorganization to finish on the destination link layer, and described non-fragment message is to the order of the protocol stack of destination APP, the order that receives fragment message and non-fragment message with the destination link layer is identical, avoids the out of order problem that causes owing to the fragment message reorganization.
The protocol stack of S305, destination APP carries out the message decapsulation to message and the described non-fragment message that described reorganization finishes, and the message that described decapsulation finishes is sent to destination APP.
Thereby the method that the message that utilizes the embodiment of the invention to provide is handled can solve the out of order problem that occurs when the destination message is recombinated in the distributed system.
The device that embodiments of the invention provide a kind of message to handle can solve the out of order problem that occurs when the destination message is recombinated in the distributed system.
Embodiment four
As shown in Figure 4, the device that described message is handled comprises:
Receiving element 401 is used for fragment message and non-fragment message that the reception sources end sends.
On send processing unit 402, be used for fragment message that described receiving element 401 is received and non-fragment message and deliver to destination APP corresponding protocols stack by same path on successively and handle.
The device that message that the embodiment of the invention provides is handled, fragment message and non-fragment message that destination reception sources end sends are delivered to destination APP corresponding protocols stack by same path on successively with described fragment message and non-fragment message and are handled.Compared with prior art, the order that destination receives fragment message and non-fragment message with on to deliver to the order of protocol stack of APP identical, the out of order problem that can avoid non-fragment message and fragment message to cause owing to the path of being walked is different.
Embodiment five
As shown in Figure 5, the device that described message is handled comprises:
Receiving element 501 is used for fragment message and non-fragment message that the reception sources end sends.
On send processing unit 502, be used for the protocol stack that fragment message that described receiving element 501 is received and non-fragment message deliver to destination APP on successively by same path and handle.
Wherein, send processing unit 502 to comprise on described:
APP protocol stack unit 5023, the message and the described non-fragment message that receives that are used for described reorganization is finished carry out the message decapsulation, and the message that described decapsulation is intact is sent to destination APP successively.
If described message is the initial IP message, fragment message that the destination link layer receives and non-fragment message are delivered to the protocol stack of destination APP on successively through same path, and fragment message is recombinated after the last protocol stack of delivering to destination APP.Then:
Described recomposition unit 5022 is positioned at described APP protocol stack unit 5023.
Under the environment of distributed protocol stack, each protocol stack all possesses complete function, can realize the message reorganization.Therefore, the fragment message of initial IP delivered in the destination corresponding protocols stack on directly recombinate, so just can guarantee the fragment message of initial IP and non-fragment message process be same protocol stack, walk same path, thereby avoid the generation of out of order problem.
If described message comprises initial IP message, TCP message and UDP message etc., the destination link layer is at first recombinated delivering to concentrated protocol stack on the fragment message that receives, the message that described reorganization is finished, and non-fragment message is then delivered to the protocol stack of destination APP on successively and is handled through same path.Then:
Described recomposition unit 5022 also is used for the message that described reorganization finishes is returned to link layer unit 5021, and at this moment, described recomposition unit 5022 is positioned at the convergence protocol stack of destination.
Then described link layer unit 5021, also be used for recombinating with delivering to recomposition unit 5022 on the described fragment message, and receiving the message that reorganization finishes, the message that described reorganization is finished, and described non-fragment message is then delivered to the protocol stack of destination APP on successively by same path.
Further, described link layer unit 5021 also was used for before the message that the reorganization that receives described recomposition unit 5022 transmissions finishes, the subsequent packet that the described receiving element 501 of buffer memory receives.
Wherein, the processing of described fragment message and non-fragment message is carried out successively according to the order that the destination link layer receives.When described fragment message between recombination phase, the destination link layer receives follow-up fragment message or non-fragment message, then subsequent packet will be buffered, and give on the ability after the fragment message reorganization of waiting for the front finishes.
Wherein, described link layer unit 5021, also be used for when the time of buffer memory subsequent packet exceeds Preset Time, abandon the message that described recomposition unit 5022 is not recombinated and finished, proceed subsequent packet on give, wherein, described Preset Time is by default, the maximum duration of storing in described link layer unit 5021 for subsequent packet.
Thereby the device that the message that utilizes the embodiment of the invention to provide is handled can solve the out of order problem that occurs when the destination message is recombinated in the distributed system.
One of ordinary skill in the art will appreciate that all or part of flow process that realizes in the foregoing description method, be to instruct relevant hardware to finish by computer program, described program can be stored in the computer read/write memory medium, this program can comprise the flow process as the embodiment of above-mentioned each side method when carrying out.Wherein, described storage medium can be magnetic disc, CD, read-only storage memory body (Read-Only Memory, ROM) or at random store memory body (Random Access Memory, RAM) etc.
The above; it only is the embodiment of the embodiment of the invention; but the protection range of the embodiment of the invention is not limited thereto; anyly be familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, the protection range of the embodiment of the invention should be as the criterion with the protection range of claim.
Claims (10)
1. the method that message is handled is characterized in that, comprising:
Fragment message and non-fragment message that the reception sources end sends;
Described fragment message and non-fragment message are delivered to destination by same path on successively to be handled based on the protocol stack of the upper layer application APP of agreement.
2. the method that message according to claim 1 is handled is characterized in that, describedly described fragment message and non-fragment message are delivered to the step that the protocol stack of destination APP handles on successively by same path comprises:
Described fragment message and non-fragment message are directly delivered to the protocol stack of destination APP on successively by same path;
Described fragment message is recombinated, and message and non-fragment message that described reorganization is finished carry out decapsulation.
3. the method that message according to claim 1 is handled is characterized in that, describedly described fragment message and non-fragment message are delivered to the step that the protocol stack of destination APP handles on successively by same path comprises:
The convergence protocol stack of delivering on the described fragment message in the destination is recombinated;
Receive the message that described reorganization finishes;
The message that described reorganization is finished, and the protocol stack that described non-fragment message is delivered to destination APP on successively by same path carries out decapsulation.
4. the method that message according to claim 3 is handled is characterized in that, before the step of the message that the described reorganization of described reception finishes, also comprises:
The subsequent packet that receives is carried out buffer memory;
Correspondingly, the method that described message is handled also comprises when the cache-time of described subsequent packet surpasses Preset Time, abandon the message that not reorganization finishes, wherein, described Preset Time is the maximum duration of described subsequent packet buffer memory in the link layer unit by default.
5. the device that message is handled is characterized in that, comprising:
Receiving element is used for fragment message and non-fragment message that the reception sources end sends;
On send processing unit, be used for fragment message that described receiving element is received and non-fragment message and deliver to destination by same path on successively and handle based on the protocol stack of the upper layer application APP of agreement.
6. the device that message according to claim 5 is handled is characterized in that, send processing unit to comprise on described:
The link layer unit is used for fragment message that described receiving element is received and non-fragment message are delivered to destination APP on successively by same path protocol stack;
Recomposition unit is used for the fragment message that described link layer unit sends over is recombinated;
APP protocol stack unit, the message and the described non-fragment message that receives that are used for described reorganization is finished carry out the message decapsulation, and the message that described decapsulation is intact is sent to destination APP successively.
7. the device that message according to claim 6 is handled is characterized in that:
Described recomposition unit is positioned at described APP protocol stack unit.
8. the device that message according to claim 6 is handled is characterized in that:
Described recomposition unit also is used for the message that described reorganization finishes is returned to the link layer unit, and at this moment, described recomposition unit is positioned at the convergence protocol stack of destination;
Then described link layer unit, also be used for recombinating with delivering to recomposition unit on the described fragment message, and receiving the message that reorganization finishes, the message that described reorganization is finished, and described non-fragment message is then delivered to the protocol stack of destination APP on successively by same path.
9. the device that message according to claim 8 is handled is characterized in that:
Described link layer unit also was used for before the message that the reorganization that receives described recomposition unit transmission finishes the subsequent packet that the described receiving element of buffer memory receives.
10. the device that message according to claim 9 is handled is characterized in that:
Described link layer unit, also be used for when the time of buffer memory subsequent packet exceeds Preset Time, abandon the message that described recomposition unit is not recombinated and finished, proceed subsequent packet on give, wherein, described Preset Time is by default, the maximum duration of storing in described link layer unit for subsequent packet.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101891027A CN101447930B (en) | 2008-12-25 | 2008-12-25 | Message processing method and device thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101891027A CN101447930B (en) | 2008-12-25 | 2008-12-25 | Message processing method and device thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101447930A CN101447930A (en) | 2009-06-03 |
| CN101447930B true CN101447930B (en) | 2011-01-05 |
Family
ID=40743342
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101891027A Active CN101447930B (en) | 2008-12-25 | 2008-12-25 | Message processing method and device thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101447930B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102065012B (en) * | 2010-12-22 | 2015-04-01 | 中兴通讯股份有限公司 | Distributed system and method for processing IP message fragments |
| CN104486226B (en) * | 2014-12-23 | 2019-04-05 | 北京天融信科技有限公司 | A kind of message processing method and device |
| CN115022423A (en) * | 2022-06-22 | 2022-09-06 | 上海弘积信息科技有限公司 | IPv4 identifier distribution method in load balancing equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1592215A (en) * | 2003-08-27 | 2005-03-09 | 中兴通讯股份有限公司 | Method for partitioned document recombination and service distribution |
| WO2008106893A1 (en) * | 2007-03-07 | 2008-09-12 | Huawei Technologies Co., Ltd. | Method for receiving message fragment of multilink ppp and device thereof |
| CN101309276A (en) * | 2008-06-27 | 2008-11-19 | 杭州华三通信技术有限公司 | Processing method and apparatus of LWAAP slicing packet |
-
2008
- 2008-12-25 CN CN2008101891027A patent/CN101447930B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1592215A (en) * | 2003-08-27 | 2005-03-09 | 中兴通讯股份有限公司 | Method for partitioned document recombination and service distribution |
| WO2008106893A1 (en) * | 2007-03-07 | 2008-09-12 | Huawei Technologies Co., Ltd. | Method for receiving message fragment of multilink ppp and device thereof |
| CN101309276A (en) * | 2008-06-27 | 2008-11-19 | 杭州华三通信技术有限公司 | Processing method and apparatus of LWAAP slicing packet |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101447930A (en) | 2009-06-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101404621B (en) | Method and routing device for implementing VRRP load balance | |
| US9237091B2 (en) | System and method of load balancing for ethernet link aggregation | |
| CN103580880B (en) | Method, equipment and system abnormal a kind of fast notification CGN | |
| US20060146835A1 (en) | Platform independent implementation of private VLANS | |
| CN103297353A (en) | Access method and system of customer premise equipment and broadband network gateway | |
| CN102025630A (en) | Load balancing method and load balancing system | |
| CN103476062A (en) | Data flow scheduling method, equipment and system | |
| CN1946061B (en) | Method and device for fast processing message | |
| CN101018159A (en) | Load balance method under the multi-gateway environment and DHCP server | |
| CN101675346A (en) | Pseudowire load balancing | |
| KR20060101466A (en) | Method, system and article for dynamic real-time stream aggregation in a network | |
| CN102404418A (en) | Method, device and system for distributing IP (internet protocol) address for user terminal | |
| CN102027732A (en) | Providing access over an ip network to a server application program | |
| CN103200072A (en) | Network-based data transmission method, device and system | |
| CN101447930B (en) | Message processing method and device thereof | |
| CN102065012B (en) | Distributed system and method for processing IP message fragments | |
| CN105743811A (en) | Data Transmitter Apparatus And Method For Data Communication Using The Same | |
| CN1812398B (en) | Method for realizing DHCP server loading sharing based on DHCP relay | |
| CN104144096A (en) | Virtual network layer construction method, device and system | |
| CN104780232A (en) | A resource allocating method, controller and system | |
| CN105007340A (en) | Distributed CAN (Controller Area Network) network supporting plug and play and automatic node address allocation method thereof | |
| CN102413052B (en) | A kind of method of access network, Apparatus and system | |
| CN102780602A (en) | Method and device for data transmission | |
| CN110535811A (en) | Remote memory management method and system, server-side, client, storage medium | |
| CN102143242A (en) | IP (internet protocol) network address allocation method, IP network address allocation equipment and IP network address allocation system |
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 |