NETWORK

TECHNICAL FIELD

[0001] Embodiments described herein generally relate to wireless communications and more specifically to cellular offloading via wireless local area network. Some embodiments relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term

Evolution) networks, and 3GPP LTE-A (LTE Advanced) networks, although the scope of the embodiments is not limited in this respect.

BACKGROUND

[0002] Cellular networks, and other wireless networks, generally include a user equipment (UE) connecting to a central point, such as an enhanced node B (eNodeB) or base station. Device-to-Device (D2D) communication systems include communication modalities whereby two UEs, or equivalent devices, communicate directly with each other and not through an eNodeB.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0004] FIG. 1 is a block diagram of an example of an environment including a system for cellular offloading via wireless local area network, in accordance with some embodiments.

[0005] FIG. 2 illustrates a timing diagram for neighbor aware network

(NaN) service discovery, in accordance with some embodiments.

[0006] FIGS. 3A-3C illustrate an example of a communications flow for

D2D proximity detection, in accordance with some embodiments. [0007] FIG. 4 is a swim lane diagram of a communications flow for D2D proximity detection, in accordance with some embodiments.

[0008] FIGS. 5A-5F illustrate an example of a communications flow for

D2D content detection, in accordance with some embodiments.

[0009] FIG. 6 is a swim lane diagram of a communications flow for D2D content detection, in accordance with some embodiments.

[0010] FIGS. 7A-7F illustrate an example of a communications flow for extending emergency broadcast information, in accordance with some embodiments.

[0011] FIG. 8 illustrates an example of a method for cellular offloading via wireless local area network, in accordance with some embodiments.

[0012] FIG. 9 illustrates an example of a method for cellular offloading via wireless local area network, in accordance with some embodiments.

[0013] FIG. 10 is a block diagram of an example of a UE upon which one or more embodiments may be implemented.

[0014] FIG. 11 is a block diagram illustrating an example of a machine upon which one or more embodiments may be implemented.

DETAILED DESCRIPTION

[0015] Cellular networks may wish to employ greater D2D

communication between UEs in order to provide better service, reduce cellular radio load, or extend cellular network reach. A challenge in extending the cellular capabilities using D2D may be a useful and efficient mechanism for coordinating inter-UE communications that are directed by a provider's network, as is often the case in cellular networks.

[0016] A solution to the above issues is to leverage available D2D communication services while configuring the way in which UEs interact with each other on those services. For example, the Wi-Fi Alliance has developed a Nan discovery mechanism called Wi-Fi Aware. This mechanism permits a device to publish services that it offers. These services are named. Other devices indicate to the NaN subsystem which services, by name and possibly other parameters, in which they are interested. When the devices come within range of each other, the NaN facility takes over, subscribing devices that are interested to those services that are published. [0017] The discovery mechanism described above may be used to extend the central network by configuring UEs to publish certain services and to subscribe to certain services. That is, the central network configures a first UE to publish a service with a specific name. The central network also configures a second UE to subscribe to the service with the same name. Thus, the UEs participate in the service discovery under the direction of the central network. This may be used to, for example, extend a network service, such as data transfer, beyond the radio limits of the central network by using an edge UE to provide the extended service to out-of-service UEs via the D2D discovery. In another example, the network may be able to measure radio parameters between two UEs, gaining additional insight on the position or other factors that the network may use to improve the radio link between the UEs. Additionally, the network may use a UE to distribute data that is local to the UE to another UE in a D2D manner to avoid incurring additional resource use on the central network or physical links of the central network.

[0018] While Wi-Fi Aware handles the discovery and service information exchange, it does not directly participate in, for example, D2D data transfers. However, other facilities, such as various mesh networking protocols, Wi-Fi direct, or even cellular D2D may be used to accomplish this task.

Regardless of the specific D2D transfer mechanisms, extending the cellular network by using D2D and other wireless local area network (WLAN) techniques may provide great benefits to central network operators and users.

[0019] FIG. 1 is a block diagram of an example of an environment 100 including a system for cellular offloading via wireless local area network, in accordance with some embodiments. The system includes UE 110 and UE 115. For illustrative purposes, UE 110 is described as a publisher of a service and UE 115 is a subscriber. However, details of UE 110 may be applied to UE 115 when, for example, the role is possible switched for a different service.

[0020] UE 110 includes a cell transceiver 120, a WLAN component 125, and a D2D management entity 130. All of the components of UE 110 are implemented in computer hardware, such as that described below with respect to FIGS. 10 and 11 (e.g., circuit sets).

[0021] The cell transceiver 120 is arranged to receive a configuration from the cellular network 105. This configuration includes a cellular network WLAN service. In an example, the cellular network 105 conforms to a 3GPP family of standards. In an example, the cellular network 105 conforms to a long term evolution (LTE) classification encompassing cellular standards. In an example, the configuration is a radio resource control (RRC) reconfiguration. Thus, the cellular network 105 provides the configuration to the UE via a standard signaling mechanism.

[0022] The WLAN component 125 is arranged to register a NaN WLAN service in accordance with the configuration. In an example, the configuration dictates the name of the service. In an example, the configuration dictates times in which the service is to be registered (e.g., published). In an example, the configuration dictates how the UE 110 is to respond to subscriptions to the service. In an example, a publish API of the WLAN standard (e.g., Wi-Fi Aware) is used to register the service. Once the service is registered (e.g., to a NaN subsystem of the WLAN component), the service is broadcast via WLAN discovery beacons.

[0023] Services may include any number of applications. In an example, the LTE network WLAN service is a proximity service. In this example, information about which UEs are close to the UE 110, communications or other conditions of those UEs, data transfer opportunities, etc. may be exploited. In an example, in the 3GPP family of standards, these services may be called ProSe.

[0024] In an example, the LTE network WLAN service is an emergency notification service. Such as emergency notification service may be useful when, for example, when central network 105 connectivity to UEs is spotty due to lack of coverage, or even network burden due to a disaster. In these situations simply reaching one UE 110 allows that UE 110 to share the emergency information with other UEs (e.g., UE 115). In an example, the emergency notification service includes an earthquake and tsunami warning system (ETWS). As these messages are usually pertinent with certain time limits, the configuration may include expiration or time window parameters. Thus, for example, if a tornado warning has lapsed, the configuration may dictate that the UE 110 cease publishing the service.

[0025] In an example, the LTE network WLAN service is a content distribution service. In this example, the UE 110 has some content locally. In an example, the UE 110 received the content from the serving network 105. The content may have included a designation from the LTE network. This designation may be neutral (e.g., unrelated) to the content itself, but rather serve as an identifier controlled by the network 105 for the content. In an example, the NaN WLAN service communicates the designation to a subscriber device (e.g., UE 115).

