JP2016526858A - Reliable wireless local area network (WLAN) access scenarios - Google Patents

Abstract

A method for supporting two scenarios in reliable wireless local area network (WLAN) access is provided herein. The method may be performed, for example, by user equipment (UE). The method typically requires a non-seamless wireless offload (NSWO) connection to the network within an Extensible Authentication Protocol (EAP) procedure, and after successful authentication, an Internet Protocol (IP) address or NSWO Receiving from a network entity at least one of a reason code indicating that is not allowed.

Description

CROSS REFERENCE TO RELATED APPLICATIONS This application is a US Provisional Patent Application No. 61 / 845,876 and July 2014 filed July 12, 2013, both of which are incorporated herein by reference in their entirety Claims the benefit of US Provisional Patent Application No. 14 / 328,518, filed on the 10th.

  The present disclosure relates generally to communication systems, and more particularly to a method for supporting two scenarios in reliable wireless local area network (WLAN) access.

  Wireless communication systems are widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcast. A typical wireless communication system can utilize multiple access technologies that can support communication with multiple users by sharing available system resources (eg, bandwidth, transmit power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier Frequency division multiple access (SC-FDMA) systems and time division synchronous code division multiple access (TD-SCDMA) systems are included.

  These multiple access technologies are employed in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate at local, national, regional and even global levels. An example of an emerging telecommunication standard is Long Term Evolution (LTE). LTE is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard published by the 3rd Generation Partnership Project (3GPP). LTE improves spectrum efficiency, lowers costs, improves service, uses new spectrum, and OFDMA on the downlink (DL), SC-FDMA on the uplink (UL), And is designed to better support mobile broadband Internet access by using multiple input multiple output (MIMO) antenna technology to better integrate with other open standards.

  The technique and equipment support for two scenarios in reliable wireless local area network (WLAN) access (e.g., scenarios where the network supports non-seamless wireless offload (NSWO) and scenarios where the network does not support NSWO). For this reason, it is provided herein.

  Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The method generally requires an NSWO connection to the network within an extensible authentication protocol (EAP) procedure, and after successful authentication, an Internet Protocol (IP) address or NSWO is not allowed Receiving at least one of the reason codes indicating that from the network entity.

  Certain aspects of the present disclosure provide a method for wireless communication. The method typically includes receiving a request from the UE for NSWO connection to the network, determining whether the network supports NSWO, and after successful authentication within the EAP procedure. Sending a reason code to the UE indicating that NSWO is not allowed based on

  Certain aspects of the present disclosure provide an apparatus for wireless communication by a UE. The device generally includes at least one of a means for requesting an NSWO connection to the network and a reason code indicating that the IP address or NSWO is not allowed after successful authentication in the EAP procedure, Means for receiving from a network entity.

  Certain aspects of the present disclosure provide an apparatus for wireless communication. The device generally authenticates successfully during the EAP procedure, a means for receiving a request for the NSWO connection to the network from the UE, a means for determining whether the network supports NSWO, and And means for sending to the UE a reason code indicating that NSWO is not allowed based on the determination.

  Certain aspects of the present disclosure provide an apparatus for wireless communication by a UE. The device typically requests an NSWO connection to the network during the EAP procedure and receives from the network entity at least one of an IP address or a reason code indicating that NSWO is not allowed after successful authentication. Including at least one processor configured to. The apparatus also generally includes a memory coupled with at least one processor.

  Certain aspects of the present disclosure provide an apparatus for wireless communication. The device typically receives a request from the UE for NSWO to the network during the EAP procedure, determines whether the network supports NSWO, and after successful authentication, NSWO It includes at least one processor configured to send a reason code indicating that it is not allowed to the UE.

  Certain aspects of the present disclosure provide a computer-readable medium for wireless communication by a UE. A computer-readable medium generally has instructions stored thereon, the instructions requesting an NSWO connection to the network, within an EAP procedure, and successful authentication by one or more processors. Receiving at least one of the reason codes indicating that the IP address or NSWO is not allowed from the network entity.

  Certain aspects of the present disclosure provide a computer-readable medium for wireless communication. The computer-readable medium generally has instructions stored thereon, the instructions receiving, by the one or more processors, a request for an NSWO connection to the network from the UE in an EAP procedure; , To determine whether the network supports NSWO and to send a reason code to the UE indicating that NSWO is not allowed based on the determination after successful authentication.

  Many other aspects are provided, including methods, apparatus, systems, computer program products, and processing systems.

  For a better understanding of the above features of the present disclosure, a more particular description of what has been briefly summarized above may be had by reference to the embodiments, some of which are shown in the accompanying drawings. . However, the attached drawings illustrate only certain typical aspects of the present disclosure and therefore should not be considered as limiting the scope of the present disclosure, because this description has other equivalent effects. Note that this can result in aspects.

FIG. 1 illustrates an example network architecture for supporting mobility between a cellular link and a wireless local area network (WLAN), in accordance with certain aspects of the present disclosure. FIG. 3 illustrates an example network architecture for supporting mobility between a cellular link and a trusted WLAN in accordance with certain aspects of the present disclosure. FIG. 3 illustrates an example SaMOG architecture in accordance with certain aspects of the present disclosure. FIG. 4 illustrates an exemplary call flow for initial connection and device authentication in SaMOG according to some aspects of the present disclosure. FIG. 6 is a block diagram illustrating an exemplary operation of wireless communication by a user equipment (UE) in accordance with certain aspects of the present disclosure. FIG. 6 illustrates exemplary means capable of performing the operations shown in FIG. 5, in accordance with certain aspects of the present disclosure. FIG. 6 is a block diagram illustrating example operations for wireless communication in accordance with certain aspects of the present disclosure. FIG. 7 illustrates exemplary means capable of performing the operations shown in FIG. 6, in accordance with certain aspects of the present disclosure.

  Techniques and apparatus are provided herein to support scenarios in reliable wireless local area network (WLAN) access. For example, in the first scenario, the WLAN may allow non-seamless wireless offload (NSWO), and in the second scenario, the WLAN may not allow NSWO. Each user equipment (UE) and WLAN may support only a single connection or may support multiple connections. In various scenarios, the WLAN determines the UE type based on whether the UE requests a packet data network (PDN) connection or an NSWO connection in the extensible authentication protocol (EAP) authentication procedure. I can know. The WLAN can send a reason code to the UE, which allows the UE to know the network type based on the reason code. The UE may disconnect, for example, based on a known network type, or may request a PDN connection and re-authenticate.

  The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be implemented. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

  Next, some aspects of a telecommunications system are presented with reference to various apparatus and methods. These devices and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). Indicated. These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

  By way of example, an element, or any portion of an element, or any combination of elements may be implemented with a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and throughout this disclosure There are other suitable hardware configured to perform the various functions described. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, instructions, instruction sets, code, code segments, program codes, programs, subprograms, It should be interpreted broadly to mean software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc.

  Thus, in one or more exemplary embodiments, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer readable media can be RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or any desired form in the form of instructions or data structures. Any other medium that can be used to carry or store the program code and that can be accessed by a computer can be included. As used herein, disk and disk include compact disk (CD), laser disk (registered trademark), optical disk, digital versatile disk (DVD), and floppy disk (registered trademark). The disk normally reproduces data magnetically, while the disk optically reproduces data with a laser. Combinations of the above should also be included within the scope of computer-readable media.

