Patent Description:
For example, a fifth generation (<NUM>) wireless communications technology (which can be referred to as new radio (NR)) is envisaged to expand and support diverse usage scenarios and applications with respect to current mobile network generations. In an aspect, <NUM> communications technology can include: enhanced mobile broadband addressing humancentric use cases for access to multimedia content, services and data; ultra-reliable-low latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which can allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information. As the demand for mobile broadband access continues to increase, however, further improvements in NR communications technology and beyond may be desired.

For example, for NR communications technology and beyond, current access network selection and handover solutions may not provide a desired level of speed or customization for efficient operation. Thus, improvements in wireless communication operations may be desired.

<CIT> discloses managing a data network connection for mobile communications based on user location. <CIT> discloses a method and apparatus for managing packet data network connectivity. <CIT> describes selection of a wireless service provider and technology for a requested service. <CIT> relates to local gateway (LGW) selection technique.

A method for selecting a connection gateway for a service operating on a wireless communications device is provided with reference to the appended claims.

Additionally, the term "component" as used herein may be one of the parts that make up a system, may be hardware, firmware, and/or software stored on a computer-readable medium, and may be divided into other components.

The present disclosure generally relates to methods and devices for enabling wireless communications devices to support services on one or more networks, such as a fifth generation (<NUM>) core (5GC) network, an evolved packet core (EPC) network, etc., using different access networks, such as a non-third generation partnership project (3GPP) access network, 3GPP access network, and/or the like. The various aspects may enable a wireless communications device to select a connection gateway based on a service related to the network, based on preferences or prioritizations specified for a service, etc. In this regard, the wireless communication device can select certain connection gateways for certain types of service to facilitate using 3GPP or non-3GPP access networks for certain services provided in a 5GC (or EPC) network.

Various aspects may further enable the wireless communications device to provide a <NUM> capability identifier into a payload or data stream associated with a service, to inform a receiving base station or server that the requesting service may be supported on either 5GC or EPC and/or using a non-3GPP access network or a 3GPP access network. The various aspects may be advantageous in mixed access networks in which <NUM> may not be fully supported for all services, and/or a combination of non-3GPP and 3GPP access networks are available to a wireless communications device. Mixed access networks including 3GPP and non-3GPP networks may present problems for <NUM> capable wireless communications devices because utilizing entirely non-3GPP access networks may degrade device security, while using only 3GPP access networks may result in some services being unsupported, thereby possibly degrading the user experience. By enabling the wireless communications device to select the access network for supporting services and/or further enabling access network infrastructure to handover services between connection gateways without requiring additional input, the various aspects may improve the integrity of service connections, reducing dropped data, and/or improving the overall user experience in mixed access networks.

Additional features of the present aspects are described in more detail below with respect to <FIG>.

It should be noted that the techniques described herein may be used for various wireless communication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" are often used interchangeably. IS-<NUM> Releases <NUM> and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-<NUM> (TIA-<NUM>) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band. The description below, however, describes an LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to <NUM> networks or other next generation communication systems).

As used herein, the terms "wireless communications device", "mobile device", "mobile computing device" and "user equipment" are used interchangeably and may refer to any computing device capable of communicating over a wireless access network. Examples may include but are not limited to smartphones, tablets, laptops, Internet-of Things (IoT) devices, wearable computing devices, smart appliances, smart lightbulbs, smart clothing, smart glasses, and the like, as described further herein.

As used herein, the term "<NUM> Access Network" refers to an access network comprising a NextGen (NG)-radio access network (RAN) and/or non-3GPP access network (AN) connecting to a <NUM> Core Network.

As used herein, "<NUM> Core Network" refers to the core network connects to a <NUM> Access Network. The <NUM> Core Network may support the connectivity of the wireless communications device via non-3GPP access networks, e.g. wireless local area network (WLAN) access.

In various aspects, non-3GPP access networks can be connected to the <NUM> Core Network via a non-3GPP InterWorking Function (N3IWF). The N3IWF interfaces to <NUM> Core Network control-plane functions and user-plane functions via N2 interface and N3 interface, respectively. The N2 and N3 reference points may be used to connect standalone non-3GPP accesses to <NUM> Core Network control-plane functions and user-plane functions respectively. In <NUM> Core Network implementations, the control-plane functions and user-plane functions may be separated.

