Patent Description:
The evolution of wireless communication to fifth generation (<NUM>) standards and technologies provides higher data rates and greater capacity with improved reliability and lower latency, which enhances mobile broadband services. <NUM> technologies also provide new classes of service for vehicular networking, fixed wireless broadband, and the Internet of Things (IoT).

For a class of service, such as enhanced mobile broadband, <NUM> networks provide higher data rates than conventional cellular systems. However, it is still desirable to use WLAN networks for mobile broadband in various settings, such as a home or office, or to reduce power consumption in mobile devices.

Offloading data traffic from a cellular network to a Wireless Local Area Network (WLAN) and handing over network connections from cellular to WLAN (e.g., Wi-Fi) reduces the cost of data transmission for end users and network operators. However, conventional techniques for interoperability between cellular and WLANs lack core network interfaces (reference points), gateways, and management interfaces to cohesively manage cellular and WLAN infrastructure, which results in challenges with handovers, dropped data traffic and context, unreliable WLAN Access Points (APs), varying levels of service quality, or the like.

<CIT> describes a method and a system applied in a WLAN for acquiring offload information. The method includes: deploying a mobile server in the WLAN; the mobile server acquiring WLAN offload information, and sending the WLAN offload information to an offload traffic control network element in a cellular or fixed network; and the offload traffic control network element executing an offload traffic decision according to the offload information.

<CIT> describes a wireless local area network discovery and selection method, device and system, and a terminal.

<CIT> describes a method of sending information to a radio access node (RAN) of a first radio access technology (RAT) regarding one or more coexisting RAN's of a second RAT. In particular, the information comprises a number of parameters and operating modes used by the one or more coexisting radio access nodes.

In accordance with the invention, there is provided: a method to monitor and manage a WLAN access point in a WLAN network by a WLAN gateway as recited by claim <NUM>; a WLAN gateway device as recited by claim <NUM>; and a system as recited by claim <NUM>.

The WLAN gateway device includes a core network interface, and a processor and memory system to implement a WLAN gateway manager application. The core network interface may include one or more core network interfaces, such as an N2a interface and/or an N2b interface for facilitating communications between a core network function, such as an AMF and the WLAN gateway device. The WLAN gateway manager application is, for example, an Application Programming Interface, API, which with the core network interface(s) defines an interface including requests, responses, commands, and procedures to add control-plane signaling over WLAN to integrate mobility management and network management between the cellular network and WLAN networks.

Aspects of a cellular-WLAN network interface are described with reference to the following drawings. The same numbers are used throughout the drawings to reference like features and components:.

This document describes improvements in mobility for user equipment (UE) between cellular and Wireless Local Area Networks (WLAN) in fifth generation new radio (5GNR) wireless networks, as well as 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA) networks. A cellular-WLAN network interface is introduced to facilitate monitoring and managing of WLAN networks and Access Points (APs) by a WLAN gateway (also referred to herein as a WLAN gateway device, or WLAN gateway or WLAN access gateway) of a cellular network, and to facilitate handoffs of UE between WLAN APs, between WLAN networks, and between WLAN networks and cellular networks. The cellular-WLAN network interface enables an Access and Mobility Management Function (AMF) in a <NUM> network or a Mobility Management Entity (MME) in an E-UTRA network to request information from UE and WLAN APs, manage the operating configuration of WLAN APs, and initiate UE handoffs.

The techniques described provide interfaces, requests, commands, and procedures (e.g., interfaces, requests, commands, and procedures that form the cellular-WLAN network interface) to connect WLAN Access Points (APs) and user equipment (UE) to the AMF or MME of a cellular network. These techniques serve to better integrate the operation and management of WLAN networks with cellular networks. By integrating the management of cellular network resources and WLAN network resources, improvements in network utilization, network capacity, interference mitigation, handoff reliability, or the like are provided.

The AMF or MME uses the requests implemented by the cellular-WLAN network interface to receive configurations of operating parameters from the UE and/or WLAN APs. The AMF or MME can also request measurement from the UE and/or WLAN APs of serving or neighbor WLAN APs. By integrating the management and measurement of the WLAN and cellular networks, mobility management techniques from the cellular network are extended to WLAN networks to improve user-plane data throughput and reliability.

While features and concepts of the described methods, devices, systems, and means for a cellular-WLAN network interface can be implemented in any number of different environments, systems, devices, and/or various configurations, aspects of the cellular-WLAN network interface are described in the context of the following example devices, systems, and configurations.

