CN104780586A

CN104780586A - Data path processing method, system and device

Info

Publication number: CN104780586A
Application number: CN201410015163.7A
Authority: CN
Inventors: 黄莹; 高音; 谢峰; 梁爽
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2014-01-13
Filing date: 2014-01-13
Publication date: 2015-07-15
Also published as: WO2015103865A1

Abstract

The invention discloses a data path processing method, system and device. The method comprises the following steps: a subordinate network element acquiring service gateway indication information from a superior network element; and the subordinate network element determining a S1 user plane data path of UE according to the acquired service gateway indication information.

Description

Data path processing method, system and equipment

Technical field

The present invention relates to wireless communication technology, be specifically related to a kind of data path processing method, system and equipment.Background technology

Home eNodeB (HeNB, Home eNB) is a kind of compact low power base station, is mainly used in the indoor place among a small circle such as family and office.Home eNodeB passes through the access in radio equipment connections such as indoor cable, Digital Subscriber Line or optical fiber to mobile operator core net, for specific user provides the access service based on mobile radio networks.Be effectively supplementing existing network deployment, effectively can improve indoor voice and high-speed data service covering.There is lot of advantages, as simple in low cost, low-power, access, plug and play, saving passback, compatible with existing terminal, improve the network coverage etc.

Third generation partnership project (3GPP, Third Generation Partnership Projects) normal structure definition (LTE, Long Term Evolution) system comprises Home eNodeB (HeNB, home eNB), the function that HeNB supports and eNB basically identical, process between HeNB and evolution block core net (EPC, EvolvedPacket Core), and between eNB and EPC, process is basically identical.Because the arrangement of HeNB is not usually through the little and One's name is legion of the network planning of mobile operator, coverage, in order to management more easily and the HeNB supporting greater number, at the universal mobile telecommunications system (E-UTRAN of evolution, Evolved UTRAN) wireless access planar network architecture under, the network element that introducing one is new between HeNB and EPC and femto gateway (HeNB GW, Home eNB Gateway), HeNB connects mobile management entity (MME, Mobility Management Entity) by HeNB GW as S1 agency.HeNB GW bears the role of MME for HeNB, MME is born to the role of base station.The function of HeNB GW comprises: the optional S1-U interface stopped between HeNB and gateway (SGW, Serving GateWay), and namely S1-U data are optionally through HeNB GW; Relaying UE is correlated with S1 message, comprise interface application protocol (S1AP) mark (ID) in amendment message, transport network layer (TNL) address, general packet radio service (General Packet Radio Service) tunnel protocol (GTP, GPRS Tunnel Protocol) endpoint of a tunnel (TEID, Tunnel Endpoint IDentifier); Stop the relevant S1 process of non-user terminal (UE); HeNB is replaced to be that UE performs NNSF function.In addition, because Home eNodeB is in most cases disposed voluntarily for user instead of by operator deployment, in order to ensure that UE passes through the fail safe of HeNB access carrier network, introduces security gateway (SeGW, Security GW) in Home NodeB system framework.SeGW replaces the core network of operator and HeNB mutually to verify.HeNB and HeNB GW, or the connection between HeNB and core network all to need by SeGW between secure tunnel.Fig. 1 is Home NodeB system framework schematic diagram in correlation technique, and as shown in Figure 1, Home NodeB system framework comprises: the network elements such as UE, HeNB, SeGW and HeNB GW; Wherein HeNB GW is optional deployment, and when not disposing HeNB GW, SeGW is positioned at the edge of core network; When disposing HeNB GW, SeGW and HeNB GW is independently logical functional entity, and SeGW is between HeNB GW and non-secure link, and in practical application, SeGW also can be integrated in HeNB GW.

Along with ever-increasing user is to the demand of high-speed data service, and in order to the user face load that reduces core net further and, 3GPP introduces selected Internet protocol traffic unloading (SIPTO, Selected IP Traffic Offload) technology, comprise selected Internet protocol traffic unloading (SIPTOabove RAN) based on resident's Access Network and selected Internet protocol traffic unloading (SIPTOLN) two class.

Fig. 2 is SIPTO above RAN configuration diagram, SIPTO above RAN is from version 10(R10) support, referring to that MME is is the nearer SGW being positioned at core net of UE chosen distance UE and packet data gateway (PGW according to the geographical position of UE, Package data GateWay), PGW is also referred to as local packet data gateway (L-PGW, Local Package data GateWa _c).SIPTO@LN is from version 12(R12) support version, refer to MME be UE select to be positioned at Access Network side closes with HeNB the gateway established or set up separately, corresponding conjunction is established local gateway (LGW, Local GateWay) framework and sets up gateway architecture separately respectively.

Fig. 3 is that SIPTO@LN closes the configuration diagram of establishing gateway (GW, GateWac), and as shown in Figure 3, the PGW of UE and local gateway (LGW, Local GateWay) close to be located in HeNB, and SGW is arranged in core net.

Fig. 4 is the configuration diagram that SIPTO@LN sets up gateway separately, and as shown in Figure 4, SGW and PGW of UE and LGW is arranged in the access network of wireless side, and sets up separately with HeNB.When setting up common core net evolved packet system (EPS, Evolved Package System) after the UE that carries sets up SIPTO service bearer, MME may select to correspond to SIPTO above RAN business from the SGW(being positioned at core net close to UE for the SIPTO service bearer of this UE), or the SGW(set up separately with HeNB selecting to be positioned at access network corresponds to SIPTO@LN and sets up gateway service separately), and be the SGW of the SIPTO business service of this UE be not same SGW usually with carrying for the common EPS of this UE the SGW served, and multiple EPS carryings of UE only allow to be served by same SGW, therefore the SGW SGW of the common EPS carrying of UE being relocated to the SIPTO service bearer of UE may be needed after the SIPTO service bearer of UE is set up.In order to support this function, introduce the mobile-initiated SGW repositioning process of non-UE, in this process, evolution RAB (E-RAB, Evolved-Radio Access Bearer) modification process is reused in the new SGW information of notice HeNB by MME.