[0026] The device-to-device (D2D) management entity 130 is arranged to perform the LTE network WLAN service using the NaN WLAN service. In an example, when the service is a proximity service, the D2D management entity 130 is arranged to accept a WLAN NaN subscription for the NaN WLAN service from a device (e.g., UE 115). In an example, wherein the LTE network WLAN service is a content distribution service, the D2D management entity 130 is arranged to transmit the content to the subscriber device (e.g., UE 115) at the request of the subscriber device. In an example, wherein the service is an emergency service, the D2D management entity 130 is arranged to forward emergency information received in the configuration during a time period also specified in the configuration to any device subscribing to the NaN WLAN service. In an example, when the UE 110 or the network 105 implements a 3GPP family of standards, D2D communications described herein may conform to the 3GPP standard for proximity services (e.g., ProSe).

[0027] UE 115 includes a cellular network stack 135, a WLAN stack

140, and a network extension entity 145. All of the components of UE 115 are implemented in computer hardware, such as that described below with respect to FIGS. 10 and 11 (e.g., circuit sets). The cellular network stack 135 may include one or more components, such as a cellular transceiver, application layer component, etc., used in communicating with the central network 105, to implement its tasks. The WLAN stack 140 may include one or more components, such as a WLAN transceiver, WLAN component, application layer component, etc., used in communicating with networks or devices (e.g., UE 110) other than the central network 105, to implement its tasks.

[0028] The cellular network stack 135 is arranged to receive a configuration that includes a cellular network WLAN service.

[0029] The WLAN stack 140 is arranged to listen for WLAN aware beacons advertising a WLAN D2D service. In an example, the WLAN stack 140 is also arranged to subscribe to the D2D service when the service conforms to the configuration. In an example, to subscribe to the D2D service when the service conforms to the configuration, the WLAN stack 140 is arranged to use a subscribe API of the WLAN standard to subscribe to a service with a name identified in the configuration. That is, the WLAN stack 140 monitors for a service named in the configuration received from the central network 105 and subscribes to the service when it is located.

[0030] In an example, the service is a proximity service. In this example, to listen for the WLAN aware beacons includes the WLAN stack 140 arranged to filter device identifiers that specify a beacon attribute upon which to initiate a subscription. In this manner, the central network 105 may specify which specific devices offering the service to which the UE 115 should subscribe.

[0031] In an example, the service is a content distribution service. In this example, the UE 115 has requested content from a serving cellular network (e.g., central network 105). The cellular network stack 135 receives a network identifier (e.g., a content identifier for the content from the network that is generated by the service provider) for the content in response to the request, but the service cellular network does not transfer the content to the UE 115. Here, the WLAN stack 140 is arranged to receive notification that a device (e.g., UE 110) to which it (UE 115) is subscribed has the content via publication of the network identifier on the D2D service. Thus, UE 115 is informed by the central network 105 of the content identifier which the UE 115 is aware is being offered by UE 110 via the subscription to UE 110's content distribution service.

[0032] The network extension entity 145 is arranged to exchange data received via the subscribed service and a D2D connection. In an example, the D2D connection is a WLAN connection in accordance with an IEEE 802.11 family of standards. In an example, the D2D connection is a D2D connection in accordance with a 3GPP family of cellular standards.

[0033] In an example, where the service is a proximity service, the network extension entity 145 is arranged to perform measurements on a subscribed device in accordance with instructions in the configuration and transmit the measurements to the cellular network. In an example, wherein the service is a content distribution service, the network extension entity 145 is arranged to retrieve the content from the device (e.g., UE 110) to which it is subscribed via a D2D connection. [0034] In an example, the service is an emergency notification service. In this example, The network extension entity 145 is arranged to request emergency information from a device (e.g., UE 110) to which the UE 115 is subscribed. In an example, the emergency notification service includes an earthquake and tsunami warning system (ETWS).

[0035] FIG. 2 illustrates a timing diagram for neighbor aware network

(NaN) service discovery, in accordance with some embodiments. The embodiment illustrated in FIG. 2 roughly follows the discovery protocol of Wi- Fi Aware. Wi-Fi Aware is a forthcoming update to the 802.11 WLAN protocol that will add beacon-like features for discovering and connecting to nearby devices. It is designed to be an always on and power efficient feature. An aspect of the evolving standard include beacons for device discovery (e.g., Wi-Fi Aware NAN specification 1.0).

[0036] As the timeline moves from left to right, NAN discovery beacons are broadcast. A discovery window (DW) starts in which device contention occurs. The DW ends and the devices contend to transmit discovery beacons again. This processes then continues to repeat. Devices publish services to be discovered during this procedure. It is to these services that other devices may subscribe. Thus, in an example, a PUBLISH_API may be used by devices to publish a service. The PUBLISH_API may include a command to publish one or more of the following fields: service_name, matching_filter_tx,

matching_filter_rx, service_specific_info, and configuration_paramaters. Also, in an example, a SUBSCRIBE_API may be used by subscribing devices. The SUBSCRIBE_API may include a command and one or more of the following fields: service_name, matching_filter_tx, matching_filter_rx,

service_specific_info, and configuration_paramaters.

[0037] FIGS. 3A-3C illustrate an example of a communications flow for

D2D proximity detection, in accordance with some embodiments. As noted above, a service that may both be published and subscribed to includes a proximity service. In the example, embodiment described in FIGS. 3A-3C and 4, an LTE central network is using Wi-Fi Aware to implement the proximity service.

[0038] In an example, the LTE network may statically configure UEs to implement the proximity service. For example, LTE broadcasts Wi-Fi Aware parameters in a system information block (SIB). In an example, this broadcast may be a SIB specific for Wi-Fi Aware configuration or as part of other proximity related configurations (e.g., ProSe) in SIB. A parameter included in this configuration is the "service name". In this example, the same configuration may be used by all devices to call the PUBLISH _API of Wi-Fi Aware. This example, is an always on mechanism that does not impact the LTE network because it is done on Wi-Fi.

[0039] Using the SIB to broadcast the service configuration allows for flexibility in tailoring the configuration information based on network deployment. It also allows for changing the configuration to suite various network deployment needs.

[0040] In an example, the LTE network may employ a dynamic configuration. For example, when the network wants to know devices that are in proximity to a particular device, the network may send this particular device a measurement configuration message using RRC Connection Reconfiguration. This measurement configuration will contain Wi-Fi Aware specific parameters which will be used by this device to call the SUBSCRIBE_API of Wi-Fi- Aware. Two parameters that may be sent via the RRC signaling include "service name" and "matching filter." The receiving device will use these parameters to call the SUBSCRIBE_API. The measurement configuration may also contain other parameters, which may be called "reporting quantities," that the network wants this device to report about from nearby devices, such as channel quality, NAN address of nearby device, a description of what content the nearby device is hosting etc.