<FIG> illustrates an example environment <NUM>, which includes multiple user equipment <NUM> (UE <NUM>), illustrated as UE <NUM>, UE <NUM>, and UE <NUM>. Each UE <NUM> can communicate with one or more cellular base stations <NUM> (illustrated as base stations <NUM> and <NUM>) through one or more wireless communication links <NUM> (wireless link <NUM>). In this example, the UE <NUM> is implemented as a smartphone. Although illustrated as a smartphone, the UE <NUM> may be implemented as any suitable computing or electronic device, such as a mobile communication device, a modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, and the like. The base stations <NUM> (e.g., an Evolved Universal Terrestrial Radio Access Network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB, Next Generation Node B, gNode B, gNB, or the like) may be implemented in a macrocell, microcell, small cell, picocell, or the like, or any combination thereof.

The base stations <NUM> communicate with the UE <NUM> via the wireless link <NUM>, which may be implemented as any suitable type, or any suitable combination of types, of wireless link. The wireless link <NUM> can include a downlink of data and control information communicated from the base stations <NUM> to the UE <NUM>, an uplink of other data and control information communicated from the UE <NUM> to the base station <NUM>, or both. The wireless link <NUM> may include one or more wireless links or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards such as 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE), Fifth Generation New Radio (<NUM> NR), and so forth. Multiple wireless links <NUM> may be aggregated in a carrier aggregation to provide a higher data rate for the UE <NUM>. Multiple wireless links <NUM> from multiple base stations <NUM> may be configured for Coordinated Multipoint (CoMP) communication with the UE <NUM>.

The base stations <NUM> are collectively a Radio Access Network <NUM> (RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5GNR RAN or NR RAN). The base stations <NUM> and <NUM> in the RAN <NUM> are connected to a cellular core network (core network) <NUM>. The core network <NUM> may include a <NUM> core network, an Evolved Packet Core (EPC), or a combination of both.

The base stations <NUM> and <NUM> connect, at <NUM> and <NUM> respectively, to the core network <NUM> via an NG2 interface for control-plane signaling and via an NG3 interface for user-plane data communications when connecting to <NUM> core network functions. The base stations <NUM> and <NUM> connect, at <NUM> and <NUM> respectively, to EPC entities via an S1 interface for control-plane signaling and user-plane data communications when connecting to EPC core network entities.

In addition to connections to core network, base stations <NUM> may communicate with each other. The base stations <NUM> and <NUM> communicate, at <NUM> via an Xn interface if the base stations <NUM> are <NUM> base stations, or via an X2 interface if the base stations <NUM> are E-UTRA base stations.

The core network <NUM> includes entities and/or functions to support access and mobility for UEs <NUM>. The core network <NUM> includes entities, functions, and/or gateways that support connectivity to the Internet <NUM> and remote service(s) <NUM>, which are described below with respect to <FIG> and <FIG>.

The UE <NUM> also can connect to the Internet <NUM> using a WLAN connection <NUM> to a WLAN AP <NUM>, illustrated as WLAN APs <NUM> and <NUM>, connected to the Internet <NUM>, via the network interfaces <NUM> and <NUM>. The WLAN AP <NUM> may be located in a user's home, an office, airport, coffee shop, and so forth. Each WLAN AP <NUM> may be independently operated, such as in a user's home, may be part of a WLAN network <NUM>, which is illustrated as including WLAN AP <NUM> and <NUM>. For example, a WLAN network <NUM> may be an enterprise network or a public network of WLAN APs <NUM> operated by a wireless network operator. The WLAN wireless network operator may be the same as the operator of the RAN <NUM> or different than the operator of the RAN <NUM>.

<FIG> illustrates an example environment <NUM> in which various aspects of a cellular-WLAN network interface are shown as generally related to functions and interfaces in a 5GNR core network <NUM>. The core network <NUM> may include additional functions and interfaces that are omitted from <FIG> for the sake of clarity.

The UE <NUM> may connect using various radio access technologies, such as the wireless link <NUM> using a cellular radio access technology to the base station <NUM> or <NUM>. Additionally, the UE <NUM> may connect using a WLAN connection <NUM>, shown as <NUM> and <NUM>, with a WLAN network <NUM>, such as a trusted WLAN network <NUM> or an untrusted WLAN network <NUM>. The trusted WLAN network <NUM> and the untrusted WLAN network <NUM> include one or more WLAN APs <NUM>, such as WLAN AP <NUM> and WLAN AP <NUM>. A trusted WLAN, and the WLAN APs <NUM> in that trusted WLAN, become trusted by being authenticated to, and thus trusted by, the cellular network that authenticates the trusted WLAN. An untrusted WLAN is a WLAN that is not authenticated by the cellular network to establish a trusted relationship.

Interconnections between services or functions to the core network <NUM> and within the core network <NUM> are defined in terms of interfaces or reference points. New interfaces are added to the core network <NUM> by the techniques described herein to implement a cellular-WLAN network interface and are illustrated in <FIG> with a heavier line weight for the sake of clarity. User-plane data for the UE <NUM>, when connected via the base station <NUM>, is sent over an N3 interface <NUM> between the base station <NUM> and a User Plane Function (UPF) <NUM>, which in turn is connected to the Internet <NUM>. Control-plane communications for the UE <NUM>, when connected to the base station <NUM>, is sent over an N2 interface <NUM> between the base station <NUM> and an Access and Mobility Management Function (AMF) <NUM>. The AMF <NUM> provides control-plane functions such as registration and authentication of multiple UE <NUM>, authorization, mobility management, or the like in the 5GNR network.

The trusted WLAN network <NUM> and the untrusted WLAN network <NUM> are connected to the core network <NUM> by SWn interfaces <NUM> and <NUM>, respectively. The SWn interface <NUM> connects the trusted WLAN network <NUM> to a Trusted WLAN Access Gateway (TWAG) <NUM> (also referred to herein as a WLAN gateway device, or WLAN gateway or WLAN access gateway). An N3a interface <NUM> is added to the core network <NUM> between the TWAG <NUM> and the User Plane Function (UPF) <NUM>. The N3a interface <NUM> is used to communicate user-plane data between the UE <NUM> and the Internet <NUM>, when the UE <NUM> is connected via the trusted WLAN network <NUM>. The SWn interface <NUM> connects the untrusted WLAN network <NUM> to an Untrusted WLAN Access Gateway (UWAG) <NUM> (also referred to herein as a WLAN gateway device, or WLAN gateway or WLAN access gateway). An N3b interface <NUM> is added to the core network <NUM>, between the UWAG <NUM> and the User Plane Function (UPF) <NUM>. The N3b interface <NUM> is used to communicate user-plane data between the UE <NUM> and the Internet <NUM>, when the UE <NUM> is connected via the untrusted WLAN network <NUM>.

New interfaces are added between the AMF <NUM> and the TWAG <NUM> and between the AMF <NUM> and the UWAG <NUM> to enable mobility management, as well as network monitoring and management of WLAN networks <NUM> by the AMF <NUM>. An N2a interface <NUM> is added to the core network <NUM> between the AMF <NUM> and the TWAG <NUM> and an N2b interface <NUM> is added to the core network <NUM> between the AMF <NUM> and the UWAG <NUM>. The N2a interface <NUM> and the N2b interface <NUM> define an interface including requests, responses, commands, and procedures to add control-plane signaling over WLAN to integrate mobility management and network management between the cellular network and WLAN networks <NUM>.

<FIG> illustrates an example environment <NUM> as generally relating to entities, gateways, and interfaces in an EPC core network <NUM>. The core network <NUM> may include additional entities, gateways, and interfaces that are omitted from <FIG> for the sake of clarity.

The UE <NUM> may connect using various radio access technologies, such as the wireless link <NUM> using a cellular radio access technology to the base station <NUM> or <NUM>. Additionally, the UE <NUM> may connect using the WLAN connection <NUM>, shown as <NUM> and <NUM>, with the trusted WLAN network <NUM> or the untrusted WLAN network <NUM>, respectively.

Interconnections between services or functions to the core network <NUM> and within the core network <NUM> are defined in terms of interfaces or reference points. New interfaces are added to the core network <NUM> by the techniques described herein to implement a cellular-WLAN network interface and are illustrated in <FIG> with a heavier line weight for the sake of clarity. User-plane data for the UE <NUM>, when connected via the base station <NUM>, is relayed via a Serving Gateway (S-GW) <NUM> to a Packet Data Network Gateway (P-GW) <NUM>, which in turn is connected to the Internet <NUM>. The base station <NUM> is connected to the S-GW <NUM> by an S1-U interface <NUM> and the S-GW <NUM> is connected to the P-GW <NUM> by an S5 interface <NUM>. Control-plane communications for the UE <NUM>, connected to the base station <NUM>, is sent over an S1-MME interface <NUM> between the base station <NUM> and a Mobility Management Entity (MME) <NUM>.