Referring to <FIG>, in accordance with various aspects of the present disclosure, an example of a wireless communication network <NUM> includes at least one UE <NUM> with a modem <NUM>. Further, wireless communication network <NUM> includes at least one base station <NUM>.

The wireless communication network <NUM> may include one or more base stations <NUM>, one or more UEs <NUM>, and a core network <NUM>. The core network <NUM> may provide user authentication, access authorization, tracking, internet protocol (IP) connectivity, and other access, routing, or mobility functions. The base stations <NUM> may interface with the core network <NUM> through backhaul links <NUM> (e.g., S1, etc.). The base stations <NUM> may perform radio configuration and scheduling for communication with the UEs <NUM>, or may operate under the control of a base station controller (not shown). In various examples, the base stations <NUM> may communicate, either directly or indirectly (e.g., through core network <NUM>), with one another over backhaul links <NUM> (e.g., X1, etc.), which may be wired or wireless communication links.

The base stations <NUM> may wirelessly communicate with the UEs <NUM> via one or more base station antennas. In some examples, base stations <NUM> may be referred to as a base transceiver station, a radio base station, an access point, an access node, a radio transceiver, a NodeB, eNodeB (eNB), gNB, Home NodeB, a Home eNodeB, a relay, or some other suitable terminology. The geographic coverage area <NUM> for a base station <NUM> may be divided into sectors or cells making up only a portion of the coverage area (not shown). The wireless communication network <NUM> may include base stations <NUM> of different types (e.g., macro base stations or small cell base stations, described below). Additionally, the plurality of base stations <NUM> may operate according to different ones of a plurality of communication technologies (e.g., <NUM> (New Radio or "NR"), fourth generation (<NUM>)/LTE, <NUM>, Wi-Fi, Bluetooth, etc.), and thus there may be overlapping geographic coverage areas <NUM> for different communication technologies.

In some examples, the wireless communication network <NUM> may be or include one or any combination of communication technologies, including a NR or <NUM> technology, a Long Term Evolution (LTE) or LTE-Advanced (LTE-A) or MuLTEfire technology, a Wi-Fi technology, a Bluetooth technology, or any other long or short range wireless communication technology. In LTE/LTE-A/MuLTEfire networks, the term evolved node B (eNB) may be generally used to describe the base stations <NUM>, while the term UE may be generally used to describe the UEs <NUM>. The wireless communication network <NUM> may be a heterogeneous technology network in which different types of eNBs provide coverage for various geographical regions. For example, each eNB or base station <NUM> may provide communication coverage for a macro cell, a small cell, or other types of cell. The term "cell" is a 3GPP term that can be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc.) of a carrier or base station, depending on context.

A macro cell may generally cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs <NUM> with service subscriptions with the network provider.

A small cell may include a relative lower transmit-powered base station, as compared with a macro cell, that may operate in the same or different frequency bands (e.g., licensed, unlicensed, etc.) as macro cells. A femto cell may also cover a small geographic area (e.g., a home) and may provide restricted access and/or unrestricted access by UEs <NUM> having an association with the femto cell (e.g., in the restricted access case, UEs <NUM> in a closed subscriber group (CSG) of the base station <NUM>, which may include UEs <NUM> for users in the home, and the like).

The communication networks that may accommodate some of the various disclosed examples may be packet-based networks that operate according to a layered protocol stack and data in the user plane may be based on the IP. A user plane protocol stack (e.g., packet data convergence protocol (PDCP), radio link control (RLC), MAC, etc.), may perform packet segmentation and reassembly to communicate over logical channels. For example, a MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use hybrid automatic repeat/request (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE <NUM> and the base stations <NUM>. The RRC protocol layer may also be used for core network <NUM> support of radio bearers for the user plane data. At the physical (PHY) layer, the transport channels may be mapped to physical channels.

The UEs <NUM> may be dispersed throughout the wireless communication network <NUM>, and each UE <NUM> may be stationary or mobile. A UE <NUM> may also include or be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE <NUM> may be a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a smart watch, a wireless local loop (WLL) station, an entertainment device, a vehicular component, a customer premises equipment (CPE), or any device capable of communicating in wireless communication network <NUM>. Additionally, a UE <NUM> may be Internet of Things (IoT) and/or machine-to-machine (M2M) type of device, e.g., a low power, low data rate (relative to a wireless phone, for example) type of device, that may in some aspects communicate infrequently with wireless communication network <NUM> or other UEs. A UE <NUM> may be able to communicate with various types of base stations <NUM> and network equipment including macro eNBs, small cell eNBs, macro gNBs, small cell gNBs, relay base stations, and the like.

UE <NUM> may be configured to establish one or more wireless communication links <NUM> with one or more base stations <NUM>. The wireless communication links <NUM> shown in wireless communication network <NUM> may carry uplink (UL) transmissions from a UE <NUM> to a base station <NUM>, or downlink (DL) transmissions, from a base station <NUM> to a UE <NUM>. The downlink transmissions may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions. Each wireless communication link <NUM> may include one or more carriers, where each carrier may be a signal made up of multiple sub-carriers (e.g., waveform signals of different frequencies) modulated according to the various radio technologies described above. Each modulated signal may be sent on a different sub-carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, etc. In an aspect, the wireless communication links <NUM> may transmit bidirectional communications using frequency division duplex (FDD) (e.g., using paired spectrum resources) or time division duplex (TDD) operation (e.g., using unpaired spectrum resources). Frame structures may be defined for FDD (e.g., frame structure type <NUM>) and TDD (e.g., frame structure type <NUM>). Moreover, in some aspects, the wireless communication links <NUM> may represent one or more broadcast channels.

In some aspects of the wireless communication network <NUM>, base stations <NUM> or UEs <NUM> may include multiple antennas for employing antenna diversity schemes to improve communication quality and reliability between base stations <NUM> and UEs <NUM>. Additionally or alternatively, base stations <NUM> or UEs <NUM> may employ multiple input multiple output (MIMO) techniques that may take advantage of multi-path environments to transmit multiple spatial layers carrying the same or different coded data.

Wireless communication network <NUM> may support operation on multiple cells or carriers, a feature which may be referred to as carrier aggregation (CA) or multi-carrier operation. A carrier may also be referred to as a component carrier (CC), a layer, a channel, etc. The terms "carrier," "component carrier," "cell," and "channel" may be used interchangeably herein. A UE <NUM> may be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation. The base stations <NUM> and UEs <NUM> may use spectrum up to Y MHz (e.g., Y = <NUM>, <NUM>, <NUM>, or <NUM>) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x = number of component carriers) used for transmission in each direction. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

The wireless communications network <NUM> may further include base stations <NUM> operating according to Wi-Fi technology, e.g., Wi-Fi access points, in communication with UEs <NUM> operating according to Wi-Fi technology, e.g., Wi-Fi stations (STAs) via communication links in an unlicensed frequency spectrum (e.g., <NUM>). When communicating in an unlicensed frequency spectrum, the STAs and AP may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.

Additionally, one or more of base stations <NUM> and/or UEs <NUM> may operate according to a NR or <NUM> technology referred to as millimeter wave (mmW or mmwave) technology. For example, mmW technology includes transmissions in mmW frequencies and/or near mmW frequencies. Extremely high frequency (EHF) is part of the radio frequency (RF) in the electromagnetic spectrum. For example, the super high frequency (SHF) band extends between <NUM> and <NUM>, and may also be referred to as centimeter wave. Communications using the mmW and/or near mmW radio frequency band has extremely high path loss and a short range. As such, base stations <NUM> and/or UEs <NUM> operating according to the mmW technology may utilize beamforming in their transmissions to compensate for the extremely high path loss and short range.

As described herein, a UE <NUM>, e.g., via modem <NUM> and/or one or more other components, can be configured to determine a connection gateway for connecting to an access network via base station <NUM> to access a certain service related to a network. For example, the connection gateway can be selected based on the service related to the network available via base station <NUM>, a stored network access preference, etc..

Referring to <FIG> a wireless communications device (e.g., UE <NUM>) may use a mixed access network architecture to support a number of device services. Mixed access network architectures <NUM>, <NUM>, and <NUM> illustrate examples of non-roaming, roaming, and home-routed architectures for implementing the various aspects.

In various aspects, a wireless communications device that accesses the <NUM> Core Network over a standalone non-3GPP access can, after attachment, support non-access stratum (NAS) signaling with <NUM> Core Network control-plane functions using the N1 reference point. When a wireless communications device is connected via a NG-RAN and via standalone non-3GPP accesses, multiple N1 instances can exist for the wireless communications device, i.e., there may be one N1 instance over NG-RAN and one N1 instance over non-3GPP access.

A wireless communications device simultaneously connected to the same <NUM> Core Network of a public land mobile network (PLMN) over 3GPP access and non-3GPP access may be served by a single access and mobility management function (AMF) if the selected N3IWF is located in the same PLMN as the 3GPP access.

