WO2010081396A1 - 毫微级接入点的入网方法、装置和系统 - Google Patents

毫微级接入点的入网方法、装置和系统 Download PDF

Info

Publication number
WO2010081396A1
WO2010081396A1 PCT/CN2010/070028 CN2010070028W WO2010081396A1 WO 2010081396 A1 WO2010081396 A1 WO 2010081396A1 CN 2010070028 W CN2010070028 W CN 2010070028W WO 2010081396 A1 WO2010081396 A1 WO 2010081396A1
Authority
WO
WIPO (PCT)
Prior art keywords
fap
asn
network
access
context
Prior art date
Application number
PCT/CN2010/070028
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 WO2010081396A1 publication Critical patent/WO2010081396A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04Large scale networks; Deep hierarchical networks
    • H04W84/042Public Land Mobile systems, e.g. cellular systems
    • H04W84/045Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • FAP Femto Access Point
  • FAP accesses the World Interoperability for Microwave Access through a wired broadband network (such as a Digital Subscriber Line (DSL) broadband network or an Internet Protocol (IP) network).
  • WiMAX wireless broadband network
  • MS WiMAX mobile terminals
  • WiMAX macro network and providing access services for WiMAX mobile terminals (MS) on the authorized spectrum.
  • MS WiMAX mobile terminals
  • WiMAX macro network and providing access services for WiMAX mobile terminals (MS) on the authorized spectrum.
  • WiMAX WiMAX mobile terminals
  • MS WiMAX mobile terminals
  • ASN Access Service Network
  • ASN-GW Access Service Network GateWay
  • the embodiments of the present invention provide a network access method, device, and system for a nano-level access point, and provide technical support for the FAP to access the access service network, thereby meeting the application requirements of the FAP.
  • the embodiment of the invention provides a method for network access of a nano-level access point, including:
  • the embodiment of the present invention further provides another method for accessing a nano-level access point, including:
  • the embodiment of the invention further provides a network access device for a nano-level access point, including:
  • the network access request receiving module is configured to receive a network access request of the femto access point FAP;
  • a context sending module configured to send the context to an access service network ASN that the FAP needs to access, for the ASN to generate a configuration required for the FAP to enter the network according to the context and the current network configuration of the ASN.
  • the parameters are sent to the FAP.
  • An embodiment of the present invention further provides another network access device for a nano-level access point, including:
  • a context receiving module configured to receive a context of the FAP sent by the authentication authorization server according to the FAP network access request
  • a configuration parameter generating module configured to generate, according to the context and a current network configuration of the access service network, configuration parameters required for the FAP to enter the network;
  • a configuration parameter sending module configured to send the configuration parameter to the FAP.
  • the embodiment of the present invention further provides a network access system for a nano-level access point, including: a security gateway, a first network access device, and a second network access device;
  • the first network access device is configured to receive, by the security gateway, a network access request of a femto access point (FAP), obtain a context of the FAP according to the network access request, and access an access service network that needs to be accessed by the FAP.
  • FAP femto access point
  • the ASN sends the context;
  • the embodiment of the invention further provides another network access system of the nano-level access point, the first security gateway and the second security.
  • the first network access device is configured to receive a network access request of the femto access point FAP by using the first security gateway; acquire a context of the FAP according to the network access request; and access the access required by the FAP
  • the service network sends the context
  • the second network access device is configured to receive a context of the FAP that is sent by the first network access device according to the FAP network access request, and generate configuration parameters required for the network access to the FAP according to the context and the current network configuration of the ASN. Transmitting, by the second security gateway, the configuration parameter to the FAP.
  • the FAP network access method, device, and system provided by the embodiments of the present invention enable the FAP to obtain the configuration parameters required for network access. After receiving the configuration parameters, the FAP can perform corresponding configuration according to the received configuration parameters, and pass the ASN- The GW accesses the ASN. When the FAP is successfully connected to the ASN, the FAP can access the macro network as a network element in the ASN, which is beneficial to provide an effective access service for the terminal and meet the application requirements of the FAP.
  • FIG. 1 is a flowchart of a method for accessing a FAP according to a first embodiment of the present invention
  • FIG. 1b is a flowchart of a method for accessing a FAP according to a second embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a network access system of a FAP according to a third embodiment of the present invention.
  • FIG. 3 is a signaling interaction diagram of a network access method of a FAP according to a fourth embodiment of the present invention.
  • FIG. 4 is a signaling interaction diagram of a network access method of a FAP according to a fifth embodiment of the present invention.
  • FIG. 5 is a signaling interaction diagram of a method for accessing a network of a FAP according to a sixth embodiment of the present invention.
  • FIG. 6 is a schematic diagram of an application scenario of FAP redirection according to a seventh embodiment of the present invention.
  • FIG. 7 is a signaling interaction diagram of a method for accessing a network of a FAP according to an eighth embodiment of the present invention.
  • FIG. 8 is a signaling interaction diagram of a method for accessing a network of a FAP according to a ninth embodiment of the present invention.
  • FIG. 9 is a signaling interaction diagram of a network access method of a FAP according to a tenth embodiment of the present invention.
  • FIG. 10 is a schematic diagram of an application scenario of a FAP roaming network redirection method according to an eleventh embodiment of the present invention
  • FIG. 11 is a signaling interaction diagram of a FAP network access method according to a twelfth embodiment of the present invention
  • FIG. 12 is a signaling interaction diagram of a method for accessing a network of a FAP according to a thirteenth embodiment of the present invention
  • FIG. 13 is a schematic diagram of a signaling interaction of a FAP access method according to a fourteenth embodiment of the present invention
  • FIG. 14 is a schematic structural diagram of a network access system of a FAP access point according to a fifteenth embodiment of the present invention
  • FIG. 16 is a schematic structural diagram of a network access device of a FAP provided by the sixteenth embodiment
  • FIG. 16 is a schematic structural diagram of a network access device of a FAP according to a seventeenth embodiment of the present invention.
  • FIG. 17 is a schematic structural diagram of a network access system of a FAP according to an eighteenth embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of a network access system of a FAP according to a nineteenth embodiment of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
  • the "network access” in the embodiment of the present invention is to access the access service network (ASN), so that the FAP successfully accessing the access service network has the function of providing network access to the terminal.
  • ASN access service network
  • the FAP can establish a connection with the external macro network through the access service network, thereby ensuring effective access services for the terminal.
  • FIG. 1 is a flowchart of a method for accessing a FAP according to a first embodiment of the present invention. As shown in FIG. la, this embodiment includes:
  • Step l la Receive a network access request from a femto access point (FAP).
  • FAP femto access point
  • the network access request may include identification information of the FAP.
  • Step 12a Acquire a context of the FAP according to the network access request.
  • the FAP context corresponding to the identifier information of the FAP may be acquired.
  • the obtained context of the FAP may include: location information of the FAP.
  • the context of the FAP may further include: identifier information of the FAP, quality of service information of the FAP, closed subscriber group information, and the like.
  • Step 13a Send the context to the access service network ASN that the FAP needs to access, for the ASN to generate configuration parameters required for the FAP to enter the network according to the context and the current network configuration of the ASN.
  • the FAP is sent.
  • the context of the FAP sent to the ASN may include: location information of the FAP and identification information of the FAP.
  • the context of the FAP may also include: quality of service information of the FAP, closed subscriber group information, and the like.
  • the configuration parameters required for the ASN to generate the network for the FAP may include: the FAP network determined for the FAP Connected ASN-GW information, FAP global unique identifier, air interface parameters, and paging group information.
  • the ASN may send configuration parameters to the FAP through the security gateway, where the parameters sent by the ASN to the security gateway include: ASN-GW information, global unique identifier of the FAP, air interface parameters, and paging group information; parameters sent by the security gateway to the FAP
  • the method includes: a globally unique identifier of the FAP, an air interface parameter, and paging group information; the parameter sent by the security gateway to the FAP may further include: ASN-GW information.
  • the ASN may also send corresponding parameters to the ASN-GW, where the parameters sent by the ASN to the ASN-GW may include: a globally unique identifier of the FAP, location information of the FAP, and the air interface parameter.
  • the executor of this embodiment may be a FAP Authentication Authorization Accounting Server (FAP AAA server) deployed on the network side, and the ASN required to be accessed by the FAP AAA server according to the FAP access request to the FAP.
  • FAP AAA server FAP Authentication Authorization Accounting Server
  • Sending a FAP context helps the ASN to allocate network resources and configuration parameters for the FAP, thereby providing support for the FAP access ASN to meet the application requirements of the FAP.
  • FIG. 1b is a flowchart of a method for accessing a FAP according to a second embodiment of the present invention. As shown in FIG. 1b, this embodiment includes:
  • Step l lb receiving the context of the FAP sent by the FAP AAA server according to the FAP incoming request.
  • Step 12b Generate, according to the context and the current network configuration of the ASN, configuration parameters required for the FAP to enter the network.
  • Step 13b Send the configuration parameter to the FAP.
  • the FAP configuration center receives the FAP context including: The FAP configuration center directly receives the FAP context through the FAP AAA server.
  • the FAP configuration center receiving the context of the FAP may further include the FAP configuration center receiving the context of the FAP indirectly, for example: the FAP AAA server sends the context of the FAP to the security gateway, and the FAP configuration center receives the context of the FAP through the security gateway.
  • the context of the received FAP includes the location information of the FAP, and may also include the identification information of the FAP.
  • the FAP can obtain configuration parameters required for network access. After receiving the configuration parameters, the FAP can perform corresponding configuration according to the received configuration parameters, and access the ASN network through the ASN-GW. When the FAP successfully accesses the ASN network, the FAP can access the macro network as a network element in the ASN network, which is beneficial to provide an effective access service for the terminal and meet the application requirements of the FAP.
  • FIG. 2 is a schematic structural diagram of a network access system of a FAP according to a third embodiment of the present invention.
  • the FAP network access system includes: FAP, security gateway (SeGW), configuration center, and FAP Authentic Authentication Account Server (FAP AAA).
  • the port is connected to the monthly network gateway (ASN-GW).
  • the macro base station In the WiMAX macro network, the macro base station (BS) is uniformly managed by an access service network gateway (ASN Gateway, ASN-GW), and the mobile terminal (MS) accesses the WiMAX macro network through the macro base station and through the ASN-GW.
  • ASN Gateway ASN Gateway
  • MS mobile terminal
  • FAP can be regarded as a low-power small base station for providing small-scale indoor coverage. It has some functions of BS, and is also managed by ASN-GW to access the WiMAX macro network.
  • FAP accesses the WiMAX macro network through a wired network. Due to the different network protocols of the wired network and the WiMAX network and for security reasons, there is no direct communication interface between the FAP and the ASN-GW, and the FAP and the ASN-GW are required. For the interactive protocol conversion, the FAP needs to establish a connection with the ASN-GW through a Security Gateway (SeGW).
  • SeGW Security Gateway
  • the configuration center is used for centralized configuration management of FAPs and for allocating network resources for FAP network access.
  • the configuration center is configured to save or obtain information about each BS in the ASN.
  • the information includes at least the BS ID, the BS air interface parameter, and the address range corresponding to each BS.
  • the configuration center is also used to save or obtain the ASN-GW information corresponding to the BS.
  • the ASN-GW ID and the like are included, and the configuration center is further configured to save the information of the accessed FAP.
  • the information of the FAP may include a FAP ID, an air interface parameter, and a context acquired by other FAPs during the network access process.
  • interface 3 is used for FAP context transmission between the SeGW and the configuration center, triggering the network resource allocation process, etc.
  • interface 4 is used to configure the interaction between the center and the FAP AAA server, such as performing FAP context transmission.
  • the interface 5 is used for the connection between the ASN-GW and the configuration center, and the interface 7 is used for the connection between the ASN-GW and the FAP AAA server; both the interface 5 and the interface 7 can be used for the ASN-GW to obtain the context of the FAP.
  • the interface 5 can be specifically an R4 interface, and the interface 7 can be an R3 interface.
  • the interface 6 is an interface between the SeGW and the ASN-GW, and is used for the interaction between the SeGW and the ASN-GW, and carries the R6 interface between the FAP and the ASN-GW.
  • the SeGW, FAP Configuration Center, and FAP AAA server can be deployed as a FAP network access system.
  • the FAP has a contract with the Network Service Provider (NSP).
  • NSP Network Service Provider
  • the FAP network access process requires the NSP to authenticate and authorize the FAP
  • the FAP AAA server can be deployed in the NSP managed connection service.
  • NAP Network Access Provider
  • the FAP AAA server can be deployed in the ASN managed by the NAP.
  • Default SeGW The SeGW preset by the FAP is used to connect the FAP to the FAP AAA server after the FAP is connected to the wired broadband network;
  • SeGW In the local redirection application scenario, the FAP redirect entry;
  • Roaming access SeGW In the roaming redirection scenario, the roaming redirection entry of the FAP;
  • the FAP configuration center is the ASN-GW selected by the FAP, and is used for FAP access to the ASN. After the FAP is successfully connected to the network, it can establish a connection with an access ASN-GW.
  • Authentication ASN-GW The ASN-GW selected by the FAP configuration center for the FAP is used to participate in FAP authentication when the FAP AAA server sends the ASN-GW access identifier.
  • H-CSN Hometown CSN
  • V-CSN Visiting place CSN
  • H-ASN Hometown ASN
  • V-ASN visited ASN
  • FIG. 3 is a signaling interaction diagram of a network access method of a FAP according to a fourth embodiment of the present invention.
  • the application scenario of this embodiment is: a FAP local network access scenario implemented based on the network architecture shown in FIG. 2; an interface between nodes in the network architecture shown in FIG. 2 utilized in the implementation process includes: interface 1, 2 , 3, 4, 5 and 6.
  • the FAP may have a contractual relationship with the NAP corresponding to the home ASN, and the FAP AAA server is deployed in the hometown ASN.
  • the FAP may also have a contractual relationship with the NSP corresponding to the home country CSN, and the FAP AAA server is deployed in the home country CSN.
  • the SeGW in this embodiment is a default SeGW corresponding to the default SeGW address information of the FAP network configured on the FAP.
  • This embodiment includes:
  • Step 31 The FAP connects to the wired network, and sends an incoming request to the SeGW.
  • the network access request may carry the identification information of the FAP.
  • the default SeGW address information is pre-configured on the FAP.
  • the FAP When the FAP needs to access the ASN, the FAP sends a network access request to the default SeGW corresponding to the address information configured by the FAP.
  • the identifier information of the FAP carrying the network access request may include: a FAP device identifier, a user identifier, a subscription information of the FAP, and the like, where the subscription information is used to indicate a FAP AAA server that has a contractual relationship with the FAP, so that the default SeGW determines the network access request according to the subscription information.
  • the destination address; or, the subscription information may be carried by the FAP device identifier or the user identifier, in which case no separate subscription information is required.
  • the network access request may also carry other information of the FAP, such as: location parameters of the FAP, user information of the FAP, and the like.
  • Step 32 The SeGW sends a network access request to the FAP AAA server.
  • the address of the FAP AAA server with the subscription relationship is pre-configured on the SeGW.
  • the SeGW receives the network access request reported by the FAP, the SeGW sends the network access request to the FAP AAA server corresponding to the identification information of the FAP.
  • Step 33 Initiate the FAP positioning process, and obtain the FAP location information by using the FAP positioning process.
  • This step is an optional step.
  • the FAP and the FAP AAA server can obtain the location information of the FAP through the ISP, the GPS, or the neighboring cell list.
  • the obtained FAP location information can be used in the process of authenticating or authorizing the FAP. .
  • This step may occur at a certain time before step 35 of the embodiment. For example, this step may be performed before step 31 or step 32, or this step may be performed before step 34 or after step 34. If the location information of the FAP is known, you can perform the FAP positioning without performing this step.
  • Step 34 The FAP AAA server performs authentication and authorization processing on the FAP through the SeGW.
  • Step 35 The SeGW establishes a channel with the FAP according to the key information after the authentication and authorization processing.
  • This step can also occur at some point between step 35 and step 312.
  • Step 36 The SeGW sends a network resource configuration request to the FAP configuration center of the ASN to which the SeGW belongs, and is configured to request to allocate network resources and configure network access parameters for the FAP.
  • the network resource configuration request includes the FAP identification information.
  • Step 36 The FAP configuration center sends a FAP parameter request to the FAP AAA server to request to obtain the FAP context.
  • the FAP parameter request carries the FAP identification information, and the FAP configuration center can obtain the FAP corresponding to the identifier information from the FAP AAA server. Context.
  • Step 38 The FAP AAA server queries the saved FAP subscription file according to the FAP identification information, obtains a FAP context corresponding to the identifier information, and sends a FAP parameter response to the FAP configuration center.
  • the FAP parameter response carries the FAP context.
  • the FAP context may include location information (Location) of the FAP.
  • the context of the FAP may further include the identification information of the FAP.
  • the context of the FAP may further include: the authentication status information of the FAP, the quality of service (QoS) of the FAP, and the closed user group of the FAP (Closed Subscriber Group) , referred to as CSG) and other parameters.
  • QoS quality of service
  • CSG Closed Subscriber Group
  • the FAP Configuration Center can obtain the location information of the FAP (ocatior) in any of steps 36 and 38.
  • Step 39 The FAP configuration center allocates network resources for the FAP according to the obtained FAP context, and generates configuration parameters required for the FAP to access the ASN for the FAP.
  • the FAP configuration center is also used to obtain the FAP context from the FAP AAA server or the default SeGW. Maintain the acquired FAP context; obtain the PG parameters from the access ASN-GW; determine the FAP ID and air interface parameters for the FAP; provide the required FAP parameters to the ASN-GW and the SeGW.
  • the FAP configuration center allocates network resources for the FAP, and the method includes: determining, by the FAP, the access ASN-GW.
  • the configuration parameters generated for FAP can include:
  • the FAP ID is the globally unique identifier assigned by the FAP Configuration Center to the FAP in the access service network.
  • ASN-GW information information of the access service network gateway connected to the FAP network determined by the FAP;
  • Air interface parameters Used to configure the air interface resources that can be used by the FAP.
  • configuration parameters generated by the FAP configuration center for the FAP may further include:
  • QoS A QoS policy corresponding to the FAP, which may include specified bandwidth, service priority, etc. from the FAP service;
  • CSG It is used to implement the function of the closed user group to obtain preferential access or obtain reserved access resources through a specific FAP to support the CSG service model and related applications of the nano-cellular system.
  • Step 310 The FAP configuration center sends configuration parameters required for the FAP to access the ASN to the access ASN-GW, where the configuration parameters may include:
  • FAP ID used to access the ASN-GW identity and address FAP
  • Locat ion FAP location information
  • Air interface parameters Used to access the ASN-GW management to optimize the wireless environment and BS air interface resources.
  • the configuration parameters sent by the FAP configuration center to the access ASN-GW may further include:
  • QoS QoS policy corresponding to the FAP, including the bandwidth and service priority from the FAP service.
  • the access ASN-GW After receiving the configuration parameters delivered by the FAP configuration center, the access ASN-GW negotiates the network that the FAP can use according to these configuration parameters. Resources and network resources covering the macro network where the FAP is located. After the negotiation is completed, the access ASN-GW is ready to establish a connection with the FAP.
  • Step 311 The FAP configuration center sends configuration parameters required for the FAP to access the ASN to the SeGW.
  • the configuration parameters may include:
  • FAP ID used for SeGW identification FAP
  • ASN-GW Info Authentication for identifying and addressing the FAP ASN-GW or access ASN_GW.
  • the FAP configuration center also sends the configuration parameters required by the FAP to the FAP through the SeGW, and the SeGW is configured according to the parameters.
  • the SeGW needs to establish a mapping relationship between the FAP identifier and the FAP ID.
  • SeGW will also The FAP configuration parameters required for self-configuration are sent to the FAP.
  • the SeGW sends a configuration parameter that is generated by the FAP configuration center to the FAP, and the configuration parameter may include: a FAP ID, a PG of the FAP, an ASN-GW Info, and an air interface parameter that can be used by the FAP.
  • Step 313 The FAP performs self-configuration according to the received configuration parameters, and opens an air interface and provides an access service to the terminal (MS). For example, the FAP completes the physical layer and the link layer configuration according to the received configuration parameters, and opens the air interface resource, and sends the packet periodically.
  • the wireless signal and the broadcast message can receive the message from the terminal; complete the process of the FAP accessing the ASN network.
  • the authentication authorization status information and the FAP context of the FAP are
  • the FAP determines the ASN-GW of the access service network that needs to be accessed, and generates the configuration parameters required for the FAP to access the network through the ASN-GW for the FAP and the ASN-GW, respectively, and implements the FAP according to the configuration parameters sent by the network side at the signing place.
  • Access ie: local access
  • macro network which helps the FAP to provide effective access services for the terminal.
  • FIG. 4 is a signaling interaction diagram of a network access method of a FAP according to a fifth embodiment of the present invention.
  • the application scenario of this embodiment is: a FAP local network access scenario implemented based on the network architecture shown in FIG. 2; an interface between nodes in the network architecture shown in FIG. 2 utilized in the implementation process includes: interface 1, 2 , 3, 4, 5, 6 and 7.
  • the difference between the embodiment corresponding to FIG. 3 is that the authentication process of the FAP is different in this embodiment.
  • the FAP configuration center allocates an authentication ASN-GW to the FAP before the authentication, and the default SeGW and the authentication ASN-GW participate in the FAP authentication. process.
  • this embodiment includes:
  • Step 41 - Step 43 is the same as Step 31 - Step 33 in the embodiment shown in Figure 3, wherein the positioning process of the FAP can be performed before step 41, or at step 42, or before step 48.
  • Step 44 The FAP AAA server sends an ASN-GW access request to the SeGW, where the ASN-GW access request carries an ASN-GW access identifier, and is used to notify the SeGW to participate in the FAP authentication process.
  • the FAP AAA server determines that the ASN-GW needs to participate in the FAP authentication process according to the pre-defined FAP authentication policy, and then notifies the SeGW of the established FAP authentication policy through the ASN-GW access request.
  • Step 45 The SeGW sends an ASN-GW information request (BP: ASN-GW Info request) to the FAP configuration center, and is configured to request the FAP configuration center to select an authentication ASN-GW to participate in the FAP authentication for the FAP, where the ASN-GW information request is carried.
  • the FAP needs to establish a connection relationship with the authentication ASN-GW.
  • the connection relationship of the authentication process is as follows: FAP—SeGW—Authentication ASN-GW—FAP AAA server, which uses interfaces 1, 6, and 7 in the authentication process. .
  • the location information of the FAP can be actively reported to the SeGW in the FAP request through the FAP, or can be obtained by the SeGW in the FAP redirect process.
  • Step 46 The FAP configuration center selects an authentication ASN_GW that participates in FAP authentication for the FAP.
  • the FAP configuration center determines, for the FAP, the authentication ASN-GW that participates in the FAP authentication, and determines the access ASN-GW of the FAP home ASN as the authentication ASN-GW participating in the FAP authentication according to the FAP location information.
  • step 413 of the embodiment there is no need to re-determine the access ASN-GW of the access service network that the FAP needs to access for the FAP, and the access ASN-GW of the access service network that the FAP needs to access and the FAP authentication.
  • the certification ASN-GW is the same. Figure 4 shows only the same situation in which the ASN-GW is accessed and the ASN-GW is authenticated.
  • the FAP configuration center may also select an authentication ASN-GW according to the current network status. In this case, if the authentication ASN-GW participating in the FAP authentication is different from the access ASN-GW of the FAP, the embodiment further needs to go through step 413.
  • the access ASN-GW of the access service network that needs to be accessed is determined for the FAP.
  • Step 47 When the FAP configuration center sends an ASN-GW Info response message to the SeGW, the ASN-GW Info carries the address information of the authentication ASN-GW that can participate in the FAP authentication process.
  • Step 48 The FAP AAA server authenticates and authorizes the FAP through the authentication ASN-GW and the SeGW selected in step 46.
  • Steps 49 to 417 are the same as those in the embodiment 35 to step 313 corresponding to FIG. 3 and will not be described again.
  • the FAP determines an authentication ASN-GW that can participate in the authentication and authentication processing of the FAP, and the FAP AAA server authenticates and authenticates the FAP through the authentication ASN-GW and the SeGW. After the FAP is authenticated and authorized, the FAP is determined to access the ASN-GW and the configuration parameters to provide effective support for the FAP to access the ASN, thereby meeting the application requirements of the FAP.
  • FIG. 5 is a signaling interaction diagram of a network access method of a FAP according to a sixth embodiment of the present invention.
  • the application scenario of this embodiment is: a FAP local network access scenario implemented based on the network architecture shown in FIG. 2; an interface between nodes in the network architecture shown in FIG. 2 utilized in the implementation process includes: interface 1, 2 , 3, 5 and 6.
  • the difference between the embodiment and the embodiment of the present invention is that the FAP configuration center does not have an interface with the FAP AAA server, and cannot directly interact with the FAP AAA server, and thus cannot obtain the context of the FAP from the FAP AAA server.
  • the FAP Configuration Center obtains the context of the FAP from the default SeGW. As shown in FIG. 5, this embodiment includes:
  • Step 51 - Step 54 is the same as Step 31 - Step 34 in the embodiment shown in Figure 3.
  • Step 55 After completing the FAP authentication and authorization processing, the FAP AAA server sends a FAP parameter sending message to the SeGW, where the FAP parameter sending message carries the FAP context required by the FAP configuration center to complete the FAP access to the ASN, where, the FAP
  • the context may include location information (Locat ion) of the FAP.
  • the context of the FAP may also include FAP Further, the context of the FAP may further include: FAP authentication status information, FAP Quality of Service (QoS), and FAP Closed Subscriber Group (CSG) parameters.
  • QoS Quality of Service
  • CSG FAP Closed Subscriber Group
  • Step 56 After receiving the FAP parameter, the SeGW returns a response message to the FAP AAA server. Steps 55 and 56 can be performed in conjunction with step 54, which can be implemented in the process of authenticating and authorizing the FAP by the FAP AAA server.
  • Step 57 is the same as step 35 in the embodiment shown in FIG. 3, and a channel between the SeGW and the FAP is established.
  • Step 57 can also be completed during the time period between steps 54 and 512.
  • Step 58 The SeGW sends a FAP network resource configuration request message to the FAP configuration center, where the message carries the FAP context delivered by the FAP AAA server.
  • Step 59 The FAP configuration center obtains the FAP context through the FAP network resource configuration request message sent by the SeGW, allocates the network resource to the FAP according to the FAP context, and generates the configuration parameter of the FAP.
  • the FAP configuration center obtains the FAP context through the FAP network resource configuration request message sent by the SeGW, allocates the network resource to the FAP according to the FAP context, and generates the configuration parameter of the FAP.
  • the configuration parameter of the FAP For details, refer to the description in step 39 in the corresponding embodiment. .
  • Step 510 - Step 513 is the same as step 310 - step 313 in the corresponding embodiment of FIG.
  • the FAP configuration center obtains the context of the FAP from the SeGW, determines the ASN-GW and the configuration parameters for the FAP according to the FAP context and the current network configuration of the ASN, and provides effective support for the FAP accessing the ASN, thereby meeting the application requirements of the FAP. .
  • FIG. 6 is a schematic diagram of an application scenario of FAP redirection according to a seventh embodiment of the present invention. This embodiment is implemented based on the system architecture shown in FIG. 2, where the FAP AAA server is located in the CSN.
  • the FAP has a contract with the NSP, and the FAP AAA server is deployed in the CSN managed by the NSP; there may be multiple ASNs that have a contract relationship with a CSN, and the application scenario shown in FIG.
  • Homeland ASN H-ASN
  • V-ASN visited ASN
  • SeGW SeGW
  • the H-SeGW configured by default on the FAP is located in the H-ASN, and the current location of the FAP is the coverage of the V-ASN. Therefore, during the FAP access process, the CSN network needs to load the FAP from the H_SeGW. Oriented to the V-SeGW of the V-ASN coverage area where the FAP is currently located, so that the FAP can access the V_ASN through the V-SeGW.
  • the FAP redirection process can include:
  • Step 61 The FAP sends a network access request to the H-SeGW, where the network access request carries the identifier information and the location information of the FAP.
  • the identification information of the FAP may include: a FAP device identifier, a user identifier, or subscription information of the FAP.
  • the subscription information is used to indicate the FAP AAA server that has a contractual relationship with the FAP, so that the H-SeGW determines the destination address of the network access request according to the subscription information; the subscription information can be used as an independent identification information, or the subscription information can be carried in the FAP device identifier or In the user ID.
  • Step 62 The H-SeGW forwards the network access request to the FAP AAA server deployed in the CSN network, where the network access request carries the identifier information and the location information of the FAP.
  • the AAP list is maintained on the FAP AAA server.
  • the information stored in the ASN list includes: the mapping relationship between the SeSN and the ASN of the CSN where the FAP AAA server is located; and the location interval information corresponding to the SeGW.
  • the FAP AAA server receives the network access request, it obtains the identification information and location information of the FAP.
  • the FAP AAA server queries the ASN list according to the FAP location information, and the SeGW corresponding to the location area where the FAP is currently located, and then learns the ASN corresponding to the SeGW according to the mapping relationship between the SeGW and the ASN.
  • the FAP AAA server determines whether the ASN is the home ASN of the FAP. If not, the FAP needs to be redirected to the V-SeGW of the visited ASN, and step 64 is performed; if the same, the FAP is not required to be redirected, and the process is terminated (not shown in FIG. 6).
  • Step 64 The H-SeGW forwards the SeGW redirection message to the FAP, where the SeGW redirection message carries the address information of the V_SeGW.
  • Step 65 The FAP initiates a V-ASN access process through the V-SeGW.
  • the FAP needs to be deployed in the FAP configuration center of the V-ASN to provide FAP configuration and subsequent network management according to the air interface environment of the FAP. Therefore, the FAP must access the V-ASN during the network access process.
  • the FAP may be redirected to the V-SeGW corresponding to the V-ASN through the redirection process, and the V-ASGW is accessed through the V-SeGW. , is conducive to guarantee the success rate of FAP access to the network.
  • FIG. 7 is a signaling interaction diagram of a method for accessing a network of a FAP according to an eighth embodiment of the present invention.
  • the application scenario shown in FIG. 6 is taken as an example to describe the FAP redirected network access process; the interfaces between the nodes in the network architecture shown in FIG. 2 used in the process of implementing the FAP redirected network access include: 2, 3, 4, 5 and 6.
  • the application scenario shown in FIG. 6 is taken as an example to further illustrate the technical solution of the FAP access method of the present invention.
  • the FAP is authenticated and authorized.
  • the embodiment includes: Step 71 - Step 73 is the same as Step 31 - Step 33 in the embodiment shown in FIG. 3, wherein Step 71 - Step
  • Step 74 The FAP AAA server selects the V_SeGW of the FAP redirection, that is, the FAP AAA server selects the FAP redirection entry.
  • the FAP AAA server can query the ASN list maintained on the FAP AAA server according to the FAP identification information and the location information.
  • the FAP AAA server learns according to the query result, the FAP H-ASN is different from the V-ASN, and the FAP is determined. Redirect to the V_SeGW of the V-ASN corresponding to the current location area of the FAP.
  • the FAP AAA server sends a SeGW redirection message to the H-SeGW, where the SeGW redirection message carries: V-SeGW address information.
  • Step 76 The FAP sends a redirected access request to the V-SeGW, where the redirected access request may carry the identifier information of the FAP, and is used to request to access the network through the V-SeGW.
  • the redirected access request may carry other information of the FAP, such as: FAP location parameters.
  • Step 77 The FAP AAA server performs authentication and authorization processing on the FAP through the V-SeGW.
  • step 78 is performed.
  • the step 78-step 716 is the same as the step 35-step 313 in the embodiment shown in FIG. 3, wherein the V-SeGW in the step 78-step 716 corresponds to the SeGW in the embodiment shown in FIG.
  • the FAP when the H-ASN of the FAP is different from the V-ASN, the FAP is redirected to the V-SeGW of the V-ASN corresponding to the current location area of the FAP, and after the FAP authentication is authorized, the FAP context is FAP.
  • the V-ASN-GW of the access service network that needs to be accessed is determined, and the configuration parameters required for the FAP to access the network through the V-ASN-GW are generated for the FAP and the V-ASN-GW, respectively, and the FAP is delivered according to the network side.
  • the configuration parameter accesses the ASN network at the visited location, thereby facilitating the FAP to provide an effective access service for the terminal.
  • Step 83 The FAP AAA server performs authentication and authorization processing on the FAP through the H-SeGW.
  • Step 84 The FAP AAA server selects the V_SeGW redirected by the FAP, that is, the FAP AAA server selects the entry of the FAP redirection. This step is the same as step 74 in the embodiment shown in FIG.
  • the FAP positioning process (not shown in Fig. 8) in this embodiment may occur in any of steps 71-74.
  • Step 85 The FAP AAA server sends a SeGW redirection message to the FAP through the H-SeGW, where the SeGW redirection message carries the V-SeGW address information, and is used to notify the FAP to establish a connection with the V-SeGW, that is, the V_SeGW is used as the FAP access V. - The entrance to the ASN.
  • the SeGW redirection message may also carry a FAP authentication identifier, which is used to notify the FAP that the legality has been verified.
  • Step 86 The FAP sends a redirection access request to the V-SeGW, where the redirection access request carries the FAP identification information, and is used to request to access the network through the V-SeGW.
  • the redirected access request may also carry a FAP authentication identifier, location information, and other parameters.
  • Step 87 The V-SeGW sends a network resource configuration request to the FAP configuration center (ie, the V-FAP) of the network where the V-SeGW is located, and is configured to request to allocate network resources and configure network access parameters for the FAP, where the network resource configuration request includes
  • the FAP identification information may also include a FAP authentication identifier.
  • Step 88 The FAP configuration center sends a FAP parameter request to the FAP AAA server to request the FAP context.
  • the FAP parameter request carries the FAP identifier information.
  • the FAP AAA server queries the saved FAP subscription file according to the FAP identification information, and obtains a FAP context and a channel establishment parameter corresponding to the FAP identification information.
  • the FAP context may include the location information (Location) of the FAP.
  • the context of the FAP may further include the identifier information of the FAP.
  • the context of the FAP may further include: the authentication status information of the FAP, the quality of service (QoS) of the FAP, and the closed user group of the FAP (Closed Subscriber Group)
  • the parameters such as CSG are used for the V-SeGW to establish a dedicated channel with the FAP in the wired broadband network, including the use of information generated during the authentication and authorization process to ensure communication security.
  • Step 810 and step 811 are the same as steps 712 and 713 in the corresponding embodiment of FIG.
  • Step 812 The V-FAP configuration center sends configuration parameters generated by the FAP to the V-SeGW, where the configuration parameters may include: a FAP ID, a PG of the FAP, an ASN-GW Info, and an air interface parameter that can be used by the FAP, and a channel establishment parameter. information.
  • the configuration parameters generated by the V-FAP configuration center for the FAP may further include: parameters of the QoS of the FAP, the CSG of the FAP, and the like.
  • Step 813 The V-SeGW establishes a channel with the FAP according to the acquired channel establishment parameter.
  • Step 814 and step 815 are the same as steps 715 and 716 in the corresponding embodiment of FIG.
  • the FAP is redirected, and the FAP is redirected from the H_SeGW to the V-SeGW, and the V-ASN-GW that needs the V-ASN is determined according to the FAP context, and is the FAP.
  • the configuration parameters required to access the network through the V-ASN-GW are generated, and the FAP accesses the ASN network according to the configuration parameters sent by the network side, thereby facilitating the FAP to provide an effective access service for the terminal.
  • FIG. 9 is a signaling interaction diagram of a method for accessing a FAP according to a tenth embodiment of the present invention.
  • the application scenario shown in FIG. 6 is taken as an example to illustrate the process of redirecting the FAP into the network; and the method used in the process of implementing the FAP redirected network access
  • the interfaces between the nodes in the network architecture shown in 2 include: interfaces 1, 2, 3, 4, 5, 6, and 7.
  • the difference between this embodiment and the corresponding embodiment of FIG. 7 is that, in this embodiment, before authenticating the legality of the FAP, the FAP is assigned an authentication V-ASN-GW that participates in FAP authentication. As shown in FIG. 9, this embodiment includes:
  • Step 91 - Step 94 is the same as Step 71 - Step 74 in the embodiment shown in Figure 7.
  • Step 95 The FAP AAA server sends a SeGW redirection message to the FAP through the H-SeGW, where the SeGW redirection message carries the address information of the V-SeGW corresponding to the current location area of the FAP, and is used to notify the FAP to establish a connection with the V-SeGW. , that is, the V-SeGW is used as an entry point for the FAP to access the V-ASN.
  • the SeGW redirection message also carries an ASN-GW access identifier, where the ASN-GW access identifier is used to notify the FAP that authentication is required in the FAP authentication process.
  • the FAP With the participation of the ASN-GW, the FAP needs to establish a connection with the authentication ASN-GW participating in the authentication before the authentication.
  • Step 96 The FAP sends a redirected access request to the V-SeGW, where the redirected access request carries the identifier information of the FAP.
  • Step 97 The V-SeGW sends an ASN-GW information request (ie, an ASN-GW Info request) to the FAP configuration center, and is configured to request the FAP configuration center to select an authentication ASN-GW to participate in the FAP authentication, where the ASN-GW information request is received. Carrying the location information (Locat ion) of the FAP.
  • ASN-GW information request ie, an ASN-GW Info request
  • the V-SeGW determines that the ASN-GW information request (ie, the ASN-GW Info request) needs to be sent to the V-FAP configuration center according to the ASN-GW access identifier, and is used to request the FAP configuration center to select an authentication ASN-GW to participate in the FAP.
  • the ASN-GW information request carries the location information (Locat ion) of the FAP.
  • Step 98 The FAP Configuration Center selects an authentication V_ASN_GW that participates in FAP authentication for the FAP.
  • the FAP configuration center determines the V-ASN-GW that participates in the FAP authentication for the FAP, and determines the V-ASN-GW of the FAP location as the authentication ASN-GW participating in the FAP authentication according to the FAP location information.
  • the V-ASN-GW of the access service network that the FAP needs to access is not required to be re-determined for the FAP, that is, the V-ASN-GW of the access service network that the FAP needs to access and the FAP authentication.
  • the certification ASN-GW is the same.
  • Figure 9 shows only The V-ASN-GW of the access service network that the FAP needs to access is the same as the authentication ASN-GW that participates in the FAP authentication.
  • the FAP configuration center selects an authentication ASN-GW according to the current status of the macro network. In this case, if the authentication ASN-GW participating in the FAP authentication is different from the V-ASN-GW in the FAP, the embodiment needs to go through step 915.
  • the FAP determines the V-ASN-GW of the access service network that needs to be accessed.
  • Step 99 is the same as step 47 in the corresponding embodiment of FIG. 4, wherein the V_SeGW and V-FAP configuration centers in steps 98 and 99 correspond to the SeGW and FAP configuration centers in the embodiment shown in FIG. 4, respectively.
  • Step 910 - Step 919 corresponds to step 77 - step 716 in the embodiment of Figure 7.
  • the FAP determines an authentication ASN-GW that can participate in the authentication and authentication processing of the FAP, and the FAP AAA server authenticates and authenticates the FAP through the authentication ASN-GW and the SeGW. After the FAP is authenticated and authorized, the FAP determines the access ASN-GW and the configuration parameters to provide effective support for the FAP to access the ASN network, thereby meeting the application requirements of the FAP.
  • FIG. 10 is a schematic diagram of an application scenario of FAP roaming network redirection according to an eleventh embodiment of the present invention.
  • the home location CSN (H-CSN) signed by the FAP and the visited CSN (V-CSN) where the FAP is currently located have signed the FAP roaming agreement; there is a contract relationship between the ASN1 and the H-CSN.
  • ASN2 and V-CSN There is a contract relationship between ASN2 and V-CSN.
  • the V-CSN provides a roaming redirection entry for the H-CSN, that is, the roaming redirection access gateway V-SeGW1, so that if the FAP needs to access the ASN with the contracting relationship with the V-CSN, The VAP is accessed by the V_SeGW1, and then the FAP redirection optimization process is performed according to the location area where the FAP is currently located, so as to provide the FAP with the SeGW that can access the ASN network.
  • the ASN list and the CSN list are maintained on the FAP AAA server.
  • the mapping between the ASNs, the ASNs, and the SeGWs, and the location interval of the SeGW are used in the ASN list. If the location information of the FAP does not match the location range in the ASN list, then it is determined that the roaming scenario matches the FAP location information with the address range in the CSN list to determine which V-CSN coverage the FAP is located in. region.
  • the CSN list there is a mapping relationship between the V-CSN and the roaming access SeGW of the roaming protocol, and an address interval corresponding to the roaming access SeGW.
  • Each CSN in the list has at least one SeGW information corresponding thereto.
  • the FAP roaming redirection process may include:
  • Step 101 The FAP sends a network access request to its default H-SeGW, where the network access request carries the FAP label. Knowledge and location information, etc.
  • Step 102 The H-SeGW forwards the network access request to the H-FAP AAA server, where the network access request carries the FAP identifier and the location information.
  • Step 103 The H-FAP AAA server queries the ASN list and the CSN list maintained on the H-FAP AAA server according to the FAP identifier and the location information.
  • the H-FAP AAA server learns according to the query result, the V-ASN to which the current location of the FAP belongs is not in the area covered by the H-CSN with which the FAP has a contractual relationship, but in the V-CSN area having the FAP roaming agreement with the H-CSN.
  • the FAP AAA server sends a roaming redirection message to the H-SeGW, where the roaming redirection message carries V-SeGW1 information (such as: V-SeGW1 address information, etc.).
  • Step 104 The H-SeGW forwards the roaming redirection message to the FAP, where the roaming redirection message carries the address information of the V-SeGW1.
  • the SeGW is deployed in the ASN, and in the roaming scenario shown in FIG. 10, the ASN is either contracted with the H-CSN, or is contracted with the V-CSN, and cannot directly interact with the CSN without the subscription relationship.
  • the interaction between the ASN and the CSN without the contractual relationship is implemented according to the roaming protocol:
  • the V-CSN provides the H-CSN with the V-SeGW1 as the roaming redirection entry of the FAP roaming from the H-CSN.
  • This V-SeGW1 is provided by an ASN under the V-CSN contract.
  • the portal of roaming redirection can be dynamically maintained, not necessarily V-SeGWl, and not necessarily only one.
  • the H-CSN will also provide roaming portals for the V-CSN.
  • Step 105 The FAP initiates a roaming redirection process to the V-SeGW1.
  • the V-ASN network access process implemented by the V-SeGW1 can be implemented by using the implementation method of the corresponding embodiment in FIG.
  • the V-SeGW1 may belong to the ASN2 or may belong to other ASNs under the V-CSN subscription. If the V-SeGW1 does not meet the requirements of the FAP roaming access, the process of configuring the network resource by the FAP configuration center may be triggered if the second redirection process is not required; if the V-SeGW1 is not the FEC accessing the ASN optimal SeGW The process of the second redirection is initiated by the process of the second redirection. If the ASN to which the V-SeGW1 belongs does not cover the area where the FAP is located, the process of the second redirection is initiated.
  • Step 106 The V-SeGW1 forwards the roaming redirection request of the FAP to the V-FAP AAA server.
  • Step 107 The V-FAP AAA server initiates a SeGW redirection process according to the FAP identification information, and determines the V-SeGW2 that accesses the V-ASN network for the FAP.
  • Step 108 The FAP initiates an access procedure for establishing a V-ASN with the current location area of the FAP through the V-SeGW2.
  • the V-ASN to which the current location area of the FAP belongs is not in the H-CSN coverage area of the FAP, and the H-CSN and the V-CSN have the FAP roaming agreement, and the V-ASN has a contractual relationship with the V-CSN. , can be roamed
  • the redirection process determines the V-SeGW of the V-ASN for the FAP, which is beneficial to ensure the success rate of the FAP.
  • FIG. 11 is a signaling interaction diagram of a method for accessing a FAP according to a twelfth embodiment of the present invention.
  • the application scenario shown in FIG. 10 is used as an example to describe the FAP roaming redirection network access process; the interfaces between the nodes in the network architecture shown in FIG. 2 used in the FAP redirection network access process include: 1, 2, 3, 4, 5 and 6.
  • the difference between this embodiment and the corresponding embodiment of FIG. 7 is that this embodiment includes a secondary redirection process. As shown in FIG. 11, this embodiment includes:
  • Step 1101 - Step 1103 is the same as step 71 - step 73 in the embodiment shown in FIG. 6, wherein the H-FAP AAA server in step 1101 and step 1103 corresponds to the FAP AAA server in the embodiment of FIG.
  • Step 1104 The H-FAP AAA server selects the V_SeGW that is redirected by the FAP, that is, the H-FAP AAA server selects the entry of the FAP redirection.
  • the H-FAP AAA server queries the CSN list maintained on the H-FAP AAA server according to the identification information of the FAP.
  • the H-FAP AAA server learns according to the query result, the FAP is located in the visited V-CSN where the roaming contract protocol exists, and the H-FAP
  • the AAA server sends a roaming redirect message to the H-SeGW, where the roaming redirect message carries the address information of the preset roaming access security gateway (V-SeGW1).
  • Step 1105 The H-FAP AAA server sends a roaming redirection message to the FAP, where the roaming redirection message carries the address information of the V-SeGW1.
  • Step 1106 The FAP sends a FAP roaming redirection request to the V-SeGW1, where the FAP device identifier and the location information of the FAP are carried in the roaming redirection request.
  • Step 1107 The V-SeGW1 sends a FAP roaming redirection request to the V-FAP AAA server, where the FAP roaming redirection request carries the FAP identifier and the location information.
  • Step 1108 Assume that the V-FAP AAA server determines that the most suitable access to the V-ASN is the V-SeGW2 for the FAP.
  • Step 1109 The V-FAP AAA server sends a SeGW redirection message to the FAP, where the SeGW redirection message carries the address information of the V-SeGW2, and is used to notify the FAP to establish a connection with the V_SeGW2.
  • Step 1110 The FAP sends a redirection access request to the V-SeGW2, where the redirection access request carries the FAP identification information, and is used to request to access the network through the V-SeGW2.
  • Step 1111 The H-FAP AAA server processes the FAP authentication and authorization through the V-FAP AAA server and V_SeGW2.
  • Step 1112 - Step 1120 is the same as Step 78 - Step 716 in the corresponding embodiment of FIG. 7, wherein the implementation The V-SeGW2 in the example step 1112-step 1120 corresponds to the V_SeGW in the corresponding embodiment of FIG.
  • the V-ASN to which the current location area of the FAP belongs is not in the coverage area of the H-CSN, and the H-CSN and the V-CSN sign the FAP roaming agreement, and the V-ASN has a contractual relationship with the V-CSN.
  • the redirection process may be performed by two or more redirection processes to accurately direct the FAP to the appropriate V-SeGW provided by the V-FAP AAA server, which is beneficial to ensure the success rate of the FAP access network.
  • FIG. 12 is a signaling interaction diagram of a network access method of a FAP according to a thirteenth embodiment of the present invention.
  • the application scenario shown in FIG. 10 is used as an example to describe the FAP roaming redirection network access process; the interfaces between the nodes in the network architecture shown in FIG. 2 used in the FAP redirection network access process include: 1, 2, 3, 4, 5, 6 and 7.
  • the difference between this embodiment and the corresponding embodiment of FIG. 11 is that the embodiment allocates an authentication ASN-GW that is involved in the FAP authentication process by the V-FAP AAA server before roaming redirection.
  • this embodiment includes: Step 1201 - Step 1204 is the same as Step 1101 - Step 1104 in the corresponding embodiment of FIG.
  • Step 1205 The H-FAP AAA server sends a roaming redirection message to the FAP, where the roaming redirection message includes the V-SeGW1 information and the ASN-GW access identifier, and is used to notify the FAP that the authentication process needs to authenticate the ASN-GW to participate.
  • Step 1206 The FAP sends a FAP roaming redirection request to the V-SeGW1, where the FAP roaming redirection request includes the FAP identification information, the location information, and the ASN-GW access identifier.
  • Step 1207 The V-SeGW1 forwards the FAP roaming redirection request to the V-FAP AAA server.
  • Step 1208 The V-FAP AAA server selects the FAP redirected access V_SeGW2, that is, the V-FAP AAA server selects the FAP redirected entry.
  • Step 1210 The FAP sends a SeGW redirection request to the V-SeGW2, where the SeGW redirection request carries the FAP identification information, the location information, and the ASN-GW access identifier.
  • Step 1211 The V-SeGW2 sends an ASN-GW information request message to the V-FAP configuration center of the V-ASN, where the V-FAP configuration center is configured to allocate an authentication ASN-GW to the FAP.
  • the ASN-GW information request message carries FAP identification information, location information, and ASN-GW access identifier.
  • Step 1213 The V-FAP configuration center sends an ASN-GW information response to the V-SeGW2, where the ASN-GW information response carries the information of the authentication ASN-GW.
  • Step 1214 The H-FAP AAA server, the V-FAP AAA server, the authentication ASN-GW, and the V-SeGW perform authentication and authorization processing on the FAP.
  • Steps 1215-1223 are the same as step 1112-step 1120 in the corresponding embodiment of FIG.
  • FIG. 13 is a signaling interaction diagram of a method for accessing a FAP according to a fourteenth embodiment of the present invention.
  • the application scenario shown in FIG. 10 is used as an example to describe the FAP roaming redirection network access process; the interfaces between the nodes in the network architecture shown in FIG. 2 used in the FAP redirection network access process include: 1, 2, 3, 4, 5 and 6.
  • the difference between this embodiment and the corresponding embodiment of FIG. 11 is that the present embodiment performs the FAP authentication and authorization process before roaming redirection.
  • this embodiment includes:
  • Step 1304 The H-FAP AAA server and the H_SeGW perform authentication and authorization processing on the FAP.
  • Step 1305 The H-FAP AAA server selects the F-redirected V-SeGW, that is, the FAP AAA server selects the FAP redirected entry.
  • Step 1306 The H-FAP AAA server sends a roaming redirection message to the FAP, where the roaming redirection message carries the address information of the V-SeGW1 and the FAP authentication identifier, where the FAP authentication identifier is used to indicate that the FAP has passed the legality authentication.
  • Step 1308 The V-SeGW1 sends a FAP roaming redirection request to the V-FAP AAA server, where the FAP roaming redirection request carries the FAP identifier, the location information of the FAP, and the FAP authentication identifier.
  • Step 1312 The V-SeGW2 sends a network resource configuration request to the FAP configuration center (gp: V-FAP) of the V-FAP, where the network resource configuration request includes the FAP identification information and the FAP authentication identifier.
  • Step 1313 The V-FAP AAA server queries the saved FAP subscription file according to the FAP identification information, and obtains a context and a channel establishment parameter corresponding to the FAP identification information.
  • the channel establishment parameter is used for establishing the V-SeGW2.
  • Steps 1314 to 1317 are the same as steps 1115 to 1118 in the corresponding embodiment of Fig. 11, respectively.
  • Step 1318 The V-SeGW establishes a channel according to the acquired channel establishment parameter and the FAP.
  • Steps 1319 and 1320 are the same as steps 1119 and 1120 in the corresponding embodiment of FIG.
  • the method for transmitting the configuration parameters described in the embodiment of FIG. 5 can also be applied to the redirection scenario shown in FIG. 6, and can also be applied to the roaming scenario shown in FIG. 10, and details are not described herein again.
  • FIG. 14 is a schematic structural diagram of a network access system of a FAP access point according to a fifteenth embodiment of the present invention.
  • the network access system of the FAP includes: a FAP, a type of security gateway (SeGW1) (that is, the first security gateway in the embodiment of the present invention), and a second type of security gateway (SeGW2) (ie, the embodiment of the present invention) Second Security Gateway), Configuration Center, FAP AAA Server, and ASN-GW.
  • SeGW1 is used for the first orientation of the FAP, providing the FAP with a connection from the wired network to the CSN (eg, the FAP AAA server deployed in the CSN); SeGW2 is used for the second orientation of the FAP, providing access to the ASN for the FAP- GW connection.
  • Each contracted FAP is configured with an address of the security gateway SeGW1 for the default incoming connection.
  • the FAP only interacts with the FAP AAA server through the SeGW1, and only interacts with the FAP configuration center and the ASN-GW through the SeGW2, and finally accesses the ASN network that has a contractual relationship with the H-CSN through the SeGW2, or accesses the H-group with the FAP.
  • the CSN signs the V-ASN network with the contractual relationship of the V-CSN of the roaming agreement.
  • the FAP access process in the different application scenarios requires the FAP redirection process, that is, the FAP is directed from the SeGW1 to the SeGW2, and the FAP access ASN network access method and Figure 3_13
  • the SeGW1 in FIG. 12 corresponds to the H-SeGW in the embodiment shown in FIG. 3 to FIG. 13
  • the SeGW2 in FIG. 14 corresponds to the implementation in FIG. 3 to FIG. V-SeGW in the example (including: V-SeGW1 and V-SeGW2); will not be described again.
  • FIG. 15 is a schematic structural diagram of a network access device of a FAP according to a sixteenth embodiment of the present invention.
  • the network access device of the FAP of this embodiment includes: a network access request receiving module 151, a context obtaining module 152, and a context sending module 153.
  • the network access request receiving module 151 is configured to receive a network access request of the femto access point FAP.
  • the network access request may include identification information of the FAP.
  • the context obtaining module 152 is configured to acquire a context of the FAP according to the network access request.
  • the context sending module 153 is configured to send the context to the access service network ASN that the FAP needs to access, for the ASN to generate a configuration required for the FAP to enter the network according to the context and the current network configuration of the ASN. The parameters are sent to the FAP.
  • the context of the FAP may include: location information of the FAP.
  • the context of the FAP may further include: identifier information of the FAP, quality of service information of the FAP, closed subscriber group information, and the like.
  • the configuration parameters generated by the access service network for the FAP may include: an access service network gateway ASN-GW information, a FAP global unique identifier, an air interface parameter, and a paging group information, which are determined by the FAP for the FAP.
  • the network access device of the FAP may further include: an access network selection module 154.
  • the access network selection module 154 is configured to select a visited ASN for the FAP according to the location information of the FAP.
  • the FAP network access device may further include: a redirect entry determining module 155 and a redirect notification module.
  • the redirecting entry determining module 155 is configured to compare whether the visited ASN is the same as the home ASN of the FAP, and if not, determine the visited security gateway accessing the visited ASN for the FAP.
  • the redirect notification module 156 is configured to send the visited security gateway information to the FAP, to notify the FAP to establish a redirect connection with the visited security gateway.
  • the network access device of the FAP may be a FAP AAA server on a specific performance function entity.
  • FAP AAA server and the interaction between the FAP AAA server and other nodes during the FAP network access control, refer to the description of the corresponding embodiments in FIG. 3 to FIG. 14 , and details are not described herein again.
  • the network access device of the FAP can send a context to the ASN that the FAP needs to access according to the FAP network access request, which is beneficial to the ASN to allocate network resources and configuration parameters for the FAP, thereby providing support for the FAP access ASN to meet the application requirements of the FAP. .
  • FIG. 16 is a schematic structural diagram of a network access device of a FAP according to a seventeenth embodiment of the present invention. As shown in FIG. 16, the embodiment includes: a context receiving module 161, a configuration parameter generating module 162, and a configuration parameter sending module 163.
  • the context receiving module 161 is configured to receive a context of the FAP sent by the authentication authorization server according to the FAP network access request.
  • the configuration parameter generation module 162 is configured to generate, for the FAP, configuration parameters required for accessing the network according to the context and the current network configuration of the access service network.
  • the configuration parameter sending module 163 is configured to send the configuration parameter to the FAP.
  • the network access device of the FAP in this embodiment may be a FAP configuration center of the ASN on the specific performance function entity. turn off
  • FAP configuration center and the interaction between the FAP configuration center and other nodes during the FAP network access control, refer to the description of the corresponding embodiments in FIG. 3 to FIG. 14 , and details are not described herein again.
  • the FAP access device can configure the FAP access ASN according to the context of the FAP and the current network configuration of the ASN, thereby providing support for the FAP access ASN to meet the application requirements of the FAP.
  • the FAP can be accessed as a network element in the ASN to access the macro network, thereby facilitating the provision of effective access services for the terminal and meeting the application requirements of the FAP.
  • FIG. 17 is a schematic structural diagram of a network access system of a FAP according to an eighteenth embodiment of the present invention. As shown in FIG. 17, the embodiment includes: a security gateway (SeGW) 172, a first network access device 173, and a second network access device 174.
  • SeGW security gateway
  • the security gateway 172 is used to establish a connection between the nano access point 171 and the first network access device 173 and the second network access device 174.
  • the first network access device 173 is configured to receive a network access request of the FAP through the security gateway 172, acquire a FAP context corresponding to the identifier information of the FAP, and send the FAP context to an access service network (ASN) that the FAP needs to access.
  • the network access request may include identification information of the FAP.
  • the second network access device 174 is configured to receive a context of the FAP that is sent by the first network access device 173 according to the FAP network access request, and generate configuration parameters required for the network access to the FAP according to the FAP context and the current network configuration of the ASN; The configuration parameters are sent to the FAP through the security gateway 172.
  • the first network access device 173 of this embodiment refers to the description of the corresponding embodiment of FIG. 15, wherein the first network access device may be a FAP AAA server on a specific performance function entity.
  • the FAP AAA server and the networking structure of the FAP AAA server during the FAP network access control refer to the description of the corresponding embodiment in FIG. 3 to FIG. 14 , and details are not described herein again.
  • the second network access device 174 of this embodiment refers to the description of the corresponding embodiment of FIG. 16, wherein the second network access device may be the FAP configuration center of the ASN on the specific performance function entity.
  • the FAP configuration center and the interaction between the FAP configuration center and other nodes during the FAP network access control refer to the description of the corresponding embodiments in FIG. 3 to FIG. 14 , and details are not described herein again.
  • the connection between the FAP deployed in the wired network and the first network access device and the second network access device deployed in the macro network is established by the security gateway, and the first network access device performs the second request according to the FAP network access request.
  • the network access device sends the context of the FAP, and the second network access device generates configuration parameters according to the context of the FAP and the current network configuration of the ASN that the FAP needs to access, thereby providing support for the FAP access ASN to meet the application requirements of the FAP.
  • FIG. 18 is a schematic structural diagram of a network access system of a FAP according to a nineteenth embodiment of the present invention. As shown in FIG. 18, the embodiment includes: a first security gateway (SeGW1) 182, a second security gateway 183, a first network access device 184, and a The second access device 185.
  • SeGW1 first security gateway
  • second security gateway 183 second security gateway
  • the second access device 185 The second access device 185.
  • the first security gateway 182 is used to establish a connection between the nano-level access point 181 and the first network access device 184.
  • the first network access device 184 is configured to receive a network access request of the FAP by using the first security gateway 182, acquire a context of the FAP according to the network access request, and send the context to an access service network (ASN) that the FAP needs to access.
  • the network access request may include identification information of the FAP.
  • the second network access device 185 is configured to receive the first network access device 184 to send according to the FAP network access request.
  • Context of the FAP generating, according to the context and the current network configuration of the ASN, configuration parameters required for the FAP to be sent to the FAP; and transmitting, by the second security gateway 183, the configuration parameters to the FAP.
  • V-SeGW1 or V-SeGW2 the second security gateway in this embodiment may correspond to the H_SeGW in the corresponding embodiment of FIG. 6 to FIG. 13 and will not be described again.
  • the first network access device 184 For the detailed functional structure of the first network access device 184, refer to the description of the corresponding embodiment of FIG. 15, wherein the first network access device may be a FAP AAA server on a specific performance function entity.
  • the FAP AAA server and the networking structure of the FAP AAA server for FAP access control refer to the description of the corresponding embodiment in FIG. 3 to FIG. 14 , and details are not described herein again.
  • the second network access device 185 For the refinement function structure of the second network access device 185, refer to the description of the corresponding embodiment of FIG. 16, wherein the second network access device may be the FAP configuration center of the ASN on the specific performance function entity.
  • the FAP configuration center and the interaction between the FAP configuration center and other nodes during the FAP network access control refer to the description of the corresponding embodiments in FIG. 3 to FIG. 14 , and details are not described herein again.
  • the first security gateway establishes a connection between the FAP deployed in the wired network and the first network access device deployed in the macro network
  • the second security gateway establishes the FAP and the second network access device deployed in the macro network.
  • the connection between the FAP access ASN is provided to meet the application requirements of the FAP.
  • modules in the devices in the embodiments may be distributed in the devices of the embodiments according to the embodiments, or may be correspondingly changed in one or more devices different from the embodiment.
  • the modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.
  • the program instructions are related to hardware, and the foregoing program may be stored in a computer readable storage medium.
  • the program When executed, the program includes the steps of the foregoing method embodiment; and the foregoing storage medium includes: R0M, RAM, magnetic A variety of media that can store program code, such as a disc or a disc.