As shown in Figure 5, the SGW that core network packet data network (PDN, Packet Data Network) connects is positioned at core net, and the SGW that SIPTO@LN connects is positioned at access network; Connect if UE has established Normal Kernel network PDN, and the S1-U interface that this PDN connects ends at HeNB GW, now UE set up again SIPTO@LN PDN connect and the SGW of this connection and PGW and HeNB set up separately, multiple PDN due to a UE connect and can only be served by same SGW, the then MME SGW that the core network PDN of this UE need be connected, resets the SGW being positioned at access network also i.e. local network; As shown in Figure 6, if now HeNB GW still stops the S1-U interface that core network PDN connects, the user face data path that then the core network PDN of UE connects is: UE-HeNB-SeGW-HeNB GW(is positioned at core net)-SGW(is positioned at Access Network)-PGW(is positioned at core net), can find out that user face data path is comparatively tediously long.And in correlation technique, HeNB GW can not determine whether user face data path will be caused the S1 interface in the user plane stopping UE tediously long, cause user plane latency in the mobile-initiated SGW repositioning process of non-UE.

In addition, according to HeNB security protocol specification, for ensureing the fail safe by the UE of HeNB access network, the connection between all HeNB and HeNB GW or between HeNB and core network all needs through SeGW.If the SGW of UE is positioned at core network, then HeNB needs first data to be sent to SeGW by secure tunnel; If the SGW of UE is positioned at access network (as UE establishes SIPTO@LN service bearer), then the S1-U data that HeNB sends directly can be sent to the SGW of access network, namely do not need to be sent to SeGW by secure tunnel, to realize shorter S1-U data path.And in correlation technique, HeNB can not determine whether S1-U data need to be sent to SeGW in the mobile-initiated SGW repositioning process of non-UE.

In addition, under little base station (small cell) deployment scenario supports SIPTO@LN, according to dual link mode, namely UE is simultaneously by two base stations and macrocell evolution base station (MeNB, Macrocell evolvedNode B) and secondary evolution base station (SeNB, Secondary evolved Node B) receive data, then also there is above Similar Problems, SeNB can not determine when sending the upstream data of UE that whether sending data to MeNB is still directly sent to and sets up gateway separately in access network, causes SIPTO@LN function not perform smoothly.

Summary of the invention

The embodiment of the present invention provides a kind of data path processing method, system and equipment, and solution user face data path is tediously long, causes the problem of user plane latency.

The technical scheme of the embodiment of the present invention is achieved in that

The embodiment of the present invention provides a kind of data path processing method, comprising:

Lower level network element obtains gateway indication information from upper level network element;

Described lower level network element, according to obtained gateway indication information, determines the S1 user face data path of UE.

The embodiment of the present invention also provides a kind of data path treatment system, comprising: upper level network element and lower level network element; Wherein,

Described lower level network element, for obtaining gateway indication information from described upper level network element;

According to obtained gateway indication information, determine the S1 user face data path of UE.

The embodiment of the present invention also provides a kind of Home eNodeB, comprising:

First acquiring unit, for obtaining gateway indication information from upper level network element;

The embodiment of the present invention also provides a kind of femto gateway, comprising:

Second acquisition unit, for obtaining gateway indication information from upper level network element;

Second determining unit, for according to obtained gateway indication information, determines the S1 user face data path of UE.

In the embodiment of the present invention, the S1 user face data path in correlation technique can be shortened according to gateway indication information, avoid the problem occurring user plane latency.

Accompanying drawing explanation

Fig. 1 is Home NodeB system framework schematic diagram;

Fig. 2 is the configuration diagram of SIPTO above RAN;

Fig. 3 supports that SIPTO@LN closes the configuration diagram of establishing GW;

Fig. 4 is the configuration diagram that SIPTO@LN sets up gateway separately;

Fig. 5 is that SIPTO@LN connects and non-SIPTO@LN connection diagram;

Non-SIPTO@LN connection diagram when Fig. 6 is HeNB GW termination S1-U after SIPTO@LN triggering SGW reorientation;

Fig. 7 is non-SIPTO@LN connection diagram when HeNB GW does not stop S1-U after SIPTO@LN triggers SGW reorientation;

Fig. 8 is the schematic flow sheet according to the embodiment of the present invention one;

Fig. 9 is the schematic flow sheet according to the embodiment of the present invention two;

Figure 10 is the schematic flow sheet according to the embodiment of the present invention three;

Figure 11 a is the scene schematic diagram according to the embodiment of the present invention four;

Figure 11 b is the schematic flow sheet according to the embodiment of the present invention four;

Figure 12 is the schematic flow sheet of embodiment of the present invention data processing method;

Figure 13 is the structural representation of embodiment of the present invention data handling system;

Figure 14 is the structural representation of embodiment of the present invention Home eNodeB;

Figure 15 is the structural representation of embodiment of the present invention femto gateway.

Embodiment

Be described in further detail the present invention below in conjunction with drawings and the specific embodiments, it should be noted that, when not conflicting, the feature in the embodiment of the present invention and embodiment can combine mutually.

The SGW connected due to core network PDN is positioned at core net, and the SGW that SIPTO@LN connects is positioned at access network, but multiple PDN of UE connect and can only be served by same SGW, in the HeNB GW deployment architecture shown in Fig. 6, connect if UE has established Normal Kernel network PDN, and the S1-U interface that this PDN connects ends at HeNB GW, if now UE set up again SIPTO LN PDN connect and SIPTO LN PDN connect SGW and PGW and HeNB set up separately, then the SGW that the core network PDN of this UE connects need be reset the SGW being positioned at access network (local network) by MME.If now HeNBGW still stops the S1-U interface that core network PDN connects, then the user face data path that the core network PDN of UE connects is: UE-HeNB-SeGW-HeNB GW(is positioned at core net)-SGW(is positioned at Access Network)-PGW(is positioned at core net).In order to shorten S1-U path, need S1-U data that the core network PDN making UE connects without HeNB GW, namely directly send S1-U data to being positioned at the SGW of access network or sending S1-U data to HeNB by the SGW being positioned at access network by HeNB, thus make HeNB GW without the need to stopping this S1-U interface.