When a wireless communications device is connected to a 3GPP access of a PLMN, if the wireless communications device selects the N3IWF and the N3IWF is located in a PLMN different from the PLMN of the 3GPP access (e.g. a different visited PLMN (VPLMN) or the home PLMN (HPLMN)) the wireless communications device may be served separately by the two PLMNs. The wireless communications device may be registered with two separate AMFs. Protocol data unit (PDU) sessions over the 3GPP access may be served by visited (V)-session management functions (SMFs) different from the V-SMF serving the PDU sessions over the non-3GPP access. The PLMN selection for the 3GPP access may not depend on the N3IWF selection. If a wireless communications device is registered over a non-3GPP, the wireless communications device may perform PLMN selection for the 3GPP access independently of the PLMN to which the N3IWF belongs.

A wireless communications device may establish an IPSec tunnel with the N3IWF to attach to the <NUM> Core Network over untrusted non-3GPP access. The wireless communications device may be authenticated by and attached to the <NUM> Core Network during the IPSec tunnel establishment procedure.

As illustrated in <FIG>, reference points specific to the non-3GPP access include Y1, a reference point between the UE <NUM> and the non-3GPP access (e.g. WLAN). This depends on the non-3GPP access technology and is outside the scope of 3GPP; Y2, a reference point between the non-3GPP access and the N3IWF for the transport of NWu traffic; and NWu, a reference point between the UE and N3IWF for establishing secure tunnel(s) between the UE and N3IWF so that control-plane and user-plane exchanged between the UE and the <NUM> Core Network is transferred securely over untrusted non-3GPP access.

Referring now to <FIG>, there is illustrated a non-roaming architecture for <NUM> Core Network with non-3GPP access. The illustrated access network architecture <NUM> and the network functions can be directly connected to non-3GPP access. This architecture supports service based interfaces for AMF <NUM>, SMF <NUM> and/or other NFs that may not be represented in the figure. In an example, access network architecture <NUM> may be or may include one or more components of a core network (e.g., core network <NUM>) and/or of a radio access network (RAN). Access network architecture <NUM> includes 3GPP access <NUM>, which may include one or more RAN nodes and/or other nodes, not explicitly shown, to facilitate 3GPP access of the UE <NUM> to the AMF <NUM> and/or other network components (e.g., one or more base stations, mobility management entity (MME), etc.). Access network architecture <NUM> may also include non-3GPP access <NUM>, which may be a non-trusted access and may include one or more RAN nodes (e.g., a wireless local area network (WLAN) access point) to facilitate non-3GPP access of the UE <NUM> to the AMF <NUM> and/or other network components (e.g., via N3IWF <NUM>). Moreover, access network architecture <NUM> may include a user plane function (UPF) <NUM> and/or a data network <NUM>.

In various aspects, the two N2 instances may apply to a single AMF <NUM> for a wireless communications device, such as UE <NUM>, which is simultaneously connected to the same <NUM> Core Network over 3GPP access <NUM> and non-3GPP access <NUM>. Similarly, the two N3 instances may apply to different UPFs <NUM> when different PDU sessions are activated over 3GPP access <NUM> and non-3GPP access <NUM>.

Referring now to <FIG>, there is illustrated a roaming architecture for LBO for <NUM> Core Network with non-3GPP access (e.g., via a gateway with a N3IWF) in the VPLMN. The illustrated access network architecture <NUM> and the network functions can be directly connected to support non-3GPP access. The illustrated architecture supports service based interfaces for AMF <NUM>, SMF <NUM>, and/or other NFs that may not be represented in the figure.

In various aspects, the two N2 instances may apply to a single AMF <NUM> for a wireless communications device, such as UE <NUM>, which is connected to the <NUM> Core Network over 3GPP access <NUM> and non-3GPP access <NUM> simultaneously. Similarly, the two N3 instances in may apply to different UPFs when different PDU sessions are activated over 3GPP access <NUM> and non-3GPP access <NUM>.

Referring now to <FIG>, there is illustrated a home-routed roaming architecture for <NUM> Core Network with non-3GPP access (e.g., via a gateway with a N3IWF) in the same VPLMN as 3GPP access. The illustrated home-routed access network architecture <NUM> and the network functions may be directly connected to support non-3GPP access. The two N2 instances may apply to a single AMF <NUM> for a UE <NUM> which is connected to the <NUM> Core Network over 3GPP access <NUM> and non-3GPP access <NUM> simultaneously. Access network architecture <NUM> may also include a vSMF <NUM> and UPF <NUM> of the VPLMN and a hSMF <NUM> and UPF <NUM> of the HPLMN.

