CN101478781A - Processing method for data transmission exception and path functional entity - Google Patents
Processing method for data transmission exception and path functional entity Download PDFInfo
- Publication number
- CN101478781A CN101478781A CNA2008102421777A CN200810242177A CN101478781A CN 101478781 A CN101478781 A CN 101478781A CN A2008102421777 A CNA2008102421777 A CN A2008102421777A CN 200810242177 A CN200810242177 A CN 200810242177A CN 101478781 A CN101478781 A CN 101478781A
- Authority
- CN
- China
- Prior art keywords
- path
- functional entity
- data
- data path
- message
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/22—Manipulation of transport tunnels
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses an abnormal handling method for data transmission and belongs to the communication technique field. The method comprises the following procedures: a first path function entity receives the user data message sent by a second path function entity through a data path established by the first path function entity and the second path function entity; if judging that the current data path is abnormal, the first path function entity sends a message to inform the second function entity of handling the abnormal data transmission, and the informing message carries along with a mark of the abnormal data path. The abnormal handling method for data transmission of the invention avoids the resource waste caused by the transmission of useless user data messages among network paths. Simultaneously, the invention also discloses a path function entity.
Description
Technical field
The present invention relates to communication technical field, relate in particular to a kind of processing method and path functional entity of data transmission exception.
Background technology
In the communications field, after the user was linked into network, network side can be set up a data transfer path for the user, was used for carrying this user-dependent user data.The equipment that participates in transfer of data in the network can be called path functional entity, for example base station BS in the network, gateway Gateway etc., and path functional entity concrete in different networks may be different.
With Wimax is example, and the Wimax network is made up of ASN (access service network) and CSN (connectivity serving network).The ASN network is divided into BS and two logic entities of ASN-GW, after the user inserts the Wimax network, can set up user's data path DataPath between BS and ASN-GW.Defined the flow process of setting up path and deletion path between two data path functional entity DataPath Function at network work group NWG, as described in Figure 1, the flow process of DataPath foundation/deletion comprises:
1, DataPath Function 1 sends DataPath foundation/removal request, requires foundation/deletion DataPath;
2, after DataPath Function 2 receives DataPath foundation/removal request, return DataPath foundation/deletion response;
3, after DataPath Function 1 receives Datapath foundation/deletion response, return DataPath foundation/deletion and confirm.
After DataPath Function 1 sets up with DataPath Function 2 data paths, transmit the user data message by the data path of setting up between two path functional entities, at this moment, if it is unusual that the path functional entity DataPath Function of receiving subscriber data message 1 takes place, the DataPath context that causes setting up is lost, still there is this DataPath relevant information and send this moment among the path functional entity DataPath Function 2 of user data message, at this moment, DataPath Function 2 can continue to send the user data message, and because this DataPath contextual information not among the DataPath Function 1, can abandon this user data message, the DataPath that DataPath Function 2 can continue to set up between use and the DataPath Function 1 sends the user data message, these useless data messages have taken the bandwidth between DataPath Function 1 and the DataPath Function 2, have wasted system resource.
Summary of the invention
The embodiment of the invention provides a kind of processing method and path functional entity of data transmission exception, to avoid transmitting useless data message between the path functional entity.
The embodiment of the invention provides a kind of processing method of data transmission exception, comprises
First path functional entity by and second path functional entity between the data path set up receive the user data message that second path functional entity sends;
It is unusual that first path functional entity determines that the current data path takes place, and sends a notification message to second path functional entity, and the processing of notifying second path functional entity to carry out data transmission exception is carried in the described notification message unusual data path sign is taken place.
The embodiment of the invention provides a kind of path functional entity, comprises
Determine receiving element, be used for by and second path functional entity between after the data path set up receives the user data message that second path functional entity sends, it is unusual to determine that the current data path takes place;
Notification unit, be used for determining unit determine the current data path take place unusual after, send a notification message to second path functional entity, the processing of notifying second path functional entity to carry out data transmission exception is carried in the described notification message unusual data path sign is taken place.
The embodiment of the invention also provides a kind of path functional entity, comprises
Receiving element, be used for by and first path functional entity between the data path set up receive the notification message that first path functional entity sends, carry the data path sign in the described notification message;
Exception processing unit is used for the notification message that receives according to receiving element, and the data path of data ID of trace route path correspondence is carried out the processing of data transmission exception.
The processing method and the path functional entity of the data transmission exception that provides by the embodiment of the invention, after path functional entity determines that the current data path takes place unusually, send a notification message to the path functional entity that sends the user data message, the path functional entity that notice sends the user data message carries out the processing of data transmission exception, thereby the path functional entity of having avoided sending the user data message continues the useless user data message of transmission and causes resource waste.
Description of drawings
Fig. 1 is the flow chart in foundation/deleted data path between two path functional entities in the prior art.
Fig. 2 is the flow chart of the processing method of a kind of data transmission exception of providing of the embodiment of the invention.
Fig. 3 is the flow chart of a kind of processing method of data transmission exception in the Wimax system.
Fig. 4 is the flow chart of the processing method of another kind of data transmission exception in the Wimax system.
Fig. 5 A is the structure chart of a kind of path functional entity of providing of the embodiment of the invention.
Fig. 5 B is the structure chart of the another kind of path functional entity that provides of the embodiment of the invention.
Fig. 6 A is the structure chart of the another kind of path functional entity that provides of the embodiment of the invention.
Fig. 6 B is the structure chart of the another kind of path functional entity that provides of the embodiment of the invention.
Fig. 7 is the structure chart of the treatment system of a kind of data transmission exception of providing of the embodiment of the invention.
Embodiment
As shown in Figure 2, the embodiment of the invention provides a kind of processing method of data transmission exception, comprising:
201, first path functional entity by and second path functional entity between the data path set up receive the user data message that second path functional entity sends;
In the embodiment of the invention, first path functional entity and second path functional entity can be according to data path method for building up foundation of the prior art data paths between the two, after data path was set up, the user data message just was carried on the data path of being set up.Wherein, path functional entity can be the various network elements of participating user transfer of data in the network, for example, base station, gateway etc., the embodiment of the invention does not limit the type and the title of path functional entity.
202, first path functional entity determines that the current data path takes place unusually, send a notification message to second path functional entity, the processing of notifying second path functional entity to carry out data transmission exception is carried in the described notification message unusual data path sign is taken place.
For example, first path functional entity finds that the data path of carrying user data message does not exist, thereby it is unusual to determine that the current data path takes place.
Optionally, if there is a side to be base station BS in the path functional entity, then in notification message, can also carry Tunnel Endpoint parameter information, the IP address of the gre tunneling relevant with DP is described, if omit this attribute then the IP address of giving tacit consent to gre tunneling equals the IP address of the transmit leg of this message.
When first path functional entity is a base station BS, if second path functional entity then also needs to carry BS ID by the DataPath of the Data Path ID in the notification message on can not unique identification BS in the notification message; Second path functional entity can be determined the data path that is designated Data Path ID that the base station corresponding with BS ID set up according to BS ID and Data Path ID, thereby determine unusual data path takes place.
After first path functional entity determines that the current data path takes place unusually, can abandon this user data message, also this user data message buffer memory can be got up, like this after data path recovers, first path functional entity can be changed away the user data message of buffer memory, thereby guarantees the continuous of user data message.
Further, this method can also comprise:
203, second path functional entity receives described notification message, according to the sign of the data path that carries in the described notification message, the corresponding data path of described data path sign is carried out abnormality processing.
Different abnormality eliminating methods is taked in the type of error indications of carrying in the strategy, network configuration information, user that second path functional entity can operator or professional priority and/or the notification message etc., and concrete abnormality eliminating method comprises:
Delete the relevant information of described data path, reclaim system resource relevant on second path functional entity with described data path; Perhaps
Initiate data path and recover flow process, data path between the recovery and first path functional entity, for example, can initiate the network travelling carriage and move back the net flow process, trigger the travelling carriage re-accessing network, thereby the restore data path perhaps can directly send data path to first path functional entity and recover message, thereby the data path between the recovery and first path functional entity.
In the above-described embodiments, when first path functional entity is the base station, can also carry the sign of described base station in the described notification message, then in the step 103, second path functional entity can be according to the Base Station Identification that carries in the notification message, data path sign, determine unusual data path takes place, thereby this data path is carried out abnormality processing.Connect a plurality of base stations when second path functional entity like this, and the data path that distributes between a plurality of base station sign is when having repetition, second path functional entity can come unique data path of determining according to Base Station Identification and ID of trace route path.
The data transmission exception processing method that the embodiment of the invention provides, guaranteed to take place when unusual when first path functional entity, unusual data path takes place can be handled timely, thereby has avoided the useless transmission of user data message in network, has reduced resource waste.
Fig. 3 is an example with the Wimax system, provides a kind of processing method of data transmission exception, and wherein BS and ASN GW transmit the user data relevant with mobile station MS as path functional entity, and this method comprises:
301, MS inserts the ASN network, creates DataPath between BS and ASN GW, is used to carry the user data message of MS, and concrete creation method is referring to the introduction in the background technology.
302, MS begins to carry out business, ASN GW by and BS between the DataPath that sets up, transmit the user data message to BS, BS is transmitted to MS with the user data message again.
303, after having transmitted N message, BS takes place unusual, causes BS to go up the DataPath context and loses, and has caused loss of data etc. in unusual reason the takes place processes such as for example system upgrade, BS are restarted, active and standby switching.
304, BS receives N+1 the user data message that ASN GW transmits, and determine that current DataPath context loses, thereby definite DataPath is unusual, abandons this user data message.
305, BS sends a notification message to ASN GW and notifies the DataPath of ASN GW carrying user data message unusual, in notification message, carry unusual DataPath ID takes place, if the DataPath that sets up between ASN GW and the different B S all uses unique DataPathID, then ASN GW can be according to the DataPath in the unique location of DataPath ID, if and the DataPath that sets up between ASN GW and the different B S uses the DataPath ID that repeats, then BS can also carry this BS ID in notification message, thereby makes ASN GW to come the unusual DataPath of unique definite generation according to BS ID and DataPath ID.
306, after the notified message of ASN GW, according to the DataPath ID that carries in the notification message or DataPath and BS ID, determine to take place unusual DataPath, and delete the relevant information of this DataPath, as the DataPath contextual information, and be recovered as this DataPath distributed system resources.
The foregoing description is to send datagram to BS with ASN GW to be example, when specific implementation, also can be that BS sends the user's data message to ASN GW, and its specific implementation flow process and above-mentioned flow process are similar, no longer repeat specification.
The exception handling that provides by the foregoing description, can guarantee after BS is finding that DataPath is unusual, in time by ASN GW, ASN GW has in time deleted the relevant information of this DataPath, after this ASN GW does not just return again and has sent useless user data message to BS by this DataPath, has avoided waste of network resources.
Fig. 4 is an example with the Wimax system, provide the processing method of another kind of data transmission exception, wherein BS, service network gateway Serving GW and anchor ASN-GW Anchor GWSN GW carry the user data relevant with mobile station MS as path functional entity, and this method comprises:
401, MS inserts ASN GW network, sets up DataPath between BS, Serving GW and the Anchor GW.
402, MS begins to carry out business, Anchor GW by and Serving GW between the DataPath that sets up, transmit the user data message to Serving GW, Serving GW is transmitted to BS with the user data message again, BS is transmitted to MS with the user data message.
403, after having transmitted N message, Serving GW occurs unusual, and for example: Serving GW is restarted, and the DataPath contextual information of this corresponding MS is lost on the Serving GW;
404, Serving GW receives N+1 the data message that Anchor GW transmits, determine that current DataPath context loses, thereby determine that this DataPath is unusual, this data message can't be transmitted to MS normally, Serving GW can select data message is abandoned, also the data message buffer memory can be got up, so that after data path recovers, to the data message of BS forwarding cache.
405, the Serving GW DataPath information that notice Anchor GW carries this MS data message that sends a notification message abandons.Carry in the notification message unusual DataPath ID takes place.
406, after the notified message of Anchor GW, determine to take place unusual DataPath, and initiate DataPath and recover flow process, recover the DataPath context on the Serving GW according to the DataPath ID that carries in the notification message.
Anchor GW recovers DataPath following dual mode:
A, Anchor GW initiate network side MS and move back the net flow process, and then trigger the MS re-accessing network; Anchor GW trigger network MS moves back the net flow process has detailed explanation in " NWG_R1_V1.3.0-Stage-3_NWGAPPROVED " standard 4.5.2.1.2.2, be not repeated in this description at this.
B, Serving GW directly initiate DataPath and recover flow process, do not need the MS re-accessing network, make the faster of MS business recovery like this.For example: DataPath loses on the Serving GW, Anchor GW can initiatively initiate path_reg_req message, carry information such as Business Stream, DataPath, " Registration Type " is designated as DataPath recovery processing in the message, Serving GW receives after the message, find that " Registration Type " for recovering DataPath, then recovers DataPath and handle.After recovering successfully, reply Path_Reg_Rsp message to Anchor GW, indication DataPath recovers successfully, and AnchorGW replys Path_Reg_Ack message again and confirms; If Serving GW recovers the DataPath failure, then respond Anchor GW Path_Reg_Rsp message and indication recovery failure.If recover failure, can repeatedly attempt, when attempting arriving the success not yet of certain number of times, then Anchor GW initiates network side MS and moves back the net flow process.
407, this step is for optional flow process, if in the process of recovering DataPath, Serving GW buffer memory M message of retransmission failure, then after DataPath recovered, Serving GW can be transmitted to MS by BS with the message elder generation of buffer memory.
408, after the DataPath on the Serving GW recovers, transmit subsequent packet normally.
The foregoing description, processing when having realized between two gateways data transmission exception taking place, unusual data path takes place by timely recovery, can in time recover user's business, and message by gateway buffer memory retransmission failure, can further guarantee user experience so that the user data message that the user receives keeps continuous.
More than the technological means applied in any combination flexibly of two embodiment, such as, in the embodiment of Fig. 3 correspondence, BS specified data path take place unusual after, user data message that also can the buffer memory retransmission failure.
Shown in Fig. 5 A, the structure chart of a kind of path functional entity 500 that provides for the embodiment of the invention, it is arranged in the data path of travelling carriage, after having set up data path with second path functional entity 502, the user data message that reception sends from the second path entity 502, it comprises:
Determining unit 520, be used for by and second path functional entity 502 between after the data path set up receives the user data message that second path functional entity 502 sends, it is unusual to determine that the current data path takes place;
Notification unit 530, after being used for determining unit 520 definite current data paths generations unusually, send a notification message to second path functional entity 502, notify second path functional entity 502 to carry out the processing of data transmission exception, carry in the described notification message unusual data path sign takes place.
For example, notification unit can not exist by the data path of finding the carrying user data message, and it is unusual to come the specified data path to take place.Optionally can also carry Tunnel Endpoint parameter information in the notification message, but its concrete purposes and description reference method embodiment.
This path functional entity can be the various network device of participating user transfer of data in the network, for example base station BS, various data gateways etc., for example ASN GW, Serving GW, Anchor GW, PDN GW etc. also can be the network equipments of other participating user transfer of data.
When this path functional entity is base station BS, can also carry BS ID in the notification message that notification unit 530 sends, so that second path functional entity is determined unusual data path takes place, and it is carried out abnormality processing according to BS ID and data path sign.
Shown in Fig. 5 B, the structure chart of the another kind of path functional entity 500 ' that provides for the embodiment of the invention, they are on path functional entity 500 bases of Fig. 5 A correspondence, also comprise a buffer unit 540, be used for after notification unit 530 determines that current path takes place unusually the user data message that buffer memory determining unit 520 receives; Recover processing unit 550, be used to receive data path and recover to trigger message, the data path between the recovery and second path functional entity; Transmitting element 560, be used for and second path functional entity between data path recover after, the user data message of forwarding cache unit 540 buffer memorys, and transmit the user data message that follow-up receiving element receives.
Wherein data path recovers to trigger the data path recovery message that message comprises that second path functional entity sends, and as path_reg_req message, perhaps the network side MS of second path functional entity initiation moves back the relevant message in the net flow process.
The path functional entity that provides by the embodiment of the invention, after path functional entity determines that the current data path takes place unusually, send a notification message to the path functional entity that sends the user data message, the path functional entity that notice sends the user data message carries out the processing of data transmission exception, thereby the path functional entity of having avoided sending the user data message continues the useless user data message of transmission and causes resource waste.Further,, and recover the back at data path and transmit the user data message of also depositing, also guaranteed the continuous type of customer service by the message of buffer memory retransmission failure.
As shown in Figure 6A, the structure chart of the another kind of path functional entity 502 that provides for the embodiment of the invention, it is arranged in the data path of travelling carriage, after having set up data path with the path functional entity of Fig. 5 A or Fig. 5 B explanation, send the user data message to path functional entity 500 or 500 ', it comprises:
Receiving element 620, be used for by and path functional entity 500 or 500 ' between data path RX path functional entity 500 or the 500 ' notification message that sends set up, carry the data path sign in the described notification message;
Exception processing unit 630 is used for the notification message that receives according to receiving element 620, and the data path of data ID of trace route path correspondence is carried out the processing of data transmission exception.
If path function unit 500 or 500 ' is a base station BS, the BS ID that then also may comprise this base station in the notification message that receiving element 620 receives, then exception processing unit 630 is further used for determining unusual data path takes place according to BS ID and data path sign, and it is carried out the processing of data transmission exception.
Shown in Fig. 6 B, the structure chart of the another kind of path functional entity 502 ' that provides for the embodiment of the invention, they are on path functional entity 502 bases of Fig. 6 A correspondence, and its exception processing unit 630 has further comprised one of following two unit or combination again:
Deletion subelement 6302 is used for the notification message that receives according to receiving element, deletes the relevant information of described data path, reclaims system resource relevant with described data path in the described data path functions entity;
Recover subelement 6304, be used to initiate data path and recover flow process, the data path between the recovery and first path functional entity.For example initiate the network side travelling carriage and move back the net flow process, trigger the travelling carriage re-accessing network; Perhaps send data path and recover message, as path_reg_req message, the data path between the recovery and first path functional entity.
The path functional entity that provides by the embodiment of the invention, after path functional entity receives notification message, the path functional entity current data path of determining the receiving subscriber data message takes place unusual, in time carry out abnormality processing, avoided continuing to send useless user data message, by deleting this data path relevant information, recovery system resource, can improve resource utilization, recover to handle by data path, can recover the user's data path, guarantee normally carrying out of customer service.
Technological means that each unit in the above-mentioned path functional entity and subelement use when specific implementation and various ins and outs all can be with reference to the descriptions among the preceding method embodiment.
As shown in Figure 7, the treatment system of a kind of data transmission exception that provides for the embodiment of the invention, it comprises the first path functional process unit and the second path function processing unit, wherein,
First path functional entity, be used for by and second path functional entity between the data path set up receive the user data message that second path functional entity sends, it is unusual to determine that the current data path takes place, send a notification message to second path functional entity, the processing of notifying second path functional entity to carry out data transmission exception is carried in the described notification message unusual data path sign is taken place;
Second path functional entity, be used for by and second path functional entity between the user data message that sends to first path functional entity of the data path set up, receive the notification message that first path functional entity sends, and, carry out the processing of data transmission exception according to described notification message.
Concrete, first path functional entity can be that data function entity 500 or 500 ', second path functional entity of Fig. 5 A or Fig. 5 B correspondence can be the data function entity 502 or 502 ' of Fig. 6 or Fig. 6 A correspondence.
Through the above description of the embodiments, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential hardware platform, can certainly all implement, but the former is better execution mode under a lot of situation by hardware.Based on such understanding, all or part of can the embodying that technical scheme of the present invention contributes to background technology with the form of software product, this computer software product can be stored in the storage medium, as ROM/RAM, magnetic disc, CD etc., comprise that some instructions are with so that a computer equipment (can be a personal computer, server, the perhaps network equipment etc.) carry out the described method of some part of each embodiment of the present invention or embodiment.
In a word, the above is the preferred embodiment of technical solution of the present invention only, is not to be used to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (14)
1, a kind of processing method of data transmission exception is characterized in that, comprising:
First path functional entity by and second path functional entity between the data path set up receive the user data message that second path functional entity sends;
It is unusual that first path functional entity determines that the current data path takes place, and sends a notification message to second path functional entity, and the processing of notifying second path functional entity to carry out data transmission exception is carried in the described notification message unusual data path sign is taken place.
2, the processing method of data transmission exception as claimed in claim 1 is characterized in that, described definite current data path takes place to comprise unusually:
First path functional entity finds that the data path of carrying user data message does not exist, thereby it is unusual to determine that the current data path takes place.
3, the processing method of data transmission exception as claimed in claim 1, it is characterized in that, this method also comprises, second path functional entity receives described notification message, according to the sign of the data path that carries in the described notification message, the corresponding data path of described data path sign is carried out abnormality processing.
4, the processing method of data transmission exception as claimed in claim 1, it is characterized in that, when described first path functional entity is the base station, also carry the sign of described base station in the described notification message, this method also comprises, second path functional entity receives described notification message, according to the Base Station Identification that carries in the described notification message, data path sign, described Base Station Identification and the corresponding data path of data path sign is carried out abnormality processing.
As the processing method of claim 3 or 4 described data transmission exceptions, it is characterized in that 5, second path functional entity carries out abnormality processing and comprises unusual data path takes place:
Delete the relevant information of described data path, reclaim system resource relevant on second path functional entity with described data path; Perhaps
Initiate data path and recover flow process, the data path between the recovery and first path functional entity.
6, the processing method of data transmission exception as claimed in claim 5 is characterized in that, described initiation data path recovers flow process, and the data path between the recovery and first path functional entity comprises:
Initiate the network side travelling carriage and move back the net flow process, trigger the travelling carriage re-accessing network; Perhaps
Send data path and recover message, the data path between the recovery and first path functional entity.
7, the processing method of data transmission exception as claimed in claim 5, it is characterized in that, after described first path functional entity determines that the current data path takes place unusually, this method also comprises the user data message that the first path functional entity buffer memory, second path functional entity sends, after the data path between first path functional entity and second path functional entity recovers, the user data message of the first path functional entity forwarding cache.
8, a kind of data path functions entity is characterized in that, comprising:
Determine receiving element, be used for by and second path functional entity between after the data path set up receives the user data message that second path functional entity sends, it is unusual to determine that the current data path takes place;
Notification unit, be used for determining unit determine the current data path take place unusual after, send a notification message to second path functional entity, the processing of notifying second path functional entity to carry out data transmission exception is carried in the described notification message unusual data path sign is taken place.
9, data path functions entity as claimed in claim 8 is characterized in that, described data path functions entity also comprises: buffer unit is used for after notification unit determines that current path takes place unusually the user data message that the buffer memory receiving element receives; Recover processing unit, be used to receive data path and recover to trigger message, the data path between the recovery and second path functional entity; Transmitting element, be used for and second path functional entity between data path recover after, the user data message of forwarding cache unit caches.
10, data path functions entity as claimed in claim 8 is characterized in that, when described data path functions entity was the base station, described notification unit also was used for carrying at the notification message that sends to second path functional entity sign of described base station.
11, a kind of data path functions entity is characterized in that, comprising:
Receiving element, be used for by and first path functional entity between the data path set up receive the notification message that first path functional entity sends, carry the data path sign in the described notification message;
Exception processing unit is used for the notification message that receives according to receiving element, and the data path of data ID of trace route path correspondence is carried out the processing of data transmission exception.
12, data path functions entity as claimed in claim 11 is characterized in that, described exception processing unit comprises with one of lower unit or combination:
The deletion subelement is used for the notification message that receives according to receiving element, deletes the relevant information of described data path, reclaims system resource relevant with described data path in the described data path functions entity;
Recover subelement, be used to initiate data path and recover flow process, the data path between the recovery and first path functional entity.
13, a kind of treatment system of data transmission exception is characterized in that, this system comprises: first path functional entity and second path functional entity, wherein,
First path functional entity, be used for by and second path functional entity between the data path set up receive the user data message that second path functional entity sends, it is unusual to determine that the current data path takes place, send a notification message to second path functional entity, the processing of notifying second path functional entity to carry out data transmission exception is carried in the described notification message unusual data path sign is taken place;
Second path functional entity, be used for by and second path functional entity between the user data message that sends to first path functional entity of the data path set up, receive the notification message that first path functional entity sends, and, carry out the processing of data transmission exception according to described notification message.
14, treatment system as claimed in claim 13 is characterized in that, described first path functional entity such as claim 8,9 or 10 described path functional entities, described second path functional entity such as claim 11 or 12 described path functional entities.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102421777A CN101478781B (en) | 2008-12-31 | 2008-12-31 | Processing method for data transmission exception and path functional entity |
| PCT/CN2009/075406 WO2010075727A1 (en) | 2008-12-31 | 2009-12-08 | Processing method for abnormal data transmission and path function entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102421777A CN101478781B (en) | 2008-12-31 | 2008-12-31 | Processing method for data transmission exception and path functional entity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101478781A true CN101478781A (en) | 2009-07-08 |
| CN101478781B CN101478781B (en) | 2010-12-22 |
Family
ID=40839400
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008102421777A Expired - Fee Related CN101478781B (en) | 2008-12-31 | 2008-12-31 | Processing method for data transmission exception and path functional entity |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101478781B (en) |
| WO (1) | WO2010075727A1 (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010075727A1 (en) * | 2008-12-31 | 2010-07-08 | 华为技术有限公司 | Processing method for abnormal data transmission and path function entity |
| WO2011020323A1 (en) * | 2009-08-20 | 2011-02-24 | 中兴通讯股份有限公司 | Idle exit path establishment method and device for an access service network |
| CN101990227A (en) * | 2009-08-07 | 2011-03-23 | 中兴通讯股份有限公司 | Method and device for establishing data channel between network elements of access service network |
| CN101640912B (en) * | 2009-08-31 | 2013-07-03 | 中兴通讯股份有限公司 | Switching method and device for accessing service network |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106547643B (en) * | 2015-09-21 | 2020-05-22 | 阿里巴巴集团控股有限公司 | Recovery method and device of abnormal data |
| CN113315676B (en) * | 2021-05-20 | 2022-11-04 | 北京达佳互联信息技术有限公司 | Method and device for detecting broken link and electronic equipment |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6393026B1 (en) * | 1998-09-17 | 2002-05-21 | Nortel Networks Limited | Data packet processing system and method for a router |
| CN100546298C (en) * | 2003-08-19 | 2009-09-30 | 华为技术有限公司 | A kind of method that realizes load sharing |
| CN101193097B (en) * | 2006-11-22 | 2011-11-30 | 中兴通讯股份有限公司 | A link state inquiry response method and its device |
| CN101217458B (en) * | 2007-12-28 | 2012-09-05 | 华为技术有限公司 | A virtual private online resource allocation method |
| CN101478781B (en) * | 2008-12-31 | 2010-12-22 | 华为技术有限公司 | Processing method for data transmission exception and path functional entity |
-
2008
- 2008-12-31 CN CN2008102421777A patent/CN101478781B/en not_active Expired - Fee Related
-
2009
- 2009-12-08 WO PCT/CN2009/075406 patent/WO2010075727A1/en active Application Filing
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010075727A1 (en) * | 2008-12-31 | 2010-07-08 | 华为技术有限公司 | Processing method for abnormal data transmission and path function entity |
| CN101990227A (en) * | 2009-08-07 | 2011-03-23 | 中兴通讯股份有限公司 | Method and device for establishing data channel between network elements of access service network |
| CN101990227B (en) * | 2009-08-07 | 2015-10-21 | 中兴通讯股份有限公司 | The method for building up of data channel and device between access service network network element |
| WO2011020323A1 (en) * | 2009-08-20 | 2011-02-24 | 中兴通讯股份有限公司 | Idle exit path establishment method and device for an access service network |
| CN101640912B (en) * | 2009-08-31 | 2013-07-03 | 中兴通讯股份有限公司 | Switching method and device for accessing service network |
| EP2475199A4 (en) * | 2009-08-31 | 2016-06-15 | Zte Corp | Handover method and device for an access service network |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2010075727A1 (en) | 2010-07-08 |
| CN101478781B (en) | 2010-12-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2013990B1 (en) | Methods and apparatus for resource management architectures for internet protocol based radio access networks | |
| JP4971312B2 (en) | Terminal apparatus having handover function based on SCTP and handover method | |
| CN101478781B (en) | Processing method for data transmission exception and path functional entity | |
| CN101589594A (en) | Multi-link support for network based mobility management systems | |
| CN101730072B (en) | Packet data web gateway identification saving method and system in multi-access scene | |
| CN101742576B (en) | Method and device for recovering reserved GBR load | |
| JP7104143B2 (en) | Communication method and communication device | |
| WO2002073906A1 (en) | Mobile terminal management system, mobile terminal, agent, and program | |
| CN102217360A (en) | Method and device for processing failures of mobility management device in idle mode signaling reduction activated scene | |
| CN103249096B (en) | A kind of switching handling method, equipment and system | |
| CN101772193A (en) | Method, system and mobile access gateway for optimizing local routing | |
| CN101589602A (en) | Message ordering for network based mobility management systems | |
| CN103686883A (en) | Method and device for performing data flow migration in multiple wireless access networks | |
| CN101730062A (en) | Method for processing exception between nonadjacent nodes | |
| CN105282803A (en) | Communication interface and information transfer method and system based on the same | |
| CN103428787A (en) | Base station switching method and device | |
| WO2013064069A1 (en) | Bearer switching method, home nodeb gateway and home nodeb | |
| CN102036377B (en) | Method, system and network element for initiating active paging | |
| WO2017028637A1 (en) | Gateway recovery processing method and device | |
| CN104754767A (en) | State update method and equipment | |
| CN106797626A (en) | A kind of beep-page message sending method and equipment | |
| CN101730125A (en) | Method for carrying out node detection between nonadjacent nodes | |
| CN104145488A (en) | Service processing method, system and related device | |
| CN102291735B (en) | Method and device for tunneling protocol (GTPC) signaling interaction of evolved packet core (EPC) network | |
| CN102365845B (en) | Method, system and network equipment for local routing implementation |
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 |
Granted publication date: 20101222 Termination date: 20171231 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |