BRPI0924923A2 - method, apparatus and system for local routing - Google Patents

Abstract

METHOD, APPARATUS AND SYSTEM FOR LOCAL ROUTING. The present invention relates to a method, apparatus and system for local routing. The method includes the steps of: installing a data transport path for user equipment (UE); judge a destination node of a data packet sent by the EU; and if the destination node of the data packet is located on a home network, send the data packet to the destination node on the home network, or if the destination node of the data packet is located on an external network, send the data packet to the destination node on the external network.

Description

| 1152 Invention Patent Descriptive Report for "METHOD, i APPARATUS AND SYSTEM FOR LOCAL ROUTING". - FIELD OF THE INVENTION The present invention relates to the field of communications technologies, and specifically to a method, an apparatus, and a system for local routing.

BACKGROUND OF THE INVENTION To satisfy the personalized requirements of different groups of subscribers, a Residential NodeB (NodeB Residencial, HNB) appears as a communications system. The HNB, as a dedicated resource, is - developed in a location such as a residence, a community, an "A; corporation, or a school, and can allow only one User Equipment (UE) with private network rights compute or have access. A residential access mode (Residential Access) is a new access mode at present. In residential access mode, a UE gains access to a mobile network by using an HNB and a licensed frequency spectrum through a universal IP access network. The licensed frequency spectrum includes frequency spectra over multiple networks, for example, the frequency spectra used by a UMTS Terrestrial Radio Access Network (Terrestrial Radio Access Network UMTS, UTRAN), a developed UMTS Terrestrial Radio Access Network (E-UTRAN), a Code Division Multiple Access network (Code Division Multiple Access, CDMA), an Interoperability network World for Microond Access as (Worldwide Interoperability For — Microwave Access, WiMax), a Wireless Local Area Network (Wireless Local Area Network, WLAN), a High Rate Packet Data network (High Rate Packet Data, HRPD), and so on, Before HNB can gain access to an IP network, it usually needs to pass through a Residential Port (GW Residential). The residential GW has functions such as aggregating and routing the IP data from the HNB and another home network device, managing a carrier over a data concentration network (backhaul), managing the Quality of Service

(QoS), and translate a network address. It should be noted that the HNB and the residential GW may be separate entities or may be an entity. physically integrated. An HNB GW is an aggregation node for the HNB located over an operator's network. The HNB GW transfers the signaling and data between the HNB and a network element over the mobile network. For mobile networks with different types of access, HNB GWs can be different entities (for example, HNB GW or HeNB GW). The HNB GW can be a separate entity or an entity integrated with another device. | While researching the present invention, the inventor discovered | . that local UE routing in residential access mode (which includes obtaining | access to another home network device by the UE or obtaining access to | 'an external network by the UE via the HNB) is a technical problem that needs be resolved urgently.

SUMMARY OF THE INVENTION The modalities of the present invention provide a method, apparatus and system for local routing to solve a problem in the local routing of an UE in a residential access mode. The method for local routing, includes: preparing a transport route data to a UE; judge a destination node of the data packet sent by the UE; and if the destination node of the data packet is located on a home network, send the data packet to the destination node on the home network, or if the destination node of the data packet is located on an external network, sending the data packet to the destination node on the external network. An apparatus to prepare a route for local routing includes: a first address allocation unit, configured to allocate a home network address to a UE; a second address allocation unit, configured for

to allocate an external network address to the UE; and a first carrier allocation unit, configured for-. to allocate a downlink carrier resource to the UE. An apparatus for local routing includes: a judgment unit, configured to judge a destination node from a data packet sent by a UE; and a sending unit, configured for: if the judgment unit determines that the destination node of the data packet is located on a home network, send the data packet to the destination node on the home network, or if the judgment unit determines that the: data packet's destination node is located on an external network, send the data packet to the destination node on the external network, 'A system for local routing includes a control node for a local routing, where: the control node for the local routing is configured to prepare a data transport path for a UE, so that a routing node for the local routing performs the local routing of the UE.

As seen above, after the control node for local routing prepares a data transport path for the UE, the UE can send the data destined for a home network to the home network and the data destined for an external network for the external network through the routing node for local routing. In this way, local routing is implemented.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a flow chart of a method for local routing of a UE according to a first embodiment of the present invention; Figure 2 is a flow chart of a method for activating a PDN connection during the local routing of a UE according to a second embodiment of the present invention; Figure 3 is a flow chart of a method for local routing of a UE according to the second embodiment of the present invention;

Figure 4 is a flow chart of a method for activating a PDN connection during the local routing of a UE according to a third embodiment of the present invention; Figure 5 (a) is a flow chart of a method for gaining access to another home network device by a UE according to the third embodiment of the present invention;

Figure 5 (b) is a flow chart of a method for gaining access to an external network device by a UE according to the third embodiment of the present invention;

Figure 6 is a flow chart of a method for activating a cone-. connection of PDN to an external network during the local routing of a UE according to a fourth embodiment of the present invention; . Figure 7 is a flow chart of a method for activating a PDN connection to a home network during the local routing of a UE in accordance with the fourth embodiment of the present invention;

Figure 8 (a) is a flow chart of a method for gaining access to another home network device by a UE according to the fourth mode of the present invention;

Figure 8 (b) is a flow chart of a method for gaining access to an external network device by a UE according to the fourth embodiment of the present invention;

Figure 9 is a flow chart of a method for activating a PDN connection to an external network by a UE during local routing according to a fifth embodiment of the present invention;

Figure 10 is a flow chart of a method for the local routing of a UE according to the fifth embodiment of the present invention;

Figure 11 is a flow chart of a method for activating a PDN connection during the local routing of a UE according to a sixth embodiment of the present invention;

Figure 12 is a flow chart of a method for the local routing of a UE according to the sixth embodiment of the present invention;

Figure 13 is a schematic diagram of a method for a

] 5/52 UE perform local routing using an IP address obtained when a PDN connection is activated according to a seventh modality of - the present invention;

Figure 14 is a schematic diagram of a method for a UE to perform local routing using a private address allocated by an HNB in accordance with the seventh embodiment of the present invention;

Figure 15 is a schematic diagram of a method for a UE to perform local routing using a local connection address in accordance with the seventh embodiment of the present invention;

Figure 16 is a schematic diagram of a method according to

- with an eighth embodiment of the present invention; Figure 17 is a schematic diagram of a method for ro-. local teaming of a UE according to a ninth embodiment of the present invention;

Figure 18 is a flow chart of a method for paying a UE according to a tenth embodiment of the present invention;

Figure 19 is a flow chart of a method for paying a UE and sending a downlink data packet to the UE according to an eleventh embodiment of the present invention;

Figure 20 is a flow chart of a method for paying a UE and for the UE to initiate a service request according to a twelfth embodiment of the present invention;

Figure 21 is a flow chart of a method for paying a UE to the UE to initiate a service request according to a tenth

ceiramodality of the present invention;

Figure 22 is a flow chart of a method for paying an UE and for the UE to initiate a service request according to a fourteenth embodiment of the present invention;

Figure 23 is a flow chart of a method for paying a UE and for the UE to initiate a service request according to a fifteenth embodiment of the present invention;

Figure 24 is a block diagram illustrating a structure of an apparatus for preparing a route for local routing according to an embodiment of the present invention; . Figure 25 illustrates an apparatus for local routing according to an embodiment of the present invention; and Figure 26 is a schematic diagram of a system according to a sixteenth embodiment of the present invention.

DETAILED DESCRIPTION OF THE MODALITIES For an easier understanding of the preceding characteristics and merits of modalities of the present invention, the present invention is described below in detail with reference to exemplary modalities, - MODE 1 Figure 1 is a flowchart of a method for local routing 'of a UE according to a first embodiment of the present invention, where the method may include the following steps: Step 101: Prepare a data transport path for the UE.

Step 102: Judge a destination node for a data packet sent by the UE.

Step 103: If the data packet's destination node is located on a home network, send the data packet to the destination node on the home network; if the destination node of the data packet is located on an external network, send the data packet to the destination node on the external network.

A control node for the local routing is configured to process a request from the UE, and to control another NE to prepare a network service for the UE, As seen from above, when the control node for the local routing prepares a route data transport to the UE, the UE can send the data destined for a residential network to the home network and the data destined for an external network to the external network through a routing node for local routing. In this way, local routing is implemented.

Step 101 can be implemented in the following two ways: The first way is to prepare a data transport path for the UE - activating a new Packet Data Network (PDN) connection, and for details, refer to the second mode until the sixth modality to follow; the second way is to implement the local routing of the UE by downloading a data packet over the routing node to the local routing, where the data packet is loaded on an original PDN connection, and for details, refer to the seventh modality up to the ninth modality to follow.

It should be noted that the control node for local routing can combine the two previous implementation modes.

Or, different HNBs can use one of the implementation modes respectively. The following describes the two implementation modes above in detail.

Before using a local routing service, the UE needs to activate a PDN connection to a home network or a PDN connection to an external network (for example, the Internet), and obtain address information from a corresponding network during activation.

This operation is carried out on a control plane.

The UE activates the PDN connection to the home network to gain access to another home network device, and activates the PDN connection to the external network to gain access to a device on the external network. This operation is performed by the user plan, MODE 2 Figure 2 is a flow chart of a method for activating a PDN connection during the local routing of a UE according to a second modality of the present invention, where the method can include the following steps: Step 201 : Before communicating with an HNB GW, an HNB can prepare an IP security tunnel (IPSec tunnel) through an IPSec tunnel configuration process.

Step 202: Before activating the PDN connection for local routing, the UE performs an Attach operation.

It should be noted that step 202 is optional. ] Step 203: The UE sends to a management entity, - for example, a Mobility Management Entity (MME), a PDN connectivity request message to the local routing. The PDN connectivity request message for local roaming can be a PDN connection establishment request message that is sent by the UE and carries a special access point name (APN, Access Point Name) or another type of indication message. Unless otherwise specified, this explanation is applicable to all connectivity request messages from. PDN for local routing here below. The UE may also send the PDN connectivity request message to the management entity 'for local routing in the preceding Attachment process. It should be noted that the HNB or HNB GW can intercept the PDN connectivity request message for local routing, and judge whether local user data routing needs to be performed, Step 204; After receiving the PDN connectivity request message for local routing from the UE, the management entity initiates a Create Section Request for the HNB GW.

If the HNB intercepts the PDN connectivity request message for local routing, the HNB directly creates a section for local routing. If the HNB GW intercepts the PDN connectivity request message for local routing, the process goes directly to step 205, Step 205: The HNB GW initiates a Create Section Request to the HNB.

Step 206: The HNB allocates an IP address for the PDN connection that is requested to be activated.

If the HNB and a residential GW are located on the same physical entity, the residential GW allocates an IP address in a home network local IP address domain. If the PDN connection that is requested to be activated is also used to gain access to an external network, the home GW must also allocate an IP address:; in an external network address domain for the UE PDN connection. In a scenario where home network devices share an external network delP address, a port may also need to be allocated. The allocated external network | P address and port can be obtained by the home GW from another device (for example, a broadband access device or the HNB GW).

If the HNB is separated from the residential GW, the HNB allocates an address in the home network's local IP address domain, where the. HNB may request the IP address of the residential GW, Similarly, if the PDN connection that is requested to be activated is also used to obtain th access to an external network, the HNB must also allocate an IP address in the network address domain. external for the UE PDN connection, In a scenario where the home network device shares the IP address of the external network, a port may also need to be allocated. The allocated external network IP address and port can be obtained from another device's HNB (for example, the home GW, the broadband access device, or the HNB GW). The residential GW prepares a “mapping to the IP address in the home network address domain and the external network IP address (a port can also be included) that are allocated to the UE, and stores the table mapping for route judgment and Network Address Translation (NAT).

Step 207: The HNB returns a Create Section Reply message to the HNB GW, where the message includes information about an address allocated to the UE.

Address information includes the IP address allocated in the local home network domain and optionally, it can also include the external network IP address or port.

Step 208: The HNB GW returns a Create Section Reply message to the management entity, where the message includes information about the address allocated to the UE.

Step 209: The management entity sends a Create Carrier Request message i to the HNB GW, where the message includes - information about the address allocated to the UE.

Step 210: HNB GW sends the Create Carrier Request message to the HNB, where the message includes information about the address allocated to the UE, Step 211: The HNB allocates a radio resource to a carrier, and sends a Radio Resource Reset message to the UE, where the message includes information about the address allocated to the UE The HNB can send only the IP address allocated in the domain of - local home network address to the UE, or you can also send the public network IP address and optionally send the port that is allocated 'by the HNB to the UE to the UE.

Step 212: UE returns a Full Radio Resource Reset message to the HNB.

The allocation of a radio carrier resource ends, Step 213: The HNB allocates a downlink carrier resource to the UE, and sends the allocated downlink carrier resource to HNB GW via a Create Reply message Carrier.

The allocation of a carrier resource ends.

Step 214: The HNB GW returns a Create Carrier Reply message to the management entity.

A carrier configuration process ends.

Figure 3 is a flowchart of a method for local routing of aUU according to the second embodiment of the present invention, where the method may include the following steps: Step 301: The UE obtains a destination address from a device target network before sending data.

Step 302: The UE sends a data packet that includes the target network device's address to the HNB via the radio bearer resource allocated in step 213. Step 303: The HNB sends the data packet that includes the address

destination price for residential GW through a residential network. Step 304: Residential GW judges the destination address of the country. data collection. If the destination address identifies an internal network device, the process goes to step 305; if the destination address identifies an external network device, the process goes to step 306.

Step 305: The home GW sends the data packet to a home network device over the home network. The process ends. Consequently, the data that the home network device sends to the UE is addressed to the HNB through the IP address in the home network IP address domain of the UE and sent over the. radio carrier to the UE. Step 306: The residential GW performs a Network Address Translation (NAT), and sends the data packet to the broadband network access device via the home network.

Step 307: The broadband network access device performs Network Address Translation (NAT), and sends the data packet to the external network device over an external network.

Consequently, the data that the external public network device sends to the UE is addressed to the residential GW through the delP address in the public network | P address domain allocated to the UE; after NAT is performed, the data is additionally addressed to the HNB and sent over the radio carrier to the UE.

Locally routed uplink and downlink data packets are routed along the same path. The processes for the routing method in this embodiment of the present invention follow the same rule.

In a downlink direction, the data that the home network device sends to the UE is addressed to the HNB via the IP address in the home network IP address domain of the UE and sent to the UE via the carrier. radio. The data that the external network device sends to the UE is addressed to the home GW via the IP address in the external network IP address domain allocated.

for the UE; after NAT is performed, the data is additionally addressed to the HNB and sent to the UE via the radio carrier.

: MODALITY 3 The third modality is different from the second modality due to the fact: in an operation performed by a user plan in the third modality, when a UE obtains access to an external network, an HNB sends a data packet to an HNB GW through a security tunnel that is prepared in advance; The HNB GW establishes a connection with the external network, and routes the data packet from the UE to the external network. Compared to a situation in which the UE sends a data packet to a home network device, two connections from Different PDNs are used and two APN identifiers (IDs) are used to 'identify the external network and a home network respectively. In the second modality, however, a residential GW sends a packet of data to a broadband network access device through the residential network; the broadband network access device establishes a connection to the external network, and routes the data packet to the UE. In the process, a PDN connection is established and an APN ID is used.

Due to the previous difference in a process of obtaining access to the external network by the user plan, over a control plan, in the third modality, HNB GW allocates the address information to obtain access to the external network for the UE, and the HNB allocates the address information to gain access to the home network for the UE. In the second embodiment, the HNB allocates the external network address information and the home network address information to the UE.

Figure 4 is a flowchart of a method to activate a PDN connection during the local routing of an UE according to the third modality of the present invention where the method can include the following steps: Step 401: Before communicating with the HNB GW, the HNB needs to prepare an IPSec tunnel through an IPSec tunnel configuration process.

Step 402: Before activating the PDN connection for local routing, the UE performs an Attach operation. - It should be noted that step 402 is optional. Step 403: The UE sends a PDON connectivity request message to a management entity for local routing.

The UE may also send the PDN connectivity request message to the management entity for local routing in the preceding Attachment process, Step 404: The management entity receives the PDN connectivity request message from the UE for local routing, and initiate a Create Section Request for HNB GW. 7 If the current process is a process to activate the PDN connection to gain access to the external network, the HNB GW needs to allocate an external network IP address and a port for the UE. The allocation process can also be performed after step 407. If the current process is a process for activating the PDN connection to gain access to the home network, HNB GW directly performs step 405, Step 405: A HNB GW continues to initiate a Create Section Request to the HNB, Step 406: If the current process is a process to activate the PDN connection to gain access to the home network, the HNB allocates a local home network IP address to the UE.

Preferably, in a PDN connection establishment process, both an IP address to gain access to the home network and an IP address and a port to gain access to the external network can be allocated to the UE. That is, through a process of establishing a PDN connection, the PDN connections to obtain access to the home network and the external network are established respectively.

Step 407: The HNB returns a Create Section Reply message to the HNB GW, where the message includes information about the address allocated to the UE.

Step 408: HNB GW returns the Create Section Reply message to the management entity, where the message includes. information about the address allocated to the UE.

Step 409: The management entity sends a Create Carrier Request message to HNB GW, where the message includes information about the address allocated to the UE.

Step 410: HNB GW sends the Create Carrier Request message to the HNB, where the message includes information about the address allocated to the UE.

Step 411: The HNB allocates a radio resource to a carrier, and sends a Radio Resource Reset message to the UE, where the message includes information about the address allocated to the UE.

Step 412: The UE resumes a Full Radio Resource Reset message for the HNB.

The allocation of a radio carrier resource ends, and a data packet can be sent and received between the UE and the HNB.

Step 413: The HNB allocates a downlink bearer resource to the UE, and sends the allocated downlink bearer resource to HNB GW. The allocation of a bearer resource ends.

Step 414: The HNB GW returns a Create Carrier Reply message to the management entity.

A carrier configuration process ends.

Figure 5 (a) is a flow chart of a method for gaining access to another home network device by a UE according to the third embodiment of the present invention, where the method can include the following steps: Step 501-1: The UE sends a data packet destined for the home network device to the HNB through a PDN radio link carrier of the home network.

Step 501-2: The HNB sends the data packet to the home GW via the home network.

Step 501-3: The home GW sends the data packet to the home network device via the home network. . Figure 5 (b) is a flow chart of a method for gaining access to an external network device by a UE according to the third mode of the present invention, where the method may include the following steps: Step 502-1 : The UE sends a data packet destined for the external network device to the HNB through a PDN connection radio carrier of the external network.

Step 502-2: The HNB sends the data packet to the HNB GW. through an IPSec tunnel that is configured in advance, Step 502-3: HNB GW sends the data packet to the external network device via the external network, MODE 4 The fourth mode is different from the third mode by fact that: in an operation performed by a user plan in the fourth modality, when an UE obtains access to an external network, an HNB sends a data packet to an HNB GW through an uplink carrier feature (for example, a GPRS Tunneling Protocol (GTP) tunnel over a 3GPP network) allocated by HNB GW; in the third mode, however, the HNB sends a data packet to the HNB GW through a security tunnel that is prepared in advance. Due to the previous difference in a process to obtain access to the external network by the user plan, over a control plan, in the fourth modality, in a process to activate a PDN connection to the external network, HNB GW also needs to allocate an uplink bearer resource for the UE.

Figure 6 is a flowchart of a method for activating a PDN connection to an external network by a UE during local routing according to a fourth embodiment of the present invention, where the method can include the following steps: Step 601: Before communicating with HNB GW, HNB needs to prepare a tunnel! IPSec through a process of configuring

IPSec level. Step 602: Before enabling the PDN connection for routing - local, the UE performs an Attach operation.

It should be noted that step 602 is optional.

Step 603: The UE sends a PDN connectivity request message to a management entity for local routing.

The UE can also send the PDN connectivity request message to the management entity for local routing in the preceding Attachment process. . Step 604: After receiving the PDN connectivity request message, the management entity initiates a Request to Create "Section for HNB GW. Step 605: HNB GW allocates the address information, which includes the | P and port, for the requested PDN connection to be activated.

Optionally, the process for obtaining the local routing IP address of the residential network by the residential GW through interaction with the HNB in the third modality can be included. For details, see step 505 to step 507. No further description will be provided here.

Step 606: HNB GW returns the Create Section Reply message to the management entity, where the message includes information about the address allocated to the UE.

Step 607: The management entity sends a Create Carrier Request message to HNB GW, where the message includes information about the address allocated to the UE.

Step 608: HNB GW allocates an uplink carrier resource to a carrier, and sends the resource to the HNB via a Create Bearer Request message, Step 609: HNB allocates a radio resource to the UE from ac- cording to the request message, and sends a Radio Resource Reconfiguration message to the UE.

Step 610: The UE returns a Complete Radio Resource Reset message to the HNB. The allocation of a radio carrier resource ends. Step 611: The HNB allocates a downlink bearer resource to the EU, and sends the allocated downlink bearer resource to the HNB GW. The allocation of a carrier resource ends. Step 612: The HNB GW returns a Create Carrier Reply message to the management entity. A carrier configuration process ends.

Figure 7 is a flow chart of a method for activating a cone. PDN connection to a home network during the local routing of an UE according to the fourth modality of the present invention, where method 'may include the following steps: Step 701: Before communicating with the HNB GW, the HNB needs to prepare a tunnel IPSec through an IPSec tunnel configuration process.

Step 702: Before activating the PDN connection for local routing, the UE performs an Attach operation. It should be noted that step 702 is optional.

Step 703: The UE sends a PDN connectivity request message to a management entity for local routing.

The UE can also send the PDN connectivity request message to the management entity for routing —local in the preceding Attachment process.

Step 704: After receiving the PDN connectivity request message, the management entity initiates a Create Section Request for HNB GW.

Step 705: The HNB GW continues to initiate a Create Section Request for the HNBE, Step 706: The HNB allocates a home network local IP address for the PDN connection that is requested to be activated.

Step 707: The HNB returns a Create Section Reply message to the HNB GW, where the message includes the address allocated to the. HUH.

Step 708: HNB GW resumes the Create Section Reply message for the management entity, where the message is the address allocated to the UE.

Step 709: The management entity sends a Create Carrier Request message to HNB GW, where the message includes the address allocated to the UE.

Step 710: The HNB GW sends a Create Carrier Request message to the HNB, where the message includes the address allocated to the UE. 'Step 711: The HNB allocates a radio resource to a carrier, sends a Radio Resource Reset message to the UE, where the message includes the address allocated to the UE, Step 712: The UE returns a message from Complete Radio Resource Reconfiguration for HNB.

The allocation of the radio bearer resource ends.

Step 713: The HNB allocates a downlink bearer resource to the EU, and sends the allocated downlink bearer resource to the HNB GW.

Carrier resource allocation ends, Step 714: HNB GW returns a Create Carrier Response message to the management entity.

A carrier configuration process ends.

Figure 8 (a) is a flow chart of a method for gaining access to another home network device by a UE according to the fourth embodiment of the present invention, where the method can include the following steps: Step 801-1: The UE sends a data packet destined for the home network device to the HNB through a PDN connection radio carrier to the home network.

Step 801-2: The HNB sends the data packet to the resident GW

through the residential network. Step 801-3: The residential GW sends the data packet to the “. home network device through the home network. Figure 8 (b) is a flowchart of a method for gaining access to an external network device by a UE according to the fourth mode of the present invention, where the method can include the following steps: Step 802-1: O UE sends a data packet destined for the external network device to the HNB through a PDN connection radio carrier to the external network.

Step 802-2: The HNB sends the data packet to the HNB GW. through the uplink carrier feature. Step 802-3: The residential GW sends the data packet to the "external network device via the external network. MODE 5 The fifth mode is different from the second mode in that: in an operation performed by a user in the fifth mode, when a UE obtains access to an external network, an HNB or a residential GW sends a data packet to an HNB GW through a security tunnel that is configured in advance, and the HNB GW that is connected to the external network judges, according to a destination address, whether the data packet is routed to a home network or an external network; in the second mode, however, the home GW sends a data packet to a network access device broadband via the home network, and the broadband network access device establishes a connection to the external network.

Due to the previous difference in a process of obtaining access to the external network by the user plan, over a control plan, in the fifth modality, HNB GW allocates the external network address information (which includes an external network IP address. and optionally includes a port) for the UE; the HNB allocates the home network address information to the UE. Optionally, the HNB can also allocate an external network | P address and a port to route local user data to an external network, and performs, on the residential GW, a NAT on 'a packet of data exchanged with the external network . In the second embodiment, í the HNB allocates the external network address information and the home network address information to the UE. In both methods, a PDN connection and a PDN ID are used.

Figure 9 is a flowchart of a method for activating a PDN connection to an external network by a UE during local routing according to a fifth embodiment of the present invention, where the method can include the following steps: Step 901: Before communicating with HNB GW, the HNB needs to - prepare an | IPSec tunnel through an IPSec tunnel configuration process.

Í Step 902: Before activating the PDN connection for local routing, the UE performs an Attach operation.

It should be noted that step 902 is optional.

Step 903: The UE sends a PDN connectivity request message to a management entity for local routing.

The UE can also send the PDN connectivity request message to the management entity for local routing in the preceding Attachment process.

Step 904: The management entity receives the PDN connectivity request message sent by the UE, and initiates a Create Section Request for the HNB GW.

If the current process is a process to activate the PDN connection to gain access to the external network, the HNB GW needs to allocate an external network | P address and optionally allocate a port for the UE. Optionally, the external network's IP address can be allocated by the HNB or the residential GW in step 906, and optionally it can also be allocated by the HNB or the residential GW.

Step 905: HNB GW continues to initiate a Create Section Request for the HNB.

Step 906: The HNB allocates a local home network IP address for the UE. . Step 907: The HNB returns a Create Section Reply message to the HNB GW, where the message includes the address allocated to the

UE Step 908: HNB GW returns the Create Section Reply message to the management entity, where the message includes the address allocated to the UE. Step 909: The management entity sends a Create Carrier Request message to HNB GW, where the message includes' the address allocated to the UE. Step 910: HNB GW sends the Create Carrier Request message to the HNB, where the message includes the address allocated to the UE. Step 911: The HNB allocates a radio resource to the UE, and sends a Radio Resource Reset message to the UE, where the message includes the address allocated to the UE. Optionally, the address is usually loaded into a Non-Access Access Stratum (NAS) message. The HNB can send only the IP address allocated in the home local domain address domain to the UE, and can also send the external network P address and optionally send to the port that the residential GW or HNB GW allocates to the EU to the EU. Step 912: The UE returns a Full Radio Resource Reset message to the HNB. The allocation of a carrier-radiotherapeutic carrier resource. Step 913: The HNB allocates a downlink bearer resource to the UE, and sends the allocated downlink bearer resource to the HNB GW via a Create Bearer Reply message, Allocation of a bearer resource ends. Step 914: HNB GW returns a Create Carrier Reply message to the management entity. A carrier configuration process ends.

Figure 10 is a flowchart of a method for the local routing of an UE according to the fifth embodiment of the present invention, - where the method may include the following steps: Step 1001: The UE obtains the destination address of a device target video before sending data. Step 1002: The UE sends a data packet that includes the destination address to the HNB through a radio carrier. Step 1003: The HNB sends the data packet that includes the destination address to the home GW over a home network.

