Home base station location information

Home base station location information technology field

[0001] The embodiments herein generally relate to location information nodes and methods in location information nodes. More specifically, the embodiments herein relate to providing the policy and charging rules function (PCRF) with location information associated with the home base station.

Background technique

[0002] In a typical cellular network (also referred to as a wireless communication system), user equipment (UE) communicates to one or more core networks (CN) via a radio access network (RAN).

[0003] User equipment is a device that can access services provided by the operator's core network and services outside the operator's network, and the operator's radio access network and core network provide access to services outside the operator's network. The user equipment may be, for example, a communication device, such as a mobile phone, a cellular phone, a smart phone, a tablet computer with wireless capabilities, or a laptop computer. The user equipment may be a portable, bagged, handheld, computer or vehicle-mounted mobile device, capable of transmitting voice and/or data to another entity (such as another mobile station or server) via a radio access network. In some figures, user equipment will be referred to as UE.

[0004] In a cellular network, user equipment can communicate wirelessly. It can be, for example, between two user equipment, between the user equipment and the program-controlled telephone, and/or between the user equipment and the server, via the radio access network included in the cellular network and possibly one or more cores. Network to communicate.

[0005] The radio access network covers a geographic area, which is divided into cell areas, where each cell area is served by a base station. In some radio access networks, base stations are also called radio base stations (RBS), evolved NodeB (eNB), NodeB, Node B, or base station. The user equipment can be in a cell or can be served by a base station. A cell is a geographic area in which a radio base station at a base station site provides radio coverage. In the local radio area, each cell is identified by an identity, and the identity is broadcast in the cell. The base station communicates with user equipment within the range of the base station through an air interface operating on radio frequencies. Cells can have different sizes and coverage, and some types of cells are femto cells, pico cells, urban cells, and micro cells-broadly speaking, increasing in size from femto cells (smallest) to micro cells (largest). A femto cell is a small cell base station, typically designed for use in a home or small business, and it provides improved cell coverage, capacity, and applications. Using the terminology of the Third Generation Partnership Project (3GPP), Home eNodeB (HeNB) is a long-term evolution (LTE) femto cell, and Home Node B (HNB) is a third generation (3G) femto cell. In the following, even if the term HeNB is used, this is equally applicable to HNB.

[0006] 3Gpp and Broadband Forum (BBF) are standardization organizations for mobile networks and fixed networks, respectively. There is an ongoing joint working group on Fixed Mobile Convergence (FMC) between these two organizations. FMC is a change in telecommunications. FMC will eventually eliminate the difference between fixed and mobile networks, using a combination of fixed broadband and local access wireless technologies to create seamless services to meet customer needs. The goal of FMC is to optimize the transmission of all data, voice and video communications to and between end users, regardless of their location or equipment, that is, a single device can be connected through wired and wireless networks, And switch between wired and wireless networks. Femto cells are an alternative way to realize the benefits of FMC.

[0007] In the case of femto, the HeNB may be located behind a network address translator (NAT). In this case, in order to provide quality of service (QoS) on femto services, NAT public internet protocol version 4 should be provided to PCRF

(IPv4) address and source User Datagram Protocol (UDP) port number. NAT can be described as the process of modifying the IP address information in the IPv4 header when passing through a service routing device. NAT allows IP networks to maintain public IP addresses separate from private IP addresses. PCRF is a node in the network, which is responsible for the policy rules in the network.

[0008] The IP address can be public or private. The public IP address is a globally unique number, which identifies a device on the Internet. Private IP addresses are typically assigned to devices on a local area network (LAN) and are not used outside the LAN. Private IP addresses are typically used in conjunction with routers. When using NAT, it is possible to have a private IP address on the local network, and use a single public IP address that will be used by devices on the local network when they access the Internet. UDP is a protocol that enables applications to send messages (ie, datagrams) to other hosts on the IP network without first establishing a dedicated transmission channel. UDP includes: source port number, destination port number, length and checksum. The source UDP port number identifies the sender's port and the port that should be considered for reply (if reply is required). The destination port number identifies the port of the recipient.

[0009] In the following, FIG. 1 shows a typical example of a network 100, in which the HeNB 101 is connected to the 3Gpp EPC 103 at the same time after NAT, where EPC is an abbreviation of Evolved Packet Core. In FIG. 1, the user equipment 104 is served by the HeNB 101. The HeNB 101 is connected to a mobility management entity/serving general packet radio service support node (MME/SGSN) 105. The MME/SGSN 105 is a control node, which uses different interfaces to work simultaneously with the radio access network and the core network. The interface between the MME 105 and the HeNB 101 is called S1-MME, and is responsible for using various types of control messages to manage the UE. The MME 105 is connected to the PCRF 107. The PCRF 107 is connected to the Broadband Policy and Charging Function (BPCF) 110. BPCF 110 connects to Broadband Remote Access Server (BRAS) 113, BRAS 113 routes services to and from broadband remote access equipment. The HeNB 101 is connected to a security gateway (SeGW) 115, and the SeGW 115 provides a secure communication link between the HeNB 101 and the core network. The SeGW 115 is connected to a packet data network gateway (PGW) 117. The Home Subscriber Server (HSS) 120 (which is connected to the MME 105) is a repository for subscriber profiles, device profiles, and status information. Even though Figure 1 illustrates the HeNB (which is an LTE femto cell), those skilled in the art will understand that this architecture can also be applied to 3G networks. In 3G networks, HNBs are used instead of HeNBs.

[0010] In Alternative A, as shown in FIG. 2a, the SeGW 115 may send the H(e)NB address information to the H(e)NB 101, that is, the public IP address and port number of the H(e)NB. Then, H(e)NB 101 can use S1 Application Protocol (S1AP) signaling to forward this information to MME/SGSN 105o S1AP is to provide signaling between the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and EPC Service agreement. Next, the MME/SGSN 105 forwards the H(e)NB address information to the PCRF 107 via the GPRS Tunneling Protocol (GTP) interface or PCRF interface. GPRS is short for General Packet Radio Service. The security issues with this alternative A have been identified. Transporting the IP address information of the H(e)NB on the S1AP may trigger security issues related to the incorrect information that the home base station may send.

