WO2014005487A1 - Procédé et dispositif d'acquisition et d'exécution d'acquisition en rapport avec une capacité réseau d'un réseau d'accès - Google Patents

Procédé et dispositif d'acquisition et d'exécution d'acquisition en rapport avec une capacité réseau d'un réseau d'accès Download PDF

Info

Publication number
WO2014005487A1
WO2014005487A1 PCT/CN2013/077802 CN2013077802W WO2014005487A1 WO 2014005487 A1 WO2014005487 A1 WO 2014005487A1 CN 2013077802 W CN2013077802 W CN 2013077802W WO 2014005487 A1 WO2014005487 A1 WO 2014005487A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
indication information
3gpp access
message
capability
Prior art date
Application number
PCT/CN2013/077802
Other languages
English (en)
Chinese (zh)
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 WO2014005487A1 publication Critical patent/WO2014005487A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel

Definitions

  • the present invention relates to the field of communications, and in particular to an access processing, acquisition method, and apparatus for access network capabilities.
  • EPS Evolved Packet System
  • 3GPP 3rd Generation Partnership Project
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 hereinafter referred to as the UE.
  • the network decides and allows the UE to access in only one mode, that is, one of the service offload and the access 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the Universal Mobile Telecommunications System 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.
  • 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
  • GGSN Gateway General Packet Radio Service Supporting Node
  • an access network processing capability acquisition method 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.
  • EAP Extended Authentication Protocol
  • DHCP Dynamic Host Configuration Protocol
  • GAS-ANQP Generic advertisement service - Access Network Query Protocol
  • 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.
  • a method for acquiring an access network network capability 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.
  • 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.
  • an apparatus for acquiring an access network network capability 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.
  • 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.
  • FIG. 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. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the foregoing capability indication information may be used to enable the UE to determine a UE type supported by the non-3GPP access network.
  • 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.
  • the non-3GPP access network is determined to be a non-3GPP access network supporting the affected 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.
  • 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.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • 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.
  • 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.
  • the foregoing apparatus may be implemented by the following scheme. As shown in FIG.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Embodiment 3 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.
  • 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.
  • 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.
  • Embodiment 4 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.
  • 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. .
  • Embodiment 5 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.
  • 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.
  • 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.
  • the APN information supporting the network selection may be extended in the RA message.
  • Embodiment 6 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.
  • 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.
  • 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.
  • 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.
  • Embodiment 7 the difference from Embodiment 5 is that the trusted non-3GPP access network delivers the APN to the UE through the GAS message.
  • 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 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.
  • Embodiment 8 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.
  • 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.
  • 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
  • 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.
  • the 3GPP network is UMTS
  • the SGSN replaces the MME in this embodiment
  • the GGSN replaces the PDN GW in this embodiment
  • 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.
  • 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.
  • steps S1307-S1315 For details, refer to the related description of Embodiment 5.
  • 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.
  • the 3GPP network is UMTS
  • the SGSN replaces the MME in this embodiment
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

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

Abstract

La présente invention se rapporte à un procédé et à un dispositif d'acquisition et d'exécution d'acquisition en rapport avec une capacité réseau d'un réseau d'accès. Le procédé d'exécution d'acquisition selon l'invention comprend les étapes suivantes : un élément de réseau d'un réseau d'accès autre que 3GPP transmet des informations d'indication de capacité à un UE, les informations d'indication de capacité comprenant un ou plusieurs des types d'informations suivants : des informations d'APN ; des informations d'indication relatives à un type de service de décision ; et des données de capacité d'un réseau d'accès autre que 3GPP. La solution technique décrite dans la présente invention est adoptée pour résoudre les problèmes techniques liés, dans l'état de la technique, au fait qu'il est impossible d'acquérir un type d'UE pris en charge par un réseau d'accès quand un équipement d'utilisateur initie un flux supplémentaire qui n'est pas pris en compte par le réseau d'accès, ce qui a un impact négatif sur l'expérience de l'utilisateur, et similaire. Au contraire, selon la présente invention, l'UE peut décider s'il doit, ou non, initier un flux spécifié, sur la base du type d'UE acquis qui est pris en charge par le réseau d'accès. L'expérience de l'utilisateur se trouve ainsi améliorée.
PCT/CN2013/077802 2012-07-02 2013-06-24 Procédé et dispositif d'acquisition et d'exécution d'acquisition en rapport avec une capacité réseau d'un réseau d'accès WO2014005487A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210225119.X 2012-07-02
CN201210225119.XA CN103533598B (zh) 2012-07-02 2012-07-02 接入网网络能力的获取处理、获取方法及装置

Publications (1)

Publication Number Publication Date
WO2014005487A1 true WO2014005487A1 (fr) 2014-01-09

Family

ID=49881323

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/077802 WO2014005487A1 (fr) 2012-07-02 2013-06-24 Procédé et dispositif d'acquisition et d'exécution d'acquisition en rapport avec une capacité réseau d'un réseau d'accès

Country Status (2)