Exemplary Wireless Communication System FIG. 1 is a diagram illustrating an exemplary network architecture 100 for supporting mobility between a cellular link and a wireless local area network (WLAN), in accordance with certain aspects of the present disclosure. is there. 3GPP has defined two mechanisms that provide this support. In the first solution, referred to as the “S2b solution”, user equipment (UE) 102 packets over WLAN to an evolved packet core (EPC) network (e.g., home public land mobile network (HPLMN) 110). Establish a data network (PDN) connection. Since the WLAN 108 is unreliable, the enhanced packet data gateway (ePDG) 104 mediates communication between the UE 102 and the PDN gateway 106. As shown, the UE 102 tunnels control and user plane data to the ePDG 104 by establishing an Internet Protocol Security (IPSec) tunnel. The ePDG 104 then establishes a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) or Proxy Mobile Internet Protocol (PMIP) tunnel to the appropriate PDN gateway (GW) 106.

  In a second solution called `` S2c solution '' (not shown in FIG. 1), the UE (e.g., similar to UE 102) is a WLAN (trusted WLAN 112 that does not use an IPSec tunnel, or an IPSec tunnel to ePDG 104. Establish connectivity by connecting to any of the unreliable WLANs 108 that use. The UE may then connect directly to the PDN GW 106 using, for example, DSMIPv6.

  In the S2b and S2c solutions, the UE 102 creates a new PDN connection over the WLAN to a given access point name (APN) chosen by the UE 102. The UE 102 then moves the existing PDN connection from the cellular to the WLAN by establishing connectivity over the WLAN and indicating handover to one or more PDN connections. The UE 102 can also connect to the same APN simultaneously via cellular and WLAN.

  FIG. 2 is a diagram illustrating an example network architecture 200 for supporting mobility between a cellular link and a trusted WLAN 208 in accordance with certain aspects of the present disclosure. In some systems, connectivity using S2a to an EPC core network (eg, HPLMN 210) via WLAN 208 may be enabled (eg, solutions based on GTP or PMIP). This is sometimes referred to as the “S2a solution”. In the S2a solution, WLANs that are considered trusted do not use IPSec tunnel establishment or use ePDG. Instead, to establish connectivity with the EPC (e.g., to establish a PDN connection), select a trusted WLAN 208, connect to it, and then exchange signaling with the access network of the trusted WLAN 208 To manage connectivity. This mechanism is called “SaMOG” (S2a mobility via GTP).

  FIG. 3 is a diagram illustrating an example SaMOG architecture 300 in accordance with certain aspects of the present disclosure. SaMOG architecture 300 is a non-3GPP WLAN access network 302, trusted WLAN authentication, authorization and billing (AAA) proxy (TWAP) 304, and trusted WLAN access gateway (TWAG) 306 network element that provides connectivity and control including. The TWAG 306 is connected to the PDN gateway 308 via the S2a interface 314.

  The function of the TWAP 304 relays AAA information between the WLAN access network 302 and the 3GPP AAA server, that is, the proxy 312 when roaming. The TWAP 304 associates the UE 310's international mobile subscriber identity (IMSI) with the medium access control (MAC) address of the UE 310 on the WLAN access network 302 to form an (IMSI, MAC) tuple. This can be accomplished by looking for AAA protocols that carry EAP-AKA exchanges. For example, the TWAP 304 may detect a layer 2 (L2) connection to the WLAN access network 302 of the UE 310 by searching on the AAA protocol to obtain an EAP success message, and the WLAN connection and disconnection events for the UE 310 (MAC, IMSI) The TWAG 306 can be notified using a tuple.

  The functions of the TWAG 306 act as a default IPv4 router, a dynamic host configuration protocol (DHCP) server, and / or a default IPv6 router. It performs routing of packets for the UE to extend to the PDN gateway 308 between the MAC address of the UE and the GTP tunnel. The function of TWAG 306 also performs per-UE L2 encapsulation of traffic to / from UE 310.

  The UE 310 selects the WLAN access network 302 connected to it, authenticates with the selected WLAN access network 302, and exchanges control signaling with the TWAG 306 related to establishing connectivity, thereby enabling the SaMOG architecture 300. Get connectivity through. In response, if TWAG 306 permits connectivity, TWAG 306 establishes connectivity to the appropriate PDN gateway 308 via the S2a interface.

  The UE-TWAG protocol controls point-to-point links per PDN (eg, setup and teardown). This protocol is denoted as WLAN Control Protocol (WLCP). WLCP is a protocol defined by 3GPP and is transported above layer 2. WLCP is not an IP protocol but is located below the IP layer.

  WLCP provides session management functionality for PDN connections. WLCP establishes PDN connection, handover of PDN connection, request for release of PDN connection by UE310, notification to UE310 of release of PDN connection, IP address assignment (IPv4 and IPv6 defined for NAS Both address assignment mechanisms can be applied) and PDN parameter management, where PDN parameters include APN, PDN type, address, protocol configuration option (PCO), request type, L2 transport identifier.

  WLCP is applied to support multiple PDN connections, allowing the UE 310 to behave similarly to the behavior on the cellular link. WLCP is a protocol running between UE 310 and TWAG 306. Thus, a node in the middle between UE 310 and TWAG 306 (eg, access point (AP)) may not support or understand WLCP.

  The WLCP protocol may be transported using wireless MAC frames from UE 310 to the access point and from the access point to TWAG 306, for example. The point-to-point link between UE 310 and TWAG 306 transports an L2 packet or L2 packet data unit (PDU), so the packet can be correctly routed to TWAG 306, so TWAG 306 Know to include control signaling. When a packet is routed from TWAG 306 to UE 310, UE 310 knows that it is control signaling.

  FIG. 4 is a diagram illustrating an exemplary call flow 400 for initial attachment and device authentication in SaMOG in accordance with certain aspects of the present disclosure. In 1, the UE 402 in the Home Public Land Mobile Network (HPLMN), both the Trusted WLAN Access Network (TWAN) 404 and the 3GPP AAA server 406, all of them are fully autonomous and reliable WLAN access to the EPC (i.e. To support multiple concurrent PDN connections, IP address storage, and concurrent NSWO and EPC access). For example, the UE 402 discovers and associates with the TWAN 404.

  Then, at 2, TWAN 404 initiates the EAP exchange by sending an EAP request message as part of the authentication procedure. As part of the EAP exchange, UE402, TWAN404, and 3GPP AAA server 406 in HPLMN are all fully autonomous and reliable WLAN access to EPC (i.e., multiple PDN connections in parallel, IP address storage, and Discover if you really support (parallel NSWO and EPC access). If UE402, TWAN404, and 3GPP AAA server 406 in HPMLN do not support fully autonomous and reliable WLAN access to EPC, then either PDN connection or NSWO can be trusted without explicit request from UE402 Not automatically presented by the WLAN.

Reliable Wireless Local Area Network (WLAN) Access Scenario An increasing number of wireless subscribers access mobile data services. Development will continue to drive an increase in the volume of mobile data traffic. However, they can also create challenges for operators in supporting traffic growth. Wireless local area networks (WLANs) are widely available in homes and various hotspots, and because they use several wireless devices, mechanisms that offload data traffic to Wi-Fi minimize data costs It is extremely attractive for operators who want to limit and make better use of their assets. Seamless offload enables seamless handover of data traffic to Wi-Fi. The basic idea is that whenever a WLAN access point is available, some or all of the traffic is routed through the WLAN access point, thus offloading cellular access. Non-seamless WLAN offload is an optional feature applied to user equipment (UE) that can support WLAN wireless access in addition to 3G wireless access. It allows the UE to be directed to shift traffic from a 3G based radio access network (RAN) to a Wi-Fi connection. In order to perform non-seamless WLAN offload, the UE obtains a local IP address through the WLAN access network. The UE does not need to connect to an evolved packet data gateway (ePDG). However, while IP addresses are maintained for seamless offload, IP addresses are not maintained for NSWO.

  As described above, a procedure may be defined for a device (eg, user equipment (UE)) to access an evolved packet core (EPC) core network through reliable wireless local area network (WLAN) access. Some systems (eg, Release 11 SaMOG) support a single packet data network (PDN) connection without Internet Protocol (IP) address storage. However, it may be desirable to support multiple PDN connections with non-seamless wireless offload (NSWO), IP address storage, and parallel PDN connections. A system that supports a single PDN connection with IP address storage (eg, pre-Rel-12) may be desirable. It may also be desirable for the solution to be backward compatible (eg, with pre-Rel-12).

  Techniques and apparatus are provided herein to support various scenarios in reliable WLAN access. For example, in the first scenario, the network (eg, similar to WLAN access network 302) may allow NSWO, and in the second scenario, the network may not allow NSWO. Each UE (eg, similar to UE 310) and network may support only a single connection or may support multiple connections. In various scenarios, the network can know the UE type based on whether the UE requests a PDN connection or an NSWO connection in an extensible authentication protocol (EAP) authentication procedure. The network can send a reason code to the UE, and the UE can know the network type based on the reason code. Based on the known network type, the UE may disconnect or may request a PDN connection and re-authenticate.

  According to some aspects, one advantage of the proposed solution is that no extra functional negotiation may be required through the EAP authentication procedure between the UE and the network. This may avoid interaction problems caused by different functions of the UE and the network. For example, the UE may be capable of single connection or multiple connections. Similarly, the network may be capable of a single connection or multiple connections.

  According to some aspects, EAP authentication may allow a UE (eg, similar to UE 310) to request a PDN or NSWO connection to a network (eg, the 3GPP home network of FIG. 3). According to some aspects, a UE that supports multiple connections may be configured to request NSWO in an EAP authentication procedure (i.e., a multi-connection UE requests a PDN connection in an EAP procedure). Not) Therefore, when the UE requests a PDN connection in the EAP authentication procedure, the network implicitly assumes the UE's capabilities (e.g., the UE supports multiple connections or only a single connection). Get to know. For example, if the UE requests a PDN in the EAP authentication procedure, the network may know that the UE supports a single PDN connection.

  According to some aspects, in response to a UE request for a PDN connection, the network may receive a reason code (e.g., “NSWO is not allowed and requires a PDN connection” or “NSWO is not allowed”). Can be returned to the UE, even if EAP authentication succeeds. Based on the reason code, the UE may know the capabilities of the network (eg, whether the network supports single connection or multiple connections and whether the network supports NSWO or not). The UE is based on what reason code was received (i.e., based on whether the UE knows that the network supports single connection or multiple connections, or does not support NSWO). Can behave differently.

  According to some aspects, the UE may support a single PDN connection or may support multiple PDN connections. According to some aspects, the network may also support a single PDN connection or may support multiple PDN connections. According to some aspects, the network may allow NSWO. Alternatively, the network cannot allow NSWO. Depending on various scenarios with different combinations of whether the UE or network supports single connection or multiple connections and whether NSWO is allowed or not allowed by the network, the UE and The behavior of the network can change.

  According to some aspects, the network may not allow NSWO for the UE. In the first scenario where the network does not allow NSWO for the UE, both the UE and the network may support a single PDN connection. A single connection UE can request an NSWO or PDN connection within the EAP authentication protocol. According to some aspects, if the UE requests a PDN, authentication may be successful and an IP address may be assigned to the UE, eg, from a packet gateway (P-GW). The network may know that the UE is a single connection UE because the UE has requested a PDN connection in authentication (ie, a multiple connection UE cannot). Alternatively, the UE may request NSWO in the EAP authentication procedure. Authentication can be successful, but no IP address can be assigned to the UE because NSWO is not allowed. Instead, the network may send a reason code to the UE that specifies “NSWO is not allowed and requires a PDN connection”. In this case, if the UE desires a PDN connection, the UE may then attempt to re-authenticate and request a PDN connection. Otherwise, if the UE does not want PDN connection, the UE may disconnect.

  In a second scenario where the network does not allow NSWO for the UE, the UE can support only a single connection and the network can support multiple connections. If a single connection UE requests a PDN connection in an EAP authentication procedure, authentication may be successful and an IP address may be assigned to the UE (eg, by the PGW). The network may know that the UE is a single connection UE because the UE has requested a PDN connection in authentication (ie, a multiple connection UE cannot). Alternatively, a single connection UE may request NSWO in the EAP authentication procedure. Authentication can succeed, but no IP address can be assigned because NSWO is not allowed. The network may send a reason code specifying “NSWO not allowed” to the UE. In this case, if the UE desires a PDN connection, the single-connection UE may attempt to re-authenticate and request a PDN connection in the EAP authentication procedure. Otherwise, the UE may disconnect. Thus, the network sends different reason codes, but a single connection UE may request only NSWO when NSWO is not allowed, and whether the network supports only single connection or multiple connections. It can behave in the same way.

  In a third scenario where the network does not allow NSWO for the UE, the UE can support multiple connections and the network can support only a single connection. Unlike the scenario for single-connection UEs, multi-connection UEs can only request NSWO in the EAP authentication procedure (i.e., multi-connection UEs can request a PDN in the EAP authentication procedure). Must not request). After requesting NSWO, authentication can succeed, but no IP address can be assigned because NSWO is not allowed. The network may send a reason code to the UE specifying “NSWO is not allowed and requires a PDN connection”. In this case, a multi-connected UE may behave similarly to a single-connected UE depending on the reason code. If the UE desires a PDN connection, the multi-connection UE may attempt to re-authenticate and request a PDN, and if the UE does not desire a PDN connection, the UE may disconnect.

  In a fourth scenario where the network does not allow NSWO for the UE, both the UE and the network can support multiple connections. Multiple connected UEs can request only NSWO in the EAP authentication procedure. Authentication can succeed, but no IP address can be assigned because NSWO is not allowed. The network may send a reason code “NSWO not allowed” to the UE. In this case, the multi-connected UE may still remain authenticated and may request a PDN connection using WLAN control protocol (WLCP).

  According to some aspects, the network may allow NSWO. In the first scenario where the network allows NSWO, the UE and the network can each support only a single connection. If a single connection UE requests a PDN connection in an EAP authentication procedure, an IP address is assigned (eg, from the P-GW) and authentication can be successful. Alternatively, if the UE requests NSWO in the EAP authentication procedure, authentication can be successful and NSWO is allowed, so a local IP address can be assigned.

  In the second scenario where the network allows NSWO, the UE can support only a single connection and the network can support multiple connections. If a single connection UE requests a PDN connection to the network in the EAP authentication procedure, authentication may be successful and an IP address may be assigned to the UE (eg, from the P-GW). According to some aspects, the network may determine whether the UE is a single connection UE based on the requested connection type (i.e., a multi-connection UE should not request a PDN in an EAP authentication procedure). It can be known implicitly. Alternatively, if the UE requests NSWO in the EAP authentication procedure, authentication can be successful and NSWO is allowed, so a local IP address can be assigned to the UE. Thus, when a network grants NSWO, a single connection UE may behave the same regardless of whether the network is a single connection or multiple connections.

  In a third scenario where the network allows NSWO, the UE can support multiple connections and the network can only support a single connection. A multi-connection UE may request only NSWO in the EAP authentication procedure (ie, a multi-connection UE shall not request a PDN in the EAP authentication procedure). Authentication can be successful and a local IP address can be assigned to the UE (eg, from the P-GW). According to some aspects, if the UE then requests a PDN using WLCP, the request may fail. According to some aspects, after several unsuccessful retries, the multi-connected UE may determine that it is roaming to a single PDN network. According to some aspects, a multi-connected UE may be configured to attempt only a limited number of retries. For example, the retry scheme may be configured in the UE. If multiple connected UEs desire PDN connectivity, the UE may request a PDN and re-authenticate.

  In a fourth scenario where the network allows NSWO, both the UE and the network can support multiple connections. In this scenario, the UE may request NSWO. Since authentication can be successful and NSWO is allowed, a local IP address can be assigned to the UE (eg, by the P-GW). According to some aspects, the UE may then request a PDN connection using WLCP.

  FIG. 5 illustrates an example operation 500 for wireless communication in accordance with certain aspects of the present disclosure. Operation 500 may be performed, for example, by a UE (eg, similar to UE 310). Operation 500 may begin at 502 by requesting an NSWO connection to the network in an EAP procedure.

  According to some aspects, if the UE and the network support multiple connections, the UE may request a PDN connection to the network using WLCP while still being authenticated.

  At 504, the UE may receive from the network entity at least one of an Internet Protocol (IP) address or a reason code indicating that NSWO is not allowed after successful authentication.

  For example, the UE may receive a reason code indicating that NSWO is not allowed if the network does not support NSWO. According to some aspects, the reason code may further indicate that a PDN connection is required if the network supports only a single connection. According to some aspects, the UE may disconnect if a PDN connection is not desired. According to some aspects, the UE may request a PDN connection to the network during the EAP re-authentication procedure. The UE may receive an IP address assigned by the network (eg, by the P-GW) after successful re-authentication.

  According to some aspects, the UE may receive an IP address if the network supports NSWO. According to some aspects, the UE may further request a PDN connection to the network using WLCP if the UE supports multiple connections and the network supports only a single connection. According to some aspects, if the request fails one or more times, the UE may determine that the UE roams to a single connected network. According to some aspects, the UE may then request a PDN connection to the network during the EAP re-authentication procedure if the UE desires a PDN connection.

  FIG. 6 illustrates an example operation 600 for wireless communication in accordance with certain aspects of the present disclosure. Operation 600 may be performed, for example, by a network entity (eg, TWAG 306). Operation 600 may begin at 602 by receiving a request from a UE for an NSWO connection to a network in an EAP procedure.

  At 604, the network entity may determine whether the network supports NSWO.

  At 606, after successful authentication, the network entity may send a reason code to the UE indicating that NSWO is not allowed based on the decision. For example, the network entity may send a reason code indicating that NSWO is not allowed if the network does not support NSWO. According to some aspects, the reason code may further indicate that a PDN connection is required if the network is a single connection network.

  According to some aspects, the network entity may then receive a request from the UE for a PDN connection to the network in an EAP re-authentication procedure. The network entity may assign an IP address (eg, by the P-GW) after successful re-authentication.

  According to some aspects, if the UE and the network support multiple connections, the network entity receives a request from the UE for a PDN connection via WLCP to the network while still being authenticated. obtain.

  Various operations of the methods described above may be performed by any suitable means that can perform the corresponding function. The means may include various hardware and / or software components and / or modules including but not limited to circuits, application specific integrated circuits (ASICs), or processors. In general, where there are illustrated operations, those operations may have corresponding action means-plus-function components with similar numbers. For example, operations 500 and 600 shown in FIGS. 5 and 6, respectively, correspond to means 500A and 600A shown in FIGS. 5A and 6A, respectively.

  For example, the means for transmitting may comprise a transmitter and / or antenna of a UE (eg, UE 310) or a network entity (eg, TWAG 306 or 3GPP AAA server 312). Means for receiving may comprise a receiver and / or antenna of a UE (eg, UE 310) or a network entity (eg, TWAG 306 or 3GPP AAA server 312). The means for determining may comprise a processing system that may include one or more processors of a UE (eg, UE 310) or a network entity (eg, TWAG 306 or 3GPP AAA server 312).

  According to some aspects, such means are configured to perform corresponding functions by performing various algorithms (e.g., in hardware or by executing software instructions). Can be implemented by a processing system. For example, an algorithm for requesting a non-seamless wireless offload (NSWO) connection to the network within an Extensible Authentication Protocol (EAP) procedure, and an Internet Protocol (IP) address or NSWO allowed after successful authentication An algorithm for receiving from a network entity at least one of a reason code indicating that it is not. Similarly, algorithms for receiving requests from user equipment (UE) for non-seamless wireless offload (NSWO) connection to the network within the Extensible Authentication Protocol (EAP) procedure, the network supports NSWO And an algorithm for sending to the UE a reason code indicating that NSWO is not allowed based on the decision after successful authentication.

  Various algorithms may be implemented by computer readable media, which may be non-transitory computer readable media. The computer readable medium may have computer-executable instructions (eg, code) stored thereon. For example, the instructions may be executed by a processor or processing system of a UE (e.g., UE 310) or a network entity (e.g., TWAG 306 or 3GPP AAA server 312), and the UE (e.g., UE 310) or network entity (e.g., TWAG 306 or 3GPP AAA) It can be stored in the memory of the server 312). For example, a computer-readable medium includes computer-executable instructions stored therein for requesting a non-seamless wireless offload (NSWO) connection to a network within an extensible authentication protocol (EAP) procedure, and After successful authentication, there may be instructions for receiving from the network entity at least one of an Internet Protocol (IP) address or a reason code indicating that NSWO is not allowed. Similarly, a computer readable medium for receiving a request from a user equipment (UE) for a non-seamless wireless offload (NSWO) connection to a network within an extensible authentication protocol (EAP) procedure. Send to the UE a computer-executable instruction stored there, an instruction to determine whether the network supports NSWO, and a reason code indicating that NSWO is not allowed based on the determination after successful authentication You may have instructions for

  As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” includes calculating, computing, processing, deriving, exploring, searching (eg, searching in a table, database, or another data structure), checking, etc. Can do. Also, “determining” can include receiving (eg, receiving information), accessing (eg, accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, selecting, establishing, and the like.

  As used herein, a phrase referring to “at least one” of a list of items refers to any combination of these items including a single member. By way of example, “at least one of a, b, or c” is intended to include a, b, c, a-b, a-c, b-c, and a-b-c.

  The method or algorithm steps described in connection with the disclosure herein may be implemented directly in hardware, in software modules executed by a processor, or in a combination of the two. Software modules reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art Can do. An exemplary storage medium is coupled to the processor such that the processor can read information from, and / or write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may be present in the user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. In general, if there are operations shown in the figures, those operations may have means-of-function components of corresponding operations having similar numbers.

  In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that enables transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer readable media instructions may be RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage device, or desired program code means. Or a general purpose or special purpose computer, or any other medium that can be accessed by a general purpose or special purpose processor, which may be used for carrying or storing in the form of a data structure. Also, any connection is properly termed a computer-readable medium. For example, the software uses a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, wireless, and microwave to websites, servers, or other When transmitted from a remote source, coaxial technology, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of the medium. The discs and discs used in this specification are compact discs (CD), laser discs (discs), optical discs (discs), digital versatile discs (DVDs) ), Floppy disk, and Blu-ray disc, the disk normally reproduces data magnetically, and the disc optically reproduces data with a laser . Combinations of the above should also be included within the scope of computer-readable media.

  The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit and scope of the disclosure. . Accordingly, the present disclosure is not limited to the examples and designs described herein but is to be accorded the maximum scope consistent with the principles and novel features disclosed herein.