Landscapes

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

Description

毫微级接入点的入网方法、 装置和系统 本申请要求于 2009年 1月 16日提交中国专利局、申请号为 200910003500. X、发明 名称为 "毫微级接入点的入网方法、 装置和系统"的中国专利申请的优先权, 其全部内 容通过引用结合在本申请中。 技术领域 本发明实施例涉及通信技术, 特别是涉及一种毫微级接入点的入网方法、装置和系 统。 背景技术 由于多数通信话务量主要发生在室内, 因而需要有效地增强室内信号覆盖。通过增 强室外宏基站部署虽然可以增强室内信号覆盖率, 但将导致投资成本的明显增加, 同时 在站点选择、机房建设、传输费用和网络优化等方面也将面临各种难题。一种增强室内 覆盖可行的解决方案极为采用宏网络对室外信号覆盖,而在室内主要使用家庭接入点进 行覆盖。 毫微级蜂窝(Femto Cell ) 网络中的毫微级接入点 (Femto Access Point, 简 称 FAP) 是一种低功耗的家庭接入点, 用于提供小范围的无线覆盖, 主要应用在室内、 家中或 SOHO (Small Office Home Office)环境。
FAP通过有线宽带网络(如: 数字用户线路(Digital Subscriber Line, 简称 DSL) 宽带网络或互联网协议(Internet Protocol , 简称 IP) 网络等)接入全球微波接入互 操作性 (World Interoperability for Microwave Access, 简称 WiMAX)宏网络中, 并 在经过授权的频谱上为 WiMAX的移动终端 (Mobile Station, 简称 MS)提供接入服务。 在 FAP向终端提供接入服务之前, 必须保证 FAP可成功地接入 WiMAX宏网络。 由于 FAP 主要用于家庭、 室内或 S0H0环境, 因此 FAP数量比较庞大, 现有的 WiMAX宏网络中进 行入网管理的接入服务网 (Access Service Network, 简称 ASN) 中, 接入服务网网关 (Access Service Network GateWay, 简称 ASN-GW) 并不支持 FAP的直接接入。 因此, 现有技术存在着为 FAP接入 WiMAX网络提供入网解决方案的技术需求。 发明内容
本发明实施例提供一种毫微级接入点的入网方法、 装置和系统, 为 FAP实现接入 到接入服务网中提供技术支持, 从而满足 FAP的应用需求。 本发明实施例提供了一种毫微级接入点的入网方法, 包括:
接收毫微级接入点 FAP的入网请求;
根据所述入网请求, 获取所述 FAP的上下文;
向所述 FAP需要接入的接入服务网 ASN发送所述上下文, 以供所述 ASN根据所述上 下文和所述 ASN当前网络配置为所述 FAP生成入网所需的配置参数并向所述 FAP发送。
本发明实施例还提供了另一种毫微级接入点的入网方法, 包括:
接收鉴权授权服务器根据 FAP入网请求发送的所述 FAP的上下文;
根据所述上下文和接入服务网当前网络配置,为所述 FAP生成入网所需的配置参数; 向所述 FAP发送所述配置参数。
本发明实施例还提供了一种毫微级接入点的入网装置, 包括:
入网请求接收模块, 用于接收毫微级接入点 FAP的入网请求;
上下文获取模块, 用于根据所述入网请求, 获取所述 FAP的上下文;
上下文发送模块, 用于向所述 FAP需要接入的接入服务网 ASN发送所述上下文, 以 供所述 ASN根据所述上下文和所述 ASN当前网络配置为所述 FAP生成入网所需的配置参 数并向所述 FAP发送。
本发明实施例还提供了另一种毫微级接入点的入网装置, 包括:
上下文接收模块,用于接收鉴权授权服务器根据 FAP入网请求发送的所述 FAP的上 下文;
配置参数生成模块,用于根据所述上下文和接入服务网的当前网络配置,为所述 FAP 生成入网所需的配置参数;
配置参数发送模块, 用于向所述 FAP发送所述配置参数。
本发明实施例还提供了一种毫微级接入点的入网系统, 包括: 安全网关、第一入网 装置和第二入网装置;
所述第一入网装置用于通过所述安全网关接收毫微级接入点 FAP的入网请求;根据 所述入网请求, 获取所述 FAP的上下文; 向所述 FAP需要接入的接入服务网 ASN发送所 述上下文;
所述第二入网装置用于接收所述第一入网装置根据 FAP入网请求发送的所述 FAP的 上下文; 根据所述上下文和所述 ASN当前网络配置, 为所述 FAP生成入网所需的配置参 数; 通过所述安全网关向所述 FAP发送所述配置参数。
本发明实施例还提供了另一种毫微级接入点的入网系统, 第一安全网关、第二安全 网关、 第一入网装置和第二入网装置;
所述第一入网装置用于通过所述第一安全网关接毫微级接入点 FAP的入网请求;根 据所述入网请求, 获取所述 FAP的上下文; 向所述 FAP需要接入的接入服务网发送所述 上下文;
所述第二入网装置用于接收所述第一入网装置根据 FAP入网请求发送的所述 FAP的 上下文; 根据所述上下文和所述 ASN当前网络配置, 为所述 FAP生成入网所需的配置参 数; 通过所述第二安全网关向所述 FAP发送所述配置参数。
本发明实施例提供的 FAP的入网方法、装置和系统, 使得 FAP可获取网络接入所需的 配置参数, 在 FAP接收到配置参数之后, 可根据接收到配置参数进行相应配置, 并通过 ASN-GW接入到 ASN中。 在 FAP成功接入到 ASN时, FAP即可作为 ASN中的一个网元接入到宏 网络, 从而有利于为终端提供有效的接入服务, 满足 FAP的应用需求。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有 技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本 发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其它的附图。
图 la为本发明第一实施例提供的 FAP的入网方法流程图;
图 lb为本发明第二实施例提供的 FAP的入网方法流程图;
图 2为本发明第三实施例提供的 FAP的入网系统的结构示意图;
图 3为本发明第四实施例提供的 FAP的入网方法信令交互图;
图 4为本发明第五实施例提供的 FAP的入网方法信令交互图;
图 5为本发明第六实施例提供的 FAP的入网方法信令交互图;
图 6为本发明第七实施例提供的 FAP重定向的应用场景示意图;
图 7为本发明第八实施例提供的 FAP的入网方法信令交互图;
图 8为本发明第九实施例提供的 FAP的入网方法信令交互图;
图 9为本发明第十实施例提供的 FAP的入网方法信令交互图;
图 10为本发明第十一实施例提供的 FAP漫游入网重定向的应用场景示意图; 图 11为本发明第十二实施例提供的 FAP的入网方法信令交互图;
图 12为本发明第十三实施例提供的 FAP的入网方法信令交互图; 图 13为本发明第十四实施例提供的 FAP的入网方法信令交互图; 图 14为本发明第十五实施例提供的 FAP接入点的入网系统的结构示意图; 图 15为本发明第十六实施例提供的 FAP的入网装置结构示意图;
图 16为本发明第十七实施例提供的 FAP的入网装置结构示意图;
图 17为本发明第十八实施例提供的 FAP的入网系统结构示意图;
图 18为本发明第十九实施例提供的 FAP的入网系统结构示意图。 具体实施方式 下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行清楚、完整 地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是全部的实施例。 基 于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有 其它实施例, 都属于本发明保护的范围。
本发明实施例中的 "入网"即为接入到接入服务网 (ASN) 中, 以使成功接入到接 入服务网的 FAP具有向终端提供网络接入的功能。 当 FAP成功接入到接入服务网中时, FAP即可通过接入服务网与外部的宏网络建立连接, 从而保证为终端提供有效的接入服 务。
图 la为本发明第一实施例提供的 FAP的入网方法流程图。如图 la所示, 本实施例 包括:
步骤 l la、 接收毫微级接入点 (FAP) 的入网请求。
所述入网请求可包括所述 FAP的标识信息。
步骤 12a、 根据所述入网请求, 获取所述 FAP的上下文。
在所述入网请求包括所述 FAP的标识信息时,可获取与所述 FAP的标识信息相应的 FAP上下文。 获取的所述 FAP的上下文可包括: FAP的位置信息。 该 FAP的上下文还可 进一步包括: FAP的标识信息、 FAP的服务质量信息和闭合用户群信息等。
步骤 13a、 向所述 FAP需要接入的接入服务网 ASN发送所述上下文, 以供所述 ASN 根据所述上下文和所述 ASN当前网络配置为所述 FAP生成入网所需的配置参数并向所述 FAP发送。
向 ASN发送的 FAP的上下文中可包括: FAP的位置信息和 FAP的标识信息。 该 FAP 的上下文还可包括: FAP的服务质量信息和闭合用户群信息等。
ASN为所述 FAP生成入网所需的配置参数可包括: 为所述 FAP确定的所述 FAP入网 连接的 ASN-GW信息、 FAP的全球唯一标识、 空口参数和寻呼组信息。
ASN可通过安全网关向所述 FAP发送配置参数, 其中, ASN向安全网关发送的参数 包括: ASN-GW信息、 FAP的全球唯一标识、 空口参数和寻呼组信息; 安全网关向 FAP发 送的参数包括: FAP的全球唯一标识、 空口参数和寻呼组信息; 安全网关向 FAP发送的 参数还可进一步包括: ASN-GW信息。
进一步的, ASN还可向 ASN-GW发送相应参数, 其中, ASN向 ASN-GW发送的参数可 包括: FAP的全球唯一标识、 所述 FAP的位置信息和所述空口参数。
本实施例的执行主体可为部署在网络侧的 FAP 鉴权授权服务器 (FAP Authentication Authorization Accounting Server, 简称 FAP AAA月艮务器), 通过 FAP AAA服务器根据 FAP的入网请求向 FAP需要接入的 ASN发送 FAP上下文, 有利于 ASN为 FAP分配网络资源和配置参数, 从而为 FAP接入 ASN提供支持, 满足 FAP的应用需求。
图 lb为本发明第二实施例提供的 FAP的入网方法流程图。 如图 lb所示, 本实施 例包括:
步骤 l lb、 接收 FAP AAA服务器根据 FAP入网请求发送的所述 FAP的上下文。 步骤 12b、 根据所述上下文和 ASN当前网络配置, 为所述 FAP生成入网所需的配置 参数。
步骤 13b、 向所述 FAP发送所述配置参数。
本实施例的执行主体可为部署在 ASN中的 FAP配置中心。
上述技术方案步骤 l ib中, FAP配置中心接收 FAP的上下文包括: FAP配置中心通 过 FAP AAA服务器直接接收 FAP的上下文。 或者, FAP配置中心接收 FAP的上下文还可 包括 FAP配置中心间接接收 FAP的上下文,如: FAP AAA服务器向安全网关发送所述 FAP 的上下文, FAP配置中心通过安全网关接收所述 FAP的上下文。 接收的 FAP的上下文包 括 FAP的位置信息, 还可包括 FAP的标识信息。
上述技术方案步骤 12b中, ASN为所述 FAP生成入网所需的配置参数可包括: 为所 述 FAP确定的所述 FAP入网连接的 ASN-GW信息、 FAP的全球唯一标识、空口参数和寻呼 组信息。
上述技术方案步骤 13b中, FAP配置中心可通过安全网关向所述 FAP发送配置参数, 其中, FAP配置中心向安全网关发送的参数包括: ASN-GW信息、 FAP的全球唯一标识、 空口参数和寻呼组信息; 安全网关向 FAP发送的参数包括: FAP的全球唯一标识、 空口 参数和寻呼组信息; 安全网关向 FAP发送的参数还可进一步包括: ASN-GW信息。 进一步的, FAP配置中心还可向 ASN-GW发送相应参数,其中, FAP配置中心向 ASN-GW 发送的参数可包括: FAP的全球唯一标识、 所述 FAP的位置信息和所述空口参数。
本实施例使得 FAP可获取网络接入所需的配置参数,在 FAP接收到配置参数之后, 可根据接收到配置参数进行相应配置, 并通过 ASN-GW接入到 ASN网络。 在 FAP成功接 入到 ASN网络时, FAP即可作为 ASN网络中的一个网元接入到宏网络, 从而有利于为终 端提供有效的接入服务, 满足 FAP的应用需求。
图 2为本发明第三实施例提供的 FAP的入网系统的结构示意图。如图 2所示, FAP 的入网系统中, 包括: FAP、 安全网关 (SeGW)、 配置中心、 FAP鉴权授权服务器(FAP Authent icat ion Authorizat ion Account ing Server, 简称 FAP AAA月艮务器)禾口接人月艮 务网网关(ASN-GW)。
WiMAX宏网络中, 宏基站(BS )通过接入服务网网关(ASN Gateway, 简称 ASN-GW) 进行统一管理, 移动终端(MS )经由宏基站并通过 ASN-GW接入到 WiMAX宏网络中。 FAP 可看作一种低功率的、 用于提供小范围室内覆盖的小型基站, 具有 BS的部分功能, 因 而也由 ASN-GW进行接入 WiMAX宏网络的入网过程进行统一管理。 但 FAP是通过有线网 络接入 WiMAX宏网络, 由于有线网络和 WiMAX网络的网络协议不同以及出于安全性的考 虑, FAP和 ASN-GW之间没有直接的通信接口,需要对 FAP和 ASN-GW的交互进行性协议 转换, FAP需要通过安全网关(Security Gateway, 简称 SeGW) 与 ASN-GW建立连接。
图 2所示的系统结构中, 安全网关(SeGW)用于为 FAP提供从有线网络到 WiMAX 宏网络的接入控制, 实现网关功能和安全功能。 每个 FAP上都预先配置有一个默认的 SeGW的信息 (如: SeGW的地址信息), 当 FAP需要从有线网络连接到 WiMAX宏网络时, 都会通过自身配置的默认 SeGW发起相应的入网流程。
配置中心用于对 FAP进行集中的配置管理以及用于为 FAP入网分配网络资源。 配 置中心用于保存或可获取 ASN中每一个 BS的信息, 信息至少包括 BS ID, BS空口参数, 各 BS对应的地址区间, 配置中心还用于保存或能获取 BS对应的 ASN-GW信息 (包括 ASN-GW ID等), 以及配置中心还用于保存已接入的 FAP的信息, FAP的信息可包括 FAP ID, 空口参数, 以及其它 FAP在入网过程中获取的上下文。
FAP鉴权授权服务器用于保存与自身有签约关系的 FAP 的签约档案 (Profi le ) ( FAP的签约档案中包括有 FAP的上下文),维护与自身有签约关系的 ASN信息列表以及 与 ASN有对应关系的 SeGW信息列表, 主要负责 FAP的入网认证、 授权处理和其它管理 维护工作。 图 2所示的系统结构中, 接口 1用于 FAP和 SeGW之间进行消息的传输; 接口 2用 于 SeGW和 FAP AAA服务器之间对 FAP进行认证授权、 FAP上下文传输或 SeGW与 FAP AAA 服务器之间其它的信令传输; 接口 3用于 SeGW与配置中心之间进行 FAP上下文传输、 触发网络资源分配过程等; 接口 4用于配置中心与 FAP AAA服务器之间的交互, 如进行 FAP上下文的传输; 接口 5用于 ASN-GW与配置中心之间的连接, 接口 7用于 ASN-GW与 FAP AAA服务器之间的连接; 接口 5和接口 7都可用于 ASN-GW获取 FAP的上下文。接口 5可具体为 R4接口, 而接口 7可为 R3接口。 接口 6为 SeGW和 ASN-GW之间的接口, 用 于 SeGW和 ASN-GW之间的交互, 承载 FAP与 ASN-GW之间的 R6接口。在图 2涉及节点的 部署过程中, SeGW、 FAP配置中心和 FAP AAA服务器可作为一个 FAP的入网系统进行集 中部署。
此外, SeGW、 FAP配置中心和 FAP AAA服务器也可根据实际需要进行独立部署; 或 者, 将 SeGW、 FAP配置中心或 FAP AAA服务器作为一个功能模块部署在现有网络架构的 网元中。例如: SeGW可单独部署, 也可与现有技术网络架构中的网元 ASN-GW—起部署; 或者将 SeGW实现的各功能进行分离部署。 FAP配置中心也可单独部署,或与其它网元一 起部署。 FAP AAA服务器的部署可由 FAP的签约关系而定, 可部署在 ASN网内或 CSN网 内。 具体的, FAP通常具有两种签约关系:
( 1 ) FAP与网络服务提供商 (Network Service Provider, 简称 NSP)存在签约 关系; 该情形下, FAP的入网过程需要 NSP对 FAP进行认证和授权处理, FAP AAA服务 器可部署在 NSP管理的连接服务网 (Connectivity Service Network, 简称 CSN) 中; ( 2 ) FAP与网络接入提供商 (Network Access Provider, 简称 NAP)存在签约关 系; 该情形下, FAP的入网过程需要 ASN对 FAP进行认证和授权处理, FAP AAA服务器 可部署在 NAP管理的 ASN中。
图 3-图 13对应的实施例均以图 2所示的系统为例,进一步说明本发明 FAP的不同 应用场景下实现入网的技术方案。其中, 图 3-图 5所示实施例对应 FAP本地入网的应用 场景; 图 6-图 9所示实施例对应 FAP本地重定向入网的应用场景; 图 10-图 13所示实 施例对应 FAP漫游重定向入网的应用场景。
为便于描述本发明实施例的技术方案,对本发明实施例涉及的技术名词说明如下: 默认 SeGW: FAP预先设置的 SeGW,用于 FAP连接有线宽带网络后向 FAP提供到 FAP AAA服务器的连接;
接入 SeGW: 本地重定向应用场景中, FAP的重定向入口; 漫游接入 SeGW: 漫游重定向场景中, FAP的漫游重定向入口;
ASN-GW接入标识: 用于 FAP AAA服务器利用该标识通知 ASN或 FAP需要 ASN-GW 参与认证, 是否下发该标识由 FAP AAA服务器的认证策略决定;
接入 ASN-GW: FAP配置中心为 FAP选择的 ASN-GW,用于 FAP接入 ASN, FAP入网成 功后可以与一个接入 ASN-GW建立连接;
认证 ASN-GW: FAP配置中心为 FAP选择的 ASN-GW, 在 FAP AAA服务器下发 ASN-GW 接入标识的情况下参与 FAP认证;
家乡地 CSN (H-CSN) : FAP签约的 CSN;
拜访地 CSN (V-CSN) : 覆盖 FAP位置所在区域的 CSN, 与家乡地 CSN签署了 FAP漫 游协议的 CSN;
家乡地 ASN (H-ASN) : FAP默认 SeGW所在的 ASN, 与家乡地 CSN具有签约关系; 拜访地 ASN (V-ASN) : 除家乡地 ASN以外、 覆盖 FAP位置所在区域的 ASN。
图 3为本发明第四实施例提供的 FAP的入网方法信令交互图。 本实施例的应用场 景为: 基于图 2所示的网络架构实现的 FAP本地入网场景; 在实现过程中利用的图 2所 示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 4、 5和 6。 本实施例中, FAP 可与家乡地 ASN对应的 NAP具有签约关系, 将 FAP AAA服务器部署在家乡地 ASN中。 或 者, FAP还可与家乡地 CSN对应的 NSP具有签约关系, 而将 FAP AAA服务器部署在家乡 地 CSN中。如图 3所示, 本实施例中的 SeGW为与 FAP上配置的 FAP入网的默认 SeGW地 址信息对应的默认 SeGW。 本实施例包括:
步骤 31、 FAP连接有线网络, 并向 SeGW发送入网请求。
该入网请求中可携带有 FAP的标识信息。
FAP上预先配置有默认 SeGW的地址信息, 当 FAP需要接入 ASN时, 会通过有线网 络向与自身配置的地址信息相应的默认 SeGW发送入网请求。 入网请求中携带 FAP的标 识信息可包括: FAP设备标识、 用户标识、 FAP的签约信息等, 其中, 签约信息用于表 明与 FAP具有签约关系的 FAP AAA服务器, 以便默认 SeGW根据签约信息确定入网请求 的目的地址; 或者, 签约信息可以由 FAP设备标识或者用户标识携带, 在这种情况下不 需要单独的签约信息。
之外, 入网请求还可携带有 FAP的其它信息, 如: FAP的位置参数、 FAP的用户信 息等。
步骤 32、 SeGW向 FAP AAA服务器发送入网请求。 SeGW上预先配置了具有签约关系的 FAP AAA服务器的地址, 当 SeGW接收到 FAP 上报的入网请求时, 将入网请求发送给与 FAP的标识信息相应的 FAP AAA服务器。
步骤 33、 发起 FAP的定位流程, 通过 FAP的定位流程获取 FAP的位置信息。
本步骤为可选步骤。在 FAP的定位流程中, FAP和 FAP AAA服务器之间可通过 ISP、 GPS或邻区列表等方式获取 FAP的位置信息, 获取的 FAP的位置信息可用于对 FAP的认 证授权或配置参数的流程中。
本步骤可发生在本实施例步骤 35之前的某个时刻, 例如: 本步骤可在步骤 31或 步骤 32之前执行, 或者, 本步骤还可在步骤 34之前或步骤 34之后执行。 如果 FAP的 位置信息已知, 也可不执行本步骤进行 FAP的定位, 即不执行步骤 33。
步骤 34、 FAP AAA服务器通过 SeGW对 FAP进行认证和授权处理。
在 FAP通过认证和授权处理后, 执行步骤 35。
步骤 35、 SeGW根据认证和授权处理后的密钥信息, 与 FAP建立通道。
本步骤也可发生在步骤 35与步骤 312之间的某个时刻。
步骤 36、 SeGW向 SeGW所属的 ASN的 FAP配置中心发送网络资源配置请求, 用于 请求为 FAP分配网络资源及配置入网参数; 其中, 网络资源配置请求中包括 FAP的标识 信息。
步骤 37、 FAP配置中心向 FAP AAA服务器发送 FAP参数请求, 用于请求获取 FAP 的上下文; FAP参数请求中携带有 FAP的标识信息, FAP配置中心可向 FAP AAA服务器 获取与该标识信息相应的 FAP上下文。
步骤 38、 FAP AAA服务器根据 FAP的标识信息查询保存的 FAP签约档案, 获取与 该标识信息相应的 FAP上下文, 并向 FAP配置中心发送 FAP参数响应; FAP参数响应中 携带有 FAP上下文。 FAP上下文可包括 FAP的位置信息(Location)。 FAP的上下文还可 包括 FAP的标识信息, 进一步的, FAP的上下文还可包括: FAP的认证状态信息、 FAP 的服务质量(Qual ity of Service,简称 QoS )和 FAP的闭合用户群(Closed Subscriber Group, 简称 CSG)等参数。
FAP配置中心可以在步骤 36和步骤 38 中的任意一个步骤获取 FAP 的位置信息 ( ocatior 。
步骤 39、 FAP配置中心根据获取的 FAP上下文, 为 FAP分配网络资源, 并为 FAP 生成 FAP接入 ASN所需的配置参数。
本步骤 FAP配置中心还用于从 FAP AAA服务器或默认 SeGW获取 FAP上下文, 动态 维护获取的 FAP上下文;从接入 ASN-GW处获取 PG参数;为 FAP确定 FAP ID,空口参数; 向 ASN-GW和 SeGW提供所需 FAP参数等。
其中, FAP配置中心为 FAP分配网络资源可包括: 为 FAP确定接入 ASN-GW。为 FAP 生成的配置参数可包括:
FAP ID: FAP ID是 FAP配置中心分配给 FAP在接入服务网中的全球唯一的标识;
ASN-GW信息: 为 FAP确定的 FAP入网连接的接入服务网网关的信息;
空口参数: 用于配置 FAP可使用的空口资源;
寻呼组(Paging Group, 简称 PG) : PG参数可包括 PG ID, 由 ASN-GW分配, 并由 配置中心从 ASN-GW获取, 涉及到 FAP接入 ASN网络之后进行寻呼控制。
进一步的, FAP配置中心为 FAP生成的配置参数还可包括:
QoS :对应于 FAP的 QoS策略,可包括规定的来自 FAP业务的带宽、业务优先级等;
CSG:用于实现闭合用户群用户通过特定 FAP获得优先接入或者获取预留接入资源 的功能, 以支持毫微级蜂窝系统的 CSG业务模型和相关应用。
FAP配置中心为 FAP生成的配置参数, 需要发送给默认 SeGW和接入 ASN_GW。 步骤 310、 FAP配置中心向接入 ASN-GW发送 FAP接入 ASN所需的配置参数, 该配 置参数可包括:
FAP ID: 用于接入 ASN-GW标识和寻址 FAP;
Locat ion: FAP位置信息;
空口参数: 用于接入 ASN-GW管理优化无线环境和 BS空口资源。
FAP配置中心向接入 ASN-GW发送的配置参数中还可进一步包括:
QoS : 对应于 FAP的 QoS策略, 包括规定来自 FAP业务的带宽、 业务优先级等; 接入 ASN-GW收到 FAP配置中心下发的配置参数后, 根据这些配置参数, 协商 FAP 可使用的网络资源与覆盖 FAP所在地的宏网络的网络资源。协商完成之后,接入 ASN-GW 已做好与 FAP建立连接的准备。
步骤 311、 FAP配置中心向 SeGW发送为 FAP接入 ASN所需的配置参数, 该配置参 数可包括:
FAP ID: 用于 SeGW标识 FAP;
ASN-GW Info: 用于标识和寻址 FAP的认证 ASN-GW或者接入 ASN_GW。
此外, FAP配置中心还将 FAP所需的配置参数通过 SeGW发送给 FAP, SeGW, 根据 参数进行配置, 如 SeGW需要建立 FAP标识与 FAP ID的映射关系等。 此外, SeGW还将 FAP自配置所需的配置参数发送给 FAP。步骤 310和步骤 311之间没有时序关系的限制。 步骤 312、 SeGW向 FAP发送 FAP配置中心为 FAP生成的配置参数, 该配置参数可 包括: FAP ID、 FAP的 PG、 ASN-GW Info和 FAP可使用的空口参数等。其中, SeGW向 FAP 转发配置参数中 ASN-GW Info为可选信息,如果 FAP支持 FAP与 ASN-GW的交互通过 SeGW 代理, SeGW向 FAP发送的配置参数中可不需要携带 ASN-GW Info; 否则, SeGW向 FAP 转发配置参数中需携带 ASN-GW Info参数。
步骤 313、 FAP根据接收的配置参数进行自配置, 开启空口并向终端(MS )提供接 入服务, 例如: FAP根据接收的配置参数完成物理层、 链路层配置, 开放空口资源, 周 期性发送无线信号和广播消息,可接收来自终端的消息;完成 FAP接入 ASN网络的流程。
本实施例在对 FAP认证授权之后, 根据 FAP的认证授权状态信息和 FAP上下文为
FAP确定需要接入的接入服务网的 ASN-GW,并分别为 FAP和 ASN-GW生成 FAP通过 ASN-GW 入网所需的配置参数, 实现了 FAP根据网络侧下发的配置参数在签约地接入(即: 本地 接入)宏网络, 从而有利于 FAP为终端提供有效的接入服务。
图 4为本发明第五实施例提供的 FAP的入网方法信令交互图。 本实施例的应用场 景为: 基于图 2所示的网络架构实现的 FAP本地入网场景; 在实现过程中利用的图 2所 示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 4、 5、 6和 7。 与图 3对应的 实施例的区别在于, 本实施例对 FAP的认证流程不同, 本实施例 FAP配置中心在认证前 为 FAP分配一个认证 ASN-GW, 默认 SeGW和认证 ASN-GW都参与 FAP认证过程。 如图 4 所示, 本实施例包括:
步骤 41-步骤 43与图 3所示实施例中步骤 31-步骤 33相同,其中 FAP的定位流程, 可在步骤 41之前执行, 或在步骤 42执行, 或在步骤 48之前执行。
步骤 44、 FAP AAA服务器向 SeGW发送 ASN-GW接入请求, 该 ASN-GW接入请求携带 有 ASN-GW接入标识, 用于通知 SeGW在 FAP的认证流程中需要 ASN-GW的参与。
FAP AAA服务器可根据预先制定的 FAP认证策略, 确定需要 ASN-GW参与到 FAP认 证流程中, 之后将既定的 FAP认证策略, 通过 ASN-GW接入请求通知 SeGW。
步骤 45、 SeGW向 FAP配置中心发送 ASN-GW信息请求(BP: ASN-GW Info请求), 用于请求 FAP配置中心为 FAP选择一个认证 ASN-GW参与 FAP认证,该 ASN-GW信息请求 中携带有 FAP的位置信息(Location)。在认证过程中 FAP需要与认证 ASN-GW建立连接 关系, 该认证过程的连接关系如下: FAP— SeGW—认证 ASN-GW— FAP AAA服务器, 在认 证过程中使用了利用了接口 1, 6和 7。 FAP的位置信息可通过 FAP在入网请求中主动上报给 SeGW,也可由 SeGW在 FAP的 重定向流程中获取。
步骤 46、 FAP配置中心为 FAP选择一个参与 FAP认证的认证 ASN_GW。
FAP配置中心为 FAP选择参与 FAP认证的认证 ASN-GW的实现方式上, 可根据 FAP 位置信息, 将 FAP家乡地 ASN的接入 ASN-GW确定为参与 FAP认证的认证 ASN-GW, 该情 形下, 本实施例步骤 413中不需要为 FAP重新确定 FAP需要接入的接入服务网的接入 ASN-GW, BP: FAP需要接入的接入服务网的接入 ASN-GW与参与 FAP认证的认证 ASN-GW 相同。 图 4仅示出了接入 ASN-GW和认证 ASN-GW相同的情形。
此外, FAP配置中心还可根据当前网络现状选择一个认证 ASN-GW, 该情形下, 如 果参与 FAP认证的认证 ASN-GW与 FAP的接入 ASN-GW不同时,本实施例还需要通过步骤 413为 FAP确定需要接入的接入服务网的接入 ASN-GW。
步骤 47、 FAP配置中心向 SeGW发送 ASN-GW Info响应消息时, 在 ASN-GW Info上 携带有可参与到 FAP认证流程中的认证 ASN-GW的地址信息。
步骤 48、 FAP AAA服务器通过步骤 46选择的认证 ASN-GW以及 SeGW对 FAP进行认 证和授权处理。
步骤 49-步骤 417与图 3对应的实施例步骤 35-步骤 313的记载相同, 不再赘述。 本实施例在对 FAP认证授权之前, 为 FAP确定一个可参与到 FAP的认证和鉴权处 理的认证 ASN-GW, FAP AAA服务器通过该认证 ASN-GW和 SeGW对 FAP进行认证和鉴权处 理, 在对 FAP进行有效的认证和授权处理后, 为 FAP确定接入 ASN-GW以及配置参数, 为 FAP接入 ASN提供有效的支持, 从而满足 FAP的应用需求。
图 5为本发明第六实施例提供的 FAP的入网方法信令交互图。 本实施例的应用场 景为: 基于图 2所示的网络架构实现的 FAP本地入网场景; 在实现过程中利用的图 2所 示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 5和 6 。 与图 3对应的实施 例的区别在于, 本实施例 FAP配置中心没有与 FAP AAA服务器的接口, 不能直接与 FAP AAA服务器交互, 也就不能从 FAP AAA服务器处获取 FAP 的上下文; 该实施例中, FAP 配置中心从默认 SeGW处获取 FAP的上下文。 如图 5所示, 本实施例包括:
步骤 51-步骤 54与图 3所示实施例中步骤 31-步骤 34相同。
步骤 55、 FAP AAA服务器在完成 FAP的认证和授权处理之后, 向 SeGW发送 FAP参 数下发消息,该 FAP参数下发消息携带了 FAP配置中心完成 FAP接入 ASN所需的 FAP上 下文,其中, FAP上下文可包括 FAP的位置信息(Locat ion)。 FAP的上下文还可包括 FAP 的标识信息, 进一步的, FAP的上下文还可包括: FAP的认证状态信息、 FAP的服务质 量 (Qual ity of Service, 简称 QoS )和 FAP的闭合用户群 (Closed Subscriber Group, 简称 CSG)等参数。
步骤 56、 SeGW收到 FAP参数下发消息之后, 向 FAP AAA服务器返回响应消息。 步骤 55和步骤 56可结合步骤 54进行, 即可在 FAP AAA服务器对 FAP进行认证和 授权处理的过程中实现。
步骤 57与图 3所示实施例中步骤 35相同, 建立 SeGW与 FAP之间的通道。
步骤 57也可在步骤 54-步骤 512之间的时间段内完成。
步骤 58、SeGW向 FAP配置中心发送 FAP网络资源配置请求消息,该消息携带了 FAP AAA服务器下发的 FAP上下文。
步骤 59、 FAP配置中心通过 SeGW发送的 FAP网络资源配置请求消息, 获取 FAP上 下文, 根据 FAP上下文为 FAP分配网络资源并生成 FAP的配置参数, 具体过程详见图 3 对应实施例中步骤 39的记载。
步骤 510-步骤 513与图 3对应实施例中步骤 310-步骤 313相同。
本实施例 FAP配置中心从 SeGW处获取 FAP的上下文,根据 FAP上下文以及 ASN当 前的网络配置, 为 FAP确定 ASN-GW以及配置参数, 为 FAP接入 ASN提供有效的支持, 从而满足 FAP的应用需求。
图 6为本发明第七实施例提供的 FAP重定向的应用场景示意图。本实施例基于图 2 所示的系统架构实现, 其中 FAP AAA服务器位于 CSN。 在图 6所示的应用场景中, FAP 与 NSP存在签约关系, FAP AAA服务器部署在 NSP管理的 CSN中; 与一个 CSN存在签约 关系的 ASN可能有多个, 图 6所示的应用场景中与 CSN存在签约关系的 ASN有二个: 家 乡地 ASN (H-ASN)和拜访地 ASN (V-ASN); 其中, 默认 SeGW (H-SeGW)位于 H-ASN中, 接入 SeGW (V-SeGW)位于 V-ASN中。
在图 6所示的应用场景中, FAP上默认配置的 H-SeGW位于 H-ASN, 而 FAP当前所 在地为 V-ASN的覆盖范围,因此在 FAP入网过程中, CSN网络需要将 FAP从 H_SeGW重定 向到 FAP当前所在的 V-ASN覆盖区域的 V-SeGW上,使得 FAP可通过 V-SeGW接入 V_ASN。 FAP重定向流程可包括:
步骤 61、 FAP向 H-SeGW发送入网请求, 该入网请求中携带有 FAP的标识信息和位 置信息。
无论 FAP上配置的 H-SeGW所在的 ASN网络是否与 FAP当前所在的 ASN网络是否一 致, 当 FAP需要接入 ASN网络时, 都会向自身配置的 H-SeGW发送入网请求。
FAP的标识信息可包括: FAP设备标识、 用户标识或 FAP的签约信息等。 签约信息 用于表明与 FAP具有签约关系的 FAP AAA服务器, 以便 H-SeGW根据签约信息确定入网 请求的目的地址; 签约信息可作为一个独立的标识信息, 或者, 签约信息可携带在 FAP 设备标识或者用户标识中。
步骤 62、 H-SeGW向部署在 CSN网络中的 FAP AAA服务器转发入网请求, 该入网请 求中携带有 FAP的标识信息和位置信息。
步骤 63、FAP AAA服务器根据 FAP的标识信息和位置信息,为 FAP确定接入的 V-ASN 的 V-SeGW, 向 H-SeGW发送 SeGW重定向消息,该 SeGW重定向消息中携带 V_SeGW的地址 信息, 执行步骤 64。
本步骤中, FAP AAA服务器上维护有 ASN列表, ASN列表中保存的信息包括: SeGW 与 FAP AAA服务器所在的 CSN签约的 ASN的映射关系; 以及 SeGW对应的位置区间信息 等。 当 FAP AAA服务器接收到入网请求时, 获取 FAP的标识信息和位置信息。 FAP AAA服 务器根据 FAP位置信息查询 ASN列表, 可知 FAP当前所在的位置区对应的 SeGW, 根据 SeGW与 ASN 的映射关系继而获知该 SeGW对应的 ASN; FAP AAA服务器判断该 ASN是否 为 FAP的家乡地 ASN, 如果不是, 则需要将 FAP重定向到拜访地 ASN的 V-SeGW, 执行步 骤 64; 如果相同, 则不需要对 FAP进行重定向处理, 结束本流程 (图 6未示出)。
步骤 64、H-SeGW向 FAP转发 SeGW重定向消息,该 SeGW重定向消息中携带有 V_SeGW 的地址信息。
步骤 65、 FAP通过 V-SeGW发起 V-ASN的接入流程。
FAP在完成从 H-SeGW重定向到 V-SeGW之后, 可采用图 3、 图 4或图 5对应实施例 的实现方法, 通过 V-SeGW实现的 V-ASN的入网流程。
FAP需要通过部署在 V-ASN中的 FAP配置中心,根据 FAP所在地的空口环境,提供 FAP的配置和入网的后续管理,因而 FAP在入网过程中须从 V-ASN接入。本实施例当 FAP 的 H-ASN, 与 FAP所在的 V-ASN不一致时, 可通过重定向流程, 将 FAP重定向到 V-ASN 对应的 V-SeGW中, 通过 V-SeGW接入 V-ASN, 有利于保证 FAP入网的成功率。
图 7为本发明第八实施例提供的 FAP的入网方法信令交互图。 本实施例是以图 6 所示的应用场景为例说明 FAP重定向入网过程;在实现 FAP重定向入网过程中利用的图 2所示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 4、 5和 6。 本实施例是 以图 6所示的应用场景为例, 进一步说明本发明 FAP的入网方法的技术方案。 本实施例 在完成 FAP的重定向处理后,对 FAP进行认证和授权处理。如图 7所示,本实施例包括: 步骤 71-步骤 73与图 3所示实施例中步骤 31-步骤 33相同, 其中, 步骤 71-步骤
73中的 H-SeGW对应图 3所示实施例中的 SeGW。
步骤 74、 FAP AAA服务器选择 FAP重定向的 V_SeGW, 即 FAP AAA服务器选择 FAP 重定向的入口。
本步骤中, FAP AAA服务器可根据 FAP的标识信息和位置信息查询 FAP AAA服务器 上维护的 ASN列表, 当 FAP AAA服务器根据查询结果获知, FAP的 H-ASN与 V-ASN不同 时, 确定将 FAP重定向到 FAP当前所在位置区对应的 V-ASN的 V_SeGW上。 FAP AAA服务 器向 H-SeGW发送 SeGW重定向消息,该 SeGW重定向消息中携带有: V-SeGW的地址信息。
步骤 75、 FAP AAA服务器通过 H-SeGW向 FAP发送 SeGW重定向消息, 该 SeGW重定 向消息中携带有 V-SeGW的地址信息, 用于通知 FAP与 V-SeGW建立连接, 即将 V-SeGW 作为 FAP接入 V-ASN的入口。
步骤 76、 FAP向 V-SeGW发送重定向接入请求, 该重定向接入请求中可携带有 FAP 的标识信息, 用于请求通过 V-SeGW入网。
重定向接入请求中除了携带有 FAP的标识信息之外,还可携带有 FAP的其它信息, 如: FAP的位置参数等。
步骤 77、 FAP AAA服务器通过 V-SeGW对 FAP进行认证和授权处理。
在 FAP通过认证和授权处理后, 执行步骤 78。
步骤 78-步骤 716与图 3所示实施例中步骤 35-步骤 313相同, 其中, 步骤 78-步 骤 716中的 V-SeGW对应图 3所示实施例中的 SeGW。
本实施例在 FAP的 H-ASN与 V-ASN不同时, 将 FAP重定向到 FAP当前所在位置区 对应的 V-ASN的 V-SeGW上, 并在对 FAP认证授权之后, 根据 FAP上下文为 FAP确定需 要接入的接入服务网的 V-ASN-GW, 并分别为 FAP和 V-ASN-GW生成 FAP通过 V-ASN-GW 入网所需的配置参数, 实现了 FAP根据网络侧下发的配置参数在拜访地接入 ASN网络, 从而有利于 FAP为终端提供有效的接入服务。
图 8为本发明第九实施例提供的 FAP的入网方法信令交互图。 本实施例是以图 6 所示的应用场景为例说明 FAP重定向入网过程;在实现 FAP重定向入网过程中利用的图 2所示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 4、 5和 6。 本实施例与 图 7对应实施例的区别在于, 本实施例在完成认证和授权处理之后, 对 FAP进行重定向 处理。 如图 8所示, 本实施例包括: 步骤 81和步骤 82与图 7所示实施例中步骤 71和步骤 72相同。
步骤 83、 FAP AAA服务器通过 H-SeGW对 FAP进行认证授权处理。
步骤 84、 FAP AAA服务器选择 FAP重定向的 V_SeGW, 即 FAP AAA服务器选择 FAP 重定向的入口。 本步骤与图 7所示实施例中步骤 74相同。
本实施例中的 FAP定位过程(图 8未示出)可发生在步骤 71-步骤 74中任一步骤 .、, -
Z刖。
步骤 85、 FAP AAA服务器通过 H-SeGW向 FAP发送 SeGW重定向消息, 该 SeGW重定 向消息中携带有 V-SeGW地址信息, 用于通知 FAP与 V-SeGW建立连接, 即将 V_SeGW作 为 FAP接入 V-ASN的入口。此外, SeGW重定向消息中还可携带有 FAP认证标识, 用于通 知 FAP已经完成合法性的认证。
步骤 86、 FAP向 V-SeGW发送重定向接入请求, 在该重定向接入请求中携带有 FAP 的标识信息, 用于请求通过 V-SeGW入网。 此外, 该重定向接入请求中还可携带有 FAP 认证标识、 位置信息和其它参数。
步骤 87、 V-SeGW向 V-SeGW所在网络的 FAP配置中心(即: V-FAP)发送网络资源 配置请求, 用于请求为 FAP分配网络资源及配置入网参数; 其中, 网络资源配置请求中 包括 FAP标识信息, 还可包括 FAP认证标识。
步骤 88、 FAP配置中心向 FAP AAA服务器发送 FAP参数请求, 用于请求获取 FAP 的上下文; FAP参数请求中携带有 FAP的标识信息。
步骤 89、 FAP AAA服务器根据 FAP标识信息, 查询保存的 FAP签约档案, 获取与 FAP标识信息相应的 FAP上下文以及通道建立参数; 其中, FAP上下文可包括 FAP的位 置信息(Location)。 FAP的上下文还可包括 FAP的标识信息, 进一步的, FAP的上下文 还可包括: FAP的认证状态信息、 FAP的服务质量(Qual ity of Service, 简称 QoS ) 和 FAP的闭合用户群(Closed Subscriber Group, 简称 CSG)等参数; 通道建立参数用 于 V-SeGW建立与 FAP在有线宽带网络中的专用通道, 包括利用在认证和授权过程中生 成的密钥等信息保证通信安全的功能。
步骤 810和步骤 811与图 7对应实施例中步骤 712和步骤 713相同。
步骤 812、 V-FAP配置中心向 V-SeGW发送为 FAP生成的配置参数, 该配置参数可 包括: FAP ID、 FAP的 PG、 ASN-GW Info和 FAP可使用的空口参数, 以及通道建立参数 等信息。 V-FAP配置中心为 FAP生成的配置参数还可进一步包括: FAP的 QoS、 FAP的 CSG 等参数。 步骤 813、 V-SeGW根据获取的通道建立参数与 FAP建立通道。
步骤 814和步骤 815与图 7对应实施例中步骤 715和步骤 716相同。
本实施例在对 FAP认证和授权处理之后, 对 FAP进行重定向, 将 FAP从 H_SeGW重 定向到 V-SeGW上, 根据 FAP上下文为 FAP确定需要 V-ASN的 V-ASN-GW, 并为 FAP生成 通过 V-ASN-GW入网所需的配置参数, 实现了 FAP根据网络侧下发的配置参数在拜访地 接入 ASN网络, 从而有利于 FAP为终端提供有效的接入服务。
图 9为本发明第十实施例提供的 FAP的入网方法信令交互图。 本实施例是以图 6 所示的应用场景为例说明 FAP重定向入网过程;在实现 FAP重定向入网过程中利用的图
2所示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 4、 5、 6和 7。 本实施例 与图 7对应实施例的区别在于, 本实施例在对 FAP的合法性进行认证之前, 为 FAP分配 了一个参与 FAP认证的认证 V-ASN-GW。 如图 9所示, 本实施例包括:
步骤 91-步骤 94与图 7所示实施例中步骤 71-步骤 74相同。
步骤 95、 FAP AAA服务器通过 H-SeGW向 FAP发送 SeGW重定向消息, 该 SeGW重定 向消息中携带有 FAP当前所在位置区对应的 V-SeGW的地址信息,用于通知 FAP与 V-SeGW 建立连接, 即将 V-SeGW作为 FAP接入 V-ASN的入口。 此外, SeGW重定向消息中还携带 有 ASN-GW接入标识, 该 ASN-GW接入标识用于通知 FAP在 FAP的认证流程中需要认证
ASN-GW的参与, FAP在认证前需要与参与认证的认证 ASN-GW建立连接。
步骤 96、 FAP向 V-SeGW发送重定向接入请求, 在该重定向接入请求中携带有 FAP 的标识信息。
步骤 97、 V-SeGW向 FAP配置中心发送 ASN-GW信息请求(即: ASN-GW Info请求), 用于请求 FAP配置中心为选择一个认证 ASN-GW参与 FAP认证,该 ASN-GW信息请求中携 带有 FAP的位置信息 (Locat ion)。
V-SeGW根据 ASN-GW接入标识, 确定需要向 V-FAP配置中心发送 ASN-GW信息请求 (即: ASN-GW Info请求), 用于请求 FAP配置中心为选择一个认证 ASN-GW参与 FAP认 证, 该 ASN-GW信息请求中携带有 FAP的位置信息 (Locat ion)。
步骤 98、 FAP配置中心为 FAP选择一个参与 FAP认证的认证 V_ASN_GW。
FAP配置中心为 FAP选择参与 FAP认证的认证 V-ASN-GW的实现方式上,可根据 FAP 位置信息, 将 FAP所在地的 V-ASN-GW确定为参与 FAP认证的认证 ASN-GW, 该情形下, 本实施例步骤 915中不需要为 FAP重新确定 FAP需要接入的接入服务网的 V-ASN-GW,即: FAP需要接入的接入服务网的 V-ASN-GW与参与 FAP认证的认证 ASN-GW相同。 图 9仅示 出了 FAP需要接入的接入服务网的 V-ASN-GW与参与 FAP认证的认证 ASN-GW相同的情形。 此外, FAP配置中心根据宏网络现状选择一个认证 ASN-GW, 该情形下, 如果参与 FAP认证的认证 ASN-GW与 FAP所在地的 V-ASN-GW不同时,本实施例还需要通过步骤 915 为 FAP确定需要接入的接入服务网的 V-ASN-GW。
步骤 99与图 4对应实施例中的步骤 47相同,其中,在步骤 98和步骤 99中的 V_SeGW 和 V-FAP配置中心分别对应图 4所示实施例中的 SeGW和 FAP配置中心。
步骤 910-步骤 919与图 7对应实施例中的步骤 77-步骤 716。
本实施例在对完成 FAP重定向后, 为 FAP确定一个可参与到 FAP的认证和鉴权处 理的认证 ASN-GW, FAP AAA服务器通过该认证 ASN-GW和 SeGW对 FAP进行认证和鉴权处 理, 在对 FAP进行有效的认证和授权处理后, 为 FAP确定接入 ASN-GW以及配置参数, 为 FAP接入 ASN网络提供有效的支持, 从而满足 FAP的应用需求。
图 10为本发明第十一实施例提供的 FAP漫游入网重定向的应用场景示意图。在图 10所示的应用场景中, FAP签约的家乡地 CSN (H-CSN)和 FAP当前所在的拜访地 CSN (V-CSN)签署了 FAP漫游协议; ASN1与 H-CSN之间存在签约关系, ASN2与 V-CSN之间 存在签约关系。 保存有 FAP签约档案(包括有 FAP的上下文) 的 FAP AAA服务器部署在 H-CSN中; V-CSN中也部署由拜访地 FAP AAA服务器( V-FAP AAA服务器), 漫游场景中, V-FAP AAA服务器会参与认证过程, H-FAP AAA服务器在认证过程把必要的 FAP上下文 发给 V-FAP AAA服务器。
假设: V-CSN为 H-CSN提供了一个漫游重定向的入口, 即漫游重定向接入网关 V-SeGWl ,这样, 如果 FAP需要接入到与 V-CSN具有签约关系的 ASN中, 则先由 V_SeGWl 接入, 之后再根据 FAP当前所在的位置区进行 FAP重定向的优化处理, 以便为 FAP提供 可接入 ASN网络的 SeGW。
FAP AAA服务器上维护有 ASN列表和 CSN列表; ASN列表中有与 H-CSN签约的所有 ASN、 ASN与 SeGW之间的映射关系、 SeGW对应的位置区间, 用于判断场景类型(本地接 入、 漫游接入等); 如果 FAP的位置信息与 ASN列表中的位置区间不匹配, 那么判断为 漫游场景, 将 FAP位置信息与 CSN列表中的地址区间匹配, 以确定 FAP位于哪个 V-CSN 的覆盖区域。 CSN列表中有漫游协议拜访地 V-CSN与漫游接入 SeGW的映射关系以及漫游 接入 SeGW对应的地址区间, 列表中每一个 CSN至少有一个 SeGW信息与之对应。
如图 10所示, FAP漫游重定向流程可包括:
步骤 101、 FAP向自身默认的 H-SeGW发送入网请求, 该入网请求中携带有 FAP标 识和位置信息等。
步骤 102、 H-SeGW向部署在 H-FAP AAA服务器转发入网请求, 该入网请求中携带 有 FAP标识和位置信息。
步骤 103、 H-FAP AAA服务器根据 FAP标识和位置信息, 查询 H-FAP AAA服务器上 维护的 ASN列表和 CSN列表。 当 H-FAP AAA服务器根据查询结果获知, FAP当前所在地 所属的 V-ASN不在与 FAP具有签约关系的 H-CSN覆盖的区域内, 而在与 H-CSN具有 FAP 漫游协议的 V-CSN区域内时, FAP AAA服务器向 H-SeGW发送漫游重定向消息, 在该漫游 重定向消息中携带有 V-SeGWl信息 (如: V-SeGWl的地址信息等)。
步骤 104、H-SeGW向 FAP转发漫游重定向消息,该漫游重定向消息中携带有 V-SeGWl 的地址信息。
这里需要说明的是, SeGW部署在 ASN中的,而在图 10所示的漫游场景中 ASN要么 和 H-CSN签约, 要么和 V-CSN签约, 不能直接与没有签约关系的 CSN交互。 ASN与没有 签约关系的 CSN之间的交互是根据漫游协议实现的: V-CSN事先为 H-CSN提供了 V-SeGWl 作为从 H-CSN漫游过来的 FAP的漫游重定向入口。这个 V-SeGWl由 V-CSN签约下的某个 ASN提供。 漫游重定向的入口可以动态维护, 不一定只是 V-SeGWl, 也不一定只有一个。 反之, H-CSN也会为 V-CSN提供漫游入口。
步骤 105、 FAP向 V-SeGWl发起漫游重定向流程。
FAP在完成从 H-SeGW重定向到 V-CSN覆盖范围下的 V-SeGWl之后,可采用图 6_图 9对应实施例的实现方法, 通过 V-SeGWl实现的 V-ASN的入网流程。
此外,在图 10所示的应用场景中, V-SeGWl可以属于 ASN2也可以属于 V-CSN签约 下的其它 ASN。 如果 V-SeGWl已经满足 FAP漫游接入的要求, 则不需要发起第二次重定 向的过程,即可触发 FAP配置中心配置网络资源的过程;如果 V-SeGWl不是 FAP接入 ASN 最优的 SeGW, 还可通过步骤 106-步骤 108发起 SeGW重定向流程; 如果 V-SeGWl所属的 ASN没有覆盖到 FAP所在的区域, 则需发起第二次重定向的过程。
步骤 106、 V-SeGWl将 FAP的漫游重定向请求转发给 V-FAP AAA服务器,。
步骤 107、 V-FAP AAA服务器根据 FAP的标识信息, 发起 SeGW重定向流程, 为 FAP 确定接入 V-ASN网络的 V-SeGW2。
步骤 108、FAP通过 V-SeGW2发起建立与 FAP当前位置区所在的 V-ASN的接入流程。 本实施例当 FAP当前所在位置区所属的 V-ASN, 不在 FAP的 H-CSN覆盖区域、 且 H-CSN与 V-CSN具有 FAP漫游协议、 V-ASN与所述 V-CSN具有签约关系时, 可通过漫游 重定向流程为 FAP确定接入 V-ASN的 V-SeGW, 有利于保证 FAP入网的成功率。
图 11为本发明第十二实施例提供的 FAP的入网方法信令交互图。本实施例是以图 10所示的应用场景为例说明 FAP漫游重定向入网过程;在实现 FAP重定向入网过程中利 用的图 2所示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 4、 5和 6。 本实 施例与图 7对应实施例的区别在于, 本实施例包括二次重定向过程。 如图 11所示, 本 实施例包括:
步骤 1101-步骤 1103与图 6所示实施例中步骤 71-步骤 73相同,其中,步骤 1101- 步骤 1103中的 H-FAP AAA服务器与图 7对应实施例的 FAP AAA服务器。
步骤 1104、 H-FAP AAA服务器选择 FAP重定向的 V_SeGW, 即 H-FAP AAA服务器选 择 FAP重定向的入口。
H-FAP AAA服务器根据 FAP的标识信息,查询 H-FAP AAA服务器上维护的 CSN列表, 当 H-FAP AAA服务器根据查询结果获知, FAP位于存在漫游签约协议的拜访地 V-CSN, H-FAP AAA服务器向 H-SeGW发送漫游重定向消息,在该漫游重定向消息中携带有预先设 置的漫游接入安全网关 (V-SeGWl ) 的地址信息。
有关漫游重定向入口的选择详见图 10对应实施例中步骤 104的记载, 不再赘述。 步骤 1105、 H-FAP AAA服务器向 FAP发送漫游重定向消息, 该漫游重定向消息中 携带有 V-SeGWl的地址信息。
步骤 1106、 FAP向 V-SeGWl发送 FAP漫游重定向请求, 在该漫游重定向请求中携 带有 FAP设备标识以及 FAP的位置信息。
步骤 1107、 V-SeGWl向 V-FAP AAA服务器发送 FAP漫游重定向请求, 在该 FAP漫 游重定向请求中携带有 FAP标识和位置信息。
步骤 1108、 假设 V-FAP AAA服务器为 FAP确定接入 V-ASN最合适的接入 SeGW为 V- SeGW2。
步骤 1109、 V-FAP AAA服务器向 FAP发送 SeGW重定向消息, 该 SeGW重定向消息 中携带有 V-SeGW2的地址信息, 用于通知 FAP与 V_SeGW2建立连接。
步骤 1110、 FAP向 V-SeGW2发送重定向接入请求, 在该重定向接入请求中携带有 FAP的标识信息, 用于请求通过 V-SeGW2入网。
步骤 1111、 H-FAP AAA服务器通过 V-FAP AAA服务器、 V_SeGW2对 FAP认证和授权 处理。
步骤 1112-步骤 1120与图 7对应实施例中步骤 78-步骤 716相同, 其中, 本实施 例步骤 1112-步骤 1120中的 V-SeGW2对应图 7对应实施例中的 V_SeGW。
本实施例当 FAP当前所在位置区所属的 V-ASN, 不在 H-CSN的覆盖区域、 且 H-CSN 与 V-CSN签署有 FAP漫游协议、 V-ASN与所述 V-CSN具有签约关系时, 可通过两次或多 次重定向过程, 以使 FAP准确定向到 V-FAP AAA服务器提供的合适的 V-SeGW上, 有利 于保证 FAP入网的成功率。
图 12为本发明第十三实施例提供的 FAP的入网方法信令交互图。本实施例是以图 10所示的应用场景为例说明 FAP漫游重定向入网过程;在实现 FAP重定向入网过程中利 用的图 2所示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 4、 5、 6和 7。 本 实施例与图 11对应实施例的区别在于, 本实施例在漫游重定向之前分配由 V-FAP AAA 服务器分配一个参与到 FAP认证过程中的认证 ASN-GW。 如图 12所示, 本实施例包括: 步骤 1201-步骤 1204与图 11对应实施例中步骤 1101-步骤 1104相同。
步骤 1205、 H-FAP AAA服务器向 FAP发送漫游重定向消息, 该漫游重定向消息中 包括 V-SeGWl信息和 ASN-GW接入标识,用于通知 FAP的认证过程需要认证 ASN-GW参与。
步骤 1206、 FAP向 V-SeGWl发送 FAP漫游重定向请求, 该 FAP漫游重定向请求中 包括 FAP的标识信息、 位置信息和 ASN-GW接入标识。
步骤 1207、 V-SeGWl向 V-FAP AAA服务器转发 FAP漫游重定向请求。
步骤 1208、 V -FAP AAA服务器选择 FAP重定向的接入 V_SeGW2, 即 V -FAP AAA 服务器选择 FAP重定向的入口。
步骤 1209、 V-FAP AAA服务器向 V-SeGWl发送 SeGW重定向消息, 该 SeGW重定向 消息中携带有 V-SeGW2信息。
步骤 1210、 FAP向 V-SeGW2发送 SeGW重定向请求, 该 SeGW重定向请求中携带有 FAP的标识信息、 位置信息和 ASN-GW接入标识。
步骤 1211、 V-SeGW2向 V-ASN的 V-FAP配置中心发送 ASN-GW信息请求消息, 用于 请求 V-FAP配置中心为 FAP分配认证 ASN-GW; 该 ASN-GW信息请求消息中携带有 FAP的 标识信息、 位置信息和 ASN-GW接入标识。
步骤 1212、 V-FAP配置中心为 FAP选择一个参与 FAP认证的认证 ASN_GW。
步骤 1213、 V-FAP配置中心向 V-SeGW2发送 ASN-GW信息响应, ASN-GW信息响应中 携带有认证 ASN-GW的信息。
步骤 1214、 H-FAP AAA服务器、 V-FAP AAA服务器、 认证 ASN-GW以及 V-SeGW对 FAP进行认证和授权处理。 步骤 1215-1223与图 11对应实施例中步骤 1112-步骤 1120相同。
本实施例在 FAP漫游重定向过程中, 为 FAP确定一个可参与到 FAP的认证和鉴权 处理的认证 ASN-GW, 使该认证 ASN-GW参与到 FAP的认证处理流程, 在对 FAP进行有效 的认证和授权处理后, 为 FAP确定接入 V-ASN的接入 ASN-GW以及配置参数, 为 FAP接 入 ASN网络提供有效的支持, 从而满足 FAP的应用需求。
图 13为本发明第十四实施例提供的 FAP的入网方法信令交互图。本实施例是以图 10所示的应用场景为例说明 FAP漫游重定向入网过程;在实现 FAP重定向入网过程中利 用的图 2所示的网络架构中的各节点之间的接口包括: 接口 1、 2、 3、 4、 5和 6。 本实 施例与图 11对应实施例的区别在于, 本实施例在漫游重定向之前进行 FAP的认证和授 权流程。 如图 13所示, 本实施例包括:
步骤 1301-步骤 1303与图 11对应实施例中步骤 1101-步骤 1103相同。
步骤 1304、 H-FAP AAA服务器、 H_SeGW对 FAP进行认证和授权处理。
步骤 1305、 H-FAP AAA服务器选择 FAP重定向的 V-SeGW, 即 FAP AAA服务器选择 FAP重定向的入口。
步骤 1306、 H-FAP AAA服务器向 FAP发送漫游重定向消息, 该漫游重定向消息中 携带有 V-SeGWl的地址信息以及 FAP认证标识,其中 FAP认证标识用于表示 FAP已通过 合法性认证。
步骤 1307、 FAP向 V-SeGWl发送 FAP漫游重定向请求, 在该漫游重定向请求中携 带有 FAP设备标识、 FAP的位置信息以及 FAP认证标识。
步骤 1308、 V-SeGWl向 V-FAP AAA服务器发送 FAP漫游重定向请求, 在该 FAP漫 游重定向请求中携带有 FAP标识、 FAP的位置信息以及 FAP认证标识。
步骤 1309、V-FAP AAA服务器为 FAP确定接入 V-ASN最合适的接入 SeGW为 V_SeGW2。 步骤 1310、 V-FAP AAA服务器向 FAP发送 SeGW重定向消息, 该 SeGW重定向消息 中携带有 V-SeGW2的信息和 FAP认证标识。
步骤 1311、 FAP向 V_SeGW2发送重定向接入请求, 在该重定向接入请求中携带有
FAP的标识信息、 位置信息和 FAP认证标识。
步骤 1312、 V-SeGW2向 V-FAP的 FAP配置中心 (gp : V-FAP )发送网络资源配置请 求, 该网络资源配置请求中包括 FAP的标识信息以及 FAP认证标识。
步骤 1313、 V-FAP AAA服务器根据 FAP标识信息, 查询保存的 FAP签约档案, 获 取与 FAP标识信息相应的上下文以及通道建立参数;通道建立参数用于 V-SeGW2建立与 FAP在有线宽带网络中的通道。
步骤 1314-步骤 1317分别与图 11对应实施例中步骤 1115-步骤 1118相同。
步骤 1318、 V-SeGW根据获取的通道建立参数与 FAP建立通道。
步骤 1319和步骤 1320与图 11对应实施例中步骤 1119和步骤 1120相同。
本实施例在对 FAP认证和授权处理之后, 通过 FAP漫游重定向过程中, 为 FAP确 定接入 V-ASN的接入 ASN-GW以及配置参数,从而为 FAP接入 ASN网络提供有效的支持, 从而满足 FAP的应用需求。
此外, 图 5对应的实施例中记载的配置参数下发的方法, 也可应用到图 6所示的 重定向场景中, 还可应用到图 10所示的漫游场景, 不再赘述。
图 14为本发明第十五实施例提供的 FAP接入点的入网系统的结构示意图。如图 14 所示, FAP的入网系统中, 包括: FAP、一类安全网关(SeGWl ) (即本发明实施例的第一 安全网关)、二类安全网关(SeGW2 ) (即本发明实施例的第二安全网关)、配置中心、 FAP AAA服务器和 ASN-GW。
SeGWl和 SeGW2均位于有线网络与 WiMAX宏网络之间, 实现网关功能和安全功能。 SeGWl用于 FAP的第一次定向, 为 FAP提供从有线网络到 CSN (如: 部署在 CSN中的 FAP AAA服务器)的连接; SeGW2用于 FAP的第二次定向, 为 FAP提供接入 ASN-GW的连接。 每一个签约的 FAP都配置了一个一类安全网关 SeGWl的地址,用于默认的入网连接。 FAP 只会通过 SeGWl与 FAP AAA服务器交互, 与 FAP配置中心和 ASN-GW只会通过 SeGW2交 互,最终通过 SeGW2接入与 H-CSN具有签约关系的 ASN网络,或者, 接入与 FAP的 H-CSN 签署了漫游协议的 V-CSN具有签约关系的 V-ASN网络。
在图 14所示的系统架构下, FAP在不同应用场景中的入网流程都需要 FAP的重定 向过程, 即将 FAP从 SeGWl定向到 SeGW2, 其中, 实现 FAP接入 ASN的入网方法与图 3_ 图 13所示实施例记载的技术方案相似, 在功能实现上, 图 12中的 SeGWl对应图 3_图 13所示实施例中的 H-SeGW,图 14中的 SeGW2对应图 3_图 13所示实施例中的 V-SeGW (包 括: V-SeGWl和 V-SeGW2 ); 不再赘述。
图 15为本发明第十六实施例提供的 FAP的入网装置结构示意图。 如图 15所示, 本实施例 FAP的入网装置包括: 入网请求接收模块 151、 上下文获取模块 152和上下文 发送模块 153。
入网请求接收模块 151用于接收毫微级接入点 FAP的入网请求。所述入网请求可包 括所述 FAP的标识信息。 上下文获取模块 152用于根据所述入网请求获取所述 FAP的上下文。
上下文发送模块 153用于向所述 FAP需要接入的接入服务网 ASN发送所述上下文, 以供所述 ASN根据所述上下文和所述 ASN当前网络配置为所述 FAP生成入网所需的配置 参数并向所述 FAP发送。
其中, 所述 FAP的上下文可包括: FAP的位置信息。 所述 FAP的上下文还可进一步 包括: FAP的标识信息、 FAP的服务质量信息和闭合用户群信息等。 接入服务网为 FAP 生成的配置参数可包括:为所述 FAP确定的所述 FAP入网连接的接入服务网网关 ASN-GW 信息、 FAP的全球唯一标识、 空口参数和寻呼组信息等。
在上述技术方案的基础上, FAP的入网装置还可包括: 接入网络选取模块 154。 接入网络选取模块 154用于根据所述 FAP的位置信息,为所述 FAP选择拜访地 ASN。 进一步的, FAP的入网装置还可包括:重定向入口确定模块 155和重定向通知模块
156。
重定向入口确定模块 155用于比较所述拜访地 ASN与所述 FAP的家乡地 ASN是否相 同, 如果不同, 为所述 FAP确定接入所述拜访地 ASN的拜访地安全网关。
重定向通知模块 156用于向所述 FAP发送所述拜访地安全网关信息,用于通知所述 FAP与所述拜访地安全网关建立重定向连接。
本实施例 FAP的入网装置在具体表现功能实体上可以是 FAP AAA服务器。关于 FAP AAA服务器的详细说明以及 FAP AAA服务器在进行 FAP入网控制时和其他节点之间的交 互, 可参见图 3-图 14对应实施例的记载, 不再赘述。
本实施例 FAP的入网装置可根据 FAP的入网请求, 向 FAP需要接入的 ASN发送上 下文, 有利于 ASN为 FAP分配网络资源和配置参数, 从而为 FAP接入 ASN提供支持, 满 足 FAP的应用需求。
图 16为本发明第十七实施例提供的 FAP的入网装置结构示意图。 如图 16所示, 本实施例包括: 上下文接收模块 161、配置参数生成模块 162和配置参数发送模块 163。
上下文接收模块 161用于接收鉴权授权服务器根据 FAP入网请求发送的所述 FAP的 上下文。
配置参数生成模块 162用于根据所述上下文和接入服务网的当前网络配置,为所述 FAP生成入网所需的配置参数。
配置参数发送模块 163用于向所述 FAP发送所述配置参数。
本实施例 FAP的入网装置在具体表现功能实体上可以是 ASN的 FAP配置中心。 关 于 FAP配置中心的详细说明以及 FAP配置中心在进行 FAP入网控制时和其他节点之间的 交互, 可参见图 3-图 14对应实施例的记载, 不再赘述。
本实施例 FAP的入网装置可根据 FAP的上下文以及 ASN当前网络配置, 为 FAP接 入 ASN进行相应配置, 从而为 FAP接入 ASN提供支持, 满足 FAP的应用需求。在 FAP成 功接入到 ASN时, FAP即可作为 ASN中的一个网元接入到宏网络, 从而有利于为终端提 供有效的接入服务, 满足 FAP的应用需求。
图 17为本发明第十八实施例提供的 FAP的入网系统结构示意图。如图 17所示, 本 实施例包括: 安全网关(SeGW) 172、 第一入网装置 173和第二入网装置 174。
安全网关 172用于建立毫微级接入点 171与第一入网装置 173和第二入网装置 174 的连接。
第一入网装置 173用于通过安全网关 172接收 FAP的入网请求;获取与所述 FAP的 标识信息相应的 FAP上下文; 向所述 FAP需要接入的接入服务网 (ASN)发送所述 FAP 上下文。 所述入网请求可包括 FAP的标识信息。
第二入网装置 174用于接收所述第一入网装置 173根据 FAP入网请求发送的所述 FAP的上下文; 根据所述 FAP上下文和 ASN当前网络配置, 为所述 FAP生成入网所需的 配置参数; 通过所述安全网关 172向所述 FAP发送所述配置参数。
本实施例第一入网装置 173的细化功能结构可参见图 15对应实施例的记载,其中, 第一入网装置在具体表现功能实体上可以是 FAP AAA服务器。 关于 FAP AAA服务器的详 细说明以及 FAP AAA服务器在进行 FAP入网控制时的组网结构, 可参见图 3_图 14对应 实施例的记载, 不再赘述。
本实施例第二入网装置 174的细化功能结构可参见图 16对应实施例的记载,其中, 第二入网装置在具体表现功能实体上可以是 ASN的 FAP配置中心。关于 FAP配置中心的 详细说明以及 FAP配置中心在进行 FAP入网控制时和其他节点之间的交互,可参见图 3- 图 14对应实施例的记载, 不再赘述。
本实施例通过安全网关, 建立部署在有线网络中的 FAP与部署在宏网络中的第一 入网装置和第二入网装置之间的连接, 由第一入网装置根据 FAP的入网请求, 向第二入 网装置发送 FAP的上下文, 并由 第二入网装置根据 FAP的上下文以及 FAP需要接入的 ASN当前网络配置生成配置参数,从而为 FAP接入 ASN提供支持,满足 FAP的应用需求。
图 18为本发明第十九实施例提供的 FAP的入网系统结构示意图。如图 18所示, 本 实施例包括: 第一安全网关(SeGWl ) 182、 第二安全网关 183、 第一入网装置 184和第 二入网装置 185。
第一安全网关 182用于建立毫微级接入点 181与第一入网装置 184的连接。
第二安全网关 183用于建立毫微级接入点 181与第二入网装置 185的连接。
第一入网装置 184用于通过第一安全网关 182接收 FAP的入网请求;根据所述入网 请求获取所述 FAP的上下文; 向所述 FAP需要接入的接入服务网 (ASN)发送所述上下 文。 所述入网请求可包括 FAP的标识信息。
第二入网装置 185用于接收所述第一入网装置 184根据 FAP入网请求发送的所述
FAP的上下文; 根据所述上下文和 ASN当前网络配置, 为所述 FAP生成入网所需的配置 参数; 通过所述第二安全网关 183向所述 FAP发送所述配置参数。
上述技术方案中, 第一安全网关可对应图 6-图 13对应实施例中的 V-SeGW (包括:
V-SeGWl或 V-SeGW2 );本实施例第二安全网关可对应图 6-图 13对应实施例中的 H_SeGW, 不再赘述。
第一入网装置 184的细化功能结构可参见图 15对应实施例的记载, 其中, 第一入 网装置在具体表现功能实体上可以是 FAP AAA服务器。 关于 FAP AAA服务器的详细说明 以及 FAP AAA服务器在进行 FAP入网控制时的组网结构, 可参见图 3_图 14对应实施例 的记载, 不再赘述。
第二入网装置 185的细化功能结构可参见图 16对应实施例的记载, 其中, 第二入 网装置在具体表现功能实体上可以是 ASN的 FAP配置中心。关于 FAP配置中心的详细说 明以及 FAP配置中心在进行 FAP入网控制时和其他节点之间的交互, 可参见图 3-图 14 对应实施例的记载, 不再赘述。
本实施例通过第一安全网关建立部署在有线网络中的 FAP与部署在宏网络中的第 一入网装置之间的连接,通过第二安全网关建立 FAP与部署在宏网络中的第二入网装置 之间的连接, 从而为 FAP接入 ASN提供支持, 满足 FAP的应用需求。
本领域普通技术人员可以理解: 附图只是一个优选实施例的示意图, 附图中的模 块或流程并不一定是实施本发明所必须的。
本领域普通技术人员可以理解:实施例中的装置中的模块可以按照实施例描述分布 于实施例的装置中, 也可以进行相应变化位于不同于本实施例的一个或多个装置中。上 述实施例的模块可以合并为一个模块, 也可以进一步拆分成多个子模块。
上述本发明实施例序号仅仅为了描述, 不代表实施例的优劣。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤可以通过 程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读取存储介质中, 该程 序在执行时, 执行包括上述方法实施例的步骤; 而前述的存储介质包括: R0M、 RAM, 磁 碟或者光盘等各种可以存储程序代码的介质。 最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其限制; 尽管 参照前述实施例对本发明进行了详细的说明, 本领域的普通技术人员应当理解: 其依然 可以对前述实施例所记载的技术方案进行修改, 或者对其中部分技术特征进行等同替 换; 而这些修改或者替换, 并不使相应技术方案的本质脱离本发明实施例技术方案的精 神和范围。

Claims

权利要求
1、 一种毫微级接入点的入网方法, 其特征在于, 包括:
接收毫微级接入点 FAP的入网请求;
根据所述入网请求, 获取所述 FAP的上下文;
向所述 FAP需要接入的接入服务网 ASN发送所述上下文, 以供所述 ASN根据所述上 下文和所述 ASN当前网络配置为所述 FAP生成入网所需的配置参数并向所述 FAP发送。
2、 根据权利要求 1所述的毫微级接入点的入网方法, 其特征在于, 所述入网请求 包括所述 FAP的标识信息; 发送的所述上下文中包括所述 FAP的标识信息。
3、 根据权利要求 1所述的毫微级接入点的入网方法, 其特征在于, 向所述 FAP需 要接入的 ASN发送所述上下文, 包括:
通过安全网关向所述 FAP需要接入的 ASN发送所述上下文。
4、 根据权利要求 1所述的毫微级接入点的入网方法, 其特征在于,
获取的所述 FAP的上下文包括: FAP的位置信息。
5、 根据权利要求 1或 4所述的毫微级接入点的入网方法, 其特征在于, 所述 ASN 根据所述上下文和所述 ASN当前网络配置为所述 FAP生成入网所需的配置参数, 包括: 所述 ASN的配置中心根据所述上下文以及所述 ASN的当前网络配置,为所述 FAP生 成入网所需的配置参数, 所述配置参数包括: 为所述 FAP确定的所述 FAP入网连接的接 入服务网网关 ASN-GW信息、 FAP的全球唯一标识、 空口参数和寻呼组信息。
6、 根据权利要求 5所述的毫微级接入点的入网方法, 其特征在于, 所述 ASN向所 述 FAP发送所述配置参数, 包括:
所述 ASN通过安全网关向所述 FAP发送所述配置参数。
7、 根据权利要求 6所述的毫微级接入点的入网方法, 其特征在于, 所述 ASN通过 安全网关向所述 FAP发送所述配置参数, 包括:
所述 ASN向所述安全网关发送 ASN-GW信息、 FAP的全球唯一标识、空口参数和寻呼 组信息;
所述安全网关向所述 FAP发送 FAP的全球唯一标识、空口参数和寻呼组信息,或者, 所述安全网关向所述 FAP发送 ASN-GW信息、 FAP的全球唯一标识、空口参数和寻呼组信 息。
8、 根据权利要求 5所述的毫微级接入点的入网方法, 其特征在于, 在所述 ASN为 所述 FAP生成入网所需的配置参数之后, 还包括: 向所述 ASN-GW发送 FAP的全球唯一标识、 所述 FAP的位置信息和所述空口参数。
9、根据权利要求 4所述的毫微级接入点的入网方法, 其特征在于, 所述 ASN包括: 所述 FAP请求接入的家乡地 ASN; 或者
根据所述 FAP的位置信息, 为所述 FAP选择的拜访地 ASN。
10、根据权利要求 9所述的毫微级接入点的入网方法, 其特征在于, 所述 ASN包括 所述 FAP选择的拜访地 ASN, 在向所述 ASN发送所述上下文之前, 还包括:
比较所述拜访地 ASN与所述 FAP 的家乡地 ASN是否相同, 如果不同, 为所述 FAP 确定接入所述拜访地 ASN的拜访地安全网关;
向所述 FAP发送所述拜访地安全网关信息,用于通知所述 FAP与所述拜访地安全网 关建立重定向连接。
11、 根据权利要求 10所述的毫微级接入点的入网方法, 其特征在于, 在所述 FAP 接收到拜访地安全网关信息之后, 还包括:
所述 FAP向所述拜访地安全网关发送重定向请求,所述重定向请求包括所述 FAP的 标识信息;
所述拜访地安全网关向所述拜访地 ASN的 FAP配置中心发送网络资源配置请求,所 述网络资源配置请求包括所述 FAP的标识信息;
所述拜访地 ASN的 FAP配置中心请求获取与所述标识信息相应的所述 FAP的上下文。
12、 一种毫微级接入点的入网方法, 其特征在于, 包括:
接收鉴权授权服务器根据 FAP入网请求发送的所述 FAP的上下文;
根据所述上下文和接入服务网当前网络配置,为所述 FAP生成入网所需的配置参数; 向所述 FAP发送所述配置参数。
13、 根据权利要求 12所述的毫微级接入点的入网方法, 其特征在于, 所述接收鉴 权授权服务器根据 FAP入网请求发送的所述 FAP的上下文, 包括:
鉴权授权服务向安全网关发送所述 FAP的上下文;
接收所述安全网关发送的所述 FAP的上下文。
14、 一种毫微级接入点的入网装置, 其特征在于, 包括:
入网请求接收模块, 用于接收毫微级接入点 FAP的入网请求;
上下文获取模块, 用于根据所述入网请求, 获取所述 FAP的上下文;
上下文发送模块, 用于向所述 FAP需要接入的接入服务网 ASN发送所述上下文, 以 供所述 ASN根据所述上下文和所述 ASN当前网络配置为所述 FAP生成入网所需的配置参 数并向所述 FAP发送。
15、 根据权利要求 14所述的毫微级接入点的入网装置, 其特征在于, 还包括: 接入网络选取模块, 用于根据所述 FAP的位置信息, 为所述 FAP选择拜访地 ASN。
16、 根据权利要求 15所述的毫微级接入点的入网装置, 其特征在于, 还包括: 重定向入口确定模块,用于比较所述拜访地 ASN与所述 FAP的家乡地 ASN是否相同, 如果不同, 为所述 FAP确定接入所述拜访地 ASN的拜访地安全网关;
重定向通知模块,用于向所述 FAP发送所述拜访地安全网关信息,用于通知所述 FAP 与所述拜访地安全网关建立重定向连接。
17、 一种毫微级接入点的入网装置, 其特征在于, 包括:
上下文接收模块,用于接收鉴权授权服务器根据 FAP入网请求发送的所述 FAP的上 下文;
配置参数生成模块,用于根据所述上下文和接入服务网的当前网络配置,为所述 FAP 生成入网所需的配置参数;
配置参数发送模块, 用于向所述 FAP发送所述配置参数。
18、 一种毫微级接入点的入网系统, 其特征在于, 包括: 安全网关、 第一入网装置 和第二入网装置;
所述第一入网装置用于通过所述安全网关接收毫微级接入点 FAP的入网请求;根据 所述入网请求, 获取所述 FAP的上下文; 向所述 FAP需要接入的接入服务网 ASN发送所 述上下文;
所述第二入网装置用于接收所述第一入网装置根据 FAP入网请求发送的所述 FAP的 上下文; 根据所述上下文和所述 ASN当前网络配置, 为所述 FAP生成入网所需的配置参 数; 通过所述安全网关向所述 FAP发送所述配置参数。
19、 一种毫微级接入点的入网系统, 其特征在于, 包括: 第一安全网关、 第二安全 网关、 第一入网装置和第二入网装置;
所述第一入网装置用于通过所述第一安全网关接收毫微级接入点 FAP的入网请求; 根据所述入网请求, 获取所述 FAP的上下文; 向所述 FAP需要接入的接入服务网发送所 述上下文;
所述第二入网装置用于接收所述第一入网装置根据 FAP入网请求发送的所述 FAP的 上下文;根据所述上下文和所述 ASN当前网络配置,为所述 FAP生成入网所需的配置参数; 通过所述第二安全网关向所述 FAP发送所述配置参数。
PCT/CN2010/070028 2009-01-16 2010-01-06 毫微级接入点的入网方法、装置和系统 WO2010081396A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910003500A CN101784050A (zh) 2009-01-16 2009-01-16 毫微级接入点的入网方法、装置和系统
CN200910003500.X 2009-01-16

Publications (1)

Publication Number Publication Date
WO2010081396A1 true WO2010081396A1 (zh) 2010-07-22

Family

ID=42339444

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/070028 WO2010081396A1 (zh) 2009-01-16 2010-01-06 毫微级接入点的入网方法、装置和系统

Country Status (2)

Country Link
CN (1) CN101784050A (zh)
WO (1) WO2010081396A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101272617A (zh) * 2008-05-05 2008-09-24 上海华为技术有限公司 接入设备参数的配置方法、装置及系统
CN101278579A (zh) * 2005-10-04 2008-10-01 艾利森电话股份有限公司 微微无线电基站的自动配置
CN101304610A (zh) * 2008-05-19 2008-11-12 华为技术有限公司 超小型蜂窝网络与宏网络间通信方法、系统及超小型网关

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101278579A (zh) * 2005-10-04 2008-10-01 艾利森电话股份有限公司 微微无线电基站的自动配置
CN101272617A (zh) * 2008-05-05 2008-09-24 上海华为技术有限公司 接入设备参数的配置方法、装置及系统
CN101304610A (zh) * 2008-05-19 2008-11-12 华为技术有限公司 超小型蜂窝网络与宏网络间通信方法、系统及超小型网关

Also Published As

Publication number Publication date
CN101784050A (zh) 2010-07-21

Similar Documents

Publication Publication Date Title
US20230345355A1 (en) Multimedia Priority Service for Wireless Devices
JP6045648B2 (ja) ユーザエンティティにネットワークアクセスを提供する方法及び装置
US9374318B2 (en) Method of call admission control for home femtocells
CN114503776A (zh) 使用共享下行链路数据支持群组通信
KR100999761B1 (ko) Wlan 상호접속에서의 서비스 및 어드레스 관리 시스템및 방법
US20060182061A1 (en) Interworking between wireless WAN and other networks
US20210385283A1 (en) Multimedia Priority Service
WO2017157339A1 (zh) 终端接入网络的方法、装置、芯片及终端
JP2003060653A (ja) 無線ネットワークおよび無線ネットワークにおける認証方法
US9241297B2 (en) Method and apparatus for providing local breakout service in wireless communication system
WO2007051423A1 (fr) Systeme et procede de communication pour l’entree et la sortie du mode repos d’un terminal
US20230171672A1 (en) Route configuration method and apparatus
WO2011075884A1 (zh) 一种向移动用户设备提供网络服务方法及其装置
JP2007060651A (ja) 移動通信システムにおけるローミングサービスの提供方法及びシステム
WO2010130174A1 (zh) 一种实现本地访问控制的方法及相应的通信系统
US20230189192A1 (en) Access to Second Network by Wireless Device
WO2012130133A1 (zh) 一种接入点及终端接入方法
WO2023185880A1 (zh) 一种接入网设备的确定方法
WO2008095433A1 (fr) Procédé, dispositif et système assurant un service d'urgence
KR101727557B1 (ko) 무선통신시스템에서 엘비오 서비스를 제공하기 위한 방법 및 장치
WO2012171430A1 (zh) 隧道信息获取方法、安全网关及演进家庭基站/家庭基站
WO2017129101A1 (zh) 路由控制方法、装置及系统
WO2011015091A1 (zh) 用于家用基站的接入方法、装置、系统及aaa服务器
WO2010091562A1 (zh) 用于固定网络与第三方网络或应用服务器交互的方法及装置
WO2012022212A1 (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: 10731030

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: 10731030

Country of ref document: EP

Kind code of ref document: A1