[0011] In alternative B, see Fig. 2b, in the H(e)NB verification process, the SeGW 115 may send the public IP address of the H(e)NB to the authentication, authorization, and accounting (AAA) server of 3Gpp And UDP port number. The AAA server makes it possible to control which users are allowed to access which services, and the amount of resources they have used. Then, in the H(e)NB authentication process, the H(e)NB or MME/SGSN 105 can receive the address information from the AAA server. For Alternative B, at least two problems have been identified. One problem is that when H(e)NB GW is used, MME/SGSN 105 is not involved in the H(e)NB authentication process. Because the interface between H(e)NB GW and MME/SGSN 105 is S1AP, so For the H(e)NB GW, it is impossible to send the local address of the H(e)NB to the MME/SGSN 105 without affecting the S1AP protocol. The second problem is that any time after the S1 session is established, NAT remapping may be triggered. After NAT remapping, H(e)NB 101 may be assigned a new local IP address and/or a new UDP port number. Secret through the Internet

During the key exchange version 2 (IKEv2) process, SeGW 115 will be notified of this change. IKEv2 is used to establish a security association in the IPsec protocol stack. However, MME 105 does not know that the IP address of the HeNB has been updated.

Summary of the invention

[0012] Therefore, one purpose of the embodiments herein is to eliminate at least one of the above problems and to provide improved communication processing in a communication network.

[0013] According to the first aspect, this object is achieved by a method in a location information node, which is used to provide the PCRF with location information associated with the home base station. The location information node is dedicated to processing location information. The location information node is connected to the AAA server and MME/SGSNo. When the home base station establishes an IPSec tunnel with the SeGW, the location information node receives the location information from the AAA server. The location information includes at least one of the following: a local IP address and a port number associated with the identity of the home base station. The location information node uses the interface between MME/SGSN and PCRF to transmit location information to PCRF via MME/SGSN, or uses SI 1/S4 interface, S5/S8 interface and Gx/Gxx interface, via MME/SGSN and SGW/PGW Transmit location information to PCRF, or use the interface between the location information node and PCRF to directly transmit location information to PCRF.

[0014] According to the second aspect, this objective is achieved by a location information node, which is used to provide the PCRF with location information associated with the home base station. The location information node is suitable for exclusively processing location information. The location information node is suitable for connecting to AAA server and MME/SGSN. The location information node includes a receiver configured to: when the home base station establishes an IPSec tunnel with the SeGW, receive location information associated with the home base station from the AAA server. The location information includes at least one of the following: a local IP address and a port number associated with the identity of the home base station. The location information node includes a transmitter that is configured to use the interface between the MME/SGSN and the PCRF to transmit the received position information to the PCRF via the MME/SGSN, or use the S11/S4 interface, S5/S8 interface, and Gx The /Gxx interface transmits the received location information to the PCRF via the MME/SGSN and SGW/PGW, or uses the interface between the location information node and the PCRF to directly transmit the received location information to the PCRF.

[0015] Because the location information node includes the location information of the home base station, for example, the local IP address/port number of the H(e)NB, the location information of the home base station can be transmitted to PCRF. The location information node can be an independent node or an existing node. Some communication nodes (such as HSS, AAA server or PCRF) are co-located or part of existing communication nodes (such as HSS, AAA server or PCRF).

[0016] The embodiments herein provide many advantages, and a non-exhaustive example list of many advantages is as follows: The embodiments herein enable policy and charging control (PCC) to be implemented when a home base station is connected via a broadband network , And then can dynamically update the PCCo during NAT remapping

[0017] The embodiments herein also provide the advantage of avoiding affecting the S1AP protocol.

[0018] The embodiments herein provide the following advantages: Compared with the prior art, because S1AP is not used, it is a safe solution. When S1AP is not used, there are no security issues.

[0019] The embodiments herein provide better services to user equipment.

[0020] The embodiments herein are not limited to the above-mentioned features and advantages. After reading the following detailed description, those skilled in the art will recognize additional features and advantages.

Description of the drawings

[0021] This article will now be further described in more detail in the following detailed description by referring to the accompanying drawings illustrating the embodiments

The embodiment in Figure 1 is a schematic block diagram illustrating a NAT-passing HeNB connected to the 3GPP evolved packet core via a SeGW.

[0022] FIGS. 2a-b are schematic block diagrams illustrating a prior art embodiment of position information processing.

[0023] FIG. 3 is a schematic block diagram illustrating an embodiment of a communication network.

[0024] FIG. 4 is a signaling block diagram illustrating an embodiment of a method for SeGW reporting of location information.

[0025] Figures 5a-c are schematic block diagrams illustrating embodiments of the method.

[0026] FIG. 6 is a signaling diagram illustrating an embodiment using S11/S4, S5/S8, and Gx/Gxx (Alternative Solution A).

[0027] FIG. 7 is a signaling diagram illustrating an embodiment (Alternative B), in which location information is reported via a new interface between MME and PCRF.

[0028] FIG. 8 is a signaling diagram illustrating an embodiment (alternative C) in which location information is reported via a new interface between the location information node and the PCRF.

[0029] FIG. 9 is a flowchart illustrating an embodiment of a method in a location information node.

[0030] FIG. 10 is a schematic block diagram illustrating an embodiment of a location information node.

[0031] The drawings are not necessarily drawn to scale, and the size of certain features may have been exaggerated for reasons of clarity.

The focus is on explaining the principles of the embodiments in this article.

Detailed ways

