WO2012024997A1 - 一种控制业务接纳的方法及系统 - Google Patents

一种控制业务接纳的方法及系统 Download PDF

Info

Publication number
WO2012024997A1
WO2012024997A1 PCT/CN2011/077539 CN2011077539W WO2012024997A1 WO 2012024997 A1 WO2012024997 A1 WO 2012024997A1 CN 2011077539 W CN2011077539 W CN 2011077539W WO 2012024997 A1 WO2012024997 A1 WO 2012024997A1
Authority
WO
WIPO (PCT)
Prior art keywords
henb
hnb
qos
authorized
admission control
Prior art date
Application number
PCT/CN2011/077539
Other languages
English (en)
French (fr)
Inventor
毕以峰
周晓云
霍玉臻
宗在峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012024997A1 publication Critical patent/WO2012024997A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a method and system for controlling service admission. Background technique
  • the Evolved Packet System (EPS) of the 3rd Generation Partnership Project (3GPP) is evolved by Evolved Universal Terrestrial Radio Access Network (E-UTRAN), mobile management.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • FIG. 1 is a schematic diagram of an architecture of a Home evolved NodeB (HeNB) accessing an EPS in a non-roaming scenario according to the related art.
  • HeNB Home evolved NodeB
  • S-GW is an access gateway device connected to E-UTRAN, in E-UTRAN and The P-GW forwards data and is responsible for buffering the paging waiting data.
  • the P-GW is the border gateway of the EPS and Packet Data Network (PDN) network, which is responsible for PDN access and EPS and PDN. Transfer data and other functions.
  • PDN Packet Data Network
  • the Policy and Charging Rules Function performs policy and charging rules. It uses the interface Rx and the carrier network.
  • the application function (AF) of the protocol (Internet Protocol, IP) service network is connected to obtain service information, which is used to generate service information of the PCC policy.
  • AF application function
  • IP Internet Protocol
  • PCRF Policy and Charging Enforcement Function
  • S-GW S5 interface adopts the GTP protocol
  • PCEF Policy and Charging Enforcement Function
  • the PCRF and the P-GW exchange information through the Gx interface, which is responsible for initiating the establishment and modification of the bearer. Release, guarantee the quality of service (QoS) of business data, and perform charging control.
  • QoS quality of service
  • the S-GW hosts Bearer Binding and Event Report Function (BBERF), and S -
  • BBERF Bearer Binding and Event Report Function
  • S - The GW and the PCRF exchange information through the Gxc interface, and the BBERF is responsible for initiating the establishment, modification, and release of the bearer, ensuring the service quality of the service data, and performing charging control by the PCEF.
  • the EPS supports the access of the HeNB, which is a small, low-power base station deployed in indoor places such as homes, offices, and corporate buildings.
  • the Closed Subscriber Group is a concept introduced after the introduction of a home base station. Usually a family or a user within an enterprise forms a closed subscriber group, which is identified by a CSG ID. The home base station serving the users in this closed subscriber group has the same CSG ID. When a closed subscriber group is served by only one home base station, the closed subscriber group can also be directly identified by the home base station identity (e.g., BS ID).
  • the CSG user and/or the non-CSG user can distinguish different levels, and the priority of the service is different, and the service quality and service category can be different.
  • the user can access the home base station corresponding to multiple closed user groups, for example, the user's office, home, and the like.
  • the concept of allowing a closed user group list to be introduced is therefore introduced. This list is stored in the user's terminal and on the user data server on the network side.
  • home base stations There are three usage modes for home base stations: closed mode, mixed mode, and open mode.
  • closed mode only the CSG subscription user to which the home base station belongs can access the base station and enjoy the service provided by the base station; when the home base station is in the open mode, any operator subscription user can access the base station.
  • the home base station at this time is equivalent to the macro base station; when the home base station is in the hybrid mode, it also allows any operator to subscribe to the user or the roaming user.
  • Incoming to use but according to whether the user subscribes to the CSG information to distinguish different levels, that is, users who sign the CSG have higher service priority when using the hybrid home base station, enjoy better service quality and service category. .
  • the HeNB usually accesses the core network of the EPS through the leased fixed network line (as shown in FIG. 1).
  • a security gateway (SeGW) is introduced in the core network for shielding, and between the HeNB and the SeGW.
  • the data will be encapsulated using Internet Protocol Security (IPS Security).
  • IPS Security Internet Protocol Security
  • the HeNB may directly connect to the MME and the S-GW of the core network through an IPSec tunnel established with the SeGW, or may connect to the MME and the S-GW through the HeNB GW.
  • the Universal Mobile Telecommunications System supports access to the home base station HNB (Home NodeB).
  • HNB Home NodeB
  • 2 is a schematic diagram of an architecture of an HNB accessing UMTS in a non-roaming scenario according to the related art.
  • the architecture in FIG. 2 is similar to the architecture of FIG. 1, except that a Serving General Packet Radio Service is used.
  • the Support Node, SGSN replaces the S-GW and replaces the P-GW with a Gateway General Packet Radio Service Support Node (GGSN).
  • GGSN Gateway General Packet Radio Service Support Node
  • HeNB PF HeNB Policy Function
  • the HeNB Policy Function (HeNB PF) is set in the 3GPP HeNB subsystem. (Accommodation by SeGW, HeNB GW and other network elements, such as HeMS) and the BroadBand Forum Policy Control Function (BBF BPCF) implement business admission management and mobile network resource management.
  • BBF BPCF BroadBand Forum Policy Control Function
  • the QoS of the fixed line that the HeNB/HNB accesses is usually restricted by the contract of the owner of the HeNB/HNB and the fixed network operator. Therefore, when the UE accesses the 3GPP core network to access the service through the HeNB/HNB, the required QoS cannot exceed the subscription QoS of the fixed network line that the fixed network operator can provide.
  • the QoS of the UE access service will not be guaranteed, especially for the guaranteed bit rate (GBR) service. Therefore, for the 3GPP network and the fixed network, when a new service is initiated, the service can only be accepted if the fixed network has sufficient resources/bandwidth and the mobile network resources are sufficient. Otherwise, The business should be rejected.
  • the main purpose of the present invention is to provide a method and system for controlling service admission, which can improve the performance of the system control service admission and improve the resource management capability of the system, thereby ensuring the QoS of the UE access service and improving the user experience.
  • a method of controlling business acceptance including:
  • the evolved home base station HeNB/home base station When the HNB is powered on, the admission control network element obtains the authorized resource information from the fixed network;
  • admission control network element performs admission control on the user UE accessed from the HeNB/HNB according to the authorized resource information.
  • the authorized resource information is an authorized quality of service QoS,
  • the authorized QoS includes one or more of the following: bandwidth, quality of service level identification, and guaranteed bit rate.
  • the admission control network element is an evolved home base station gateway HeNB GW, a mobility management unit MME or an HeNB.
  • the admission control network element is a home base station gateway HNB GW or HNB.
  • the admission control network element When the admission control network element is the HeNB GW, when the HeNB is powered on, the admission control network element obtains the authorization resource information from the fixed network as:
  • the HeNB is powered on and registered with the HeNB GW, and the HeNB GW requests the QoS of the authorized home base station policy function entity;
  • the evolved home base station policy function entity requests an authorized QoS from the fixed network resource management unit, and After obtaining the authorized QoS, it is fed back to the HeNB GW, and the HeNB GW stores the QoS.
  • the admission control network element is the HNB GW, when the HNB is powered on, the admission control network element obtains the authorization resource information from the fixed network as:
  • the HNB is powered on and registered with the HNB GW, and the HNB GW requests the authorized QoS from the home base station policy function entity;
  • the home base station policy function entity requests the QoS of the authorized network from the fixed network resource management unit, and after receiving the authorized QoS, feeds it back to the HNB GW, and the HNB GW stores the QoS.
  • the admission control network element When the admission control network element is the MME, when the HeNB is powered on, the admission control network element obtains the authorization resource information from the fixed network as:
  • the HeNB is powered on and registered with the MME, and the MME requests the QoS of the authorized home base station policy function entity;
  • the evolved home base station policy function entity requests the authorized QoS from the fixed network resource management unit, and feeds back the obtained authorized QoS to the MME, and the MME stores the QoS.
  • the admission control network element When the admission control network element is the HeNB, when the HeNB is powered on, the admission control network element obtains the authorization resource information from the fixed network as:
  • the HeNB is powered on and registered with the HeNB GW/MME, and the HeNB GW/MME requests the authorized QoS from the evolved home base station policy function entity; the evolved home base station policy function entity requests the authorized QoS from the fixed network resource management unit, and obtains the authorized QoS.
  • the QoS is fed back to the HeNB GW/MME; the HeNB GW/MME sends the authorized QoS to the HeNB, and the HeNB stores the authorized QoS, or
  • the eNB After the HeNB is powered on, the eNB requests the authorized QoS from the evolved home base station policy function entity; the evolved home base station policy function entity requests the fixed QoS from the fixed network resource management unit, and feeds the obtained authorized QoS to the HeNB, and the HeNB stores the authorization. QoS.
  • the admission control network element When the admission control network element is an HNB, when the HNB is powered on, the admission control network element obtains the authorization resource information from the fixed network as: The HNB is powered on and registered with the HNB GW, and the HNB GW requests the authorized QoS from the home base station policy function entity; the home base station policy function entity requests the authorized QoS from the fixed network resource management unit, and feeds the obtained authorized QoS to the HNB GW; The HNB GW feeds back the authorized QoS to the HNB, and the HNB stores the authorized QoS, or
  • the eNB After the HNB is powered on, the eNB requests the authorized QoS from the home base station policy function entity; the home base station policy function entity requests the fixed QoS from the fixed network resource management unit, and feeds the obtained authorized QoS to the HNB, and the HNB stores the authorized QoS. .
  • the admission control network element obtains the authorization resource information from the fixed network as follows: When the authorized resource information changes, the fixed network actively sends the modified authorization resource information to the admission control network element by the home base station policy function entity.
  • the QoS that is requested by the fixed network resource management unit carries the tunnel information/local information, and the fixed network resource management unit searches for the backhaul network where the HeNB/HNB is located according to the tunnel information/local information, and uses the current backhaul network resource according to the tunnel information/local information.
  • the condition is that the HeNB/HNB authorizes QoS.
  • the tunnel information/local information is carried by the HeNB/HNB itself and/or encapsulated by the SeGW into the HeNB/HNB registration information and sent to the HeNB GW / HNB GW; admission control If the network element is the MME, the tunnel information/local information is carried by the HeNB itself and/or encapsulated by the SeGW into the HeNB registration information and sent to the MME. If the admission control network element is the HeNB/HNB, the tunnel information is used. The /local information is obtained by the HeNB/HNB itself.
  • the tunnel information/local information includes one or more of the following: an IP address assigned by the fixed network to the terminal, a NAT address converted by the network address translation port, and a port number; an IP address, a port number, and a SeGW address allocated by the SeGW for the terminal and Port number, the identity of the HeNB.
  • the fixed network resource management unit is a BPCF
  • the evolved home base station policy function entity/family base station policy function entity is a HeNB PF/HNB PF.
  • the method also includes: When the fixed network returns the authorization resource information to the admission control network element, the semi-static indication is carried, and after receiving the semi-static indication, the admission control network element performs admission control according to the authorized resource information, and is no longer fixed. Web query.
  • the method further includes: the admission control network element records the usage status of the current fixed network resource.
  • the admission control network element performs admission control on the UE accessed from the HeNB/HNB according to the authorized resource information:
  • the admission control is performed when the UE accesses the HeNB/HNB, initiates attach by the HeNB/HNB, establishes a PDN connection request, a bearer setup/modify/delete request, or initiates a bearer setup/modification/delete request by the core network side.
  • the network element performs the admission decision according to the QoS of the fixed network feedback, that is, when the fixed network resource is satisfied, the admission control network element accepts the request; when the fixed network resource is not satisfied, the admission control network element rejects the request, or the admission The control network element decides to preempt the existing used resources to satisfy the request.
  • a system for controlling service admission comprising: a HeNB/HNB, an admission control network element, and a fixed network;
  • the admission control network element is configured to: when the HeNB/HNB is powered on, obtain the authorization resource information from the fixed network; and access the information from the HeNB/HNB according to the authorized resource information returned by the fixed network.
  • the UE performs admission control
  • the fixed network is configured to provide authorized resource information of the HeNB/HNB.
  • the authorized resource information returned by the fixed network is an authorized quality of service QoS.
  • the admission control network element is an evolved home base station gateway HeNB.
  • the admission control network element is a home base station gateway HNB GW or HNB.
  • the admission control network element obtains the authorization resource information from the fixed network as follows: the HeNB is powered on and registered with the HeNB GW, and the HeNB GW requests the evolved home base station policy function entity to evolve the home base station policy function entity to request the authorized QoS; The evolved home base station policy function entity requests the fixed QoS from the fixed network resource management unit, and after obtaining the authorized QoS, feeds it back to the HeNB GW, and the HeNB GW stores the QoS.
  • the admission control network element When the HNB is powered on, the admission control network element obtains the authorization resource information from the fixed network: the HNB is powered on and registered with the HNB GW, and the HNB GW requests the authorized QoS from the home base station policy function entity home base station policy function entity;
  • the home base station policy function entity requests the QoS of the authorized network from the fixed network resource management unit, and after receiving the authorized QoS, feeds it back to the HNB GW, and the HNB GW stores the QoS.
  • the admission control network element When the HeNB is powered on, the admission control network element obtains the authorization resource information from the fixed network: the HeNB is powered on and registered with the MME, and the MME requests the authorized QoS from the evolved home base station policy function entity;
  • the evolved home base station policy function entity requests the authorized QoS from the fixed network resource management unit, and feeds back the obtained authorized QoS to the MME, and the MME stores the QoS.
  • the admission control network element obtains the authorization resource information from the fixed network as follows: the HeNB is powered on and registered with the HeNB GW/MME, and the HeNB GW/MME requests the authorized QoS from the evolved home base station policy function entity; The base station policy function entity requests the authorized QoS from the fixed network resource management unit, and feeds the obtained authorized QoS to the HeNB GW/MME;
  • the HeNB GW/MME feeds back the authorized QoS to the HeNB, and the HeNB stores the authorized
  • the evolved home base station policy function entity requests the authorized QoS from the fixed network resource management unit, and feeds the obtained authorized QoS to the HeNB, the HeNB storage office. Describe the QoS of the authorization.
  • the admission control network element obtains the authorized resource information from the fixed network as:
  • the HNB is powered on and registered with the HNB GW, and the HNB GW requests the authorized QoS from the home base station policy function entity; the home base station policy function entity requests the authorized QoS from the fixed network resource management unit, and feeds the obtained authorized QoS to the HNB GW; HNB GW will authorize the QoS is fed back to the HNB, and the HNB stores the authorized QoS,
  • the home base station policy function entity requests the authorized QoS from the fixed network resource management unit, and feeds the obtained authorized QoS to the HNB, where the HNB stores the authorization. QoS.
  • the admission control network element obtains the authorization resource information from the fixed network as follows: When the authorized resource information changes, the fixed network actively sends the modified authorization resource information to the admission control network element by the home base station policy function entity.
  • the QoS that is requested by the fixed network resource management unit carries the tunnel information/local information, and the fixed network resource management unit searches for the backhaul network where the HeNB/HNB is located according to the tunnel information/local information, and uses the current backhaul network resource according to the tunnel information/local information.
  • the condition is that the HeNB/HNB authorizes QoS.
  • the tunnel information/local information is carried by the HeNB/HNB itself and/or encapsulated by the SeGW into the HeNB/HNB registration information and sent to the HeNB GW / HNB GW; admission control If the network element is the MME, the tunnel information/local information is carried by the HeNB itself and/or encapsulated by the SeGW into the HeNB registration information and sent to the MME. If the admission control network element is the HeNB/HNB, the tunnel information is used. The /local information is obtained by the HeNB/HNB itself.
  • the tunnel information/local information includes one or more of the following: an IP address assigned by the fixed network to the terminal, a NAT address converted by the network address translation port, and a port number; an IP address, a port number, and a SeGW address allocated by the SeGW for the terminal and Port number, the identity of the HeNB.
  • the fixed network resource management unit is a BPCF
  • the evolved home base station policy function entity/family base station policy function entity is a HeNB PF/HNB PF.
  • the fixed network is further configured to carry a semi-static indication when returning the authorized resource information to the admission control network element;
  • the admission control network element is further configured to perform admission control according to the authorized resource information after receiving the semi-static indication, and no longer query the fixed network.
  • the admission control network element is further configured to record the current usage status of the fixed network resource.
  • the admission control network element performs admission control on the UE accessed from the HeNB/HNB according to the authorized resource information:
  • the admission control is performed when the UE accesses the HeNB/HNB, initiates attach by the HeNB/HNB, establishes a PDN connection request, a bearer setup/modify/delete request, or initiates a bearer setup/modification/delete request by the core network side.
  • the network element performs the admission decision according to the QoS of the fixed network feedback, that is, when the fixed network resource is satisfied, the admission control network element accepts the request; when the fixed network resource is not satisfied, the admission control network element rejects the request, or the admission The control network element decides to preempt the existing used resources to satisfy the request.
  • the method and system for controlling the service admission of the present invention in the scenario that the UE accesses the core network through the HeNB/HNB, only when the fixed network and the mobile network have sufficient resources, the core network accepts the service initiated by the UE, therefore,
  • the invention can improve the performance of the system control service admission, and at the same time improve the resource management capability of the system, thereby further ensuring the QoS of the UE access service and improving the user experience.
  • FIG. 1 is a schematic structural diagram of a HeNB accessing an EPS in a non-roaming scenario according to the related art
  • FIG. 2 is a schematic structural diagram of an HNB accessing UMTS in a non-roaming scenario according to the related art
  • FIG. 3 is a schematic flowchart of a method for controlling service admission according to the present invention.
  • FIG. 5 is a schematic flowchart of a receiving control performed by a HeNB GW when a UE is established through a HeNB attach or a PDN connection according to Embodiment 2 of the present invention
  • FIG. 6 is a schematic flowchart of performing admission control by a HeNB when a terminal or a core network side initiates a dedicated bearer setup or modification operation after the UE is attached by the HeNB according to Embodiment 3 of the present invention
  • FIG. 7 is a UE or a core network side after the UE is attached by the HeNB according to Embodiment 4 of the present invention;
  • FIG. 8 is a flow chart of the HeNB performing the resource update registration when the terminal or the network side initiates the user detach operation after the terminal is attached by the HeNB according to the embodiment 5 of the present invention; schematic diagram;
  • FIG. 9 is a schematic flowchart of the admission control of the HeNB GW according to Embodiment 6 of the present invention
  • FIG. 10 is a schematic flowchart of the MME acquiring the authorized QoS when the HeNB is powered on according to Embodiment 7 of the present invention
  • FIG. 11 is a schematic flowchart of a method for an HeNB to acquire an authorized QoS when the HeNB is powered on according to Embodiment 8 of the present invention
  • FIG. 12 is another schematic flowchart of the HeNB acquiring the authorized QoS when the HeNB is powered on according to the embodiment of the present invention. detailed description
  • the basic idea of the present invention is: In the scenario where the UE accesses the core network through the HeNB/HNB, the core network accepts the service initiated by the UE only when it is ensured that the fixed network and the mobile network have sufficient resources.
  • FIG. 3 is a schematic flowchart of a method for controlling service admission according to an embodiment of the present invention. As shown in FIG. 3, the method includes:
  • Step 301 When the HeNB/HNB is powered on, the admission control network element obtains the authorization resource information from the fixed network.
  • the authorized resource information generally refers to the authorized QoS, and the authorized QoS may include one or more of the following: Quality of service level identification, guaranteed bit rate.
  • the fixed network refers to the fixed access network, including the existing wireless local area network, Asymmetric Digital Subscriber Line (ADSL) access, and the like.
  • ADSL Asymmetric Digital Subscriber Line
  • the admission control network element is a HeNB GW, an MME, or an HeNB; in the case that the HNB is powered on, the admission control network element is an HNB GW or an HNB, specifically:
  • the admission control network element is the HeNB GW/HNB GW
  • the HeNB/HNB is powered on and registered with the HeNB GW/HNB GW, and the HeNB GW/HNB GW requests the QoS of the HeNB PF/HNB PF (ie, the HeNB/HNB can Guaranteed QoS);
  • HeNB PF/HNB PF requests authorized QoS from the fixed network resource management unit (BPCF), and the HeNB PF/HNB PF obtains the authorized QoS and feeds it back to the HeNB GW/HNB GW, HeNB GW/HNB GW storage The QoS.
  • BPCF fixed network resource management unit
  • the UE When the UE accesses the HeNB B, the UE attaches through the HeNB/HNB, establishes a P connection, requests bearer setup/modification, or the core network side requests bearer setup/modification, the HeNB GW/HNB GW according to the fixed network feedback QoS, current resource usage, and existing mechanisms determine whether the service can be accepted.
  • the admission control network element is the MME
  • the HeNB is powered on and registered with the MME, and the MME requests the authorized QoS from the HeNB PF; the HeNB PF requests the QoS of the fixed network resource management unit (BPCF), and the HeNB PF acquires the QoS. It is then fed back to the MME, which stores the QoS.
  • the UE accesses the HeNB/HNB
  • the UE attaches through the HeNB, establishes a PDN connection, requests bearer setup/modification, or the core network side requests bearer setup/modification
  • the MME uses the QoS of the fixed network feedback and the current resource usage status. And the existing mechanism to decide whether the business can be accepted.
  • the HeNB/HNB can be powered on and registered with the HeNB GW/HNB GW, and the HeNB GW/HNB GW requests the authorized QoS from the HeNB PF/HNB PF; HeNB PF/HNB PF to the fixed network
  • the resource management unit (BPCF) requests the authorized QoS; the HeNB PF/HNB PF obtains the authorized QoS and feeds it back to the HeNB GW/HNB GW; the HeNB GW/HNB GW feeds the QoS back to the HeNB/HNB, and the HeNB/HNB stores
  • the QoSo or HeNB/HNB can request the authorized QoS (the QoS that can be guaranteed by the HeNB/HNB) after the HeNB/HNB is powered on; the HeNB PF/HNB PF requests authorization from the fixed network resource management unit (BPCF) QoS, the HeNB PF/HNB PF obtains the QoS and feeds it back to
  • BPCF fixed network resource
  • the UE accesses the HeNB/HNB QoS based on fixed network feedback when the HeNB/HNB initiates attach, establishes a P connection request, requests a bearer setup/modify/delete request, or the core network side initiates a bearer setup/modification/delete request.
  • modified authorized resource information may be sent to the admission control network element by the home base station policy function entity by the fixed network when the authorized resource information changes.
  • the admission control network element carries the tunnel information/local information to the HeNB Policy Control Function Entity (PF), and the HeNB PF carries the tunnel information/local information when requesting the authorized QoS to the fixed network BPCF, and the BPCF according to the tunnel information/local
  • the information finds the backhaul network where the HeNB/HNB is located, and authorizes the QoS for the HeNB/HNB according to the current usage status of the backhaul network resources.
  • the tunnel information/local information may include one or more of the following information: an IP address allocated by the fixed network for the terminal, an IP address assigned by the SeGW to the terminal, a SeGW address, and a Network Address Translation (NAT) conversion. The address and port number after the HeNB's identity.
  • NAT Network Address Translation
  • the tunnel information/local information may be carried by the HeNB/HNB itself and/or encapsulated by the SeGW into the HeNB/HNB registration information and sent to the HeNB GW / HNB GW;
  • the tunnel information/local information may be carried by the HeNB itself and/or encapsulated by the SeGW into the HeNB registration information and sent to the MME; when the HeNB/HNB is used as the admission control network element, the tunnel information/local information HeNB/ HNB Get it yourself.
  • the fixed network can determine the location of the HeNB and the authorized QoS that can be provided according to the tunnel information/local information, and the fixed network can also determine the authorized resources according to factors such as the HeNB/HNB level.
  • the MME can register with the MME, and the MME feeds back the authorized QoS to the HeNB/HNB.
  • the process is similar to the foregoing registration to the HeNB GW, and is not described in detail herein.
  • the semi-static indication may be carried, indicating that the authorized resource is valid in the HeNB/HNB registration state, and the admission control network element receives the semi-static indication. Then, the admission control may be performed according to the authorized resource information, and the query is not performed to the fixed network.
  • Step 302 The admission control network element performs admission control on the UE accessed from the HeNB/HNB according to the authorized resource information.
  • the admission control network element performs the admission decision according to the QoS of the fixed network feedback, that is, when the fixed network resource is satisfied, the admission control network element accepts the request; when the fixed network resource is not satisfied, the admission control network element rejects the request, or The admission control network element decides to preempt the existing used resources to satisfy the request.
  • admission control includes two aspects: 1. Admission control of user access/PDN connection; 2. Admission control initiated by bearer.
  • the HeNB/HNB when the UE accesses the HeNB/HNB, attaches/establishes a PDN connection through the HeNB/HNB, requests bearer setup/modification, or requests a bearer setup/modification of the core network side, the HeNB/HNB is configured according to a fixed network.
  • the feedback QoS makes admission decisions.
  • admission control also involves related resource management.
  • the admission control network element records the current use of the fixed network resource. status.
  • the present invention also provides a system for controlling service admission, the system comprising: a HeNB/HNB, an admission control network element, and a fixed network;
  • the admission control network element is configured to: when the HeNB/HNB is powered on, obtain the authorization resource information from the fixed network; and perform admission control on the UE accessed from the HeNB/HNB according to the authorized resource information returned by the fixed network;
  • the fixed network is configured to provide authorized resource information of the HeNB/HNB.
  • the authorized resource information returned by the fixed network is an authorized quality of service QoS.
  • the admission control network element is an evolved home base station gateway HeNB.
  • the admission control network element is a home base station gateway HNB GW or HNB.
  • the admission control network element When the HeNB is powered on, the admission control network element obtains the authorization resource information from the fixed network: the HeNB is powered on and registered with the HeNB GW, and the HeNB GW requests the authorized QoS from the evolved home base station policy function entity HeNB PF;
  • the HeNB PF requests the QoS of the authorized network resource management unit BPCF, and after obtaining the authorized QoS, feeds it back to the HeNB GW, and the HeNB GW stores the QoS.
  • the admission control network element When the HNB is powered on, the admission control network element obtains the authorization resource information from the fixed network as follows: the HNB is powered on and registered with the HNB GW, and the HNB GW sends the policy function entity to the home base station.
  • HNB PF requests authorization QoS
  • HNB PF requests authorized QoS from the fixed network resource management unit BPCF, and obtains authorization
  • the admission control network element When the HeNB is powered on, the admission control network element obtains the authorization resource information from the fixed network: the HeNB is powered on and registered with the MME, and the MME requests the authorized QoS from the HeNB PF; the HeNB PF requests the authorized QoS from the BPCF, and obtains the QoS.
  • the MME the MME stores the QoS.
  • the admission control network element When the HeNB is powered on, the admission control network element obtains the authorization resource information from the fixed network as follows: the HeNB is powered on and registered with the HeNB GW/MME, and the HeNB GW/MME requests the authorized QoS from the HeNB PF; the HeNB PF requests authorization from the BPCF. QoS, and will get the authorization of
  • the QoS is fed back to the HeNB GW/MME; the HeNB GW/MME feeds back the authorized QoS to
  • HeNB HeNB stores the authorized QoS
  • the HeNB after the HeNB is powered on, requesting the authorized QoS from the HeNB PF; the HeNB PF to the BPCF The authorized QoS is requested, and the obtained authorized QoS is fed back to the HeNB, and the HeNB stores the authorized QoS.
  • the admission control network element obtains the authorized resource information from the fixed network as:
  • the HNB is powered on and registered with the HNB GW, and the HNB GW requests the authorized QoS from the HNB PF.
  • the HNB PF requests the authorized QoS from the BPCF, and feeds the obtained authorized QoS to the HNB GW;
  • the HNB GW feeds back the authorized QoS to the HNB, and the HNB stores the authorized QoS, or requests the authorized QoS from the HNB PF after the HNB is powered on; the HNB PF requests the authorized QoS from the BPCF, and obtains the authorized QoS.
  • the QoS is fed back to the HNB, which stores the QoS of the grant.
  • the receiving control network element may obtain the authorization resource information from the fixed network.
  • the fixed network may actively send the modified authorized resource information to the admission control network element by using the home base station policy function entity when the authorized resource information changes.
  • the QoS that is requested by the fixed network resource management unit carries the tunnel information/local information, and the fixed network resource management unit searches for the backhaul network where the HeNB/HNB is located according to the tunnel information/local information, and uses the current backhaul network resource according to the tunnel information/local information.
  • the condition is that the HeNB/HNB authorizes QoS.
  • the tunnel information/local information is carried by the HeNB/HNB itself and/or encapsulated by the SeGW into the HeNB/HNB registration information and sent to the HeNB GW / HNB GW; admission control If the network element is the MME, the tunnel information/local information is carried by the HeNB itself and/or encapsulated by the SeGW into the HeNB registration information and sent to the MME. If the admission control network element is the HeNB/HNB, the tunnel information is used. The /local information is obtained by the HeNB/HNB itself.
  • the tunnel information/local information includes one or more of the following: an IP address assigned by the fixed network to the terminal, a NAT address converted by the network address translation port, and a port number; an IP address, a port number, and a SeGW address allocated by the SeGW for the terminal and Port number, the identity of the HeNB.
  • the fixed network resource management unit is a BPCF
  • the base station policy function entity is the HeNB PF/HNB PF.
  • the fixed network is further configured to carry a semi-static indication when returning the authorized resource information to the admission control network element;
  • the admission control network element is further configured to perform admission control according to the authorized resource information after receiving the semi-static indication, and no longer query the fixed network.
  • the admission control network element is further configured to record the current usage status of the fixed network resource.
  • the admission control network element performs admission control on the UE accessed from the HeNB/HNB according to the authorized resource information:
  • the admission control is performed when the UE accesses the HeNB/HNB, initiates attach by the HeNB/HNB, establishes a PDN connection request, a bearer setup/modify/delete request, or initiates a bearer setup/modification/delete request by the core network side.
  • the network element performs the admission decision according to the QoS of the fixed network feedback, that is, when the fixed network resource is satisfied, the admission control network element accepts the request; when the fixed network resource is not satisfied, the admission control network element rejects the request, or the admission The control network element decides to preempt the existing used resources to satisfy the request.
  • the admission control is performed by the HeNB GW.
  • the HeNB GW obtains the authorized QoS information from the fixed network and stores it.
  • the terminal passes the HeNB attach, access, DN connection establishment, bearer setup, bearer modification, detachment, or PDN connection release, the HeNB GW implements admission control for the service/user according to the authorized QoS, service level, user level, and the like.
  • FIG. 4 is a schematic diagram of a process for registering a HeNB power-on according to Embodiment 1 of the present invention. As shown in FIG. 4, the process includes:
  • Step 401 The HeNB is powered on and accesses the fixed network.
  • the fixed network allocates a local IP address to the HeNB through a related mechanism, and the address is used as an external IP address of the encapsulated data packet.
  • Step 402 The HeNB and the SeGW establish an IPsec tunnel to ensure the security and integrity of the data during transmission.
  • Step 403 The HeNB registers with the HeMS to obtain related configuration information.
  • Step 404 The HeNB registers with the HeNB GW. During the registration process, the HeNB GW acquires tunnel information/local information of the IPsec tunnel between the HeNB and the SeGW.
  • the manner in which the HeNB GW acquires the tunnel information/local information may include: the HeNB carries the tunnel information/local information to the HeNB GW through the registration message sent by the HeNB to the HeNB GW; or when the registration message sent by the HeNB to the HeNB GW passes through the SeGW, the SeGW will The tunnel information/local information is sent together to the HeNB GW; or the SeGW sends the follow-up information to the HeNB GWo through separate signaling.
  • Steps 405-406 The HeNB GW sends a resource request message to the fixed network resource management unit (here, played by the BPCF) through the HeNB PF, and carries the IPsec tunnel information/local information.
  • the fixed network resource management unit here, played by the BPCF
  • Steps 407-408 The fixed network resource management unit (here acted by the BPCF) finds the backhaul network (Backhaul) where the HeNB is located according to the obtained IPsec tunnel information/local information, and determines the current usage status of the fixed network resource.
  • the HeNB authorizes a specific QoS guarantee and returns a resource request response message to the HeNB GW through the HeNB PF.
  • the fixed network resource management unit is hereby acted by the BPCF.
  • the specific implementation depends on the specific situation of the fixed network. It can also be used by other network elements as a "fixed network resource management unit” or by multiple fixed network resource management units (such as BPCF). Implemented in consultation with BNG/BRAS).
  • the authorized QoS is allocated by the fixed network to the HeNB according to information such as the fixed network resource usage status, the HeNB level, and the fixed network user level.
  • the authorized QoS can be information such as available bandwidth, guaranteed bit rate, and the like.
  • Step 409 The HeNB GW stores the authorized QoS for subsequent service/user admission control and resource management.
  • Steps 410-412 After the HeNB is powered on, it is in the registered state, and the fixed network re-adjusts the authorized QoS for the HeNB. At this time, the fixed network resource management unit (here, the BPCF) passes the adjusted authorized QoS information through the HeNB. The PF is pushed to the HeNB GW, which stores the authorized QoS information and is used for subsequent service/user admission control and resource management.
  • the fixed network resource management unit here, the BPCF
  • 5 is a second embodiment of the present invention, when a UE is established through a HeNB attach or a PDN connection, the HeNB
  • Step 501 The HeNB is powered on and completes registration, and the HeNB GW acquires the QoS of the fixed network authorization.
  • Step 502 The UE initiates an attach or PDN connection establishment operation, and performs processing related to the radio side and the core network, including air interface, core network signaling, core network bearer establishment, PCC session establishment, and policy delivery.
  • Step 503 If it is an attach procedure, the EPS core network (for example, MME) sends an "initial context setup request/attach accept" message to the HeNB; if it is a PDN connection establishment procedure, the EPS core network (for example, MME) sends a "bearer setup request" to the HeNB. / PDN connection accepts "message.
  • the EPS core network for example, MME
  • PDN connection accepts "message.
  • a type of operation in which the PDN connection establishment operation is performed when the terminal attaches to the EPS network, the first PDN connection is established, which is called a default PDN connection; then the terminal can also initiate the second, third, ... PDN connection.
  • Establish establish multiple additional PDN connections.
  • the establishment of the PDN connection referred to in the flowchart refers to the establishment of an additional PDN connection, the same below.
  • Step 504 The HeNB GW intercepts the "initial context setup request/attach accept” message or the "bearer setup request/PDN connection accept” message sent by the MME to the HeNB, and according to the current fixed network resource usage status and interception message recorded by the HeNB GW. Admission decisions are made by the requested resource, and the type and level of the user/PDN connection.
  • the current usage status of the fixed network resource recorded by the HeNB GW refers to: HeNB GW acquisition With the authorized QoS, it can be known that the fixed network can provide certain resource guarantee for the HeNB. Before the UE initiates an attach or PDN connection establishment by the HeNB, the other UE may already occupy a certain resource (fixed network resource) of the HeNB, and after the HeNB GW deducts the used resources from the authorized resources, the remaining solid The status of the network resources is referred to herein as "current fixed network resource usage status".
  • Step 505. The HeNB GW forwards an "Initial Context Setup Request/Attach Accept” message or a "Load Setup Request/PDN Connection Accept” message to the HeNB.
  • Step 506 Complete the attach/PDN connection establishment of the UE according to the HeNB existing technical operation procedure.
  • Step 505 The HeNB GW feeds back to the core network (here, the MME) a response that the attach/PDN connection establishment fails.
  • the core network here, the MME
  • Step 506 Perform related processing on the attachment/PDN connection establishment failure according to the HeNB prior art.
  • FIG. 6 is a schematic flowchart of a process performed by a HeNB to perform admission control when a terminal or a core network side initiates a dedicated bearer setup or modification operation after the UE is attached by the HeNB according to the embodiment of the present invention. As shown in FIG. 6, the process includes:
  • Step 601 The HeNB is powered on and completes registration, and the HeNB GW acquires the QoS of the fixed network authorization, and the UE attaches to the EPS network through the HeNB.
  • the UE or the network side initiates the establishment or modification of the dedicated bearer.
  • the message flow reaches the EPS core network element MME.
  • Step 602 If it is a proprietary bearer establishment process, the EPS core network (here, the network element MME) sends a "bearer setup request/session management request" message to the HeNB; if it is a bearer modification process, the EPS core network (here is the network)
  • the element MME sends a "bearer modification request/session management request" message to the HeNB.
  • Step 603 The HeNB GW intercepts the "bearer setup request/session management request" message or the "bearer modification request/session management request” message sent by the MME to the HeNB, and according to the current fixed network resource usage status and interception message recorded by the HeNB GW. Admission decisions are made by the requested resource, and the type and level of the user/bearer.
  • the results of the HeNB GW's admission decision are: Acceptance of success and rejection of admission. The following two categories are discussed.
  • Step 604 The HeNB GW forwards the bearer setup request/session management request message or the bearer modification request/session management request message to the HeNB.
  • Step 605 Perform a dedicated bearer setup/bearer modification operation according to the HeNB existing technical operation procedure.
  • Step 604 The HeNB GW feeds back a response to the failure of the dedicated bearer setup/bearer modification to the core network (here, the MME).
  • Step 605 Perform related processing on the failure of the dedicated bearer setup/bearer modification according to the HeNB existing technology.
  • FIG. 7 is a schematic flowchart of a process for the HeNB to perform resource update registration when the UE or the core network side initiates a dedicated bearer deactivation operation after the UE is attached by the HeNB according to the embodiment of the present invention. As shown in FIG. 7, the process includes:
  • Step 701 The HeNB is powered on and completes registration, and the HeNB GW acquires the QoS of the fixed network authorization.
  • the UE is attached to the EPS network through the HeNB.
  • the UE or the network side initiates a deactivation operation of the dedicated bearer, and after the processing of the relevant network element, the message flow reaches the EPS core network element MME.
  • Step 702 The EPS core network (here, the network element MME) sends a bearer activation request message to the HeNB.
  • Step 703 The HeNB GW intercepts the "deactivation request" message sent by the MME to the HeNB, and updates the registered current fixed network resource usage status according to the content in the message.
  • This step is an optional step.
  • Step 704 The HeNB GW "bearer deactivation request" message is forwarded to the HeNB.
  • Step 705 The bearer deactivates the air interface resource, which is a prior art.
  • Step 706 The HeNB feeds back the bearer deactivation response/bearer context deactivation accept message to the core network (here, the MME), and carries a success or failure indication.
  • the core network here, the MME
  • Step 707 The HeNB GW intercepts the deactivation response/load context deactivation accept message sent by the HeNB to the MME, and updates the registered current fixed network resource usage status according to the content in the message.
  • Step 708 The HeNB GW forwards the "bearer deactivation response/bearer context deactivation accept" message to the core network (here, the MME).
  • the core network performs related processing according to the message.
  • FIG. 8 is a schematic flowchart of a process for registering a resource update by a HeNB when a terminal or a network side initiates a user detach operation after the terminal is attached by the HeNB according to Embodiment 5 of the present invention. As shown in FIG. 8, the process includes:
  • Step 801 The HeNB is powered on and completes registration, and the HeNB GW acquires the QoS of the fixed network authorization, and the UE attaches to the EPS network through the HeNB.
  • the UE or the network side initiates a user detach operation, and after processing by the relevant network element, the message flow reaches the EPS core network element MME.
  • Step 802 The EPS core network (here, the network element MME) sends an "S1 interface UE context release command" message to the HeNB.
  • This step is an optional step.
  • Step 804 The HeNB GW forwards the "SI Interface UE Context Release Command" message to the HeNB 0.
  • Step 805 The bearer deactivates the air interface resource and releases the Radio Resource Control (RRC) connection.
  • RRC Radio Resource Control
  • Step 806 The HeNB feeds back the "S1 interface UE context release complete" message to the core network (here, the MME), and carries a success or failure indication.
  • the core network here, the MME
  • Step 807 The HeNB GW intercepts the "SI interface UE context release completion" message sent by the HeNB to the MME, and updates the registered current fixed network resource usage status according to the content in the message.
  • Step 808 The HeNB GW forwards the "S1 Interface UE Context Release Complete" message to the core network (here, the MME).
  • the core network performs related processing according to the message.
  • this embodiment describes the user detach procedure. Similarly, the PDN connection is released, and the HeNB GW also re-registers and records the resources, except that the SI interface UE context release command/completion is completed. "The message corresponding to the change to "bearing deactivation request / response" signaling can be.
  • FIG. 9 is a schematic flowchart of the admission control of the HeNB GW according to Embodiment 6 of the present invention. As shown in FIG. 9, the process includes: Steps 901-902: Same as steps 601-602.
  • Step 903 The HeNB GW intercepts the bearer setup request/load modification request/session management request message sent by the MME to the HeNB, and performs admission control according to the message content and the current fixed network resource usage status.
  • the HeNB GW finds that the currently available fixed network resources are no longer able to satisfy the dedicated bearer.
  • the HeNB GW performs preemptive admission control according to the QoS level of the bearer, the level of the PDN connection to which the bearer belongs, and the level of the user. For example, if the priority of the newly created bearer is higher than the established bearer priority, the HeNB GW deactivates the established bearer and releases the resources, thereby preempting the new bearer by preempting the resources of the existing service.
  • Steps 904-905 The HeNB GW sends a deactivation request to the HeNB, and the HeNB performs corresponding bearer release.
  • the deactivated bearer corresponding resource is released.
  • the admission control is performed by the MME.
  • the MME obtains the authorized QoS information from the fixed network and stores it.
  • the terminal/network performs operations such as HeNB attach/access/PDN connection establishment/bearer setup/bearer modification/de-attachment/PDN connection release
  • the MME implements admission control for the service/user according to the authorized QoS, service level, user level, and the like. Or manage resources.
  • This embodiment is equivalent to migrating the function modules of the HeNB GW in the embodiments 1 to 6 for obtaining the authorization QoS information, the service admission control, and the resource update registration to the MME.
  • the HeNB GW Since the HeNB GW does not exist, the HeNB registers with the MME directly, and the MME requests the authorized QoS from the fixed network through the HeNB PF.
  • the specific process is shown in FIG. 10, and the description of the process corresponds to the description of FIG. 4.
  • the modification is only to replace the HeNB GW with the MME.
  • the MME before the EPS core network/MME sends a message such as a dedicated bearer setup request, an initial context setup, an attach accept, a PDN connection accept, a bearer modification request, a session management request, and an S1 interface UE context deletion to the HeNB, the MME The admission decision is first based on the authorized QoS/current fixed network resource usage status, and then an instruction is sent to the HeNB according to the decision result.
  • a message such as a dedicated bearer setup request, an initial context setup, an attach accept, a PDN connection accept, a bearer modification request, a session management request, and an S1 interface UE context deletion to the HeNB.
  • the HeNB performs the admission control, and the HeNB sends the QoS request directly to the HeNB in the power-on registration process to obtain the authorized QoS (as shown in FIG. 11) or obtains the QoS of the authorized press through the HeNB GW.
  • the HeNB stores the authorized QoS information.
  • the terminal performs operations such as attach, access, PDN connection establishment, bearer establishment, bearer modification, detachment, and PDN connection release through the HeNB
  • the HeNB implements admission control on the service/user according to the authorized QoS, service level, user level, and the like. Or manage resources.
  • This embodiment is equivalent to migrating the function module of HeNB GW service admission control and resource update registration to the HeNB.
  • the above solution is also applicable to the HNB, and only needs 4 B HeNB, HeNB GW, and MME corresponding to HNB, HNB GW, and SGSN.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种控制业务接纳的方法,包括:演进家庭基站(HeNB)/家庭基站(HNB)上电时,接纳控制网元从固网获取授权资源信息;所述接纳控制网元根据所述授权资源信息,对从所述HeNB/HNB接入的用户(UE)进行接纳控制。本发明还相应地公开了一种控制业务接纳的系统。本发明在UE通过HeNB/HNB接入核心网的场景下,只有在保证固网和移动网均有足够的资源时,核心网才接纳UE发起的业务,所以,本发明能够提高系统控制业务接纳的性能,同时提高系统的资源管理能力,从而保障UE访问业务的QoS,提高用户体验。