Step 1004: The home GW judges the destination address of the - data packet, If the destination address indicates that the destination device is an internal network device, the process goes to step 1005; if the destination address indicates that the destination device is an external network device, the process goes to step 1006, Step 1005: The home GW sends the data packet to the home network device via the home network. The process ends.

Step 1006: The residential GW sends the data packet to the HNB GW through the IPSec tunnel.

Step 1007: The HNB GW performs NAT, and sends the data packet to the external network device via an external network. Optionally, NAT can also be performed in step 1006 according to a specific condition, MODALITY 6 The sixth modality is different from the fifth modality in that: in an operation performed by a user plan in the sixth modality, when a UE obtains access to an external network, a residential GW sends a data packet to an HNB GW through an uplink carrier resource allocated by the HNB GW; in the fifth modality, however, residential GW sends a data packet to HNB GW through a security tunnel that is configured in advance. Due to the previous difference in a process of obtaining access to the external network by the user plan, or a control plan, in the sixth modality, in a process of activating a PDN connection to the external network, HNB GW - also needs to allocate a uplink carrier resource for the UE. Figure 11 is a flow chart of a method for activating a PDN connection during the local routing of a UE according to a sixth embodiment of the present invention, where the method can include the following steps: Step 1101: Before communicating with HNB GW, an HNB needs to prepare an IPSec tunnel through a tunnel configuration process.

. Step 1102: Before activating the PDN connection for local routing, the UE performs an Attach operation. 'It should be noted that step 1102 is optional.

Step 1103: The UE sends a PDN connectivity request message to a management entity for local routing.

The UE can also send the PDN connectivity request message to the management entity for local routing in the Attachment process.

Step 1104: After receiving the PDN connectivity request message, the management entity initiates a Create Section Request for HNB GW.

Optionally, the process of obtaining the P address of the residential network by GW residential through interaction with the HNB in the fifth modality can be included. For details, see step 905 to step 907. No further description will be provided here.

Step 1105: The HNB GW allocates an IP address for the PDN connection that is requested to be activated.

Step 1106: The HNB GW returns a Create Section Reply message to the management entity, where the message includes the address allocated to the UE.

Step 1107: The management entity sends a Create Carrier Request message to HNB GW, where the message includes the address allocated to the UE. - Step 1108: HNB GW allocates an uplink carrier resource to the UE, and sends the resource information to the HNB via the Create Carrier Request message. Step 1109: The HNB allocates a radio resource to a carrier, and sends a Radio Resource Reset message to the UE. Step 1110: The UE resumes a Full Radio Resource Reset message for the HNB. The allocation of a resource. radio carrier ends. Step 1111: The HNB allocates a downlink bearer resource 'to the UE, and sends the allocated downlink bearer resource to HNB GW. The allocation of a bearer resource ends.

Step 1112: The HNB GW returns a Create Carrier Response message to the management entity, A carrier configuration process ends.

Figure 12 is a flowchart of a method for the local routing of an UE according to the sixth embodiment of the present invention, where the method can include the following steps: Step 1201: The user obtains a destination address from a target network device before sending the data.

Step 1202: The UE sends a data packet that includes the destination address to the HNB through a radio carrier.

Step 1203: The HNB sends the data packet that includes the destination address to the home GW over a home network.

Step 1204: The home GW judges the destination address of the data packet. If the destination address indicates that the destination device is an internal network device, the process goes to step 1205; if the destination address indicates that the destination device is an external network device, the process goes to step 1206.

Step 1205: The home GW sends the data packet to the home network device over the home network. The process ends. - Step 1206: The residential GW sends the data packet to the HNB GW using the previous uplink carrier feature. Step 1207: The HNB GW performs NAT, and sends the data packet to the external network device via the external network, as seen from above, when a control node for the local route sets up a transport path data to the UE, the UE can send the data destined for a home network to the home network and the data destined for an external network to the external network. through a routing node for local routing. In this way, local routing is implemented.

"If no HNB GW is developed on the network, in the second modality up to the previous sixth modality, the MME is directly co-connected in the HNB, and a process of interaction between the MME, the HNB, and the HNB GW does not exist. IPSec tunnel in the second modality, in the third modality, and in the fifth modality it is directly connected to a core network user plan entity or to a security port of the core network user plan entity.

It should be noted that in the second mode up to the sixth mode, when a PDN connection to gain access to the home network is established for the UE, a home GW route can be used directly from a home access network route. broadband to the external network through a local access network, without passing through the HNB GW.

Consequently, an operator may suffer a loss.

To restrict access to an external network through the PDN connection to the home network, in a process of establishing a PDN connection, a configuration file for route restriction can be sent to the home GW in an interaction process between the control name for local routing and HNB. For example, it can be specified that a data packet that is sent over an HNB port and routed with the IP address in the home network's local IP address domain (for example, 10.xxx, 192.168.xx) cannot be routed to | external network.

In addition, a Network Management System (NMS) - can configure the configuration file for the residential GW so that access to the external network through the PDN connection to the home network is restricted.

Above detailed is a process for configuring a data transport path for the UE by activating a new PDN connection so that local routing is implemented for the UE.

The following describes a process for downloading a packet of data about the “routing node for local routing based on a connection. of original PDN so that local routing is implemented for the UE. 'As seen above, when the control node for local routing sets up a data transport path for the UE, the UE can send data destined for a home network to the home network and data destined for an external network for the external network through the routing node for local routing.

In this way, local routing is implemented.

It should be noted that in the second mode up to the sixth mode, when a PDN connection to gain access to the home network is configured for the UE, the home GW route can be used directly from the band access network route. broadband to the external network through the local access network, without passing through the HNB GW or the core network user plan entity.

Consequently, if the operator needs the traffic transmitted by the HNB user over the HNB GW or the core network user plan entity or the operator needs to intercept in the name of the law a data stream that is locally routed from the UE for the external network over the HNB GW or the core network user plan entity, traffic measurement and interception in the name of the law are difficult to implement because the local data flow does not pass through the HNB GW or the core network user plan.

To restrict access to the external network through co-operation

IP connection to the home network or specify which data streams need to pass through a local HNB GW route or perform an inter-. in the name of the law and traffic measurement at the HNB, in a process of sending a NodeB registration response message and a NodeB configuration update message or in the process of establishing a PDN connection, the control node for Local routing (HNB GW or MME) can send a configuration file or parameter to the residential GW / HNB in a message (an initial UE context configuration request, a request to modify UE, a radio resource configuration / modification request, or a transfer request, or a message recently added for exchange) that is exchanged with the HNB, or the NMS performs the configuration for the residential GW / HNB in an HNB binding initialization process.

The configuration is an operator policy, and can be dynamically changed.

For example, to restrict the UE from gaining access to the external network via the PDN connection to the home network, it can be specified that the data packet that is sent over the HNB port and routed with an IP address in the address domain local home network IP address (for example, 10.xxx, 192.168.xx) cannot be routed to the external network, or it can be specified that a data packet sent through the HNB port and whose destination address is an address public network P's cannot be routed to the external network.

To restrict a specified data stream from passing through a local HNB GW route, it can be specified (for the second mode, the fifth mode of this mode) that a data stream from a specified user, a data stream sent to a specified destination address, or a data stream of a specified service type must be sent to HNB GW through a security tunnel or a carrier resource.

In this case, the residential GW can perform NAT over a corresponding data packet while routing the data.

Consequently, all data packets sent by the external network to the UE can be retrieved.

the same route.

The preceding configuration policy can be used to intercept in the name of the law the data in the local routing of the UE.

In the configuration file or parameter, it can also be specified that a data packet from a specified user, a data packet sent to a destination address, or data packets from a specified service type must be intercepted in the name of the law. .

During execution, the home GW can replicate a data packet that needs to be intercepted, and send the data packet to the HNB GW or the core network user plan entity through a security tunnel or an uplink carrier feature.

NAT can be performed on the packet. data at residential GW; or the data packet can be encapsulated in the home GW, and after information such as a user ID and address of the user or HNB is added, the data packet is sent to a functional interception entity in the name of the specified law .

In this case, an interception entity address in the name of the law needs to be specified in the configuration. The residential GW can perform such replication and interception on the data packets that the UE sends to a communication pair and the communication pair sends to the HUH.

The preceding configuration policy can also be used to measure data traffic in the local routing of the UE. In the configuration file or in the parameter, it can be specified that a data packet from a specified user, a data packet sent to a specified destination address, or a data packet for a specified service type requires traffic measurement.

During execution, the residential GW can report the measurement of data traffic in the user's local routing for times and batches based on a report request or specified time according to the policy.

Traffic measurement can be performed on a NodeB or user unit, or performed according to a type of service, a destination address, an uplink / downlink direction, a time segment, and network access residential or external network.

The measurement result can be loaded into an interface message, for example, between a current NodeB and the core network or transferred using a newly added interface message. o For configuration policy confidentiality, the configuration file or parameter can be encrypted and then sent to the HNB. A specified health ID or security ID can also be added to the data intercepted in the name of the law.