Referring to <FIG>, a wireless communications device (e.g., UE <NUM>) may use multiple access network architectures to support a number of device services via multiple core networks. Wireless communication system <NUM> illustrates example connectivity between both a 5GC and evolved packet core (EPC) using 3GPP and non-3GPP access networks.

With the migration from EPC, which is typically associated with 3GPP networks including LTE deployment, to 5GC and the NR deployment, an operator may decide to migrate services gradually. For example, an operator may decide to maintain voice over Internet Protocol (VoIP) services over EPC, and later migrate them to 5GC. Also, for example, an operator may decide to deploy in the 5GC services that are available in EPC (over both 3GPP access and via an evolved Packet Data Gateway (ePDG)) only over the <NUM> RAN, but not on new N3IWF deployments.

In such scenario, access via N3IWF to 5GC may not initially support VoIP. Therefore, if a wireless communications device is configured to support VoIP (e.g. use Internet Protocol (IP) Multimedia Subsystem (IMS) APN), the wireless communications device (e.g., UE <NUM>) may prioritize the discovery of an ePDG (e.g., over a N3IWF) and establish a PDU session for VoIP via the ePDG to the EPC. For other scenarios (e.g., non-IMS APN), the wireless communication device (e.g., UE <NUM>) may not prioritize discovery of an ePDG or may otherwise attempt to discover a N3IWF gateway (e.g., instead of or before ePDG attempts) to establish a session with a 5GC.

Various aspects may enable seamless mobility between connectivity to the EPC <NUM> or the 5GC <NUM>. For example, a UE <NUM> can access the EPC <NUM> via ePDG <NUM> and connectivity to 5GC <NUM> via NG RAN <NUM>. This may be beneficial when services already deployed in EPC <NUM> (including via ePDG <NUM>) to 5GC <NUM> via NG RAN <NUM>. In such aspects the wireless communications device, such as UE <NUM>, may be connected via a 3GPP access to the EPC <NUM>, and via N3IWF <NUM> to the 5GC <NUM>. For example the wireless communications device, such as UE <NUM>, may originally connect via NG-RAN <NUM> and/or N3IWF <NUM> to the 5GC <NUM>, and then a handover from NG-RAN <NUM> to E-UTRAN <NUM> occurred. In such case, in fact, if WLAN coverage is available, there may be no technical reason for moving the PDU sessions via the N3IWF <NUM> to the EPC <NUM>.

In an aspect, a <NUM> capable wireless communications device, such as UE <NUM>, may connect first via E-UTRAN <NUM> to the EPC <NUM>, but may be capable of discovering an N3IWF <NUM> and connecting to the 5GC <NUM> via N3IWF <NUM>. Because the wireless communications device (e.g., UE <NUM>) may be handed over to the NG-RAN <NUM>, it may be beneficial to allow the wireless communications device to select an N3IWF <NUM> (if available) instead of limiting the wireless communications device to connect to an ePDG <NUM>.

In another aspect, the PDN connection may be established in EPC <NUM> via an ePDG <NUM> by a 5GC capable wireless communications device, such as UE <NUM>, with the ability to handover the PDN connection to the 5GC <NUM> when the wireless communications device hands over to a NG-RAN <NUM>), the wireless communications device may adopt PGW selection a mechanism. For example, the wireless communications device (e.g., UE <NUM>) upon PDN connection establishment via the ePDG <NUM>, may provide an indication to the ePDG <NUM> that the wireless communications device is 5GC capable, so that the ePDG <NUM> performs SMF/PGW-C selection considering, in addition to the APN provided by the wireless communications device, also the ability of the wireless communications device to connect to the 5GC <NUM>. Moreover, for example, EPC may include a PGW <NUM> that may facilitate access to a SMF/UPF-PGW <NUM> shared between, or otherwise communicatively coupled to both of, EPC <NUM> and 5GC <NUM>. 5GC <NUM> may include an AMF <NUM> (e.g., for similar purposes) as well.