Description

一种控制业务接纳的方法及系统 技术领域
本发明涉及无线通信领域, 尤其涉及一种控制业务接纳的方法及系统。 背景技术
第三代合作伙伴计划 ( 3rd Generation Partnership Project, 3GPP ) 的演 进的分组系统( Evolved Packet System, EPS ) 由演进的通用地面无线接入 网 ( Evolved Universal Terrestrial Radio Access Network, E-UTRAN )、 移动 管理单元( Mobility Management Entity, MME )、服务网关( Serving Gateway, S-GW )、 分组数据网络网关( Packet Data Network Gateway, P-GW ), 归属 用户服务器( Home Subscriber Server, HSS )组成。
图 1是根据相关技术的非漫游场景下的演进家庭基站(Home evolved NodeB , HeNB )接入 EPS的架构示意图, 如图 1所示, MME与 EUTRAN、 S-GW和家庭基站网关 (HeNB GW )相连接, 负责移动性管理、 非接入层 信令的处理和用户移动管理上下文的管理等控制面的相关工作; S-GW是与 E-UTRAN相连的接入网关设备, 在 E-UTRAN和 P-GW之间转发数据, 并 且负责对寻呼等待数据进行緩存; P-GW则是 EPS与分组数据网络( Packet Data Network, PDN ) 网络的边界网关, 负责 PDN的接入及在 EPS与 PDN 间转发数据等功能。
如果 EPS系统支持策略计费控制(Policy and Charging Control, PCC ), 则策略和计费规则功能(Policy and Charging Rules Function, PCRF )进行 策略和计费规则的制定, 它通过接口 Rx 和运营商网络协议 ( Internet Protocol , IP ) 业务网络中的应用功能( Application Function , AF )相连, 获取业务信息, 用于生成 PCC策略的业务信息。 当 S-GW与 P-GW之间的 S5接口采用 GTP协议时, P-GW中驻留了策略和计费执行功能( Policy and Charging Enforcement Function, PCEF ), PCRF与 P-GW间通过 Gx接口交 换信息, 负责发起承载的建立、 修改和释放, 保证业务数据的服务质量 ( Quality of Service, QoS ), 并进行计费控制。 当 S-GW与 P-GW的 S5接 口采用代理移动 IP ( Proxy Mobile IP, PMIP ) 时, S-GW中驻留承载绑定 和事件报告功能( Bearer Binding and Event Report Function, BBERF ), 并且 S-GW与 PCRF之间通过 Gxc接口交换信息, 由 BBERF负责发起承载的建 立、 修改和释放, 保证业务数据的服务质量, 由 PCEF进行计费控制。
EPS支持 HeNB的接入, HeNB是一种小型、低功率的基站, 部署在家 庭、 办公室及企业大楼等室内场所。 闭合用户组(Closed Subscriber Group, CSG )是引入家庭基站后提出的概念。 通常一个家庭或者一个企业内部的 用户组成一个闭合用户组, 这个闭合用户组用 CSG ID进行标识。 为这个闭 合用户组内用户服务的家庭基站具有相同的 CSG ID。 当一个闭合用户组只 由一个家庭基站服务时, 该闭合用户组也可以直接采用家庭基站标识(例 如 BS ID )来进行标识。根据家庭基站管理者的意愿, CSG用户和 /或非 CSG 用户可以区分不同的等级, 优先级不同则其享受的业务优先级, 享受服务 质量和业务类别都可以不同。 用户通过与运营商签约可以接入到多个闭合 用户组所对应的家庭基站, 例如, 用户的办公场所、 家庭等。 因此引入了 允许闭合用户组列表的概念。 这个列表保存在用户的终端和网络侧的用户 数据服务器中。
家庭基站的使用模式分为三种: 闭合模式、 混合模式和开放模式。 当 家庭基站是闭合模式的时候, 只有该家庭基站所属 CSG签约用户可以接入 该基站并享受基站提供的业务; 当家庭基站是开放模式的时候, 任何运营 商签约用户都可以接入该基站, 此时的家庭基站等同于宏基站使用; 当家 庭基站是混合模式的时候, 同样允许任何运营商签约用户或者漫游用户接 入使用, 但是要根据用户是否签约 CSG的信息区分不同的级别, 也就是说 签约该 CSG的用户在使用混合型家庭基站的时候具有更高的业务优先级, 享受更好的服务质量和业务类别。
HeNB通常通过租用的固网线路接入 EPS的核心网 (如图 1所示), 为 了保障接入的安全, 核心网中引入安全网关( Security Gateway, SeGW )进 行屏蔽, HeNB与 SeGW之间的数据将采用因特网协议安全性( IP Security, IPSec )进行封装。 HeNB可以通过与 SeGW建立的 IPSec隧道直接连接到 核心网的 MME和 S-GW,也可以再通过 HeNB GW连接到 MME和 S-GW。
此夕卜 ,通用移动通信系统( Universal Mobile Telecommunications System, UMTS )支持家庭基站 HNB ( Home NodeB )的接入。 图 2是根据相关技术 的非漫游场景下的 HNB接入 UMTS的架构示意图, 图 2中的架构与图 1 的架构类似, 不同的是, 使用服务通用分组无线业务支撑节点 (Serving General Packet Radio Service Support Node, SGSN )代替了 S-GW, 使用网 关通用分组无线业务支持节点 (Gateway General Packet Radio Service Supporting Node, GGSN )代替了 P-GW。
在当前的研究进程中, 已经有一些架构性的初步方案用于实现对业务 的接纳管理和资源管理,如图 1所示, HeNB策略功能实体( Policy Function, HeNB PF )设置于 3GPP HeNB子系统(由 SeGW、 HeNB GW以及其他网 元, 比如 HeMS等构成 )和宽带论坛策略控制功能实体( BroadBand Forum Policy Control Function, BBF BPCF )之间, 实现对业务接纳管理和移动网 资源管理。
但是, 在用户通过 HeNB/HNB接入核心网的场景下, 由于 HeNB/HNB 接入的固网线路的 QoS通常是受到 HeNB/HNB的拥有者与固网运营商的签 约限制的。 因此, 当 UE通过 HeNB/HNB接入 3GPP核心网访问业务时 , 所需的 QoS不能超过固网运营商所能提供的固网线路的签约的 QoS,否贝' J , UE访问业务的 QoS将得不到保障,特别是保障比特率(Guaranteed Bitrate, GBR )的业务更是如此。 因此, 对于 3GPP网络和固网来说, 当有新的业务 发起的时候, 只有在固网保证有足够的资源 /带宽, 兼顾考虑移动网资源也 充足的条件下, 才能接纳该业务, 否则, 就应该拒绝该业务。 发明内容
有鉴于此, 本发明的主要目的在于提供一种控制业务接纳的方法及系 统, 能够提高系统控制业务接纳的性能, 同时提高系统的资源管理能力, 从而保障 UE访问业务的 QoS, 提高用户体验。
为达到上述目的, 本发明的技术方案是这样实现的:
一种控制业务接纳的方法, 包括:
演进家庭基站 HeNB/家庭基站 HNB上电时,接纳控制网元从固网获取 授权资源信息;
所述接纳控制网元根据所述授权资源信息, 对从所述 HeNB/HNB接入 的用户 UE进行接纳控制。
所述授权资源信息为授权的服务质量 QoS,
所述授权的 QoS包括以下一项或多项: 带宽、 服务质量等级标识、 保 证比特率。
HeNB 上电的情况下, 所述接纳控制网元为演进家庭基站网关 HeNB GW、 移动管理单元 MME或 HeNB; HNB上电的情况下, 所述接纳控制网 元为家庭基站网关 HNB GW或 HNB。
接纳控制网元为 HeNB GW的情况下, 所述 HeNB上电时, 接纳控制 网元从固网获取授权资源信息为:
HeNB上电并到 HeNB GW注册, HeNB GW向演进家庭基站策略功能 实体请求授权的 QoS;
演进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并 在获取授权的 QoS后将其反馈给 HeNB GW, HeNB GW存储所述 QoS。 接纳控制网元为 HNB GW的情况下 , 所述 HNB上电时, 接纳控制网 元从固网获取授权资源信息为:
HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体请 求授权的 QoS;
家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并在获 取授权的 QoS后将其反馈给 HNB GW, HNB GW存储所述 QoS。
接纳控制网元为 MME的情况下, 所述 HeNB上电时, 接纳控制网元 从固网获取授权资源信息为:
HeNB上电并到 MME注册, MME向演进家庭基站策略功能实体请求 授权的 QoS;
演进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并 将获取的授权的 QoS反馈给 MME, MME存储该 QoS。
接纳控制网元为 HeNB的情况下, 所述 HeNB上电时, 接纳控制网元 从固网获取授权资源信息为:
HeNB上电并到 HeNB GW/MME注册, HeNB GW/MME向演进家庭基 站策略功能实体请求授权的 QoS; 演进家庭基站策略功能实体向固网资源 管理单元请求授权的 QoS,并将获取的授权的 QoS反馈给 HeNB GW/MME; HeNB GW/MME将所述授权的 QoS发送给 HeNB, HeNB存储所述授权的 QoS, 或者,
HeNB上电后向演进家庭基站策略功能实体请求授权的 QoS;演进家庭 基站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取到的授 权的 QoS反馈给 HeNB, HeNB存储所述授权的 QoS。
接纳控制网元为 HNB的情况下 , 所述 HNB上电时, 接纳控制网元从 固网获取授权资源信息为: HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体请 求授权的 QoS; 家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取的授权的 QoS反馈给 HNB GW; HNB GW将所述授权的 QoS反馈给 HNB, HNB存储所述授权的 QoS, 或者,
HNB上电后向家庭基站策略功能实体请求授权的 QoS; 家庭基站策略 功能实体向固网资源管理单元请求授权的 QoS, 并将获取到的授权的 QoS 反馈给 HNB, HNB存储所述授权的 QoS。
所述接纳控制网元从固网获取授权资源信息为: 固网在授权的资源信 息发生变化时, 主动将修改后的授权资源信息经家庭基站策略功能实体发 送给接纳控制网元。
所述向固网资源管理单元请求授权的 QoS时携带隧道信息 /本地信息, 固网资源管理单元根据所述隧道信息 /本地信息查找 HeNB/HNB 所在的回 程网, 并根据当前回程网资源的使用状况为所述 HeNB/HNB授权 QoS。
接纳控制网元为 HeNB GW/HNB GW的情况下, 所述隧道信息 /本地信 息由 HeNB/HNB本身携带和 /或由 SeGW封装到 HeNB/HNB注册信息中发 送给 HeNB GW /HNB GW; 接纳控制网元为 MME的情况下, 所述隧道信 息 /本地信息由 HeNB本身携带和 /或由 SeGW封装到 HeNB注册信息中发送 给 MME; 接纳控制网元为 HeNB/HNB的情况下, 所述隧道信息 /本地信息 由 HeNB/HNB 自身获取。
所述隧道信息 /本地信息包括以下一种或多种: 固网为终端分配的 IP地 址、 网络地址转换 NAT转换后的地址和端口号; SeGW为终端分配的 IP地 址及端口号、 SeGW地址及端口号、 HeNB 的标识。
所述固网资源管理单元为 BPCF, 所述演进家庭基站策略功能实体 /家 庭基站策略功能实体为 HeNB PF/HNB PF。
该方法还包括: 所述固网向所述接纳控制网元返回授权资源信息时携带半静态指示, 所述接纳控制网元收到所述半静态指示后, 根据所述授权资源信息进 行接纳控制, 不再向固网查询。
该方法还包括: 接纳控制网元记录当前固网资源的使用状态。
所述接纳控制网元根据所述授权资源信息, 对从所述 HeNB/HNB接入 的 UE进行接纳控制为:
当 UE接入所述 HeNB/HNB、通过所述 HeNB/HNB发起附着、建立 PDN 连接请求、 承载建立 /修改 /删除请求, 或者核心网络侧发起承载建立 /修改 / 删除请求时, 所述接纳控制网元根据固网反馈的 QoS进行接纳决策, 即当 固网资源满足时, 接纳控制网元接受所述请求; 固网资源不满足时, 接纳 控制网元拒绝所述请求, 或者, 所述接纳控制网元决定抢占现有已使用的 资源来满足所述请求。
一种控制业务接纳的系统, 包括: HeNB/ HNB、 接纳控制网元和固网; 其中,
所述接纳控制网元, 用于在 HeNB/ HNB上电时, 从固网获取授权资源 信息; 以及根据固网返回的授权资源信息, 对从所述 HeNB/HNB 接入的
UE进行接纳控制;
所述固网, 用于提供 HeNB/ HNB的授权资源信息。
所述固网返回的授权资源信息为授权的服务质量 QoS。
HeNB 上电的情况下, 所述接纳控制网元为演进家庭基站网关 HeNB
GW、 移动管理单元 MME或 HeNB; HNB上电的情况下, 所述接纳控制网 元为家庭基站网关 HNB GW或 HNB。
所述 HeNB上电时, 接纳控制网元从固网获取授权资源信息为: HeNB上电并到 HeNB GW注册, HeNB GW向演进家庭基站策略功能 实体演进家庭基站策略功能实体请求授权的 QoS; 演进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并 在获取授权的 QoS后将其反馈给 HeNB GW, HeNB GW存储所述 QoS。
所述在 HNB上电时, 接纳控制网元从固网获取授权资源信息为: HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体家 庭基站策略功能实体请求授权的 QoS;
家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并在获 取授权的 QoS后将其反馈给 HNB GW, HNB GW存储所述 QoS。
所述在 HeNB上电时, 接纳控制网元从固网获取授权资源信息为: HeNB上电并到 MME注册 , MME向演进家庭基站策略功能实体请求 授权的 QoS;
演进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并 将获取的授权的 QoS反馈给 MME, MME存储该 QoS。
所述在 HeNB上电时, 接纳控制网元从固网获取授权资源信息为: HeNB上电并到 HeNB GW/MME注册, HeNB GW/MME向演进家庭基 站策略功能实体请求授权的 QoS; 演进家庭基站策略功能实体向固网资源 管理单元请求授权的 QoS,并将获取的授权的 QoS反馈给 HeNB GW/MME;
HeNB GW/MME将所述授权的 QoS反馈给 HeNB, HeNB存储所述授权的
QoS,
或者, HeNB上电后向演进家庭基站策略功能实体请求授权的 QoS; 演 进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取 到的授权的 QoS反馈给 HeNB, HeNB存储所述授权的 QoS。
在 HNB上电时, 接纳控制网元从固网获取授权资源信息为:
HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体请 求授权的 QoS; 家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取的授权的 QoS反馈给 HNB GW; HNB GW将所述授权的 QoS反馈给 HNB, HNB存储所述授权的 QoS,
或者, HNB上电后向家庭基站策略功能实体请求授权的 QoS; 家庭基 站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取到的授权 的 QoS反馈给 HNB, HNB存储所述授权的 QoS。
所述接纳控制网元从固网获取授权资源信息为: 固网在授权的资源信 息发生变化时, 主动将修改后的授权资源信息经家庭基站策略功能实体发 送给接纳控制网元。
所述向固网资源管理单元请求授权的 QoS时携带隧道信息 /本地信息, 固网资源管理单元根据所述隧道信息 /本地信息查找 HeNB/HNB 所在的回 程网, 并根据当前回程网资源的使用状况为所述 HeNB/HNB授权 QoS。
接纳控制网元为 HeNB GW/HNB GW的情况下, 所述隧道信息 /本地信 息由 HeNB/HNB本身携带和 /或由 SeGW封装到 HeNB/HNB注册信息中发 送给 HeNB GW /HNB GW; 接纳控制网元为 MME的情况下, 所述隧道信 息 /本地信息由 HeNB本身携带和 /或由 SeGW封装到 HeNB注册信息中发送 给 MME; 接纳控制网元为 HeNB/HNB的情况下, 所述隧道信息 /本地信息 由 HeNB/HNB 自身获取。
所述隧道信息 /本地信息包括以下一种或多种: 固网为终端分配的 IP地 址、 网络地址转换 NAT转换后的地址和端口号; SeGW为终端分配的 IP地 址及端口号、 SeGW地址及端口号、 HeNB 的标识。
所述固网资源管理单元为 BPCF, 所述演进家庭基站策略功能实体 /家 庭基站策略功能实体为 HeNB PF/HNB PF。
所述固网, 还用于在向所述接纳控制网元返回授权资源信息时携带半 静态指示;
所述接纳控制网元, 还用于在收到所述半静态指示后, 根据所述授权 资源信息进行接纳控制, 不再向固网查询。 所述接纳控制网元, 还用于记录当前固网资源的使用状态。 所述接纳控制网元根据所述授权资源信息, 对从所述 HeNB/HNB接入 的 UE进行接纳控制为:
当 UE接入所述 HeNB/HNB、通过所述 HeNB/HNB发起附着、建立 PDN 连接请求、 承载建立 /修改 /删除请求, 或者核心网络侧发起承载建立 /修改 / 删除请求时, 所述接纳控制网元根据固网反馈的 QoS进行接纳决策, 即当 固网资源满足时, 接纳控制网元接受所述请求; 固网资源不满足时, 接纳 控制网元拒绝所述请求, 或者, 所述接纳控制网元决定抢占现有已使用的 资源来满足所述请求。
本发明控制业务接纳的方法及系统, 在 UE通过 HeNB/HNB接入核心 网的场景下, 只有在保证固网和移动网均有足够的资源时, 核心网才接纳 UE发起的业务, 所以, 本发明能够提高系统控制业务接纳的性能, 同时提 高系统的资源管理能力,从而进一步保障 UE访问业务的 QoS,提高用户体 验。 附图说明
图 1为根据相关技术的非漫游场景下的 HeNB接入 EPS的架构示意图; 图 2为根据相关技术的非漫游场景下的 HNB接入 UMTS的架构示意 图;
图 3为本发明控制业务接纳的方法流程示意图;
图 4为本发明实施例 1 HeNB上电注册流程示意图;
图 5为本发明实施例 2 UE在通过 HeNB附着或 PDN连接建立时, HeNB GW进行接纳控制的流程示意图;
图 6为本发明实施例 3 UE通过 HeNB附着之后,终端或者核心网侧发 起专有承载建立或修改操作时, HeNB执行接纳控制的流程示意图;
图 7为本发明实施例 4 UE通过 HeNB附着之后, UE或者核心网侧发 起专有承载去激活操作时, HeNB执行资源更新登记的流程示意图; 图 8为本发明实施例 5终端通过 HeNB附着之后, 终端或者网络侧发 起用户去附着操作时, HeNB执行资源更新登记的流程示意图;
图 9为本发明实施例 6 HeNB GW进行接纳控制的流程示意图; 图 10为本发明实施例 7 HeNB上电时, MME获取授权的 QoS的流程 示意图;
图 11为本发明实施例 8 HeNB上电时, HeNB获取授权的 QoS的一种 流程示意图;
图 12为本发明实施例 8 HeNB上电时, HeNB获取授权的 QoS的另一 种流程示意图。 具体实施方式
本发明的基本思想是: 在 UE通过 HeNB/HNB接入核心网的场景下, 只有在保证固网和移动网均有足够的资源时, 核心网才接纳 UE发起的业 务。
图 3为本发明实施例控制业务接纳的方法流程示意图, 如图 3所示, 该方法包括:
步驟 301: HeNB/HNB 上电时, 接纳控制网元从固网获取授权资源信 这里, 所述授权资源信息一般指授权的 QoS, 所述授权的 QoS可以包 括以下一项或多项: 带宽、 服务质量等级标识、 保证比特率。 固网指固定 接入网络, 包括现有的无线局域网、 非对称数字用户环路( Asymmetric Digital Subscriber Line, ADSL )接入等。
需要说明的是, HeNB上电的情况下,所述接纳控制网元为 HeNB GW、 MME或 HeNB; HNB上电的情况下, 所述接纳控制网元为 HNB GW或 HNB, 具体的: 当接纳控制网元为 HeNB GW/HNB GW时, HeNB/HNB上电并到 HeNB GW/HNB GW注册, HeNB GW/HNB GW向 HeNB PF/HNB PF请求授权的 QoS (即为该 HeNB/HNB可以保证的 QoS ); HeNB PF/HNB PF向固网资源 管理单元( BPCF )请求授权的 QoS, HeNB PF/HNB PF获取授权的 QoS后 将其反馈给 HeNB GW/HNB GW, HeNB GW/HNB GW存储该 QoS。 当 UE 接入所述 HeNB顯 B、 UE通过所述 HeNB/HNB附着、 建立 P 连接、 请 求承载建立 /修改, 或者核心网络侧请求承载建立 /修改时, HeNB GW/HNB GW根据固网反馈的 QoS、 当前资源的使用状况以及现有的自身机制决策 该业务是否可以被接纳。
当接纳控制网元为 MME时, HeNB上电并到 MME注册, MME向 HeNB PF请求授权的 QoS; HeNB PF向固网资源管理单元( BPCF )请求授 权的 QoS, HeNB PF获取到所述的 QoS后将其反馈给 MME, MME存储该 QoS。 当 UE接入所述 HeNB/HNB、 UE通过该 HeNB附着、 建立 PDN连 接、 请求承载建立 /修改, 或者核心网络侧请求承载建立 /修改时, MME根 据固网反馈的 QoS、 当前资源的使用状况以及现有的自身机制决策该业务 是否可以被接纳。
当接纳控制网元为 HeNB /HNB时, HeNB /HNB可以上电并到 HeNB GW/HNB GW注册, HeNB GW/HNB GW向 HeNB PF/HNB PF请求授权的 QoS; HeNB PF/HNB PF向固网资源管理单元( BPCF )请求授权的 QoS; HeNB PF/HNB PF获取到授权的 QoS后将其反馈给 HeNB GW/HNB GW; HeNB GW/HNB GW将该 QoS反馈给 HeNB/HNB, HeNB/HNB存储该 QoSo 或者, HeNB /HNB上电后, 可以向 HeNB PF /HNB PF请求授权的 QoS (为该 HeNB/HNB可以保证的 QoS ); HeNB PF/HNB PF向固网资源管 理单元( BPCF )请求授权的 QoS, HeNB PF/HNB PF获取到所述的 QoS将 其反馈给 HeNB/HNB, HeNB/HNB存储该 QoS。 之后, 当 UE接入所述 HeNB顯 B、 UE通过该 HeNB/HNB发起附着、 建立 P 连接请求、 请求 承载建立 /修改 /删除请求,或者核心网络侧发起承载建立 /修改 /删除请求时, HeNB/HNB根据固网反馈的 QoS、 当前资源的使用状况以及现有的自身机 制决策该业务是否可以被接纳。
当然, 也可以由固网在授权的资源信息发生变化时, 主动将修改后的 授权资源信息经家庭基站策略功能实体发送给接纳控制网元。
需要说明的是, 上述方案中, 接纳控制网元向 HeNB策略控制功能实 体( PF ), HeNB PF在向固网 BPCF请求授权的 QoS时携带隧道信息 /本地 信息, BPCF根据所述隧道信息 /本地信息查找 HeNB/HNB所在的回程网, 并根据当前回程网资源的使用状况为所述 HeNB/HNB授权 QoS。 所述隧道 信息 /本地信息可以包括以下信息中的一种或者几种: 固网为终端分配的 IP 地址、 SeGW为终端分配的 IP地址、 SeGW地址、 网络地址转换( Network Address Translation, NAT )转换后的地址和端口号、 HeNB 的标识。
需要说明的是, HeNB GW /HNB GW作为接纳控制网元时, 隧道信息 / 本地信息可以 HeNB/ HNB本身携带和 /或由 SeGW封装到 HeNB/HNB注册 信息中发送给 HeNB GW /HNB GW; MME作为接纳控制网元时, 隧道信 息 /本地信息可以由 HeNB本身携带和 /或由 SeGW封装到 HeNB注册信息中 发送给 MME; HeNB/ HNB作为接纳控制网元时,隧道信息 /本地信息 HeNB/ HNB自身获取。
固网可以根据隧道信息 /本地信息判断该 HeNB所在的位置以及该位置 上可以提供的授权的 QoS, 固网还可以结合所述 HeNB/HNB等级等因素确 定授权资源。
需要说明的是,接纳控制网元为 HeNB时,可以到 MME注册,由 MME 将授权的 QoS反馈给 HeNB/HNB , 流程与上述到 HeNB GW注册类似, 在 此不作详细描述。 固网向所述接纳控制网元返回相应的授权资源信息时, 还可以携带半 静态指示, 表明该授权资源在 HeNB/HNB注册状态下是有效的, 接纳控制 网元收到所述半静态指示, 则可以根据所述授权资源信息进行接纳控制, 不再向固网查询。
步驟 302 : 所述接纳控制网元根据所述授权资源信息, 对从所述 HeNB/HNB接入的 UE进行接纳控制。
具体的 , 当 UE接入所述 HeNB/HNB、通过所述 HeNB/HNB发起附着、 建立 PDN连接请求、 承载建立 /修改 /删除请求, 或者核心网络侧发起承载 建立 /修改 /删除请求时,所述接纳控制网元根据固网反馈的 QoS进行接纳决 策, 即当固网资源满足时, 接纳控制网元接受所述请求; 固网资源不满足 时, 接纳控制网元拒绝所述请求, 或者, 所述接纳控制网元决定抢占现有 已使用的资源来满足所述请求。
通常,接纳控制包含两个方面: 1、 用户接入/ PDN连接的接纳控制; 2、 承载发起的接纳控制。
具体的 , 当 UE接入所述 HeNB/HNB、通过所述 HeNB/HNB附着 /建立 PDN连接、请求承载建立 /修改, 或者核心网络侧请求承载建立 /修改时, 所 述 HeNB/HNB根据固网反馈的 QoS进行接纳决策。
需要说明的是, 接纳控制的过程中也涉及相关的资源管理, 一般的, 当 UE或者核心网侧发起去附着、 释放 PDN连接、 请求承载释放时, 接纳 控制网元记录当前固网资源的使用状态。
本发明还提出一种控制业务接纳的系统, 该系统包括: HeNB/ HNB、 接纳控制网元和固网; 其中,
所述接纳控制网元, 用于在 HeNB/ HNB上电时, 从固网获取授权资源 信息; 以及根据固网返回的授权资源信息, 对从所述 HeNB/HNB 接入的 UE进行接纳控制; 所述固网, 用于提供 HeNB/ HNB的授权资源信息。
所述固网返回的授权资源信息为授权的服务质量 QoS。
HeNB 上电的情况下, 所述接纳控制网元为演进家庭基站网关 HeNB
GW、 移动管理单元 MME或 HeNB; HNB上电的情况下, 所述接纳控制网 元为家庭基站网关 HNB GW或 HNB。
所述 HeNB上电时, 接纳控制网元从固网获取授权资源信息为: HeNB上电并到 HeNB GW注册, HeNB GW向演进家庭基站策略功能 实体 HeNB PF请求授权的 QoS;
HeNB PF向固网资源管理单元 BPCF请求授权的 QoS, 并在获取授权 的 QoS后将其反馈给 HeNB GW, HeNB GW存储所述 QoS。
所述在 HNB上电时, 接纳控制网元从固网获取授权资源信息为: HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体
HNB PF请求授权的 QoS;
HNB PF向固网资源管理单元 BPCF请求授权的 QoS,并在获取授权的
QoS后将其反馈给 HNB GW, HNB GW存储所述 QoS。
所述在 HeNB上电时, 接纳控制网元从固网获取授权资源信息为: HeNB上电并到 MME注册 , MME向 HeNB PF请求授权的 QoS; HeNB PF向 BPCF请求授权的 QoS, 并将获取的授权的 QoS反馈给
MME, MME存储该 QoS。
所述在 HeNB上电时, 接纳控制网元从固网获取授权资源信息为: HeNB上电并到 HeNB GW/MME注册, HeNB GW/MME向 HeNB PF 请求授权的 QoS; HeNB PF向 BPCF请求授权的 QoS, 并将获取的授权的
QoS反馈给 HeNB GW/MME; HeNB GW/MME将所述授权的 QoS反馈给
HeNB, HeNB存储所述授权的 QoS,
或者, HeNB上电后向 HeNB PF请求授权的 QoS; HeNB PF向 BPCF 请求授权的 QoS, 并将获取到的授权的 QoS反馈给 HeNB, HeNB存储所 述授权的 QoS。
在 HNB上电时, 接纳控制网元从固网获取授权资源信息为:
HNB上电并到 HNB GW注册, HNB GW向 HNB PF请求授权的 QoS;
HNB PF向 BPCF请求授权的 QoS,并将获取的授权的 QoS反馈给 HNB GW;
HNB GW将所述授权的 QoS反馈给 HNB, HNB存储所述授权的 QoS, 或者, HNB上电后向 HNB PF请求授权的 QoS; HNB PF向 BPCF请 求授权的 QoS, 并将获取到的授权的 QoS反馈给 HNB, HNB存储所述授 权的 QoS。
所述接纳控制网元从固网获取授权资源信息还可以为: 固网在授权的 资源信息发生变化时, 主动将修改后的授权资源信息经家庭基站策略功能 实体发送给接纳控制网元。
所述向固网资源管理单元请求授权的 QoS时携带隧道信息 /本地信息, 固网资源管理单元根据所述隧道信息 /本地信息查找 HeNB/HNB 所在的回 程网, 并根据当前回程网资源的使用状况为所述 HeNB/HNB授权 QoS。
接纳控制网元为 HeNB GW/HNB GW的情况下, 所述隧道信息 /本地信 息由 HeNB/HNB本身携带和 /或由 SeGW封装到 HeNB/HNB注册信息中发 送给 HeNB GW /HNB GW; 接纳控制网元为 MME的情况下, 所述隧道信 息 /本地信息由 HeNB本身携带和 /或由 SeGW封装到 HeNB注册信息中发送 给 MME; 接纳控制网元为 HeNB/HNB的情况下, 所述隧道信息 /本地信息 由 HeNB/HNB 自身获取。
所述隧道信息 /本地信息包括以下一种或多种: 固网为终端分配的 IP地 址、 网络地址转换 NAT转换后的地址和端口号; SeGW为终端分配的 IP地 址及端口号、 SeGW地址及端口号、 HeNB 的标识。
所述固网资源管理单元为 BPCF, 所述演进家庭基站策略功能实体 /家 庭基站策略功能实体为 HeNB PF/HNB PF。
所述固网, 还用于在向所述接纳控制网元返回授权资源信息时携带半 静态指示;
所述接纳控制网元, 还用于在收到所述半静态指示后, 根据所述授权 资源信息进行接纳控制, 不再向固网查询。
所述接纳控制网元, 还用于记录当前固网资源的使用状态。
所述接纳控制网元根据所述授权资源信息, 对从所述 HeNB/HNB接入 的 UE进行接纳控制为:
当 UE接入所述 HeNB/HNB、通过所述 HeNB/HNB发起附着、建立 PDN 连接请求、 承载建立 /修改 /删除请求, 或者核心网络侧发起承载建立 /修改 / 删除请求时, 所述接纳控制网元根据固网反馈的 QoS进行接纳决策, 即当 固网资源满足时, 接纳控制网元接受所述请求; 固网资源不满足时, 接纳 控制网元拒绝所述请求, 或者, 所述接纳控制网元决定抢占现有已使用的 资源来满足所述请求。
下面结合实施例对本发明的技术方案作进一步的详细描述。
实施例 1
本实施例中 , 通过 HeNB GW做接纳控制。 HeNB在上电注册流程中 , HeNB GW从固网处获取到了授权的 QoS 信息并存储之。 当终端通过该 HeNB 附着、 接入、 DN连接建立、 承载建立、 承载修改、 去附着或 PDN 连接释放时, HeNB GW根据授权的 QoS、 业务级别、 用户级别等对业务 / 用户实施接纳控制。
图 4为本发明实施例 1 HeNB上电注册流程示意图,如图 4所示,该流 程包括:
步驟 401: HeNB上电 , 接入固网, 固网通过相关机制为 HeNB分配本 地的 IP地址, 该地址作为封装数据包的外部 IP地址。 步驟 402: HeNB和 SeGW建立 IPsec 隧道, 以保证数据在传输过程中 的安全性和完整性。
步驟 403: HeNB到 HeMS进行注册, 获取相关的配置信息。
步驟 404. HeNB向 HeNB GW注册。 注册过程中 , HeNB GW获取了该 HeNB与 SeGW之间的 IPsec隧道的隧道信息 /本地信息。
HeNB GW获取隧道信息 /本地信息的方式可以有: HeNB通过 HeNB 发向 HeNB GW的注册消息将隧道信息 /本地信息携带给 HeNB GW; 或者 在 HeNB发向 HeNB GW的注册消息经过 SeGW时, SeGW将隧道信息 /本 地信息一起发送给 HeNB GW;或者 SeGW通过单独的信令将随到信息发送 给 HeNB GWo
需要说明的是, 这种情况未必发生在 HeNB向 HeNB GW注册过程中。 步驟 405-406: HeNB GW通过 HeNB PF向固网资源管理单元(在此由 BPCF充当 )发送资源请求消息, 并携带 IPsec隧道信息 /本地信息。
步驟 407-408:固网资源管理单元(在此由 BPCF充当)根据获取的 IPsec 隧道信息 /本地信息, 查找到该 HeNB所在的回程网 (Backhaul ), 并判断当 前固网资源的使用状况,为该 HeNB授权特定的 QoS保障,并通过 HeNB PF 将资源请求应答消息返回给 HeNB GW。
固网资源管理单元在此由 BPCF充当, 具体实现依赖于固网的具体状 况, 也可以由其他的网元充当 "固网资源管理单元", 也可以由多个固网资 源管理单元(如 BPCF和 BNG/BRAS )共同协商来实现。
该授权的 QoS是固网根据固网资源使用状况、 HeNB等级、 固网用户 等级等信息为该 HeNB分配的。
授权的 QoS可以是可用带宽、 保证比特率等信息。
步驟 409: HeNB GW存储授权的 QoS, 用于后续的业务 /用户接纳控制 和资源管理。 步驟 410-412: 在 HeNB上电后处于已注册状态, 固网重新调整了对该 HeNB的授权 QoS, 此时, 固网资源管理单元(此处是 BPCF )将调整了的 授权 QoS信息通过 HeNB PF推送到 HeNB GW, HeNB GW存储授权 QoS 信息, 并用于后续的业务 /用户接纳控制和资源管理。
上述流程中的 "资源请求"、 "资源请求应答"、 "资源信息更新" 消息 名称是概括性的名称, 具体实现是可以采用不同名称的消息。 实施例 2
图 5为本发明实施例 2 UE在通过 HeNB附着或 PDN连接建立时, HeNB
GW进行接纳控制的流程示意图, 如图 5所示, 该流程包括:
步驟 501 : HeNB上电并完成注册, HeNB GW获取了固网授权的 QoS。 步驟 502: UE发起附着或者 PDN连接建立操作,无线侧及核心网的执 行相关处理, 其中包括空口、 核心网信令传送, 核心网承载建立, PCC会 话建立和策略下发等。
步驟 503: 如果是附着流程, EPS核心网 (例如 MME ) 向 HeNB发送 "初始上下文建立请求 /附着接受" 消息; 如果是 PDN连接建立流程, EPS 核心网 (例如 MME )向 HeNB发送 "承载建立请求/ PDN连接接受" 消息。
其中 PDN连接建立操作时这样的一类操作:终端在附着到 EPS网络时, 会建立第一个 PDN连接, 称作默认 PDN连接; 之后终端还可以发起第二、 第三……个 PDN连接的建立, 建立多个附加 (Additional ) PDN连接。 流 程图中所指的 PDN连接建立指的是附加 PDN连接的建立, 下同。
步驟 504: HeNB GW截获 MME发往 HeNB的 "初始上下文建立请求 /附着接受"消息或 "承载建立请求/ PDN连接接受"消息,并根据 HeNB GW 所记录的当前固网资源使用状况、 截获消息中所请求的资源、 以及该用户 /PDN连接的种类和级别等做出接纳决策。
其中 HeNB GW所记录的当前固网资源使用状况是指: HeNB GW获取 了授权的 QoS, 即可知固网能为该 HeNB提供一定的资源保证。 在该 UE 通过该 HeNB发起附着或者 PDN连接建立之前, 可能其他的 UE已经占用 了该 HeNB的一定的资源 (固网资源), HeNB GW把授权的资源扣除掉已 经使用的资源后, 剩余的固网资源状况在此我们称作 "当前固网资源使用 状况"。
HeNB GW做接纳决策的结果有: 接纳成功和拒绝接纳。 下面对此两种 情况分类讨论:
接纳成功的情况下:
步驟 505. HeNB GW将 "初始上下文建立请求 /附着接受" 消息或 "承 载建立请求/ PDN连接接受"消息转发给 HeNB。
步驟 506: 按照 HeNB现有技术操作流程完成 UE的附着 /PDN连接建 立。
拒绝接纳的情况下:
步驟 505,: HeNB GW向核心网 (此处是 MME )反馈附着/ PDN连接 建立失败的应答。
步驟 506,:按照 HeNB现有技术对附着/ PDN连接建立失败进行相关处 理。
实施例 3
图 6为本发明实施例 3 UE通过 HeNB附着之后,终端或者核心网侧发 起专有承载建立或修改操作时, HeNB执行接纳控制的流程示意图, 如图 6 所示, 该流程包括:
步驟 601 : HeNB上电并完成注册, HeNB GW获取了固网授权的 QoS, UE通过 HeNB附着到 EPS网络。 UE或者网络侧发起专有承载的建立或者 修改操作, 经过相关网元的处理, 消息流程到了 EPS核心网网元 MME。 步驟 602: 如果是专有承载建立流程, EPS核心网(在此是网元 MME ) 向 HeNB发送 "承载建立请求 /会话管理请求"消息; 如果是承载修改流程, EPS核心网 (在此是网元 MME ) 向 HeNB发送 "承载修改请求 /会话管理 请求" 消息。
步驟 603: HeNB GW截获 MME发往 HeNB的 "承载建立请求 /会话管 理请求" 消息或 "承载修改请求 /会话管理请求" 消息, 并根据 HeNB GW 所记录的当前固网资源使用状况、 截获消息中所请求的资源、 以及该用户 / 承载的种类和级别等做出接纳决策。
HeNB GW做接纳决策的结果有: 接纳成功和拒绝接纳, 下面对此两种 情况分类讨论。
接纳成功的情况下:
步驟 604: HeNB GW会将承载建立请求 /会话管理请求" 消息或 "承载 修改请求 /会话管理请求" 消息转发给 HeNB。
步驟 605: 按照 HeNB现有技术操作流程完成专有承载建立 /承载修改 操作。
拒绝接纳的情况下:
步驟 604,: HeNB GW向核心网 (此处是 MME )反馈专有承载建立 / 承载修改失败的应答。
步驟 605,: 按照 HeNB现有技术对专有承载建立 /承载修改失败进行相 关处理。 实施例 4
图 7为本发明实施例 4 UE通过 HeNB附着之后, UE或者核心网侧发 起专有承载去激活操作时, HeNB执行资源更新登记的流程示意图, 如图 7 所示, 该流程包括:
步驟 701 : HeNB上电并完成注册, HeNB GW获取了固网授权的 QoS, UE通过 HeNB附着到 EPS网络。 UE或者网络侧发起专有承载的去激活操 作 , 经过相关网元的处理 , 消息流程到了 EPS核心网网元 MME。
步驟 702: EPS核心网 (在此是网元 MME ) 向 HeNB发送 载去激 活请求" 消息。
步驟 703: HeNB GW截获 MME发往 HeNB的 " 载去激活请求" 消 息, 并根据消息中的内容更新登记的当前固网资源使用状况。
该步驟为可选步驟。
步驟 704: HeNB GW "承载去激活请求" 消息转发给 HeNB。
步驟 705: 承载去激活空口资源, 为现有技术。
步驟 706: HeNB向核心网 (此处是 MME )反馈承载去激活响应 /承载 上下文去激活接受消息, 并携带成功或者失败指示。
步驟 707: HeNB GW截获 HeNB发往 MME的 载去激活响应 / 载 上下文去激活接受" 消息, 并根据消息中的内容更新登记的当前固网资源 使用状况。
步驟 708: HeNB GW向核心网 (此处是 MME )转发 "承载去激活响 应 /承载上下文去激活接受" 消息。 核心网根据该消息进行相关处理。 实施例 5
图 8为本发明实施例 5终端通过 HeNB附着之后, 终端或者网络侧发 起用户去附着操作时, HeNB执行资源更新登记的流程示意图,如图 8所示, 该流程包括:
步驟 801: HeNB上电并完成注册, HeNB GW获取了固网授权的 QoS, UE通过 HeNB附着到 EPS网络。 UE或者网络侧发起用户去附着操作, 经 过相关网元的处理, 消息流程到了 EPS核心网网元 MME。
步驟 802: EPS核心网 (在此是网元 MME ) 向 HeNB发送 "S1接口 UE上下文释放命令" 消息。 步驟 803: HeNB GW截获 MME发往 HeNB的 "SI接口 UE上下文释 放命令" 消息, 并根据消息中更新登记的当前固网资源使用状况。
该步驟为可选步驟。
步驟 804: HeNB GW将 "SI接口 UE上下文释放命令" 消息转发给 HeNB0
步驟 805: 承载去激活空口资源, 释放无线资源控制 (Radio Resource Control, RRC )连接。
步驟 806: HeNB向核心网 (此处是 MME )反馈 "S1接口 UE上下文 释放完成" 消息, 并携带成功或者失败指示。
步驟 807: HeNB GW截获 HeNB发往 MME的 "SI接口 UE上下文释 放完成" 消息, 并根据消息中的内容更新登记的当前固网资源使用状况。
步驟 808: HeNB GW向核心网 (此处是 MME )转发 "S1接口 UE上 下文释放完成" 消息。 核心网根据该消息进行相关处理。
需要说明的是, 该实施例描述的是用户去附着流程, 类似的, PDN连 接释放是, HeNB GW也要对资源进行重新登记和记录,不同之处在于将" SI 接口 UE上下文释放命令 /完成"消息对应的改成"承载去激活请求 /响应 "信 令即可。 实施例 6
本实施例中, UE通过 HeNB附着之后, UE或者核心网侧发起专有承 载建立 /修改操作, 需要占用更多的固网资源, HeNB GW发现当前可用的 固网资源已经不能够满足该专有承载, HeNB GW根据该承载的 QoS级别、 该承载所属 PDN连接的级别、 所属用户的级别等做接纳控制。 举例来说: 如果新建承载的优先级高于已建承载优先级, 则 HeNB GW通过去激活已 建承载,释放资源,用于新建承载的建立。图 9为本发明实施例 6 HeNB GW 进行接纳控制的流程示意图, 如图 9所示, 该流程包括: 步驟 901-902: 同步驟 601-602。
步驟 903: HeNB GW截获 MME发往 HeNB的 载建立请求 / 载修 改请求 /会话管理请求" 消息, 并根据消息内容和当前固网资源使用状况做 接纳控制。
HeNB GW 发现当前可用的固网资源已经不能够满足该专有承载, HeNB GW根据该承载的 QoS级别、 该 载所属 PDN连接的级别、 所属用 户的级别等做抢占式的接纳控制。 举例来说: 如果新建承载的优先级高于 已建承载优先级, 则 HeNB GW通过去激活已建承载, 释放资源, 从而通 过抢占现有业务的资源来接纳新建承载。
步驟 904-905: HeNB GW向 HeNB发送 载去激活请求, HeNB进行 相应的承载释放。
步驟 906-908. 被去激活承载对应资源释放。 实施例 7
本实施例中 ,通过 MME做接纳控制。 HeNB在上电注册流程中 , MME 从固网处获取到了授权的 QoS信息并存储之。 当终端 /网络通过该 HeNB附 着 /接入 /PDN连接建立 /承载建立 /承载修改 /去附着 /PDN连接释放等操作, MME根据授权的 QoS、 业务级别、 用户级别等对业务 /用户实施接纳控制 或者对资源进行管理。
本实施例相当于把实施例 1至 6中的 HeNB GW获取授权 QoS信息、 业务接纳控制、 资源更新登记的功能模块迁移到了 MME。
因为 HeNB GW不存在,故 HeNB直接向 MME注册, MME通过 HeNB PF向固网请求授权的 QoS。具体流程如图 10所示,流程描述对应图 4的描 述 , 改动只是把 HeNB GW换成 MME。
在 MME获取了授权的 QoS后, 当终端 /网络通过该 HeNB附着 /接入 /PDN连接建立 /承载建立 /承载修 ^去附着 /PDN连接释放时, MME执行接 纳控制和资源登记管理功能。 具体的实施例与实施例 2至 6对应存在并且 类似, 在此不再单独给出流程图, 具体的不同之处描述如下:
实施例 2至 6中, EPS核心网 /MME向 HeNB发送专有承载建立请求、 初始上下文建立、 附着接受、 PDN连接接受、 承载修改请求、 会话管理请 求、 S1接口 UE上下文删除等消息前, MME先根据授权的 QoS/当前固网 资源的使用状况对接纳决策, 然后根据决策结果再向 HeNB发送指令。 实施例 8
本实施例中, 通过 HeNB做接纳控制, HeNB在上电注册流程中, 直接 到 HeNB PF请求, 获取授权的 QoS (如图 11所示 )或者通过 HeNB GW获 取到授权按的 QoS后再下发到 HeNB (如图 12所示), HeNB存储授权的 QoS信息。 当终端通过该 HeNB进行附着、 接入、 PDN连接建立、 承载建 立、 承载修改、 去附着、 PDN连接释放等操作时, HeNB根据授权的 QoS、 业务级别、 用户级别等对业务 /用户实施接纳控制或者对资源进行管理。
本实施例相当于把 HeNB GW业务接纳控制、 资源更新登记的功能模 块迁移到了 HeNB。
以上方案同样适用于 HNB, 只需要 4巴 HeNB, HeNB GW, MME对应 的换成 HNB, HNB GW, SGSN即可。
显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步驟 可以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者 分布在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执 行的程序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来 执行, 并且在某些情况下, 可以以不同于此处的顺序执行所示出或描述的 步驟, 或者将它们分别制作成各个集成电路模块, 或者将它们中的多个模 块或步驟制作成单个集成电路模块来实现。 这样, 本发明不限制于任何特 定的硬件和软件结合。