[0032] The embodiments herein involve reporting the location information of the home base station, for example, the local IP address of the home eNB or HNB, to the PCRF when the user equipment is attached to the communication network via the home base station. The PCRF needs to know the location information of the home base station in order to find the strategy to be applied. The embodiments herein propose several alternatives to forward the local IP address/port number of the H(e)NB to the PCRF. A new logical location information node created in the architecture is proposed. The logical location information node includes location information, such as the local IP address and port number of the H(e)NB. The new logical location information node can be co-located with any existing 3GPP entity (for example, HSS or 3GPP AAA server, SeGW or PCRF), or any existing 3GPP entity (for example, HSS or 3GPP AAA server, SeGW or PCRF) )a part of. Depending on the actual deployment (whether co-located or non-co-located), the signaling messages to and from the location information node can vary. In the following text, it is assumed that it is a separate logical entity, and the signaling message in the figure is only an example.

[0033] FIG. 3 depicts a communication network 300 implementing the embodiments herein. In some embodiments, the communication network 300 may be applied to one or more radio access technologies, such as, for example, Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications (GSM) ) Or any other 3rd Generation Partnership Project (3GPP) radio access technology or any other radio access technology, such as for example WLAN_O

[0034] The communication network 300 is divided into three parts, the evolved packet system (EPS) 301, the access and network defined by BBF 303, and the customer premises network 305. The dotted line used in FIG. 3 is used to illustrate the division of these three parts. .

[0035] The customer premises network 305 includes a 3Gpp femto 307, and the 3GPP femto 307 is a home base station, such as HNB. If the network 300 is an LTE network, the home base station will be an H(e)NB. The 3Gpp Femto 307 serves at least one user equipment (UE) 370. User equipment can be any equipment (mobile or fixed) that can communicate on a radio channel in a communication network, such as but not limited to, for example, mobile phones, smart phones, sensors, meters, vehicles, household devices, medical devices, media Players, cameras, or any other types of consumer electronic products, such as but not limited to televisions, radios, lighting devices, tablet computers, laptop computers, or PCs. In some of these figures, the user equipment is referred to as UE. The customer premises network 305 also includes a BBF device 310. Both the 3GPP femto 307 and the BBF device 310 are connected to a residential gateway (RG) 313.

[0036] The access and network 303 defined by the BBF includes: an access node (AN) 315, and the AN may be, for example, a digital subscriber line access multiplexer (DSLAM) or an optical network terminal (ONT). DSLAM uses multiplexing technology to connect multiple customer digital subscriber line interfaces to high-speed data communication channels. The access and network 303 defined by BBF also includes BRAS/BNG 317, where BRAS is an abbreviation for broadband remote access server, and BNG is an abbreviation for broadband network. The access and network 303 defined by the BBF also includes the broadband policy and charging function (BPCF) 320.

[0037] The evolved packet system 301 includes: E-UTRAN 223a, UTRAN 223b, and GERAN 323c. The reference sign 323 is used to refer to any one of E-UTRAN, UTRAN and GERAN. E-UTRAN is the abbreviation for the evolved universal terrestrial radio access network, UTRAN is the abbreviation for the universal terrestrial radio access network, and GERAN is the abbreviation for the GSM EDGE radio access network. The E-UTRAN, UTRAN, and GERAN 323 are connected to the MME 325 via the SbMME interface. The MME 325 is connected to the HSS 326 via an S6a interface. The S10 interface illustrated at the MME 325 is an interface between a plurality of MMEs 325.

[0038] The MME 325 is connected to the location information node 327. The location information node 327 can also be described as a home base station location database, a control node for controlling, processing, or managing the location information of the H(e)NB location database or the HNB location database . The location information node 327 may be an independent logical entity in the EPC architecture, or it may be a co-located node among existing nodes in the network 300, or it may be at least a part of the existing nodes in the network 300.

[0039] The location information node 327 is connected to the AAA server 330. The AAA server 330 is connected to the SeGW 332, and the SeGW 332 is connected to the BRAS/BNG 317 in the access and network 303 defined by the BBF. The SeGW 332 is connected to the HNB GW 335, and the HNB GW 335 is connected to the mobile switching center (MSC) 337 via the lu-CS interface. The HNB GW 335 is connected to E-UTRAN, UTRAN, and GERAN 323 via the lu-PS interface. The HNB GW 335 is connected to the SGSN 340, and the SGSN 340 is connected to the serving gateway (SGW) 343 via the S4 interface. SGW 343 is connected to E-UTRAN, UTRAN, GERAN 323 via SbU interface.

[0040] Home base station 345 (for example, HeNB GW or H(e)NB) is located between MME 325 and SeGW 332. The SGW 343 is connected to the PDN gateway 348 via the S5 interface, and the PDN gateway 348 is connected to the PCRF 350 via the Gx interface. The Gxc interface between PCRF 350 and SGW 343 is only used for the S5 interface based on Proxy Mobile IP (PMIP). S9a is the interface between the access defined by PCRF 350 and BBF and the BPCF 320 in the network 303. S15 is the interface between PCRF 350 and HNB GW 335. The PCRF 350 is connected to the operator's IP service 353 via the Rx interface. Examples of operator IP services are IMS and PSS. The PDN gateway 348 is connected to the operator IP service 353 via the SGi interface.

[0041] In this document, location information, such as the local address information of H(e)NB, is referred to as IPv6 local address, IPv4 local address, or IPv4 local together with a port number (such as a UDP port number (if NAT is detected)). address. The local IP address of the home base station may be a public IP address or a private IP address. This IP address together with the port allows PCRF 350 to find the corresponding policy enforcement node in the fixed network. When the home base station 345 is behind the NAT, the home base station 345 will be assigned a private IP address. PCRF 350 cannot use the private IP address to find out the location of the H(e)NB. According to the embodiment herein, the NAT public IP address plus the UDP port number is passed to the PCRF 350. PCRF 350 can use this information to find out the location of the NAT and implement policies.

[0042] Reporting the location information to the location information node As illustrated in FIG. 4, the location information is reported from the SeGW 332 to the AAA server 330, for example, the local address of the H(e)NB. 4 also depicts that the AAA server 330 forwards location information (for example, the local address of the H(e)NB) to the location information node 327. The location information node 327 may be a logical function called a home base station location information database. That is, when the home base station 345 (for example, H(e)NB or HeNB) establishes an IPSec tunnel with SeGW 332, SeGW 332 should