As shown in Figure 7, the user face data path that the core network PDN of UE connects is: UE-HeNB-SGW(is positioned at Access Network-PGW(and is positioned at core net).Due to the mobile-initiated SGW repositioning process of non-UE be used for UE move outside scene in SGW reorientation, comprise and set up GW separately by SIPTO@LN() or SIPTO above RAN PDN connection establishment trigger.If set up GW separately by SIPTO@LN() connection establishment triggering SGW reorientation, then new SGW is positioned at access network; If trigger SGW reorientation by SIPTO above RAN PDN connection establishment, then new SGW is positioned at core network.In correlation technique, HeNB GW can not determine whether the S1-U user face data stopping this UE in the mobile-initiated SGW repositioning process of non-UE, will cause user face data path redundancy and the delay of adding users face.In embodiments of the present invention, HeNB GW and HeNB can obtain new SGW indication information and/or the data path indication information of reorientation, HeNB GW can determine whether to stop S1-U interface according to this information, namely whether revises the SGW tunnel information in reorientation S1 signaling.Such as, when new SGW is positioned at access network, then HeNB GW does not stop the S1-U interface of UE; When new SGW is positioned at core network, HeNB GW optionally stops the S1-U interface of UE.In addition, according to this information, HeNB also can judge whether up S1-U data need first to be sent to SeGW through secure tunnel.If the SGW of UE is positioned at core network, then HeNB needs first S1-U data to be sent to SeGW by secure tunnel; If the SGW of UE is positioned at access network (as UE establishes SIPTO@LN service bearer), then the S1-U data that HeNB sends can not need to be sent to SeGW by secure tunnel, are namely directly sent to the SGW of access network.

Embodiment one

What the present embodiment described is the method that under not having HeNB GW to dispose, HeNB determines S1-U data path according to gateway indication information, and Fig. 8 is the schematic flow sheet of the present embodiment, as shown in Figure 8, comprises the following steps:

Step 801, MME determines to perform the mobile-initiated SGW repositioning process of non-UE.

This SGW repositioning process can be triggered by SIPTO above RAN or SIPTO@LN connection establishment event, establishes SGW reorientation to be triggered by SIPTO@LN connection establishment event in the present embodiment.

Step 802, the SGW that the non-SIPTO of this UE connects is reset the SGW being positioned at SIPTO LN and connecting by MME, and sends E-RAB modify request messages to HeNB.

Owing to not having HeNB GW to dispose, this S1 message is directly sent to HeNB.Comprise gateway indication information in this message, this indication information can carry for the mode of per UE or per E-RAB, comprises following information one of at least:

1) whether the new SGW of reorientation is positioned at local network or whether SGW repositioning process is triggered by SIPTO@LN connection establishment;

2) whether the new SGW of reorientation is positioned at core network or whether SGW repositioning process is triggered by SIPTO above RAN connection establishment;

3) whether S1 user face data is through femto gateway;

4) whether S1 user face data is through security gateway;

5) whether described S1 user face data is through MeNB.

In the present embodiment, SGW reorientation is triggered by SIPTO@LN connection establishment event, therefore this gateway refers to that the new SGW of indication information instruction reorientation is positioned at local network or SGW repositioning process is triggered by SIPTO@LN connection establishment, or S1 user face (S1-U) data are without security gateway.

According to the gateway indication information in this message, step 803, after HeNB receives E-RAB modify request messages, determines whether the S1-U data of UE need to be sent to security gateway by secure tunnel.

After step 803, according to determined S1 user face data path transmission data.

In the present embodiment, HeNB judges that the S1-U data of UE do not need to be sent to security gateway by secure tunnel, namely directly sends S1-U data to the SGW being positioned at access network.

Embodiment two

What the present embodiment described is the method that under having HeNB GW to dispose, HeNB and HeNB GW determines S1-U data path according to gateway indication information, and Fig. 9 is the present embodiment method flow schematic diagram, as shown in Figure 9, comprises the following steps:

Step 901, MME determines to perform the mobile-initiated SGW repositioning process of non-UE.

Step 902, the SGW that the non-SIPTO of this UE connects is reset the SGW being positioned at SIPTO LN and connecting by MME, and sends E-RAB modify request messages to HeNB GW.

When disposing HeNB GW, described E-RAB modify request messages is first sent to HeNB GW, comprises gateway indication information in this message, and this indication information can carry for the mode of per UE or per E-RAB, comprises following information one of at least:

2) whether the new SGW of reorientation is positioned at core network or whether SGW repositioning process is triggered by SIPTOabove RAN connection establishment;

3) whether S1 user face data is through femto gateway;

4) whether S1 user face data is through security gateway;

5) whether described S1 user face data is through MeNB.

In the present embodiment, SGW reorientation is triggered by SIPTO@LN connection establishment event, and therefore this gateway indication information one of indicates following information at least: the new SGW of reorientation is positioned at local network or SGW repositioning process is triggered by SIPTO@LN connection establishment; S1 user face data is without femto gateway; S1 user face data is without security gateway;

According to the gateway indication information in this message, step 903, determines that whether the S1-U data of UE are through HeNB GW after HeNB GW receives E-RAB modify request messages.

In the present embodiment, HeNB judges that the S1-U data of UE do not need through HeNB GW, namely S1-U data are directly sent to the SGW being positioned at access network, then HeNB GW does not revise the tunnel information of the new SGW in this message, comprises transport network layer (TNL) address and interface application protocol (S1AP) mark (ID).

Step 904, the E-RAB modify request messages carrying gateway indication information is sent to HeNB by HeNB GW.

According to the gateway indication information in this message, step 905, after HeNB receives E-RAB modify request messages, determines whether the S1-U data of UE need to be sent to security gateway by secure tunnel.

After step 905, according to determined S1 user face data path transmission data.

Embodiment three

What the present embodiment described is the method that under having HeNB GW to dispose, HeNB and HeNB GW determines S1-U data path according to gateway indication information and/or data path indication information, Figure 10 is the present embodiment method flow schematic diagram, as shown in Figure 10, comprise the following steps:

Step 1001, MME determines to perform the mobile-initiated SGW repositioning process of non-UE.

This SGW repositioning process can be triggered by SIPTO above RAN or SIPTO@LN connection establishment event.SGW reorientation is established to be triggered by SIPTO@LN connection establishment event in the present embodiment.

Step 1002, the SGW that the non-SIPTO of this UE connects is reset the SGW being positioned at SIPTO LN and connecting by MME, and sends E-RAB modify request messages.

When disposing HeNB GW, this S1 message is directly first sent to HeNB GW, comprises gateway indication information in this message, and this indication information can carry for the mode of per UE or per E-RAB, comprises following information one of at least:

3) whether S1 user face data is through femto gateway;

4) whether S1 user face data is through security gateway;

5) whether described S1 user face data is through MeNB.