The trusted WLAN network <NUM> and the untrusted WLAN network <NUM> are each connected to the core network <NUM> by SWn interfaces <NUM> and <NUM>, respectively. The SWn interface <NUM> connects the trusted WLAN network <NUM> to the TWAG <NUM>. User-plane data for the UE <NUM>, when connected via the trusted WLAN network <NUM>, is sent over an S2a interface <NUM> between the TWAG <NUM> and the P-GW <NUM>, which in turn is connected to the Internet <NUM>. The SWn interface <NUM> connects the untrusted WLAN network <NUM> to an Evolved Packet Data Gateway (ePDG) <NUM>. User-plane data for the UE <NUM>, when connected via the untrusted WLAN network <NUM>, is sent over an S2b interface <NUM> between ePDG <NUM> and the P-GW <NUM>, which in turn is connected to the Internet <NUM>.

New interfaces are added between the MME <NUM> and the TWAG <NUM> and between the MME <NUM> and the ePDG <NUM> to enable mobility management via WLAN and network monitoring and management of WLAN networks by the MME <NUM>. An S2a-MME interface <NUM> is added to the core network <NUM> between the MME <NUM> and the TWAG <NUM>, and an S2b-MME interface <NUM> is added between the MME <NUM> and the ePDG <NUM>. The S2a-MME interface <NUM> and the S2b-MME interface <NUM> define an interface including requests, responses, commands, and procedures to add control-plane signaling over WLAN to integrate mobility management and network management between the cellular network and WLAN networks <NUM>.

<FIG> illustrates an example device diagram <NUM> of the multiple UE <NUM> and the base stations <NUM>. The multiple UE <NUM> and the base stations <NUM> may include additional functions and interfaces that are omitted from <FIG> for the sake of clarity. The UE <NUM> includes antennas <NUM>, a radio frequency front end <NUM> (RF front end <NUM>), an LTE transceiver <NUM>, and a 5GNR transceiver <NUM> for communicating with base stations <NUM> in the <NUM> NR and E-UTRA RANs <NUM>. The RF front end <NUM> of the UE <NUM> can couple or connect the LTE transceiver <NUM>, and the 5GNR transceiver <NUM> to the antennas <NUM> to facilitate various types of wireless communication. The antennas <NUM> of the UE <NUM> may include an array of multiple antennas that are configured similar to or differently from each other. The antennas <NUM> and the RF front end <NUM> can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3GPP LTE and 5GNR communication standards and implemented by the LTE transceiver <NUM>, and/or the 5GNR transceiver <NUM>. Additionally, the antennas <NUM>, the RF front end <NUM>, the LTE transceiver <NUM>, and/or the 5GNR transceiver <NUM> may be configured to support beamforming for the transmission and reception of communications with the base stations <NUM>. By way of example and not limitation, the antennas <NUM> and the RF front end <NUM> can be implemented for operation in sub-gigahertz bands, sub-<NUM> bands, and/or above <NUM> bands that are defined by the 3GPP LTE and 5GNR communication standards.

The UE <NUM> also includes processor(s) <NUM> and computer-readable storage media <NUM> (CRM <NUM>). The processor <NUM> may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media described herein excludes propagating signals. CRM <NUM> may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data <NUM> of the UE <NUM>. The device data <NUM> includes user data, multimedia data, beamforming codebooks, applications, and/or an operating system of the UE <NUM>, which are executable by processor(s) <NUM> to enable user-plane communication, control-plane signaling, and user interaction with the UE <NUM>.

CRM <NUM> also includes a user equipment manager <NUM>. Alternately or additionally, the user equipment manager <NUM> may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE <NUM>. In at least some aspects, the user equipment manager <NUM> configures the RF front end <NUM>, the LTE transceiver <NUM>, and/or the 5GNR transceiver <NUM> to implement the techniques for an uplink handover pilot described herein.

The UE <NUM> includes a WLAN transceiver <NUM> that implements the functions of a WLAN station (STA). The WLAN transceiver <NUM> may be coupled to the RF front end <NUM> and antennas <NUM>, may include an RF front end and antennas, or both. The user equipment manager <NUM> may control the configuration and operation of the WLAN transceiver <NUM> to coordinate operation in the WLAN and cellular frequency bands, or the configuration and operation of the WLAN transceiver <NUM> may be distributed between the user equipment manager <NUM> and the WLAN transceiver <NUM> in any suitable manner. The WLAN transceiver <NUM> is configured to operate in any WLAN frequency band and using any protocols defined in the IEEE <NUM> specifications. The WLAN transceiver <NUM> may also be configured to support beamformed communication.

The device diagram for the base stations <NUM>, shown in <FIG>, includes a single network node (e.g., a gNode B). The functionality of the base stations <NUM> may be distributed across multiple network nodes or devices and may be distributed in any fashion suitable to perform the functions described herein. The base stations <NUM> include antennas <NUM>, a radio frequency front end <NUM> (RF front end <NUM>), one or more LTE transceivers <NUM>, and/or one or more <NUM> NR transceivers <NUM> for communicating with the UE <NUM>. The RF front end <NUM> of the base stations <NUM> can couple or connect the LTE transceivers <NUM> and the 5GNR transceivers <NUM> to the antennas <NUM> to facilitate various types of wireless communication. The antennas <NUM> of the base stations <NUM> may include an array of multiple antennas that are configured similar to or differently from each other. The antennas <NUM> and the RF front end <NUM> can be tuned to, and/or be tunable to, one or more frequency band defined by the 3GPP LTE and 5GNR communication standards, and implemented by the LTE transceivers <NUM>, and/or the 5GNR transceivers <NUM>. Additionally, the antennas <NUM>, the RF front end <NUM>, the LTE transceivers <NUM>, and/or the 5GNR transceivers <NUM> may be configured to support beamforming, such as Massive-MIMO, for the transmission and reception of communications with the UE <NUM>.

The base stations <NUM> also include processor(s) <NUM> and computer-readable storage media <NUM> (CRM <NUM>). The processor <NUM> may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM <NUM> may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data <NUM> of the base stations <NUM>. The device data <NUM> includes network scheduling data, radio resource management data, beamforming codebooks, applications, and/or an operating system of the base stations <NUM>, which are executable by processor(s) <NUM> to enable communication with the UE <NUM>.

CRM <NUM> also includes a base station manager <NUM>. Alternately or additionally, the base station manager <NUM> may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the base stations <NUM>. In at least some aspects, the base station manager <NUM> configures the LTE transceivers <NUM> and the <NUM> NR transceivers <NUM> for communication with the UE <NUM>, as well as communication with a core network. The base stations <NUM> include an inter-base station interface <NUM>, such as an Xn and/or X2 interface, which the base station manager <NUM> configures to exchange user-plane and control-plane data between another base station <NUM>, to manage the communication of the base stations <NUM> with the UE <NUM>. The base stations <NUM> include a core network interface <NUM> that the base station manager <NUM> configures to exchange user-plane and control-plane data with core network functions and entities. This core network interface <NUM> may include interfaces such as the NG2 interface <NUM>, the NG3 interface <NUM>, the N2 interface <NUM>, the N3 interface <NUM>, the S1-U interface <NUM>, and the S1-MME <NUM> as described previously with respect to <FIG>.

<FIG> illustrates an example device diagram <NUM> of the WLAN AP <NUM> and a core network server <NUM>. The WLAN AP <NUM> and a core network server <NUM> may include additional functions and interfaces that are omitted from <FIG> for the sake of clarity.

The WLAN AP <NUM> includes antennas <NUM>, a radio frequency front end <NUM> (RF front end <NUM>), one or more transceivers <NUM> that are configured for WLAN communication with the UE <NUM>. The RF front end <NUM> can couple or connect the transceivers <NUM> to the antennas <NUM> to facilitate various types of wireless communication. The antennas <NUM> of the WLAN AP <NUM> may include an array of multiple antennas that are configured similarly to or differently from each other. The antennas <NUM> and the RF front end <NUM> can be tuned to, and/or be tunable to, one or more frequency bands defined by the IEEE <NUM> communication standards and implemented by the transceivers <NUM>. Additionally, the antennas <NUM>, the RF front end <NUM>, and/or the transceivers <NUM> may be configured to support beamforming for the transmission and reception of communications with the UE <NUM>.

The WLAN AP <NUM> also includes processor(s) <NUM> and computer-readable storage media <NUM> (CRM <NUM>). The processor <NUM> may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM <NUM> may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useful to store device data <NUM> of the WLAN AP <NUM>. The device data <NUM> includes network scheduling data, radio resource management data, applications, and/or an operating system of the WLAN AP <NUM>, which are executable by processor(s) <NUM> to enable communication with the UE <NUM>.

CRM <NUM> also includes an access point manager <NUM>, which, in one implementation, is embodied on CRM <NUM> (as shown). Alternately or additionally, the access point manager <NUM> may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the WLAN AP <NUM>. In at least some aspects, the access point manager <NUM> configures the transceivers <NUM> for communication with the UE <NUM>, as well as communication of user-plane and control-plane data with the core network <NUM> via a network interface <NUM>.