When sending the identity of the home base station (for example, H(e)NB ID or HNB ID) and its local address information to the AAA server 330. When the location information has changed, such as the H(e)NB local address or HeNB local address, for example, during NAT remapping, the SeGW 332 also uses the same process as described above, using the home base station identifier (for example, H(e) NB ID or HeNB ID) and new/changed location information to update the AAA server 330. In the above case, the AAA server 330 forwards the home base station identification (for example, H(e)NB ID) and its local address to the location information node 327. The location information node 327 is a new logical node, for example, a home base station location information database. Therefore, the location information node 327 always has updated location information, for example, the local address of the H(e)NB or the local address of the HeNB, which is associated with the home base station identity, such as H(e)NB ID or HeNB ID, for example Global H(e)NB ID, Global HeNB ID> ECGL·CGL·H(e)NB name (FQDN) or HeNB name.

[0043] Providing location information to PCRF There are several alternative embodiments for how to provide location information (eg, H(e)NB address or HNB address) to PCRF 350. Some of these alternatives will now be described with reference to Figures 5a-c, 6, 7 and 8. Figures 5a-c provide an overview of the three different alternatives. Figures 6, 7 and 8 provide more detailed information for each of the three alternatives in Figures 5a-c. The messages described with respect to these figures are shown as examples only. The message sent in this process depends on whether the location information node 327 is an independent node or is contained in an existing node.

[0044] As mentioned above, Figures 5a-c provide an overview of three alternatives for providing location information to the PCRF. FIG. 5a illustrates Alternative A, in which the AAA server 330 transmits the location information associated with the home base station 345 to the location information node 327. The location information includes at least one of the following: a local IP address, a port number, and a home base station ID. The location information node 327 transmits location information to the MME/SGSN 325, 340. The MME/SGSN 325 transmits location information to the SGW/PGW 343 and 348 via the S11/S4 interface based on the GTP protocol and the S5/S8 interface based on the GTP or Proxy Mobile IPv6 (PMIP) protocol. S11 is the interface between MME 325 and SGW 343. S4 is the interface between SGSN 340 and SGW 343. S5/S8 is the interface between SGW 343 and PGW 348. SGW/PGW 343 and 348 transmit location information to PCRF 350 via Gx/Gxx interface. PMIP is a network-based mobility management protocol, and is used to establish a common access technology independent of the mobile core network and accommodate various access technologies (such as WiMAX, 3GPP, 3Gpp2 and WLAN-based access architecture) protocols .

[0045] FIG. 5b illustrates Alternative B, in which the AAA server 330 transmits location information to the location information node 327. The location information node 327 transmits location information to the MME/SGSN325>340. The MME/SGSN 325, 340 transmits location information to the PCRF 350.

[0046] FIG. 5c illustrates alternative 3 in which the AAA server 330 transmits location information to the location information node 327. The location information node 327 directly transmits location information to the PCRF 350.

[0047] In FIGS. 6, 7 and 8, which will be described below, H(e)NB is used as an example for the home base station 345, and H(e)NB location information is used as an example for location information. However, those skilled in the art will understand that the description is equally applicable to scenarios where the home base station is HENB and the location information is HENB location information.

[0048] Alternative A: Via S11/S4, S5/S8 and Gx/Gxx interfaces (see Figure 6) PCRF 350 transmits location information. The method includes the following steps, which can be performed in any suitable order other than the order described below. [0049] The following steps 601-608 involve session establishment, such as initial attachment or PDP context activation.

[0050] Step 601

UE 370 sends an attach request message to MME/SGSN 1 325. This is used to perform the UE session establishment process, such as

For example, E-UTRAN initial attach process or PDP context activation process. The attach request message may include: location information associated with the UE 370, such as, for example, the cell ID.

[0051] Step 602 During the UE session establishment process, such as the E-UTRAN initial attachment process or PDP context activation, the MME/SGSN 325, 340 uses the UE location information (eg, cell ID) to retrieve H( e) The local address of NB. [0052] The location information node 327 creates an association between the H(e)NB 345 and the MME/SGSN 325, 340, and stores the MME/SGSN IDo in a database included in a storage device or a memory unit. [0053] Step 603 The location information node 327 transmits the local address of the H(e)NB to the MME/SGSN 325, 340.

[0054] Step 604 Next, the MME/SGSN 325, 340 forward the H(e)NB local address information to the SGW/PGW 343, 348.

[0055] Step 605 forwards the local address information of the H(e)NB to the PCRF 350 from the SGW/PGW 343 and 348.

[0056] Step 606

The PCRF 350 transmits a response message to the SGW/PGW 343, 348, the response message confirming that the PCRF 350 has received the local address information of the H(e)NB.

[0057] Step 607

The SGW/PGW 343, 348 forwards the response message to the MME/SGSN 1 325, 340.

[0058] Step 608

The MME/SGSN 1 325, 340 transmits an attach accept message to the UE 370, and the attach accept message is a response to the request message transmitted in step 601. Therefore, the UE 470 knows that the session is established.

[0059] The following steps 609-614 involve the change of location information due to, for example, NAT remapping. NAT remapping triggers the update of the local address of the H(e)NB from the location information node 327 to the MME/SGSN 325,340.

[0060] Step 609 When the location information node 327 receives the updated or changed H(e)NB local address, for example, during NAT remapping, it searches its storage device/memory to know whether there is a connection with the H(e)NB. ) The MME/SGSN 1 325, 340 associated with the NB 345, for the port (6) 345, the local address of the H(e)NB 345 has been updated or changed. If the associated MME/SGSN 325,340 is found in step 609, the location information node 327 will update the MME/SGSN 325, 340.

[0061] Step 610

The MME/SGSN 1 325,340 transmits a response message to the location information node 327 to confirm that the updated information in step 609 is received.

[0062] Step 611

The MME/SGSN 1 325, 340 transmits the updated H(e) NB local address to the SGW/PGW 343, 348 via the S11/S4 and S5/S8 interfaces.

[0063] Step 612

The SGW 343 and 348 forward the updated H(e)NB local address to the PCRF 350 via the Gx/Gxx interface.