[0041] On performing a Wi-Fi Aware subscribe, the device actively listens to the beacons of the nearby Wi-Fi Aware devices in the DW. When a publish beacon matches the "matching filter," Wi-Fi Aware generates a DISCO VERY_E VENT. The device may then establish a D2D connection to gather other information it may need (e.g., based on "reporting quantities"). The device then packages this information in a measurement report and sends it to network. The matching filter provided in the measurement configuration may be tuned to receive discovery event from all nearby LTE devices or a particular LTE device that network may be interested to know about. [0042] FIG. 3A illustrates a first stage in the proximity service. A static configuration may be provided to every device (message A). Each device may then call the PUBLISH_API (message B). In an example, the service name may be LTE_Wifi_Aware_ProSe.

[0043] FIG. 3B illustrates a second stage. The network sends RRC

Connection reconfiguration to Device 1 (message C), for example, want to know what other devices are in Device 1 's proximity. Device 1 uses the measurement configuration to call the SUBSCRIBE_API (message D).

[0044] FIG. 3C illustrates a third stage. Device 2, which is in proximity to Device 1, generates a DISCOVERY event in Device 1 (message E). Device 1 gets the requested information from Device 2 and triggers a measurement report back to the network (message F) with some or all of the collected information.

[0045] FIG. 4 is a swim lane diagram of a communications flow for D2D proximity detection, in accordance with some embodiments. FIG. 4 illustrates a condensed set of events illustrated in FIG. 3A-3C. Devices 1 , 2, and 3 register with the network. These devices then receive configuration from the network to publish a Wi-Fi Aware service with the same service name. The network then sends an RRC reconfiguration to Device 1. In an example, the reconfiguration includes a filter that matches a subset of devices, such as Device 2. In an example, the reconfiguration omits the filter, such that every other device) e.g., both devices 2 and 3) will be addressed by Device 1. Device 1 then calls the SUBSCRIBE_API, with the filter if it was specified.

[0046] By calling the SUBSCRIBE_API, the Wi-Fi Aware subsystem will generate discovery events for the after the DW. As the discovery events are generated, Device 1 may collect information from the discovered devices. In an example, Device 1 will use information from the discovery process to produce the measurement report. In an example, Device 1 will use a D2D link (e.g., Wi- Fi Direct) to capture the requested data. Finally, Device 1 will assemble and deliver the measurement report to the network.

[0047] The technique illustrated above with respect to FIGS. 3A-3C may solve proximity detection in LTE devices, such as is being considered in 3GPP release 12 and 13 ProSe. Some current proposals for proximity detection involve changing the LTE random access channel (RACH) mechanism or other solutions that involve change LTE protocols. Here, interworking with Wi-Fi Aware allows the technique to leverage a near ubiquitous technology without drastic changes to the cellular network protocols, providing a less expensive and quicker to market solution.

[0048] FIGS. 5A-5F illustrate an example of a communications flow for D2D content detection, in accordance with some embodiments. As noted above, a service that may both be published and subscribed to includes a content distribution service. In the example, embodiment described in FIGS. 5A-5F and 6, an LTE central network is using Wi-Fi Aware to implement the content distribution service.

[0049] Both Device 1 and Device 2 include LTE and NaN (e.g., Wi-Fi

Aware) capabilities. These devices may include an LTE service application (illustrated) or an LTE stack component (not illustrated) to interface between the LTE network and the NaN. This interface may be configured (e.g., installed) with a unique, LTE specific, "service name" and "service specific info," for example, as defined in the NaN specification. These LTE service related parameters may be the same (e.g., identical) across all LTE devices. The LTE service application is arranged to interact with the network (e.g., eNodeB) and handle different content identification (ID) information given to it from the eNodeB. This information may then be used in the NaN to share content or other data. As illustrated, Device 1 is the publisher and Device 2 is the subscriber.

[0050] FIG. 5A illustrates a first stage in the content distribution. Device

2 subscribes (message B) by providing the LTE service name (message A) and continuously listens (message C) for LTE information as, for example, described in the Wi-Fi Aware specification.

[0051] FIG. 5B illustrates a second stage where Device 1 downloads content (e.g., Ml - Video 1 and M2 - Video 2) using the LTE network (message D). Content IDs Ml and M2 are generated in the LTE network based on device ID and content description information, although other techniques (e.g., a completely random ID generation) may be used. The content ID uniquely identifies a piece of content and a device in the network.

[0052] FIG. 5C illustrates a third stage where Device 1 publishes (e.g., via the LTE services application) (messages E, F, G, and H) the LTE service name and the content ID information for Ml and M2. Specifically, message E is the PUSHLISH_API call, while message F communicates the information to the NaN subsystem. Message G is a callback to alert the PUBLISH_API caller that the information is published with an ID, and message H is the broadcast of the information.

[0053] FIG. 5D illustrates a fourth stage where Device 2 actively listens for the LTE service over Wi-Fi Aware and receives (message I) and stores the published information (message J).

[0054] When Device 2 requests content from the LTE network, it sends the eNodeB the usual content request along with whatever content ID information it has gathered and stored, such as Ml and M2 (message K).

[0055] FIG. 5E is a fifth stage where the eNodeB correlates the received

Ml and M2 from Device 2 as identifying Video 1 and Video 2 earlier downloaded by Device 1. The eNodeB searches for a match between the content requested by Device 2 and Ml or M2 that Device 2 has detected within its vicinity. The eNodeB matches Device 2's request to M2 (Video 2) and instructs Device 2 to retrieve this content (Ml) from Device 1 (message L). This is then passed up to the LTE service application to retrieve the content (message M).

[0056] FIG. 5F is a sixth stage where Device 2 forms a D2D connection

(e.g., Wi-Fi direct, LTE D2D, etc.) to get Video 2 using the M2 ID (message N).

[0057] FIG. 6 is a swim lane diagram of a communications flow for D2D content detection, in accordance with some embodiments. FIG. 6 illustrates a condensed set of events illustrated in FIG. 5A-5F. Device 1 receives shareable content from the network. Content IDs for the shareable content are also received from the network. Device 1 publishes the received content IDs.

[0058] Meanwhile, Device 2 has subscribed to the same service name that the content IDs are published under. Following NaN discovery, Device 2 becomes aware of the contents IDs (e.g., Ml and M2).

[0059] Unrelated to discovering Ml and M2, Device 2 requests new data

(Rl) from the network. It so happens that Rl refers to Video 2, the same video to which M2 refers. The network makes this connection and derives that Device 1 is in proximity to Device 2 because Device 2 sent M2 along with its content request.

[0060] The network then communicates control information to Device 2 to retrieve the requested content from Device 1. Device 2 then forms a D2D link to retrieve the content. [0061] FIGS. 7A-7F illustrate an example of a communications flow for extending emergency broadcast information, in accordance with some embodiments. As noted above, a service that may both be published and subscribed to includes an emergency notification service. In the example, embodiment described in FIGS. 7A-7f, an LTE central network is using Wi-Fi Aware to implement the emergency notification service.