100 network architecture
102 User equipment
104 Enhanced packet data gateway
106 PDN gateway
108 Untrusted WLAN
110 Home Public Land Mobile Network
112 Reliable WLAN
200 network architecture
202 User equipment
208 Reliable WLAN
210 Home Public Land Mobile Network
300 SaMOG architecture
302 WLAN access network
304 Reliable WLAN authentication, authorization and billing proxy
306 Reliable WLAN access gateway
308 PDN gateway
310 User equipment
312 3GPP AAA server
314 S2a interface
402 User equipment
404 Reliable WLAN access network
406 3GPP AAA server

Claims (36)

A method for wireless communication by a user equipment (UE),
Requesting a non-seamless wireless offload (NSWO) connection to the network within an extensible authentication protocol (EAP) procedure;
Receiving from a network entity at least one of an Internet Protocol (IP) address or a reason code indicating that NSWO is not allowed after successful authentication.   Receiving the at least one of the reason codes indicating that the IP address or NSWO is not authorized from the network entity indicates that the NSWO is not authorized if the network does not support NSWO; The method of claim 1, comprising receiving a reason code.   The method of claim 2, wherein the reason code further indicates that a packet data network (PDN) connection is required if the network supports only a single connection.   The method of claim 1, further comprising disconnecting if a packet data network (PDN) connection is not desired. Requesting a packet data network (PDN) connection to the network in an EAP re-authentication procedure;
The method of claim 1, further comprising receiving an IP address assigned by the network after successful re-authentication.   The method according to claim 5, wherein the IP address is assigned by a packet gateway (P-GW). If the UE and the network support multiple connections, use a Wireless Local Area Network (WLAN) Control Protocol (WLCP) to establish a packet data network (PDN) connection to the network while still being authenticated. The method of claim 1, further comprising the step of requesting.   Receiving from the network entity at least one of the reason code indicating that the IP address or NSWO is not authorized comprises receiving the IP address if the network supports NSWO; The method of claim 1. If the UE supports multiple connections and the network supports only a single connection, a packet data network (PDN) connection to the network can be made using a Wireless Local Area Network (WLAN) Control Protocol (WLCP). Requesting steps,
9. The method of claim 8, further comprising: determining that the UE is roaming to the single connection network if the request fails one or more times. 10. The method of claim 9, further comprising requesting a PDN connection to the network in an EAP re-authentication procedure if the UE desires a PDN connection. A method for wireless communication,
Receiving from a user equipment (UE) a request for a non-seamless wireless offload (NSWO) connection to a network within an extensible authentication protocol (EAP) procedure;
Determining whether the network supports NSWO; and
Sending a reason code to the UE indicating that NSWO is not allowed based on the determination after successful authentication.   12. Sending to the UE a reason code indicating that NSWO is not allowed based on the determination comprises sending a reason code indicating that the NSWO is not allowed if the network does not support NSWO. The method described in 1.   13. The method of claim 12, wherein the reason code further indicates that a packet data network (PDN) connection is required if the network is a single connection network. Receiving, from the UE, a packet data network (PDN) connection to the network in an EAP re-authentication procedure;
12. The method of claim 11, further comprising assigning an IP address to the UE after successful re-authentication.   The method according to claim 14, wherein the IP address is assigned by a packet gateway (P-GW). If the UE and the network support multiple connections, for packet data network (PDN) connection to the network via the Wireless Local Area Network (WLAN) Control Protocol (WLCP) while still being authenticated The method of claim 11, further comprising receiving a request from the UE. A device for wireless communication by user equipment (UE),
Means for requesting a non-seamless wireless offload (NSWO) connection to the network within an extensible authentication protocol (EAP) procedure;
Means for receiving from a network entity at least one of an Internet Protocol (IP) address or a reason code indicating that NSWO is not allowed after successful authentication.   The means for receiving from the network entity the at least one of the reason codes indicating that the IP address or NSWO is not authorized, if the network does not support NSWO, the NSWO is not authorized The apparatus of claim 17, comprising means for receiving the reason code indicating.   19. The apparatus of claim 18, wherein the reason code further indicates that a packet data network (PDN) connection is required if the network supports only a single connection.   18. The apparatus of claim 17, further comprising means for disconnecting if a packet data network (PDN) connection is not desired. Means for requesting a packet data network (PDN) connection to the network in an EAP re-authentication procedure;
18. The apparatus of claim 17, further comprising means for receiving an IP address assigned by the network after successful re-authentication.   The apparatus according to claim 21, wherein the IP address is assigned by a packet gateway (P-GW). If the UE and the network support multiple connections, use a Wireless Local Area Network (WLAN) Control Protocol (WLCP) to establish a packet data network (PDN) connection to the network while still being authenticated. The apparatus of claim 17, further comprising means for requesting.   The means for receiving from the network entity at least one of the reason code indicating that the IP address or NSWO is not authorized is for receiving the IP address if the network supports NSWO. 18. The apparatus of claim 17, comprising: If the UE supports multiple connections and the network supports only a single connection, a packet data network (PDN) connection to the network can be made using a Wireless Local Area Network (WLAN) Control Protocol (WLCP). Means for requesting;
25. The apparatus of claim 24, further comprising means for determining that the UE is roaming to the single-connected network if the request fails one or more times. 26. The apparatus of claim 25, further comprising means for requesting a PDN connection to the network during an EAP re-authentication procedure if the UE desires a PDN connection. A device for wireless communication,
Means for receiving from a user equipment (UE) a request for non-seamless wireless offload (NSWO) connection to a network within an extensible authentication protocol (EAP) procedure;
Means for determining whether the network supports NSWO;
Means for sending a reason code to the UE indicating that NSWO is not allowed based on the decision after successful authentication.   The means for sending to the UE a reason code indicating that NSWO is not allowed based on the determination includes means for sending a reason code indicating that the NSWO is not allowed if the network does not support NSWO. 28. The apparatus of claim 27, comprising.   29. The apparatus of claim 28, wherein the reason code further indicates that a packet data network (PDN) connection is required if the network is a single connection network. Means for receiving a request for packet data network (PDN) connection to the network from the UE in an EAP re-authentication procedure;
28. The apparatus of claim 27, further comprising means for assigning an IP address to the UE after successful re-authentication.   The apparatus according to claim 30, wherein the IP address is assigned by a packet gateway (P-GW). If the UE and the network support multiple connections, for packet data network (PDN) connection to the network via the Wireless Local Area Network (WLAN) Control Protocol (WLCP) while still being authenticated 28. The apparatus of claim 27, further comprising means for receiving a request from the UE. A device for wireless communication by user equipment (UE),
Request a non-seamless wireless offload (NSWO) connection to the network within the Extensible Authentication Protocol (EAP) procedure,
At least one processor configured to receive from a network entity at least one of an Internet Protocol (IP) address or a reason code indicating that NSWO is not allowed after successful authentication;
And a memory coupled to the at least one processor. A device for wireless communication,
In a Extensible Authentication Protocol (EAP) procedure, a request for non-seamless wireless offload (NSWO) connection to the network is received from the user equipment (UE),
Determine whether the network supports NSWO;
At least one processor configured to send a reason code to the UE indicating that NSWO is not allowed based on the determination after successful authentication;
And a memory coupled to the at least one processor. A computer-readable recording medium storing instructions, wherein the instructions are executed by one or more processors,
Requesting a non-seamless wireless offload (NSWO) connection to the network within the extensible authentication protocol (EAP) procedure;
A computer readable recording medium executable for receiving at least one of a reason code indicating that an Internet Protocol (IP) address or NSWO is not allowed after successful authentication from a network entity. A computer readable recording medium for wireless communication storing instructions, wherein the instructions are by one or more processors,
Receiving from a user equipment (UE) a request for a non-seamless wireless offload (NSWO) connection to a network within an extensible authentication protocol (EAP) procedure;
Determining whether the network supports NSWO;
A computer readable recording medium executable after sending a reason code to the UE indicating that NSWO is not allowed based on the determination after successful authentication.

Images