[0064] Step 613

The PCRF 350 transmits a response message to the SGW/PGW 343, 348 to confirm receipt of the updated information in step 612

interest.

[0065] Step 614

SGW/PGW 343 and 348 forward the response message to MME/SGSN 1 325.

[0066] The following steps 615-623 involve mobility procedures, for example, Tracking Area Update (TAU). TAU is a process initiated by UE 370 to update its registration status with the network. Some reasons for initiating the TAU process may be that the UE 370 has moved into a new tracking area (TA), some UE-specific parameters have been changed, and the TAU process can be initiated periodically. This may be due to errors, etc. After the recovery.

[0067] Step 615

The UE 370 transmits a TAU request message to the MME/SGSN 2 325, 340.

[0068] Step 616 performs context transfer between MME/SGSN 2 325, 340 and MME/SGSN 1 325, 340. Before the mobility procedure, UE 370 is served by MME/SGSN 1. After the mobility procedure, UE 370 is served by MME/SGSN 2. [0069] Step 617 During the mobility process, when the MME/SGSN 325, 340 detects that the UE location (for example, the current cell (ECGI/CGI)) has changed, the MME/SGSN 325, 340 will query the location information node 327 to obtain updated information. H(e)NB local address. [0070] Step 618: The location information node 327 transmits the updated H(e)NB local address to the inquiring MME/SGSN 2 325, 340.

[0071] Step 619

The MME/SGSN 2 325, 340 reports the changed H(e)NB local address to the SGW/PGW 343, 348.

[0072] Step 620

The SGW/PGW 343, 348 forwards the changed H(e)NB local address to the PCRF 350.

[0073] Step 621

The PCRF 350 transmits a response message to the SGW/PGW 343, 348 to confirm that the updated information in step 620 is received.

[0074] Step 622

SGW/PGW 343 and 348 forward the response message to MME/SGSN 2.

[0075] Step 623

The MME/SGSN 2 transmits a TAU acceptance message to the UE.

[0076] For the scenario where the last UE session associated with the same H(e)NB is released, the above process is also valid, and the MME/SGSN 325,340 can notify the location information node 327 to remove the home base station 345 and MME/ Association between SGSN 325 and 340.

[0077] Alternative B: Via a new interface between MME and PCRF (see Figure 7). The difference between alternatives B and A is that in alternative B, MME 325 directly sends H( e) NB address information. Alternative B is illustrated in Figure 7. In Figure 7, the H(e)NB local address is reported via the new interface between MME 3325 and PCRF 350. Compared with alternative A, the benefit of this alternative B is that it reduces the extra signaling used to report the changed H(e)NB local address on S5/S8. The method includes the following steps, which can be performed in any suitable order other than the order described below.

[0078] The following steps 701-706 involve session establishment, such as initial attachment or PDP context activation.

[0079] Step 701

UE 370 sends an attach request message to MME/SGSN 1 325. This is to perform a UE session establishment procedure, such as, for example, an E-UTRAN initial attach procedure or a PDP context activation procedure. The attach request message may include: location information associated with the UE 370, such as, for example, the cell ID. [0080] Step 702 During the UE session establishment process, such as the E-UTRAN initial attach process or PDP context activation, the MME/SGSN 325, 340 The UE location information (eg, cell ID) is used to retrieve the H(e)NB local address from the location information node 327. The location information node 327 creates an association between the H(e)NB 345 and the MME/SGSN 325, 340, and stores the MME/SGSN ID in a database included in a storage device or a memory unit. [0081] Step 703: The location information node 327 sends The MME/SGSN 325, 340 transmits the H(e)NB local address.

[0082] Step 704 Next, the MME/SGSN 325 and 340 directly transmit the H(e)NB local address information to the PCRF 350.

[0083] Step 705

The PCRF 350 transmits a response message to the MME/SGSN 325, 340, and the response message confirms that the PCRF 350 has received the local address information of the H(e)NB.

[0084] Step 706

The MME/SGSN 1 325, 340 transmits an attach accept message to the UE 370, and the attach accept message is a response to the request message transmitted in step 701. Therefore, the UE 370 knows that the session is established.

[0085] The following steps 707-710 involve changes in location information due to, for example, NAT remapping. NAT remapping triggers the update of the H(e)NB local address from the location information node 327 to the MME/SGSN 325,340.

[0086] Step 707 When the location information node 327 receives the updated or changed H(e)NB local address, for example, in NAT remapping, it searches its storage device/memory to know whether there is a connection with the H(e)NB 345. The associated MME/SGSN 1 325, 340, for the H(e)NB 345, the local address of the H(e)NB 345 has been updated or changed. If the associated MME/SGSN 325, 340 is found, the location information node 327 will update the MME/SGSN 1 325, 340 by transmitting the updated H(e)NB local address to the MME/SGSN 1 325, 340.

[0087] Step 708

The MME/SGSN 1 325, 340 transmits a response message to the location information node 327 to confirm that the updated information in step 707 is received.

[0088] Step 709

The MME/SGSN 1 325, 340 directly transmits the updated H(e)NB local address to the PCRF 350.

[0089] Step 710

The PCRF 350 transmits a response message to the MME/SGSN 1 325, 340 to confirm that the updated information in step 709 is received.

[0090] The following steps 711-717 involve mobility procedures, for example, Tracking Area Update (TAU). TAU is a process initiated by UE 370 to update its registration status with the network. Some reasons for initiating the TAU procedure may be that the UE 370 has moved into a new tracking area (TA), some UE-specific parameters have changed, and the TAU procedure may be initiated periodically. This may be due to the fact that an error has been performed after an error has occurred. Recovery and so on.

[0091] Step 711

The UE 370 transmits a TAU request message to the MME/SGSN 2 325, 340.

