CN103069917A

CN103069917A - Method for establishing a data path, device and communication system

Info

Publication number: CN103069917A
Application number: CN201180005033XA
Authority: CN
Inventors: 周青; 康斯坦丁诺斯·潘蒂克斯; 康纳·帕普; 马里斯·克里斯; 佳格斯·魏佳善; 托马斯·马歌丹
Original assignee: Huawei Technologies Co Ltd; Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
Current assignee: Huawei Technologies Co Ltd; Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
Priority date: 2011-02-25
Filing date: 2011-02-25
Publication date: 2013-04-24
Anticipated expiration: 2031-02-25
Also published as: EP2507955A1; EP2507955A4; WO2012113156A1; CN103069917B

Abstract

In a method for establishing a data path for a mobile entity (110) in a communication network having one or more forwarding entities (151, 152) for providing data packets for a data path and a plurality of mobility binding entities (161, 162) for forwarding data packets on the data path, data traffic assigned to the mobile entity (110) is received by one forwarding entity (151, 152) of one or more forwarding entities (151, 152). A binding information assigned to the mobile entity (110) is requested by a request of the one forwarding entity (151, 2). In response to receiving the request of the one forwarding entity (151, 152), a mobility binding entity (161, 162) of the plurality of mobility binding entities (161, 62) is allocated. The requested binding information is provided including an identity of the allocated mobility binding entity (161, 162). The one forwarding 1 entity (151, 152) forwards the data traffic to the allocated mobility binding entity (161, 162) in dependence on the binding information.

Description

Be used for setting up the method for data path, equipment and communication system

Technical field

The present invention is relevant with communication network field, and is especially, relevant with mobile communications network.

Background technology

In current communication network, can pass through portable terminal, (for example: the internet) connect packet data network.For this reason, mobile communication provider provides some entities (for example: gateway) think that portable terminal sets up the connection to packet data network usually.

For example, if portable terminal is connected to communication network via the base station, then will and set up data path for the portable terminal fixed allocation.Especially, transmit from or be sent to each entity of the packet of portable terminal thereon, all can the movement-based terminal arrange with being connected of base station.

Therefore, usually understand the distribute data path, transmit even without the packet existence and by data path.In addition, as long as portable terminal safeguards and being connected of base station, the entity on the data path will can be not exchanged.Therefore, if in the connection procedure of portable terminal, network parameter is changed, and the data path of then having set up will become second and select.Correspondingly, if should distribute the new data path for portable terminal, then portable terminal to the connection of base station will be interrupted, and therefore, will lose the connection to packet data network temporarily.

Summary of the invention

The objective of the invention is in order to provide effective concept to set up the data path of mobile communication.

The embodiment of the invention is to realize by the characteristic of describing each claim.Embodiment in the future will follow these rights statement that rely on.

The embodiment of the invention is based upon the mobile entity that is connected to communication network and searches data path, can set up when the data service that is assigned to mobile entity exists.Correspondingly, the data path of mobile entity will be set up as requested.Therefore, as long as the data service relevant with mobile entity exists, then can be kept at the resource of untapped other data paths in the communication network.In addition, the data path of optimization can be selected when actual needs.Can also be the downloading data business of mobile entity in order to originate from the professional and target of uploading data of mobile entity, select different data paths.

For example, communication network comprises one or more Delivery Function, is used to data path that packet is provided, and a plurality of mobility binding entity, is used for forwarding data bag on data path.Then, if the Delivery Function request data path, then only would to set up data path, because Delivery Function has the data service that will be forwarded.

According to first aspect, the embodiment of the invention is relevant with the method that is used for setting up data path at communication network for mobile entity.Communication network comprises one or more Delivery Function, is used to data path that packet is provided, and a plurality of mobility binding entity, is used for forwarding data bag on data path.A Delivery Function of one or more Delivery Function receives the data service of distributing to mobile entity.By the request of a Delivery Function, ask to be assigned to the binding information of mobile entity.In order to respond the request of a Delivery Function of receiving, the mobility binding entity of a plurality of mobility binding entities will be distributed.Then, with the binding information that provides request to arrive, binding information comprises the sign of the mobility binding entity that has distributed.A Delivery Function is incited somebody to action, and based on binding information, data service is transmitted to the mobility binding entity that has distributed.

For example, communication network comprises mobile controller, and for example, management is tied to the data service of the mobile entity of communication network.Correspondingly, distribute the mobility binding entity to carry out by mobile controller.For example, mobile entity is attached to communication network and uses mobile controller to register.For example, registration comprises the reception network address (as: IP address).When registration, will not distribute and set up data path.The request of a Delivery Function will be sent to its mobile controller that distributes, and receive request, mobility binding entity with response.After distributing, the request binding information that comprises the sign identifier of the mobility binding entity that has distributed will transfer to a Delivery Function from mobile controller.