[0062] Currently, whenever LTE devices receive EMERGENCY INFO

(e.g., ETWS information), they are informed through LTE system information. However, this information cannot be received by out of service (OOS) devices when the emergency information is broadcast or when the devices miss a page indicating the emergency information broadcast. The present techniques address this issue by using NaN to distribute this information between peer devices, including those that are OOS or otherwise unable to receive the broadcast.

[0063] Consider Device 1 and Device 2 that both have NaN and LTE capabilities. The devices may include an LTE service application for emergency services, or an LTE facility to address the functions described herein attributed to the service application. The service application may include a unique LTE service name, such as "EMERGENCY INFO) and related service parameters. The LTE service parameters may be the same across all LTE devices. The LTE service application will receive the emergency information (e.g., ETWS broadcast) from the LTE network, for example, in a SIB (e.g., SIB 10) message. The emergency information may also include the NaN parameters.

[0064] FIG. 7A illustrates a first stage where Device 2 subscribes to the emergency service by providing the LTE service name (e.g., EMEREGENCY INFOR SERVICE ID) (message A to provide the ID, message B to deliver the ID to the NaN subsystem) and continuously listening for LTE information (message C) as, for example, described in the Wi-Fi Aware specification.

[0065] FIG. 7B illustrates a second stage where Device 1 receives ETWS notification (e.g., a paging indication) and reads relevant system information to get the emergency information from the network (message D). In an example, SIB 10 is used to transmit the emergency information and also includes Wi-Fi Aware information (e.g., E-Info) that specifies the Wi-Fi Aware parameters to be used by Device 1 to publish the ETWS information. [0066] FIG. 7C illustrates a third stage where Device 1 , for example via the LTE service application (message E), to publishing the EMERGENCY SERVICE INFO ID using the E-Info (message F to publish and message G to receive a callback from the publication) received in the SIB. With the publication, Device 1 is broadcasting the emergency information in accordance with the publication (message H).

[0067] FIG. 7D illustrates a fourth stage where Device to, which is actively listening for the LTE EMERGENCY SERVICE INFO ID, receives the information (message I), noting that the LTE emergency information is being broadcast from Device 1.

[0068] FIG. 7E illustrates a fifth stage where Device 2 sets up a D2D

(e.g., Wi-Fi Direct connection to Device 1 to obtain (e.g., receive or retrieve) the ETWS information, including any other relevant emergency information, from Device 1 (message J).

[0069] FIG. 7F illustrates a sixth stage where Device 2, based on E-Info received from Device 1 , reads an optional "validity time" parameter set by the network. This addresses the often transient nature of emergency information. As long as the emergency information remains valid, according to the validity time, Device 2 broadcasts the emergency information to other devices in a manner similar to that performed by Device 1 (message K).

[0070] FIG. 8 illustrates an example of a method for cellular offloading via wireless local area network, in accordance with some embodiments. The operations of FIG. 8 are performed by computer hardware, such as that described above with respect to FIG. 1, or below with respect to FIGS. 10 and 11 (e.g., circuit sets).

[0071] At operation 805, a transmission from a serving cellular network is received that contains a configuration defining parameters of a cellular network WLAN service. In an example, the cellular network WLAN service is an emergency notification service. In an example, the cellular network WLAN service is a content distribution service. In an example, the cellular network

WLAN service is a proximity service. In an example, the configuration is a radio resource control (RRC) reconfiguration.

[0072] At operation 810, WLAN aware beacons announcing a WLAN device-to-device (D2D) service that conforms to the parameters of the cellular network WLAN service are listened for. In an example, where the cellular network WLAN service is a proximity service, listening for the WLAN aware beacons includes filtering device identifiers that specify a beacon attribute upon which to initiate a subscription.

[0073] At operation 815, the D2D service offered by a device when the

D2D service is identified via the listening is subscribed to. In an example, subscribing to the D2D service includes using a subscription API of the WLAN standard with the parameters from the configuration. In an example, where the cellular network WLAN service is a content distribution service, the UE performing the method 800 receives notification that the device has content via the subscribed service.

[0074] At operation 820, data from the device is received in accordance with the subscribed service. In an example, where the cellular network WLAN service is a content distribution service, the UE performing the method 800 has requested content from a serving cellular network, and the UE has received a network identifier for the content from the serving cellular network, receiving data from the device includes retrieving the content from the device via a D2D connection. In an example, the D2D connection is a WLAN connection in accordance with an IEEE 802.11 family of standards. In an example, the D2D connection is a D2D connection in accordance with a 3GPP family of cellular standards. In an example, where the cellular network WLAN service is a proximity service, retrieving data from the device includes performing measurements on radio communications with the device in accordance with instructions in the configuration and transmitting the measurements to the serving cellular network.

[0075] In an example, where the cellular network WLAN service is an emergency notification service, receiving data from the device includes requesting emergency information. In an example, the emergency notification service includes an earthquake and tsunami warning system (ETWS).

[0076] FIG. 9 illustrates an example of a method for cellular offloading via wireless local area network, in accordance with some embodiments. The operations of FIG. 9 are performed by computer hardware, such as that described above with respect to FIG. 1, or below with respect to FIGS. 10 and 11 (e.g., circuit sets). [0077] At operation 905, a configuration is received from an eNodeB.

The configuration received includes a cellular network WLAN service configuration. In an example, the configuration is a radio resource control (RRC) reconfiguration. In an example, the cellular network WLAN service is an emergency notification service. In an example, the emergency notification service includes an earthquake and tsunami warning system (ETWS). In an example, the cellular network WLAN service is a content distribution service. In an example, the cellular network WLAN service is a proximity service.

[0078] At operation 910, a NaN WLAN service is registered in accordance with the configuration. The service will be announced in accordance with a NaN WLAN protocol when registered. In an example, to register the NaN WLAN service in accordance with the configuration includes using a publish API of the WLAN standard to publish a service with a name identified in the configuration. In an example, where the cellular network WLAN service is a content distribution service and the UE performing the method 900 has received content from a serving LTE network— the content including a designation from the LTE network— the NaN WLAN service communicates the designation to a subscriber device.

[0079] At operation 915, the cellular network WLAN service is performed using the NaN WLAN service and a device-to-device connection. In an example, where the service is an emergency notification service, performing the cellular network WLAN service includes forwarding emergency information received in the configuration during a time period also specified in the configuration to any device subscribing to the NaN WLAN service. In an example, where the cellular network WLAN service is a content distribution service, performing the cellular network WLAN service includes transmitting the content to the subscriber device at the request of the subscriber device. In an example, where the cellular network WLAN service is a proximity service, performing the NaN WLAN service includes accepting a WLAN NaN subscription for the NaN WLAN service from a device I

[0080] FIG. 10 is a block diagram of an example of a UE 1000 upon which one or more embodiments may be implemented. In an example, the UE 1000 may include application circuitry 1002, baseband circuitry 1004, Radio Frequency (RF) circuitry 1006, front-end module (FEM) circuitry 1008 and one or more antennas 1010, coupled together at least as shown. As used with reference to FIG. 10, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.

[0081] The application circuitry 1002 may include one or more application processors. For example, the application circuitry 1002 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors,

application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[0082] The baseband circuitry 1004 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1004 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1006 and to generate baseband signals for a transmit signal path of the RF circuitry 1006. Baseband processing circuity 1004 may interface with the application circuitry 1002 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1006. For example, the baseband circuitry 1004 may include a second generation (2G) baseband processor 1004a, third generation (3G) baseband processor 1004b, fourth generation (4G) baseband processor 1004c, and/or other baseband processor(s) 1004d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 1004 (e.g., one or more of baseband processors 1004a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1006. The radio control functions may include, but are not limited to, signal modulation/demodulation,

encoding/decoding, radio frequency shifting, etc. In an example, modulation/demodulation circuitry of the baseband circuitry 1004 may include Fast-Fourier Transform (FFT), precoding, and/or constellation

mapping/demapping functionality. In an example, encoding/decoding circuitry of the baseband circuitry 1004 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0083] In an example, the baseband circuitry 1004 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 1004e of the baseband circuitry 1004 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In an example, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 1004f. The audio DSP(s) 1004f may be include elements for

compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. In an example, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board. In an example, some or all of the constituent components of the baseband circuitry 1004 and the application circuitry 1002 may be implemented together such as, for example, on a system on a chip (SOC).

[0084] In an example, the baseband circuitry 1004 may provide for communication compatible with one or more radio technologies. For example, the baseband circuitry 1004 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 1004 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry. [0085] RF circuitry 1006 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1006 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1006 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1008 and provide baseband signals to the baseband circuitry 1004. RF circuitry 1006 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1004 and provide RF output signals to the FEM circuitry 1008 for transmission.

[0086] In an example, the RF circuitry 1006 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1006 may include mixer circuitry 1006a, amplifier circuitry 1006b and filter circuitry 1006c. The transmit signal path of the RF circuitry 1006 may include filter circuitry 1006c and mixer circuitry 1006a. RF circuitry 1006 may also include synthesizer circuitry 1006d for synthesizing a frequency for use by the mixer circuitry 1006a of the receive signal path and the transmit signal path. In an example, the mixer circuitry 1006a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1008 based on the synthesized frequency provided by synthesizer circuitry 1006d. The amplifier circuitry 1006b may be configured to amplify the down-converted signals and the filter circuitry 1006c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1004 for further processing. In an example, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In an example, mixer circuitry 1006a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0087] In an example, the mixer circuitry 1006a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1006d to generate RF output signals for the FEM circuitry 1008. The baseband signals may be provided by the baseband circuitry 1004 and may be filtered by filter circuitry 1006c. The filter circuitry 1006c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0088] In an example, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In an example, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In an example, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a may be arranged for direct downconversion and/or direct upconversion, respectively. In an example, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may be configured for super-heterodyne operation.