[0092] Step 712 performs context transfer between MME/SGSN 2 325, 340 and MME/SGSN 1 325, 340. Before the mobility procedure, UE 370 is served by MME/SGSN 1. After the mobility procedure, UE 370 is served by MME/SGSN 2. [0093] Step 713 During the mobility process, when the MME/SGSN 325, 340 detects that the UE location (such as the current cell (ECGI/CGI)) has changed, the MME/SGSN 325, 340 will query the location information node 327 to obtain updated information. H(e)NB local address. [0094] Step 714: The location information node 327 transmits the updated H(e)NB local address to the inquiring MME/SGSN 2 325, 340.

[0095] Step 715

The MME/SGSN 2 325, 340 reports the changed H(e)NB local address to the PCRF 350.

[0096] Step 716

The PCRF 350 transmits a response message to the MME/SGSN 2 325, 340 to confirm receipt of the updated information in step 715.

[0097] Step 717

The MME/SGSN 2 325, 340 transmits a TAU acceptance message to the UE.

[0098] Alternative C: New interface between location information node and PCRF (see Fig. 8) Fig. 8 illustrates alternative 3 In Fig. 8, in UE session establishment, such as E-UTRAN initial attachment or PDP context When activated, the location information is directly sent to the PCRF 350 during the IPYAN session establishment process. The method includes the following steps, which can be performed in any suitable order other than the order described below.

[0099] The following steps 801-806 involve session establishment, such as initial attachment or PDP context activation.

[0100] Step 801

UE 370 sends an attach request message to MME/SGSN 1 325. This is to perform a UE session establishment procedure, such as, for example, an E-UTRAN initial attach procedure or a PDP context activation procedure. The attach request message may include: location information associated with the UE 370, such as, for example, a cell ID. [0101] Step 802

The MME/SGSN 1 325, 340 transmits the UE location information associated with the UE 370 to the PCRF 350 via the SGW/PGW 343, 348. The UE location information may be, for example, (E)CGI, cell ID.

[0102] Step 803

The PCRF 350 sends a response back to the MME/SGSN 1 325, 340 via the SGW/PGW 343, 348 to confirm that the UE location information in step 802 is received.

[0103] Step 804

The PCRF 350 uses the received UE location information (eg, E(CGI), cell ID) to retrieve the H(e)NB local address from the location information node 327 (eg, H(e)NB location database) via a new interface.

[0104] Step 805: The location information node 327 receives the request for the H(e)NB local address from the PCRF 350, creates an association between the H(e)NB 345 and the PCRF 350, and the PCRF 350 stores the PCRF ID in its In the database in memory. The location information node 327 transmits the H(e)NB local address to the PCRF 350.

[0105] Step 806

Π/page 15

The MME/SGSN_1 325 and 340 transmit an attach accept message to the UE 370, and the attach accept message is a response to the request message transmitted in step 701. Therefore, the UE 370 knows that the session is established.

[0106] The following steps 807-808 involve changes in location information due to, for example, NAT remapping. NAT remapping triggers the update of the H(e)NB local address from the location information node 327 to the MME/SGSN 325,340.

[0107] Step 807 When the location information node 327 receives the updated or changed H(e)NB local address, for example, during NAT remapping, it searches its storage device to find the associated PCRF 350θ. If it finds the associated PCRF 350, the location information node 327 will update the PCRF 350 with the updated H(e)NB local address information.

[0108] Step 808

The PCRF 350 transmits a response message to the location information node 327 to confirm that the updated information in step 807 is received.

[0109] If the last IPYAN session is associated with the same H(e)NB, the PCRF 350 may notify the location information node 327 to remove the association between the H(e)NB 345 and the PCRF 350.

[0110] The following steps 809-815 involve mobility procedures, for example, Tracking Area Update (TAU).

[0111] Step 809

The UE 370 transmits a TAU request message to the MME/SGSN 2 325, 340.

[0112] Step 810 performs context transfer between MME/SGSN 2 325, 340 and MME/SGSN 1 325, 340. Before the mobility procedure, UE 370 is served by MME/SGSN 1 325,340. After the mobility procedure, UE 370 is served by MME/SGSN 2 325, 340.

[0113] Step 811 During the mobility procedure, such as the TAU procedure, when UE370 moves from one H(e)NB to another H(e)NB, MME/SGSN 2 325, 340 via SGW/PGW343>348 Report the changed UE location information to the PCRF 350, such as ECGI/CGI changes. The MME/SGSN 2 325, 340 also indicates to the PCRF 350 whether the UE 370 can be accessed from the H(e)NB.

[0114] The aforementioned ECGI is an abbreviation for the E-UTRAN cell global identifier, and it is used to identify a cell globally. ECGI is constructed from the PLMN identity to which the cell belongs and the cell identity (CI) of the cell. The included PLMN is the PLMN given by the first PLMN entry in SIB1. The eNB identifier (eNB ID) is used to identify the eNB in the PLMN. The eNB ID is included in the CI of its cell. The global eNB ID is used to identify the eNB globally. The global eNB ID is constructed from the PLMN identity to which the eNB belongs and the eNB ID. MCC and MNC are similarly included in the E-UTRAN Cell Global Identifier (ECGI). The global eNB ID of the RN is the same as its serving DeNB. The Tracking Area Identity (TAI) is used to identify the tracking area. The TAI is constructed from the PLMN identity to which the tracking area belongs and the TAC (Tracking Area Code) of the tracking area. The CSG ID (CSG ID) is used to identify the CSG in the PLMN.

[0115] Step 812

The PCRF 350 sends a response message to the MME/SGSN 2 325, 340 to confirm receipt of the updated information in step 811.

[0116] Step 813 During the mobility procedure, such as the TAU procedure, when the PCRF 350 detects that the UE location (for example, the current cell information (ECGI/CGI)) has changed, the PCRF 350 will query the location information node 327 to obtain Corresponding H(e)NB book

Address.

[0117] Step 814: The location information node 327 transmits the corresponding H(e)NB local address to the PCRF 350.

[0118] Step 815

The MME/SGSN 2 325, 340 transmits a TAU acceptance message to the UE 370.