Claims

权利要求书
1、 一种控制业务接纳的方法, 其特征在于, 该方法包括:
演进家庭基站 HeNB/家庭基站 HNB上电时,接纳控制网元从固网获取 授权资源信息;
所述接纳控制网元根据所述授权资源信息, 对从所述 HeNB/HNB接入 的用户 UE进行接纳控制。
2、 根据权利要求 1所述的方法, 其特征在于, 所述授权资源信息为授 权的服务质量 QoS,
所述授权的 QoS包括以下一项或多项: 带宽、 服务质量等级标识、 保 证比特率。
3、 根据权利要求 2所述的方法, 其特征在于, HeNB上电的情况下, 所述接纳控制网元为演进家庭基站网关 HeNB GW、移动管理单元 MME或 HeNB; HNB上电的情况下, 所述接纳控制网元为家庭基站网关 HNB GW 或 HNB。
4、根据权利要求 3所述的方法,其特征在于,接纳控制网元为 HeNB GW 的情况下, 所述 HeNB上电时, 接纳控制网元从固网获取授权资源信息为:
HeNB上电并到 HeNB GW注册, HeNB GW向演进家庭基站策略功能 实体请求授权的 QoS;
演进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并 在获取授权的 QoS后将其反馈给 HeNB GW, HeNB GW存储所述 QoS。
5、根据权利要求 3所述的方法,其特征在于,接纳控制网元为 HNB GW 的情况下, 所述 HNB上电时, 接纳控制网元从固网获取授权资源信息为:
HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体请 求授权的 QoS;
家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并在获 取授权的 QoS后将其反馈给 HNB GW, HNB GW存储所述 QoS。
6、 根据权利要求 3所述的方法, 其特征在于, 接纳控制网元为 MME 的情况下, 所述 HeNB上电时, 接纳控制网元从固网获取授权资源信息为:
HeNB上电并到 MME注册, MME向演进家庭基站策略功能实体请求 授权的 QoS;
演进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并 将获取的授权的 QoS反馈给 MME, MME存储该 QoS。
7、 根据权利要求 3所述的方法, 其特征在于, 接纳控制网元为 HeNB 的情况下, 所述 HeNB上电时, 接纳控制网元从固网获取授权资源信息为:
HeNB上电并到 HeNB GW/MME注册, HeNB GW/MME向演进家庭基 站策略功能实体请求授权的 QoS; 演进家庭基站策略功能实体向固网资源 管理单元请求授权的 QoS,并将获取的授权的 QoS反馈给 HeNB GW/MME; HeNB GW/MME将所述授权的 QoS发送给 HeNB, HeNB存储所述授权的 QoS, 或者,
HeNB上电后向演进家庭基站策略功能实体请求授权的 QoS;演进家庭 基站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取到的授 权的 QoS反馈给 HeNB, HeNB存储所述授权的 QoS。
8、 根据权利要求 3所述的方法, 其特征在于, 接纳控制网元为 HNB 的情况下, 所述 HNB上电时, 接纳控制网元从固网获取授权资源信息为:
HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体请 求授权的 QoS; 家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取的授权的 QoS反馈给 HNB GW; HNB GW将所述授权的 QoS反馈给 HNB, HNB存储所述授权的 QoS, 或者,
HNB上电后向家庭基站策略功能实体请求授权的 QoS; 家庭基站策略 功能实体向固网资源管理单元请求授权的 QoS, 并将获取到的授权的 QoS 反馈给 HNB, HNB存储所述授权的 QoS。
9、 根据权利要求 1所述的方法, 其特征在于, 所述接纳控制网元从固 网获取授权资源信息为: 固网在授权的资源信息发生变化时, 主动将修改 后的授权资源信息经家庭基站策略功能实体发送给接纳控制网元。
10、 根据权利要求 4至 8任一项所述的方法, 其特征在于, 所述向固 网资源管理单元请求授权的 QoS时携带隧道信息 /本地信息, 固网资源管理 单元根据所述隧道信息 /本地信息查找 HeNB/HNB所在的回程网,并根据当 前回程网资源的使用状况为所述 HeNB/HNB授权 QoS。
11、根据权利要求 10所述的方法,其特征在于,接纳控制网元为 HeNB GW/HNB GW的情况下, 所述隧道信息 /本地信息由 HeNB/HNB本身携带 和 /或由 SeGW封装到 HeNB/HNB注册信息中发送给 HeNB GW /HNB GW; 接纳控制网元为 MME的情况下, 所述隧道信息 /本地信息由 HeNB本身携 带和 /或由 SeGW封装到 HeNB注册信息中发送给 MME; 接纳控制网元为 HeNB/HNB的情况下, 所述隧道信息 /本地信息由 HeNB/HNB 自身获取。
12、 根据权利要求 11所述的方法, 其特征在于, 所述隧道信息 /本地信 息包括以下一种或多种: 固网为终端分配的 IP地址、 网络地址转换 NAT 转换后的地址和端口号; SeGW为终端分配的 IP地址及端口号、 SeGW地 址及端口号、 HeNB 的标识。
13、 根据权利要求 4至 8任一项所述的方法, 其特征在于, 所述固网 资源管理单元为 BPCF, 所述演进家庭基站策略功能实体 /家庭基站策略功 能实体为 HeNB PF/HNB PF。
14、 根据权利要求 1至 8任一项所述的方法, 其特征在于, 该方法还 包括:
所述固网向所述接纳控制网元返回授权资源信息时携带半静态指示, 所述接纳控制网元收到所述半静态指示后, 根据所述授权资源信息进 行接纳控制, 不再向固网查询。
15、 根据权利要求 1至 8任一项所述的方法, 其特征在于, 该方法还 包括: 接纳控制网元记录当前固网资源的使用状态。
16、 根据权利要求 2至 8任一项所述的方法, 其特征在于, 所述接纳 控制网元根据所述授权资源信息, 对从所述 HeNB/HNB接入的 UE进行接 纳控制为:
当 UE接入所述 HeNB/HNB、通过所述 HeNB/HNB发起附着、建立 PDN 连接请求、 承载建立 /修改 /删除请求, 或者核心网络侧发起承载建立 /修改 / 删除请求时, 所述接纳控制网元根据固网反馈的 QoS进行接纳决策, 即当 固网资源满足时, 接纳控制网元接受所述请求; 固网资源不满足时, 接纳 控制网元拒绝所述请求, 或者, 所述接纳控制网元决定抢占现有已使用的 资源来满足所述请求。
17、一种控制业务接纳的系统,其特征在于,该系统包括: HeNB/ HNB, 接纳控制网元和固网; 其中,
所述接纳控制网元, 用于在 HeNB/ HNB上电时, 从固网获取授权资源 信息; 以及根据固网返回的授权资源信息, 对从所述 HeNB/HNB 接入的 UE进行接纳控制;
所述固网, 用于提供 HeNB/ HNB的授权资源信息。
18、 根据权利要求 17所述的系统, 其特征在于, 所述固网返回的授权 资源信息为授权的服务质量 QoS。
19、根据权利要求 16所述的系统, 其特征在于, HeNB上电的情况下, 所述接纳控制网元为演进家庭基站网关 HeNB GW、移动管理单元 MME或 HeNB; HNB上电的情况下, 所述接纳控制网元为家庭基站网关 HNB GW 或 HNB。
20、 根据权利要求 19所述的系统, 其特征在于, 所述 HeNB上电时, 接纳控制网元从固网获取授权资源信息为:
HeNB上电并到 HeNB GW注册, HeNB GW向演进家庭基站策略功能 实体演进家庭基站策略功能实体请求授权的 QoS;
演进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并 在获取授权的 QoS后将其反馈给 HeNB GW, HeNB GW存储所述 QoS。
21、 根据权利要求 19所述的系统, 其特征在于, 所述在 HNB上电时, 接纳控制网元从固网获取授权资源信息为:
HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体家 庭基站策略功能实体请求授权的 QoS;
家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并在获 取授权的 QoS后将其反馈给 HNB GW, HNB GW存储所述 QoS。
22、根据权利要求 19所述的系统,其特征在于,所述在 HeNB上电时, 接纳控制网元从固网获取授权资源信息为:
HeNB上电并到 MME注册 , MME向演进家庭基站策略功能实体请求 授权的 QoS;
演进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并 将获取的授权的 QoS反馈给 MME, MME存储该 QoS。
23、 根据权利要求 197所述的系统, 其特征在于, 所述在 HeNB上电 时, 接纳控制网元从固网获取授权资源信息为:
HeNB上电并到 HeNB GW/MME注册, HeNB GW/MME向演进家庭基 站策略功能实体请求授权的 QoS; 演进家庭基站策略功能实体向固网资源 管理单元请求授权的 QoS,并将获取的授权的 QoS反馈给 HeNB GW/MME; HeNB GW/MME将所述授权的 QoS反馈给 HeNB, HeNB存储所述授权的 QoS,
或者, HeNB上电后向演进家庭基站策略功能实体请求授权的 QoS; 演 进家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取 到的授权的 QoS反馈给 HeNB, HeNB存储所述授权的 QoS。
24、 根据权利要求 19所述的系统, 其特征在于, 在 HNB上电时, 接 纳控制网元从固网获取授权资源信息为:
HNB上电并到 HNB GW注册, HNB GW向家庭基站策略功能实体请 求授权的 QoS; 家庭基站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取的授权的 QoS反馈给 HNB GW; HNB GW将所述授权的 QoS反馈给 HNB, HNB存储所述授权的 QoS,
或者, HNB上电后向家庭基站策略功能实体请求授权的 QoS; 家庭基 站策略功能实体向固网资源管理单元请求授权的 QoS, 并将获取到的授权 的 QoS反馈给 HNB, HNB存储所述授权的 QoS。
25、 根据权利要求 16所述的系统, 其特征在于, 所述接纳控制网元从 固网获取授权资源信息为: 固网在授权的资源信息发生变化时, 主动将修 改后的授权资源信息经家庭基站策略功能实体发送给接纳控制网元。
26、 根据权利要求 20至 24任一项所述的系统, 其特征在于, 所述向固网资源管理单元请求授权的 QoS时携带隧道信息 /本地信息, 固网资源管理单元根据所述隧道信息 /本地信息查找 HeNB/HNB 所在的回 程网, 并根据当前回程网资源的使用状况为所述 HeNB/HNB授权 QoS。
27、根据权利要求 26所述的系统,其特征在于,接纳控制网元为 HeNB GW/HNB GW的情况下, 所述隧道信息 /本地信息由 HeNB/HNB本身携带 和 /或由 SeGW封装到 HeNB/HNB注册信息中发送给 HeNB GW /HNB GW; 接纳控制网元为 MME的情况下, 所述隧道信息 /本地信息由 HeNB本身携 带和 /或由 SeGW封装到 HeNB注册信息中发送给 MME; 接纳控制网元为 HeNB/HNB的情况下, 所述隧道信息 /本地信息由 HeNB/HNB 自身获取。
28、 根据权利要求 27所述的系统, 其特征在于, 所述隧道信息 /本地信 息包括以下一种或多种: 固网为终端分配的 IP地址、 网络地址转换 NAT 转换后的地址和端口号; SeGW为终端分配的 IP地址及端口号、 SeGW地 址及端口号、 HeNB 的标识。
29、 根据权利要求 20至 24任一项所述的系统, 其特征在于, 所述固 网资源管理单元为 BPCF, 所述演进家庭基站策略功能实体 /家庭基站策略 功能实体为 HeNB PF/HNB PF。
30、 根据权利要求 17至权利要求 24任一项所述的系统, 其特征在于, 所述固网, 还用于在向所述接纳控制网元返回授权资源信息时携带半 静态指示;
所述接纳控制网元, 还用于在收到所述半静态指示后, 根据所述授权 资源信息进行接纳控制, 不再向固网查询。
31、 根据权利要求 17至权利要求 24任一项所述的系统, 其特征在于, 所述接纳控制网元, 还用于记录当前固网资源的使用状态。
32、 根据权利要求 18至权利要求 24任一项所述的系统, 其特征在于, 所述接纳控制网元根据所述授权资源信息, 对从所述 HeNB/HNB 接入的 UE进行接纳控制为:
当 UE接入所述 HeNB/HNB、通过所述 HeNB/HNB发起附着、建立 PDN 连接请求、 承载建立 /修改 /删除请求, 或者核心网络侧发起承载建立 /修改 / 删除请求时, 所述接纳控制网元根据固网反馈的 QoS进行接纳决策, 即当 固网资源满足时, 接纳控制网元接受所述请求; 固网资源不满足时, 接纳 控制网元拒绝所述请求, 或者, 所述接纳控制网元决定抢占现有已使用的 资源来满足所述请求。
PCT/CN2011/077539 2010-08-27 2011-07-25 一种控制业务接纳的方法及系统 WO2012024997A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2010102666004A CN102387487A (zh) 2010-08-27 2010-08-27 一种控制业务接纳的方法及系统
CN201010266600.4 2010-08-27

