WO2013104247A1 - 一种通过非3gpp接入核心网的方法、装置和系统 - Google Patents

一种通过非3gpp接入核心网的方法、装置和系统 Download PDF

Info

Publication number
WO2013104247A1
WO2013104247A1 PCT/CN2012/087205 CN2012087205W WO2013104247A1 WO 2013104247 A1 WO2013104247 A1 WO 2013104247A1 CN 2012087205 W CN2012087205 W CN 2012087205W WO 2013104247 A1 WO2013104247 A1 WO 2013104247A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
capability
apn
message
tnan
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2012/087205
Other languages
English (en)
French (fr)
Inventor
刘国燕
朱春晖
梁爽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to EP12865052.0A priority Critical patent/EP2804420A4/en
Priority to US14/371,159 priority patent/US9516681B2/en
Priority to JP2014550621A priority patent/JP5872066B2/ja
Publication of WO2013104247A1 publication Critical patent/WO2013104247A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/084—Access security using delegated authorisation, e.g. open authorisation [OAuth] protocol
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/17—Selecting a data network PoA [Point of Attachment]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for accessing a core network through a non-3rd Generation Partnership Project (3GPP). Background technique
  • EPS Evolved Packet System
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • the EPS supports interworking with non-3GPP systems (as shown in Figure 1), where interworking with non-3GPP systems is implemented through the S2a/b/c interface, and the P-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; among them, the evolved packet data gateway (Evolved Packet) is required for untrusted non-3GPP access.
  • the Data Gateway (ePDG) is connected to the P-GW.
  • the interface between the ePDG and the P-GW is S2b. When the trusted non-3GPP access is available, the S2a interface can be directly connected to the P-GW.
  • the S2a interface uses the proxy mobile Internet protocol (Proxy).
  • the Mobile IP, ⁇ ) protocol exchanges information; in addition, the S2c interface provides user plane-related control and mobility support between the User Equipment (UE) and the P-GW, and the mobility management protocol supported by the S2c interface is Moblie IPv6 Support for Dual Stack Hosts and Routers (DSMIPv6), which can be used for untrusted non-3GPP and trusted non-3GPP access.
  • DSMIPv6 Dual Stack Hosts and Routers
  • the Wireless Local Area Network can be used as an Evolved Packet Core (EPC) for non-3GPP system access. It can support the above three interfaces, including: S2a, S2b, and S2c. At present, there are many researches on the process and policy interworking of S2b and S2c interfaces.
  • EPC Evolved Packet Core
  • the process refinement and policy interworking of the S2a interface are beginning to be studied.
  • it is studied how to trigger S2a session establishment without the need to enhance the functionality of existing UEs.
  • the UE completes the non-3GPP-specific process and the Extensible Authentication Protocol (EAP) authentication process
  • the UE and the trusted non-3 GPP IP access network (trusted non-3 GPP IP access network, TNAN ) Perform L3 messages between network elements.
  • TNAN received
  • the process of establishing the S2a session is initiated to the P-GW of the mobile core network.
  • L2 messages can also be used as a trigger, such as: EAP messages.
  • the triggering method for the above S2a session establishment is discussed and basically accepted.
  • the UE does not support the transmission of an Access Point Name (APN), a packet data network (PDN) type, etc., but the information is required for the 3GPP EPC to establish an S2a session or assign an IP address to the UE.
  • Key information for example: If the APN information is not known, an additional PDN connection cannot be established for the UE; if the PDN type cannot be known, the P-GW cannot perceive the IP address type that the UE wants to request, and can only be assigned according to the type of the signed IP address. IP address, and this allocation method is easy to waste IP address resources.
  • the UE when switching from 3GPP access to non-3GPP access, the UE cannot transmit information that needs to retain the UE IP address to the EPC, and cannot guarantee service continuity.
  • the main object of the present invention is to provide a method, an apparatus, and a system for accessing a core network through a non-3GPP, to know the capabilities of the UE, to determine whether to support the establishment of an additional PDN connection, and to switch between access systems. Business continuity.
  • a method for accessing a core network through a non-3rd Generation Partnership Project 3GPP comprising: a decision result of receiving, after the user equipment UE transmits capability information of the UE, whether to allow the UE to transmit information required to establish an evolved packet core network EPC session ;
  • the UE decides whether to pass the information required to establish an EPC session.
  • the capability information of the UE is carried in an extensible authentication protocol EAP authentication message or a dynamic host configuration protocol DHCP message.
  • a method for accessing a core network through a non-3rd Generation Partnership Project 3GPP comprising: learning capability information of a user equipment UE and/or capability information of a non-3GPP access system; determining whether to allow permission according to the learned capability information
  • the UE passes the information needed to establish an EPC session.
  • the operation of learning the capability information is performed by a UE or a non-3GPP access system.
  • the non-3GPP access system when the decision is made by a non-3GPP access system, the non-3GPP access system will send a decision result to the UE to allow the UE to transmit the information required to establish an EPC session.
  • the method further includes:
  • the non-3GPP access system After receiving the requested APN carried by the UE, the non-3GPP access system transmits the APN requested by the UE to the EPC.
  • the APN information is used to implicitly indicate the capability of the UE.
  • the capability information of the UE is carried in an extensible authentication protocol EAP authentication message or a dynamic host configuration protocol DHCP message.
  • the information required for establishing an EPC session is carried in an EAP authentication message or a DHCP message.
  • the capability information of the UE is: an APN requested by the UE, or a capability indication of the UE; and the information required to establish an EPC session is: the requested APN.
  • the capability information of the non-3GPP access system is: a capability indication local to the non-3GPP access system.
  • the communication entity that performs the decision is a UE, or a non-3GPP access system.
  • a system for accessing a core network through a non-3GPP including a capability information learning unit and an enhanced information decision unit;
  • the capability information obtaining unit is configured to learn capability information of the UE and/or capability information of the non-3GPP access system;
  • the enhanced information decision unit is configured to determine, according to the capability information, the capability information obtained by the unit, whether the UE is allowed to transmit information required to establish an EPC session.
  • the enhanced information decision unit is further configured to send, to the UE, a decision result of whether to allow the UE to transmit information required to establish an EPC session.
  • the enhanced information decision unit determines that the UE is allowed to transmit information required for establishing an EPC session; the enhanced information decision unit is further configured to:
  • the APN requested by the UE is delivered to the EPC.
  • the APN information is used to implicitly indicate the capability of the UE.
  • the capability information of the UE is carried in an EAP authentication message or a DHCP message.
  • the information required for establishing an EPC session is carried in an EAP authentication message or a DHCP message.
  • the capability information of the UE is: an APN requested by the UE, or a capability indication of the UE; and the information required to establish an EPC session is: the requested APN.
  • the capability information obtaining unit is configured in a UE or a non-3GPP access system
  • the enhanced information decision unit is configured in a UE or a non-3GPP access system.
  • An apparatus for accessing a core network by using a non-3GPP the apparatus being a UE, configured to: after transmitting capability information of the UE, receive a decision result of whether to allow the UE to transmit information required to establish an EPC session; and according to the decision result, Decide whether to pass the information needed to establish an EPC session.
  • the capability information of the UE is carried in an extensible EAP authentication message or a DHCP message.
  • FIG. 1 is a network structure diagram of a 3GPP network interworking with a non-3GPP network in the prior art
  • FIG. 2 is a flowchart of a UE accessing an EPC through a trusted WLAN in the prior art
  • FIG. 3 is an embodiment of the present invention
  • FIG. 4 is a flowchart of a UE carrying an APN requested by a UE in an EAP authentication message according to another embodiment of the present invention
  • FIG. 5 is a flowchart of a UE carrying an UE capability indication in an EAP authentication message according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a UE carrying an UE capability indication in an EAP authentication message according to another embodiment of the present invention.
  • FIG. 7 is a flowchart of a capability indication that a TNAN carries a network support in an EAP authentication message according to the present invention
  • FIG. 8 is a flowchart of a capability indication that a TNAN carries network support in an L3 message according to an embodiment of the present invention
  • FIG. 9 is a flowchart of a capability indication that a TNAN carries network support in an L3 message according to another embodiment of the present invention.
  • FIG. 10 is a flowchart of a capability indication that a TNAN carries a network support in an L3 message according to another embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a process of accessing a core network through a non-3GPP according to an embodiment of the present invention
  • FIG. 12 is a system diagram of accessing a core network by using a non-3GPP according to an embodiment of the present invention.
  • the capability information of the UE and/or the capability information of the non-3GPP access system may be known (directly or implicitly learned); and according to the acquired capability information, whether to allow the UE to carry the enhancement required by the EPC is determined. Information, ie whether the decision allows the UE to pass the information needed to establish an EPC session.
  • the non-3GPP access system may be a trusted non-3GPP access system or an untrusted non-3GPP access system. The following only describes a trusted non-3GPP access system as an example.
  • the communication entity that performs the decision may be a UE, or a non-3GPP access system
  • the capability information carried by the UE may be: an APN requested by the UE, or a capability indication of the UE;
  • the UE carries the requested APN information, and may implicitly indicate the capability of the UE;
  • the capability information of the non-3GPP access system may be: a capability indication local to the non-3GPP access system;
  • the enhanced information carried by the UE may be: the requested APN; If the UE is allowed to carry the enhanced information after the decision, the non-3GPP access system transmits the APN requested by the UE to the EPC after receiving the requested APN carried by the UE; for example, transmitting the APN requested by the UE to the P-GW.
  • the non-3GPP access system sends a decision result whether to allow the UE to carry the enhanced information to the UE;
  • the capability information of the UE may be carried by an EAP authentication message or a DHCP (Dynamic Host Configuration Protocol) message;
  • DHCP Dynamic Host Configuration Protocol
  • the enhanced information of the UE may be carried by an EAP authentication message or a DHCP message.
  • the EAP authentication message when the UE accesses the EPC through the trusted non-3GPP, the EAP authentication message supports the APN that is requested by the UE to the TNAN, and the TNAN decides whether to support the APN that carries the UE request to the EPC.
  • the EAP authentication message triggers the TNAN to create a GTP/PMIP session to the P-GW. For details, see the process shown in Figure 3. The process includes the following steps:
  • Step 301 The UE and the TNAN network element perform a non-3GPP-specific process, such as: link establishment, access authentication, and the like;
  • Steps 302-310 The TNAN acts as an EAP Authenticator and triggers an EAP authentication process to the UE.
  • the UE carries the APN requested by the UE to the TNAN in the EAP-RES/Identity message. And the TNAN decides whether to allow the UE to carry the requested APN according to the requested APN and the local policy carried by the UE, specifically: if the TNAN supports the UE to carry the requested APN, the subsequent process is continued; otherwise, the subsequent operation is in the prior art.
  • the process of the UE does not carry the requested APN is the same.
  • the solution for the UE to obtain the IP address includes the following methods: Mode 1: The EAP authentication message triggers the TNAN to create a session, and the session allocates an IP address to the UE.
  • Steps 311-312 After receiving the EAP-SUCCESS message, the TNAN ignores the received default APN, and initiates a process of creating a session to the P-GW.
  • the TNAN carries the APN requested by the UE to the P-GW, and the P-GW. An S2a session is established.
  • the P-GW allocates an IP address to the UE, and returns the IP address to the TNAN.
  • the TNAN locally stores the IP addresses, and the IP address may specifically include an IPv4 and/or an IPv6 address.
  • the TNAN locally stores the association relationship between the UE MAC address and the IP address.
  • Step 313-315 If the TNAN receives the route request message, the TNAN finds the corresponding IP address according to the UE MAC address, and the TNAN sends a route response message to the UE, where the P-GW carries the IPv6 address allocated by the UE.
  • Steps 316-317 If the TNAN receives the DHCPv6 (Release 6) request message or the DHCPv4 (Release 4) discovery message, the IP address allocation process is performed, and the TNAN discovers the UE according to the DHCPv6 request message or the DHCPv4 discovery message.
  • the MAC address finds the corresponding IP address, and carries the IP address to the DHCPv6 reply message or the DHCPv4 acknowledgement message. UE.
  • Manner 2 The EAP authentication message triggers the TNAN to create a session.
  • the session allocates an IP address for the UE delay, but carries the APN to the P-GW.
  • Steps 311-312 After receiving the EAP-SUCCESS message, the TNAN initiates a request message for creating a session to the P-GW, and carries a delayed allocation IP address indication for notifying the P-GW to delay assigning an IP address to the UE;
  • the APN requested by the UE is sent to the P-GW, and the S2a session is established with the P-GW.
  • the P-GW does not carry the IP address of the UE in the Create Session Response message according to the indication carried in the Create Session Request message.
  • the TNAN locally stores the association between the UE MAC address and the core network session.
  • the P-GW locally saves the association between the core network session and the APN.
  • Steps 313-315 If the TNAN receives the route request message, the TNAN finds the corresponding core network session identifier according to the UE MAC address therein, and the TNAN requests the P-GW to allocate an IP address through the newly constructed route request message, where, the P-GW The locally saved APN can be found through the core network session identifier, and the IPv6 address assigned to the UE is returned.
  • the TNAN sends a route response message to the UE, where the P-GW carries the IPv6 address allocated by the UE.
  • the P-GW locally stores the association between the UE IP address and the core network session identifier.
  • the TNAN network element After receiving the route request or the route advertisement message, the TNAN network element generates a new route request or a route advertisement message and parses the message to the P-GW network element, which carries the associated core network session identifier. It should be emphasized that the TNAN network element is not used as a relay forwarding route request or route advertisement message.
  • Steps 316-317 If the TNAN receives the DHCPv6 request message or the DHCPv4 discovery message, the process of performing IP address allocation is performed, and after receiving the DHCPv6 request message or the DHCPv4 discovery message, the TNAN network element acts as a DHCP relay, and receives the The associated core network session identifier is added to the DHCPv6 request message or the DHCPv4 discovery message, and the message is forwarded to the P-GW.
  • the P-GW acts as a DHCP server and implicitly supports IPv6 or IPv4 information according to the DHCP message, and allocates IPv6 or UE to the UE.
  • the IPv4 address is returned to the UE by the DHCPv6 reply or the DHCPv4 acknowledgment message, and the message flow between the TNAN and the P-GW is as shown in steps 315a0, 315al and 316a.
  • the P-GW locally stores the association between the UE IP address and the core network session identifier.
  • IPv6 addresses are sufficient, the method of delaying the allocation of IP addresses may be rarely used.
  • IPv4 addresses are relatively lacking, so the method of delaying the allocation of IP addresses may be adopted for IPv4 addresses.
  • Manner 3 The EAP authentication message triggers the TNAN to create a session.
  • the session does not assign an IP address to the UE and does not carry the APN to the P-GW.
  • Steps 311-312 After receiving the EAP-SUCCESS message, the TNAN initiates a process of creating a session to the P-GW, where the TNAN does not carry the APN requested by the UE, but establishes an S2a session with the P-GW, and the P-GW is not the UE. Assign an IP address.
  • the TNAN locally stores the association relationship between the UE MAC address, the APN, and the core network session.
  • Steps 313-315 If the TNAN receives the route request message, the TNAN according to the UE therein The MAC address finds the corresponding APN information. The TNAN carries the APN information through the newly constructed route request message, and requests the P-GW to allocate an IP address, and the P-GW returns the IPv6 address allocated for the UE. The TNAN sends a route response message to the UE, where the P-GW carries the IPv6 address allocated by the UE. For message interaction between the TNAN and the P-GW, see steps 314a0 and 314al.
  • Steps 316-317 If the TNAN receives the DHCPv6 request message or the DHCPv4 discovery message, the process of performing the IP address allocation is performed. After receiving the DHCPv6 request message or the DHCPv4 discovery message, the TNAN network element acts as a DHCP relay and adds the APN information. The message that adds the APN information is forwarded to the P-GW, and the P-GW acts as a DHCP server, and implicitly supports IPv6 or IPv4 information according to the DHCP message, allocates an IPv6 or IPv4 address to the UE, and replies with a DHCPv6 reply or a DHCPv4 acknowledgement message. The allocated IPv6 or IPv4 address is returned to the UE. The message interaction between the TNAN and the P-GW is shown in steps 315a0, 315al and 316a. The P-GW locally stores the association between the UE IP address and the core network session identifier.
  • Mode 3 is applicable not only to IPv6 but also to IPv4. For details, see Mode 2.
  • the TNAN carries the APN requested by the UE to the AAA in the EAP-RES/Identity message, and then the AAA carries the APN requested by the UE to the HSS in the Request Profile message, and the HSS determines not according to the received APN information. Send the default APN to AAA.
  • steps 302-317 are performed when each PDN is connected.
  • the EAP authentication message supports the carrying of the APN requested by the UE to the TNAN, and the TNAN decides whether to support the APN carrying the UE request to the EPC; the routing request message or the DHCP message triggers the TNAN to create a GTP/PMIP session to the P-GW.
  • the process shown in Figure 4. The process includes the following steps:
  • Steps 401-410 Same as steps 301-310.
  • the TNAN After the EAP authentication succeeds, the TNAN locally stores the association between the UE MAC and the APN. Steps 411 - 414: If the TNAN receives the route request message, the TNAN finds the corresponding APN according to the UE MAC address, and the TNAN requests the P-GW to allocate an IP address by creating a session request message, where the create session request message carries the APN information. The P-GW returns the IPv6 address assigned to the UE. The TNAN sends a route response message to the UE, where the P-GW carries the IPv6 address allocated by the UE. The P-GW locally stores the association between the UE IP address and the core network session identifier.
  • Steps 415-419 If the TNAN receives the DHCPv6 request message or the DHCPv4 discovery message, the TNAN finds the APN corresponding to the received message according to the UE MAC address, and the TNAN requests the P-GW to allocate an IP address by creating a session request message.
  • the Create Session Request message carries the APN information, and the P-GW returns an IPv6 or IPv4 address allocated for the UE.
  • the TNAN returns the allocated IPv6 or IPv4 address to the UE through a DHCPv6 reply or a DHCPv4 acknowledgement message.
  • the P-GW locally stores the UE IP address and the core network session identifier. connection relation.
  • the UE does not carry the APN information to the TNAN in the EAP authentication process, but carries the UE capability indication.
  • the TNAN decides the final capability indication according to the local capability indication and the UE capability indication, and the TNAN establishes a dedicated bearer with the P-GW to delete the default bearer. For details, see the process shown in Figure 5. The process includes the following steps:
  • Step 501 The UE and the TNAN network element perform a non-3GPP specific process.
  • Steps 502-510 The TNAN acts as an EAP Authenticator and triggers an EAP authentication process to the UE.
  • the UE carries the UE capability indication to the TNAN in the EAP-RES/Identity message.
  • the TNAN negotiates the UE capability indication according to the UE capability indication carried by the UE and the locally allowed UE capability indication.
  • the specific negotiation principles are as follows:
  • the negotiated UE capability indication does not support the UE to carry the APN; if the UE capability indication carried by the UE is not supported by the UE, The APN is carried, but the TNAN locally supports the message that the UE carries the APN. Then, the negotiated UE capability indication is that the UE does not support the APN.
  • the UE capability indication may also be expressed in other forms, but the meaning of the expression should be the same as that achieved by the above description.
  • the TNAN locally stores the association relationship between the IMSI and the negotiated UE capability indication, and carries the negotiated UE capability indication to the UE in the EAP-REQ/AKA'-Challenge message.
  • the scheme for how the UE obtains the IP address includes the following methods: Mode 1: The EAP authentication message triggers the TNAN to create a session, and the session allocates an IP address to the UE.
  • Steps 511-512 After receiving the EAP-SUCCESS message, the TNAN initiates a process of creating a session to the P-GW.
  • the TNAN carries the subscribed default APN to the P-GW in the Create Session Request message, and the P-GW allocates IP to the UE. Address, and possibly a timer, which is the default timer.
  • the TNAN locally stores the assigned IP address, which may specifically include an IPv4 and/or IPv6 address prefix.
  • the session established between the TNAN and the P-GW is the default bearer.
  • the TNAN distinguishes the received subsequent IP address request message according to the negotiated UE capability indication, as follows:
  • the TNAN locally allocates the corresponding IP address to the UE according to the received routing request message or the DHCPv6 request, or the DHCPv4 discovery message.
  • the route request message or the DHCP message needs to be extended to support carrying the APN information. Since the route request message belongs to a part of the route discovery mechanism and is a broadcast message, it may not be suitable for enhancement; therefore, the extended DHCPv6 request message is prioritized, and of course, the possibility of extending the route request message is not excluded.
  • the invention extends the DHCP message to For example, to illustrate the subsequent processing, see steps 513-516.
  • Step 513 The UE may determine whether to send a route request message according to the negotiated capability indication. For example, if the negotiated UE capability indication is that the UE supports carrying the APN information, the UE does not send the route request message.
  • the UE does not perform the judgment of whether to send the route request message, and always sends the route request message.
  • the negotiated UE capability indication is that the UE supports carrying the APN information
  • the TNAN directly discards the received route request. Message.
  • Steps 514-516 If the TNAN receives the DHCPv6 request message or the DHCPv4 discovery message, the TNAN initiates a create session request message, which carries the APN information, requests the P-GW to allocate an IP address, and the P-GW returns the IP address assigned to the UE to the TNAN.
  • the IP address can be an IPv6 or IPv4 address.
  • Steps 517-519 If the default timer expires and the default bearer still has no data, the P-GW initiates a delete bearer request to the TNAN, and the TNAN replies to the P-GW to delete the bearer response message, indicating that the default bearer has been deleted. .
  • the TNAN sends a delete bearer command to the P-GW to notify the P-GW to delete the default bearer, and then the P-GW sends the DHCPv6 request message or the DHCPv4 discovery message.
  • the TNAN initiates the delete bearer request, and the TNAN replies to the P-GW with the delete bearer response message, indicating that the default bearer has been deleted.
  • Steps 520-521 After receiving the Create Session Response message, the TNAN obtains an IPv6 or IPv4 address, and sends a DHCPv6 advertisement or a DHCPv4 providing message to the UE.
  • the DHCPv6 advertisement or the DHCPv4 providing message may include an IP allocated by the P-GW to the UE. address.
  • the UE sends a DHCP request message to the P-GW; the P-GW returns the assigned IPv6 or IPv4 address to the UE through a DHCPv6 reply or a DHCPv4 acknowledge message.
  • Manner 2 The EAP authentication message triggers the TNAN to create a session. The session does not assign an IP address to the UE.
  • step 511-512 during the process of establishing a session between the TNAN and the P-GW, if the P-GW does not assign an IP address to the UE, the TNAN does not need to locally save the IP address.
  • the TNAN passes the DHCP relay or other manner according to the received routing request message or the DHCPv6 request message, or the DHCPv4 discovery message (refer to step 314a0-314al of Embodiment 1 for details). Steps 315a0-315al, 316a), requesting the P-GW to allocate an IP address, and the P-GW returns an IPv6 address assigned to the UE.
  • the TNAN sends a route response message to the UE, where the P-GW carries the IPv6 address allocated by the UE.
  • Step 513-521 If the negotiated UE capability indication is that the UE supports carrying the APN information, go to Step 513-521.
  • Method 3 DHCP message triggering TNAN to create a session
  • Steps 511-512 The process related to the default bearer establishment and deletion is not performed, and includes: Steps 511-512, Steps 517-519. Steps 513-516 and steps 520-521: This step is performed, and the details are the same as before.
  • Example 4 The process related to the default bearer establishment and deletion is not performed, and includes: Steps 511-512, Steps 517-519. Steps 513-516 and steps 520-521: This step is performed, and the details are the same as before.
  • Example 4 The process related to the default bearer establishment and deletion is not performed, and includes: Steps 511-512, Steps 517-519. Steps 513-516 and steps 520-521: This step is performed, and the details are the same as before.
  • Example 4 The process related to the default bearer establishment and deletion is not performed, and includes: Steps 511-512, Steps 517-519. Steps 513-516 and steps 520-521: This step is performed, and the details are the same as before.
  • Example 4
  • the TNAN still retains the default bearer while establishing a dedicated bearer with the P-GW.
  • the process includes the following steps:
  • Steps 601-613 Same as step 501-513.
  • Steps 614-616 If the TNAN receives the DHCPv6 request message or the DHCPv4 discovery message, the TNAN initiates a create session request message, where the APN information is carried, the P-GW is requested to allocate an IP address, and the P-GW returns an IP address assigned to the UE to the TNAN.
  • the IP address can be an IPv6 or IPv4 address.
  • Steps 617-618 After receiving the Create Session Response message, the TNAN obtains an IP address, and sends a DHCPv6 advertisement or a DHCPv4 providing message to the UE.
  • the DHCPv6 advertisement or the DHCPv4 providing message may include an IP address allocated by the P-GW to the UE. The default IP address.
  • the UE sends a DHCP request message to the P-GW; the P-GW returns the assigned IPv6 or IPv4 address to the UE through a DHCPv6 reply or a DHCPv4 acknowledge message.
  • the method for obtaining the IP address by the UE mainly includes the first mode and the second mode in the third embodiment.
  • the TNAN first carries the capability indication supported by the network to the UE, and the UE determines the final capability indication according to the capability indication of the capability and the capability indication supported by the network.
  • the TNAN first carries the capability indication supported by the network to the UE, and the UE determines the final capability indication according to the capability indication of the capability and the capability indication supported by the network.
  • Step 701-707 Same as step 401-407, the difference is that the UE does not send the UE capability indication to the TNANo.
  • Step 708 The TNAN carries the capability indication of the network support to the UE in the EAP-REQ/AKA, -Challenge message.
  • the UE negotiates the UE capability indication according to the capability indication supported by the TANA network and the locally supported UE capability indication.
  • Step 709 The UE carries the negotiated UE capability indication to the TNAN in the EAP-RES/AKA'-Challenge message sent to the TNAN. Since the UE is an untrusted device, the TNAN checks whether the negotiated UE capability indication is within the allowed range indication of the network support. For example, the negotiated UE capability indication is to support carrying the APN, but the network does not support the UE to carry. If the negotiated UE capability indication is not within the capability indication of the network support, and the EAP authentication is still considered successful, step 710 is performed.
  • the TNAN is processed according to the manner in which the UE does not support the carrying of the APN, and the eNB is configured to ignore the UE capability indication that is requested by the UE that is carried in the DHCP message.
  • the following steps 711-718 refer to the corresponding processing of the three modes in Embodiment 2, Example 6
  • the capability indications of the UE and the network side are learned through negotiation. If the UE first requests an IPv4 address, the capability indication is negotiated through a DHCPv4 message.
  • the specific capability indication and the negotiation principle refer to the related description of Embodiment 3. If the UE and the network side support the UE to carry the requested APN, the specific process can be seen in Figure 8. The process includes the following steps:
  • Steps 801-804 Same as step 301-310, the difference is that the capability indication is not negotiated in the EAP authentication process.
  • Steps 805-812 If the TNAN receives the DHCPv4 discovery message, the TNAN decides whether the UE is allowed to carry the APN requested by the UE according to the local capability indication and the APN requested by the UE carried in the DHCPv4 discovery message. If allowed, a session creation request message is initiated, in which the APN information is carried, the P-GW is requested to allocate an IP address, and the P-GW returns an IP address assigned to the UE to the TNAN.
  • a session creation request message is initiated, in which the APN information is carried, the P-GW is requested to allocate an IP address, and the P-GW returns an IP address assigned to the UE to the TNAN.
  • the TNAN performs the following processing for the IPv6 network scenario: If the TNAN decides to allow the UE to carry the APN requested by the UE, the following processing is performed: Step 813: If the route request message is received, the TNAN discards the Route request message. Step 814-817: If the TNAN receives the DHCPv6 request message, the TNAN initiates a create session request message, where the APN information is used to request the P-GW to allocate an IP address; and the P-GW returns an IP address assigned to the UE to the TNAN.
  • the TNAN decides not to allow the UE to carry the APN requested by the UE, the following processing is performed:
  • the TNAN If the TNAN receives the route request message or the DHCPv6 request message, the TNAN requests the P-GW to allocate an IP address, and returns the assigned IP address to the UE.
  • the specific processing is the same as the processing of the APN information that the UE does not carry the request.
  • the difference from the embodiment 6 is that if the network side does not support the UE to carry the requested APN, refer to the process shown in FIG. 9 , and the process includes the following steps:
  • Steps 901-904 Same steps 801-804.
  • Step 905-907 If the TNAN receives the DHCPv4 discovery message, the TNAN decides whether to allow the UE to carry the requested APN information according to the local capability indication and the APN requested by the UE carried in the received DHCPv4 discovery message. If not allowed, the TNAN carries a specific cause value in the DHCP negative acknowledgement message, indicating that the APN information carrying the request is not supported by the UE.
  • Step 908 After receiving the DHCP negative acknowledgement message, the UE resends the DHCP discovery message, which does not carry the requested APN information.
  • Steps 909-911 The UE obtains the assigned IP address through the DHCP process.
  • the route request message or the DHCPv6 request message may be sent according to the foregoing network capability indication.
  • the specific processing is the same as the process in which the UE does not carry the requested APN information, as follows:
  • Steps 912-914 If the route request message is received, the TNAN requests the P-GW to allocate an IPv6 address, and sends a route advertisement message to the UE, where the route advertisement message includes an IPv6 address allocated by the P-GW to the UE.
  • Step 915 If the DHCPv6 request message is received, the TNAN requests the P-GW to allocate an IPv6 address, and sends a DHCPv6 acknowledgment message to the UE.
  • the DHCPv6 acknowledgment message includes the IPv6 address allocated by the P-GW to the UE.
  • the UE first sends a route request message, and the capability indication of the network is notified to the UE by using a route advertisement message.
  • the process includes the following steps: Steps 1001-1004: Same steps as 801-804.
  • Step 1005 If the TNAN receives the route request message, the TNAN decides whether to allow the UE to carry the requested APN information according to the local capability indication.
  • the specific treatment is as follows:
  • step 1006 If allowed, see step 1006:
  • Step 1006 The TNAN directly sends a route advertisement message to the UE, where the capability indicator of the network is carried, and the APN information supporting the UE to carry the request is indicated.
  • Step 1007-1009 The TNAN requests the P-GW to allocate an IP address, and returns the assigned IP address to the UE.
  • the specific processing is the same as the processing in which the UE does not carry the requested APN information.
  • the UE determines whether to allow the UE to carry the requested APN according to the capability indication of the network and whether it supports the APN carrying the request, and performs specific difference processing according to the decision result. :
  • the route request message may be sent immediately or after a period of time, and the TNAN receives the route request message again, and the process is the same as step 1007-1009.
  • the UE may also send a DHCPv6 request message, where the requested APN is not carried, and the specific processing is the same as the process in which the UE does not carry the requested APN.
  • the UE If the UE supports the APN carrying the request, it sends a DHCPv6 request message, which carries the requested APN. See steps 1010-1017, and the specific processing is the same as step 814-817.
  • the UE first sends a DHCPv6 request message.
  • a DHCPv6 request message For the specific processing, refer to the processing of steps 805-812 in Embodiment 6, or the processing of steps 905-911 in Embodiment 7.
  • the GTP tunnel is established between the non-3GPP access network element and the P-GW.
  • the foregoing embodiment is also applicable to the establishment of the PMIP tunnel, as long as the corresponding message replacement is performed, for example: using a proxy Binding update message replaces create session request message, confirm with proxy binding The message replacement creates a session response message.
  • the parameters that need to be transmitted between the non-3GPP access network element and the P-GW in the GTP tunnel are also applicable to the PMIP message, and specifically include: the APN requested by the UE.
  • IPv6 address received by the UE may also be an IPv6 prefix.
  • the operation of the present invention by using a non-3GPP access core network can represent the process shown in FIG. 11, and the process includes the following steps:
  • Step 1101 Obtain capability information of the UE and/or capability information of the non-3GPP access system.
  • Step 1102 Determine, according to the learned capability information, whether the UE is allowed to deliver the information required to establish an EPC session.
  • the non-3GPP access system may be a trusted non-3GPP access system or an untrusted non-3GPP access system.
  • FIG. 12 is a system diagram of accessing a core network through a non-3GPP according to an embodiment of the present invention, where the system includes a connected capability information learning unit and an enhanced information decision unit.
  • the capability information obtaining unit may be set in the UE, or may be set in a non-3GPP access network (trusted or untrusted) such as a non-3GPP access network; of course, it may also be set in other communication functions such as a 3GPP access system.
  • a non-3GPP access network trusted or untrusted
  • 3GPP access system 3GPP access system
  • the enhanced information decision unit may be set in the UE, or may be set in a non-3GPP access network (trusted or untrusted) such as a non-3GPP access network; of course, it may also be set in 3GPP.
  • a non-3GPP access network trusted or untrusted
  • the access system it is determined whether the UE is allowed to transmit the information required to establish an EPC session.
  • the enhanced information decision unit is further configured to send, to the UE, a decision result of whether to allow the UE to transmit information required to establish an EPC session.
  • the enhanced information decision unit determines that the UE is allowed to pass the information required to establish an EPC session; the enhanced information decision unit is further configured to:
  • the APN requested by the UE is delivered to the EPC.
  • the APN information is used to implicitly indicate the capability of the UE.
  • the capability information of the UE is carried in an EAP authentication message or a DHCP message.
  • the information required for establishing an EPC session is carried in an EAP authentication message or a DHCP message.
  • the capability information of the UE is: an APN requested by the UE, or a capability indication of the UE; and the capability information of the non-3GPP access system is: a capability indication local to the non-3GPP access system;
  • the information required to establish an EPC session is: The requested APN.
  • the capability information obtaining unit is disposed in the UE or the non-3GPP access system,
  • the enhanced information decision unit is disposed in a UE or a non-3GPP access system.
  • the present invention can be accessed by non-3GPP, whether it is a method, a device or a system.
  • the technology of the core network can enhance the capabilities of the UE to support the establishment of additional PDN connections and the continuity of services when accessing the inter-system handover.
  • the UE and the network can sense the capabilities of the peers, so the network can simultaneously support the existing Normal access of the UE and the enhanced UE.

Landscapes

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

Abstract

本发明公开了一种通过非3GPP接入核心网的方法、装置和系统，可获知UE的能力信息和/或非3GPP接入系统的能力信息，并根据获知的所述能力信息，决策是否允许 UE传递建立EPC会话所需的信息。本发明能够增强UE的能力以支持额外的PDN连接的建立，以及接入系统间切换时的业务连续性；同时，通过UE和网络能感知对端的能力，因此网络可以同时支持现有的UE和增强后的UE的正常接入。

Description

一种通过非 3GPP接入核心网的方法、 装置和系统
技术领域 本发明涉及通信领域， 具体涉及一种通过非第三代合作伙伴计划 （3rd Generation Partnership Project, 3 GPP )接入核心网的方法、 装置和系统。 背景技术
3GPP的演进的分组系统（ Evolved Packet System, EPS )由演进的通用 地面无线接入网 ( Evolved Universal Terrestrial Radio Access Network , E-UTRAN )、 移动管理单元 ( Mobility Management Entity, MME )、 月良务网 关 （Serving Gateway, S-GW )、 分组数据网络网关 （Packet Data Network Gateway, P-GW )和归属用户服务器（ Home Subscriber Server, HSS )组成。
EPS支持与非 3GPP系统的互通（如图 1所示）， 其中， 与非 3GPP系 统的互通通过 S2a/b/c接口实现， P-GW作为 3GPP与非 3GPP系统间的锚 点。 在 EPS的系统架构图中， 非 3GPP 系统接入被分为不可信任非 3GPP 接入和可信任非 3GPP接入； 其中， 进行不可信任非 3GPP接入时需经过演 进的分组数据网关（ Evolved Packet Data Gateway, ePDG )与 P-GW相连， ePDG与 P-GW间的接口为 S2b;进行可信任非 3GPP接入时可直接通过 S2a 接口与 P-GW连接， S2a接口采用代理移动因特网协议（ Proxy Mobile IP , ΡΜΙΡ )协议进行信息交互；另外， S2c接口提供了用户设备（ User Equipment , UE )与 P-GW之间的用户面相关的控制和移动性支持， S2c接口支持的移 动性管理协议为支持双栈的移动 IPv6 ( Moblie IPv6 Support for Dual Stack Hosts and Routers, DSMIPv6 ), 可用于不可信任非 3GPP和可信任非 3GPP 接入。
无线局域网络（Wireless Local Area Network, WLAN )可以作为非 3GPP 系统接入演进的分组核心网（Evolved Packet Core, EPC ), 可以支持上述三 种接口， 包括： S2a、 S2b、 S2c。 目前， 对于 S2b、 S2c接口的流程和策略 互通的研究很多。
随着 WLAN作为可信任的非 3GPP系统接入 EPC这种方式逐渐被运营 商接受， S2a接口的流程细化和策略互通问题开始被研究。 首先， 研究了如 何触发 S2a会话建立， 且不需要增强现有 UE的功能。 如图 2所示， UE完 成非 3GPP特有的流程以及可扩展的认证协议 ( Extensible Authentication Protocol, EAP )认证流程之后， UE 和可信任的非 3GPP接入网 （trusted non-3 GPP IP access network, TNAN ) 网元之间执行 L3消息。 TNAN收到 L3消息之后， 向移动核心网络的 P-GW发起 S2a会话建立的流程。 除了 L3 消息外， L2消息同样也能作为一种触发方式， 比如： EAP消息。 以上的 S2a 会话建立的触发方式被讨论， 且基本被接受。
目前， UE不支持传递接入点名称（Access Point Name, APN ), 分组 数据网络 （Packet Data Network , PDN )类型等信息， 但这些信息是 3GPP EPC建立 S2a会话或者为 UE分配 IP地址所需要的关键信息， 比如： 如果 无法获知 APN信息，无法为 UE建立额外的 PDN连接；如果无法获知 PDN 类型， P-GW则不能感知 UE要请求的 IP地址类型， 只能根据签约的 IP地 址类型来分配 IP地址， 而这种分配方式容易引起 IP地址资源浪费。 另外， 在从 3GPP接入切换到非 3GPP接入时， UE不能将需要保留 UE IP地址的 信息传递给 EPC, 无法保证业务连续性。 发明内容 有鉴于此，本发明的主要目的在于提供一种通过非 3GPP接入核心网的 方法、 装置和系统， 获知 UE的能力， 决策是否支持额外的 PDN连接的建 立， 以及接入系统间切换时的业务连续性。
为达到上述目的， 本发明的技术方案是这样实现的：
一种通过非第三代合作伙伴计划 3GPP接入核心网的方法， 包括： 用户设备 UE发送 UE的能力信息后， 接收是否允许 UE传递建立演进 的分组核心网 EPC会话所需的信息的决策结果；
UE根据所述决策结果， 决定是否传递建立 EPC会话所需的信息。 其中， 所述 UE的能力信息， 携带于可扩展的认证协议 EAP认证消息 或者动态主机配置协议 DHCP消息中。
一种通过非第三代合作伙伴计划 3GPP接入核心网的方法， 包括： 获知用户设备 UE的能力信息和 /或非 3GPP接入系统的能力信息； 根据获知的所述能力信息， 决策是否允许 UE传递建立 EPC会话所需 的信息。
其中， 获知所述能力信息的操作由 UE或非 3GPP接入系统执行。
其中， 所述决策由非 3GPP接入系统做出时， 则非 3GPP接入系统将是 否允许 UE传递建立 EPC会话所需的信息的决策结果发送给 UE。
其中， 进行所述决策后， 确定允许 UE传递建立 EPC会话所需的信息， 该方法还包括：
非 3GPP接入系统在收到 UE携带的所请求的 APN后， 向 EPC传递 UE请求的 APN。
其中， 所述 APN信息， 用于隐式表示 UE的能力。
其中， 所述 UE的能力信息， 携带于可扩展的认证协议 EAP认证消息 或者动态主机配置协议 DHCP消息中； 建立 EPC会话所需的所述信息，携带于 EAP认证消息或者 DHCP消息 中。
其中， 所述 UE的能力信息为： UE请求的 APN,或者 UE的能力指示； 建立 EPC会话所需的所述信息为： 所请求的 APN。
其中， 所述非 3GPP接入系统的能力信息为： 非 3GPP接入系统本地的 能力指示。
其中， 进行所述决策的通信实体为 UE, 或者非 3GPP接入系统。
一种通过非 3GPP接入核心网的系统， 包括能力信息获知单元、增强信 息决策单元； 其中，
所述能力信息获知单元， 用于获知 UE的能力信息和 /或非 3GPP接入 系统的能力信息；
所述增强信息决策单元， 用于根据所述能力信息获知单元所获知的所 述能力信息， 决策是否允许 UE传递建立 EPC会话所需的信息。
其中， 所述增强信息决策单元还用于将是否允许 UE传递建立 EPC会 话所需的信息的决策结果发送给 UE。
其中，进行所述决策后，所述增强信息决策单元确定允许 UE传递建立 EPC会话所需的信息； 所述增强信息决策单元还用于：
在收到 UE携带的所请求的 APN后， 向 EPC传递 UE请求的 APN。 其中， 所述 APN信息， 用于隐式表示 UE的能力。
其中，所述 UE的能力信息，携带于 EAP认证消息或者 DHCP消息中； 建立 EPC会话所需的所述信息，携带于 EAP认证消息或者 DHCP消息 中。
其中， 所述 UE的能力信息为： UE请求的 APN,或者 UE的能力指示； 建立 EPC会话所需的所述信息为： 所请求的 APN。
其中， 所述能力信息获知单元设置于 UE或者非 3GPP接入系统中， 所述增强信息决策单元设置于 UE或者非 3GPP接入系统中。
一种通过非 3GPP接入核心网的装置， 该装置为 UE, 用于在发送 UE 的能力信息后， 接收是否允许 UE传递建立 EPC会话所需的信息的决策结 果； 以及根据所述决策结果， 决定是否传递建立 EPC会话所需的信息。
其中，所述 UE的能力信息，携带于可扩展的 EAP认证消息或者 DHCP 消息中。
本发明方法、 装置和系统能够增强 UE的能力以支持额外的 PDN连接 的建立， 以及接入系统间切换时的业务连续性； 同时， 通过 UE和网络能感 知对端的能力， 因此网络可以同时支持现有的 UE和增强后的 UE的正常接 入。 附图说明 图 1为现有技术中 3GPP网络与非 3GPP网络互通的网络结构图； 图 2为现有技术中 UE通过可信任的 WLAN接入 EPC的流程图； 图 3为本发明一实施例中， UE在 EAP认证消息中携带 UE请求的 APN 的流程图；
图 4为本发明另一实施例中， UE在 EAP认证消息中携带 UE请求的 APN的流程图；
图 5为本发明一实施例中，UE在 EAP认证消息中携带 UE能力指示的 流程图；
图 6为本发明另一实施例中， UE在 EAP认证消息中携带 UE能力指示 的流程图；
图 7为本发明中， TNAN在 EAP认证消息中携带网络支持的能力指示 的流程图；
图 8为本发明一实施例中， TNAN在 L3消息中携带网络支持的能力指 示的流程图；
图 9为本发明另一实施例中， TNAN在 L3消息中携带网络支持的能力 指示的流程图；
图 10为本发明又一实施例中， TNAN在 L3消息中携带网络支持的能 力指示的流程图；
图 11为本发明实施例中， 通过非 3GPP接入核心网的流程简图； 图 12为本发明实施例中， 通过非 3GPP接入核心网的系统图。 具体实施方式 在实际应用中， 可以获知 （直接获取或隐式获知） UE 的能力信息和 / 或非 3GPP接入系统的能力信息； 并根据获取的能力信息， 决策是否允许 UE携带 EPC需要的增强信息， 即决策是否允许 UE传递建立 EPC会话所 需的信息。
所述非 3GPP接入系统可以是可信任的非 3GPP接入系统，也可以是不 可信任的非 3GPP接入系统，下面仅以可信任的非 3GPP接入系统为例进行 描述。
需要说明的是， 进行所述决策的通信实体可以为 UE, 或者非 3GPP接 入系统；
UE携带的能力信息可以为： UE请求的 APN, 或者 UE的能力指示；
UE携带请求的 APN信息， 可以隐式表示 UE的能力；
非 3GPP接入系统的能力信息可以为：非 3GPP接入系统本地的能力指 示；
UE携带的增强信息可以为： 所请求的 APN; 如果决策后允许 UE携带增强信息， 非 3GPP接入系统在收到 UE携带 的所请求的 APN后， 会向 EPC传递 UE请求的 APN; 如， 向 P-GW传递 UE请求的 APN。
如果所述决策由非 3GPP接入系统做出，则非 3GPP接入系统会将是否 允许 UE携带增强信息的决策结果发送给 UE;
UE的能力信息，可以通过 EAP认证消息或者 DHCP (动态主机配置协 议） 消息携带；
UE的增强信息， 可以通过 EAP认证消息或者 DHCP消息携带。
下面结合附图及实施例， 对本发明进行详细描述。
实施例 1
该实施例中， UE通过可信任的非 3GPP接入 EPC时， EAP认证消息支 持携带 UE请求的 APN给 TNAN , TNAN决策是否支持携带 UE请求的 APN 给 EPC。 EAP认证消息触发 TNAN向 P-GW创建 GTP/PMIP会话。 具体可 参见如图 3所示流程， 该流程包括以下步驟：
步驟 301 : UE与 TNAN网元执行非 3GPP特有的流程， 比如： 链路建 立、 接入认证等；
步驟 302-310: TNAN作为 EAP认证者 , 会向 UE触发 EAP认证流程。 其中， UE在 EAP-RES/Identity消息中携带 UE请求的 APN给 TNAN。并且 , TNAN根据 UE携带的请求的 APN和本地的策略， 决策是否允许 UE携带 请求的 APN, 具体为： 如果 TNAN支持 UE携带请求的 APN, 则继续后续 流程； 否则，后续操作与现有技术中的 UE不携带请求的 APN的流程相同， 对于 UE如何获取 IP地址的方案， 具体包括几种方式， 如下： 方式一： EAP认证消息触发 TNAN创建会话， 该会话会为 UE分配 IP 地址。
步驟 311-312: TNAN收到 EAP-SUCCESS消息之后， 忽略收到的缺省 的 APN, 会向 P-GW发起创建会话的流程， TNAN携带 UE请求的 APN给 P-GW, 并与 P-GW建立 S2a会话， P-GW为 UE分配 IP地址， 并将该 IP 地址返回给 TNAN, TNAN本地保存这些 IP地址，所述 IP地址具体可能包 括 IPv4和 /或 IPv6地址。 TNAN本地保存 UE MAC地址和 IP地址的关联关 系。
步驟 313-315: 如果 TNAN收到路由请求消息， TNAN根据其中的 UE MAC地址找到对应的 IP地址， TNAN发送路由响应消息给 UE , 其中携带 P-GW为 UE分配的 IPv6地址。
步驟 316-317:如果 TNAN收到 DHCPv6(版本 6 )请求消息或者 DHCPv4 (版本 4 )发现消息， 则执行 IP地址分配的流程， TNAN根据收到的所述 DHCPv6请求消息或者 DHCPv4发现消息中的 UE MAC地址找到对应的 IP 地址，并通过 DHCPv6的答复消息或者 DHCPv4的确认消息携带 IP地址给 UE。
方式二： EAP认证消息触发 TNAN创建会话， 该会话为 UE延迟分配 IP地址， 但携带 APN给 P-GW。
步驟 311-312: TNAN收到 EAP-SUCCESS消息之后， 会向 P-GW发起 创建会话的请求消息，同时携带一个延迟分配 IP地址指示，用于通知 P-GW 延迟为 UE分配 IP地址； TNAN携带 UE请求的 APN给 P-GW,并与 P-GW 建立 S2a会话， P-GW根据创建会话请求消息中携带的指示，在创建会话响 应消息中不携带 UE的 IP地址。 TNAN本地保存 UE MAC地址和核心网会 话的关联关系。 P-GW本地保存核心网会话和 APN的关联关系。
步驟 313-315: 如果 TNAN收到路由请求消息， TNAN根据其中的 UE MAC地址找到对应的核心网会话标识 , TNAN通过新构造的路由请求消息 向 P-GW请求分配 IP地址， 其中， P-GW可以通过核心网会话标识找到本 地保存的 APN, 返回为 UE分配的 IPv6地址。 并且， TNAN发送路由响应 消息给 UE, 其中携带 P-GW为 UE分配的 IPv6地址。 P-GW本地要保存 UE IP地址和核心网会话标识的关联关系。
其中， TNAN 网元收到路由请求或者路由通告消息时， 本地对这些报 文解析之后， 生成新的路由请求或者路由通告消息并发送给 P-GW网元， 其中携带关联的核心网会话标识。 需要强调的是， TNAN 网元不是作为中 继转发路由请求或者路由通告消息。
步驟 316-317: 如果 TNAN收到 DHCPv6请求消息或者 DHCPv4发现 消息 , 则执行 IP地址分配的流程， TNAN网元收到 DHCPv6请求消息或者 DHCPv4发现消息后， 作为 DHCP中继， 在收到的所述 DHCPv6请求消息 或者 DHCPv4 发现消息中增加关联的核心网会话标识， 并转发该消息给 P-GW, P-GW作为 DHCP服务器， 会根据 DHCP消息隐含支持 IPv6或者 IPv4的信息， 为 UE分配 IPv6或者 IPv4地址， 并通过 DHCPv6答复或者 DHCPv4确认消息将分配的所述 IPv6或者 IPv4地址返回给 UE; TNAN和 P-GW之间的消息流程参见步驟 315a0、 315al和 316a。 P-GW本地要保存 UE IP地址和核心网会话标识的关联关系。
通常情况下， 由于 IPv6地址比较充足， 因此可能很少采用延迟分配 IP 地址的方式； 而 IPv4地址比较缺乏， 因此针对 IPv4地址 4艮可能会采用延迟 分配 IP地址的方式。
方式三： EAP认证消息触发 TNAN创建会话， 该会话不会为 UE分配 IP地址， 且不携带 APN给 P-GW。
步驟 311-312: TNAN收到 EAP-SUCCESS消息之后， 会向 P-GW发起 创建会话的流程， 其中， TNAN不携带 UE请求的 APN, 但与 P-GW建立 S2a会话， P-GW不为 UE分配 IP地址。 TNAN本地保存 UE MAC地址、 APN和核心网会话的关联关系。
步驟 313-315: 如果 TNAN收到路由请求消息， TNAN根据其中的 UE MAC地址找到对应的 APN信息， TNAN通过新构造的路由请求消息中携 带 APN信息， 并向 P-GW请求分配 IP地址， P-GW返回为 UE分配的 IPv6 地址。 并且 , TNAN发送路由响应消息给 UE , 其中携带 P-GW为 UE分配 的 IPv6地址。 TNAN和 P-GW之间的消息交互参见步驟 314a0和 314al。
步驟 316-317: 如果 TNAN收到 DHCPv6请求消息或者 DHCPv4发现 消息 , 则执行 IP地址分配的流程， TNAN网元收到 DHCPv6请求消息或者 DHCPv4发现消息后， 作为 DHCP中继， 在其中增加 APN信息， 并将增加 了 APN信息的消息转发给 P-GW, P-GW作为 DHCP服务器，会根据 DHCP 消息隐含支持 IPv6或者 IPv4的信息， 为 UE分配 IPv6或者 IPv4地址， 并 通过 DHCPv6答复或者 DHCPv4确认消息将分配的所述 IPv6或者 IPv4地 址返回给 UE。 TNAN和 P-GW之间的消息交互参见步驟 315a0、 315al和 316a。 P-GW本地要保存 UE IP地址和核心网会话标识的关联关系。
方式三不仅对 IPv6方式适用，对于 IPv4方式同样适用， 具体描述参见 方式二。
可选地， TNAN在 EAP-RES/Identity消息中， 将 UE请求的 APN携带 给 AAA, 然后由 AAA在 Request Profile消息中将 UE请求的 APN携带给 HSS, HSS根据收到的 APN信息， 决定不发送缺省 APN给 AAA。
如果 UE支持多 PDN连接且每个 APN对应一个 PDN连接， 则在每个 PDN连接时， 都要执行步驟 302-317。
实施例 2
该实施例中 , EAP认证消息支持携带 UE请求的 APN给 TNAN, TNAN 决策是否支持携带 UE请求的 APN给 EPC; 路由请求消息或者 DHCP消息 触发 TNAN向 P-GW创建 GTP/PMIP会话。 具体可参见如图 4所示流程， 该流程包括以下步驟：
步驟 401-410: 同步驟 301-310。
在 EAP认证成功之后， TNAN本地保存 UE MAC和 APN的关联关系。 步驟 411 -414： 如果 TNAN收到路由请求消息， TNAN根据 UE MAC 地址找到对应的 APN, TNAN通过创建会话请求消息 , 向 P-GW请求分配 IP地址， 其中， 创建会话请求消息中携带 APN信息， P-GW返回为 UE分 配的 IPv6地址。 并且， TNAN发送路由响应消息给 UE, 其中携带 P-GW 为 UE分配的 IPv6地址。 P-GW本地要保存 UE IP地址和核心网会话标识 的关联关系。
步驟 415-419: 如果 TNAN收到 DHCPv6请求消息或者 DHCPv4发现 消息， TNAN根据 UE MAC地址找到收到的所述消息所对应的 APN, TNAN 通过创建会话请求消息， 向 P-GW请求分配 IP地址， 其中， 创建会话请求 消息中携带 APN信息， P-GW返回为 UE分配的 IPv6或者 IPv4地址。 并 且， TNAN通过 DHCPv6答复或者 DHCPv4确认消息将分配的所述 IPv6或 者 IPv4地址返回给 UE。 P-GW本地要保存 UE IP地址和核心网会话标识的 关联关系。
实施例 3
该实施例中， UE在 EAP认证流程中不携带 APN信息给 TNAN, 而是 携带 UE能力指示。 TNAN根据本地的能力指示和 UE能力指示， 决策出最 终的能力指示， TNAN与 P-GW建立专有承载， 删除缺省承载。 具体可参 见如图 5所示流程， 该流程包括以下步驟：
步驟 501 : UE与 TNAN网元执行非 3GPP特有的流程；
步驟 502-510: TNAN作为 EAP认证者， 会向 UE触发 EAP认证流程。 其中， UE在 EAP-RES/Identity消息中携带 UE能力指示给 TNAN。 TNAN 会根据 UE携带的 UE能力指示和本地允许的 UE能力指示， 协商出 UE能 力指示。 具体协商原则如下：
如果 UE携带的 UE能力指示为 UE支持携带 APN, 但是 TNAN本地 不支持 UE携带 APN的消息， 那么， 协商出的 UE能力指示为不支持 UE 携带 APN；如果 UE携带的 UE能力指示为 UE不支持携带 APN ,但是 TNAN 本地支持 UE携带 APN的消息， 那么， 协商出的 UE能力指示为不支持 UE 携带 APN。 UE能力指示也可以采用其他形式表示，但表达的意思应该和上 述描述实现的目的相同。
TNAN 本地保存 IMSI 和协商出的 UE 能力指示的关联关系， 并在 EAP-REQ/AKA'-Challenge消息中携带协商出的 UE能力指示给 UE。
对于 UE如何获取 IP地址的方案， 具体包括几种方式， 如下： 方式一： EAP认证消息触发 TNAN创建会话， 该会话会为 UE分配 IP 地址。
步驟 511-512: TNAN收到 EAP-SUCCESS消息之后， 会向 P-GW发起 创建会话的流程， TNAN在创建会话请求消息中携带签约的缺省 APN给 P-GW, P-GW为 UE分配 IP地址， 且可能启用一个定时器， 该定时器是缺 省^^载的定时器。 TNAN本地保存分配的所述 IP地址， 该 IP地址具体可能 包括 IPv4和 /或 IPv6地址前缀。 TNAN和 P-GW之间建立的会话为缺省承 载。
TNAN根据协商出的 UE能力指示， 对接收到的后续 IP地址请求消息 进行区分处理， 具体如下：
1) 如果协商出的 UE能力指示为 UE不支持携带 APN信息， TNAN根 据接收到的路由请求消息或者 DHCPv6请求，或者 DHCPv4发现消 息 , 本地分配相应的 IP地址给 UE。
2) 如果协商出的 UE能力指示为 UE支持携带 APN信息，则路由请求 消息或者 DHCP消息需要扩展参数， 以支持携带 APN信息。 由于 路由请求消息属于路由发现机制的一部分， 并且为广播消息， 因此 可能不适合增强； 因此， 优先考虑扩展 DHCPv6请求消息， 当然， 不排除扩展路由请求消息的可能性。 本发明以扩展 DHCP 消息为 例， 来说明后续的处理， 具体参见步驟 513-516。
步驟 513: UE可以根据协商出的能力指示， 决定是否发送路由请求消 息； 比如： 如果协商出的 UE能力指示为 UE支持携带 APN信息， 则 UE 不发送路由请求消息；
可选地， UE不会进行是否发送路由请求消息的判断， 总是发送路由请 求消息， 这时， 如果协商出的 UE能力指示为 UE支持携带 APN信息， 则 TNAN直接丟弃收到的路由请求消息。
步驟 514-516: 如果 TNAN收到 DHCPv6请求消息或者 DHCPv4发现 消息， TNAN发起创建会话请求消息， 其中携带 APN信息， 向 P-GW请求 分配 IP地址， P-GW向 TNAN返回为 UE分配的 IP地址， 该 IP地址具体 可以为 IPv6或者 IPv4地址。
步驟 517-519: 如果缺省定时器超时， 而缺省承载仍没有数据时， 则 P-GW向 TNAN发起删除承载请求， TNAN向 P-GW回复删除承载响应消 息， 表示已删除该缺省承载。
如果 P-GW没有启用缺省承载定时器， 则 TNAN在收到 DHCPv6请求 消息或者 DHCPv4发现消息时，会向 P-GW发送删除承载命令，通知 P-GW 删除缺省承载， 然后 P-GW向 TNAN发起删除承载请求， TNAN向 P-GW 回复删除承载响应消息， 表示已删除缺省承载。
步驟 520-521： TNAN收到创建会话响应消息后 , 获取 IPv6或者 IPv4 地址， 并发送 DHCPv6通告或者 DHCPv4提供消息给 UE, 所述 DHCPv6 通告或者 DHCPv4提供消息中可包括 P-GW为 UE分配的 IP地址。 然后， UE发送 DHCP请求消息给 P-GW; P-GW通过 DHCPv6答复或者 DHCPv4 确认消息 , 将分配的 IPv6或者 IPv4地址返回给 UE。
方式二： EAP认证消息触发 TNAN创建会话， 该会话不会为 UE分配 IP地址。
在步驟 511-512中， 在 TNAN与 P-GW之间建立会话的过程中， 如果 P-GW没有为 UE分配 IP地址， 则 TNAN不需要本地保存 IP地址。
如果协商出的 UE能力指示为 UE不支持携带 APN信息， TNAN根据 接收到的路由请求消息或者 DHCPv6请求消息， 或者 DHCPv4发现消息， 通过 DHCP relay或者其他方式（具体参见实施例 1的步驟 314a0-314al , 步 驟 315a0-315al、 316a ), 向 P-GW请求分配 IP地址， P-GW返回为 UE分 配的 IPv6地址。 并且， TNAN发送路由响应消息给 UE, 其中携带 P-GW 为 UE分配的 IPv6地址。
如果协商出的 UE 能力指示为 UE 支持携带 APN信息， 执行步驟 513-521。
方式三： DHCP消息触发 TNAN创建会话
与缺省承载建立、 删除相关的流程不执行， 包括： 步驟 511-512、 步驟 517-519。 步驟 513-516和步驟 520-521 : 该步驟执行， 具体描述同前。 实施例 4
该实施例中， TNAN在与 P-GW建立专有承载的同时， 仍然保留缺省 承载。 具体可参见如图 6所示流程， 该流程包括以下步驟：
步驟 601-613: 同步驟 501-513。
步驟 614-616: 如果 TNAN收到 DHCPv6请求消息或者 DHCPv4发现 消息， TNAN发起创建会话请求消息， 其中携带 APN信息， 向 P-GW请求 分配 IP地址， P-GW向 TNAN返回为 UE分配的 IP地址， 该 IP地址具体 可以为 IPv6或者 IPv4地址。
步驟 617-618: TNAN收到创建会话响应消息后， 获取 IP地址， 并发 送 DHCPv6通告或者 DHCPv4提供消息给 UE, 所述 DHCPv6通告或者 DHCPv4提供消息中可包括 P-GW为 UE分配的 IP地址和缺省 IP地址。 然 后， UE发送 DHCP请求消息给 P-GW; P-GW通过 DHCPv6 答复或者 DHCPv4确认消息 , 将分配的 IPv6或者 IPv4地址返回给 UE。
UE获取 IP地址的方法， 主要包括实施例 3中的方式一和方式二。 实施例 5
该实施例中， TNAN首先将网络支持的能力指示携带给 UE, UE根据 本身的能力指示和网络支持的能力指示， 决策出最终的能力指示， 具体能 力指示的定义和协商原则参见实施例 3的相关描述。 具体可参见如图 7所 示流程， 该流程包括以下步驟：
步驟 701-707: 同步驟 401-407, 区别在于 UE不发送 UE能力指示给 TNANo
步驟 708： TNAN在 EAP-REQ/AKA，-Challenge消息中携带网络支持的 能力指示给 UE。
UE会根据 TANA网络支持的能力指示和本地支持的 UE能力指示，协 商出 UE能力指示。
步驟 709: UE在向 TNAN发送的 EAP-RES/AKA'-Challenge消息中， 携带协商出的 UE能力指示给 TNAN。 由于 UE是不可信的设备， TNAN会 检查协商出的 UE能力指示是否在网络支持的能力指示允许范围内， 比如： 协商出的 UE 能力指示为支持携带 APN, 而实际上网络不支持 UE携带 如果协商出的 UE能力指示不在网络支持的能力指示允许范围内 ,仍然 认为 EAP认证是成功的， 执行步驟 710。 在后续的流程中， TNAN按照 UE 不支持携带 APN的方式来处理， 会忽略 DHCP消息中所携带的 UE请求的 如果协商出的 UE能力指示在网络支持的能力指示允许范围内，执行步 驟 710,并且，后面的步驟 711-718参考实施例 2中的三种方式的相应处理， 实施例 6
该实施例中， 在 L3 DHCPv4消息交互流程中， 通过协商以获知 UE和 网络侧的能力指示。 假如 UE先请求 IPv4地址， 通过 DHCPv4消息来协商 能力指示。 具体能力指示的定义和协商原则参见实施例 3 的相关描述。 如 果 UE和网络侧都支持 UE携带请求的 APN , 具体的流程可参见图 8 , 该流 程包括以下步驟：
步驟 801-804: 同步驟 301-310, 区别在于 EAP认证流程中， 不协商能 力指示。
步驟 805-812: 如果 TNAN收到 DHCPv4发现消息， TNAN根据本地 的能力指示以及 DHCPv4发现消息中携带的 UE请求的 APN, 决策是否允 许 UE携带 UE请求的 APN。 如果允许， 则发起创建会话请求消息， 其中 携带 APN信息， 向 P-GW请求分配 IP地址， P-GW向 TNAN返回为 UE 分配的 IP地址。对于 TNAN和 P-GW之间的流程处理参见前面实施例 5的 相关描述。
基于所述决策结果， 针对 IPv6网络场景， TNAN会执行如下处理： 如果 TNAN决策为允许 UE携带 UE请求的 APN,则会进行如下处理： 步驟 813: 如果收到路由请求消息， 则 TNAN丟弃该路由请求消息。 步驟 814-817: 如果 TNAN收到 DHCPv6请求消息， 则 TNAN发起创 建会话请求消息， 其中携带 APN信息， 用于向 P-GW请求分配 IP地址； P-GW向 TNAN返回为 UE分配的 IP地址。
如果 TNAN决策为不允许 UE携带 UE请求的 APN, 则会进行如下处 理：
如果 TNAN收到路由请求消息或者 DHCPv6请求消息 , TNAN向 P-GW 请求分配 IP地址， 并将分配的 IP地址返回给 UE。 具体的处理和 UE不携 带请求的 APN信息的处理相同。
以上描述以针对 DHCPv4的决策结果为例， 该描述与针对 DHCPv6的 决策结果为例的描述相同。
实施例 7
该实施例中， 与实施例 6的区别在于，如果网络侧不支持 UE携带请求 的 APN, 具体可参见如图 9所示的流程， 该流程包括以下步驟：
步驟 901-904: 同步驟 801-804。
步驟 905-907: 如果 TNAN收到 DHCPv4发现消息， 则根据本地的能 力指示以及所收到的 DHCPv4发现消息中携带的 UE请求的 APN, 决策是 否允许 UE携带请求的 APN信息。如果不允许， 则 TNAN在 DHCP否定确 认消息中携带具体原因值， 标明不支持 UE携带请求的 APN信息。
步驟 908: UE收到 DHCP否定确认消息后， 会重新发送 DHCP发现消 息， 其中不携带请求的 APN信息。
步驟 909-911 : UE通过 DHCP流程获取到分配的 IP地址。 当 UE请求 IPv6地址时， 根据上述的网络能力指示， 可以发送路由请 求消息或者 DHCPv6请求消息， 具体的处理和 UE不携带请求的 APN信息 的处理相同， 具体如下：
步驟 912-914: 如果收到路由请求消息， 则 TNAN向 P-GW请求分配 IPv6地址， 并发送路由通告消息给 UE, 该路由通告消息中包含 P-GW为 UE分配的 IPv6地址。
步驟 915: 如果收到 DHCPv6请求消息， 则 TNAN向 P-GW请求分配 IPv6地址， 并发送 DHCPv6确认消息给 UE, 该 DHCPv6确认消息中包含 P-GW为 UE分配的 IPv6地址。
以上描述以针对 DHCPv4的决策结果为例， 该描述与针对 DHCPv6的 决策结果为例的描述相同。
实施例 8
该实施例中， UE先发送路由请求消息， 网络的能力指示是通过路由通 告消息通知 UE的。 具体可参见如图 10所示流程， 该流程包括以下步驟： 步驟 1001-1004: 同步驟 801-804。
步驟 1005: 如果 TNAN收到路由请求消息， TNAN根据本地的能力指 示， 决策是否允许 UE携带请求的 APN信息。 具体处理如下：
如果允许， 参见步驟 1006:
步驟 1006: TNAN直接向 UE回复路由通告消息， 其中携带网络的能 力指示， 标明支持 UE携带请求的 APN信息。
如果不允许， 则 TNAN正常处理路由请求消息， 参见步驟 1007-1009。 步驟 1007-1009: TNAN向 P-GW请求分配 IP地址， 并将分配的 IP地 址返回给 UE。 具体的处理和 UE不携带请求的 APN信息的处理相同。
如果 UE收到路由通告消息， 且其中携带网络的能力指示， UE根据网 络的能力指示以及本身是否支持携带请求的 APN, 决策出是否允许 UE携 带请求的 APN, 并根据决策结果进行具体的区别处理：
如果 UE不支持携带请求的 APN, 可能会立即或者过一段时间发送路 由请求消息， TNAN再次收到路由请求消息， 则处理同步驟 1007-1009。 或 者， UE也可能发送 DHCPv6请求消息， 其中不携带请求的 APN, 具体的 处理和 UE不携带请求的 APN的处理相同。
如果 UE支持携带请求的 APN, 会发送 DHCPv6请求消息， 其中携带 请求的 APN, 参见步驟 1010-1017, 具体处理同步驟 814-817。
实施例 9
该实施例中， UE先发送 DHCPv6请求消息， 其具体的处理参见实施例 6中步驟 805-812的处理， 或者实施例 7中步驟 905-911的处理。
以上实施例 ,在非 3GPP接入网网元和 P-GW之间建立的是 GTP隧道； 当然，上述实施例也适用于 PMIP隧道的建立，只要进行相应的消息替换即 可， 比如： 用代理绑定更新消息替换创建会话请求消息， 用代理绑定确认 消息替换创建会话响应消息， 非 3GPP接入网网元和 P-GW之间在 GTP隧 道需要传递的参数也同样适用于 PMIP消息， 具体包含： UE请求的 APN。
另外， UE接收到的 IPv6地址也可能为 IPv6前缀。
结合以上各实施例可知，本发明通过非 3GPP接入核心网的操作思路可 以表示如图 11所示的流程， 该流程包括以下步驟：
步驟 1101 : 获知 UE的能力信息和 /或非 3GPP接入系统的能力信息。 步驟 1102:根据获知的所述能力信息，决策是否允许 UE传递建立 EPC 会话所需的信息。
所述非 3GPP接入系统可以是可信任的非 3GPP接入系统或是不可信任 的非 3GPP接入系统。
为了保证上述各实施例以及操作思路能够顺利实现， 可以进行如图 12 所示的设置。 参见图 12, 图 12为本发明实施例中， 通过非 3GPP接入核心 网的系统图， 该系统包括相连的能力信息获知单元、 增强信息决策单元。
其中， 能力信息获知单元可以设置于 UE中， 也可以设置于非 3GPP接 入网等非 3GPP接入系统（可信任或不可信任） 中； 当然， 还可以设置于 3GPP接入系统等其它通信功能实体中， 只要能够顺利获知 UE的能力信息 和 /或非 3GPP接入系统的能力信息即可。
与所述能力信息获知单元类似， 增强信息决策单元可以设置于 UE中， 也可以设置于非 3GPP接入网等非 3GPP接入系统（可信任或不可信任）中； 当然，还可以设置于 3GPP接入系统等其它通信功能实体中，只要能够根据 所述能力信息获知单元所获知的能力信息，决策是否允许 UE传递建立 EPC 会话所需的信息即可。
需要说明的是，所述增强信息决策单元还用于将是否允许 UE传递建立 EPC会话所需的信息的决策结果发送给 UE。
进行所述决策后， 所述增强信息决策单元确定允许 UE传递建立 EPC 会话所需的信息； 所述增强信息决策单元还用于：
在收到 UE携带的所请求的 APN后 , 向 EPC传递 UE请求的 APN。 所述 APN信息， 用于隐式表示 UE的能力。
所述 UE的能力信息， 携带于 EAP认证消息或者 DHCP消息中； 建立 EPC会话所需的所述信息，携带于 EAP认证消息或者 DHCP消息 中。
所述 UE的能力信息为： UE请求的 APN, 或者 UE的能力指示； 所述非 3GPP接入系统的能力信息为：非 3GPP接入系统本地的能力指 示；
建立 EPC会话所需的所述信息为： 所请求的 APN。
所述能力信息获知单元设置于 UE或者非 3GPP接入系统中，
所述增强信息决策单元设置于 UE或者非 3GPP接入系统中。
综上所述可见， 无论是方法、 装置还是系统， 本发明通过非 3GPP接入 核心网的技术， 能够增强 UE的能力以支持额外的 PDN连接的建立， 以及 接入系统间切换时的业务连续性；同时，通过 UE和网络能感知对端的能力， 因此网络可以同时支持现有的 UE和增强后的 UE的正常接入。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种通过非第三代合作伙伴计划 3GPP接入核心网的方法， 包括： 用户设备 UE发送 UE的能力信息后， 接收是否允许 UE传递建立演进 的分组核心网 EPC会话所需的信息的决策结果；
UE根据所述决策结果， 决定是否传递建立 EPC会话所需的信息。
2、 根据权利要求 1所述的方法， 其中， 态主机配置协议 DHCP消息中。
3、 一种通过非第三代合作伙伴计划 3GPP接入核心网的方法， 包括： 获知用户设备 UE的能力信息和 /或非 3GPP接入系统的能力信息； 根据获知的所述能力信息， 决策是否允许 UE传递建立 EPC会话所需 的信息。
4、 根据权利要求 3所述的方法， 其中，
获知所述能力信息的操作由 UE或非 3GPP接入系统执行。
5、 根据权利要求 3所述的方法， 其中， 所述决策由非 3GPP接入系统 做出时， 则非 3GPP接入系统将是否允许 UE传递建立 EPC会话所需的信 息的决策结果发送给 UE。
6、 根据权利要求 3 所述的方法， 其中， 进行所述决策后， 确定允许 UE传递建立 EPC会话所需的信息， 该方法还包括：
非 3GPP接入系统在收到 UE携带的所请求的 APN后， 向 EPC传递 UE请求的 APN。
7、 根据权利要求 6所述的方法， 其中， 所述 APN信息， 用于隐式表 示 UE的能力。
8、 根据权利要求 3至 7任一项所述的方法， 其中， 态主机配置协议 DHCP消息中；
建立 EPC会话所需的所述信息，携带于 EAP认证消息或者 DHCP消息 中。
9、 根据权利要求 3至 8任一项所述的方法， 其中，
所述 UE的能力信息为： UE请求的 APN, 或者 UE的能力指示； 建立 EPC会话所需的所述信息为： 所请求的 APN。
10、 根据权利要求 3至 9任一项所述的方法， 其中，
所述非 3GPP接入系统的能力信息为：非 3GPP接入系统本地的能力指 示。
11、 根据权利要求 3至 10任一项所述的方法， 其中，
进行所述决策的通信实体为 UE, 或者非 3GPP接入系统。
12、 一种通过非 3GPP接入核心网的系统， 包括能力信息获知单元、增 强信息决策单元； 其中，
所述能力信息获知单元， 用于获知 UE的能力信息和 /或非 3GPP接入 系统的能力信息；
所述增强信息决策单元， 用于根据所述能力信息获知单元所获知的所 述能力信息， 决策是否允许 UE传递建立 EPC会话所需的信息。
13、 根据权利要求 12所述的系统， 其中， 所述增强信息决策单元还用 于将是否允许 UE传递建立 EPC会话所需的信息的决策结果发送给 UE。
14、 根据权利要求 12所述的系统， 其中， 进行所述决策后， 所述增强 信息决策单元确定允许 UE传递建立 EPC会话所需的信息； 所述增强信息 决策单元还用于：
在收到 UE携带的所请求的 APN后 , 向 EPC传递 UE请求的 APN。
15、 根据权利要求 12所述的系统， 其中， 所述 APN信息， 用于隐式 表示 UE的能力。
16、 根据权利要求 13至 15任一项所述的系统， 其中，
所述 UE的能力信息， 携带于 EAP认证消息或者 DHCP消息中； 建立 EPC会话所需的所述信息，携带于 EAP认证消息或者 DHCP消息 中。
17、 根据权利要求 12至 15任一项所述的系统， 其中，
所述 UE的能力信息为： UE请求的 APN, 或者 UE的能力指示； 建立 EPC会话所需的所述信息为： 所请求的 APN。
18、 根据权利要求 12至 15任一项所述的系统， 其中，
所述能力信息获知单元设置于 UE或者非 3GPP接入系统中， 所述增强信息决策单元设置于 UE或者非 3GPP接入系统中。
19、 一种通过非 3GPP接入核心网的装置， 该装置为 UE, 用于在发送 UE的能力信息后，接收是否允许 UE传递建立 EPC会话所需的信息的决策 结果； 以及根据所述决策结果， 决定是否传递建立 EPC会话所需的信息。
20、 根据权利要求 19所述的装置， 其中， 所述 UE的能力信息， 携带 于可扩展的 EAP认证消息或者 DHCP消息中。
PCT/CN2012/087205 2012-01-09 2012-12-21 一种通过非3gpp接入核心网的方法、装置和系统 Ceased WO2013104247A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP12865052.0A EP2804420A4 (en) 2012-01-09 2012-12-21 METHOD, DEVICE AND SYSTEM FOR ACCESSING THE CORE NETWORK THROUGH NON-3GPP
US14/371,159 US9516681B2 (en) 2012-01-09 2012-12-21 Method, device and system for accessing core network by means of non-3GPP access
JP2014550621A JP5872066B2 (ja) 2012-01-09 2012-12-21 非３ｇｐｐによってコアネットワークにアクセスする方法、装置及びシステム

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210004672.0 2012-01-09
CN201210004672.0A CN103200628B (zh) 2012-01-09 2012-01-09 一种通过非3gpp接入核心网的方法和系统