[0089] In an example, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1006 may include analog-to-digital converter (ADC) and digital-to- analog converter (DAC) circuitry and the baseband circuitry 1004 may include a digital baseband interface to communicate with the RF circuitry 1006.

[0090] In a dual-mode example, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0091] In an example, the synthesizer circuitry 1006d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1006d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0092] The synthesizer circuitry 1006d may be configured to synthesize an output frequency for use by the mixer circuitry 1006a of the RF circuitry 1006 based on a frequency input and a divider control input. In an example, the synthesizer circuitry 1006d may be a fractional N/N+l synthesizer. [0093] In an example, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1004 or the applications processor 1002 depending on the desired output frequency. In an example, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1002.

[0094] Synthesizer circuitry 1006d of the RF circuitry 1006 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In an example, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In an example, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0095] In an example, synthesizer circuitry 1006d may be configured to generate a carrier frequency as the output frequency, while in other

embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In an example, the output frequency may be a LO frequency (fLO). In an example, the RF circuitry 1006 may include an IQ/polar converter.

[0096] FEM circuitry 1008 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1010, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1006 for further processing. FEM circuitry 1008 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1006 for transmission by one or more of the one or more antennas 1010. [0097] In an example, the FEM circuitry 1008 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1006). The transmit signal path of the FEM circuitry 1008 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1006), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1010.

[0098] In an example, the UE 1000 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

[0099] FIG. 11 illustrates a block diagram of an example machine 1100 upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform. In alternative embodiments, the machine 1100 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 1100 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 1100 may act as a peer machine in peer-to-peer

(P2P) (or other distributed) network environment. The machine 1100 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

[0100] Examples, as described herein, may include, or may operate by, logic or a number of components, or mechanisms. Circuit sets are a collection of circuits implemented in tangible entities that include hardware (e.g., simple circuits, gates, logic, etc.). Circuit set membership may be flexible over time and underlying hardware variability Circuit sets include members that may alone or in combination, perform specified operations when operating. In an example, hardware of the circuit set may be immutably designed to carry out a specific operation (e.g., hardwired). In an example, the hardware of the circuit set may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a computer readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation. In connecting the physical components, the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuit set in hardware via the variable connections to carry out portions of the specific operation when in operation. Accordingly, the computer readable medium is communicatively coupled to the other components of the circuit set member when the device is operating. In an example, any of the physical components may be used in more than one member of more than one circuit set. For example, under operation, execution units may be used in a first circuit of a first circuit set at one point in time and reused by a second circuit in the first circuit set, or by a third circuit in a second circuit set at a different time.

[0101] Machine (e.g., computer system) 1100 may include a hardware processor 1102 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1104 and a static memory 1106, some or all of which may communicate with each other via an interlink (e.g., bus) 1108. The machine 1100 may further include a display unit 1110 (e.g., a raster display, vector display, holographic display, etc.), an alphanumeric input device 1112 (e.g., a keyboard), and a user interface (UI) navigation device 1114 (e.g., a mouse). In an example, the display unit 1110, input device 1112 and UI navigation device 1114 may be a touch screen display. The machine 1100 may additionally include a storage device (e.g., drive unit) 1116, a signal generation device 1118 (e.g., a speaker), a network interface device 1120, and one or more sensors 1121, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 1 100 may include an output controller 1128, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0102] The storage device 1116 may include a machine readable medium 1122 on which is stored one or more sets of data structures or instructions 1124 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 1124 may also reside, completely or at least partially, within the main memory 1104, within static memory 1106, or within the hardware processor 1102 during execution thereof by the machine 1100. In an example, one or any combination of the hardware processor 1102, the main memory 1104, the static memory 1106, or the storage device 1116 may constitute machine readable media.