The user being able to perform local routing can be a part of the user's subscription information, especially the subscription information of a Closed Subscriber Group (CSG). The subscription can be specified for some NodeBs or CSGs or for all HNBs and. CSGs. When the UE initiates a request to establish a PDN connection, the control node for local routing over the network judges, according to the user's subscription, whether the user is allowed to run a local routing service; if the user is not allowed to perform local routing, the network may refuse to establish a PDN connection for local routing. NodeB having a local routing capability can be a basis for the UE to decide to settle on NodeB and start a local routing service. Capacity can be if NodeB physically has hardware and software functions for local routing or if NodeB can allow configuration of a local routing function that the operator determines according to the subscription and a development policy - network. In a NodeB System Information Transmission (SIB), for example, SIB1, NodeB can transmit an indication that indicates its ability to support local routing, and the UE can judge, according to the indication received, getting access to NodeB and starting a local routing service when settling on NodeB. The indication indicating the local routing capacity can be further divided into whether local routing to the home network is supported and local routing to the Internet is supported. The UE can display the indication to the user in a user interface in an image or text mode.

NodeB having a local routing capability is also a basis for the control node for local routing on the network (especially by HNB GW and MME) to decide whether to configure a local route for the UE.

When NodeB registers, NodeB can send an indication that NodeB has the capacity for local routing to HNB GW or MME.

Generally, when HNB GW is developed, the indication of capacity can only be reported for HNB GW.

If the network performs section management under MME only, MME does not know whether NodeB has the capability for local routing.

The first mode is: The HNB reports whether the HNB has the capacity. to support local routing to the HNB GW through a NodeB log message; when the UE initiates to the MME a request to 'establish PDN connection for local routing, the MME initiates | a Request to Create Section for HNB GW; HNB GW makes a judgment! according to the local routing capability of the NodeB that is locally stored; if the NodeB does not have the local routing capability, the PDN connection establishment request is rejected, and the MME rejects the UE's PDN connection establishment request accordingly.

Another way is: The HNB reports whether the HNB has the capacity to support local routing to the HNB GW via a NodeB log message; when the UE rests on the HNB and sends an INITIAL EU MESSAGE (INITIAL EU MESSAGE) to the network, the HNB GW loads, in the INITIAL EU MESSAGE (INITIAL EU MESSAGE) sent to the MME, an indication that indicates whether the HNB supports local routing.

When the UE initiates a request to establish a PDN connection for local routing to MME, the MME determines whether to initiate a Create Section Request as indicated; if NoB does not have local routing capability, the MME rejects the request to establish a PDN connection from the UE.

The third way is: NodeB loads, in an INITIAL EU MESSAGE (INITIAL EU MESSAGE) sent to MME, an

cation indicating whether NodeB supports local routing; or NodeB sends an indication to HNB GW via the INITIAL EU MESSAGE, and HNB GW transfers the INITIAL EU MESSAGE to the MME. When the UE initiates a request for PDN connectivity to the local routing for MME, MME determines whether to initiate a Create Section Request in accordance with the instruction; if NodeB does not have local routing capability, the MME rejects the request for UE PDN connectivity. The fourth mode is: The HNB loads, in a UPLINK NAS TRANSPORT message (UPLINK NAS TRANSPORT) sent to MME (or sent to HNB GW and transferred to MME. By HNB GW), an indication that indicates whether the HNB has the capacity to support local routing; or the HNB reports whether the HNB has the ability to 'support local routing to the HNB GW via a NodeB log message, and when the HNB sends a UPLINK NAS TRANSPORT message (UPLINK NAS TRANSPORT) ), HNB GW adds NodeB's local routing capability to the UPLINK NAS TRANSPORT message (UPLINK NAS TRANSPORT), and sends the UPLINK NAS TRANSPORT message to the MME. When the UE initiates a request for PDON connectivity for local routing to the MME, the MME determines whether to initiate a Create Section Request according to the instruction; if NodeB does not have local routing capability, the MME rejects the UE's PON connectivity request. When the PDN connection establishment for local routing fails, the MME or HNB GW can send a Non-Access Stratum (NAS) message that notifies the UE of a fact that the HNB does not have the capacity for local routing , NodeB can send an RRC (Radio Resource Control) message that carries an indication that NodeB does not have the local routing capability for the

UE Above detailed is a process of configuring a data transport path to the UE by activating a new data connection.

PDN so that local routing is implemented for the UE.

The following describes a method for the local routing of a UE by directly replacing the source address of a data packet on an original carrier based on an original PDN connection.

The implementation of a local routing policy, interception in the name of the law, and measurement of preceding traffic by sending a configuration file or a parameter may also apply in the following method.

It should be noted that the download of a data packet over a routing node for local routing can be implemented through the following method: directly replacing the source address. of the data package.

MODE 7 'For an uplink packet sent by a UE, an HNB judges, according to a destination address, whether to send the packet to another home network device.

For example, another home network device can register a device's IP address with the HNB or obtain an IP address from the HNB, or register the device's IP address with a third-party server.

The HNB can query the IP address of another home network device, and then judge whether the destination address for the uplink data packet sent by the UE is the address of another home network device; if the destination address of the uplink data packet sent by the UE is the address of another home network device, the uplink data packet is transferred to another home network device.

Optionally, before the transfer, an address translation can be performed.

An IP address used by the UE can be an IP address that is obtained when a PDN connection is activated, a private address from an IP address allocated by the HNB, or a local connection address (local address of connection) from an IP address.

The details are as follows: Figure 13 is a schematic diagram of a method for a UE to perform local routing using an IP address obtained when a PDN connection is activated according to a seventh embodiment of the present invention. "a In an uplink direction, the UE activates the PDN connection, and obtains an IP address from a data port; the UE sends an uplink data packet to the HNB; the HNB performs the download accordingly with the destination address of the uplink data packet sent by the UE, that is, after replacing the source address of the uplink data packet destined for another home network device, the u-Plink data packet intended for another home network device is sent to the destination address, and other uplink data packets are sent to a HNB GW.

In a downlink direction, another home network device sends an IP packet of downlink data destined for the UE to the HNB; the HNB obtains a downlink carrier from the UE according to an address translation table, and sends the downlink data packet sent by another home network device to the UE.

Figure 14 is a schematic diagram of a method for a UE to perform local routing using a private address allocated by an HNB in accordance with the seventh embodiment of the present invention.

In the uplink direction, the UE activates the PDN connection, and obtains a | P address from the data port; the UE sends a Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol, DHCP) message to the HNB, and obtains a private address from the HNB. The DHCP message can be loaded into a Radio Resource Control (RRC) message, or sent as a standard data packet. After analyzing that the data packet is a DHCP message, the HNB processes the message according to a DHCP server mode. The UE sends a data packet to the HNB using the private address; the HNB performs the download according to the destination address of the data packet sent by the UE, that is, a data packet destined for another home network device is sent to the destination address, and other data packets are sent for HNB GW.

In the downlink direction, another home network device sends a data packet destined for the UE to the HNB, and the HNB sends the received data packet to the UE. . Figure 15 is a schematic diagram of a method for a UE to perform local routing using a local connection address in accordance with the seventh embodiment of the present invention. In the uplink direction, the UE activates the PDN connection, and obtains an IP address from the data port; the UE sends a data packet to the HNB using a local connection address; if the HNB determines that the data packet includes a Request Router message. (RS), the data packet is sent to the HNB GW; if the HNB determines that the data packet does not include an RS message, the data packet 'is sent to another home network device. In the downlink direction, another home network device sends a data packet destined for the UE to the HNB, and the HNB sends the received data packet to the UE. MODE 8 An HNB GW or an HNB determines, according to the destination addresses of a data packet sent by an UE, which data packets need to be routed locally. For example, destination addresses can be classified, and a data packet whose destination address is located on the Internet to the Internet and a data packet whose destination address is located on another external network to a corresponding destination address.

In addition, a user's subscription data (for example, a user class) can also be considered. A data packet from a high class user is sent to a core network to guarantee QoS. A data packet a low-class user whose destination address is located on the Internet is sent to the Internet to relieve a load on the core network.

Figure 16 is a schematic diagram of a method according to an eighth embodiment of the invention.

In an uplink direction, the UE activates a PDN connection, and obtains an IP address from the data port.

The UE sends a data packet to the HNB GW; HNB GW performs the download accordingly. with the destination address of the data packet sent by the UE and the network settings of an operator or according to a preference of the UE.

A home network replaces a source address in a data packet destined for the Internet, and sends the data packet with the substituted source address to the Internet and other data packets to a mobile core network.

In a downlink direction, HNB GW receives data packets sent over the Internet, where these data packets are destined for the UE.

HNB GW obtains a downlink carrier from the UE according to an address translation table.

HNB GW sends the data packages to the UE.

MODE 9 Figure 17 is a schematic diagram of a method for the local routing of a UE according to a ninth modality of the present invention.

An MME notifies an MME subscription data HNB GW and an HNB user.

The specific implementation includes: MME sends an INITIAL CONTEXT CONFIGURATION message (INITIAL CONTEXT CONFIGURATION) to HNB GW, where the INITIAL CONTEXT CONFIGURATION message loads some user subscription data, including but not limited to any combination of the following: a class of user, whether home network access is allowed, whether local routing directly from the Internet is allowed, and so on.

The HNB GW performs local routing to the UE according to the user class and a destination address.