The core network server <NUM> may provide all or part of a function, entity, service, and/or gateway in the core network <NUM> (e.g., the WLAN gateway device). Each function, entity, service, and/or gateway in the core network <NUM> may be provided as a service in the core network <NUM>, distributed across multiple servers, or embodied on a dedicated server. For example, the core network server <NUM> may provide all or a portion of the services or functions of the UPF <NUM>, AMF <NUM>, TWAG <NUM>, UWAG <NUM>, S-GW <NUM>, P-GW <NUM>, MME <NUM>, or ePDG <NUM>. The core network server <NUM> is illustrated as being embodied on a single server that includes processor(s) <NUM> and computer-readable storage media <NUM> (CRM <NUM>). The processor <NUM> may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM <NUM> may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), hard disk drives, or Flash memory useful to store device data <NUM> of the core network server <NUM>. The device data <NUM> includes data to support a core network function or entity, and/or an operating system of the core network server <NUM>, which are executable by processor(s) <NUM>.

CRM <NUM> also includes one or more core network applications <NUM>, which, in one implementation, is embodied on CRM <NUM> (as shown). The one or more core network applications <NUM> may implement the functionality of the UPF <NUM>, AMF <NUM>, TWAG <NUM>, UWAG <NUM>, S-GW <NUM>, P-GW <NUM>, MME <NUM>, or ePDG <NUM>. Alternately or additionally, the one or more core network applications <NUM> may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the core network server <NUM>. The core network server <NUM> also includes a core network interface <NUM> for communication of user-plane and control-plane data with the other functions or entities in the core network <NUM>, base stations <NUM>, or WLAN networks <NUM>, using any of the network interfaces described herein.

In aspects the cellular-WLAN network interface provides an application programming interface (API) for requests, responses, commands, and procedures to enable an AMF <NUM> or MME <NUM> to monitor and/or manage WLAN networks <NUM> in addition to the cellular network. The AMF <NUM> or MME <NUM> may be able to monitor and make requests of all WLAN networks <NUM> that support the API, but may be limited to reconfiguring or controlling WLAN networks <NUM> that are not directly under the control of a network operator of the AMF <NUM> or MME <NUM>. For example, a cellular network operator may have control of the trusted WLAN network <NUM> and thus be able to reconfigure the trusted WLAN network <NUM>, but may not have control of the untrusted WLAN network <NUM> and the AMF <NUM> or MME <NUM> may only be able to monitor the untrusted WLAN network <NUM>.

To implement the cellular-WLAN network interface, the API is supported in several interfaces in the cellular and WLAN networks. The API for the cellular-WLAN network interface is included in a messaging interface of each WLAN STA, such as in the WLAN transceiver <NUM> or the user equipment manager <NUM> in the UE <NUM>. The API for the cellular-WLAN network interface is included in a messaging interface of each WLAN AP <NUM>, such as in the network interface <NUM> or in the access point manager <NUM> in the WLAN AP <NUM>. The network interface <NUM> may include interfaces such as the SWn interfaces <NUM> or <NUM>, the N2a interface <NUM>, the N2b interface <NUM>, the N3a interface <NUM>, the N3b interface <NUM>, the S2a-MME interface <NUM>, and the S2b-MME interface <NUM>, as described previously with respect to <FIG> and <FIG>.

To provide the AMF <NUM> or MME <NUM> access to the APIs in the WLAN stations and APs, interfaces are added to the core network <NUM>, as well as implementing the API in the TWAG <NUM> and the UWAG <NUM> in 5GNR core networks and in the TWAG <NUM> and the ePDG <NUM> in EPC networks. The TWAG <NUM>, UWAG <NUM>, or ePDG <NUM> forwards requests, responses, and commands, between the AMF <NUM> or MME <NUM> and the WLAN APs <NUM> and WLAN STA in the UE <NUM>. In the 5GNR core network, the N2a interface <NUM> is added between the AMF <NUM> and the TWAG <NUM> to enable the AMF <NUM> to access the API for the trusted WLAN network <NUM>, and the N2b interface <NUM> is added between the AMF <NUM> and the UWAG <NUM> to enable the AMF <NUM> to access the API for the untrusted WLAN network <NUM>. In the EPC, the S2a-MME interface <NUM> is added between the MME <NUM> and the TWAG <NUM> to enable the MME <NUM> to access the API for the trusted WLAN network <NUM>, and the S2b-MME interface <NUM> is added between the MME <NUM> and the ePDG <NUM> to enable the MME <NUM> to access the API for the untrusted WLAN network <NUM>.