[0103] While the machine readable medium 1122 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 1124.

[0104] The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 1 100 and that cause the machine 1100 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non- limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. In an example, a massed machine readable medium comprises a machine readable medium with a plurality of particles having invariant (e.g., rest) mass. Accordingly, massed machine-readable media are not transitory propagating signals. Specific examples of massed machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory

(EPROM), Electrically Erasable Programmable Read-Only Memory

(EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks. [0105] The instructions 1124 may further be transmitted or received over a communications network 1126 using a transmission medium via the network interface device 1120 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as WiFi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 1120 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 1126. In an example, the network interface device 1120 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 1100, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

Additional Notes & Examples [0106] Example 1 is an apparatus of a user equipment (UE) for cellular offloading via wireless local area network (WLAN), the apparatus comprising: a long term evolution (LTE) network transceiver chain component to receive a configuration that includes an LTE network WLAN service; a WLAN component to register a neighbor aware networking (NaN) WLAN service in accordance with the configuration, the service to be broadcast via WLAN discovery beacons once registered; and a device-to-device (D2D) management entity to perform the LTE network WLAN service using the NaN WLAN service. [0107] In Example 2, the subject matter of Example 1 optionally includes wherein to register the NaN WLAN service in accordance with the configuration includes the WLAN component to use a publish API of the WLAN standard to publish a service with a name identified in the configuration.

[0108] In Example 3, the subject matter of any one or more of Examples

1-2 optionally include wherein the LTE network WLAN service is a proximity service, and wherein to perform the LTE network WLAN service includes the D2D management entity to accept a WLAN NaN subscription for the NaN WLAN service from a device.

[0109] In Example 4, the subject matter of any one or more of Examples

1-3 optionally include wherein the LTE network WLAN service is an emergency notification service, and wherein to perform the LTE network WLAN service includes the D2D management entity to forward emergency information received in the configuration during a time period also specified in the configuration to any device subscribing to the NaN WLAN service.

[0110] In Example 5, the subject matter of Example 4 optionally includes wherein the emergency notification service includes an earthquake and tsunami warning system (ETWS).

[0111] In Example 6, the subject matter of any one or more of Examples 1-5 optionally include wherein the LTE network WLAN service is a content distribution service, wherein the UE has received content from a serving LTE network, the content including a designation from the LTE network, wherein the NaN WLAN service communicates the designation to a subscriber device; and wherein the D2D management entity transmits the content to the subscriber device at the request of the subscriber device.

[0112] In Example 7, the subject matter of any one or more of Examples

1-6 optionally include wherein the configuration is a radio resource control (RRC) reconfiguration.

[0113] In Example 8, the subject matter of any one or more of Examples 1-7 optionally include a raster display.

[0114] Example 9 is an apparatus of a user equipment (UE) for cellular offloading via wireless local area network (WLAN), the apparatus comprising: a cellular network stack to receive a configuration that includes a cellular network WLAN service; a WLAN stack to: listen for WLAN aware beacons advertising a WLAN device-to-device (D2D) service; and subscribe to the D2D service when the service conforms to the configuration; and a network extension entity to exchange data received via the subscribed service and a D2D connection.

[0115] In Example 10, the subject matter of Example 9 optionally includes wherein to subscribe to the D2D service when the service conforms to the configuration includes the WLAN stack to use a subscribe API of the WLAN standard to subscribe to a service with a name identified in the configuration.

[0116] In Example 11 , the subject matter of any one or more of

Examples 9-10 optionally include wherein the service is a proximity service, and wherein to listen for the WLAN aware beacons includes the WLAN stack to filter device identifiers that specify a beacon attribute upon which to initiate a subscription, and wherein to exchange data received via the subscribed service includes the network extension entity to perform measurements on a subscribed device in accordance with instructions in the configuration and transmit the measurements to the cellular network.

[0117] In Example 12, the subject matter of any one or more of

Examples 9-11 optionally include wherein the service is an emergency notification service, and wherein to exchange data received via the subscribed service includes the network extension entity to request emergency information from a device to which the UE is subscribed.

[0118] In Example 13, the subject matter of Example 12 optionally includes wherein the emergency notification service includes an earthquake and tsunami warning system (ETWS).

[0119] In Example 14, the subject matter of any one or more of Examples 9-13 optionally include wherein the service is a content distribution service, wherein the UE has requested content from a serving cellular network, wherein the cellular network stack receives a network identifier for the content, wherein the WLAN stack has received notification that a device to which it is subscribed has the content via publication of the network identifier on the D2D service, and wherein the network extension entity retrieves the content from the device to which it is subscribed via a D2D connection.

[0120] In Example 15, the subject matter of Example 14 optionally includes wherein the D2D connection is a WLAN connection in accordance with an IEEE 802.11 family of standards. [0121] In Example 16, the subject matter of any one or more of

Examples 14-15 optionally include wherein the D2D connection is a D2D connection in accordance with a 3GPP family of cellular standards.

[0122] In Example 17, the subject matter of any one or more of Examples 9-16 optionally include wherein the configuration is a radio resource control (RRC) reconfiguration.

[0123] In Example 18, the subject matter of any one or more of

Examples 9-17 optionally include a speaker to render audio.

[0124] Example 19 is at least one machine readable medium of a user equipment (UE), the machine readable medium including instructions for cellular offloading via wireless local area network (WLAN) when executed by the UE, the instructions configuring the UE to: receive a transmission from a serving cellular network that contains a configuration defining parameters of a cellular network WLAN service; listen for WLAN aware beacons announcing a WLAN device-to-device (D2D) service that conforms to the parameters of the cellular network WLAN service; subscribe to the D2D service offered by a device when the D2D service is identified via the listening; and receive data from the device in accordance with the subscribed service.

[0125] In Example 20, the subject matter of Example 19 optionally includes wherein the cellular network WLAN service is a content distribution service, wherein the UE has requested content from a serving cellular network, wherein the UE receives a network identifier for the content from the serving cellular network, wherein the UE receives notification that the device has the content via the subscribed service, and wherein to receive data from the device includes instructions configuring the UE to retrieve the content from the device via a D2D connection.

[0126] In Example 21 , the subject matter of Example 20 optionally includes wherein the D2D connection is a WLAN connection in accordance with an IEEE 802.11 family of standards.

[0127] In Example 22, the subject matter of any one or more of

Examples 20-21 optionally include wherein the D2D connection is a D2D connection in accordance with a 3GPP family of cellular standards.

[0128] In Example 23, the subject matter of any one or more of

Examples 19-22 optionally include wherein to subscribe to the D2D service includes instructions configuring the UE to use a subscription API of the WLAN standard with the parameters from the configuration.

[0129] In Example 24, the subject matter of any one or more of

Examples 19-23 optionally include wherein the cellular network WLAN service is an emergency notification service, and wherein to receive data from the device includes instructions configuring the UE to request emergency information.

[0130] In Example 25, the subject matter of Example 24 optionally includes wherein the emergency notification service includes an earthquake and tsunami warning system (ETWS).

[0131] In Example 26, the subject matter of any one or more of

Examples 19-25 optionally include wherein the configuration is a radio resource control (RRC) reconfiguration.

[0132] In Example 27, the subject matter of any one or more of

Examples 19-26 optionally include wherein the cellular network WLAN service is a proximity service, and wherein to listen for the WLAN aware beacons includes instructions configuring the UE to filter device identifiers that specify a beacon attribute upon which to initiate a subscription, and wherein to retrieve data from the device includes instructions configuring the UE to perform measurements on radio communications with the device in accordance with instructions in the configuration and to transmit the measurements to the serving cellular network.

[0133] Example 28 is at least one machine readable medium of a user equipment (UE), the machine readable medium including instructions for cellular offloading via wireless local area network (WLAN) when executed by the UE, the instructions configuring the UE to: receive a configuration from an eNodeB, the configuration including a cellular network WLAN service configuration; register a neighbor aware networking (NaN) WLAN service in accordance with the configuration, the service to be announced in accordance with a NaN WLAN protocol when registered; and perform the cellular network WLAN service using the NaN WLAN service and a device-to-device connection.

[0134] In Example 29, the subject matter of Example 28 optionally includes wherein the cellular network WLAN service is an emergency notification service, and wherein to perform the cellular network WLAN service includes instructions configuring the UE to forward emergency information received in the configuration during a time period also specified in the configuration to any device subscribing to the NaN WLAN service.

[0135] In Example 30, the subject matter of Example 29 optionally includes wherein the emergency notification service includes an earthquake and tsunami warning system (ETWS).

[0136] In Example 31 , the subject matter of any one or more of

Examples 28-30 optionally include wherein to register the NaN WLAN service in accordance with the configuration includes instructions configuring the UE to use a publish API of the WLAN standard to publish a service with a name identified in the configuration.

[0137] In Example 32, the subject matter of any one or more of

Examples 28-31 optionally include wherein the cellular network WLAN service is a content distribution service, wherein the UE has received content from a serving LTE network, the content including a designation from the LTE network, wherein the NaN WLAN service communicates the designation to a subscriber device; and wherein to perform the cellular network WLAN service includes instructions configuring the UE to transmit the content to the subscriber device at the request of the subscriber device.

[0138] In Example 33, the subject matter of any one or more of

Examples 28-32 optionally include wherein the cellular network WLAN service is a proximity service, and wherein to perform the NaN WLAN service includes instructions configuring the UE to accept a WLAN NaN subscription for the NaN WLAN service from a device.

[0139] In Example 34, the subject matter of any one or more of

Examples 28-33 optionally include wherein the configuration is a radio resource control (RRC) reconfiguration.

[0140] Example 35 is a method performed by user equipment (UE) for cellular offloading via wireless local area network (WLAN), the method comprising: receiving a configuration from an eNodeB, the configuration including a cellular network WLAN service configuration; registering a neighbor aware networking (NaN) WLAN service in accordance with the configuration, the service to be announced in accordance with a NaN WLAN protocol when registered; and performing the cellular network WLAN service using the NaN WLAN service and a device-to-device connection.

[0141] In Example 36, the subject matter of Example 35 optionally includes wherein the cellular network WLAN service is an emergency notification service, and wherein performing the cellular network WLAN service includes forwarding emergency information received in the configuration during a time period also specified in the configuration to any device subscribing to the NaN WLAN service.

[0142] In Example 37, the subject matter of Example 36 optionally includes wherein the emergency notification service includes an earthquake and tsunami warning system (ETWS).

[0143] In Example 38, the subject matter of any one or more of

Examples 35-37 optionally include wherein to register the NaN WLAN service in accordance with the configuration includes using a publish API of the WLAN standard to publish a service with a name identified in the configuration.

[0144] In Example 39, the subject matter of any one or more of

Examples 35-38 optionally include wherein the cellular network WLAN service is a content distribution service, wherein the UE has received content from a serving LTE network, the content including a designation from the LTE network, wherein the NaN WLAN service communicates the designation to a subscriber device; and wherein performing the cellular network WLAN service includes transmitting the content to the subscriber device at the request of the subscriber device.

[0145] In Example 40, the subject matter of any one or more of

Examples 35-39 optionally include wherein the cellular network WLAN service is a proximity service, and wherein performing the NaN WLAN service includes accepting a WLAN NaN subscription for the NaN WLAN service from a device.

[0146] In Example 41 , the subject matter of any one or more of

Examples 35-40 optionally include wherein the configuration is a radio resource control (RRC) reconfiguration.

[0147] Example 42 is a method of a user equipment (UE) for cellular offloading via wireless local area network (WLAN), the method comprising: receiving a transmission from a serving cellular network that contains a configuration defining parameters of a cellular network WLAN service; listening for WLAN aware beacons announcing a WLAN device-to-device (D2D) service that conforms to the parameters of the cellular network WLAN service;

subscribing to the D2D service offered by a device when the D2D service is identified via the listening; and receiving data from the device in accordance with the subscribed service.

[0148] In Example 43, the subject matter of Example 42 optionally includes wherein the cellular network WLAN service is a content distribution service, wherein the UE has requested content from a serving cellular network, wherein the UE receives a network identifier for the content from the serving cellular network, wherein the UE receives notification that the device has the content via the subscribed service, and wherein receiving data from the device includes retrieving the content from the device via a D2D connection.

[0149] In Example 44, the subject matter of Example 43 optionally includes wherein the D2D connection is a WLAN connection in accordance with an IEEE 802.11 family of standards.

[0150] In Example 45, the subject matter of any one or more of

Examples 43-44 optionally include wherein the D2D connection is a D2D connection in accordance with a 3GPP family of cellular standards.

[0151] In Example 46, the subject matter of any one or more of Examples 42-45 optionally include wherein subscribing to the D2D service includes using a subscription API of the WLAN standard with the parameters from the configuration.

[0152] In Example 47, the subject matter of any one or more of

Examples 42-46 optionally include wherein the cellular network WLAN service is an emergency notification service, and wherein receiving data from the device includes requesting emergency information.

[0153] In Example 48, the subject matter of Example 47 optionally includes wherein the emergency notification service includes an earthquake and tsunami warning system (ETWS).

[0154] In Example 49, the subject matter of any one or more of

Examples 42-48 optionally include wherein the configuration is a radio resource control (RRC) reconfiguration.

[0155] In Example 50, the subject matter of any one or more of

Examples 42-49 optionally include wherein the cellular network WLAN service is a proximity service, and wherein listening for the WLAN aware beacons includes filtering device identifiers that specify a beacon attribute upon which to initiate a subscription, and wherein retrieving data from the device includes performing measurements on radio communications with the device in accordance with instructions in the configuration and transmitting the measurements to the serving cellular network.

[0156] Example 51 is a method wherein LTE devices indicate their capability of supporting WiFi Aware (WiFi NAN) to LTE network.

[0157] In Example 52, the subject matter of Example 51 optionally includes LTE network or LTE devices may be replaced by any cellular devices in their corresponding cellular network.

[0158] Example 53 is a method where Cellular network broadcasts WiFi

Aware parameters required for calling Publish API of WiFi Aware in system information.

[0159] In Example 54, the subject matter of Example 53 optionally includes may change in system information based on the requirements for network deployment.

[0160] In Example 55, the subject matter of any one or more of

Examples 53-54 optionally include may not be restricted to system information and could be sent to specific device in dedicated measurement configuration.

[0161] Example 56 is a method for making devices discoverable wherein devices using information mentioned in Example.

[0162] In Example 57, the subject matter of Example 56 optionally includes call the Publish API of WiFi Aware and transmit discovery beacons.

[0163] Example 58 is a method to determine proximity of cellular devices by configuring measurement configuration to devices and getting measurement reports based on this configuration.

[0164] In Example 59, the subject matter of Example 58 optionally includes shall contain information required to call the Subscribe API of WiFi Aware.

[0165] In Example 60, the subject matter of any one or more of

Examples 58-59 optionally include may contain device specific matching filter to be able to determine proximity of a particular device to the configured device. [0166] In Example 61 , the subject matter of any one or more of

Examples 58-60 optionally include can contain report quantities that shall be reported back to network by the configured device.

[0167] Example 62 is a method for reporting proximity by sending measurement report to network when discovery event triggered by WiFi Aware.

[0168] In Example 63, the subject matter of Example 62 optionally includes shall contain zero or more report quantities which can be used by network to determine nearby devices.

[0169] In Example 64, the subject matter of Example 63 optionally includes to act as a trigger for initiating a D2D connection between two devices in the measurement report.

[0170] In Example 65, the subject matter of any one or more of

Examples 63-64 optionally include to act as trigger for initiating D2D service between reporting device and other devices reported.

[0171] In Example 66, the subject matter of any one or more of

Examples 63-65 optionally include to act as trigger for acting upon proximity information derived from the report quantities included in measurement report.

[0172] Example 67 is a method wherein LTE devices indicate their capability of supporting Wi-Fi Aware (Wi-Fi NAN) to LTE network.

[0173] In Example 68, the subject matter of Example 67 optionally includes wherein LTE network or LTE devices may be replaced by any cellular devices in their corresponding cellular network.

[0174] Example 69 is a content identification mechanism where network generates Content Id for the downloaded content that can be shared using D2D links across devices. This Content Id represents a shareable content on a particular device uniquely in the network.

[0175] Example 70 is a method wherein LTE SERVICE APP registers as a Wi-Fi Aware service using predefined LTE service name, LTE service specific info and starts to subscribe for LTE service using Wi-Fi Aware specification.

[0176] Example 71 is an LTE SERIVCE APP capable of handling

Content ID generated in Example 70 along with any QoC parameters received by network. [0177] Example 72 is a content detection mechanism where a device subscribed for LTE service over Wi-Fi Aware gets a discovery event and from the info is able to derive Content Ids published from nearby device.

[0178] Example 73 is a method to establish D2D connection between two devices based on identifying the source device using the Content Id and sending D2D formation parameters to target device as a response to new content request that was sent as a part of Example 72.

[0179] Example 74 is a mechanism for content identification and proximity detection where Content Ids discovered by a device and any other service specific info discovered using Wi-Fi Aware are sent to the network along with the request for new data/content from network.

[0180] Example 75 is a content identification mechanism and proximity detection mechanism at network side using the Content Id, new content request and any other service specific info to determine that a D2D link between the two devices is suitable to be formed.

[0181] In Example 76, the subject matter of Example 75 optionally includes may comprise of but not limited to LTE D2D link, or Wi-Fi Direct link.

[0182] In Example 77, the subject matter of any one or more of

Examples 75-76 optionally include D link in Example 75 from source device using Content Id. The LTE service APP identifies the content associated with the Content Id.

[0183] Example 78 is a method wherein LTE devices indicate their capability of supporting Wi-Fi Aware (Wi-Fi NAN) to LTE network.

[0184] In Example 79, the subject matter of Example 78 optionally includes in the above Example LTE network or LTE devices may be replaced by any cellular devices in their corresponding cellular network.

[0185] Example 80 is a Service identification mechanism where LTE or a 3 GPP modem registers with Wi-Fi as a service.

[0186] In Example 81 , the subject matter of Example 80 optionally includes LTE SERVICE APP registers as a Wi-Fi Aware service using predefined LTE service name, LTE service specific info and starts to subscribe for LTE service using Wi-Fi Aware specification.

[0187] Example 82 is a method wherein Wi-Fi Aware parameters are broadcast in system information. [0188] In Example 83, the subject matter of Example 82 optionally includes the system information may be emergency system information sued for ETWS and the Wi-Fi Aware info correspond to the E-Info to be used to publish this ETWS info over Wi-Fi Aware.

[0189] Example 84 is a LTE SERVICE APP capable of using "validity time" provided by network to re-publish the ETWS info received from peer device.

[0190] In Example 85, the subject matter of Example 84 optionally includes may comprise of but not limited to LTE D2D link, or Wi-Fi Direct link.

[0191] Example 86 is a LTE SERIVCE APP capable of handling E-Info present in system info and using that to publish ETWS info over Wi-Fi Aware.

[0192] Example 87 is a LTE SERVICE APP capable of establishing

D2D connection to get ETWS information from peer device.

[0193] The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that may be practiced. These embodiments are also referred to herein as "examples." Such examples may include elements in addition to those shown or described.

However, the present inventors also contemplate examples in which only those elements shown or described are provided. Moreover, the present inventors also contemplate examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.

[0194] All publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) should be considered supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.

[0195] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In the appended claims, the terms "including" and "in which" are used as the plain- English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[0196] The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with each other. Other embodiments may be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is to allow the reader to quickly ascertain the nature of the technical disclosure and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. This should not be interpreted as intending that an unclaimed disclosed feature is essential to any claim. Rather, inventive subject matter may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed

Description, with each claim standing on its own as a separate embodiment. The scope of the embodiments should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.