The HNB GW sends an INITIAL CONTEXT CONFIGURATION message (INITIAL CONTEXT CONFIGURATION) to an HNB, where the INITIAL CONTEXT CONFIGURATION message carries an indication that indicates whether the user is allowed to gain access to a home network; if the user is allowed to gain access to the home network, the HNB provides the UE with a home network access service, that is, the UE can obtain access to another home network device. . As seen above, the HNB detects a source IP address from a data packet sent by the UE.

If it is determined that the data packet is sent to the home network, the data packet is transferred to another home network device.

This mode can allow the UE to work in common with an IP layer of another home network device, and allow the HNB to differentiate a data stream between the UE and another home network device from other data streams, the that helps the UE e. the home network running a | P-based service.

HNB GW classifies data streams according to the destination addresses of the data packets.

One type of data stream is located on the Internet, and the other type is located on a core network.

If the destination address of a data packet sent by the UE is located on the Internet, the data packet is sent directly to the Internet; if the destination address of the data packet is located on the core network, the data packet is sent to the core network.

This mode prevents all data packets from the UE from being sent to the “core” network, and therefore relieves a load on the core network.

Detailed above is a method for the local routing of an UE. The following describes the payment caused by the local routing of the UE.

It should be noted that, in the modalities of the present invention, a cause of payment is: If a carrier between the UE and a control node for local routing is released, when a routing node on a network receives a data packet sent to the UE, the network routing node needs to try to find the UE in order to send the received data packet to the UE.

In this case, the network routing node initiates payment to search for the UE.

MODE 10 Figure 18 is a flow chart of a method for paying a UE according to a tenth modality of the present invention, where the method can include the following steps: O. Step 1801: When receiving downlink data, a node . network routing initiates payment according to an address | downlink data destination, where the network routing node includes an HNB or HNB GW.

Step 1802: The network routing node receives a payment response returned by the UE. As seen from the above, a payment problem caused by local routing is resolved through step 1801 and step 1802.

'MODALITY 11 Figure 19 is a flowchart of a method for paying a UE' and sending a downlink data packet to the UE according to an eleventh embodiment of the present invention, where the method can include the following steps: Step 1901 : When an HNB GW receives a downlink data stream sent over an external network, the HNB GW sends a data arrival notification message to a network control plan entity.

HNB GW caches the downlink data stream routed by the external network, verifies a destination address of a packet of data in the data stream, and determines, according to a locally stored address table , a user ID, and an ID of a core network control plan entity where the UE is registered, a UE that needs to be paid for, and the core network control plan entity where the UE is registered.

HNB GW loads, in a notification message sent to the core network control plan entity, a user ID indicating a user who needs to be paid; a special ID indicating that locally routed data from EU arrivals can also be loaded. The user ID refers to an International Mobile Subscriber Identity (IMSI), a Temporary Mobile Subscriber Identity (TMSI),

a PS-TMSI (P-TMSI), and a SAE-TMSI (S-TMSI) or an IP address, 'and so on. Preferably, the user ID can be an IMSI. o Step 1902: The core network control plan entity. finds the context information stored in the UE according to the user's 1D, and sends a payment message to the HNB GW according to the context information.

The payment message loads the user ID and user registration area information for the user, and can also load a user's CSG list. The user ID in the payment message refers to IMS), TMSI, P-TMSI, or S-TMSI, and so on. . If a downlink data stream that is sent by a core network control plan entity exists at this time or in a 'time window, the core network control plan entity must also pay the UE in another NodeB and HNB macro. Step 1903: After receiving the payment message, HNB GW sends the payment message to an HNB controlled by HNB GW.

HNB GW may also judge, according to the TAI list and the user's CSG list, some HNBs controlled by HNB GW and to which payment information is sent, or HNB GW may send the payment message only to an HNB controlled by HNB GW and with which the user recently establishes a connection.

Step 1904: The HNB that receives the pay-as-you-go message to the HNB-controlled UE, Step 1905: After receiving the payment, the UE responds to the payment, and initiates a payment response service request (REQUEST FOR SERVICE) for the core network control plan entity.

Step 1906: The core network control plan entity sends an INITIAL CONTEXT CONFIGURATION message to HNB GW, and notifies HNB GW of stored carrier information from the core network control plan entity. i Step 1907: HNB GW stores carrier information x; of the core network control plan entity, allocates a carrier,. sends an INITIAL CONTEXT CONFIGURATION message to the HNB according to the received carrier information, and notifies the allocated carrier's HNB.

Step 1908: The HNB sends a Connection Reconfiguration message to the UE, and sends the carrier information to the UE.

Step 1909: The UE completes the reconfiguration of connection, and sends a Complete Connection Reconfiguration message to the HNB. . Step 1910: The HNB allocates the carrier, and notifies the HNB GW through an INITIAL CON- TEXT CONFIGURATION RESPONSE message. In this case, the HNB GW can send the downlinked data stream to the UE.

Step 1911: HNB GW notifies the core network control plan entity of carrier resource allocation information.

Step 1912: The core network control plan entity sends an Update Carrier Request message to the core network control plan entity, notifying, through the Update Carrier Request message, the control plan entity core network of information about the carrier resource that is allocated by HNB GW.

Step 1913: The core network control plan entity sends an Update Carrier Reply message to the core network control plan entity.

Through step 1912 and step 1913, if the data stream comes from the core network, the data stream can also be sent to the UE. MODE 12 The twelfth modality is different from the eleventh modality in that: in the twelfth modality, a core network control plan entity initiates payment for all

HNB GWs, HNBs, and macro NodeBs in a list of TAI; in the eleventh modality, however, the core network control plan entity initiates payment to an HNB GW for which the core network control plan entity initiates a notification. Figure 20 is a flow chart of a method for paying a UE and for the UE to initiate a service request according to a twelfth modality of the present invention, where the method can include the following steps: Step 2001: When HNB GW receives a downlink data stream sent over an external network, the HNB GW sends a message. arrival notification notification for the network control plan entity.

'HNB GW caches the downlink data stream routed by the external network, verifies a destination address of a packet of data in the data stream, and determines, according to a stored address table , a user ID, and an ID of the core network control plan entity where the UE is registered, a UE that needs to be paid, and the core network control plan entity where the UE is registered.

HNB GW loads, in a notification message sent to the core network control plan entity, a user ID indicating a user who needs to be paid; a special ID that indicates that locally routed data from EU arrivals can also be loaded.

Step 2002: The core network control plan entity initiates a payment message for all HNB GWs, HNBs, and NodeBs macro in the TAI list.

The core network control plan entity may also initiate a payment message to an HNB under the HNB GW first, and, if the HNB does not respond, initiate a payment message to other HNB GWs, HNBs, and macro NodeBs on the TAI list.

Paying can be initiated for a NodeB macro and another

HNB GW due to the arrival of downlink data from the core network. 'Step 2003: An HNB GW, an HNB or a NodeB macro that receives the payment message initiates the payment for an air interface'. If the UE that responds to the payment is located under the HNB of the HNB GW that caches the downlink data, see step 1905 to step 1913 for subsequent processes. If the user who responds to the payment is located under the NodeB macro or another HNB that is controlled by the HNB GW but did not have access by the UE last time, subsequent steps are performed. Step 2004: The UE under the NodeB macro responds to the payment, and sends a service request message to the core network control plan entity.

Step 2005: The core network control plan entity sends a notification message to HNB GW, where the notification message is used to notify HNB GW of a fact that the UE is unreachable in an area governed by HNB GW.

Step 2006: HNB GW ends a section with the UE, or deletes the context information from the UE.

The HNB GW can also end the session with the UE or delete the context information from the UE after waiting for a period of time. If the UE reconnects to the HNB GW within this time period, the section can continue, MODE 13 The thirteenth modality is different from the twelfth modality in that: in the thirteenth modality, after receiving a downlink data stream, a HNB GW does not notify a core network control plan entity but initiates 6 payments directly, the 12th modality, however, HNB GW receives a downlink data stream, and notifies the network control plan entity - cleo; the core network control plan entity initiates payment.

Figure 21 is a flow chart of a method for paying an UE. : for the UE to initiate a service request according to a thirteenth modality of the present invention, where the method can include the following steps: Step 2101: When a downlink data stream arrives, the HNB GW initiates payment to an HNB controlled by HNB GW.

If HNB GW stores a user's TAI list and a user's CSG list, HNB GW, according to the information, initiates payment to the HNB controlled by HNB GW.

When a downlink data stream arrives, the HNB GW will set it. caches the downlink data stream, HNB GW verifies a destination address of a data packet in the data stream, and determines, according to a locally stored address table and the user ID, a user to be paid.

Step 2102: The HNB that receives a payment message initiates payment to the HNB-controlled UE.

Step 2103: After receiving the payment, the UE responds to the payment, and initiates a payment response service request (SERVICE REQUEST) to the core network control plan entity.

Step 2104: The core network control plan entity sends an INITIAL CONTEXT CONFIGURATION message to the HNB GW, and notifies the HNB GW of stored carrier information from a core network control plan entity.

Step 2105: HNB GW stores the carrier information sent by the core network control plan entity, allocates a carrier, sends a CONTEXT CONFIGURATION | - HOME message to the HNB according to the carrier information received, and notifies the HNB of the allocated carrier.

Step 2106: The HNB sends a Radio Resource Reset message to the UE, and sends the carrier information to the UE.