Referring to <FIG> for example, a method <NUM> of wireless communication in operating a wireless communications device (e.g., UE <NUM>) according to the above-described aspects to select a connection gateway for supporting services operating on the wireless communications device includes one or more of the herein-defined actions. A 5GC-capable wireless communications device configured to access non-3GPP access over either EPC or 5GC may select a gateway for connectivity to the network over a non-3GPP access.

For example, at block <NUM>, services requiring network access can be identified. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM> may (optionally) identify the one or more services requiring network access (e.g., connection or access to one or more connection gateways). In an example, the one or more services may be identified as services corresponding to a certain data network name (DNN) or access point name (APN) and in which the APN can be identified based on a configured mapping between an application/service and the DNN or APN. In an example, the base station <NUM> can advertise one or more services (e.g., in a broadcast message) based on DNN, APN, etc., and the connectivity selection component <NUM> can determine and/or select one or more services for requesting from the base station <NUM>.

In block <NUM>, a connection gateway for a requesting service may be selected (e.g., based at least in part on a stored network access preference). In an example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may select the connection gateway for requesting service. For example, the connectivity selection component <NUM> may examine a stored network access preference and/or a capability of the device to determine whether the wireless communications device is configured to prioritize connectivity via an N3IWF/via 5GC or via EPC/via ePDG, etc. In various aspects, the stored network access preference may include, on a per DNN/APN/service/application, a configuration of whether priority is given to connectivity to 5GC or EPC, etc. In other aspects, the stored network access preference may include whether the service is available in EPC. In other aspects, the stored network access preference may include whether the service is available in 5GC.

In block <NUM>, the selected connection gateway can be connected to. For example the a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may connect to the selected connection gateway, which may include discovering the type of connection gateway selected (e.g., N3IWF with respect to ePDG) and establishing connectivity to the discovered gateway. Further, if the selected type connection gateway is an N3IWF and no N3IWF is available, the connectivity selection component <NUM> may discover an ePDG and attempt to connect to the ePDG.

Referring to <FIG> for example, a method <NUM> of wireless communication in operating a wireless communications device (e.g., UE <NUM>) according to the above-described aspects to select a connection gateway for supporting services operating on the wireless communications device includes one or more of the herein-defined actions.

For example, at block <NUM>, a service can be identified. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may (optionally) identify the service. For example, the service may be specified for, or related to, a network or network access, and/or may require network access, as described herein. In an example, the one or more services may be identified as services corresponding to a certain DNN or APN, as described, and in which the APN can be identified based on a configured mapping between an application/service and the DNN or APN. In one example, the service may correspond to an IMS or non-IMS system. Whether the service relates to IMS or non-IMS can be determined based on the DNN or APN, based on an indicator in information received from the network regarding the service (e.g., in one or more broadcast messages from the network), and/or the like. For example, a base station <NUM> can advertise the service, and the UE <NUM> can determine to connect to the service based at least in part on detecting that the service is advertised by the base station <NUM>, a list of services stored in the UE <NUM>, etc. In addition, the UE <NUM> can determine to connect to the service based on a request from an application executing on the UE <NUM> (e.g., to a VoIP service based on a request from a VoIP application, etc.).

For example, at block <NUM>, it can be determined whether to prioritize a type of connection gateway for using the service. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may (optionally) determine whether to prioritize the type of connection gateway (and/or a specific connection gateway) for using the service. For example, this can be determined based on the service identified as related to the network and/or as determined by the UE <NUM> to utilize in communicating with the network. In one example, whether to prioritize the type of connection gateway can include determining whether to prioritize the type of connection gateway over another type of connection gateway. For example, this can include determining to prioritize a connection gateway using non-3GPP access for certain types of services (e.g., services related to an IMS), determining not to prioritize the type of connection gateway using non-3GPP access for other types of services (e.g., services not related to IMS), etc. In another example, determining whether to prioritize the type of connection gateway using the non-3GPP access can include determining whether, for the determined service, type of service (e.g., IMS, non-IMS, etc.), and/or the like, the UE <NUM> is configured to select a connection gateway in non-3GPP access configurations. If so, for example, the connectivity selection component <NUM> can select the connection gateway based on a stored network access preference at least for certain types of services and/or based on a type of the connection gateway.