In this embodiment, SGW reorientation is triggered by SIPTO@LN connection establishment event, and therefore this gateway refers to that indication information one of indicates following information at least: the new SGW of reorientation is positioned at local network or SGW repositioning process is triggered by SIPTO@LN connection establishment; S1 user face data is without femto gateway; S1 user face data is without security gateway.

According to the gateway indication information in this message, step 1003, determines that whether the S1-U data of UE are through HeNB GW after HeNB GW receives E-RAB modify request messages.

In the present embodiment, HeNB judges that the S1-U data of UE do not need through HeNB GW, and namely directly send S1-U data to the SGW being positioned at access network, then HeNB GW does not revise the tunnel information (TNL address and GTP TEID) of the new SGW in this message.

Step 1004, perform in step 1004a, 1004b and 1004c one of at least:

The E-RAB modify request messages carrying gateway indication information is sent to HeNB by 1004a, HeNB GW; 1004b, HeNB GW sends data path indication information to HeNB by E-RAB modify request messages; 1004c, HeNB GW carries gateway indication information and data path indication information in E-RAB modify request messages simultaneously.

Described data path indication information be used to indicate S1 user face data whether through femto gateway or S1 user face data whether through security gateway, this data path indication information can carry for the mode of per UE or perE-RAB.

In the present embodiment, this gateway indication information and described data path indication information are used to indicate following information one of at least: the new SGW of reorientation is positioned at local network or SGW repositioning process is triggered by SIPTO@LN connection establishment; S1 user face data is without femto gateway; S1 user face data is without security gateway.

Step 1005, after HeNB receives E-RAB modify request messages, according to the gateway indication information in this message and/or data path indication information, determines whether the S1-U data of UE need to be sent to security gateway by secure tunnel.

After step 1005, according to determined S1 user face data path transmission data.

In the present embodiment, HeNB judges that the S1-U data of UE do not need be sent to security gateway by secure tunnel but be directly sent to the SGW being positioned at access network.

Embodiment four

What the present embodiment described is that under having small cell to support SIPTO@LN scene, SeNB determines the method for S1-U data path according to gateway indication information, and Figure 11 a is the present embodiment method scene schematic diagram.As shown in figure 11, UE, by dual link mode access network, can receive data from MeNB and SeNB simultaneously.What wherein SeNB was connected to SIPTO@LN sets up GW separately; Figure 11 b is the present embodiment method flow schematic diagram, as shown in figure lib, comprises the following steps:

Step 1101, MME determines to be required to be the reorientation that UE sets up carrying or execution SGW.

Step 1102, MME transmission initial context sets up message or E-RAB sets up/revise message to MeNB.

Can comprise gateway indication information in this message, whether this gateway indication information can be used for indicating the S1 user face data of UE through MeNB; This gateway indication information can be per UE's or perE-RAB granularity.

Step 1103, MeNB sends initial context to SeNB after UE determines the SeNB served to set up message or E-RAB sets up/revise message.

Can comprise gateway indication information in this message, whether this gateway indication information can be used for indicating the S1 user face data of UE through MeNB; This gateway indication information can be obtain from MME reception, or MeNB self determines according to the ability of SeNB and MeNB self information on load.

Step 1104, SeNB judges after receiving gateway indication information that whether the S1 user face data of UE is through MeNB.

If through MeNB, then the S1 user face data of UE is first sent to MeNB by SeNB; If without MeNB, then what the S1 user face data of UE was directly sent to the SIPTO@LN being positioned at access network by SeNB sets up gateway separately;

In addition, under there is the scene of change in SeNB, if what new SeNB was connected to SIPTO@LN sets up gateway separately, then MeNB performs in SeNB change flow process, can according to the ability of SeNB, the information such as MeNB self load condition determine that whether the S1 user face data of SeNB is through MeNB or the gateway that sets up separately being directly sent to SIPTO@LN, then set up/revise message by carrying and be indicated to SeNB.

The embodiment of the present invention also records a kind of data path processing method, as shown in figure 12, comprises the following steps:

Step 121, lower level network element obtains gateway indication information from upper level network element.

Step 122, described lower level network element, according to obtained gateway indication information, determines the S1 user face data path of UE.

Wherein, described lower level network element obtains gateway indication information from upper level network element, comprising:

Described lower level network element obtains described gateway indication information from described upper level network element in the gateway repositioning process of described UE; Or,

Described lower level network element obtains described gateway indication information from described upper level network element in the process of establishing of the carrying of described UE.

Wherein, described lower level network element comprises the network element of following form: Home eNodeB, femto gateway, SeNB;

Correspondingly, when described lower level network element is Home eNodeB, described upper level network element is femto gateway or mobile management entity;

When described lower level network element be Home eNodeB and femto gateway time, described upper level network element is mobile management entity;

When described lower level network element is SeNB, described upper level network element is macrocell evolution base station MeNB.

Wherein, described gateway indication information comprises information one of at least:

Whether gateway is positioned at local network;

Whether gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

Whether described gateway repositioning process is triggered by SIPTO@LN connection establishment;

Whether described gateway repositioning process is triggered by SIPTO above RAN connection establishment;

Whether described S1 user face data is through MeNB.

Wherein, described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process when being triggered by SIPTO@LN connection establishment, and described gateway indication information also indicates described gateway and described Home eNodeB to close and establishes or set up separately.

Wherein, described gateway repositioning process is triggered by non-UE moving event, and described non-UE moving event is the UE event outside the handover event of UE and the tracking area update event of UE.

Wherein, the trigger condition of described gateway repositioning process comprises following condition one of at least:

SIPTO above RAN connection establishment;

SIPTO@LN connection establishment.

Wherein, when described lower level network element is Home eNodeB and femto gateway, described upper level network element is mobile management entity, described lower level network element obtains gateway indication information from upper level network element in the gateway repositioning process of UE, comprising:

Described femto gateway receives the E-RAB modify request messages that described mobile management entity sends, and received E-RAB modify request messages is sent to described Home eNodeB, and described E-RAB modify request messages carries described gateway indication information.

Wherein, when described lower level network element is Home eNodeB, described upper level network element is mobile management entity, described lower level network element obtains gateway indication information from upper level network element in the gateway repositioning process of UE, comprising:

Described Home eNodeB receives the E-RAB modify request messages that described mobile management entity sends, and described E-RAB modify request messages carries described gateway indication information.