Step 2107: The UE completes the reconfiguration of connection, and sends a Complete Radio Resource Reconfiguration message to, the HNB. . Step 2108: The HNB allocates the carrier, and notifies the HNB GW through an INITIAL CONTEXT CONFIGURATION RESPONSE message.

In this case, the downlink data stream cached in the HNB GW can be sent to the UE.

Step 2109: HNB GW notifies the control plan entity of the carrier's resource allocation information core. through an INITIAL CONTEXT CONFIGURATION RESPONSE message. 'Step 2110: The core network control plan entity sends an Update Carrier Request message to the core network control plan entity, notifying the core network control plan entity of information about the resource carrier that is allocated by HNB GW.

Step 2111: The core network control plan entity returns an Update Carrier Response message to the core network control plan entity.

Through step 2110 and step 2111, if a data stream comes from the core network, the data stream can also be sent to the UE.

MODE 14 The fourteenth modality is different from the thirteenth modality in that a HNB receives a downlink data stream and initiates payment directly.

In the thirteenth modality, however, a HNB GW receives a downlink data stream and initiates the payment directly. Figure 22 is a flowchart of a method for paying a UE and for the UE to initiate a service request accordingly. with a fourteenth embodiment of the present invention, where the method may include the following

following steps: Step 2201: The HNB starts paying. a Downlink data flow on a home network arrives at. HNB; the HNB caches the data stream, verifies a destination address for a data packet, and determines, according to a locally stored address table and the user ID, a UE to be paid for.

Step 2202: After receiving the payment, the UE responds to the payment, and initiates a payment response service request (SERVICE REQUEST) to the core network control plan entity. . Step 2203: The core network control plan entity sends an INITIAL CONTEXT CONFIGURATION message to the 'HNB GW, and notifies the HNB GW of stored carrier information from a core network control plan entity.

Step 2204: HNB GW stores the carrier information for the core network control plan entity, allocates a carrier, sends an INITIAL CONTEXT CONFIGURATION message to the HNB according to the carrier information received, and notifies the HNB the allocated carrier.

Step 2205: The HNB sends a Radio Resource Reset message to the UE, and sends the carrier information to the UE.

Step 2206: The UE completes the connection reset, and resets a connection reset response message to the HNB.

Step 2207: The HNB allocates the carrier, and notifies the HNB GW through an INITIAL CONTEXT CONFIGURATION RESPONSE message.

In this case, the downlink data stream cached in the HNBGW is sent to the EU.

Step 2208: HNB GW notifies the core network control plan entity of carrier resource allocation information.

Step 2209: The core network control plan entity: sends an Update Carrier Request message to the core network user plan entity, notifying the plan entity. core network user of information about the carrier resource that is allocated by the HNB GW. Step 2210: The core network user plan entity returns an Update Carrier Response message. Through step 2209 and step 2210, if a data stream comes from the core network, the data stream can also be sent to the

HUH . MODALITY 15 The fifteenth modality is different from the fourteenth mode. due to the fact that: In the fifteenth modality, after receiving a downlink data stream, a HNB notifies a HNB GW; HNB GW starts paying. Optionally, HNB GW can continue to notify a kernel network control plan entity, and the kernel network control plan entity initiates payment. In the fourteenth modality, however, the HNB receives a downlink data stream and starts the payment directly. Figure 23 is a flow chart of a method for paying a UE and for the UE to initiate a service request according to a fifteenth modality of the present invention, where the method can include the following steps: Step 2301: A flow of local downlink data on the home network — arrives at the HNB; the HNB caches the data stream, checks a destination address for a data packet in the data stream, determines, according to a locally stored address table and the user ID, a UE to be paid for, and sends a downlink data notification message to the HNB GW to notify the HNB GW of a fact that a downlink data flow arrives at the HNB, where the downlink data notification message carries a user ID. HNB GW initiates payment to HNB,

Optionally, HNB GW can notify the core network control plan entity of the arrival of local downlink data on the home network, where the notification carries a user ID; the entity of. core network control plan initiates payment to HNB GW; and aHNBGWinitialpayment for HNB.

Step 2302: The HNB that receives a payment message initiates payment to the UE controlled by the HNB.

Step 2303: After receiving the payment, the UE responds to the payment, and initiates a payment response service request (SERVICE REQUEST) TO the control plan entity. core network.

Step 2304: The core network control plan entity # sends an INITIAL CONTEXT CONFIGURATION message to HNB GW, and notifies HNB GW of stored carrier information from a core network control plan entity.

Step 2305: HNB GW stores the carrier information for the core network control plan entity, allocates a carrier, and sends an INITIAL CONTEXT CONFIGURATION message to the HNB according to the carrier information received, and notifies the carrier. Carrier HNB allocated.

Step 2306: The HNB sends a Radio Resource Reset message to the UE, and sends the carrier information to the UE.

Step 2307: The UE completes the connection reset, and returns a Connection Reset Response message to the HNEB.

Step 2308: The HNB allocates the carrier, and notifies the HNB GW through an INITIAL CONTEXT CONFIGURATION RESPONSE message.

In this case, the downlink data stream cached in the HNB GW is sent to the UE.

Step 2309: HNB GW notifies the core network control plan entity of carrier resource allocation information. 'Step 2310: The core network control plan entity sends an Update Carrier Request message to the entity. core network control plan entity, notifying the core network control plan entity of information about the carrier resource that is allocated by HNB GW.

Step 2311: The core network control plan entity returns an Update Carrier Response message.

Through step 2310 and step 2311, if a data stream comes from the core network, the data stream can also be sent to the UE.

Above detailed is the payment caused by local routing and a data transmission process after the UE is paid. It should be noted that before starting the payment, the HNB GW needs to configure a user | lP address, a user ID , a user's TAI list, and a user's CSG list.

A specific configuration method includes: When routing data locally, the HNB GW needs to perform a NAT.

In this case, a mapping relationship between the user's address and the HNB GW address and port are recorded. When a connection between the core network control plan entity and the HNB GW is established in the control plan, the control entity core network control plan sends a message to HNB GW, where the message can be an INITIAL CONTEXT CONFIGURATION message or a DOVWNLINK NAS TRANSPORT message.

The message includes a (user D, and optionally, may also include a user's Tracking Area Identity list (TAI list) and / or a user's Closed Subscriber Group list (CSG list).

HNB GW stores the information, and sends an INITIAL CONTEXT CONFIGURATION RESPONSE message to the core network control plan entity.

When the core network control plan entity has

for the release of a connection, the HNB GW stores the information about the UE. Or when the core network control plan entity says to release a connection, HNB GW maintains a self-connection. nalization with the core network control plan entity, and releases only one connection between the HNB GW and the HNB.

The preceding method for configuring a user | P address, a user ID, a user's TAI list, and a user's CSG list by HNB GW is also applicable to the configuration of user context information by HNB . When the HNB activates a local route, the core network control plan entity sends information such as one. User ID for the HNB GW, and the HNB GW still sends the information to the HNB. . The user ID can be a permanent ID (for example, an MSI) or a temporary ID (for example, an S-TMSI or a GUTI). If what is notified by the core network control plan entity to the HNB GW is an IMSI, this parameter can be sent only when a user control plan logical connectivity request is built for the first time. If what is notified to the HNB GW is an S-TMS! I core network control plan entity or a GUTI, this parameter can be loaded into the control plan logical connectivity request each time, or this parameter can be loaded into the control plan's logical connectivity request only when the parameter is changed. In a payment process, the following two exceptional cases exist: The first exceptional case is: If the HNB GW receives data from downlink whose destination address does not exist in the address table or does not have corresponding context information (for example, a user ID and / or core network control plan entity ID where the UE is registered) from the UE, the data is discarded.

The second exceptional case is: When the core network control plan entity receives a downlink data notification sent by the HNB, if a corresponding user ID is not found] or indicating that a corresponding user's local route is not activate it. the core network control plan entity does not send a: payment message, and notifies HNB GW of a situation that a corresponding payment is invalid, HNB GW discards downlink data and deletes the context information that correspond to the UE.

As seen from the above, the payment method provided in the modalities of the present invention can optimize the payment messages from the HNB and the macro NodeB in a scenario where a NodeB supports local routing, and improve network efficiency.

A A modality of the present invention also provides a device for local routing, where the device is applied in the architecture of the system in a residential access mode.

As shown in figure 24, one embodiment of the present invention provides a device for configuring path for local routing, where the device includes: a first address allocation unit 2401, configured to allocate a home network address to a HUH; a second address allocation unit 2402, configured to allocate an external network address to the UE; and a first carrier allocation unit 2403, configured to allocate a downlink carrier resource to UE.

The device can also include: a second carrier allocation unit configured to allocate an uplink carrier resource to UE.

The device includes an HNB, HNB GW or MME from a core network.

As shown in figure 25, one embodiment of the present invention provides an apparatus for local routing, where the apparatus includes: a judgment unit 2501, configured to judge a destination node of a data packet sent by a UE; and a sending unit 2502, configured for: if the judgment unit 2501 determines that the destination node of the data packet is' located on a home network, send the data package to the destination node on the home network; if judgment unit 2501 determines. Since the destination node of the data packet is located on an external network, the data packet will be sent to the destination node on the external network.

The device includes an HNB, an HNB GW or a residential GW.