[0119] The above method will now be described from the perspective of the location information node 327. FIG. 9 is a flowchart describing a method in the location information node 327 for providing the PCRF 350 with location information associated with the home base station 345. The location information node 327 is dedicated to processing location information when the user equipment 370 is attached to the communication network 300 via the home base station 345. The location information node 327 is connected to the AAA server 330 and the MME/SGSN 325, 340. The home base station 345 may be a home evolved node B (HeNB) or a home node B (HNB)_OIn some embodiments, the location information node 327 is an independent node, or the location information node 327 is co-located with the HSS 326, AAA server 330, SeGW, or PCRF 350. The method includes: additional steps performed by the location information node 327: Step 901 This step corresponds to step 40L in FIG. 4. The location information node 327 receives the location information associated with the home base station 345 from the AAA server 330.

[0120] When the home base station 345 and the SeGW 323 establish an IPSec tunnel, the location information can be received from the AAA server 330. The location information may include at least one of the following: a local Internet Protocol (IP) address and port number associated with the home base station 345, and the identity of the home base station 345. The local IP address can be an IPv6 address or an IPv4 address, and the port number is a UDP port number. When a network address translator (NAT) is detected, the location information may include the port number associated with the home base station 345.

[0121] In some embodiments, the location information includes a home base station identity. In some embodiments, the home base station identifier is the global base station ID, ECGI, CGI, home base station name or FQDNo

[0122] Step 902 This step corresponds to step 602 in FIG. 6, step 702 in FIG. 7, and step 804 in FIG. 8. In some embodiments, the location information node 327 receives requests for location information from the MME/SGSN 325,340. The request includes: UE location information and MME/SGSN ID. The UE 370 is served by the home base station 345.

[0123] In some embodiments, the location information node 327 directly receives a request for location information from the PCRF 350.

The request includes: user equipment (UE) location information and PCRF ID. The UE 370 is served by the home base station 345.

[0124] Step 903 This step corresponds to step 603 and step 604 in FIG. 6, step 703 and step 704 in FIG. 7, and step 805 in FIG. 8. The location information node 327 transmits location information to the PCRF 350.

[0125] In some embodiments, the interface between the MME/SGSN 325, 340 and the PCRF 350 is used, via the MME/SGSN

325 and 340 transmit location information to PCRF 350.

[0126] In some embodiments, the S11/S4 interface, the S5/S8 interface and the Gx/Gxx interface are used via MME/SGSN

325, 340 and SGW/PGW 343, 348 transmit position information to PCRF 350.

[0127] In some embodiments, the interface between the location information node 327 and the PCRF 350 is used to directly transmit location information to the PCRF 350.

[0128] Step 904. In some embodiments, the location information node 327 creates a relationship between the home base station 345 and the MME/SGSN 325, 340.

And receive the request from the MME/SGSN 325, 340, or it creates an association between the home base station 345 and the PCRF 350, and receives the request from the PCRF 350. It depends on which of the alternatives is executed in step 902.

[0129] The MME/SGSN 325 and 340 do not have any H(e)NB IPSec tunnel information. But MME/SGSN has H(e)NB cell ID, and SeGW 332 has H(e)NB IP address and H(e)NB ID. The MME/SGSN 325, 340 must use the H(e)NB ID to map to the cell ID and retrieve the H(e)NB NAT IP address from the new interface. Therefore, "association" refers to the mapping function.

[0130] Step 905 In some embodiments, the location information node 327 obtains location information based on UE location information and MME/SGSN ID, or based on UE location information and PCRF ID.

[0131] Step 906 In some embodiments, the location information node 327 updates the received location information.

[0132] Step 907 This step corresponds to steps 609, 610, 611, 612, 618, 619 and step 620 in Figure 6, steps 707, 708, 709, 714 and step 715 in Figure 1, and steps in Figure 8 Step 807 and step 814. In some embodiments, the location information node 327 transmits updated location information to the PCRF 350.

[0133] In some embodiments, when the location information node 327 has created the home base station 345 and the MME/SGSN 325,

During the association between 340, the updated location information is transmitted to PCRF 350 via MME/SGSN 325 and 340.

[0134] In some embodiments, when the location information node 327 has already created an association between the home base station 345 and the MME/SGSN 325, 340, the updated information will be updated via the MME/SGSN 325, 340 and SGW/PGW 343, 348. The location information is sent to PCRF 350ο

[0135] In some embodiments, when the location information node 327 has created an association between the home base station 345 and the PCRF 350, the updated location information is directly transmitted to the PCRF 350.

[0136] Step 908 This step corresponds to step 617 in FIG. 6, step 713 in FIG. 7, and step 813 in FIG. 8. In some embodiments, the location information node 327 receives a request for updated location information.

[0137] In some embodiments, a request for updated location information is received from the MME/SGSN 325, 340, or from the PCRF 350.

[0138] Step 909 In some embodiments, the location information node 327 receives information about removing the association between the home base station 345 and the MME/SGSN 325, 340, or the association between the home base station 345 and the PCRF 350.

[0139] Step 910 After step 909, perform this step. In some embodiments, the location information node 327 removes the association between the home base station 345 and the MME/SGSN 325, 340, or the association between the home base station 345 and the PCRF 350.

[0140] In order to perform the method steps shown in FIG. 8 for providing the PCRF 350 with location information associated with the home base station 345, the location information node 327 includes an arrangement as shown in FIG. 10. The location information node 327 is adapted to be dedicated to processing location information when the user equipment 370 is attached to the communication network 300 via the home base station 345. The location information node 327 is adapted to connect to the AAA server 330 and the MME/SGSN 325. In some embodiments, the location information includes at least one of the following: a local IP address and port number associated with the home base station 345. In some embodiments, the local IP address is an IPv6 address or an IPv4 address, and the port number is a UDP port number. Location information can include home base stations

Logo. The home base station identifier can be a global base station ID, ECGI, CGI, home base station name, or FQDN. In some embodiments, the location information node 327 is an independent node, or where the location information node 327 is co-located with the HSS 326, AAA server 330, SeGW, or PCRF 350. The home base station 345 may be a HeNB or HNB.