Described femto gateway receives the E-RAB modify request messages that described mobile management entity sends, and according to received E-RAB modify request messages, determines that following information is one of at least:

Whether described gateway is positioned at local network;

Whether described gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

The Internet protocol traffic unloading SIPTO@LN connection establishment whether described gateway repositioning process is selected by local network triggers;

Whether described gateway repositioning process unloads SIPTO above RAN connection establishment by the selected Internet protocol traffic based on resident's Access Network is triggered;

Whether described S1 user face data is through macrocell evolution base station MeNB;

Determined information is carried in Service Gateway info, and described Service Gateway info is carried in E-RAB modify request messages sends to described Home eNodeB.

Wherein, described method also comprises:

Determined information is carried in data path indication information by described femto gateway, and described to be carried in E-RAB modify request messages according to path indication information is sent to described Home eNodeB; Or,

Determined information is carried in Service Gateway info and data path indication information by described femto gateway, and described Service Gateway info and data path indication information is carried in E-RAB modify request messages and sends to described Home eNodeB.

Wherein, described lower level network element determines the S1 user face data path of described UE according to described gateway indication information, comprising:

According to described gateway indication information, described femto gateway determines that whether the S1 user face data of described UE is through described femto gateway.

Wherein, according to described gateway indication information, described femto gateway determines that whether the S1 user face data of described UE is through femto gateway, comprising:

Meet the following conditions at least for the moment: described gateway indication information indicates described gateway to be positioned at local network; Described gateway repositioning process is triggered by SIPTO@LN connection establishment; Described gateway is not positioned at core network;

Described femto gateway determines that the S1 user face data of described UE is without described femto gateway.

Wherein, when described femto gateway determines the S1 user face data of described UE without described femto gateway, described method also comprises:

Described femto gateway does not revise the tunnel information of the SGW in described message when receiving described E-RAB modify request messages.

Wherein, described lower level network element, according to described gateway indication information, is determined the S1 user face data path of described UE, being comprised:

According to described gateway indication information, described Home eNodeB determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel.

Wherein, according to described gateway indication information, described Home eNodeB determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel, comprising:

The gateway indication information received when described Home eNodeB meets the following conditions for the moment: described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO LN connection establishment; Described gateway is not positioned at core network; Described S1 user face data is without security gateway;

Described Home eNodeB determines that the S1 user face data of described UE is not sent to security gateway by secure tunnel, is directly sent to described gateway; Otherwise, determine that the S1 user face data of described UE need be sent to security gateway by secure tunnel.

Wherein, described lower level network element, according to obtained gateway indication information, is determined to comprise the S1 user face data path that described UE is corresponding:

The gateway indication information that described Home eNodeB carries according to received E-RAB modify request messages and/or data path indication information, determine whether the S1 user face data of described UE is sent to security gateway by secure tunnel.

Wherein, described Home eNodeB, according to described gateway indication information and described data path indication information, determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel, comprising:

When described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO@LN connection establishment, and described data path indication information indicates described S1 user face data through femto gateway, described Home eNodeB determines that described S1 user face data need be sent to security gateway by secure tunnel;

When described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO@LN connection establishment, and described data path indication information is when indicating described S1 user face data without femto gateway, described Home eNodeB determines that described S1 user face data does not need to be sent to security gateway by secure tunnel, is directly sent to described gateway.

Wherein, described Home eNodeB, according to data path indication information, determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel, comprising:

When described data path indication information indicates described S1 user face data through security gateway, described Home eNodeB determines that described S1 user face data need be sent to security gateway by secure tunnel; Otherwise, determine that described S1 user face data does not need to be sent to security gateway by secure tunnel, be directly sent to described gateway.

The embodiment of the present invention also records a kind of computer-readable storage medium, stores computer executable instructions in described computer-readable storage medium, and described computer executable instructions is for performing the above data path processing method.

For implementing above-mentioned data path processing method, the embodiment of the present invention also records a kind of data path treatment system, as shown in figure 13, comprising:

Upper level network element 131 and lower level network element 132; Wherein,

Described lower level network element 132, for obtaining gateway indication information from described upper level network element 131;

Wherein, described lower level network element 132, also for obtaining described gateway indication information from described upper level network element 131 in the gateway repositioning process of described UE; Or,

Described lower level network element 132 obtains described gateway indication information from described upper level network element 131 in the process of establishing of the carrying of described UE.

Wherein, described lower level network element 132 comprises the network element of following form: Home eNodeB, femto gateway, SeNB;

Correspondingly, when described lower level network element 132 is Home eNodeB, described upper level network element 131 is femto gateway or mobile management entity;

When described lower level network element 132 be Home eNodeB and femto gateway time, described upper level network element 131 is mobile management entity;

When described lower level network element 132 is SeNB, described upper level network element 131 is macrocell evolution base station MeNB.

Whether described gateway is positioned at local network;

Whether described gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

Whether described S1 user face data is through MeNB.

SIPTO above RAN connection establishment;

SIPTO@LN connection establishment.

Wherein, described lower level network element 132 be Home eNodeB and femto gateway, described upper level network element 131 for mobile management entity time,

Described femto gateway, also for receiving the evolution RAB E-RAB modify request messages that described mobile management entity sends, and received E-RAB modify request messages is sent to described Home eNodeB, described E-RAB modify request messages carries described gateway indication information.

Wherein, described lower level network element 132 be Home eNodeB, described upper level network element 131 for mobile management entity or femto gateway time,

Described Home eNodeB, also for receiving the E-RAB modify request messages of described mobile management entity or femto gateway transmission, described E-RAB modify request messages carries described gateway indication information.

Described femto gateway, also for receiving the E-RAB modify request messages that described mobile management entity sends, according to received E-RAB modify request messages, determine that following information is one of at least:

Whether described gateway is positioned at local network;

Whether described gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

Wherein, described femto gateway, also for determined information being carried in data path indication information, and sends to described Home eNodeB by described to be carried in E-RAB modify request messages according to path indication information; Or,

Determined information is carried in Service Gateway info and data path indication information, and described Service Gateway info and described data path indication information are carried in E-RAB modify request messages send to described Home eNodeB.

Wherein, described femto gateway, also for determining that according to described gateway indication information whether the S1 user face data of described UE is through described femto gateway.

