WO2014005487A1

WO2014005487A1 - Acquisition processing and acquisition method and device for network capability of access network

Info

Publication number: WO2014005487A1
Application number: PCT/CN2013/077802
Authority: WO
Inventors: 刘国燕; 朱春晖; 周星月
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-07-02
Filing date: 2013-06-24
Publication date: 2014-01-09
Also published as: CN103533598A; CN103533598B

Abstract

Provided are an acquisition processing and acquisition method and device for the network capability of an access network. The acquisition processing method includes: a network element of a non-3GPP access network transmitting capability indication information to UE, wherein the capability indication information includes at least one of the following: APN information, decisional service type indication information, and non-3GPP access network capability information. The technical solution provided in the present invention is adopted to solve the technical problems in the related art that are due to the inability to acquire a UE type supported by an access network, whereby user equipment initiates an additional flow which is not supported by the access network, affecting the user experience and the like, so that the UE can decide whether to initiate a specified flow according to the acquired UE type supported by the access network, and the user experience is improved.

Description

The present invention relates to the field of communications, and in particular to an access processing, acquisition method, and apparatus for access network capabilities. BACKGROUND OF THE INVENTION The Evolved Packet System (EPS) of the 3rd Generation Partnership Project (3GPP) is evolved by the Evolved Universal Terrestrial Radio Access Network (referred to as Evolved Universal Terrestrial Radio Access Network). E-UTRAN), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (PDN GW), and home subscribers The server (Home Subscriber Server, referred to as HSS) is composed.

The EPS supports interworking with non-3GPP systems (as shown in FIG. 1), wherein interworking with non-3GPP systems is implemented through an S2a/b/c interface, and the PDN GW acts as an anchor between 3GPP and non-3GPP systems. In the system architecture diagram of EPS, non-3GPP system access is divided into untrusted non-3GPP access and trusted non-3GPP access; wherein untrusted non-3GPP access requires evolved packet data gateway (Evolved Packet Data Gateway) The ePDG is connected to the PDN GW. The interface between the ePDG and the PDN GW is S2b. The trusted non-3GPP access can be directly connected to the PDN GW through the S2a interface. The S2a interface uses the PMIP protocol to exchange information. In addition, the S2c interface provides User plane related control and mobility support between User Equipment (UE) and PDN GW. The supported mobility management protocol supports mobile IPv6 (Moblie IPv6 Support for Dual Stack Hosts and Routers, abbreviated as DSMIPv6), are available for untrusted non-3GPP and trusted non-3GPP access. Wireless Local Area Network (WLAN) can be used as a non-3GPP system to access the Evolved Packet Core (EPC). This involves the interconnection of fixed-line mobile convergence that many operators pay attention to. Interoperability issues. At present, there are many studies on the process and policy interworking of S2b and S2c interfaces, and there are few studies on S2a interfaces. Study on S2a Mobility based On GTP & WLAN access to EPC (SaMOG for short) The main topic is to study WLAN as a trusted non-3GPP IP access network (TNAN). The UE accesses the interconnection and interworking problem of the EPC through the S2a interface. In the prior art, as shown in FIG. 2, the UE accesses the 3GPP EPC through a non-3GPP access network, There are two main ways to distinguish between the non-3GPP access network and the PDN GW. The method is as follows: Mode 1: The UE completes the non-3GPP-specific process and the Extensible Authentication Protocol (EAP). After the authentication process, the UE and the trusted TNAN network element perform an L3 message, and then the TNAN initiates a tunnel establishment process to the PDN GW of the mobile core network after receiving the L3 message. Method 2: In addition to L3 messages, L2 messages can also be used as a trigger, such as: EAP messages. After the UE completes the non-3GPP-specific process and the EAP authentication process, the TNAN initiates a tunnel establishment process to the PDN GW of the mobile core network after receiving the EAP authentication success message.