According to some forms of implementation, this assigning process can be carried out in a Delivery Function.For example, a Delivery Function has internal memory and cache, has some the selection for the mobility binding entity that distributes.Correspondingly, binding information provides by a Delivery Function self.

According to some forms of implementation, the distribution of mobility binding entity is carried out by mobile controller.The binding information that comprises the sign of distributing the mobility binding entity is stored in the cache of the cache of a Delivery Function and/or other Delivery Function.Therefore, if Delivery Function has the data service that is assigned to the mobile entity that will transmit, in case then the mobility binding entity distributes by mobile controller, it can be searched and will transmit to it mobility binding entity of the data service of cache.

First form of implementation according to a first aspect of the invention, the present invention is relevant in a method, and wherein, in order to respond the update request of upgrading binding information, the other mobility binding entity of a plurality of mobility binding entities will be distributed to mobile entity.The binding information that has upgraded will offer a Delivery Function, and wherein, the binding information that has upgraded comprises the sign of the other mobility binding entity that has distributed that is assigned to mobile entity.For example, the request of having upgraded can receive from communication network, from the receptions such as mobility binding entity of previous distribution.Can also be to receive update request (for example: be used for safeguarding purposes) by way to manage.In addition, update request can in the mobile controller internal trigger, for example, be used for the load balance purpose.

In case a Delivery Function receives the binding information that has upgraded, then can set up new data path and forwarding data business on new data path.But the data service that sends on the data path formerly then must resend.

According to some execution modes, the identity of the mobility binding entity that further distributes will be provided for the mobility binding entity of previous distribution.Correspondingly, the previous mobility binding entity that distributes can be forwarded to the data service (being assigned to mobile entity) of importing into the mobility binding entity of further appointment.Therefore, the previous data service that distributes will be directed to the mobility binding entity of the data path of new appointment again.

Second form of implementation according to a first aspect of the invention, the present invention is relevant with a method, and wherein, data path is specified for data service, and data path comprises mobile entity, one of them Delivery Function and a mobility binding entity that has distributed.

For example, if data service originates from mobile entity, then data service is by a Delivery Function, on data path from mobile entity to the mobility binding entity transmission of having distributed.Can also be, if data service take mobile entity as target, then data service will by the mobility binding entity that has distributed, be transmitted to mobile entity from a Delivery Function on data path.If data service originates from mobile entity, it can be called the business of uploading data.Correspondingly, if the target of data service is mobile entity, it can be called the downloading data business.Therefore, can distribute at least two independent data paths, that is, one is downloading data path (it is professional to be used for downloading data) and the path that uploads data (being used for the business that uploads data).

The 3rd enforcement according to a first aspect of the invention, the embodiment of the invention is relevant with a method, wherein, in order to respond the request of termination, the distribution of the mobility binding request that has distributed will be deleted, and the binding information that has upgraded provides and will offer mobility binding entity (its distribution is deleted), and the binding information that has upgraded comprises deleted distribution.Correspondingly, if do not need data path, for example, exist because be assigned to the data service of mobile entity, then can be released in the resource of using in the data path that has distributed.

For example, the binding information that has upgraded that comprises deleted distribution further offers Delivery Function (providing binding information to it in the past).Correspondingly, if after deletion distributes, Delivery Function receives the data service that is assigned to mobile entity, then will be formulated by Delivery Function the new request of binding information.

According to some execution modes, if certain distribution is carried out by mobile controller, then the deletion of this distribution is also carried out by mobile controller.

The 4th enforcement according to a first aspect of the invention, the embodiment of the invention is relevant with a method, and in the method, target is that the Delivery Function of data service by a plurality of Delivery Function of further forwarding of mobile entity receives.Delivery Function request in the future is assigned to the binding information of mobile entity.Then, with the binding information that provides request to arrive, binding information comprises the sign of the mobility binding entity that has distributed.Delivery Function in the future can be forwarded to data service the mobile entity that has distributed.

Correspondingly, if the mobility binding entity partitioning to the downlink data path of mobile entity, relevant information of distributing then mainly is the sign of the mobility binding entity that distributed, can offer other Delivery Function into mobile entity receiving downlink data business.For example, have the binding information of the mobility binding entity that has distributed, be stored in the cache of mobile controller and/or in the cache of another Delivery Function, for example, it can be Delivery Function, thereby the request of formulating causes the distribution of mobility binding entity.