For example, where it is determined, at block <NUM>, to prioritize a type of connection gateway, method <NUM> can include, at block <NUM>, selecting the connection gateway based on a stored network access preference. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may (optionally) select the connection gateway based on the stored network access preference and/or based on a type of the connection gateway where it determines to select the connection gateway for the service using the non-3GPP access. As described, this can include determining that the UE <NUM> is configured to prioritize connectivity in non-3GPP access configurations for certain types of services (e.g., services related to an IMS). Moreover, as described, the UE <NUM> can store the stored network access preference (e.g., in a memory, such as memory <NUM>) indicating a preference for one or more types of connection gateway (e.g., ePDG, N3IWF gateway, etc.), a ranked list of preferred types of connection gateways, etc. Thus, the connectivity selection component <NUM> may attempt to connection to the preferred type of connection gateway, may attempt connection to one or more connection gateways according to the ranked list of preferred types, etc. Moreover, as described in an example, the stored network access preference(s) may be indicated per DNN and/or APN, per service or type of service, network or type of network, and/or the like, and the connectivity selection component <NUM> may determine the appropriate preference(s) to apply in selecting the connection gateway based on the service, corresponding DNN/APN, network, etc..

In a specific example, selecting the connection gateway at <NUM> may include discovering the type of connection gateway selected (e.g., N3IWF wrt ePDG) and establishing connectivity to the discovered gateway, if any, and/or if the selected or preferred type of connection gateway is an N3IWF and no N3IWF gateway is available, discovering an ePDG and attempting to connect to the ePDG. Thus, for example, where a gateway corresponding to the stored network access preference is not available, the connectivity selection component <NUM> may select another type of connection gateway, at least in some examples. In other examples, the connectivity selection component <NUM> may not select a connection gateway and/or may return an error in a process to connect to the network. In another example, where a gateway corresponding to the stored network access preference is not available, the connectivity selection component <NUM> may attempt connection in a different network (e.g., to another connection gateway in the different network).

For example, where it is determined, at block <NUM>, to not prioritize a type of connection gateway, method <NUM> can include, at block <NUM>, selecting the connection gateway regardless of a stored network access preference. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may (optionally) select the connection gateway regardless of the stored network access preference where it determines to not select the type of connection gateway for the service using the non-3GPP access. As described, this can include determining that the UE <NUM> is not configured to prioritize connectivity in non-3GPP access configurations for certain types of services (e.g., services related to a non-IMS). In this example, the UE <NUM> can attempt connection to a certain type of connection gateway regardless of the stored network access preference. For example, the UE <NUM> can attempt connection to a N3IWF gateway where it determines to not prioritize the connection gateway for the service using the non-3GPP access. In addition, the UE <NUM> can attempt connection to other types of connection gateways (e.g., ePDG) where connection to the first gateway (e.g., a N3IWF gateway) fails.

In either case, at block <NUM>, the selected connection gateway can be connected to. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may (optionally) connect to the selected connection gateway. In an example, the connectivity selection component <NUM> may transmit a request to connect to the selected connection gateway via one or more RAN nodes and/or nodes of the corresponding core network (e.g., EPC, 5GC, etc.).

Referring to <FIG> for example, a method <NUM> of wireless communication in operating a wireless communications device (e.g., UE <NUM>) according to the above-described aspects to indicate whether the wireless communications device has <NUM> capability can include one or more of the herein-defined actions. A 5GC capable wireless communications device, such as a UE <NUM>, when establishing connectivity to a data network (identified by an APN) may provide an indication of whether the wireless communications device is 5GC capable.

For example, in block <NUM> a <NUM> capability indicator can be inserted in a payload. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may insert the <NUM> capability indicator into the payload. In various aspects, the wireless communications device may provide the 5GC capability indication in the same information element in which the wireless communications device provides the APN identifying the data network, i.e. the IKEv2 Identification Payload Response (IDr).

In various aspects, the <NUM> capability indicator may alternatively include a new Identification Type Field value for the IDr payload, (e.g. UE Capability, and set to a value "5GC"). The wireless communications device may provide an IDr payload for the APN and an additional IDr payload for the wireless communications device capability. In other aspects, the <NUM> capability indicator may include a specific bit or combination of bits in the ID_KEY_ID Identification Type Field of the IDr payload to provide the wireless communications device capability indication. In other aspects, the <NUM> capability indicator may be encoded together with the APN by adding a marker indication 5GC, e.g. if the APN is "Internet-<NUM>. mcc222.3gppnetwork. org" then the marked APN with 5GC indication is if the APN is "Internet-<NUM>. mcc222.3gppnetwork. In other aspects, the <NUM> capability indicator may be encoded together with the APN by performing network address identifier (NAI) decoration, by adding an indication 5GC, e.g. if the APN is "Internet-<NUM>. mcc222.3gppnetwork. org", then the decorated NAI may be if the APN is "5GC. Internet-<NUM>. mcc222.3gppnetwork. org" or if the APN is "5GC@Internet-<NUM>. mcc222.3gppnetwork.