Wherein, described femto gateway, also for meeting the following conditions at least for the moment: described gateway indication information indicates described gateway to be positioned at local network; Described gateway repositioning process is triggered by SIPTO@LN connection establishment; Described gateway is not positioned at core network;

Determine that the S1 user face data of described UE is without described femto gateway.

Wherein, described femto gateway, also for when determining the S1 user face data of described UE without described femto gateway, does not revise the tunnel information of the SGW in sent described E-RAB modify request messages.

Wherein, described Home eNodeB, also for determining whether the S1 user face data of described UE is sent to security gateway by secure tunnel according to described gateway indication information.

Wherein, described Home eNodeB, also for meeting the following conditions at received gateway indication information for the moment: described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO LN connection establishment; Described gateway is not positioned at core network; Described S1 user face data is without security gateway;

Determine that the S1 user face data of described UE is not sent to security gateway by secure tunnel, be directly sent to described gateway; Otherwise, determine that the S1 user face data of described UE need be sent to security gateway by secure tunnel.

Wherein, described lower level network element 132, according to obtained gateway indication information, is determined to comprise the S1 user face data path that described UE is corresponding:

Described Home eNodeB, according to received E-RAB modify request messages, determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel.

Wherein, described Home eNodeB, also for indicating described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO@LN connection establishment when described gateway indication information, and described data path indication information indicates described S1 user face data through femto gateway, determine that described S1 user face data need be sent to security gateway by secure tunnel;

When described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO@LN connection establishment, and described data path indication information is when indicating described S1 user face data without femto gateway, determine that described S1 user face data does not need to be sent to security gateway by secure tunnel, be directly sent to described gateway.

Wherein, described Home eNodeB, also for according to data path indication information, determine whether the S1 user face data of described UE is sent to security gateway by secure tunnel, comprising:

For implementing above-mentioned data path treatment system, the embodiment of the present invention also records a kind of Home eNodeB, as shown in figure 14, comprising:

First acquiring unit 141, for obtaining gateway indication information from upper level network element;

First determining unit 142, for according to obtained gateway indication information, determines the S1 user face data path of UE.

Wherein, described first acquiring unit 141, also for obtaining described gateway indication information from described upper level network element in the gateway repositioning process of described UE; Or,

Described gateway indication information is obtained from described upper level network element in the process of establishing of the carrying of described UE.

Wherein, described first acquiring unit 141, also for receiving the E-RAB modify request messages that described upper level network element sends, described E-RAB modify request messages carries described gateway indication information.

Wherein,

Described first determining unit 142, also for determining whether the S1 user face data of described UE is sent to security gateway by secure tunnel according to described gateway indication information.

Wherein,

Described first determining unit 142, also for meeting the following conditions for the moment: described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO LN connection establishment or gateway is not positioned at core network or described S1 user face data without security gateway;

Wherein, described first acquiring unit 141, also for receiving E-RAB modify request messages, described E-RAB modify request messages carries gateway indication information and/or data path indication information;

Described first determining unit 142, also for according to described gateway indication information and/or described data path indication information, determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel.

Wherein, described first determining unit 142, also for indicating described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO@LN connection establishment when described gateway indication information, and described data path indication information indicates described S1 user face data through femto gateway, described Home eNodeB determines that described S1 user face data need be sent to security gateway by secure tunnel;

Wherein, described first determining unit 142, also for indicating described S1 user face data through security gateway when described data path indication information, described Home eNodeB determines that described S1 user face data need be sent to security gateway by secure tunnel; Otherwise, determine that described S1 user face data does not need to be sent to security gateway by secure tunnel, be directly sent to described gateway.

In practical application, described first acquiring unit 141 and described first determining unit 142 can by the central processing unit (CPU in described Home eNodeB, Central Processing Unit), digital signal processor (DSP, Digital Signal Processor) or field programmable gate array (FPGA, Field Programmable GateArray) realization.

For implementing above-mentioned data path treatment system, the embodiment of the present invention also records a kind of femto gateway, as shown in figure 15, comprising:

Second acquisition unit 151, for obtaining gateway indication information from upper level network element;

Second determining unit 152, for according to obtained gateway indication information, determines the S1 user face data path of UE.

Wherein, described second acquisition unit 151, also for obtaining described gateway indication information from described upper level network element in the gateway repositioning process of described UE; Or,

Wherein, described second acquisition unit 151, also for receiving the E-RAB modify request messages that described upper level network element sends, and received E-RAB modify request messages is sent to described Home eNodeB, described E-RAB modify request messages carries described gateway indication information.

Wherein, described second acquisition unit 151, also for receiving the E-RAB modify request messages that described mobile management entity sends;

Described second determining unit 152, also for according to received E-RAB modify request messages, determine that following information is one of at least:

Whether described gateway is positioned at local network;

Whether described gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

Described second acquisition unit 151, also for the described information determined being carried in Service Gateway info, and is carried at described Service Gateway info in E-RAB modify request messages and sends to Home eNodeB.

Wherein, described second acquisition unit 151, also for the described information determined being carried in data path indication information, and sends to Home eNodeB by described to be carried in E-RAB modify request messages according to path indication information; Or,

The described information determined is carried in Service Gateway info and data path indication information, and described Service Gateway info and data path indication information are carried in E-RAB modify request messages send to Home eNodeB.

Wherein, according to described gateway indication information, described second determining unit 152, also determines that whether the S1 user face data of described UE is through described femto gateway for described femto gateway.

Wherein, described second determining unit 152, the gateway also for obtaining at described second acquisition unit 151 meets the following conditions at least for the moment: described gateway indication information indicating service gateway is positioned at local network; Described gateway repositioning process is triggered by SIPTO@LN connection establishment; Gateway is not positioned at core network;

Wherein, described second acquisition unit 151, also for determining that in described second determining unit 152 described femto gateway determines that the S1 user face data of described UE is through described femto gateway, does not revise the tunnel information of the SGW in received E-RAB modify request messages.

In practical application, described second acquisition unit 151 and described second determining unit 152 can be realized by CPU, DSP or the FPGA in described femto gateway.

The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, all any amendments done within the spirit and principles in the present invention, equivalent replacement and improvement etc., all should be included within protection scope of the present invention.

Those skilled in the art should understand, embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt the form of hardware embodiment, software implementation or the embodiment in conjunction with software and hardware aspect.And the present invention can adopt in one or more form wherein including the upper computer program implemented of computer-usable storage medium (including but not limited to magnetic disc store and optical memory etc.) of computer usable program code.