The API provides a number of requests that can be made to the API included in the WLAN AP <NUM>, and corresponding responses provided by that API in the WLAN AP <NUM>. In the example requests and responses below, the interface syntax is illustrated in the context of a 5GNR core network interface, such as "5GNR_N2[a/b]_request name," where "N2" indicates that the request is sent via an N2 interface, and either "a" or "b" in "[alb]" is selected to indicate that the request is being made via the N2a interface <NUM> for the trusted WLAN network <NUM> or via the N2b interface <NUM> for the untrusted WLAN network <NUM>. The "request name" indicates which request/response is being selected in the API. Although the following examples are illustrated with respect to the <NUM> NR core network, a similar syntax, such as substituting "EUTRAN_S2[a/b]-MME" for "5GNR_N2[a/b]" may be used for EPC networks, where either "a" or "b" in "[alb]" is selected to indicate that the request is being made via the S2a-MME interface <NUM> for the trusted WLAN network <NUM> or via the S2b-MME interface <NUM> for the untrusted WLAN network <NUM>.

In an aspect, the API provides requests and responses for information from the WLAN AP <NUM> that include:.

In another aspect, the API provides commands to the WLAN AP <NUM> that include:.

In further aspect, the API provides requests and responses for information from the UE <NUM> that include:.

In a further aspect, the API provides commands to the UE <NUM> that includes:.

To support the handoff request, the API may also include additional requests and responses to measure various radio parameters of the RAN <NUM>, the trusted WLAN network <NUM> and/or the untrusted WLAN network <NUM>. The AMF <NUM> or MME <NUM> may use these additional measurements to determine parameters for potential handoff candidates to receive the UE <NUM> during the handoff.

In an additional aspect, the new core network interfaces and the API provide the AMF <NUM> or the MME <NUM> with access to perform a procedure with the UE <NUM> via the trusted WLAN network <NUM> or the untrusted WLAN network <NUM>. In addition to performing these procedures via the cellular network, the new core network interfaces (e.g., the N2a interface <NUM>, N2b interface <NUM>, N3a interface <NUM>, N3b interface <NUM>, S2a-MME interface <NUM>, S2b-MME interface <NUM>) and the API enable the AMF <NUM> or the MME <NUM> to perform procedures via a WLAN network <NUM>, including a UE authentication procedure and a UE capability exchange procedure.

Example methods <NUM>-<NUM> are described with reference to <FIG> in accordance with one or more aspects of a cellular-WLAN network interface. The order in which the method blocks are described are not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order, or skipped to implement a method or an alternate method. Generally, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on computer-readable storage memory that is local and/or remote to a computer processing system, and implementations can include software applications, programs, functions, and the like. Alternatively or in addition, any of the functionality described herein can be performed, at least in part, by one or more hardware logic components, such as, and without limitation, Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SoCs), Complex Programmable Logic Devices (CPLDs), and the like.

<FIG> illustrates example method(s) <NUM> of a cellular-WLAN network interface as generally related to the UE <NUM>. At block <NUM>, a UE receives a request from the core network function for one or more parameters related to a WLAN network that the UE is using for WLAN communication. For example, the UE <NUM> receives a request from the AMF <NUM> via the TWAG <NUM> or the UWAG <NUM>, or the MME <NUM> via the TWAG <NUM> or the ePDG <NUM>, for one or more parameters related to the WLAN network <NUM> that the UE <NUM> is using for WLAN communication.

At block <NUM>, in response to the request, the UE transmits a response to the core network function that includes the one or more requested parameters. For example, in response to the request, the UE <NUM> transmits a response to the AMF <NUM> or the MME <NUM> that includes the one or more requested parameters.

At block <NUM>, the UE receives a command to handoff from the serving WLAN AP to one of the neighbor WLAN APs or the cellular network. For example, the UE <NUM> receives a command from the AMF <NUM> or the MME <NUM> to handoff from the serving WLAN AP to one of the neighbor WLAN APs or the cellular network.

<FIG> illustrates example method(s) <NUM> of a cellular-WLAN network interface as generally related to the WLAN AP <NUM>. At block <NUM>, a WLAN AP receives a request from the core network function to report one or more parameters of the WLAN AP to the core network function. For example, the WLAN AP <NUM> receives a request from the AMF <NUM>, via the TWAG <NUM> or the UWAG <NUM>, or the MME <NUM> via the TWAG <NUM> or the ePDG <NUM> to report one or more parameters of the WLAN AP <NUM> to the AMF <NUM> or the MME <NUM>.

At block <NUM>, in response to the request, the WLAN AP transmits, to the core network function, a response including the one or more requested parameters. For example, in response to the request, the WLAN AP <NUM> transmits a response including the one or more requested parameters to the AMF <NUM> or the MME <NUM>.

