CN102860084A - Method and device for adapting a data path for a mobile entity in a communication network - Google Patents
Method and device for adapting a data path for a mobile entity in a communication network Download PDFInfo
- Publication number
- CN102860084A CN102860084A CN2011800026951A CN201180002695A CN102860084A CN 102860084 A CN102860084 A CN 102860084A CN 2011800026951 A CN2011800026951 A CN 2011800026951A CN 201180002695 A CN201180002695 A CN 201180002695A CN 102860084 A CN102860084 A CN 102860084A
- Authority
- CN
- China
- Prior art keywords
- entity
- delivery function
- data path
- binding
- mobility binding
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/34—Modification of an existing route
- H04W40/36—Modification of an existing route due to handover
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
According to the invention, a method and a device for adapting a data path for a mobile entity (201) in a communication network are suggested. The communication network has at least one forwarding entity (203, 205) for providing data packets for the data path and a plurality of mobility binding entities (207, 209) for forwarding data packets on the data path, wherein a first mobility binding 10 entity (207) is allocated to the data path for the mobile entity (201) according to binding information for the mobile entity (201). The method has a step receiving (101) a re-allocation request for re-allocating a second mobility binding entity (209) to the data path for the mobile entity (201), a step of updating (103) the binding information for the mobile entity (201) on the basis of the received re-15 allocation request, a step of forwarding (105) data packets received from the forwarding entity (203, 205) by the first mobility binding entity (207) to the second mobility binding entity (209) until the updated binding information is received at the forwarding entity (203, 205), and a step of forwarding (107) data packets from the forwarding entity (203, 205) to the second mobility binding entity (209) after the 20 updated binding information is received at the forwarding entity (203, 205).
Description
Background technology
The present invention is with to carry out communication in communication network relevant, especially radio communication system is such as second-generation system (comprising global system communication system (GSM)) or third generation partner program (3GPP) system (comprising universal mobile telecommunications telecommunication system (UMTS) or Long Term Evolution (LTE)).
In present communication network, can be connected to packet data network by mobile entities such as portable terminals, for example the Internet.For this reason, mobile communication supplier can provide multiple entity (such as gateway) usually, connects so that portable terminal can be set up packet data network.
For example, if portable terminal is connected to communication network by GPRS Support Node (GSN) (for example base station), namely can obtain assign one fixing, aim at portable terminal and the data path set up.Especially, for those packets that transmits from and be sent to portable terminal, each entity can connect between portable terminal and base station targetedly.
Therefore, transmit by data path even without packets need, also can distribute data path.In addition, as long as mobile entity keeps and being connected of base station, just cannot change the entity on the data path.Therefore, if in the portable terminal connection procedure, network data changes, and the data path of so having set up will become suboptimum.Correspondingly, if for portable terminal distributes the new data path, the connection between portable terminal and the base station will be interrupted so, causes interrupting with being connected temporarily of packet data network.
In traditional communication system, such as the packet switching mobile system, the standardization body such as 3GPP and IETF can consider each mobile node, the specific data path, and adopting has the data path of strict demand transmitted by the data traffic of mobility limitation with processing in length.Therefore, packet data network (PDN) gateway (GW) will be selected a single mobility binding entity (MBE).May between mobile node and mobility binding entity, set up one group of tunnel.
Owing to having strict traditional binding relationship between mobile node and the mobility binding entity, so the size of moving range fixes, and is irrelevant with any mobility relevant feature or the mobility pattern of mobile node.For example, wireless connectivity devices mobile and that be fixed on certain position has the moving range identical with mobile device.
For example, in 3GPP EPC (evolution block core) standard, can connect (for example subscriber equipment (UE)) for each PDN of mobile entity or mobile node and select a PDN Gateway, between UE and PDN GW, set up one group of tunnel simultaneously.At this, everybody may find, can set up many PDN data paths.But the data traffic on these multiple PDN data paths possibly can't keep seamless and dynamic balance.
In addition, 3GPP EPC provides fixing moving range, for example uses optimization data path and the transparent mobility of identical PDN GW, and is irrelevant with the mobility pattern of subscriber equipment.This expression, the moving range size is identical, for example, household electrical appliances have identical moving range with smart mobile phone.In both of these case, for mobile UE and the restricted UE of mobility, physical quantities must be identical to keep mobile management related, for example eNodeB, Serving-GW (S-GW) and PDN GW.In addition, must between the entity of equal number, set up the tunnel.
For bypass flow, 3GPP can select PDN GW neatly according to APN (APN).Bypass possibly can't dynamically be adjusted.
By convention, for each UE with is connected PDN and connects according to the fixing moving range of conventional method definition.Therefore, need pre-configured based on offline network plan and size.For example, the equipment that keeped in repair recently comprises the restricted equipment of mobility, and its processing method is identical with the mobile management function of mobile device.Moving range is fixed, need to carry out for deployment pre-configured, irrelevant with user's mobility pattern.In addition, in the situation that needs change moving range for example changes in response to the bypass data flow, then be necessary for part or all of data traffic and set up new PDN connection.。
Summary of the invention
The target that the present invention will realize is that improved data path binding is provided in communication network.
According to first aspect, we will be for selecting data path to propose a suggesting method for mobile entity in the communication network.Communication network has at least a Delivery Function to be used to data path that packet is provided, and there are a plurality of mobility binding entities to be used for forwarding data bag on data path, wherein, according to the binding information of mobile entity, first mobility binding entity can be assigned to the data path of mobile entity.The method can be divided into a plurality of steps: it is to receive to redistribute request that a step is arranged, and second mobility binding entity is reassigned to the data path of mobile entity; It is according to the request of redistributing that receives that a step is arranged, and upgrades the binding information of mobile entity; It is the packet of transmitting from Delivery Function that a step is arranged, and its method is that first mobility binding entity is forwarded to second mobility binding entity, until Delivery Function receives the binding information of renewal; Also having a step is after Delivery Function is received the binding information of renewal, and the package forward that Delivery Function is sent to second mobility binding entity is gone out.
Then, namely can provide a data path binding self-adapting program that is retained in the communication network, upgrade respectively the binding information on the Delivery Function.
Because the data path binding becomes the second mobility binding entity (MBE) from the first mobility binding entity, so the first mobility binding entity also can be described as " source MBE ", the second mobility binding entity can be described as " target MBE ".The request of redistributing may be asked in data path for the mobility entity with target MBE alternate source MBE.
The request of redistributing may comprise a cover sign, is used to indicate target MBE.Source MBE may receive the request of redistributing.Then, source MBE just has the sign of target MBE.Because source MBE knows sign, also just known the identity of target MBE, so source MBE may be with package forward to target MBE.In Delivery Function received time interval between the binding information redistribute and receive renewal, Delivery Function may not know still that MBE redistributes.Thus, Delivery Function just can continue Packet Generation to source MBE.Because source MBE may be with target MBE binding so that with package forward to target MBE, so packet can not be left in the basket.That is to say, because be sent to the packet of source MBE from Delivery Function, can be forwarded to again target MBE from source MBE, so can prevent data-bag lost.
In detail, data path can be in the situation that loss of data do not occur and redistribute, whole Delivery Function, source mobility entity and Suitable For Moving-goal Problems examination question are passed in binding because packet can be followed data path, until Delivery Function is received the binding information of renewal.After Delivery Function is received the binding information of renewal, data path will switch to the sequence of Delivery Function and target MBE.
According to the part performance, when using the method, Delivery Function may also can receive the request of redistributing from the first mobility binding entity, and can be for mobile entity, from Delivery Function to the second mobility binding entity, upgrade the mobile entity binding information in Delivery Function and/or the Delivery Function packet.
According to the part performance, this process can not impact the data in the transmission.So packet need not to cushion.
According to the part performance, mobility binding entity (MBE) only can just be redistributed after receiving the request of redistributing.Therefore, data path only in the situation that needs just can upgrade.In addition, selected even target MBE is moved entity according to the part performance, in target MBE, all need not to set up data path, unless data traffic must be forwarded.
According to the part performance, the binding information of renewal may be to transmit the form of Delivery Function response, and it is the message of mobile entity that described Delivery Function is transmitted target, perhaps from the message of mobile entity.
In addition, according to the part performance, in Delivery Function, can not upgrade binding information or mobility binding information, unless this Delivery Function transmit at least one packet to or from mobile entity.
According to the part performance, the request of redistributing may be one and reselect request.This situation may occur in redistributing: a mobility binding entity has been assigned to the data path of mobile entity, and the mobility binding entity that distributes is substituted by another mobility binding entity.
According to the part performance, can make neatly the data path self adaptation or redistribute decision according to different parameters, these parameters comprise offered load, mobile entity, mobility or similar content.
By the present self-adapting program of data path binding, can more effectively be controlled at the data traffic of certain carrier network repeating, especially in granularity in various degree.It is worth mentioning that, source MBE may use traffic flow template (TFT) to distinguish the data traffic that has been sent to target MBE.In addition, Delivery Function may be forwarded to a plurality of MBE simultaneously with the flow by traffic filtering.
According to the part performance, in the situation of not relevant with mobile entity data traffic, existing program can reduce signal transmitting and receiving.
In addition, according to the part performance, need not forwarded mechanism (for example IP route) is modified.According to the part performance, existing program can have precedence over various forwarding mechanisms and be used, and can not revise the forwarding mechanism of bottom-layer network transmission.
According to the part performance, mobility binding entity (MBE) can be any entity that configures for forwarding data bag on data path.In addition, Delivery Function can be any entity that configures in order to provide packet to data path.Mobile entity can be a mobile node, for example a subscriber equipment, a mobile phone or a smart phone.
According to first enforcement of first, the method can be divided into a plurality of steps: it is to receive the request of redistributing at the first mobility binding entity that a step is arranged; It is the request of redistributing of receiving according to first mobility binding entity that one step is arranged, for mobile entity upgrades binding information; Have a step with the binding information that upgrades from the first mobility binding entity transmission to Delivery Function.
In first form of implementation, first or source MBE can be the entities of being responsible for receiving the request of redistributing.The request of redistributing may be an event of can the trigger data path binding upgrading.In detail, source MBE may be from Delivery Function receive data bag, because this may be a unique known paths that is applicable to the mobile entity of separately appointment between Delivery Function and the MBE.May send packet from mobile entity, also may be with Packet Generation to mobile entity.This expression uplink and downlink all are attainable.
Because the data of receiving are applicable to or come from mobile entity, and the MBE of this mobile entity has changed because redistributing from source MBE to target MBE asked, so source MBE can be responsible for the deal with data routing update.This expression, in this first form of implementation, source MBE is for the entity that upgrades binding information.In addition, source MBE can usage data path binding information, the package forward that will receive from Delivery Function is to target MBE, especially in the situation that identify label demonstrates target MBE identity.Described identify label is a part of redistributing request.In addition, source MBE can with the form of the binding information after the renewal of specifying mobile entity, be sent to Delivery Function with new binding information.
In the very first time (source MBE receives the request of redistributing) with in the time interval between the second time (binding information after Delivery Function receives renewal), packet can be sent through whole data path [Delivery Function-source MBE-target MBE], and this is applicable to uplink and downlink.
In addition, when Delivery Function was received transmission from the binding information of the renewal of source MBE, Delivery Function can replace with the data path binding information binding information of the renewal that newly receives.This can allow Delivery Function with package forward to target MBE, and can not be forwarded to the source MBE that specifies mobile entity.Therefore, receive the binding information of renewal after, Delivery Function can forward the data to target MBE.Thus, uplink and downlink, packet all can be transmitted through data path [Delivery Function-target MBE].
According to second enforcement of first, in the method: it is that request is redistributed in the reception of the first mobility binding entity that a step is arranged, and comprises an identify label in the request and redistribute, and represents the identity of the second mobility binding entity; It is to extract identify label the request from redistributing of receiving that a step is arranged; It is that the forwarding data bag that first mobility binding entity is received from Delivery Function is forwarded to second mobility entity, until Delivery Function is received the binding information of renewal according to the identify label of extracting that a step is arranged.
According to the 3rd enforcement of first, the method can be divided into a plurality of steps: it is to receive the request of redistributing at the second mobility binding entity that a step is arranged; It is the request of redistributing of receiving according to the second mobility binding entity that a step is arranged, for mobile entity upgrades binding information; It is that the binding information that will upgrade is from the second mobility binding entity transmission to the first mobility binding entity and Delivery Function that a step is arranged.
The 4th enforcement according to first, one of them step of the method is in time interval between the very first time (request is redistributed in reception) and the second time (Delivery Function is received the binding information of renewal), sets up binding between the first mobility binding entity and second mobility binding entity.Binding can be mobility binding, especially in the situation that comprise a mobile environment.
Mobile environment may comprise at least following items one of them: policy and toll control (PCC), service quality (QoS), rule and/or Internet protocol (IP), tunnel are set up.
According to the 5th enforcement of first, data path distributes for data traffic, and data path has just had mobile entity, Delivery Function, the first mobility binding entity and/or the second mobility binding entity like this.
According to the 6th enforcement of first, data path distributes for data traffic, depends on the binding information of mobile entity, and data path just can have different entities within the different time like this.Front in the very first time (receiving the request redistributed), data path has mobile entity, Delivery Function and first mobility binding entity.
Between the very first time and the second time (Delivery Function is received the binding information of renewal), data path has mobile entity, Delivery Function, first mobility binding entity and the second mobility binding entity.After the second time, data path has mobile entity, Delivery Function and the second mobility binding entity.
According to the 7th enforcement of first, if data traffic rises from mobile entity, this data traffic will on data path, transfer to the mobility binding entity of distribution from mobile entity by Delivery Function.Therefore, data traffic can be transmitted via the uplink data path.
According to the 8th enforcement of first, if the data traffic destination is mobile entity, this data traffic will on data path, transfer to mobile entity by the mobility binding entity that distributes from Delivery Function.Therefore, data traffic can be transmitted via the downlink data path.
The 9th enforcement according to first, first data path distributes for the uplink data traffic, second data path then distributed for the downlink data flow, and wherein the renewal of the binding information in first data path and second data path will be carried out simultaneously.
According to the tenth enforcement of first, when Delivery Function was received a packet from specific mobility binding entity, Delivery Function can be set up one by the reverse data path of specific mobility binding entity.
The 11 enforcement according to part provides a plurality of independent Delivery Function, in order to a plurality of data paths are distributed to mobile entity.
In detail, Delivery Function may not need use uplink and downlink.Therefore, can use simultaneously a plurality of data paths, and can realize seamless exchange.For example, if Delivery Function refers to eNodeBs or access point, MBE is the gateway in the operator master territory, just mobile entity can link a plurality of access networks, for example many Interface Moving node simultaneously.
In addition, if Delivery Function refers to operator's borderline entity in master territory, MBE is gateway and near mobile entity, just can receive the data traffic of mobile entity from IP master territory by the link of multi-core network, and not need indirectly by any central entities (for example proxy gateway (P-GW)).In addition, if made decision-making (for example multipath support license) based on strategy, just identical mobile entity can use a plurality of MBE simultaneously.
In addition, mobile node data traffic division and merging all can realize, especially when gateway has detecting function based on flow.Thus, just can use simultaneously a plurality of data paths by a single MBE.
According to the 12 enforcement of first, the mobility binding entity refers to and is in the borderline access network gateway in operator master territory, couple in router, eNodeB, access point/base station or Delivery Function.
According to the 13 enforcement of first, Delivery Function refers to eNodeB, access point/base station, couple in router or backhaul entity, to guarantee package forward at least one gateway.
Any type of enforcement of first can be interosculated, to obtain other form of implementation of first.
According to second aspect, the present invention is relevant with computer program, is used for forming a program code, when at least one computer moves, can carry out the data path employing method of certain mobile entity in the communication network.
According to third part: an equipment is arranged, allow certain mobile entity can adopt data path in the communication network, this equipment has at least one Delivery Function (so that packet is provided for data path) and a plurality of mobility binding entity (so that on data path forwarding data bag); In addition, according to the binding information of mobile entity, the data path of mobile entity obtains and has distributed first mobility binding entity, and this equipment composition comprises:
Receiving entity be used for to receive the request of redistributing, in order to the second mobility binding entity is redistributed data path to mobile entity,
More novel entities is used for upgrading the binding information of mobile entity according to the request of redistributing of receiving,
The first Delivery Function, the forwarding data bag that is used for the first mobility binding entity is received from Delivery Function is forwarded to the second mobility binding entity, until Delivery Function receives the binding information of renewal, and
The second Delivery Function is used for after Delivery Function is received the binding information of renewal, will be from package forward to the second mobility binding entity of transmitting entity.
Receiving entity can be any receiver or any receive mode.In addition, more novel entities can be any update mode.Each Delivery Function also can be any pass-through mode.
The whole bag of tricks, especially receiving entity, more novel entities and each Delivery Function all may be implemented in hardware or the software.If described method is implemented in the hardware, it just may be an equipment (for example computer or processor), also may be system's part (for example computer system).If described method is implemented in the software, it may be a computer program product, and for example function, usual practice, program code maybe can be carried out object.
According to the 4th part, system's (especially communication system) comprises at least one can allow certain mobile device in the communication network adopt the equipment of data path.
Description of drawings
Hereinafter will contrast the following drawings, to more embodiment of the present invention description of making an explanation, wherein:
The form of implementation that Fig. 1 shows is to allow certain mobile device in the communication network adopt the method for data path,
The form of implementation that Fig. 2 shows is the layout of implementing the contained step of Fig. 1,
The form of implementation that Fig. 3 shows is the data path of concluding according to third step shown in Figure 1,
The form of implementation that Fig. 4 shows is the data path of concluding according to the 4th step shown in Figure 1,
What Fig. 5 showed is the preparation flow process of concluding according to form of implementation,
What Fig. 6 showed is the downlink data manipulation flow process of concluding according to form of implementation,
What Fig. 7 showed is the uplink data manipulation flow process of concluding according to form of implementation,
The form of implementation that Fig. 8 shows is to allow interior certain mobile device of communication network adopt the equipment of data path.
Embodiment
The embodiment that Fig. 1 describes is to allow interior certain mobile device of communication network adopt the method for data path.
Method form of implementation shown in Figure 1 comprises method step 101,103,105 and 107, with reference to the layout among Fig. 2, and has configured the described layout of Fig. 2 200 in the description process, is used for the described step 101-107 of execution graph 1.
The layout 200 that Fig. 2 is described has shown 201, Delivery Function of a mobile node (MN) (FE) 203 (with MN 201 direct connections) and another Delivery Function (FE) 205.Between two Delivery Function (FE) 203 and 205, the mobility binding entity (MBE) 207 and 209 of two direct connections is arranged.
According to the binding information of mobile entity 201, source MBE 207 is assigned to the data path of MN 201.
In step 101, receive that is redistributed a request, request reassigns to second or target MBE 209 data path of MN 201.Redistribute and may represent: source MBE 207 is dispensed to the data path of MN 201, this distribution condition is deleted, the substitute is target MBE 209 and is assigned to described data path.For example, source MBE 207 receives the described request of redistributing.
In step 103, the binding information of MN 201 upgrades according to the request of redistributing of receiving.Described renewal can be carried out by MBE 207.
In step 105, be received from the packet of Delivery Function 2 03 or 205, be responsible for being forwarded to target MBE209 by source MBE 207, until Delivery Function 2 03 or 205 is received the binding information of renewal.For uplink, it is Delivery Function 2 03.On the contrary, for downlink, then be Delivery Function 2 05.
What in this, Fig. 3 showed is the form of implementation that data path 300 was concluded according to the 3rd step shown in Figure 1.In situation shown in Figure 3, binding between source MBE 207 and the target MBE 209, its time can equal the time interval between the very first time (receiving the request redistributed) and the second time (binding information that Delivery Function 2 03 (uplink) or 205 (downlink does not show) upgrades) at least.
In step 107, receive the binding information of renewal at Delivery Function 2 03 or 205 after, the packet that is received from Delivery Function 2 03 or 205 will be forwarded to target MBE 209.As mentioned above, for uplink, will be transmitted by Delivery Function 2 03.On the contrary, for downlink, then transmitted by Delivery Function 2 05.
What in addition, Fig. 4 showed is to implement according to the data path that step 107 is concluded.Delivery Function 2 03 (up) or 205 (descending, show) will be received packet-as shown by arrows-and directly be forwarded to target MBE 209, and it may be with package forward other entity to the communication network.In step 107, may not need to connect source MBE 207, this is because the identity that Delivery Function 2 03 has been received the binding information of renewal and known target MBE209.
Summary: data path distributes for data traffic, depends on the binding information of MN 201, and thus, data path just can have different entities in different time.Front in the very first time (receiving the request redistributed), data path has mobile entity 201, Delivery Function 2 03 or 205, and source MBE 207.Between the very first time and the second time (Delivery Function 2 03 or 205 is received the binding information of renewal), data path has mobile entity 201, Delivery Function 2 03 and Delivery Function 2 05, source MBE 207 and target MBE 209.After the second time, data path has mobile entity 201, Delivery Function 2 03 or 205, and target MBE 209.
What Fig. 5 showed is the preparation flow process of concluding according to form of implementation.
Fig. 5 shows is according to the preparation flow process that can be concluded by the form of implementation that communication system 500 is carried out.Communication system 500 shown in Figure 5 has 503, the source MBE 505 in 501, base stations of a mobile node (MN) (BS), target MBE507 and Delivery Function border (FE-BR) 509,511,513.In the situation that be without loss of generality, Fig. 5 has also shown three Delivery Function borders (FE-BR) 509,511,513.
In Fig. 5, the solid line four-headed arrow represents scrupulously forwarding information.In addition, the dotted line four-headed arrow expresses possibility can provide loose information.Single arrow represents movable process step.
The described example shown of Fig. 5 be binding relationship rigorous between MN 501 and the BS 503 and a loose path of pointing to IP master territory.Uplink is connected expression and has implemented rigorous binding with downlink.The loose path in IP master territory is pointed in each loose descending connection (dotted line four-headed arrow) representative.
What BS 503 represented is an entity, and MN 501 binds in order to carry out communication with this entity scrupulously.As the example of evolution block core (EPC), BS 503 can be expressed as eNodeB.
In addition, Delivery Function border (FE-BR1, FE-BR2, FE-BR3) 509,511,513 is functions, is used for data traffic is forwarded to IP master territory from MN 501, perhaps is forwarded to MN 501 from IP master territory.As mentioned above, in example shown in Figure 5, having considered altogether three FE-BR, is respectively 509,511 and 513.FE-BR 509,511 and 513 can both by and MN 501 between exist the source MBE505 of data path binding that data traffic is forwarded to MN 501.This is called as " loose descending connection ".
Therefore, between BS 503 and source MBE 505, may set up UL and DL path.This may be included in the PCC flow process of carrying out on BS 503 and the source MBE 505.Source MBE 505 receives that any one is sent to the packet of MN 501 from FE-BR 509,511,513.Source MBE 507 may be according to the low layer routing mechanism, with package forward to FE-BR 509,511,513 any one.Source MBE 505 is that MN 501 keeps binding:
[MN identity, IP address, IMSI, BS, *],
Wherein the DL data traffic of MN 501 can be forwarded to the BS 503 of BS representative in the above-mentioned binding, and the UL data traffic may be sent to * representative FE-BR 509,511,513 any one.
In the step 1 of Fig. 5, source MBE 505 reselects decision for MN 501 has made, in order to use target MBE 507.Reselecting or redistribute decision can receive by external trigger, for example is connected to the MBE 507 of MN 501 by other BS (demonstration is not arranged, switch such as access network).In addition, can use various management means, such as attended operation.
In step 2, source MBE 505 transfers to target MBE 507 with the forwarding information of MN 501:
[MN identity, IP address, IMSI, BS, *],
Wherein the UL data traffic of MN 501 can be forwarded to BS 503, data traffic may be sent to * representative FE-BR 509,511,513 any one.In addition, target MBE 507 can store the forwarding information of transmission, and knows which destination is data traffic be sent to from MN 501, or data traffic is sent to MN501 from which source.
In step 3, source MBE 505 can store with the form of following forwarding entry the identity of target MBE 507:
-[MN identity, IP address, IMSI, target MBE, target MBE],
-wherein, first target MBE that mentions represents that the data traffic of MN 501 has been forwarded to 507, the second target MBE that mention of target MBE and has represented that the UL data traffic may be sent to target MBE 507.
Therefore, all packets related with MN 501 will be transmitted by target MBE 507.
Note that in step 2, target MBE 507 may ask the PCC rule of PCRF (policy control and fees policy function).Because data traffic can all be transmitted by target MBE 507, single PCEF (policy control and charge execution function) can be used for charging-carry out by target MBE 507 after step 2.
As mentioned above, what Fig. 6 showed is the downlink data manipulation flow process of concluding according to form of implementation, can be responsible for execution by communication system 500.Communication system 500 shown in Figure 6 is corresponding to the communication system among Fig. 5.
The prerequisite of example shown in Figure 6 is: executed preparation flow process shown in Figure 5 has also been grasped following information:
The BS:[MN identity, IP address, IMSI, MN, source MBE]
Source MBE:[MN identity, IP address, IMSI, target MBE, target MBE]
Target MBE:[MN identity, IP address, IMSI, BS, *]
The FE-BR:[MN identity, IP address, IMSI, source MBE, *]
In step 1, MN 501 with the UL Packet Generation to BS 503.
In step 2, BS 503 is according to its UL mobility binding information, with Packet Generation to source MBE 505.
In step 3, source MBE 505 checks the data path information, according to its UL mobility binding information, with Packet Generation to target MBE 507.
In step 4, target MBE 507 receives packet and makes and transmit determining, with Packet Generation to the FE-BR (for example FE-BR150) that is fit to, again with Packet Generation to IP master territory.
In step 5, source MBE 505 first forwarding information message is sent to BS, comprising: [MN identity, IP address, IMSI, MN, target MBE]
In step 6, BS 503 can store new forwarding information, so as with the UL package forward to target MBE 507.Therefore, BS 503 can directly be forwarded to target MBE 507 with the UL packet.
In step 7, be sent to the packet in IP master territory according to what receive from MBE 507, can select to determine that by FE-BR1509 the new MBE of MN 501 is target MBE 507 and in inside its data path binding information is changed to [MN identity, the IP address, IMSI, target MBE, *].
Therefore, FE-BR1509 can be with the DL package forward to target MBE 507.
What Fig. 7 showed is the uplink data manipulation flow process of concluding according to form of implementation, can be responsible for execution by communication system 500.This communication system 500 is corresponding to the communication system among Fig. 5 and Fig. 6.
The prerequisite of example shown in Figure 7 is: executed preparation flow process shown in Figure 5 has also been grasped following information:
The BS:[MN identity, IP address, IMSI, MN, source MBE]
Source MBE:[MN identity, IP address, IMSI, target MBE, target MBE]
Target MBE:[MN identity, IP address, IMSI, BS, *]
The FE-BR:[MN identity, IP address, IMSI, source MBE, *]
[*，*，*MBE1，MBE1]
In step 1, FE-BR2511 receives the DL packet that is sent to MN 501 from IP master territory.
In step 2, FE-BR2511 is according to its DL mobility binding information, with Packet Generation to source MBE 505.
In step 3, source MBE 505 checks the data path binding informations, according to its DL mobility binding information, with Packet Generation to target MBE 507.
In step 4, target MBE 507 receives packet and makes and transmit determining, packet is forwarded to BS 503, BS 503 again with Packet Generation to MN 501.
In step 5, source MBE 505 first forwarding information message is sent to FE-BR2511, comprising: [MN identity, IP address, IMSI, target MBE, *]
In step 6, FE-BR2511 can store new forwarding information, so as with the DL package forward to target MBE 507.
Therefore, FE-BR2511 will directly be forwarded to target MBE 507 with packet.Owing to not receiving any data traffic by FE-BR1 509 or FE-BR3 513, the loose DL route of these entities still is retained on the source MBE 505.
In step 7, according to the packet that is about to be forwarded to from target MBE 507 MN 501 of receiving, BS 503 determines that optionally new MBE is target MBE 507 and in inside its data path binding information is changed to: [MN identity, the IP address, IMSI, MN, target MBE].If the uplink transfer of data occurs in before the downlink transfer of data, just this information is available.
According to the part performance, even be in the stage that transfers to Flat Architecture from EPC (evolution block core), the existing adaptivity of binding still can realize disposing easily.For example, cooperate following items, can be adopted:
MBE (for UL) among FE among the eNodeB and the S-GW/PDN GW, and
FE in the operator IP master territory and the MBE (for DL) among the PDN GW.
The form of implementation that Fig. 8 shows is to allow interior certain mobile device of communication network adopt the equipment 801 of data path.Communication network has a Delivery Function that is used to data path that packet is provided at least, and a plurality of mobility binding entity for forwarding data bag on data path.According to the binding information of mobile entity, first mobility binding entity can be assigned to the data path of mobile entity.
Receiving entity 803 is configured to redistribute request for reception, in order to second mobility binding entity redistributed data path to mobile entity.
More novel entities 805 is configured to upgrade the binding information of mobile entity for according to the request of redistributing of receiving.
In addition, first Delivery Function 807 is configured to be forwarded to second mobility binding entity for the forwarding data bag that first mobility binding entity is received from Delivery Function, until Delivery Function receives the binding information of renewal.
In addition, second Delivery Function 809 is arranged to after Delivery Function is received the binding information of renewal, will be from package forward to the second a mobility binding entity of transmitting entity.
Claims (15)
1. the adaptive method of mobile entity (201) data path, (201 in a communication network for this mobile entity, at least comprise a Delivery Function (203,205) and a plurality of mobility binding entity (207,209), Delivery Function provides packet for described data path, and the mobility binding entity is the forwarding data bag on described data path; According to the binding information of mobile entity (201), for obtaining, the data path of mobile entity (201) distributes the first mobility binding entity (207), and the method comprises:
Receive (101) and redistribute request, the second mobility binding entity (209) being redistributed the data path to mobile entity (201),
Be used for upgrading the binding information of (103) mobile entity (201) according to the request of redistributing of receiving, and
After described Delivery Function (203,205) is received the binding information of renewal, will be from the package forward (107) of transmitting entity (203,205) to described the second mobility binding entity (209).
2. described method according to claim 1 comprises:
Locate to receive the request of redistributing at first mobility binding entity (207),
According to the request of redistributing that the first mobility binding entity (207) is received, upgrade the binding information of mobile entity, and
The binding information that upgrades is transferred to Delivery Function (203,205) from the first mobility binding entity (207).
3. according to the described method of any claim in the aforementioned claim, comprising:
First mobility binding entity (207) receives the request of redistributing, and described redistributing comprises an identify label in order to representing the identity of the second mobility binding entity (209) in the request,
Obtain described identify label the request from redistributing of receiving, and
According to the described identify label that gets access to, the forwarding data bag that described the first mobility binding entity (207) is received from Delivery Function (203,205) is forwarded to described the second mobility entity (209), until Delivery Function (203,205) is received the binding information of renewal.
4. according to the described method of any claim in the aforementioned claim, comprising:
Described the second mobility binding entity (209) receives the request of redistributing,
According to the request of redistributing that described the second mobility binding entity (209) is received, upgrade the binding information of described mobile entity, and
The binding information that upgrades is transferred to first mobility binding entity (207) and described Delivery Function (203,205) from the second mobility binding entity (209).
5. according to the described method of any claim in the aforementioned claim, comprising:
In the time interval between the very first time and the second time, between first mobility binding entity (207) and second mobility binding entity (209), set up binding, wherein the very first time is to receive the described time of redistributing request, and the second time was the time that Delivery Function (203,205) is received the binding information of renewal.
6. according to the described method of any claim in the aforementioned claim:
Wherein, data path is to distribute for transfer of data, so described data path comprises described mobile entity (201), a described Delivery Function (203,205), described the first mobility binding entity (207) and/or described the second mobility binding entity (209).
7. according to the described method of any claim in the aforementioned claim:
Wherein, carry out transfer of data according to minute being equipped with of the binding information data path of described mobile entity (201), described data path comprises described mobile entity (201), Delivery Function (203,205) and the first mobility binding entity (207) before the very first time; In the time of between the very first time and the second time, comprise described mobile entity (201), Delivery Function (203), the first mobility binding entity (207) and the second mobility binding entity (209); After the second time, comprise described mobile entity (201), Delivery Function (203,205) and the second mobility binding entity (209), wherein the very first time is to receive the described time of redistributing request, and the second time was the time that Delivery Function (203,205) is received the binding information of renewal.
8. according to the described method of any claim in the aforementioned claim:
If data traffic is sent from described mobile entity (201), this data traffic will be transferred at data path the described mobility binding entity (207,209) of distribution by mobile entity (201) by described Delivery Function (203).
9. according to the described method of any claim in the aforementioned claim:
If the data traffic destination is described mobile entity (201), this data traffic will transfer to described mobile entity (201) by the mobility binding entity (207,209) that distributes from described Delivery Function (205) at data path.
10. according to the described method of any claim in the aforementioned claim:
Wherein, the first data path is distributed to the uplink data traffic, and the second data path is distributed to the downlink data flow, and the binding information of described the first data path and described the second data path upgrades simultaneously.
11. according to the described method of any claim in the aforementioned claim:
Wherein, when described Delivery Function (203,205) was received a packet from specific mobility binding entity (207,209), described Delivery Function (203,205) was set up one by the reverse data path of described specific mobility binding entity (207,209).
12. according to the described method of any claim in the aforementioned claim:
Wherein, provide a plurality of independent Delivery Function (203,205) in order to a plurality of data paths are distributed to described mobile entity (201).
13. according to the described method of any claim in the aforementioned claim:
Wherein, mobility binding entity (207,209) is for being in the borderline access network gateway in operator master territory, couple in router, eNodeB, access point/base station or Delivery Function.
14. according to the described method of any claim in the aforementioned claim:
Wherein, described Delivery Function (203,205) is eNodeB, access point/base station, couple in router or backhaul entity, so that packet can be forwarded at least one gateway.
15. be the equipment (801) in mobile entity distribute data path in the communication network, this equipment comprises that at least one Delivery Function is used to data path that packet is provided, a plurality of mobility binding entities are used for forwarding data bag on data path; According to the binding information of mobile entity, for obtaining, the data path of mobile entity distributes first mobility binding entity, and this equipment also comprises:
Receiving entity (803) be used for to receive the request of redistributing, the second mobility binding entity being redistributed the data path to mobile entity,
More novel entities (805) is used for upgrading the binding information of described mobile entity according to the request of redistributing of receiving,
The first Delivery Function (807), the forwarding data bag that is used for described the first mobility binding entity is received from described Delivery Function is forwarded to the second mobility binding entity, until Delivery Function receives the binding information of renewal, and
The second Delivery Function (809) is used for after Delivery Function is received the binding information of renewal, will be from the package forward of transmitting entity to described the second mobility binding entity.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2011/071307 WO2012113154A1 (en) | 2011-02-25 | 2011-02-25 | Method and device for adapting a data path for a mobile entity in a communication network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102860084A true CN102860084A (en) | 2013-01-02 |
| CN102860084B CN102860084B (en) | 2016-06-22 |
Family
ID=46720099
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201180002695.1A Expired - Fee Related CN102860084B (en) | 2011-02-25 | 2011-02-25 | The method and apparatus in mobile entity matching data path in communication network |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102860084B (en) |
| WO (1) | WO2012113154A1 (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101895458A (en) * | 2009-05-18 | 2010-11-24 | 大唐移动通信设备有限公司 | Method and system for releasing packet data network connection, and data gateway |
| US7876728B1 (en) * | 2007-04-05 | 2011-01-25 | Sprint Communications Company L.P. | Maintaining path optimization during foreign agent handoff |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8526404B2 (en) * | 2006-04-25 | 2013-09-03 | Cisco Technology, Inc. | Mobile network operator multihoming and enterprise VPN solution |
-
2011
- 2011-02-25 CN CN201180002695.1A patent/CN102860084B/en not_active Expired - Fee Related
- 2011-02-25 WO PCT/CN2011/071307 patent/WO2012113154A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7876728B1 (en) * | 2007-04-05 | 2011-01-25 | Sprint Communications Company L.P. | Maintaining path optimization during foreign agent handoff |
| CN101895458A (en) * | 2009-05-18 | 2010-11-24 | 大唐移动通信设备有限公司 | Method and system for releasing packet data network connection, and data gateway |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012113154A1 (en) | 2012-08-30 |
| CN102860084B (en) | 2016-06-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| ES2827682T3 (en) | Telecommunications networks | |
| CN106664732B (en) | Apparatus and method for multipath TCP with LTE connection | |
| CN101822080B (en) | Technique for providing support for plurality of mobility management protocols | |
| US8824365B2 (en) | Method for establishing connection by HNB | |
| CN103987088B (en) | Dynamic uplink and downlink flow unloading method and system based on heterogeneous network convergence | |
| CN105813153B (en) | Inter-network switch method, network element and system | |
| US9629044B2 (en) | Apparatus and method for communication | |
| CN103857004A (en) | Wireless network user access processing method, device and system | |
| CN104038967A (en) | Data flow transmission method and data flow transmission device | |
| CN108464036A (en) | Use enhanced special core network（DNC）Method, core-network entities and the wireless transmitter/receiver unit of selection（WTRU） | |
| CN102045691A (en) | Method and device for acquiring grouped identifiers of machine type communication (MTC) equipment | |
| CN110235510A (en) | Enhance the system and method for session management in NextGen mobile core network | |
| CN103889002B (en) | Flow control method and device, mobile node, access gateway | |
| CN111567082A (en) | Traffic steering between LTE and NR | |
| CN110740149A (en) | Communication method and device | |
| CN107534608A (en) | Method and apparatus for processing data stream within a wireless communication network | |
| CN103024823A (en) | Implementing method of flow migration, terminal and grouped data network gateway | |
| US10349331B2 (en) | Packet processing method for software-defined network | |
| KR20160050483A (en) | Method for traffic path diversity in wireless communication system | |
| CN104041122A (en) | Method, apparatus and system for processing data-field service | |
| US8639233B1 (en) | Data session continuity between wireless networks | |
| KR101481337B1 (en) | Mobile Communication System Based on Software Defined Networks and Method for Processing Access of Mobile Equipment thereof | |
| JP2019057929A (en) | Communication system, data center, and communication method | |
| CN105612717A (en) | User data processing method and device and network system | |
| JP6315894B2 (en) | Method and apparatus for accessing multiple radio bearers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20160622 Termination date: 20190225 |