CN103069917B - For setting up the method for data path, equipment and communication system - Google Patents

For setting up the method for data path, equipment and communication system Download PDF

Info

Publication number
CN103069917B
CN103069917B CN201180005033.XA CN201180005033A CN103069917B CN 103069917 B CN103069917 B CN 103069917B CN 201180005033 A CN201180005033 A CN 201180005033A CN 103069917 B CN103069917 B CN 103069917B
Authority
CN
China
Prior art keywords
entity
mbe
mobile
delivery function
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.)
Expired - Fee Related
Application number
CN201180005033.XA
Other languages
Chinese (zh)
Other versions
CN103069917A (en
Inventor
周青
康斯坦丁诺斯·潘蒂克斯
康纳·帕普
马里斯·克里斯
佳格斯·魏佳善
托马斯·马歌丹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
Original Assignee
Huawei Technologies Co Ltd
Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd, Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV filed Critical Huawei Technologies Co Ltd
Publication of CN103069917A publication Critical patent/CN103069917A/en
Application granted granted Critical
Publication of CN103069917B publication Critical patent/CN103069917B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Abstract

For in a communication network for mobile entity (110) sets up the method for data path, it has one or more Delivery Function (151,152) (for providing packet for data path) and multiple mobility binding entity (161,162) (packet on forwarding data path), and the data service being assigned to mobile entity (110) will receive from one of them Delivery Function of one or more Delivery Function (151,152) (151,152).Be assigned to the binding information of mobile entity (110), asked by the request of one of them Delivery Function (151,152).In order to respond the request receiving one of them Delivery Function (151,152), a mobility binding entity (161,162) of multiple mobility binding entity (161,162) will be distributed.The binding information of having asked provided, comprises the mark of the mobility binding entity (161,162) distributed.A Delivery Function (151,152), will rely on binding information, data service will be transmitted to the mobility binding entity (161,162) distributed.

Description

For setting up the method for data path, equipment and communication system
Technical field
The present invention is relevant to communication network field, especially, relevant to mobile communications network.
Background technology
In current communication network, can mobile terminal be passed through, connect packet data network (such as: internet).For this reason, mobile communication provider provides some entities (such as: gateway) to think the connection of mobile terminal foundation to packet data network usually.
Such as, if mobile terminal is connected to communication network via base station, then for mobile terminal fixed allocation and data path will be set up.Especially, transmit from or be sent to each entity of packet of mobile terminal thereon, all can arrange based on the connection of mobile terminal and base station.
Therefore, meeting distribute data path, is existed even without packet and is transmitted by data path usually.In addition, as long as mobile terminal safeguards the connection with base station, the entity on data path can not be exchanged.Therefore, if in the connection procedure of mobile terminal, network parameter is changed, then the data path set up will become the second selection.Correspondingly, if should distribute new data path for mobile terminal, then mobile terminal will be interrupted to the connection of base station, therefore, will lose the connection to packet data network temporarily.
Summary of the invention
The object of the invention is to provide effective concept to set up the data path of mobile communication.
The embodiment of the present invention is realized by the characteristic describing each claim.Embodiment in the future will follow these relied on rights statement.
The embodiment of the present invention is based upon the mobile entity being connected to communication network and searches data path, sets up when can exist in the data service being assigned to mobile entity.Correspondingly, the data path of mobile entity will be set up as requested.Therefore, as long as the data service relevant to mobile entity exists, then the resource of other data paths untapped in a communication network can be preserved.In addition, the data path of optimization can be selected when actual needs.In order to originate from the downloading data business that the business that uploads data of mobile entity and target are mobile entity, different data paths can also be selected.
Such as, communication network comprises one or more Delivery Function, for providing packet for data path, and multiple mobility binding entity, for forwarding data bag on data path.Then, if Delivery Function request data path, then only to set up data path, because Delivery Function has the data service that will be forwarded.
According to first aspect, the embodiment of the present invention to for for mobile entity, to set up the method for data path relevant in a communication network.Communication network comprises one or more Delivery Function, for providing packet for data path, and multiple mobility binding entity, for forwarding data bag on data path.A Delivery Function of one or more Delivery Function, receives the data service distributing to mobile entity.By the request of a Delivery Function, ask the binding information being assigned to mobile entity.In order to respond the request of the Delivery Function received, the mobility binding entity of multiple mobility binding entity will be distributed.Then, will provide the binding information asking to arrive, binding information comprises the mark of the mobility binding entity distributed.A Delivery Function is incited somebody to action, and based on binding information, data service is transmitted to the mobility binding entity distributed.
Such as, communication network comprises mobile controller, and such as, management is tied to the data service of the mobile entity of communication network.Correspondingly, distribute mobility binding entity to be performed by mobile controller.Such as, mobile entity is attached to communication network and uses mobile controller to register.Such as, registration packet is containing receiving the network address (as: IP address).When registering, will not distribute and set up data path.The mobile controller that the request of a Delivery Function will be sent to it and distributes, to respond the request of reception, mobility binding entity.After the distribution, the request binding information comprising the Identification Identifier of the mobility binding entity distributed will transfer to a Delivery Function from mobile controller.
According to some forms of implementation, this assigning process can perform in a Delivery Function.Such as, a Delivery Function has internal memory and cache, has some mobility binding entities selected for distributing.Correspondingly, binding information is provided by a Delivery Function self.
According to some forms of implementation, mobility binding entity be dispensing by mobile controller to perform.The binding information comprising the mark of distributing mobility binding entity is stored in the cache of a Delivery Function and/or the cache of other Delivery Function.Therefore, if Delivery Function has the data service being assigned to the mobile entity that will forward, then once mobility binding entity is distributed by mobile controller, it can search the mobility binding entity that will forward the data service of cache to it.
First form of implementation according to a first aspect of the invention, the present invention is correlated with in a method, and wherein, in order to respond the update request upgrading binding information, the other mobility binding entity of multiple mobility binding entity will distribute to mobile entity.The binding information upgraded will be supplied to a Delivery Function, and wherein, the binding information upgraded comprises the mark of the other mobility binding entity distributed being assigned to mobile entity.Such as, the request upgraded can receive from communication network, from receptions such as the mobility binding entities previously distributed.Can also be receive update request (such as: for safeguarding purposes) by way to manage.In addition, update request can in mobile controller internal trigger, such as, for load balance object.
Once a Delivery Function receives the binding information upgraded, then can set up new data path and on new data path forwarding data business.But the data service sent on previous data path then must resend.
According to some execution modes, the identity of the mobility binding entity distributed further will be provided to the mobility binding entity previously distributed.Correspondingly, the data service of importing into (being assigned to mobile entity) can be forwarded to the mobility binding entity of specifying further by the mobility binding entity previously distributed.Therefore, the mobility binding entity that the data service previously distributed will be redirected to the data path of newly specifying.
Second form of implementation according to a first aspect of the invention, the present invention is relevant to a method, and wherein, data path is specified in order to data service, and data path comprises mobile entity, one of them Delivery Function and a mobility binding entity distributed.
Such as, if data service originates from mobile entity, then data service is by a Delivery Function, from mobile entity to the mobility binding entity transmission of having distributed on data path.Can also be that if data service take mobile entity as target, then data service is by the mobility binding entity by having distributed, and data path transmits from a Delivery Function to mobile entity.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 downloading data business.Therefore, can distribute at least two independent data paths, that is, one is downloading data path (for downloading data business) and a path that uploads data (for the business of uploading data).
The 3rd enforcement according to a first aspect of the invention, the embodiment of the present invention is relevant to a method, wherein, in order to respond the request of termination, the distribution of the mobility binding request distributed will be deleted, and the binding information upgraded provides and will be supplied to mobility binding entity (its distribution is deleted), and the binding information upgraded comprises deleted distribution.Correspondingly, if do not need data path, such as, because the data service being assigned to mobile entity exists, then the resource used in the data path distributed can be released in.
Such as, the binding information upgraded comprising deleted distribution is supplied to Delivery Function (in the past to which providing binding information) further.Correspondingly, if after deletion distributes, Delivery Function receives the data service being assigned to mobile entity, then will be formulated the new request of binding information by Delivery Function.
According to some execution modes, if certain distribution is performed by mobile controller, then the deletion of this distribution is also performed by mobile controller.
The 4th enforcement according to a first aspect of the invention, the embodiment of the present invention is relevant to a method, and in the method, target is that the data service of mobile entity is received by the Delivery Function forwarding multiple Delivery Function further.Delivery Function request is in the future assigned to the binding information of mobile entity.Then, will provide the binding information asking to arrive, binding information comprises the mark of the mobility binding entity distributed.Data service can be forwarded to the mobile entity distributed by Delivery Function in the future.
Correspondingly, if mobility binding entity partitioning is to the downstream data paths of mobile entity, then the information about distributing, the mark of the mobility binding entity mainly distributed, can be supplied to other Delivery Function into mobile entity receiving downlink data business.Such as, have the binding information of the mobility binding entity distributed, be stored in the cache of mobile controller and/or in the cache of another Delivery Function, such as, it can be Delivery Function, and formulation is asked thus caused the distribution of mobility binding entity.
The 5th form of implementation according to a first aspect of the invention, the embodiment of the present invention is relevant to a method, and wherein, after binding information is supplied to Delivery Function, mobile link is registered between Delivery Function and the binding entity distributed.Such as, between conversion entity and mobility binding entity, establish one or more carrying, comprise the carrying of acquiescence.
According to forms of implementation more of the present invention, registration mobile link can comprise to be set up or defines one of at least following item: strategy and charging control, PCC, quality services, QoS, rule, Internet Protocol, IP, tunnel are set up.Such as, register mobile link to support by mobile controller.
In addition, mobile controller can perform 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 to a method, and wherein, mobile entity uses mobile controller to register, and this registration packet is containing 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 reception identification data business has been assigned to the information needed for mobile entity.
The 7th form of implementation according to a first aspect of the invention, the present invention is relevant to a method, wherein, the data service received from Delivery Function is forwarded to the gateway entity of packet data network by the mobility binding entity distributed, and gateway entity is one of one of multiple mobility binding entity or one or more Delivery Function.
According to a second aspect of the invention, the embodiment of the present invention is relevant to mobile communications network, and communication network comprises one or more Delivery Function, for providing packet for data path, and multiple mobility binding entity, for forwarding data bag on data path.This Equipments Setting is the mobile entity that registration is tied to communication network.This equipment is also configured to the mobility binding entity distributing multiple mobility binding entity, and to respond the request of the binding information being assigned to mobile entity, this request is the Delivery Function received from one or more Delivery Function.This equipment is also configured to the binding information of request to be forwarded to a Delivery Function, and this binding information comprises the binding information of the mobility binding entity distributed, and the data service being assigned to mobile entity will be forwarded by a Delivery Function.
Some forms of implementation according to a second aspect of the invention, this equipment is regarded as mobile controller (description as carried out for first aspect of the present invention).
According to the further form of implementation in second direction of the present invention, this equipment can be configured to process update request and upgrade binding information for described in first aspect of the present invention.This equipment can also be configured to process as described in first aspect of the present invention and stop request.
Some forms of implementation according to a second aspect of the invention, this Equipments Setting is for performing first method of the present invention.
According to a third aspect of the present invention, the present invention is relevant to the communication system of communication network, and communication system comprises one or more Delivery Function (for providing packet for data path), multiple mobility binding entity (for forwarding data bag on data path) and the equipment according to second method of the present invention.
Accompanying drawing explanation
Below with reference to the accompanying drawings further embodiment of the present invention is described, wherein:
Fig. 1 shows the communication network according to form of implementation;
Fig. 2 shows the communication network according to form of implementation;
Fig. 3 shows the flow chart of the method according to form of implementation;
Fig. 4 shows the flow chart of the method according to form of implementation;
Fig. 5 shows the flow chart of the method according to form of implementation;
Fig. 6 shows the flow chart of the method according to form of implementation; And
Fig. 7 shows the flow chart of the method according to form of implementation.
Embodiment
Fig. 1 shows the communication network according to form of implementation.In a communication network, mobile entity is regarded as mobile node, and MN, 110 is connected to mobile controller, and MC, 120 has the signal path be represented by dotted lines.MC120 is to provide a part for business'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 showing in the graphic in order to whole structure).
MN110 is connected to provider network 130 by mobile link (representing with solid line).Provider network 130 also has the data cube computation (representing with solid line) to data network 140.FE151,152 does not have usage data to be connected with MBE161,162 to carry out connecting (representing with solid line) each other, and each is connected to MC120(by signaling and is represented by dotted lines).One or more entity 151,152,161,162 can have the connection to data network 140, thus serves the data network gateway of provider network 130.
Next, will illustrate how MN110 is connected to provider network 130 and data network 140 respectively, and data service how to transmit from and to MN110.
Therefore, after MN110 is attached to network 130, use MC120 registers by MN110.Data path is added by this and is linked to MN110.When one of them FE, 151,152 has the data service that will forward being assigned to MN110, MC120 can select MBE161, one of 162.MC120 sets up data path by for the MN110 between a FE and selected MBE.When MBE changes, such as, have changed the information in provider network 130, will MC120 be notified.Then, MC120 will notify FE, and that specifies data service to MN110.
According to the annex of network, MN110 asks and receives network environment (such as: the IP address that can arrive or any other network addresss clearly specifying additional MN110.MC120 creates and storing mobile binding, such as, comprise the mapping between 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 to be used for data path, such as, and permanent entity (MN110 adopts the mode similar with base station to be connected on it).As a result, be arranged in unique entity that control plane MC120 is system (mainly provider network 130), it can be bound to MN110 alert notification.But, be not MN110 assignment constraint data path.
About the forwarding of data service, if FE151,152 one of them there is the data service that will forward, this data service is assigned to MN110, then corresponding FE can from the MC120 request binding information corresponding with the identifier of MN110.Such as, FE can inquire that MC120 whither sends data service.In order to respond the request of FE, the MBE161 on data path, one of 162 can be distributed to MN110 by MC120.Such as, MC120 can distribute a MBE, and it can receive the data service being sent to MN110 or therefrom sending.MC120 can select the binding information between the identifier and the MBE distributed of MN110.Correspondingly, only when forwarding the data service distributing to MN110, just can select for MN110 or distribute MBE.
About setting up auto-correlation FE to the data path distributing MBE, the mark of distributing MBE can be sent to the FE that have sent request by MC120.Such as, MC120 can inform FE sends data service to which MBE.The mark of the MBE distributed can send in binding information.The message comprising binding information can forward auto-correlation FE from MC120, can directly send, and also can be sent by the MBE distributed.MC120 can notify that the MBE distributed sets up the context to relevant FE.Such as, between relevant FE and the MBE distributed, establish one or more carrying, comprise the carrying of acquiescence.MC120 can start control based on Quality of Service, the QoS of user, rule and strategy and charging, PCC.Downloading data path can be set up with the path that uploads data in independent operating procedure.But upload data path and downloading data path can comprise the different entities of provider network 130.As a result, entity on selection data path is as the forwarding of packet.
Data service is forwarded to the MBE distributed by relevant FE.Such as, packet is transferred into the MBE distributed.
About the change of MBE, the update request that MC120 can receive MN110 path is asked with change, wherein, receives in the MBE that this request can distribute from network 130 or etc.This request can also be received by way to manage, such as, in order to safeguard purposes.This request can in the internal trigger of MC120, such as, for load balancing object.
In order to respond update request, the new MBE on data path is distributed to MN110 by MC120.Such as, MC120 distributes new MBE, for receiving from MN110 or the data service to its transmission.Note that this operates distributes similar, except redistributing MBE to first of above-mentioned MBE.This MC120 can select the cache of the binding information upgraded between the identifier comprising MN110 and the MBE distributed.
About the notice after change MBE, the identifier of newly assigned MBE can be sent to one or more FE by MC120.Such as, the binding information upgraded can be sent to all FE by MC120.But such binding information upgraded can only be sent to those FE of the binding information with request by MC120.The message comprising the binding information upgraded can be sent to FE from MC120, can directly send, and also can be sent by MBE that is newly assigned or that distributed.MC120 can notify that newly assigned MBE sets up the context to FE.Such as, FE and, establish one or more carrying between newly assigned MBE, comprise the carrying of acquiescence.According to some forms of implementation, FE has the binding information of cache for MN110, can upgrade these binding informations in such cache.
As a result, packet is forwarded to the newly assigned MBE data path from FE.
Fig. 2 shows 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 implement as the eNodeB of the packet-based core networks of evolution (EPC).Provider network 230 and packet data network, PDN, 240 can be connected to by these base stations 211,212, MN110.Provider network 230 comprises MC120 and multiple multiple entities 251,252,261,262 with gateway function.Such as, entity 251,262 is gateway, S gateway, and entity 252,261 is PDN Gateway.S gateway and corresponding PDN Gateway can form SAE gateway.Each in S gateway 251,262 is connected to base station 211,212 simultaneously.PDN Gateway 252,261 has the connection to packet data network 240.
With reference to figure 1, MBE can by eNodeB or another accessing points or represent for another base station of downloading data business, by S gateway or the specific gateway of another accesses network or download and upload data service represents, by for download and upload data service PDN Gateway or another universal gateway represents or the Delivery Function (provider network 230 as the business of uploading data) of boundary by provider domain represents.
Equally, FE can by for the eNodeB of the business of uploading data or other accessing points or base station represents, by for upload with the S gateway of downloading data business or another Access Network particular gateway represents, by for upload or downloading data business PDN Gateway or another universal gateway represents, by for representing to the passback entity of gateway forwards packet for download and upload data service, or to be represented by the Delivery Function being positioned at the edge of provider domain for downloading data business.
Below, with reference to Fig. 2, the multiple programs according to each embodiment form are described.But should be appreciated that, the entity shown in Fig. 2 should not be regarded as restriction, and is only to better illustrate.Correspondingly, supposing that there is restriction binding between MN110 and base station, when relating to the IP territory represented by PDN240, supposing to use loose data path.Base station represents the entity of strict binding MN110 for communication.Such as, base station can be represented by the eNodeB of EPC.Universal gateway (GG) represents the gateway be positioned at for safeguarding for MN110 on the data path of mobility binding.Such as, can be represented by PDN Gateway or PDN and S gateway for EPC, GG.The carrying that GG can be required for based on user distributes and PCC.Data service can be forwarded to and/or the function of MN110 and/or the data service from IP territory by the Delivery Function FE-BR being positioned at boundary.MC represents independent function, such as, and MME.MN110 can be tied to multiple base station simultaneously.But in example below, MN110 is regarded as only being tied to a base station.Correspondingly, downloading data business must arrive this certain base station to be forwarded to MN110.
Fig. 3 shows the flow chart of the operation according to forms of implementation more of the present invention.There has been described communication and the operation of MN301, it can be implemented as eNodeB as subscriber equipment, UE, base station 303(), first and second GG305,307(can implement as PDN Gateway), mobile controller 309(can increase powerful MME and implement as having) and be positioned at Fe, the FE-BR, 311,313 on provider domain border.
In this Fig. 3, describe the annex of MN301 to network.In step 320, MN301 establishes the connectivity of itself and base station 303.In step 322, base station sends the identifier of MN301 to MC309, and the identifier of base station 303 is as assignment information.In this step 322, base station 303 can require from MC309 the IP address will distributing to MN301.In step 324, MC309 receives information from base station 303, and adds cache entry to its cache.Such as, the MN301 for forwarding to base station 303 is stored all downloading data business by MC309.In addition, it is noted that and can not distribute any MBE, and data service can receive from any FE-BR.It also stores the business that uploads data received from base station 303, and can not distribute any MBE for uploading.Data service can be forwarded to any FE-BR.In step 326, MC309 sends to base station and confirms.If MC309 distributing IP address, then confirm to comprise IP address.As a result, its reachability information is stored in MC309 by MN301.Any MBE can not be selected in this stage.
Fig. 4 describes the operation relevant with the relevant business that uploads data according to some forms of implementation.In the graphic, show entity 401,403,405,407,409,411,413, may correspond to the related entities 301 to 313 in Fig. 3.Suppose to perform according to the mounting program of Fig. 3.MN401 is connected to network, and MC409 has reachability information.
At step 420 which, to base station 403, MN401 notifies that it is intended to.Such as, notice is sent to base station 403 by arriving the connection status bag that maybe will upload data.
In step 422, base station 403, when supposing previously do not had data services, checks whether and sets up PCC and mobile context.In step 424, base station 403 is from MC409 request forward information or binding information.In step 426, MC409 will check whether the binding information comprising MBE is distributed in the past, if not, the MBE of GG1505 as MN401 will be distributed.
In step 428, forwarding information is sent to GG405, and can select to be sent to base station 403.Forwarding information requests the connection with base station by enabling GG405 know from MN401.In addition, forwarding information can enable GG1 to know that data service can be forwarded to any FE-BR by it.
In step 430, between base station 403 and GG405, PCC and mobile context is established.This process of establishing can be started by GG405.Mobile link or mobile context can comprise PCC and QoS rule and IP forwarding tunnel is 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.This operation as a result, upload and download connection establishing on the path of mobile node 401 to GG405 via base station 403 temporarily.
In optional step 432, GG405 can forwarding decision, namely can forward FE-BR411,413 data services to it.Otherwise being forwarded to FE-BR can be performed by existing IP routine mechanism static state.It should be noted that the data path must followed and distribute that only uploads data.
Fig. 5 shows the flow chart of the operation according to some forms of implementation, and this operation is relevant to the downloading data business of MN.Fig. 5 shows 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 perform 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.By inspection, whether it has the cache data relevant to MN501 to FE-BR513.Suppose not have forwarding information buffer memory FE-BR513, FE-BR513 will in step 524, from the binding information that MC509 request is relevant to MN501.Similar with step 426, in step 526, MC509 will check binding information and search all downloading services that must forward to base station 503, but does not distribute any MBE.Then, MC509 can distribute GG505 as MBE, for the downloading data path of MN501.
In step 528, forwarding information or binding information are sent to FE-BR513 by MC509.In addition, if previously do not distribute MBE, then forwarding information or binding information can also be supplied to the MBE distributed, that is, GG505.FE-BR513 will create cache entry, and it comprises the information received from MC509.
In optional step 532, forwarding information or binding information can also be supplied to base station 503.This information make base station 503 can know request for MN501 with the connection of GG505.Such as, this operation is very useful to enter connection status for triggering MN501.In step 534, between base station 503 and GG505, establish PCC and mobile context or mobile link.This process of establishing can be started by GG505, or, if base station 503 has forwarding information, also can be started by base station 503.
As a result, for a time period, or for specific downloading data business, data service will be forwarded to GG505 from FE-BR513.
Fig. 6 shows the flow chart of the operation according to forms of implementation more of the present invention.This operation is relevant to reselecting of MBE.Fig. 6 shows entity 601,603,605,607,609,611,613, and they can be relevant to the previous entity shown in Fig. 3 to 5.
Suppose to perform according to the additional process of Fig. 3, and MC509 safeguards reachability information.Also suppose that MN601 is connected to network by base station 603 and GG605.Upload binding information gateway 605 is defined as the MBE distributed is used for the business of uploading data.In addition, for downloading data business, it further defines arrive FE-BR611, one of 613 data service must be forwarded to GG605 as Delivery Function.
In step 620, formulation MBE is redistributed strategy so that MC609 must perform MBE re-allocation process.Such as, this operation can be triggered via another base station by the additional of MN601, that is, Access Network transfer.Re-allocation process can also be passed through way to manage (such as: attended operation) and trigger (as shown in Figure 6).Redistributing in decision-making, this MC609 determines that selection second GG607 is used for MN601 as new MBE.When uploading available with down operation, MC609 will change them, so that the business of uploading data must be forwarded to GG607 from base station 603, and must be forwarded to GG607 from FE-BR611, one of the 613 downloading data business received.
In optional step 622, forwarding information or binding information are provided to newly assigned MBE, i.e. GG607.This information can also be sent to base station 603.This information can make base station 603 know request for MN601 with the connection of GG607.This information can also be sent to the MBE previously distributed, i.e. GG605.This information makes GG605 can delete PCC and mobile context and will be addressed to the data retransmission of MN601 to GG607.
In step 624, between base station 603 and GG607, establish PCC and mobile context.This process of establishing can be started by GG607.Mobile link or mobile context can comprise PCC and QoS rule and IP forwarding tunnel is set up.In this case, in step 622, information can also be sent to base station 603, PCC and mobile context to set up and can also be started by base station 603.This operation as a result, establish on the path from mobile node 601 to base station, 603 to GG603 and upload and download connection temporarily.
In step 626, which checking in FE-BR611,613 needs to upgrade by MC609.MC609 will upgrade to they forwarding informations.In step 628, FE-BR611,613 can use its cache of information updating, and the downloading data bag relevant to MN601 will be forwarded to newly assigned GG607.
Fig. 7 shows the flow chart of the operation according to forms of implementation more of the present invention.This operation stops relevant to binding.Entity 701,703,705,707,709,711,713 can correspond to the entity previously described in Fig. 3 to 6.
Similar with more previously described forms of implementation, suppose that GG705 distributes and be used for uploading and downloading connection as MBE, MN701 is connected in network.
In step 720, the decision-making removed MBE and distribute will be formulated.Correspondingly, MC709 must perform MBE and remove process.Such as, this operation can trigger in the following manner: MN701 is in idle pulley, or does not communicate within the predefined time period.Other triggers can be from any network building-out MN701.709 determine the MBE binding of deleting MN701, not have MBE to be assigned to MN and for the business of uploading data and downloading data business.
In step 722, which checking in FE-BR711,713 is required termination message by MC709.MC sends to FE-BR711,713 binding information upgraded, and comprises the information of the distribution about deleting MBE.In step 724, FE-BR711,713 will delete relevant information in its cache.
In step 726, termination message is also sent in the GG705 previously distributed by MC709.In addition, these information also will be sent to base station 703.In step 728, the PCC between base station 703 and the GG705 distributed and mobile context will be terminated, and this process is started by GG705.If in step 726, the binding information upgraded also is transferred into base station 703, then move contextual termination and also can be started by base station 703.
As the result of this operation, by the connection stopping uploading and downloading in the path previously distributed temporarily.
Obviously, above-mentioned steps can combine, and the step that can perform in a program wherein can use the step of other programs to exchange, such as, according to distribute and with distribute relevant transmission information.
According to some forms of implementation, can distribute separately and upload and download path.But, in order to simplify allocation step, can distribute simultaneously uploading and download path.For uploading and downloading data path, FE may be independent of each other.Therefore, multiple data path can be used simultaneously, and can seamless exchange 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 provider network, then MN can pass through multiple access network (being called multiplex roles MN) simultaneously connects.If FE is for being positioned at the entity of the boundary of provider domain (being called FE-BR), and MBE is the gateway close with MN, then the data service of MN can be received from IP territory by multiple core net link, and can not ask any central entities (as: PDN Gateway) that leads.Multiple MBE can simultaneously for identical MN, such as, if carry out decision-making at MC or by PCC based on the decision-making of strategy.Therefore, can also split or merge the data service of MN, such as, if perform the low operational decision making of granularity at gateway and/or FE.
In above-mentioned form of implementation, binding not strict between mobile node and data path.Can based on different events (such as: the mobility etc. of network loading, MN), the decision-making of dynamic system given data path optimization.The data service being forwarded to carrier network can control more more dynamically in following granularity level: for one or more packet, for one or more data flow, for the communication completely of MN.Data path can carry out distributing (only upon request) on request.Data path can seamlessly be redistributed.Such as, data path redistributes the packet that can not affect in transmission, that is, packet has been forwarded to another data path.In addition, data path is redistributed and can be performed in the FE between two packets, and can not require buffer memory.The function of data path can also be reselected as requested.
According to some forms of implementation, only when redistributing, just request data path.There is no the data path redistributed that can perform, unless FE asks this to operate.The information redistributed can only transfer to FE, and it has (or having) will be transmitted to the packet of MN.
Above-mentioned form of implementation allows can use multiple data path simultaneously.In addition, signaling is reduced under can be implemented in particular case.Do not have message to send to datapath entities, communicate unless the mn.These information can only transfer to FE, and it has (or having) will forward from MN or the data service from its transmission.
Above-mentioned form of implementation does not require amendment forwarded mechanism (such as: IP route).Above-mentioned form of implementation can be applied based on multiple forwarding mechanism, and can not revise the forwarding mechanism of bottom-layer network transmission.
Even if at transfer phase, the form of implementation described in also can disposing from EPC to slab construction.Such as, above-mentioned steps can use in eNodeB and MBE of FE in S gateway/PDN Gateway and dispose (for the business of uploading data), and uses the FE in the IP territory of operator and the MBE on PDN Gateway to carry out disposing for downloading data business.

Claims (14)

1., in a communication network for setting up the method for data path for mobile entity MN, described communication network comprises one or more Delivery Function FE, multiple mobility binding entity MBE, mobile controller MC, and it is characterized in that, the method comprises:
A Delivery Function FE in described one or more Delivery Function FE receives the data service distributing to described mobile entity MN;
A described Delivery Function FE asks mobile controller MC to distribute to the binding information of described mobile entity MN;
A described Delivery Function FE receives the binding information that described mobile controller MC feeds back, comprise the mark of the mobility binding entity MBE of distribution in the binding information of feedback, the mobility binding entity MBE of described distribution is one in described multiple mobility binding entity MBE;
A described Delivery Function FE sets up context based on the mobility binding entity MBE of binding information and described distribution, data service is transmitted to the mobility binding entity MBE of described distribution.
2. method according to claim 1, is characterized in that, described method comprises:
A described Delivery Function FE receives the binding information upgraded, the binding information of described renewal responds update request by described mobile controller MC and generates and send to a described Delivery Function FE, and the content of the binding information record of described renewal is: other a mobility binding entity MBE in multiple mobility binding entity MBE is distributed to mobile entity MN to replace the mobility binding entity MBE previously distributing to mobile entity MN.
3. method as claimed in claim 2, it is characterized in that, by mobile controller MC, other the mark of a mobility binding entity MBE described is supplied to the mobility binding entity MBE previously distributed, so that the data service of importing into is forwarded to other a mobility binding entity MBE described by the mobility binding entity MBE previously distributed, so that other a mobility binding entity MBE described continues the data service transmitting mobile entity MN with described Delivery Function FE.
4. the method for claim 1, is characterized in that, comprises: the mobility binding entity MBE of mobile entity MN, a described distribution and described Delivery Function FE according to the data path for transmitting data service that the context set up is determined.
5. method as claimed in claim 4, it is characterized in that, if data service originates from mobile entity MN, on the data path of transmitting data service, through the mobility binding entity MBE of described distribution, data service is transferred to a described Delivery Function FE from mobile entity MN.
6. method as claimed in claim 4, it is characterized in that, if if the target of data service is mobile entity MN, on the data path of transmitting data service, through the mobility binding entity MBE of described distribution, data service is transferred to described mobile entity MN from a described Delivery Function FE.
7. the method for claim 1, it is characterized in that, responded by mobile controller MC and stop asking and generating the binding information comprising unbind, the described binding information comprising unbind is sent to the mobility binding entity MBE of described distribution, so that the mobility binding entity MBE of described distribution stops the binding with mobile entity MN.
8. method as claimed in claim 7, it is characterized in that, described method comprises:
A described Delivery Function FE receives by mobile controller MC to the binding information comprising unbind described in described Delivery Function FE transmission, according to the described binding information of binding information deletion for binding mobility binding entity MBE and mobile entity MN comprising unbind.
9. the method for claim 1, is characterized in that, also comprises:
Receive, by Delivery Function FE other in described one or more Delivery Function FE, the data service of receiving target position mobile entity MN;
Request, by other Delivery Function FE, request mobile controller MC distributes to the binding information of mobile entity MN, and binding information comprises the mark of the mobility binding entity MBE of described distribution;
Forward, by other Delivery Function FE, data service is transmitted to the mobility binding entity MBE of described distribution.
10. the method for claim 1, is characterized in that, described method comprises:
A described Delivery Function FE, after obtaining binding information from mobile controller MC, registers mobile link with the mobility binding entity MBE of described distribution.
11. methods as described in claim 1-11 as described in any one, it is characterized in that, registered to mobile controller MC by mobile entity MN, this registration comprises communication identifier is sent to mobile controller MC, and described communication identifier comprises at least one following parameters of mobile entity MN:
Media interviews control (Media Access Control is called for short MAC) address,
IMSI International Mobile Subscriber Identity IMSI,
Internet protocol IP address,
Device identifier,
User identifier,
User ID.
12. the method for claim 1, it is characterized in that, by the mobility binding entity MBE of described distribution, the data service received from described Delivery Function FE is forwarded to the gateway entity of packet data network, described gateway entity is one of one of described multiple mobility binding entity MBE or described one or more Delivery Function FE, so that gateway entity forwards described data service to described mobile entity MN.
13. 1 kinds of mobile controller MC, is characterized in that, mobile controller MC is configured to:
Register the mobile entity MN be attached on communication network;
Distribute a mobility binding entity MBE in multiple mobility binding entity MBE, to respond the request of the binding information being assigned to mobile entity MN, this request receives from a Delivery Function FE described one or more Delivery Function FE;
This binding information is transferred to the Delivery Function FE sending this request, this binding information comprises the mark of the mobility binding entity MBE distributed, and is forwarded by the mobility binding entity MBE that the data service of mobile entity MN is specified by the Delivery Function FE and this binding information sending this request.
14. for the communication system of communication network, and it is characterized in that, this communication system comprises one or more Delivery Function FE, multiple mobility binding entity MBE, and mobile controller MC according to claim 13.
CN201180005033.XA 2011-02-25 2011-02-25 For setting up the method for data path, equipment and communication system Expired - Fee Related CN103069917B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/071315 WO2012113156A1 (en) 2011-02-25 2011-02-25 Method for establishing a data path, device and communication system

Publications (2)

Publication Number Publication Date
CN103069917A CN103069917A (en) 2013-04-24
CN103069917B true CN103069917B (en) 2015-08-19

Family

ID=46720101

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201180005033.XA Expired - Fee Related CN103069917B (en) 2011-02-25 2011-02-25 For setting up the method for data path, equipment and communication system

Country Status (3)

Country Link
EP (1) EP2507955A4 (en)
CN (1) CN103069917B (en)
WO (1) WO2012113156A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107026776A (en) * 2017-04-20 2017-08-08 深圳拓邦股份有限公司 A kind of communication path collocation method, apparatus and system
CN117527680A (en) * 2022-07-29 2024-02-06 华为技术有限公司 Resource reservation path establishment and communication method and device

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656765A (en) * 2009-09-14 2010-02-24 中兴通讯股份有限公司 Address mapping system and data transmission method of identifier/locator separation network

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4491468B2 (en) * 2007-02-08 2010-06-30 Ｎｅｃアクセステクニカ株式会社 Router route control method and router
EP2071807A1 (en) * 2007-12-11 2009-06-17 Nokia Siemens Networks Oy Advanced Mobile IP system employing distributed home agents
CN101662811B (en) * 2009-08-17 2011-08-17 北京航空航天大学 Distributed routing protocol based on reliable path

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656765A (en) * 2009-09-14 2010-02-24 中兴通讯股份有限公司 Address mapping system and data transmission method of identifier/locator separation network

Also Published As

Publication number Publication date
CN103069917A (en) 2013-04-24
EP2507955A1 (en) 2012-10-10
EP2507955A4 (en) 2013-01-02
WO2012113156A1 (en) 2012-08-30

Similar Documents

Publication Publication Date Title
CN111466110B (en) Edge computing relocation
US10355982B2 (en) Network device and terminal for multi-path communication, operation method thereof, and program implementing operation method
CN109792663B (en) Method and apparatus for serving mobile communication devices using tunneling protocol
KR101595527B1 (en) System for configurating dynamic service network based on netstore and method thereof
US8711858B2 (en) Packet communication system and packet communication method, and node and user device
CN110896553B (en) Multi-access edge computing method and platform and communication system
KR102580499B1 (en) Communication methods and communication devices
CN110602761B (en) Data transmission method and device
WO2019048021A1 (en) Network entity, user equipment and method for the control and use of network slices
CN101868790B (en) Support for continuity of tunnel communications for mobile nodes having multiple care of addressing
US20130188598A1 (en) Local storage of content in a wireless network
US6958988B1 (en) Mobile communication network and data delivery method in mobile communications network
CN112187495B (en) Communication method and communication system for terminal and server
JP2009525632A (en) Selective service update method for communication network
US7940701B2 (en) Network selection
JP2019511880A (en) Data transmission method, apparatus and session management device
CN102369764A (en) System and method operable to enable shortest connection route
CN102571963B (en) Content delivery method, device and access network equipment
US20140112307A1 (en) User terminal and communication apparatus for preventing interuption of communication in information centric network and method thereof
CN103069917B (en) For setting up the method for data path, equipment and communication system
JP6138136B2 (en) A method, system, computer program, and software image originated by an online provider are dynamically present on the edge network of the cellular network to provide online services from the service provider to the user through the wireless cellular network How to enable
CN102316086A (en) Relay method for service data and relay node system
US9531836B2 (en) Distributing an application via a network node
CN112543511A (en) Method, device, apparatus and medium for providing and discovering moving edge calculation
CN102369744A (en) System and method operable to enable shortest connection route

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20150819

Termination date: 20200225

CF01 Termination of patent right due to non-payment of annual fee