The present invention describes with reference to according to the flow chart of the method for the embodiment of the present invention, equipment (system) and computer program and/or block diagram.Should understand can by the combination of the flow process in each flow process in computer program instructions realization flow figure and/or block diagram and/or square frame and flow chart and/or block diagram and/or square frame.These computer program instructions can being provided to the processor of all-purpose computer, special-purpose computer, Embedded Processor or other programmable data processing device to produce a machine, making the instruction performed by the processor of computer or other programmable data processing device produce device for realizing the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.

These computer program instructions also can be stored in can in the computer-readable memory that works in a specific way of vectoring computer or other programmable data processing device, the instruction making to be stored in this computer-readable memory produces the manufacture comprising command device, and this command device realizes the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.

These computer program instructions also can be loaded in computer or other programmable data processing device, make on computer or other programmable devices, to perform sequence of operations step to produce computer implemented process, thus the instruction performed on computer or other programmable devices is provided for the step realizing the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.

The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.

Claims

1. a data path processing method, comprising:

Described lower level network element, according to obtained gateway indication information, determines the S1 user face data path of user terminal UE.

2. method according to claim 1, is characterized in that, described lower level network element obtains gateway indication information from upper level network element, comprising:

3. method according to claim 2, is characterized in that, described lower level network element comprises the network element of following form: Home eNodeB, femto gateway, secondary evolution base station SeNB;

4. method according to claim 3, is characterized in that, described gateway indication information comprises information one of at least:

Whether gateway is positioned at local network;

Whether gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

Whether described gateway repositioning process unloads SIPTO@LN connection establishment by the selected Internet protocol traffic of local network is triggered;

Whether described S1 user face data is through macrocell evolution base station MeNB.

5. method according to claim 2, it is characterized in that, described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process when being triggered by SIPTO@LN connection establishment, and described gateway indication information also indicates described gateway and described Home eNodeB to close and establishes or set up separately.

6. method according to claim 2, is characterized in that, described gateway repositioning process is triggered by non-UE moving event, and described non-UE moving event is the UE event outside the handover event of UE and the tracking area update event of UE.

7. method according to claim 2, is characterized in that, the trigger condition of described gateway repositioning process comprises following condition one of at least:

SIPTO above RAN connection establishment;

SIPTO@LN connection establishment.

8. method according to claim 3, it is characterized in that, when described lower level network element is Home eNodeB and femto gateway, described upper level network element is mobile management entity, described lower level network element obtains gateway indication information from upper level network element in the gateway repositioning process of UE, comprising:

Described femto gateway receives the evolution RAB E-RAB modify request messages that described mobile management entity sends, and received E-RAB modify request messages is sent to described Home eNodeB, described E-RAB modify request messages carries described gateway indication information.

9. method according to claim 3, it is characterized in that, described lower level network element is Home eNodeB, described upper level network element is mobile management entity or femto gateway time, described lower level network element obtains gateway indication information from upper level network element in the gateway repositioning process of UE, comprising:

Described Home eNodeB receives the E-RAB modify request messages of described mobile management entity or femto gateway transmission, and described E-RAB modify request messages carries described gateway indication information.

10. method according to claim 8, it is characterized in that, when described lower level network element is Home eNodeB and femto gateway, described upper level network element is mobile management entity, described lower level network element obtains gateway indication information from upper level network element in the gateway repositioning process of UE, comprising:

Whether described gateway is positioned at local network;

Whether described gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

11. methods according to claim 10, is characterized in that, described method also comprises:

Determined information is carried in Service Gateway info and data path indication information by described femto gateway, and described Service Gateway info and described data path indication information is carried in E-RAB modify request messages and sends to described Home eNodeB.

12. methods according to claim 8, is characterized in that, described lower level network element determines the S1 user face data path of described UE according to described gateway indication information, comprising:

13. methods according to claim 12, is characterized in that, according to described gateway indication information, described femto gateway determines that whether the S1 user face data of described UE is through femto gateway, comprising:

14. methods according to claim 13, is characterized in that, when described femto gateway determines the S1 user face data of described UE without described femto gateway, described method also comprises:

15. methods according to claim 10, is characterized in that, described lower level network element, according to described gateway indication information, is determined the S1 user face data path of described UE, being comprised:

16. methods according to claim 15, is characterized in that, according to described gateway indication information, described Home eNodeB determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel, comprising:

17. methods according to claim 11, is characterized in that, described lower level network element, according to obtained gateway indication information, is determined to comprise the S1 user face data path that described UE is corresponding:

18. methods according to claim 17, is characterized in that, described Home eNodeB, according to described gateway indication information and described data path indication information, determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel, comprising:

19. methods according to claim 17, is characterized in that, described Home eNodeB, according to data path indication information, determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel, comprising:

20. 1 kinds of data path treatment systems, comprising: upper level network element and lower level network element; Wherein,

According to obtained gateway indication information, determine the S1 user face data path of user terminal UE.

21. systems according to claim 20, is characterized in that,

Described lower level network element, also for obtaining described gateway indication information from described upper level network element in the gateway repositioning process of described UE; Or,

22. systems according to claim 21, is characterized in that, described lower level network element comprises the network element of following form: Home eNodeB, femto gateway, secondary evolution base station SeNB;

23. systems according to claim 22, is characterized in that, described gateway indication information comprises information one of at least:

Whether described gateway is positioned at local network;

Whether described gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

24. systems according to claim 21, it is characterized in that, described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process when being triggered by SIPTO@LN connection establishment, and described gateway indication information also indicates described gateway and described Home eNodeB to close and establishes or set up separately.

25. systems according to claim 21, is characterized in that, described gateway repositioning process is triggered by non-UE moving event, and described non-UE moving event is the UE event outside the handover event of UE and the tracking area update event of UE.

26. systems according to claim 21, is characterized in that, the trigger condition of described gateway repositioning process comprises following condition one of at least:

SIPTO above RAN connection establishment;

SIPTO@LN connection establishment.

27. systems according to claim 22, is characterized in that, when described lower level network element is Home eNodeB and femto gateway, described upper level network element is mobile management entity,

28. systems according to claim 22, is characterized in that, described lower level network element is Home eNodeB, described upper level network element is mobile management entity or femto gateway time,