One embodiment of the present invention provides a system for local routing, where the system includes: a control node for local routing, configured for. configure a data transport path for a UE, so that a routing node for local routing performs local routing is the UE.

The local routing of the UE includes: judging, by the routing node for local routing, a destination node of a data packet sent by the UE; if the destination node of the data packet is located on a home network, send the data packet to the destination node on the home network; if the destination node of the data packet is located on an external network, send the data packet to the destination node on the external network.

The control node for local routing includes an HNB, an HNB GW, or an MME of a core network.

The routing node for local routing includes an HNB, an HNB GW or a residential GW. If a data transport path that the control node for local routing sets for the UE is released and the HNB or HNB GW receives data downlink, the HNB or HNB GW is additionally configured to initiate payment according to a destination address in the downlink data.

Figure 26 is a schematic diagram of a system according to a sixteenth embodiment of the present invention.

In the system provided in this embodiment of the present invention, an operation performed by each device is the same as an operation in the methods provided in the embodiments of the present invention.

For details, see the description of the methods provided in the modalities of the present invention, and no further description will be provided here. . Finally, it should be noted that the terms used here as "first" and "second" are used only to differentiate an entity or operation from another entity or operation, and do not require or imply that any relationship or sequence should exist between these entities or operations.

In addition, the terms "include", "comprise", or any other variants thereof are intended to cover non-exclusive inclusions, so that a process, a method, an article, or a device. that includes a series of elements includes not only these elements but also other elements not specified or elements inherent in the process, method, article, or device.

If there are no further limitations, in addition to an element defined by the statement "includes one ..." or "comprises one ...", other similar elements can also be included in a process, a method, an article, or a device that includes the element.

Through the description of the above modalities, it is understandable for those skilled in the art that the present invention can be implemented by software in addition to a necessary hardware platform or by hardware only.

However, in most cases, the former is preferred.

Based on such an understanding, all or part of the contributions of the technical solutions of the present invention to the prior art can be incorporated by a software product.

The software product can be stored on a storage medium, for example, a Read Only Memory / Random Access Memory (ROM / RAM), a magnetic disk or a Compact Disc Read Only Memory (CD-RM), and incorporates various instructions for instructing a computer device, for example, a personal computer, a server, or a network device, to perform a method described in each embodiment of the present invention or in some parts of an embodiment of the present invention, Detailed above are the modalities of the present invention.

Although the principle and implementation of the present invention are described with reference to exemplary modalities, the modalities are only intended to help understand the methods and a basic idea of. present invention.

In addition, with respect to the implementation and application of the present invention, modifications and variations can be made by persons skilled in the art according to the idea of the present invention.

Therefore, the specification should not be considered as limitations of the present invention.

Claims (18)

CLAIMS '1. Method for local routing characterized by the fact that it comprises the steps of:. establish a data transport path for a User Equipment (UE); determining a destination node for a data packet sent by the UE; and sending the data packet to the destination node located on the home network, sending the data packet to the destination node located on the external network via a data transport path if the node. destination of the data packet is located on an external network. 2. Method, according to claim 1, characterized by the 'fact that the establishment of a data transport path for a User Equipment (UE) comprises: establishing, through a control node for local routing, the path data transport to the UE, where the control node for local routing comprises a Residential NodeB (HNB), a Residential NodeB Port (HNB GW) or a Mobility Management Entity (MME) of a network core; determining a destination node for a data packet sent by the UE, comprises: determining, by a routing node for local routing, the destination node of the data packet sent by the UE; and sending the data packet to the destination node located on the home network via the data transport path if the destination node of the data package is located on the home network, or sending the data packet to the destination node located on the external network via the data transport path if the destination node of the data packet is located on the external network comprises: sending, through the routing node to the local routing, the data package to the destination node located on the home network via the data transport path if the destination node of the data packet dos is located on the home network, or send, through the routing node to the local routing, the data packet to the destination node located on the external network via the data transport path if the node. destination of the data packet is located on the external network; wherein the routing node for local routing comprises an HNB, an HNB GW or a residential GW. 3. Method, according to claim 2, characterized by the fact that the stage of preparing, through the control node for local routing, the data transport path to the UE, comprises: establishing, through the control node for the local routing, o. data transport path to the UE activating a new connection - Packet Data Network (PDN); or,. control, through the control node for local routing, the routing node for local routing to download the data packet, when the data packet is loaded on an original PDN connection. 4. Method, according to claim 3, characterized by the fact that if the data transport path is established for the UE by activating a new PDN connection, the sending, through the routing node to the local routing, of the packet data for the destination node located on the external network, comprises the steps of: sending, through the residential GW, the data packet to a broadband access device through the residential network; and send, through the broadband access device, the data packet to the destination node located on the external network through the external network 5. Method, according to claim 4, characterized by the fact that by establishing the control node for local routing, a data transport path to the UE activating a new PDN connection comprises the steps of: allocating, through the HNB , an external network address and a home network address for the UE. 6. Method, according to claim 3, characterized by the fact that if a data transport path is established for the 'UE activating a new PDN connection, the sending, via the routing node to the local routing, the data packet to the destination node located. on the external network, it comprises the steps of: sending, via HNB or residential GW, the data package to HNB GW through a security tunnel that is established in advance; and send, through HNB GW, the data packet to the destination node located on the external network through the external network. 7. Method, according to claim 6, characterized by: the fact that establish by the control node for local routing o. data transport path to the UE activating a new connection. PDN comprises the step of: allocating, through the HNB GW, an external network address for the UE, and allocating, through the HNB, a home network address for the UE. 8. Method, according to claim 3, characterized by the fact that if a data transport path is established for the UE activating a new PDN connection, the sending, through the routing node to the local routing, of the packet of data for the destination node located on the external network, comprises the steps of: sending, through the HNB or residential GW, the data packet to HNB GW through an uplink carrier resource; and send, by HNB GW, the data packet to the destination node located on the external network through the external network. 9. Method, according to claim 8, characterized by the fact that establishing, through the control node for local routing, the data transport path to the UE activating a new PDN connection comprises the step of: allocating, by HNB GW, the uplink bearer resource for the UE, and allocate, through the HNB, a downlink bearer resource for the UE to receive the downlink data sent to the UE. 10. Method according to claim 2, characterized by o the fact that it still comprises: 'obtaining, by means of the routing node for local routing, an IP address from the source of the data packet; . where the source IP address is obtained when the UE activates the PDN connection, either a private address or a local connection address allocated by the HNB. 11. Method, according to claim 3, characterized by the fact that if a data transport path is established for the UE by downloading the data packet into the routing node for local routing, the method also comprises: 'an INITIAL CONTEXT CONFIGURATION message z is sent to the HNB, where the message carries an indication that in-. hint if the UE is allowed to access the home network; and if the UE is allowed to access the home network, the HNB sends the data packet sent by the UE to the destination node located on the home network. 12. Method, according to claim 2, characterized by the fact that the method still comprises: if the data transport path that the control node for local routing establishes for the UE is released and the HNB or HNB GW receives the data from the downlink, initiate, through the HNB or HNB GW, the payment according to a destination address of the downlink data. 13. Method, according to claim 2, characterized by the fact that if the data transport path that the control node for local routing establishes for the UE is released, the method still comprises the step of: notifying, by HNB GW, a core network control plan entity that the downlink data arrives from, to make the core network control plan entity initiate payment according to the context information of the UE. 14. Method, according to claim 2, characterized by the fact that if the data transport path that the control node S / 6 for the local routing establishes for the UE to be released, the method still comprises the step of: o notify, the HNB GW, a BR core network control plan entity that the downlink data arrives, to make the entity of core network control plan to initiate payment for all HNB GWs, HNBs, and macro NodeBs in a Tracking Area Identity (TAI) list. 15. Method, according to claim 14, characterized by the fact that it still comprises: if the UE under one of the macro NodeBs responds to the payment,. the HNB GW ends a UE session under the NodeB macro or clears the UE context information or continues the session after the UE reconnects to. HMB GW, 16. Method according to claim 12, characterized by the fact that it still comprises: if the HNB receives the downlink data, the HNB notifies the HNB GW that the downlink data arrives, so that the HNB GW initiates the payment or the HNB GW triggers an entity from the core network control plan to initiate payment. 17. Apparatus for local routing characterized by the fact that it comprises: a determination unit configured to determine a destination node of a data packet sent by a User Equipment (UE); and a sending unit, configured to send the data packet to the destination node located on the home network if the determining unit determines that the data packet's destination node is located on an external network, or sends the packet data to the destination node located on the external network if the unit of determination determines which destination node of the data packet is located on an external network. 18. System for local routing characterized by the fact that ERREI Sata MONTHS Es a A 1/23: 101 CONFIGURING A DATA TRANSPORTATION ROUTE TO AN EU JUDGING A DESTINATION NODE FROM A DATA PACKAGE SENT FROM THE EU. 702 IF THE DATA PACKAGE DESTINATION NODE IS LOCATED IN A RESIDENTIAL NETWORK, SEND THE DATA PACKAGE TO 03 DESTINATION NODE IN THE RESIDENTIAL NETWORK; IF THE DATA PACKAGE DESTINATION NODE IS LOCATED IN AN EXTERNAL NETWORK, SEND THE PACKAGE OF DATA FOR THE DESTINATION NODE IN THE EXTERNAL NETWORK FIG. 1