The research solution of the SaMOG project is mainly divided into a scheme that has no impact on user equipment (User Equipment, UE for short) and a scheme that affects the UE. The scheme that has no effect on the UE means that the UE does not support the transmission of the Access Point Name (APN) information, and the additional Packet Data Network (PDN) connection and the access system. The handover procedure, etc., hereinafter referred to as the UE is an unaffected UE; and the scheme that affects the UE refers to the UE supporting the delivery of the APN information, and the additional PDN connection, the handover procedure between the access systems, etc. Affected UE. For the unaffected UE, when the UE accesses the network, the network decides and allows the UE to access in only one mode, that is, one of the service offload and the access EPC. When accessing the EPC, the UE It is not necessary to further select the appropriate APN access according to the specific service characteristics, because there is only one default APN. For the affected UE, the UE supports both traffic offload and access to the EPC, and supports additional PDN connections and handover procedures, etc.; and the affected UE may access the non-3GPP access network that supports only the unaffected UEs. It is also possible to access a non-3GPP access network supporting the affected UE. At present, based on the existing technical analysis, the following problems may exist: Currently, the affected UE receives the response information and access support when it accesses the non-3GPP access network of the unaffected UE. If the non-3GPP access network of the UE is the same, the affected UE may mistakenly consider that it accesses the non-3GPP access network supporting the affected UE, and then initiates an additional PDN connection process or handover procedure, and supports the unaffected The UE's non-3GPP access network will reject requests for these processes, thereby affecting the user experience. In addition, if the influential UE carries the APN to the non-3GPP access network, and the non-3GPP access network is the network supporting the unaffected UE, the access network ignores the APN carried by the influential UE; when the 3GPP AAA decides to When the UE allows access to the EPC, the default APN is adopted. However, the influential UE does not know that the non-3GPP access network has selected the new default APN, and erroneously believes that the APN access it carries is still affected, which affects the service experience. In addition, the Universal Mobile Telecommunications System (UMTS) also supports interworking with non-3GPP systems; the difference is that the Serving General Packet Radio Service Support Node (Serving General Packet Radio Service Support Node, The SGSN is used instead of the MME and the S-GW, and the Gateway General Packet Radio Service Supporting Node (GGSN) is used instead of the P-GW. Therefore, the above problem also exists in accessing the UMTS core network through the non-3GPP system. In view of the above problems in the related art, there is currently no effective solution. SUMMARY OF THE INVENTION In the related art, the present invention provides an access network capability, because the user equipment cannot learn the UE type supported by the access network and initiates an additional process that the access network does not support, thereby affecting technical problems such as user experience. The acquisition processing, acquisition method and device are used to solve at least the above technical problems. According to an embodiment of the present invention, an access network processing capability acquisition method is provided, including: a network element of a non-3GPP access network sends capability indication information to a UE, where the capability indication information includes at least one of the following : APN information, service type indication information for decision, non-3GPP access network capability information. The foregoing network element sends the capability indication information to the UE by using one of the following messages: an Extended Authentication Protocol (EAP) message, a Dynamic Host Configuration Protocol (DHCP) message, a general advertisement service-access network query protocol ( Generic advertisement service - Access Network Query Protocol, abbreviated as GAS-ANQP) message. The APN information indicates the APN selected by the non-3GPP access network; or the service type indication information of the decision indicates that the service is offloaded or accesses the EPC; or the non-3GPP access network capability information indicates that the non-3GPP access network supports the affected UE. . The above capability indication information is used to enable the UE to determine the UE type supported by the non-3GPP access network. The UE is an unaffected UE or an influential UE. The unaffected UE does not support the delivery of the APN, and the affected UE supports the delivery of the APN. The method further includes: when the affected UE receives the capability indication information, determining that the non-3GPP access network supports the affected UE. The method further includes: after receiving the capability indication information, the affected UE initiates an additional PDN connection according to the service requirement or initiates a handover process according to the selection policy of the access network. According to another embodiment of the present invention, a method for acquiring an access network network capability is provided, including: receiving, by a UE, capability indication information of a network element from a non-3GPP access network, where the capability indication information includes at least the following A: an access point name APN information, a service type indication information of a decision, and a non-3GPP access network capability information; the UE determines a UE type supported by the non-GPP access network according to the capability indication information. The foregoing network element sends the determined capability indication information to the UE by using one of the following messages: an EAP message, a DHCP message, and a GAS-ANQP message.

The APN information indicates the APN selected by the non-3GPP access network; or the service type indication information of the decision indicates that the service is offloaded or accesses the EPC; or the non-3GPP access network capability information indicates that the non-3GPP access network supports the influential UE. According to still another embodiment of the present invention, an apparatus for acquiring access network network capability is provided, which is located in a network element of a non-3GPP access network, and includes: a sending module, configured to send capability indication information to the UE, where The capability indication information includes at least one of the following: an access point name APN information, a determined service type indication information, and a non-3GPP access network capability information. The foregoing sending module is further configured to send the determined capability indication information to the UE by using one of the following messages: an EAP message, a DHCP message, and a GAS-ANQP message. According to still another embodiment of the present invention, an apparatus for acquiring an access network network capability is provided, which is located in a UE, and includes: a receiving module, configured to receive capability indication information of a network element from a non-3GPP access network, where The capability indication information includes at least one of the following: an access point name APN information, a determined service type indication information, and a non-3GPP access network capability information. The determining module is configured to determine, according to the capability indication information, a UE supported by the non-GPP access network. Types of. The receiving module is further configured to receive capability indication information by using one of the following messages: an EAP message, a DHCP message, and a GAS-ANQP message. With the present invention, the UE can learn the UE type supported by the access network according to the capability indication information sent by the network element of the branch access network, thereby solving the UE type that is not supported by the access network because the user equipment cannot be known in the related art. Initiating an additional process that is not supported by the access network, thereby affecting technical problems such as user experience, so that the UE can decide whether to initiate a specified process according to the type of UE supported by the obtained access network, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a schematic diagram of a network structure of a 3GPP network interworking with a non-3GPP network according to the related art; FIG. 2 is a schematic flowchart of a UE accessing an EPC through a trusted WLAN according to the related art; FIG. 4 is a structural block diagram of an access network capability acquisition processing apparatus according to Embodiment 1 of the present invention; FIG. 4b is a structural block diagram of an access network network capability acquisition processing apparatus according to Embodiment 1 of the present invention; FIG. 5 is a flowchart of a method for acquiring an access network capability according to Embodiment 2 of the present invention; FIG. 6 is an access network according to Embodiment 2 of the present invention; FIG. 7 is a schematic diagram of a first flow of a non-3GPP access network transmitting a APN to a UE by using a DHCP message according to Embodiment 3 of the present invention; FIG. 8 is a non-3GPP connection according to Embodiment 4 of the present invention; FIG. 9 is a schematic diagram of a third flow of a non-3GPP access network transmitting a APN to a UE by using a DHCP message according to Embodiment 5 of the present invention; FIG. Schematic flow chart APN to the UE by the EAP messages transmitted in accordance with the present invention the non-3GPP access networks in Example 6; FIG. 11 is a APN transmitted to the non-3GPP access network according to Example 7 of the present invention by a message 802.11u