Publications (1)

Publication Number Publication Date
WO2013104247A1 true WO2013104247A1 (zh) 2013-07-18

Family

ID=48722948

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/087205 Ceased WO2013104247A1 (zh) 2012-01-09 2012-12-21 一种通过非3gpp接入核心网的方法、装置和系统

Country Status (5)

Country Link
US (1) US9516681B2 (zh)
EP (1) EP2804420A4 (zh)
JP (1) JP5872066B2 (zh)
CN (1) CN103200628B (zh)
WO (1) WO2013104247A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12160413B2 (en) * 2017-01-30 2024-12-03 Telefonaktiebolaget Lm Ericsson (Publ) Parameter exchange during emergency access using extensible authentication protocol messaging

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104618891B (zh) * 2013-11-04 2018-10-19 华为终端（东莞）有限公司 一种通信方法、终端及核心网实体
BR112017022545B1 (pt) * 2015-04-22 2024-03-05 Huawei Technologies Co., Ltd Método, aparelho, e sistema de autorização de nome de ponto de acesso
EP3242466B1 (de) * 2016-05-04 2019-04-17 Siemens Aktiengesellschaft Verfahren zur konfiguration von kommunikationsgeräten eines industriellen automatisierungssystems und konfigurationsdatenverteilereinheit
WO2018155934A1 (ko) * 2017-02-22 2018-08-30 엘지전자 주식회사 무선 통신 시스템에서 3GPP access를 통해 non-3GPP에 관련된 데이터를 수신하는 방법 및 이를 위한 장치
US11968614B2 (en) 2018-04-17 2024-04-23 Mediatek Singapore Pte. Ltd. Apparatuses and methods for handling access type restriction information
WO2022151271A1 (en) * 2021-01-14 2022-07-21 Zte Corporation A method for external authentication and authorization

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374334A (zh) * 2007-08-22 2009-02-25 华为技术有限公司 传递分组数据网络标识信息的方法和系统
CN101472263A (zh) * 2008-05-04 2009-07-01 中兴通讯股份有限公司 一种网络连接方式的决定方法
CN101631354A (zh) * 2008-07-18 2010-01-20 华为技术有限公司 一种分组数据网络选择的方法、装置与系统
CN101931946A (zh) * 2009-06-23 2010-12-29 中兴通讯股份有限公司 演进的分组系统中的终端的多接入方法及系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1997206A (zh) * 2006-01-04 2007-07-11 华为技术有限公司 一种正确为用户终端选择服务网络的方法
CN101127652B (zh) * 2006-08-17 2011-04-27 华为技术有限公司 一种确定用户终端访问外部网络锚点的方法、装置及系统
EP2079253A1 (en) * 2008-01-09 2009-07-15 Panasonic Corporation Non-3GPP to 3GPP network handover optimizations
CN101577935B (zh) 2008-07-17 2011-09-21 中兴通讯股份有限公司 一种事件触发器的下发和安装方法
CN102056168A (zh) * 2009-10-28 2011-05-11 中兴通讯股份有限公司 接入方法及装置
EP2364041B1 (en) * 2010-03-03 2012-09-19 Research In Motion Limited Method and apparatus to signal use-specific capabilities of mobile stations to establish data transfer sessions
EP2689567B1 (en) * 2011-03-22 2015-06-24 Telefonaktiebolaget L M Ericsson (publ) Network node and method to route through or around traffic detection function nodes
US20130121322A1 (en) * 2011-11-10 2013-05-16 Motorola Mobility, Inc. Method for establishing data connectivity between a wireless communication device and a core network over an ip access network, wireless communication device and communicatin system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374334A (zh) * 2007-08-22 2009-02-25 华为技术有限公司 传递分组数据网络标识信息的方法和系统
CN101472263A (zh) * 2008-05-04 2009-07-01 中兴通讯股份有限公司 一种网络连接方式的决定方法
CN101631354A (zh) * 2008-07-18 2010-01-20 华为技术有限公司 一种分组数据网络选择的方法、装置与系统
CN101931946A (zh) * 2009-06-23 2010-12-29 中兴通讯股份有限公司 演进的分组系统中的终端的多接入方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses (Release 11)", 3GPPTS 23.402 V 11.1.0, 14 December 2011 (2011-12-14), pages 1 - 232, XP050554523 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12160413B2 (en) * 2017-01-30 2024-12-03 Telefonaktiebolaget Lm Ericsson (Publ) Parameter exchange during emergency access using extensible authentication protocol messaging