Publications (1)

Publication Number Publication Date
WO2012024997A1 true WO2012024997A1 (zh) 2012-03-01

Family

ID=45722880

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/077539 WO2012024997A1 (zh) 2010-08-27 2011-07-25 一种控制业务接纳的方法及系统

Country Status (2)

Country Link
CN (1) CN102387487A (zh)
WO (1) WO2012024997A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103369501B (zh) * 2012-04-09 2019-03-12 中兴通讯股份有限公司 一种资源管理方法、系统和资源管理网元
CN103384395B (zh) * 2012-05-04 2018-10-09 南京中兴软件有限责任公司 上行带宽配置方法及装置
CN104113889B (zh) * 2014-07-10 2017-09-26 京信通信系统(中国)有限公司 一种基于回传通道的连接建立的方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101675687A (zh) * 2007-04-30 2010-03-17 交互数字技术公司 具有新功能的家庭节点-b
CN101730311A (zh) * 2008-10-22 2010-06-09 华为技术有限公司 一种无线接入承载管理方法、装置和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100571185C (zh) * 2006-06-05 2009-12-16 华为技术有限公司 一种跨不同管理域网络的边缘连接选路方法
CN101730155A (zh) * 2009-04-30 2010-06-09 中兴通讯股份有限公司 一种对用户进行资源控制的系统及方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101675687A (zh) * 2007-04-30 2010-03-17 交互数字技术公司 具有新功能的家庭节点-b
CN101730311A (zh) * 2008-10-22 2010-06-09 华为技术有限公司 一种无线接入承载管理方法、装置和系统