Country Link
CN (1) CN103533598B (fr)
WO (1) WO2014005487A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104717632A (zh) * 2013-12-11 2015-06-17 中兴通讯股份有限公司 支持能力信息处理方法、装置、基站及终端
EP3099137B1 (fr) 2014-02-25 2019-05-22 Huawei Technologies Co., Ltd. Procédé, dispositif et système de notification de type de terminal pris en charge par une cellule courante
CN104902521B (zh) * 2014-03-07 2018-12-11 电信科学技术研究院 一种保证ip连续性的方法和设备
EP3244588B1 (fr) * 2016-05-10 2021-06-23 Nokia Solutions and Networks Oy Support de noyau dédié des réseaux d'accès wlan
CN107517489A (zh) * 2016-06-17 2017-12-26 中兴通讯股份有限公司 实现业务连续性的通信方法及装置
WO2019090662A1 (fr) * 2017-11-10 2019-05-16 Oppo广东移动通信有限公司 Procédé et appareil d'implémentation de service de réseau, dispositif informatique, et support de stockage
CN114222356B (zh) * 2019-10-08 2024-04-02 荣耀终端有限公司 一种降低ue功耗的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1833224A1 (fr) * 2006-03-08 2007-09-12 Alcatel Lucent Déclenchement des actions DHCP par des changements d'état IEEE 802.1x
CN101374334A (zh) * 2007-08-22 2009-02-25 华为技术有限公司 传递分组数据网络标识信息的方法和系统
CN101686191A (zh) * 2008-09-24 2010-03-31 华为技术有限公司 访问分组数据网业务的方法及系统、网关和终端
CN101902507A (zh) * 2010-08-02 2010-12-01 华为技术有限公司 一种地址分配方法、装置和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101547142B (zh) * 2008-03-26 2011-09-28 华为技术有限公司 分组数据网络连接的注册方法及装置
KR20100000171A (ko) * 2008-06-24 2010-01-06 주식회사 케이티 데이터 송수신 장치 및 방법
CN102457837B (zh) * 2010-10-21 2016-01-20 中兴通讯股份有限公司 一种用户签约信息处理方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1833224A1 (fr) * 2006-03-08 2007-09-12 Alcatel Lucent Déclenchement des actions DHCP par des changements d'état IEEE 802.1x
CN101374334A (zh) * 2007-08-22 2009-02-25 华为技术有限公司 传递分组数据网络标识信息的方法和系统
CN101686191A (zh) * 2008-09-24 2010-03-31 华为技术有限公司 访问分组数据网业务的方法及系统、网关和终端
CN101902507A (zh) * 2010-08-02 2010-12-01 华为技术有限公司 一种地址分配方法、装置和系统

Also Published As

Publication number Publication date
CN103533598B (zh) 2019-01-15
CN103533598A (zh) 2014-01-22

Similar Documents

Publication Publication Date Title
WO2014005487A1 (fr) Procédé et dispositif d'acquisition et d'exécution d'acquisition en rapport avec une capacité réseau d'un réseau d'accès
EP2858418B1 (fr) Procédé pour mettre à jour des informations d'identité au sujet d'une passerelle de paquets, serveur aaa et passerelle de paquets
US9167430B2 (en) Access method and system, and mobile intelligent access point
JP5101734B2 (ja) トンネル管理方法、トンネル管理装置および通信システム
EP3154306B1 (fr) Établissement d'une connexion de réseau
JP5504340B2 (ja) 発展型パケットシステムにおける端末のマルチアクセス方法及びシステム
US9843975B2 (en) Method and apparatus for establishing a PDN connection
US9113436B2 (en) Method and system for information transmission
CN102695236B (zh) 一种数据路由方法及系统
WO2013155920A1 (fr) Procédé de contrôle d'accès pour terminal d2d, terminal d2d, enb et mme
TW201141157A (en) User equipment (UE), home agent node (HA), methods, and telecommunications system for home network prefix (HNP) assignment
CN102763372A (zh) 一种异种网络切换时选择网关方法、装置及系统
WO2014067420A1 (fr) Procédé, dispositif et système de gestion de type de réseau de données en paquets
EP2741530A1 (fr) Procédé et système d'accès, et point d'accès intelligent mobile
WO2015024394A1 (fr) Procédé de traitement d'adresse réseau, dispositif, système, wlan et ue
WO2012068946A1 (fr) Procédé et système pour une interrogation de passerelle
WO2012100611A1 (fr) Procédé et système pour accéder à un système de paquets évolués
WO2013178178A2 (fr) Dispositif et procédé de libération de ressources
WO2013107243A1 (fr) Procédé et dispositif d'établissement de session
WO2013037271A1 (fr) Procédé et système d'accès multiple
WO2013060214A1 (fr) Procédé et appareil de signalement d'informations d'application
WO2014177022A1 (fr) Procédé et dispositif de traitement destinés à une capacité de prise en charge de mobilité de flux, et passerelle pdn
US20120176973A1 (en) Method for processing multiple access, home agent and user equipment
WO2015106565A1 (fr) Procédé et dispositif de régulation de congestion lors de l'accès à un réseau central par l'intermédiaire d'un twan
WO2012171425A1 (fr) Procédé et dispositif de traitement de service

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

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

Country of ref document: EP

Kind code of ref document: A1