[0141] The location information node 327 includes a receiver 1001 configured to receive location information associated with the home base station 345 from the AAA server 330. The location information includes at least one of the following: a local IP address or port number associated with the identity of the home base station 345. The receiver 1001 may also be configured to receive requests for location information from the MME/SGSN 325, 340. The request includes location information and MME/SGSN ID. The UE 370 is served by the home base station 345. In some embodiments, the receiver 1001 is also configured to receive information about removing the association between the home base station 345 and the MME/SGSN 325, 340. In some embodiments, the receiver 1001 is further configured to directly receive a request for location information from the PCRF 350, the request including UE location information or PCRF ID_O The UE 370 is served by the home base station 345. In some embodiments, the receiver 1001 is also configured to receive information about removing the association between the home base station 345 and the PCRF 350. In some embodiments, the receiver 1001 is also configured to receive a request for updated location information. In some embodiments, the receiver 1001 is also configured to receive requests from the MME/SGSN 325, 340 or from the PCRF 350. In some embodiments, the receiver 1001 is further configured to receive location information from the AAA server 330 when the home base station 345 establishes an IPSec tunnel with the SeGW 332.

[0142] The location information node 327 includes a transmitter 1003, which is configured to transmit location information to the PCRF 350. In some embodiments, the transmitter 1003 is configured to use the interface between the MME/SGSN 325, 340 and the PCRF 350 to transmit location information to the PCRF 350 via the MME/SGSN 325, 340. In some embodiments, the transmitter 1003 is configured to use the S11/S4 interface, the S5/S8 interface, and the Gx/Gxx interface to transmit location information to the PCRF 350 via the MME/SGSN 325, 340 and the SGW/PGW 343, 348. In some embodiments, the transmitter 1003 is further configured to directly transmit the position information to the PCRF 350 using the interface between the position information node 327 and the PCRF 350. In some embodiments, the transmitter 1003 is further configured to transmit updated location information to the PCRF 350. In some embodiments, the transmitter 1003 is further configured to: when the location information node 327 has established an association between the home base station 345 and the MME/SGSN 325, 340, transmit the updated information to the PCRF 350 via the MME/SGSN 325, 340 location information. In some embodiments, The transmitter 1003 is also configured to: when the location information node 327 has established an association between the home base station 345 and the MME/SGSN 325, 340, it transmits the update to the PCRF 350 via the MME/SGSN 325, 340 and the SGW/PGW 343, 348 Location information. In some embodiments, the transmitter 1003 is further configured to directly transmit the updated position information to the PCRF 350 when the location information node 327 has established an association between the home base station 345 and the PCRF 350.

[0143] In some embodiments, the location information node 327 further includes a processor 1005, and the processor 1005 is configured to establish an association between the home base station 345 and the MME/SGSN 325, 340, and receive the information from the MME/SGSN 325, 340 request. In some embodiments, the processor 1005 is configured to obtain location information based on UE location information and MME/SGSN ID. In some embodiments, the processor 1005 is further configured to remove the association between the home base station 345 and the MME/SGSN 325,340. In some embodiments, the processor 1005 is further configured to create an association between the home base station 325 and the PCRF 350 to obtain location information based on the UE location information and the PCRF ID. In some embodiments, the processor 1005 is further configured to: remove the association between the home base station 345 and the PCRF 350. In some embodiments, the processor 705 is further configured to update location information. In some embodiments, the processor 1005 is further configured to: detect NAT. When the NAT is detected, the location information may include: the port number associated with the home base station 345.

[0144] It may be implemented by one or more processors, such as the processor 1005 in the node device depicted in FIG. 10, together with computer program codes for performing the functions of the embodiments herein, for sending to the PCRF 350 Provide with home

This mechanism of location information associated with the base station 345. The processor 1005 may be, for example, a digital signal processor (DSP), an application specific integrated circuit (ASIC) processor, a field programmable gate array (FPGA) processor, or a microprocessor. The above-mentioned program code can be provided as a computer program product, for example, in the form of a data carrier carrying computer program code. When the computer program code is loaded into the location information node 327, the computer program code is used to execute Examples in this article. One such carrier may be in the form of a CD ROM disc. However, the use of other data carriers (such as memory sticks) is feasible. The computer program code can also be provided as pure program code on the server, and the computer program code can be downloaded to the location information node 327.

[0145] The location information node 327 may further include a memory 1010, and the memory 1010 includes one or more memory units. The memory 1010 is arranged to store data, received data streams, home base station location information, UE location information, MME/SGSN ID, PCRF ID, updated home base station location information, history of changes to home base station location information, Information about the association between the Femtocell and PCRF and the information about the association between Femtocell and MME/SGSN, request for information, IP address, UDP port number, threshold, time period, configuration, scheduling, and application, when When the application is executed in the location information node 327, the application is used to execute the method in this document.

[0146] Those skilled in the art will also understand that the receiver 1001 and transmitter 1003 described above may refer to a combination of analog circuits and digital circuits, and/or be configured with software and/or firmware (for example, stored in 1010). When the software and/or firmware is executed by one or more processors (such as the processor 1005), the software and/or firmware executes the one or more processors described above). One or more of these processors and other digital hardware can be included in a single application specific integrated circuit (ASIC), or several processors and various digital hardware can be distributed among several components, regardless of individual The ground package is still assembled into a system-on-chip (SoC).

[0147] The embodiments herein are not limited to the above-mentioned embodiments. Various alternatives, modifications, and equivalents can be used. Therefore, the above-mentioned embodiments should not be considered as limiting the scope of the embodiments.

[0148] It should be emphasized that when used in this context, the word "includes/includes" is used to designate the existence of stated features, wholes, steps or components, but does not exclude the presence or addition of one or more additional features, wholes , Steps, components, or a combination of them. It should also be noted that the word "a" or "an" before an element does not exclude the presence of multiple such elements.

[0149] It should also be emphasized that, without departing from the embodiments herein, the steps of the methods defined in the additional embodiments may be performed in a different order than the order in which they are shown.

[0150] Those skilled in the art will understand that different options can be directly predicted or obtained from the examples that have been shown in this document.