FIG. 12 is a schematic flowchart of a service type of a non-3GPP access network transmitting a decision by an EAP to a UE according to Embodiment 8 of the present invention; FIG. 13 is a WLAN of a non-3GPP access network according to an embodiment of the present invention. A schematic diagram of the flow of the service type of the Uu message to the UE. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. Embodiment 1 In this embodiment, in the related art, an additional process that is not supported by the access network is initiated because the UE cannot learn the UE type supported by the access network, thereby affecting technical problems such as user experience, and providing a connection The method for obtaining the access network capability includes: transmitting, by the network element of the non-3GPP access network, the capability indication information to the UE, where the capability indication information includes at least one of the following: APN information, service type indication information of the decision, and 3GPP access network capability information. In a preferred embodiment of the present embodiment, the foregoing process may be implemented by the following process: FIG. 3 is a flowchart of a method for acquiring an access network capability according to Embodiment 1 of the present invention. As shown in FIG. 3, the method includes: Step S302: A network element of a non-3GPP access network determines capability indication information of a non-3GPP access network, where the capability indication information includes at least one of the following: APN information, a service type of the decision Indication information, non-3GPP access network capability information. In this embodiment, the non-3GPP access network may be a non-3GPP access network supporting the affected UE. Step S304, the network element sends the determined capability indication information to the UE. Through the foregoing processing steps, the network element of the non-3GPP access network sends the capability indication information for indicating the support of the non-3GPP access network to the UE, so that the UE can obtain the supported UE type of the access network (for example, the unaffected The UE and the influencing UE, etc., avoid the additional process that the access network does not support because the user equipment cannot know the type of the UE supported by the access network, and solves the problem that affects the user experience. The UE may decide whether to initiate a specified process according to the acquired UE type supported by the access network, thereby improving the user experience. In this embodiment, the network element sends the determined capability indication information to the UE by using one of the following messages: an EAP message, a DHCP message, and a GAS-ANQP message. That is, at least one of the foregoing APN information, the service type indication information of the decision, and the non-3GPP access network capability information may be sent by using one of the EAP message, the DHCP message, and the GAS-ANQP message. In this embodiment, the APN information indicates the APN selected by the non-3GPP access network; or the service type indication information of the decision indicates that the service is offloaded or accesses the EPC; or the non-3GPP access network capability information indicates the non-3GPP access. The network supports influential UEs. As can be seen from the foregoing embodiment, in this embodiment, the foregoing capability indication information may be used to enable the UE to determine a UE type supported by the non-3GPP access network. In this embodiment, the UE is an unaffected UE or an influential UE, where the unaffected UE does not support the delivery of the APN, and the affected UE supports the delivery of the APN. In this embodiment, when the UE that receives the capability indication information is an influential UE, the non-3GPP access network is determined to be a non-3GPP access network supporting the affected UE. When the UE that receives the capability indication information supports the influential UE, the UE that receives the capability indication information may initiate an additional PDN connection according to the service requirement or initiate a handover procedure according to the selection policy of the access network. It should be noted that, when the UE is an unaffected UE, the unaffected UE ignores the foregoing capability indication information, that is, does not respond to the foregoing capability indication information. In this embodiment, an access network processing capability acquisition device is also provided, where the device is located in a network element of a non-3GPP access network that supports an influential UE, and is used to implement the foregoing embodiments and preferred embodiments. The description of the modules involved in the device will be described below. As used hereinafter, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable. 4a is a structural block diagram of an apparatus for acquiring access network network capabilities according to Embodiment 1 of the present invention. As shown in FIG. 4a, the device includes: a sending module 42, configured to send capability indication information to the UE, where the capability indication information includes at least one of the following: an access point name APN information, a service type indication information of the decision Non-3GPP access network capability information. In a preferred embodiment of the present embodiment, the foregoing apparatus may be implemented by the following scheme. As shown in FIG. 4b, the apparatus in the preferred embodiment includes: a determining module 40, connected to the sending module 42, and configured to determine non-3GPP. The capability indication information of the access network, where the capability indication information includes at least one of the following: an access point name APN information, a determined service type indication information, and a non-3GPP access network capability information; and a sending module 42 configured to The determined capability indication information is sent to the UE. Through the functions implemented by the foregoing processing module, the UE can also obtain the UE type supported by the access network (for example, an unaffected UE and an influential UE, etc.), and avoids that the user equipment cannot know the UE supported by the access network. The type initiates an additional process that is not supported by the access network, and solves the problem that affects the user experience. Preferably, the sending module 42 is further configured to send the determined capability indication information to the UE by using one of the following messages: an EAP message, a DHCP message, and a GAS-ANQP message. Embodiment 2 This embodiment corresponds to Embodiment 1, and describes an access scheme of an access network capability on a user equipment side. Specifically, FIG. 5 is a flowchart of a method for acquiring an access network capability according to Embodiment 2 of the present invention. As shown in FIG. 5, the method includes: Step S502: The UE receives the capability indication information of the network element of the non-3GPP access network that supports the influential UE, where the capability indication information includes at least one of the following: APN information The service type indication information of the decision, the non-3GPP access network capability information; the step S504, the UE determines, according to the capability indication information, the UE type supported by the non-GPP access network, that is, the UE determines the non-GPP access network support according to the foregoing capability indication information. UE type. Corresponding to the solution described in Embodiment 1, the UE acquires the UE type supported by the non-GPP access network according to the capability indication information of the network element of the non-3GPP access network that supports the influential UE, so that the UE can The acquired UE type supported by the access network determines whether to initiate a specified process, which improves the user experience. The foregoing network element sends the determined capability indication information to the UE by using one of the following messages: an EAP message, a DHCP message, and a GAS-ANQP message. In this embodiment, the APN information indicates the APN selected by the non-3GPP access network; or the service type indication information of the decision indicates that the service is offloaded or accesses the EPC; or the non-3GPP access network capability information indicates the non-3GPP access. The network supports influential UEs. In this embodiment, an apparatus for acquiring access network capability is also provided, which is located in the UE. FIG. 6 is a structural block diagram of an apparatus for acquiring an access network capability according to Embodiment 2 of the present invention. As shown in Figure 6, the device includes: The receiving module 60 is connected to the determining module 62, and is configured to receive the capability indication information of the network element of the non-3GPP access network that supports the influential UE, where the capability indication information enables the UE to determine the non-3GPP access network support. The UE type, the influential UE is the UE corresponding to the version 12 of the 3GPP standard; the determining module 62 is configured to determine the UE type supported by the non-3GPP access network according to the foregoing capability indication information. In this embodiment, the receiving module 60 is further configured to receive the foregoing capability indication information by using one of the following messages: an EAP message, a DHCP message, and a GAS-ANQP message. In order to better understand the above-described Embodiment 1 and Embodiment 2, the following will be described in detail in conjunction with Embodiment 3 and Embodiment 4. The design idea of the following embodiment is that the non-3GPP network returns the network capability to the terminal, and the terminal can receive the network capability returned by the network, so that the influential UE can determine that the access is non-3GPP supporting the influential UE access. The network, or a non-3GPP network that only supports unaffected UE access, can further know whether the network supports multiple PDN links or handover procedures. Specifically, the non-3GPP access network supporting the affected UE can pass the selected APN and/or the determined service type indication and/or the non-3GPP access network capability information through the EAP message, or the DHCP message, or the GAS-ANQP. The message is delivered to the UE; if the affected UE receives the information, it can be judged to be a non-3GPP access network supporting the affected UE; if the affected UE determines that it is a non-3GPP access supporting the influential UE The network may initiate an additional PDN connection; in addition, if the unaffected UE receives this information, it ignores the information. The following embodiments relate to a scheme for acquiring information of a decision service type when a UE accesses a mobile core network through a non-3GPP, and in particular, the non-3GPP access network that supports an unaffected UE and an influential support for an affected UE respectively. Processing of the UE when the non-3GPP accesses the network. The following is the following: Embodiment 3 In this embodiment, the scenario is that the UE performs an additional PDN connection through the trusted non-3GPP initial access EPC or the UE through the trusted non-3GPP, where the EAP needs to transmit the APN, the PCO, and the like. The key information is described in the two scenarios, and the APN information is transmitted to the UE through DHCP. For details, refer to the process shown in FIG. 7. The process includes the following steps: Step S701a: The UE performs a non-3GPP-specific process, such as link establishment, access authentication, and the like, with the trusted non-3GPP access gateway network element. Step S701b: The UE may have accessed the 3GPP EPC through the non-3GPP access system. Steps S701a and S701b are two scenarios, step 701a occurs at the time of initial access, and step 701b occurs when the UE has completed initial attachment. The two steps are independent of the scene. Step S702: The UE sends an EAP-Start message to the non-3GPP access system. Steps S703-S705: The trusted non-3GPP access gateway acts as an EAP authenticator, and triggers an EAP authentication process to the UE. The UE carries the information such as the APN, the PDN type, the PCO, and the request type to the trusted non-3GPP access gateway in the EAP-RES/Identity message, where the request type is initial attachment or handover. Among them, APN is optional information. Steps S706-S710: The other processes of the EAP are completed between the UE and the AAA server. If the network side decision allows the UE to access the EPC, and then requests the PDN GW to allocate an IP address, the flow of the following manner 1 or method 2 is performed. Manner 1: The EAP authentication success message triggers the trusted non-3GPP access gateway to establish a session with the PDN GW: Step S711: After receiving the message that the EAP authentication succeeds, the trusted non-3GPP access gateway sends a create session request to the PDN GW or The proxy binds the update message. Step S712: Perform an IP-CAN session establishment operation between the PDN GW and the PCRF. Step S713: The PDN GW updates the PDN GW address to the HSS through the AAA server. Step S714: The PDN GW sends a create session response or a proxy binding acknowledgement message to the trusted non-3GPP access gateway, where the message includes an IP address allocated for the UE. Step S715: The non-3GPP access gateway sends an EAP authentication success message to the UE. Manner 2: The IP address request message triggers the trusted non-3GPP access gateway to establish a session with the PDN GW: Step S716: After receiving the message that the EAP authentication succeeds, the UE sends a request/DHCP discovery message to the trusted non-3GPP access gateway. . Step S717: After receiving the request/DHCP discovery message, the trusted non-3GPP access gateway sends a create session request or a proxy binding update message to the PDN GW. Steps S718-S720: Same steps S712-S714. Step S721: After receiving the create session request or the proxy binding update message, the trusted non-3GPP access gateway sends an advertisement/DHCP provision to the UE, where the message may carry the UE IP address. Step S722: The UE sends a request/DHCP request message to the trusted non-3GPP access gateway, and the trusted non-3GPP access gateway replies with a reply/DHCP acknowledgement message to the UE, where the message includes the selected APN and IP address. If the affected UE does not carry the APN information in the EAP request message, the APN included in the reply/DHCP acknowledgment message replied by the trusted non-3GPP access gateway to the UE is the default APN. The UE may perform the following operations according to the received information: If the trusted non-3GPP access gateway is configured to support the affected UE, the UE may initiate additional PDN connection establishment or handover. NOTE: In the foregoing embodiment, if the trusted non-3GPP access gateway sends the APN information to the unaffected UE, the UE in the embodiment considers that the unaffected UE ignores the information. If the network considers that the APN carried by the UE is the wrong APN, the EAP authentication failure message is sent to the UE, and the message includes an error reason value, such as: an incorrect APN, and does not perform subsequent request to the PDN GW to allocate an IP address. Process. When the 3GPP network is UMTS, the SGSN replaces the MME in this embodiment, and the GGSN replaces the PDN GW in this embodiment, and the functions to be enhanced are the same. Embodiment 4 In this embodiment, a scenario in which an UE performs an additional PDN connection through a trusted non-3GPP initial access EPC or a UE through a trusted non-3GPP, where a 3GPP required for APN, PCO, etc. is required through DHCP messaging Key Information. Description In these two scenarios, the APN information is transmitted to the UE through DHCP. For details, refer to the process shown in FIG. 8. The process includes the following steps: Step S801a: The UE may have accessed the 3GPP EPC through the non-3GPP access system. Steps S801b-S802: The UE performs a non-3GPP-specific process, such as link establishment, access authentication, and the like, with the trusted non-3GPP access gateway network element. Then, the UE completes the EAP authentication and authorization process. Steps S801a and S801b-S802 are two scenarios. Steps S801b-S802 occur at the time of initial access, and step S801a occurs when the UE has completed initial attachment. The two steps are independent of the scene. Step S803: The UE sends a request/DHCP discovery message to the trusted non-3GPP access gateway. The message carries the APN, PDN type, PCO, request type and other information to the trusted non-3GPP access gateway, where the request type is initial attachment or handover. Among them, APN is optional information. If the network side decision allows the UE to access the EPC, then requesting the PDN GW to allocate an IP address, then performing the following steps S804-S807. Step S804: After receiving the request/DHCP discovery message, the trusted non-3GPP access gateway sends a create session request or a proxy binding update message to the PDN GW. Step S805: Perform an IP-CAN session establishment operation between the PDN GW and the PCRF. Step S806: The PDN GW updates the PDN GW address to the HSS through the AAA server. Step S807: The PDN GW sends a create session response or a proxy binding acknowledgement message to the trusted non-3GPP access gateway, where the message includes an IP address allocated for the UE. Step S808: After receiving the create session request or the proxy binding update message, the trusted non-3GPP access gateway sends an advertisement/DHCP provision to the UE, where the message may carry the UE IP address. Step S809: The UE sends a request/DHCP request message to the trusted non-3GPP access gateway, and the trusted non-3GPP access gateway replies with a reply/DHCP acknowledgement message to the UE, where the message includes the APN and the IP address. If the affected UE does not carry the APN information in the EAP request message, the APN included in the reply/DHCP acknowledgment message replied by the trusted non-3GPP access gateway to the UE is the default APN.

The UE may perform the following operations according to the received information: If the trusted non-3GPP access gateway is configured to support the affected UE, the UE may initiate additional PDN connection establishment or handover. NOTE: In the foregoing embodiment, if the trusted non-3GPP access gateway sends the APN information to the unaffected UE, the UE in the embodiment considers that the unaffected UE ignores the information. If the network considers that the APN carried by the UE is an incorrect APN, it sends a DHCP negative message to the UE, and the message includes an error cause value, such as: an incorrect APN, and does not perform a subsequent process of requesting an IP address to the PDN GW. . When the 3GPP network is UMTS, the SGSN replaces the MME in this embodiment, and the GGSN replaces the PDN GW in this embodiment, and the functions to be enhanced are the same. Embodiment 5 In this embodiment, a scenario in which a UE performs an additional PDN connection through a trusted non-3GPP initial access EPC or a UE through a trusted non-3GPP, where a 3GPP required for APN, PCO, etc. is required through GAS messaging Key Information. Description In these two scenarios, the APN information is transmitted to the UE through DHCP. For details, refer to the process shown in FIG. 9. The process includes the following steps: Step S901a: The UE may have accessed the 3GPP EPC through the non-3GPP access system. Steps S901b-S904: The UE performs a non-3GPP-specific process with the trusted non-3GPP access gateway network element, for example, link establishment, access authentication, and the like, and GAS session establishment. Then, the UE completes the EAP authentication and authorization process. Steps S901a and S901b-S904 are two scenarios. Steps S901b-S904 occur at the time of initial access, and step S901a occurs when the UE has completed initial attachment. The two steps are independent of the scene. Step S905: After receiving the message that the EAP authentication succeeds, the UE sends a GAS-ANQP initial request message to the trusted non-3GPP access gateway. The trusted WLAN universal container in the message carries information such as APN, PDN type, PCO, request type, etc. to the trusted non-3GPP access gateway, where the request type is initial attachment or handover. Among them, APN is optional information. Step S906: The trusted non-3GPP access gateway sends a GAS-ANQP initial response message to the UE. Step S907: After receiving the message that the EAP authentication succeeds, the UE sends a request/DHCP discovery message to the trusted non-3GPP access gateway. Step S908: After receiving the request/DHCP discovery message, the trusted non-3GPP access gateway sends a create session request or a proxy binding update message to the PDN GW. Step S909: Perform an IP-CAN session establishment operation between the PDN GW and the PCRF. Step S910: The PDN GW updates the PDN GW address to the HSS through the AAA server. Step S911: The PDN GW sends a create session response or a proxy binding acknowledgement message to the trusted non-3GPP access gateway, where the message includes an IP address allocated for the UE. Step S912: After receiving the create session request or the proxy binding update message, the trusted non-3GPP access gateway sends an advertisement/DHCP provision to the UE, where the message may carry the UE IP address. Step S913: The UE sends a request/DHCP request message to the trusted non-3GPP access gateway, and the trusted non-3GPP access gateway replies with a reply/DHCP acknowledgement message to the UE, where the message includes the APN and the IP address. If the affected UE does not carry the APN information in the GAS-ANQP request message, the APN included in the reply/DHCP acknowledgment message replied by the trusted non-3GPP access gateway to the UE is the default APN. Step S914: After the delay time arrives, the UE sends a GAS-ANQP recovery request message to the trusted non-3GPP access gateway. Step S915: The trusted non-3GPP access gateway sends a GAS-ANQP recovery response message to the UE. The message may carry the parameters assigned by the P-GW.

The UE may perform the following operations according to the received information: If the trusted non-3GPP access gateway is configured to support the affected UE, the UE may initiate additional PDN connection establishment or handover. NOTE: In the foregoing embodiment, if the trusted non-3GPP access gateway sends the APN information to the unaffected UE, the UE in the embodiment considers that the unaffected UE ignores the information. If the network considers that the APN carried by the UE is the wrong APN, it sends a GAS-ANQP failure message to the UE. The message contains the error cause value, such as the wrong APN, and does not perform subsequent request to allocate the IP address to the PDN GW. Process. When the 3GPP network is UMTS, the SGSN replaces the MME in this embodiment, and the GGSN replaces the PDN GW in this embodiment, and the functions to be enhanced are the same. In the foregoing embodiment 1-3, if the IP address request is supported by the RS/RA message, the APN information supporting the network selection may be extended in the RA message. Embodiment 6 In this embodiment, the difference from Embodiment 3 is that the trusted non-3GPP access network delivers the APN to the UE through the EAP message. For details, see the process shown in Figure 10. The process includes the following steps: Step S1001: The UE performs a non-3GPP-specific process, such as link establishment, access authentication, and the like, with the trusted non-3GPP access gateway network element. Step S1001b: The UE may have accessed the 3GPP EPC through the non-3GPP access system. Steps S100a1 and S1001b are two scenarios, step S100a1 occurs at the time of initial access, and step S1001b occurs when the UE has completed initial attachment. The two steps are independent of the scene. Step S1002: The UE sends an EAP-Start message to the non-3GPP access system. Steps S1003-S1005: The trusted non-3GPP access gateway acts as an EAP authenticator, and triggers an EAP authentication process to the UE. The UE carries the information such as the APN, the PDN type, the PCO, and the request type to the trusted non-3GPP access gateway in the EAP-RES/Identity message, where the request type is initial attachment or handover. Among them, APN is optional information. Steps S1006-S1010: Other processes of EAP are completed between the UE and the AAA server. The trusted non-3GPP access gateway carries the selected APN to the UE by using an EAP-REQ/AKA'-Challenge message. If the affected UE does not carry the APN information in the EAP request message, the APN included in the EAP-REQ/AKA'-Challenge message that the trusted non-3GPP access gateway replies to the UE is the default APN. Manner 1: The EAP authentication success message triggers the trusted non-3GPP access gateway to establish a session with the PDN GW: Step S1011: After the trusted non-3GPP access gateway receives the EAP authentication success message, the PDN is sent to the PDN.

The GW sends a create session request or a proxy binding update message. Step S1012: Perform an IP-CAN session establishment operation between the PDN GW and the PCRF. Step S1013: The PDN GW updates the PDN GW address to the HSS through the AAA server. Step S1014: The PDN GW sends a create session response or a proxy binding acknowledgement message to the trusted non-3GPP access gateway, where the message includes an IP address allocated for the UE. Step S1015: The non-3GPP access gateway sends an EAP authentication success message to the UE. Manner 2: The IP address request message triggers the trusted non-3GPP access gateway to establish a session with the PDN GW: Step S1016: After receiving the message that the EAP authentication succeeds, the UE sends a request/DHCP discovery message to the trusted non-3GPP access gateway. . Step S1017: After the trusted non-3GPP access gateway receives the request/DHCP discovery message, the PDN is sent to the PDN.

The GW sends a create session request or a proxy binding update message. Steps S1018-S1020: Same steps S1012-S1014. Step S1021: After receiving the create session request or the proxy binding update message, the trusted non-3GPP access gateway sends an advertisement/DHCP provision to the UE, where the message may carry the UE IP address. Step S1022: The UE sends a request/DHCP request message to the trusted non-3GPP access gateway, and the trusted non-3GPP access gateway replies with a reply/DHCP acknowledgement message to the UE, where the message includes an IP address.

The UE may perform the following operations according to the received information: If the trusted non-3GPP access gateway is configured to support the affected UE, the UE may initiate additional PDN connection establishment or handover. NOTE: In the foregoing embodiment, if the trusted non-3GPP access gateway sends the APN information to the unaffected UE, in this embodiment, the unaffected UE ignores the information. If the network considers that the APN carried by the UE is the wrong APN, the EAP authentication failure message is sent to the UE, and the message includes an error reason value, such as: an incorrect APN, and does not perform subsequent request to the PDN GW to allocate an IP address. Process. When the 3GPP network is UMTS, the SGSN replaces the MME in this embodiment, and the GGSN replaces the PDN GW in this embodiment, and the functions to be enhanced are the same. Embodiment 7 In this embodiment, the difference from Embodiment 5 is that the trusted non-3GPP access network delivers the APN to the UE through the GAS message. For details, refer to the process shown in Figure 11. The process includes the following steps: Step S1101a: The UE may have accessed the 3GPP EPC through the non-3GPP access system. Steps S1101b-S1104: The UE performs a non-3GPP-specific procedure with the trusted non-3GPP access gateway network element, for example, link establishment, access authentication, and the like, and GAS session establishment. Then, the UE completes the EAP authentication and authorization process. Steps SI 101a and S1101b-S1104 are two scenarios. Steps S1101b-S1104 occur at the time of initial access, and step S110la occurs when the UE has completed initial attachment. The two steps are independent of the scene. Step S1105: After receiving the message that the EAP authentication succeeds, the UE sends a GAS-ANQP initial request message to the trusted non-3GPP access gateway. The trusted WLAN universal container in the message carries information such as APN, PDN type, PCO, request type, etc. to the trusted non-3GPP access gateway, where the request type is initial attachment or handover. Among them, APN is optional information. Step S1106: The trusted non-3GPP access gateway sends a GAS-ANQP initial response message to the UE, where the message carries the selected APN. If the influential UE does not carry the APN information in the GAS-ANQP initial request message, the trusted non-3GPP access gateway replies to the UE that the APN included in the GAS-ANQP initial response message is the default APN. Step S1107: After receiving the message that the EAP authentication succeeds, the UE sends a request/DHCP discovery message to the trusted non-3GPP access gateway. Step S1108: After receiving the request/DHCP discovery message, the trusted non-3GPP access gateway sends a create session request or a proxy binding update message to the PDN GW. Step S1109: Perform an IP-CAN session establishment operation between the PDN GW and the PCRF. Step S1110: The PDN GW updates the PDN GW address to the HSS through the AAA server. Step S111: The PDN GW sends a create session response or a proxy binding acknowledgement message to the trusted non-3GPP access gateway, where the message includes an IP address allocated for the UE. Step S1112: After receiving the create session request or the proxy binding update message, the trusted non-3GPP access gateway sends an advertisement/DHCP provision to the UE, where the message may carry the UE IP address. Step S1113: The UE sends a request/DHCP request message to the trusted non-3GPP access gateway, and the trusted non-3GPP access gateway replies with a reply/DHCP acknowledgement message to the UE, where the message includes an IP address. Step S1114: After the delay time arrives, the UE sends a GAS-ANQP recovery request message to the trusted non-3GPP access gateway. Step S1115: The trusted non-3GPP access gateway sends a GAS-ANQP recovery response message to the UE. The message may carry the parameters assigned by the P-GW. The UE may perform the following operations according to the received information: If the trusted non-3GPP access gateway is configured to support the affected UE, the UE may initiate additional PDN connection establishment or handover. NOTE: In the foregoing embodiment, if the trusted non-3GPP access gateway sends the APN information to the unaffected UE, the UE in the embodiment considers that the unaffected UE ignores the information. If the network considers that the APN carried by the UE is the wrong APN, it sends a GAS-ANQP failure message to the UE. The message contains the error cause value, such as the wrong APN, and does not perform subsequent request to allocate the IP address to the PDN GW. Process. When the 3GPP network is UMTS, the SGSN replaces the MME in this embodiment, and the GGSN replaces the PDN GW in this embodiment, and the functions to be enhanced are the same. Embodiment 8 In this embodiment, a scenario in which a UE performs an additional PDN connection through a trusted non-3GPP initial access EPC or a UE through a trusted non-3GPP, and a trusted non-3GPP access network transmits a decision through EAP. Service type information is given to the UE. For details, refer to the process shown in Figure 12, where the process includes the following steps: Step S1201a: The UE performs a non-3GPP-specific process, such as link establishment, access authentication, and the like, with the trusted non-3GPP access gateway network element. Step S1201b: The UE may have accessed the 3GPP EPC through the non-3GPP access system. Steps S1201a and S1201b are two scenarios. Step S1201a occurs at the time of initial access, and step 301b occurs when the UE has completed initial attachment. The two steps are independent of the scene. Step S1202: The UE sends an EAP-Start message to the non-3GPP access system. Steps S1203-S1205: The trusted non-3GPP access gateway acts as an EAP authenticator, and triggers an EAP authentication process to the UE. Steps S1206-S1210: Other processes of EAP are completed between the UE and the AAA server. The trusted non-3GPP access gateway carries the determined service type to the EAP-REQ/AKA'-Challenge message. The UE, the service type of the decision may indicate that the service is offloaded or accesses the EPC through an indication, such as: 1 represents service offload, 0 represents access to EPC, or other information is represented. If it is accessing the EPC, it requests the PDN GW to allocate an IP address. For the specific process, refer to steps S1211-S1222. For details, refer to the related description of Embodiment 3. Optionally, the selected APN may be delivered to the UE by using a DHCP message or an EAP authentication response message, and the selected APN is delivered to the UE in step S1209 or step S1222. If the traffic is offloaded, the trusted non-3GPP access network locally assigns an IP address to the UE, and steps S1211-S1214 and steps S1217-S1220 are not performed.

The UE may perform the following operations according to the received information: When determining that the trusted non-3GPP access gateway supports the influential UE, the UE may initiate additional

PDN connection establishment or switching process. NOTE: In the foregoing embodiment, the trusted non-3GPP access gateway also sends the determined service type information to the unaffected UE. In this embodiment, the unaffected UE ignores the information. When the 3GPP network is UMTS, the SGSN replaces the MME in this embodiment, and the GGSN replaces the PDN GW in this embodiment, and the functions to be enhanced are the same. Embodiment 9 In this embodiment, the difference from Embodiment 8 is that the trusted non-3GPP access network gives the UE the service type of the decision through the GAS message. For details, refer to the process shown in Figure 13. The process includes the following steps: Step S1301a: The UE may have accessed the 3GPP EPC through the non-3GPP access system. Steps S1301b-S1304: The UE performs a non-3GPP-specific process with the trusted non-3GPP access gateway network element, for example, link establishment, access authentication, and the like, and GAS session establishment. Then, the UE completes the EAP authentication and authorization process. Steps S1301a and S1301b-S1304 are two scenarios. Steps S1301b-S1304 occur at the time of initial access, and step S10a occurs when the UE has completed initial attachment. The two steps are independent of the scene. Step S1305: After receiving the message that the EAP authentication succeeds, the UE sends a GAS-ANQP initial request message to the trusted non-3GPP access gateway. Step S1306: The trusted non-3GPP access gateway sends a GAS-ANQP initial response message to the UE, where the service type of the decision is carried to the UE, and the service type of the decision may indicate that the service is offloaded or accessed through an indication. EPC, for example: 1 represents service offload, 0 represents access to EPC, or other information is represented. If it is accessing the EPC, it requests the PDN GW to allocate an IP address. For the specific process, refer to steps S1307-S1315. For details, refer to the related description of Embodiment 5. Optionally, the selected APN may be delivered to the UE by using a DHCP message or a GAS-ANQP initial response message, and the selected APN is delivered to the UE in step S1306 or step S1313. If the traffic is offloaded, the trusted non-3GPP access network locally allocates an IP address to the UE, and steps S1308-S1311 are not performed.

The UE may perform the following operations according to the received information: If the trusted non-3GPP access gateway is configured to support the affected UE, the UE may initiate additional PDN connection establishment or handover. NOTE: In the foregoing embodiment, the trusted non-3GPP access gateway also sends the determined service type information to the unaffected UE. In this embodiment, the unaffected UE ignores the information. When the 3GPP network is UMTS, the SGSN replaces the MME in this embodiment, and the GGSN replaces the PDN GW in this embodiment, and the functions to be enhanced are the same. Embodiment 10 In this embodiment, it is explained that a trusted non-3GPP access network supports transmitting a network capability indication information to a UE to a UE. For example, when the UE sends the requested APN to the trusted non-3GPP access network, the trusted non-3GPP access network may not carry the selected APN to the UE, because the UE selects one of the subscribed APNs, the network The side will generally accept. At this time, the trusted non-3GPP access network may send a network capability indication to support the capability of the influential UE on the non-3GPP access network, for example: 1 means support for influential UE, 0 The representative only supports unaffected UEs. With this indication, the influential UE can know whether the trusted non-3GPP access network supports the affected UE or only the unaffected UE. Alternatively, regardless of whether the UE carries the APN, the trusted non-3GPP access network sends a network capability indication and a determined service type information, and the UE can determine whether it is a service offload or an access EPC through the combination of the two information. If the decision is to allow access to the EPC, the APN used by the UE may be considered as the APN carried by the UE or the default APN.

Based on the received information, the UE may perform the following operations: To determine that the trusted non-3GPP access gateway supports the influential UE, the UE may initiate an additional PDN connection establishment or handover procedure. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing system, which can be concentrated on a single computing system or distributed in a network composed of multiple computing systems. Alternatively, they may be implemented by program code executable by the computing system, such that they may be stored in the storage system by the computing system and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

An access processing method for access network capabilities, including:

The network element of the non-3GPP access network sends the capability indication information to the user equipment UE, where the capability indication information includes at least one of the following: an access point name APN information, a determined service type indication information, and a non-3GPP access network. Capability information.

2. The method according to claim 1, wherein the network element sends the capability indication information to the UE by using one of the following messages:

Extended Authentication Protocol EAP Message, Dynamic Host Setup Protocol DHCP Message, Generic Advertising Service - Access Network Query Protocol GAS-ANQP message.

The method according to claim 1, wherein the APN information indicates an APN selected by the non-3GPP access network; or the service type indication information of the decision indicates that the service is offloaded or accesses the EPC; or The non-3GPP access network capability information indicates that the non-3GPP access network supports an influential UE.

The method according to claim 1, wherein the capability indication information is used to enable a UE to determine a UE type supported by the non-3GPP access network.

The method according to claim 4, wherein the UE is an unaffected UE or an influential UE, wherein the unaffected UE does not support delivery of an APN, and the influential UE supports delivery of an APN.

6. The method according to claim 5, further comprising:

When the affected UE receives the capability indication information, it is determined that the non-3GPP access network supports the affected UE.

The method according to any one of claims 1 to 6, further comprising:

After receiving the capability indication information, the influential UE initiates an additional PDN connection according to the service requirement or initiates a handover process according to the selection policy of the access network.

8. A method for obtaining access network capability, comprising:

The user equipment UE receives the capability indication information of the network element from the non-3GPP access network, where the capability indication information includes at least one of the following: an access point name APN information, a determined service type indication information, and a non-3GPP access. Network capability information; The UE determines, according to the capability indication information, a UE type supported by the non-GPP access network.

9. The method according to claim 8, wherein the network element sends the determined capability indication information to the UE by using one of the following messages:

The method according to claim 8, wherein the APN information indicates an APN selected by the non-3GPP access network; or the service type indication information of the decision indicates that the service is offloaded or accesses the EPC; or The non-3GPP access network capability information indicates that the non-3GPP access network supports an influential UE.

An apparatus for acquiring access network network capability, located in a network element of a non-3GPP access network, the apparatus includes:

The sending module is configured to send the capability indication information to the user equipment UE, where the capability indication information includes at least one of the following: an access point name APN information, a determined service type indication information, and a non-3GPP access network capability information. .

12. The apparatus according to claim 11, wherein the sending module is further configured to send the determined capability indication information to the UE by using one of the following messages: an extended authentication protocol EAP message, a dynamic host setting protocol DHCP Message, General Advertising Service - Access Network Query Protocol GAS-ANQP message.

An apparatus for acquiring an access network network capability, which is located in a user equipment UE, and the apparatus includes:

The receiving module is configured to receive the capability indication information of the network element from the non-3GPP access network, where the capability indication information includes at least one of the following: an access point name APN information, a service type indication information of the decision, and a non-3GPP Access network capability information;

The determining module is configured to determine, according to the capability indication information, a UE type supported by the non-GPP access network.

14. The apparatus of claim 13, wherein the receiving module is further configured to receive the capability indication information by one of: an extended authentication protocol EAP message, a dynamic host setup protocol DHCP message, a universal advertising service-connected Enter the network query protocol GAS-ANQP message.