The 5th form of implementation according to a first aspect of the invention, the embodiment of the invention is relevant with a method, and wherein, after binding information was offered Delivery Function, mobile link was registered between Delivery Function and the binding entity that distributed.For example, between conversion entity and mobility binding entity, set up one or more carryings, comprised the carrying of acquiescence.

According to forms of implementation more of the present invention, the registration mobile link can comprise to be set up or one of item below the definition at least: strategy and charging control, PCC, quality services, QoS, rule, Internet Protocol, IP, building tunnel.For example, the registration mobile link is subjected to mobile controller support.

In addition, mobile controller can be carried out the renewal of binding information in Delivery Function.

The 6th form of implementation according to a first aspect of the invention, the present invention is relevant with a method, and wherein, mobile entity uses mobile controller to register, and this registration comprises communication identifier is sent to mobile controller.This communication identifier comprises one of them parameter of mobile entity: Media Access Control, MAC, address, internet mobile subscriber identifier (International Mobile Subscriber Identity), IMSI, Internet Protocol, IP, address, device identifier, user identifier, user ID.Use registration, mobile controller receives the identification data business and has been assigned to the required information of mobile entity.

The 7th form of implementation according to a first aspect of the invention, the present invention is relevant with a method, wherein, the mobility binding entity that has distributed will be forwarded to from the data service that Delivery Function receives the gateway entity of packet data network, and gateway entity is one of one of a plurality of mobility binding entities or one or more Delivery Function.

According to a second aspect of the invention, the embodiment of the invention is relevant with mobile communications network, and communication network comprises one or more Delivery Function, is used to data path that packet is provided, and a plurality of mobility binding entity, is used for forwarding data bag on data path.This equipment is configured to register the mobile entity that is tied to communication network.This equipment also is configured to distribute the mobility binding entity of a plurality of mobility binding entities, is assigned to the request of the binding information of mobile entity with response, the Delivery Function of this request for receiving from one or more Delivery Function.This equipment also is configured to the binding information of request is forwarded to a Delivery Function, and this binding information comprises the binding information of the mobility binding entity that has distributed, and the data service that is assigned to mobile entity will be transmitted by a Delivery Function.

Some forms of implementation according to a second aspect of the invention, this equipment are regarded as mobile controller (such as the description of carrying out for first aspect of the present invention).

According to the further form of implementation of second direction of the present invention, this equipment can be configured to process update request to be used for according to the described renewal binding information in first aspect of the present invention.This equipment can also be configured to stop request such as processing as described in first aspect of the present invention.

Some forms of implementation according to a second aspect of the invention, this equipment are configured to carry out first method of the present invention.

According to a third aspect of the present invention, the present invention is relevant with the communication system of communication network, and communication system comprises one or more Delivery Function (being used to data path that packet is provided), a plurality of mobility binding entity (being used for forwarding data bag on data path) and according to the equipment of second method of the present invention.

Description of drawings

Below with reference to accompanying drawing further embodiment of the present invention has been described, wherein:

Fig. 1 has shown the communication network according to form of implementation;

Fig. 2 has shown the communication network according to form of implementation;

Fig. 3 has shown the flow chart according to the method for form of implementation;

Fig. 4 has shown the flow chart according to the method for form of implementation;

Fig. 5 has shown the flow chart according to the method for form of implementation;

Fig. 6 has shown the flow chart according to the method for form of implementation; And

Fig. 7 has shown the flow chart according to the method for form of implementation.

Embodiment

Fig. 1 has shown the communication network according to form of implementation.In communication network, mobile entity is regarded as mobile node, and MN, 110 is connected to mobile controller, and MC, 120 has the signal path that is represented by dotted lines.MC120 provides the part of merchant's network 130, and it is connected to data network 140.Provider network 130 comprises first and second Delivery Function, FE, 151,152 and first and second mobility binding entity, MBE, 161,162.Provider network 130 can also have Delivery Function and mobility binding entity (not being presented in the figure for whole structure).

MN110 is connected to provider network 130 by mobile link (representing with solid line).Provider network 130 also has the data connections (representing with solid line) to data network 140.FE151,152 is connected with MBE161 162 does not have usage data to connect (representing with solid line) each other, and each is connected to MC120(by signaling and is represented by dotted lines).One or more entities 151,152,161,162 can have to the connection of data network 140, thereby serve the data network gateway of provider network 130.

Next, will illustrate how MN110 is connected to respectively provider network 130 and data network 140, and data service how to transmit from and to MN110.