In block <NUM>, the payload may be transmitted over an access network. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the UE <NUM>, may transmit the payload over the access network (e.g., the selected data network). In so doing, the wireless communications device may indicate to the receiving network node that the transmitting device is <NUM> capable and thus its services may be handed over from a non-3GPP access network to a <NUM> access network as needed.

Referring to <FIG> for example, a method <NUM> of wireless communication in operating a wireless communications device (e.g., base station <NUM>) according to the above-described aspects to receive an indication of whether a UE <NUM> has <NUM> capability can include one or more of the herein-defined actions.

For example, in block <NUM> a payload, including a <NUM> capability indicator, can be received over an access network. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the base station <NUM>, may receive the payload, including the <NUM> capability indicator, over the access network. For example, the connectivity selection component <NUM> can receive the payload from a UE <NUM> to indicate whether the UE <NUM> is capable of supporting <NUM> communications, related services, etc., as described above in reference to <FIG>.

For example, in block <NUM> a connection gateway used by a wireless communication device (e.g., UE <NUM>) to support a service can be modified based on the <NUM> capability indicator. For example, a connectivity selection component <NUM> (described in <FIG>), e.g., in conjunction with processor <NUM>, transceiver <NUM>, etc. of the base station <NUM>, may modify, based on the <NUM> capability indicator, the connection gateway used by the wireless communication device (e.g., UE <NUM>) to support the service. For example, the connectivity selection component <NUM> can select a connection gateway to include a <NUM> gateway (e.g., a N3IWF gateway) where the <NUM> capability indicator indicates that the UE <NUM> can support <NUM>. In an example, the connectivity selection component <NUM> can select the connection gateway at least in part by facilitating communications between the UE <NUM> and the selected connection gateway to provide the service requested by the UE <NUM>.

Referring to <FIG>, one example of an implementation of UE <NUM> may include a variety of components, some of which have already been described above, but including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM>. Further, the one or more processors <NUM>, modem <NUM>, memory <NUM>, transceiver <NUM>, RF front end <NUM> and one or more antennas <NUM>, may be configured to support voice and/or data calls (simultaneously or non-simultaneously) in one or more radio access technologies.

In an aspect, the one or more processors <NUM> can include a modem <NUM> that uses one or more modem processors. The various functions may be included in modem <NUM> and/or processors <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver <NUM>. In other aspects, some of the features of the one or more processors <NUM> and/or modem <NUM> associated with the connectivity selection component <NUM> may be performed by transceiver <NUM>.

Also, memory <NUM> may be configured to store data used herein and/or local versions of applications <NUM> being executed by at least one processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or at least one processor <NUM>, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining and/or data associated therewith.

Receiver <NUM> may include hardware, firmware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). Additionally, receiver <NUM> may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, SNR, RSRP, RSSI, etc. Transmitter <NUM> may include hardware, firmware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium).

The modem <NUM> and/or processor <NUM> can include the connectivity selection component <NUM> that can include one or more subcomponents to perform aspects of the methods described in <FIG>.

Referring to <FIG>, one example of an implementation of base station <NUM> may include a variety of components, some of which have already been described above, but including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM>.

Claim 1:
A method of selecting a connection gateway for a service operating on a wireless communications device, comprising:
identifying (<NUM>), by a processor of the wireless communications device, a service;
determining, by the processor and based at least in part on the service, whether to prioritize (<NUM>) a type of connection gateway to utilize in connecting to the service;
where if the processor determines to prioritize the type of connection gateway, selecting (<NUM>), by the processor, a connection gateway for the service based at least in part on a stored network access preference for the service, wherein the stored network access preference indicates whether to select an evolved Packet Data Gateway, ePDG, or a gateway with a non-3GPP InterWorking Function, N3IWF, and
connecting, by the processor, to the service via the connection gateway, based at least in part on the stored network access preference, to the ePDG or the gateway with the N3IWF;
where if the processor determines not to prioritize the type of connection gateway, selecting (<NUM>), by the processor, the connection gateway for the service regardless of the stored network access preference for the service; and
connecting (<NUM>), by the processor, to the service via the connection gateway