29. systems according to claim 27, is characterized in that, when described lower level network element is Home eNodeB and femto gateway, described upper level network element is mobile management entity,

Whether described gateway is positioned at local network;

Whether described gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

30. systems according to claim 29, is characterized in that,

Described femto gateway, also for determined information being carried in data path indication information, and sends to described Home eNodeB by described to be carried in E-RAB modify request messages according to path indication information; Or,

31. systems according to claim 27, is characterized in that,

Described femto gateway, also for determining that according to described gateway indication information whether the S1 user face data of described UE is through described femto gateway.

32. systems according to claim 31, is characterized in that,

Described femto gateway, also for meeting the following conditions at least for the moment: described gateway indication information indicates described gateway to be positioned at local network; Described gateway repositioning process is triggered by SIPTO@LN connection establishment; Described gateway is not positioned at core network;

33. systems according to claim 32, is characterized in that,

Described femto gateway, also for when determining the S1 user face data of described UE without described femto gateway, does not revise the tunnel information of the SGW in sent described E-RAB modify request messages.

34. systems according to claim 29, is characterized in that,

Described Home eNodeB, also for determining whether the S1 user face data of described UE is sent to security gateway by secure tunnel according to described gateway indication information.

35. systems according to claim 32, is characterized in that,

Described Home eNodeB, also for meeting the following conditions at received gateway indication information for the moment: described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO LN connection establishment; Described gateway is not positioned at core network; Described S1 user face data is without security gateway;

36. systems according to claim 30, is characterized in that, described lower level network element, according to obtained gateway indication information, is determined to comprise the S1 user face data path that described UE is corresponding:

37. systems according to claim 36, is characterized in that,

Described Home eNodeB, also for indicating described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO@LN connection establishment when described gateway indication information, and described data path indication information indicates described S1 user face data through femto gateway, determine that described S1 user face data need be sent to security gateway by secure tunnel;

38. systems according to claim 36, is characterized in that,

Described Home eNodeB, also for according to data path indication information, determine whether the S1 user face data of described UE is sent to security gateway by secure tunnel, comprising:

39. 1 kinds of Home eNodeB, comprising:

40., according to Home eNodeB according to claim 39, is characterized in that,

Described first acquiring unit, also for obtaining described gateway indication information from described upper level network element in the gateway repositioning process of described UE; Or,

41., according to Home eNodeB according to claim 39, is characterized in that,

Described first acquiring unit, also for receiving the E-RAB modify request messages that described upper level network element sends, described E-RAB modify request messages carries described gateway indication information.

42., according to Home eNodeB according to claim 39, is characterized in that,

Described second determining unit, also for determining whether the S1 user face data of described UE is sent to security gateway by secure tunnel according to described gateway indication information.

43. Home eNodeB according to claim 42, is characterized in that,

Described second determining unit, also for meeting the following conditions for the moment: described gateway indication information indicates described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO LN connection establishment or gateway is not positioned at core network or described S1 user face data without security gateway;

44., according to Home eNodeB according to claim 39, is characterized in that,

Described first acquiring unit, also for receiving E-RAB modify request messages, described E-RAB modify request messages carries gateway indication information and/or data path indication information;

Described second determining unit, also for according to described gateway indication information and/or described data path indication information, determines whether the S1 user face data of described UE is sent to security gateway by secure tunnel.

45. Home eNodeB according to claim 44, is characterized in that,

Described second determining unit, also for indicating described gateway to be positioned at local network or described gateway repositioning process is triggered by SIPTO@LN connection establishment when described gateway indication information, and described data path indication information indicates described S1 user face data through femto gateway, described Home eNodeB determines that described S1 user face data need be sent to security gateway by secure tunnel;

46. Home eNodeB according to claim 44, is characterized in that,

Described second determining unit, also for indicating described S1 user face data through security gateway when described data path indication information, described Home eNodeB determines that described S1 user face data need be sent to security gateway by secure tunnel; Otherwise, determine that described S1 user face data does not need to be sent to security gateway by secure tunnel, be directly sent to described gateway.

47. 1 kinds of femto gateways, comprising:

Second determining unit, for according to obtained gateway indication information, determines the S1 user face data path of user terminal UE.

48. femto gateways according to claim 47, is characterized in that,

Described second acquisition unit, also for obtaining described gateway indication information from described upper level network element in the gateway repositioning process of described UE; Or,

49. femto gateways according to claim 47, is characterized in that,

Described second acquisition unit, also for receiving the evolution RAB E-RAB modify request messages that described upper level network element sends, and received E-RAB modify request messages is sent to described Home eNodeB, described E-RAB modify request messages carries described gateway indication information.

50. femto gateways according to claim 47, is characterized in that,

Described second acquisition unit, also for receiving the E-RAB modify request messages that described mobile management entity sends;

Described second determining unit, also for according to received E-RAB modify request messages, determine that following information is one of at least:

Whether described gateway is positioned at local network;

Whether described gateway is positioned at core network;

Whether described S1 user face data is through described femto gateway;

Whether described S1 user face data is through security gateway;

Described second acquisition unit, also for the described information determined being carried in Service Gateway info, and is carried at described Service Gateway info in E-RAB modify request messages and sends to Home eNodeB.

51. femto gateways according to claim 50, is characterized in that,

Described second acquisition unit, also for the described information determined being carried in data path indication information, and sends to Home eNodeB by described to be carried in E-RAB modify request messages according to path indication information; Or,

The described information determined is carried in Service Gateway info and data path indication information, and described Service Gateway info and described data path indication information are carried in E-RAB modify request messages send to Home eNodeB.

52. femto gateways according to claim 51, is characterized in that,

According to described gateway indication information, described second determining unit, also determines that whether the S1 user face data of described UE is through described femto gateway for described femto gateway.

53. femto gateways according to claim 52, is characterized in that,

Described second determining unit, the gateway also for obtaining at described second acquisition unit meets the following conditions at least for the moment: described gateway indication information indicating service gateway is positioned at local network; Described gateway repositioning process is triggered by SIPTO@LN connection establishment; Gateway is not positioned at core network;

54. femto gateways according to claim 53, is characterized in that,

Described second acquisition unit, also for when described second determining unit determines that described femto gateway determines the S1 user face data of described UE without described femto gateway, do not revise the tunnel information of the SGW in received E-RAB modify request messages.