Therefore, after MN110 is attached to network 130, MN110 will use MC120 to register.Data path is by this additional MN110 that is linked to.When one of them FE, 151,152 had the data service that will transmit that is assigned to MN110, MC120 can select MBE161, one of 162.MC120 will set up data path for the MN110 between a FE and the selected MBE.When MBE changes, for example, changed the information in the provider network 130, will notify MC120.Then, MC120 will notify FE, and that has specified data service to MN110.

According to the annex of network, the MN110 request also (for example: the IP address that can arrive or any other network addresss that clearly indicated additional MN110 receives network environment.MC120 creates and the storing mobile binding, for example, comprise the mapping between the MN110 communication identifier, wherein communication identifier comprises at least one of following parameters of mobile entity: MAC Address, IMSI, IP address, device identifier, user identifier, user identity.This MC120 can also select the storage of finger URL identifier is used for data path, for example, and permanent entity (MN110 adopts with the similar mode in base station and is connected on it).The result is, being arranged in control plane MC120 is unique entity of system's (mainly being provider network 130), and its can be bound to the MN110 alert notification.But, be not MN110 assignment constraint data path.

About the forwarding of data service, if FE151,152 one of them have the data service that will transmit, this data service is assigned to MN110, then corresponding FE can be from the MC120 request binding information corresponding with the identifier of MN110.For example, FE can inquire that MC120 whither sends data service.In order to respond the request of FE, MC120 can distribute to MN110 with the MBE161 on the data path, one of 162.For example, MC120 can distribute a MBE, and it can receive the data service that is sent to MN110 or therefrom sends.MC120 can be chosen in the identifier of MN110 and the MBE that distributed between binding information.Correspondingly, only when transmitting the data service of distributing to MN110, just can select or distribution MBE for MN110.

About setting up auto-correlation FE to the data path that distributes MBE, MC120 can be sent to the sign of distributing MBE the FE that has sent request.For example, MC120 can inform FE sends data service to which MBE.The sign of the MBE that has distributed can send in binding information.The message that comprises binding information can be transmitted auto-correlation FE from MC120, can directly send, and also can send by the MBE that has distributed.MC120 can notify the MBE that has distributed to set up to the context of relevant FE.For example, between the MBE that is correlated with FE and has distributed, set up one or more carryings, comprised the carrying of acquiescence.MC120 can start based on user's Quality of Service, QoS, rule and strategy and charging control, PCC.The downloading data path can be set up in independent operating procedure with the path that uploads data.But upload data path and downloading data path can comprise the different entities of provider network 130.The result is that the entity on the selection data path is as the forwarding of packet.

Relevant FE is forwarded to data service the MBE that has distributed.For example, packet is transferred into the MBE that has distributed.

About the change of MBE, the update request that MC120 can receive the MN110 path and change request, wherein, this request can be from network 130 or the MBE that has distributed etc. in receive.This request can also receive by way to manage, for example, and in order to safeguard purposes.This request can in the internal trigger of MC120, for example, be used for the load balancing purpose.

In order to respond update request, MC120 distributes to MN110 with the new MBE on the data path.For example, MC120 distributes new MBE, is used for receiving from MN110 or to the data service of its transmission.Note that this operation is similar to first distribution of above-mentioned MBE, except redistributing MBE.This MC120 can select to upgrade the cache of the identifier that comprises MN110 and the binding information between the MBE that has distributed.

About the notice after the change MBE, MC120 can be sent to the identifier of newly assigned MBE one or more FE.For example, MC120 can send to the binding information that has upgraded all FE.But MC120 can only send to such binding information that has upgraded those FE of the binding information with request.The message that comprises the binding information that has upgraded can be sent to FE from MC120, can directly send, and also can send by MBE newly assigned or that distributed.MC120 can notify newly assigned MBE to set up context to FE.For example, FE and, set up one or more carryings between the newly assigned MBE, comprise the carrying of acquiescence.According to some forms of implementation, FE has cache to be used for the binding information of MN110, can upgrade these binding informations in such cache.

The result is, packet is forwarded to newly assigned MBE on the data path from FE.

Fig. 2 has shown the communication network of further form of implementation.Mobile entity or mobile node 110 can be connected to first or second base station 211,212, can be used as evolution packet-based core networks (EPC) eNodeB and implement.By these base stations 211,212, MN110 can be connected to provider network 230 and packet data network, PDN, 240.Provider network 230 comprises MC120 and a plurality of a plurality of entities 251,252,261,262 with gateway function.For example, entity 251,262 is gateway, S gateway, and entity 252,261 is PDN Gateway.The S gateway can form the SAE gateway with corresponding PDN Gateway.In the S gateway 251,262 each is connected to base station 211,212 simultaneously.PDN Gateway 252,261 has to the connection of packet data network 240.

With reference to figure 1, MBE can represent by eNodeB or another accessing points or another base station that is used for the downloading data business, by S gateway or the specific gateway of another accesses network or the download and upload data service represents, by the PDN Gateway that is used for the download and upload data service or another universal gateway represents or the Delivery Function (as being used for the provider network 230 of the business of uploading data) of boundary by provider domain represents.

Equally, FE can by be used for uploading data professional eNodeB or other accessing points or the base station represents, by be used for uploading with the S gateway of downloading data business or another Access Network particular gateway represents, by be used for uploading the PDN Gateway of downloading data business or another universal gateway represents, by being used for representing with the passback entity that is used for the download and upload data service that to the gateway forwards packet perhaps the Delivery Function by the edge that is positioned at provider domain that is used for the downloading data business represents.

Below, with reference to a plurality of programs of Fig. 2 description according to each embodiment form.But, should be appreciated that the entity that shows among Fig. 2 should not be regarded as restriction, and only is in order better to illustrate.Correspondingly, suppose between MN110 and base station, to have the restriction binding, when relating to the IP territory that is represented by PDN240, suppose to use loose data path.The base station represents strictly to bind MN110 to be used for the entity of communication.For example, the base station can be represented by the eNodeB of EPC.Universal gateway (GG) expression is positioned at the gateway on the data path that is used to MN110 to safeguard mobility binding.For example, for EPC, GG can be represented by PDN Gateway or PDN and S gateway.The carrying that GG can be required for based on the user distributes and PCC.The Delivery Function FE-BR that is positioned at boundary can be forwarded to data service and/or MN110 and/or from the function of the data service in IP territory.MC represents independent function, for example, and MME.MN110 can be tied to a plurality of base stations simultaneously.But in the example below, MN110 is regarded as only being tied to a base station.Correspondingly, downloading data is professional must arrive this certain base station in order to be forwarded to MN110.

Fig. 3 has shown the flow chart according to the operation of forms of implementation more of the present invention.Described communication and the operation of MN301 herein, it can be used as subscriber equipment, UE, base station 303(can be used as eNodeB and implement), first and second GG305,307(can be used as PDN Gateway and implement), mobile controller 309(can be used as to have and increases powerful MME and implement) and Fe, the FE-BR, 311,313 that are positioned at the provider domain border.

In this Fig. 3, the annex of MN301 to network described.In step 320, MN301 has set up the connectivity of itself and base station 303.In step 322, the base station is to the identifier of MC309 transmission MN301, and the identifier of base station 303 is as assignment information.In this step 322, base station 303 can require to distribute to from MC309 the IP address of MN301.In step 324, MC309 is 303 reception information from the base station, and add the cache clauses and subclauses to its cache.For example, MC309 will be for storing all downloading datas business by 303 MN301 that transmit to the base station.In addition, it is noted that and can not distribute any MBE, and data service can receive from any FE-BR.It also stores 303 business that upload data of receiving from the base station, and can not distribute any MBE for uploading.Data service can be forwarded to any FE-BR.In step 326, MC309 sends to the base station and confirms.If MC309 distributing IP address is then confirmed to comprise the IP address.The result is that MN301 is stored in its reachability information among the MC309.Can not select any MBE in this stage.

Fig. 4 has illustrated and operation according to the relevant traffic aided that uploads data of some forms of implementation.In figure, shown entity 401,403,405,407,409,411,413, can be corresponding to the related entities 301 to 313 among Fig. 3.Suppose to carry out according to the program that articulates of Fig. 3.MN401 is connected to network, and MC409 has reachability information.

In step 420, MN401 403 notifies its intention to the base station.For example, notice is maybe will upload data to wrap by the arrival connection status to be sent to base station 403.

In step 422, base station 403 had not before had in the situation of data services in hypothesis, checked whether set up PCC and mobile context.In step 424, base station 403 is from MC409 request forwarding information or binding information.In step 426, the binding information that MC409 comprises MBE with inspection distributes before whether, if not, with the MBE that distributes GG1505 as MN401.

In step 428, forwarding information is sent to GG405, and can select to be sent to base station 403.Forwarding information will make GG405 can know from MN401 and ask and being connected of base station.In addition, forwarding information can be enabled GG1 and data service can be forwarded to any FE-BR to know it.

In step 430, PCC and mobile context between base station 403 and GG405, have been set up.This is set up process and can be started by GG405.Mobile link or mobile context can comprise PCC and QoS rule and IP forwarding tunnel and set up.If forwarding information is transmitted to base station 403 in step 428, then PCC and mobile context are set up and can be started by base station 403.The result of this operation is, uploads temporarily and is connected connection having set up via the path of base station 403 from mobile node 401 to GG405.

In optional step 432, GG405 can forwarding decision, namely can transmit FE-BR411,413 data services to it.Otherwise being forwarded to FE-BR can carry out by existing IP routine mechanism is static.Should be noted that only uploads data must follow the data path that has distributed.

Fig. 5 has shown the flow chart according to the operation of some forms of implementation, the downloading data traffic aided of this operation and MN.Fig. 5 has shown entity 501,503,505,507,509,511,513, and it corresponds respectively to previously described entity 301 to 313 or 401 to 413.Suppose to have carried out attended operation according to Fig. 3, MN501 will be connected to network, and MC509 has the reachability information of MN501.

In step 520, FE-BR513 will receive the downloading data bag of MN501.FE-BR513 will check whether it has the cache data relevant with MN501.The FE-BR513 that supposed not have the forwarding information buffer memory, FE-BR513 will be in step 524, from the MC509 request binding information relevant with MN501.Similar with step 426, in step 526, MC509 will check binding information and search must be to the base station 503 all downloading services of transmitting, but do not distribute any MBE.Then, MC509 can distribute GG505 as MBE, is used for the downloading data path of MN501.

In step 528, MC509 is sent to FE-BR513 with forwarding information or binding information.In addition, if before do not distributed MBE, then forwarding information or binding information can also offer the MBE that has distributed, that is, and and GG505.FE-BR513 will create the cache clauses and subclauses, and it comprises the information that receives from MC509.

In optional step 532, forwarding information or binding information can also offer base station 503.This information make that base station 503 can know that request is used for MN501 with being connected of GG505.For example, this operation is very useful to enter connection status for triggering MN501.In step 534, PCC and mobile context or mobile link between base station 503 and GG505, have been set up.This sets up process and can be started by GG505, perhaps, if base station 503 has forwarding information, also can be started by base station 503.

The result is that for a time period, perhaps professional for specific downloading data, data service will be forwarded to GG505 from FE-BR513.

Fig. 6 has shown the flow chart according to the operation of forms of implementation more of the present invention.This operation is relevant with reselecting of MBE.Fig. 6 has shown entity 601,603,605,607,609,611,613, and they can be relevant with the previous entity that shows in Fig. 3 to 5.

Suppose to carry out according to the additional process of Fig. 3, and MC509 safeguards reachability information.Suppose that also MN601 is connected to network by base station 603 and GG605.Uploading binding information is defined as the MBE that distributed with gateway 605 and is used for the business that uploads data.In addition, professional for downloading data, it has also defined and has arrived FE-BR611, one of 613 data service must be forwarded to GG605 as Delivery Function.

In step 620, will formulate that MBE redistributes strategy so that MC609 must carry out the MBE re-allocation process.For example, this operation can trigger via another base station by the additional of MN601, that is, Access Network shifts.Re-allocation process can also be by way to manage (for example: attended operation) trigger (as shown in Figure 6).In redistributing decision-making, this MC609 determines to select second GG607 to be used for MN601 as new MBE.But when uploading and the down operation time spent, MC609 will change them, so that the business of uploading data must be from the base station 603 be forwarded to GG607, and the downloading data business that receives from FE-BR611, one of 613 must be forwarded to GG607.

In optional step 622, forwarding information or binding information are provided for newly assigned MBE, i.e. GG607.This information can also be sent to base station 603.This information can make that base station 603 knows that request is used for MN601 with being connected of GG607.This information can also be sent to the MBE of previous distribution, i.e. GG605.This information is so that GG605 can delete PCC and mobile context also will be addressed to the data retransmission of MN601 to GG607.

In step 624, PCC and mobile context between base station 603 and GG607, have been set up.This is set up process and can be started by GG607.Mobile link or mobile context can comprise PCC and QoS rule and IP forwarding tunnel and set up.In this case, in step 622, information can also be sent to base station 603, PCC and mobile context are set up and can also be started by base station 603.The result of this operation is, 603 to GG603 path setting up and uploads temporarily and be connected connection to the base station from mobile node 601.

In step 626, MC609 will check that among the FE-BR611,613 which needs to upgrade.MC609 will upgrade to their forwarding informations.In step 628, FE-BR611,613 can use its cache of information updating, and the downloading data bag relevant with MN601 will be forwarded to newly assigned GG607.

Fig. 7 has shown the flow chart according to the operation of forms of implementation more of the present invention.This operation stops relevant with binding.Entity 701,703,705,707,709,711,713 can be corresponding to the previous entity of describing in Fig. 3 to 6.

Similar with more previously described forms of implementation, suppose that the GG705 distribution is used for uploading and being connected connection as MBE, MN701 is connected in the network.

In step 720, remove the decision-making that MBE distributes with formulating.Correspondingly, MC709 must carry out MBE and remove process.For example, this operation can trigger in the following manner: MN701 is in idle pulley, does not perhaps communicate within the predefined time period.Other triggers can be for from any network building-out MN701.709 determine the MBE binding of deletion MN701, in order to there is not MBE to be assigned to MN and professional for the business of uploading data and downloading data.

In step 722, MC709 will check that among the FE-BR711,713 which requires termination message.MC sends the binding information that has upgraded to FE-BR711,713, comprises the information of the distribution of relevant deletion MBE.In step 724, FE-BR711,713 will delete relevant information in its cache.

In step 726, MC709 also is sent to termination message among the GG705 of previous distribution.In addition, these information also will be sent to base station 703.In step 728, PCC and mobile context between base station 703 and the GG705 that distributed will be terminated, and this process is started by GG705.If in step 726, the binding information that has upgraded also is transferred into base station 703, and then mobile contextual termination also can be started by base station 703.

As the result of this operation, will stop uploading and the connection of being connected in the path of formerly distributing temporarily.

Obviously, above-mentioned steps can combine, and the step of can be therein carrying out in program can use the step of other programs to exchange, for example, and according to distributing and the transmission information relevant with distribution.

According to some forms of implementation, can distribute separately and upload and download path.But, in order to simplify allocation step, can distribute simultaneously and upload and download path.For uploading and the downloading data path, FE may be independent of each other.Therefore, a plurality of data paths can be used simultaneously, and seamless exchange can be carried out.

According to some forms of implementation, if FE is eNodeB or access point, and MBE is the gateway in provider domain or the provider network, and then MN can connect by a plurality of access networks (being called many interfaces MN) simultaneously.If FE is the entity that is positioned at the boundary of provider domain (being called FE-BR), and MBE is the gateway close with MN, then the data service of MN can receive from the IP territory by a plurality of core net links, and can not ask any central entities (as: PDN Gateway) that leads.A plurality of MBE can be used for identical MN simultaneously, for example, if make a strategic decision at MC or by PCC based on the decision-making of strategy.Therefore, can also cut apart or merge the data service of MN, for example, if carried out the low operational decision making of granularity at gateway and/or FE.

In above-mentioned form of implementation, between mobile node and data path, do not have strict binding.Can based on different events (such as: network load, the mobility of MN etc.), the decision-making of dynamic system given data path optimization.The data service that is forwarded to carrier network can be controlled more more dynamically in following granularity rank: be used for one or more packets, be used for one or more data flow, be used for the fully communication of MN.Data path can distribute (only when request) on request.Data path can seamlessly be redistributed.For example, data path is redistributed the packet that can not affect in the transmission, that is, packet has been forwarded to another data path.In addition, data path is redistributed and can be carried out among the FE between two packets, and can not require buffer memory.Can also reselect as requested the function of data path.

According to some forms of implementation, only when redistributing, request data path.There is not the data path of redistributing that to carry out, unless FE asks this operation.The information of redistributing can only transfer to FE, and it has the packet that (or having had) will be transmitted to MN.

Above-mentioned form of implementation allows to use simultaneously a plurality of data paths.In addition, can be implemented under the particular case and reduce signaling.There is not message will send to datapath entities, unless the MN ongoing communication.These information can only transfer to FE, and it has (or having had) and will transmit from MN or from the data service of its transmission.

Above-mentioned form of implementation does not require (for example: the IP route) revises forwarded mechanism.Above-mentioned form of implementation can be used based on a plurality of forwarding mechanism, and can not revise the forwarding mechanism that bottom-layer network transmits.

Even at transfer phase, also can dispose from EPC to slab construction described form of implementation.For example, above-mentioned steps can use FE in S gateway/PDN Gateway eNodeB and MBE in dispose (to be used for the business that uploads data), and use FE and the MBE on the PDN Gateway in the IP territory of operator to dispose to be used for downloading data professional.

Claims

1. in communication network, be used to mobile entity (110) to set up the method for data path, it has one or more Delivery Function (151,152), so that packet (being used to data path) and a plurality of mobility binding entity (161,162) (being used for the packet on the forwarding data path) to be provided, the method comprises:

By a Delivery Function (151,152) of a Delivery Function (151,152), receive the data service of distributing to mobile entity (110);

By a Delivery Function (151,152), the binding information of mobile entity (110) is distributed in request;

In order to respond one of them Delivery Function (151,152) that receives, distribute a mobility binding entity (161,162) of a plurality of mobility binding entities (161,162);

The binding information that provides request to arrive, binding information comprises the sign of the mobility binding entity (161,162) that has distributed, and

By a Delivery Function (151,152), based on binding information, data service is transmitted to the mobility binding entity (161,162) that has distributed.

2. method according to claim 1, wherein, be used for upgrading binding information in order to respond update request, with another mobility binding entity partitioning in a plurality of mobility binding entities (161,162) to mobile entity (110), and the binding information that will upgrade offers a Delivery Function, and the binding information that has upgraded comprises that the sign of the other mobility binding entity that will distribute distributes to mobile entity (110).

3. method as claimed in claim 1 or 2, wherein, the sign of the other mobility binding entity that has distributed offers the mobility binding entity of previous distribution, and the data service (being assigned to mobile entity (110)) that the mobility binding entity that wherein, had before distributed will import into is forwarded to the other mobility binding entity that has distributed.

4. such as each method as described in the claim 1-3, wherein, data path is distributed to data service, the mobility binding entity (161,162) that data path comprises mobile entity (110), a Delivery Function (151,152) and distributed.

5. such as each described method as described in the claim 1-4, wherein, data service by data path, via a Delivery Function, is forwarded to the mobility binding entity (if data service originates from this mobile entity (110)) that has distributed from mobile entity (110).

6. such as each described method as described in the claim 1-5, wherein, data service via the mobility binding entity that has distributed, transfers to mobile entity (110) (if the target of data service is mobile entity (110)) from one of them Delivery Function on data path.

7. such as each described method as described in the claim 1-6, wherein, in order to respond the request of termination, the mobility binding entity (161,162) that has distributed will be deleted, and the binding information that has upgraded will offer mobility binding entity (161,162) (its distribution is deleted), and the binding information that has upgraded comprises deleted distribution.

8. such as each described method as described in the claim 1-7, wherein, the binding information that has upgraded comprises deleted distribution is offered one or more Delivery Function (151,152) (before providing binding information to this Delivery Function).

9. such as each described method as described in the claim 1-8, also comprise:

Receive, by other Delivery Function in one or more Delivery Function (151,152), the data service of entity (110) is moved in the receiving target displacement;

Request, by another one Delivery Function (151,152), the binding information of mobile entity (110) is distributed in request;

Provide the binding information of request to other forwarding mobile entity (151,152), binding information comprises the sign of the mobility binding entity (161,162) that has distributed; And

Transmit, by other Delivery Function (151,152), data service is transmitted to the mobility binding entity (161,162) that has distributed.

10. such as each described method as described in the claim 1-9

Wherein, binding information is being offered Delivery Function (151,152) afterwards, will between Delivery Function (151,152) and the mobility binding entity that has distributed (161,162), register mobile link.

11. this distribution is carried out by mobile controller (120) such as each described method as described in the claim 1-10 wherein.

12. such as each described method as described in the claim 1-11 wherein, mobile entity (110) uses mobile controller (120) to register, this registration comprises communication identifier is sent to mobile controller (120) that communication identifier comprises at least one following parameters of mobile single entity (110):

Media Access Control (media interviews control), MAC, address;

IMSI International Mobile Subscriber Identity, IMSI;

Internet Protocol, IP, address;

Device identifier;

User identifier;

User ID.

13. such as each described method as described in the claim 1-12 wherein, the mobility binding entity that has distributed (161,162) will be forwarded to from the data service that Delivery Function (151,152) receives the gateway entity of packet data network, and gateway entity is one of one of a plurality of mobility binding entities (161,162) or one or more Delivery Function (151,152).

14. have the communication network (being used to data path that packet is provided) of one or more Delivery Function (151,152), and a plurality of mobility binding entities (161,162) (being used for forwarding data bag on data path), this equipment is configured to:

Registration is attached to the mobile entity (110) on the communication network;

The mobility binding entity (161,162) that distributes a plurality of mobility binding entities, be assigned to the request of the binding information of mobile entity (110) with response, this request receives from a Delivery Function (151,152) of one or more Delivery Function (151,152).

The binding information of having asked is transferred to a Delivery Function, and this binding information comprises the binding information of the mobility binding entity that has distributed, and the data service that is assigned to mobile entity (110) will be transmitted by a Delivery Function.

15. be used for the communication system of communication network, this communication system comprises one or more Delivery Function (151,152) (being used to data path that packet is provided), a plurality of mobility binding entity (161,162) (being used for forwarding data bag on data path), and as the described equipment of above-mentioned claim.