At block <NUM>, the WLAN AP receives one or more commands to reconfigure the WLAN AP. For example, the WLAN AP <NUM> receives one or more commands to reconfigure the WLAN AP <NUM> from the AMF <NUM> or the MME <NUM>.

At block <NUM>, based on the reception, the WLAN AP reconfigures the WLAN AP using the one or more received commands. For example, the WLAN AP <NUM> reconfigures the WLAN AP <NUM> using the one or more commands received from the AMF <NUM> or the MME <NUM>.

<FIG> illustrates example method(s) <NUM> of a cellular-WLAN network interface as generally related to a WLAN gateway of a cellular network. At block <NUM>, a WLAN gateway receives, a control-plane request from a core network function to report one or more parameters of a WLAN AP to the core network function. For example, the Trusted WLAN Access Gateway (TWAG) <NUM> via the N2a interface <NUM> or the S2a-MME interface <NUM>, the Untrusted WLAN Access Gateway (UWAG) <NUM> via the N2b interface <NUM>, or the Evolved Packet Data Gateway (ePDG) <NUM> via the S2b-MME interface <NUM>, receives a request from the AMF <NUM> or the MME <NUM> to report one or more parameters of the WLAN AP <NUM>.

At block <NUM>, the WLAN gateway forwards the request to the WLAN AP that is effective to cause the WLAN AP to respond to the request. For example, the Trusted WLAN Access Gateway (TWAG) <NUM>, the Untrusted WLAN Access Gateway (UWAG) <NUM>, or the Evolved Packet Data Gateway (ePDG) <NUM> forwards the request to the WLAN AP <NUM> that is effective to cause the WLAN AP <NUM> to respond to the request.

At block <NUM>, the WLAN gateway receives a response to the control-plane request from the WLAN AP. For example, the Trusted WLAN Access Gateway (TWAG) <NUM>, the Untrusted WLAN Access Gateway (UWAG) <NUM>, or the Evolved Packet Data Gateway (ePDG) <NUM> receives a response to the control-plane request from the WLAN AP <NUM>.

At block <NUM>, the WLAN gateway forwards the response from the WLAN AP to the core network function. For example, the Trusted WLAN Access Gateway (TWAG) <NUM> via the N2a interface <NUM> or the S2a-MME interface <NUM>, the Untrusted WLAN Access Gateway (UWAG) <NUM> via the N2b interface <NUM>, or the Evolved Packet Data Gateway (ePDG) <NUM> via the S2b-MME interface <NUM>, forwards the response from the WLAN AP <NUM> to the AMF <NUM> or the MME <NUM>.

Claim 1:
A method to monitor and manage a wireless local area network, WLAN, access point, AP, (<NUM>) in a WLAN network (<NUM>) by a WLAN gateway (<NUM>, <NUM>, <NUM>) of a cellular network, the method comprising:
receiving (<NUM>), by the WLAN gateway, a control-plane request from a core network function (<NUM>, <NUM>) to report one or more parameters of the WLAN AP to the core network function;
forwarding (<NUM>) the control-plane request to the WLAN AP, the forwarding being effective to cause the WLAN AP to respond to the control-plane request;
receiving (<NUM>) a response to the control-plane request from the WLAN AP;
forwarding (<NUM>) the response from the WLAN AP to the core network function;
receiving, by the WLAN gateway, a control-plane command from the core network function to configure one or more settings of the WLAN AP; and
forwarding the control-plane command to the WLAN AP that is effective to cause the WLAN AP to change the one or more settings of the WLAN AP based on the control-plane command, wherein:
the one or more parameters of the WLAN AP (<NUM>) include a current radio frequency of the WLAN AP, the received response to the control-plane request from the WLAN AP includes the current radio frequency of the WLAN AP, and the one or more settings include an RF frequency or channel of the WLAN AP;
the one or more parameters of the WLAN AP include a current transmit power of the WLAN AP, the received response to the control-plane request from the WLAN AP includes the current transmit power of the WLAN AP, and the one or more settings include a transmit power of the WLAN AP;
the one or more parameters of the WLAN AP include a current transmit bandwidth of the WLAN AP, the received response to the control-plane request from the WLAN AP includes the current transmit bandwidth of the WLAN AP, and the one or more settings include a channel bandwidth of the WLAN AP; and/or
the one or more parameters of the WLAN AP include a current AP identity of the WLAN AP, the received response to the control-plane request from the WLAN AP includes the current AP identity of the WLAN AP, and the one or more settings include a Service Set Identifier, SSID, of the WLAN AP.