Also Published As

Publication number Publication date
JP2015507876A (ja) 2015-03-12
CN103200628B (zh) 2018-05-15
US20140355541A1 (en) 2014-12-04
JP5872066B2 (ja) 2016-03-01
EP2804420A4 (en) 2015-10-21
CN103200628A (zh) 2013-07-10
EP2804420A1 (en) 2014-11-19
US9516681B2 (en) 2016-12-06

Similar Documents

Publication Publication Date Title
US9241255B2 (en) Local breakout with optimized interface
KR101814969B1 (ko) 네트워크에 액세스하는 시스템 및 방법
US9503417B2 (en) Method for acquiring information, user equipment, and network equipment
CN101873589B (zh) 多网接入控制方法、通讯系统以及相关设备
US9392636B2 (en) Methods and apparatuses for setting up a packet data network (PDN) connection
CN103987092B (zh) 切换过程中选择网络设备的方法和装置
CN101282287B (zh) 协商移动性管理协议的方法及其装置
EP3678349B1 (en) Configuration of liveness check using internet key exchange messages
WO2018235793A1 (ja) 端末装置及びコアネットワーク装置
WO2013104247A1 (zh) 一种通过非3gpp接入核心网的方法、装置和系统
WO2008151544A1 (en) Method, apparatus and system for establishing bearer connection
WO2019225326A1 (ja) ユーザ装置、制御装置、及び通信制御方法
WO2013174190A1 (zh) 路由选择方法及功能网元
WO2012130133A1 (zh) 一种接入点及终端接入方法
WO2010130270A1 (en) Local breakout and ip address selection
JP6446546B2 (ja) データ処理方法、装置、端末、モビリティ管理エンティティ、およびシステム
CN101730151A (zh) 实现dhcp模式协商的方法、系统及接入服务网网关
WO2013097614A1 (zh) 为ue分配ip地址的方法、系统及tnan、ue
WO2011160509A1 (zh) 在分流网络中实现地址分配的方法和装置
CN106162801A (zh) 实现缺省路由决策的方法、核心网网元、用户设备及系统

Legal Events

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

Ref document number: 12865052

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2014550621

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 14371159

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012865052

Country of ref document: EP