Also Published As

Publication number Publication date
CN102387487A (zh) 2012-03-21

Similar Documents

Publication Publication Date Title
JP5528563B2 (ja) ホーム・フェムトセル用のコール許可制御の方法
WO2012065499A1 (zh) 一种实现服务质量控制的方法和系统
WO2012136167A2 (zh) 一种本地网络和实现本地网关和家庭基站建立连接的方法
WO2011050737A1 (zh) 一种实现本地接入的方法及系统
WO2011026392A1 (zh) 一种路由策略的获取方法及系统
WO2009059532A1 (fr) Procédé et dispositif pour exploitation de support
WO2011075884A1 (zh) 一种向移动用户设备提供网络服务方法及其装置
WO2015192323A1 (zh) 一种mme重选的方法和mme
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
CN102143530B (zh) 一种对移动用户本地接入的策略控制方法和系统
WO2010003359A1 (zh) 区别用户计费规则的计费方法和系统
WO2012129923A1 (zh) 接入网网元、接入网络系统及接入方法
WO2010130174A1 (zh) 一种实现本地访问控制的方法及相应的通信系统
WO2012062183A1 (zh) 一种实现数据流服务质量和计费策略控制的方法及系统
WO2012025031A1 (zh) 基于本地接入的承载建立方法及系统
US8874079B2 (en) Control method for home base station access and home base station gateway
WO2012003781A1 (zh) 一种控制业务接纳的方法及系统
WO2012024997A1 (zh) 一种控制业务接纳的方法及系统
WO2012126319A1 (zh) 一种本地访问业务的切换方法及系统
WO2011015086A1 (zh) 一种本地ip访问接入控制的方法及系统
WO2014071790A1 (zh) 固网移动融合的策略控制方法、装置及系统
WO2013082987A1 (zh) 对本地卸载数据进行资源控制的方法及系统
WO2012146093A1 (zh) 一种实现业务处理的方法和系统
WO2010121421A1 (zh) 一种实现本地ip接入的方法、系统及网络设备
WO2013159605A1 (zh) 一种通信系统、装置和方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11819372

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11819372

Country of ref document: EP

Kind code of ref document: A1