IDC-11614US03
`
`METHODS TO ENABLE WLAN PROXIMITY SERVICE
`
`CROSS REFERENCE TO RELATED APPLICATIONS
`
`[0001]
`
`This application is a continuation of US. Patent Application No.
`
`14/440,312 filed May 1, 2015, which claims the benefit of PCT Application No.
`
`PCT/US2013/067986, filed November 1, 2013, and US. provisional application No.
`
`61/721,321, filed November 1, 2012, the contents of which are hereby incorporated
`
`by reference herein.
`
`BACKGROUND
`
`[0002]
`
`Proximity-based services involve devices that are within proximity of
`
`each other. These devices are able to exchange data, for example,
`
`if they are
`
`running similar applications.
`
`[0003]
`
`Currently, traffic and signaling are generally routed in the network,
`
`and proximity-based services are not widely implemented. However,
`
`there are
`
`widespread applications for which proximity based services may be desired,
`
`including: commercial/social use, network offloading, public safety, integration of
`
`current infrastructure services, and to assure the consistency of the user experience
`
`including reachability and mobility aspects.
`
`[0004]
`
`Accordingly, methods and apparatus to enable wireless local area
`
`network based proximity service are desired.
`
`SUMMARY
`
`[0005]
`
`Described herein are methods and apparatus for enabling a wireless
`
`local area network (WLAN). A network may be configured to establish a WLAN
`
`Proximity Service (ProSe) connection between WLAN ProSe capable wireless
`
`transmit/receive units (WTRUs) based on a trigger or request. The triggers or
`
`requests for establishing the WLAN ProSe connection may be generated by the
`
`WLAN ProSe capable WTRU or come from the network. The methods further
`
`describe how to enable an evolved-Node-B (eNB) or Mobility Management Entity
`
`(MME) to discover an access point (AP) in a predetermined area to facilitate the
`
`4530815-1
`
`_ 1-
`
`

`

`IDC-11614US03
`
`WLAN ProSe
`
`connection. Other
`
`described methods
`
`facilitate
`
`connection
`
`establishment procedures, for example,
`
`the network may provide configuration
`
`information to the WTRU via Radio Resource Control (RRC) or Non-Access Stratum
`
`(NAS) signaling to establish the connection. The WLAN ProSe connection may be
`
`via a WLAN AP or a WLAN ProSe direct link connection between WLAN ProSe
`
`capable WTRU(s).
`
`[0006]
`
`In an example direct link method, a WLAN ProSe capable WTRU
`
`triggers or requests an establishment of a WLAN ProSe connection with other
`
`WLAN ProSe capable WTRU(s), where a ProSe discovery process is used to
`
`determine the presence of other WLAN ProSe capable WTRU(s). The WTRU
`
`receives configuration information from a network node to facilitate the WLAN
`
`ProSe connection to other WLAN ProSe capable WTRU(s). The configuration
`
`information includes one of a WLAN ID of the other WLAN ProSe capable
`
`WTRU(s), a medium access control (MAC) ID of the other WLAN ProSe capable
`
`WTRU(s), a WLAN access point Service Set Identification (SSID) or Basic SSID
`
`(BSSID), a frequency or channel number, a beacon interval, and timing information.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0007]
`
`A more detailed understanding may be had from the following
`
`description, given by way of example in conjunction with the accompanying
`
`drawings wherein:
`
`[0008]
`
`FIG. 1A is a system diagram of an example communications system in
`
`which one or more disclosed embodiments may be implemented;
`
`[0009]
`
`FIG. 1B is a system diagram of an example wireless transmit/receive
`
`unit (WTRU) that may be used within the communications system illustrated in
`
`FIG. 1A;
`
`[0010]
`
`FIG. 1C is a system diagram of an example radio access network and
`
`an example core network that may be used within the communications system
`
`illustrated in FIG. 1A;
`
`4530815-1
`
`

`

`IDC-11614USO3
`
`[0011]
`
`FIG. 2 shows an example scenario where a network or wireless
`
`transmit/receive units (WTRUs) determine that they are within a predetermined
`
`proximity;
`
`[0012]
`
`FIG.
`
`3
`
`shows
`
`an example of additional paths
`
`for proximity
`
`communication;
`
`[0013]
`
`FIG. 4 shows an example where the data path for communication is
`
`WTRU to WTRU directly over an air interface;
`
`[0014]
`
`FIG. 5 shows an example method wherein communication traffic is
`
`offloaded over Wi-Fi;
`
`[0015]
`
`FIG. 6 shows two example cases of enabling proximity service (ProSe)
`
`using wireless local area network (WLAN);
`
`[0016]
`
`FIG. 7 is a flow diagram of an example method for WLAN ProSe
`
`connectivity via a WLAN AP;
`
`[0017]
`
`FIG. 8 shows a flowchart for a direct link connection between at least
`
`two WLAN ProSe capable WTRUs; and
`
`[0018]
`
`FIG. 9 shows a flowchart of a method to enable WLAN ProSe
`
`connections.
`
`DETAILED DESCRIPTION
`
`[0019]
`
`FIG. 1A is a diagram of an example communications system 100 in
`
`which
`
`one
`
`or more
`
`disclosed
`
`embodiments may be
`
`implemented. The
`
`communications system 100 may be a multiple access system that provides content,
`
`such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
`
`The communications system 100 may enable multiple wireless users to access such
`
`content through the sharing of system resources, including wireless bandwidth. For
`
`example, the communications systems 100 may employ one or more channel access
`
`methods, such as code division multiple access (CDMA),
`
`time division multiple
`
`access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA
`
`(OFDMA), single-carrier FDMA (SC-FDMA), and the like.
`
`4530815-1
`
`

`

`IDC-11614USO3
`
`[0020]
`
`As shown in FIG. 1A, the communications system 100 may include
`
`wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access
`
`network (RAN) 104, a core network 106, a public switched telephone network
`
`(PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated
`
`that the disclosed embodiments contemplate any number of WTRUs, base stations,
`
`networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d
`
`may be any type of device configured to operate and/or communicate in a wireless
`
`environment. By way of example,
`
`the WTRUs 102a, 102b, 102c, 102d may be
`
`configured to transmit and/or receive wireless signals and may include user
`
`equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a
`
`cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a
`
`netbook, a personal computer, a wireless sensor, consumer electronics, and the like.
`
`[0021]
`
`The communications systems 100 may also include a base station 114a
`
`and a base station 114b. Each of the base stations 114a, 114b may be any type of
`
`device configured to wirelessly interface with at least one of the WTRUs 102a, 102b,
`
`102c, 102d to facilitate access to one or more communication networks, such as the
`
`core network 106, the Internet 110, and/or the networks 112. By way of example,
`
`the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an
`
`eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a
`
`wireless router, and the like. While the base stations 114a, 114b are each depicted
`
`as a single element, it will be appreciated that the base stations 114a, 114b may
`
`include any number of interconnected base stations and/or network elements.
`
`[0022]
`
`The base station 114a may be part of the RAN 104, which may also
`
`include other base stations and/or network elements (not shown), such as a base
`
`station controller (BSC), a radio network controller (RNC), relay nodes, etc. The
`
`base station 114a and/or the base station 114b may be configured to transmit and/or
`
`receive wireless signals within a particular geographic region, which may be
`
`referred to as a cell (not shown). The cell may further be divided into cell sectors.
`
`For example, the cell associated with the base station 114a may be divided into
`
`three sectors. Thus, in one embodiment, the base station 114a may include three
`
`4530815-1
`
`-4-
`
`

`

`IDC-11614US03
`
`transceivers, i.e., one for each sector of the cell. In another embodiment, the base
`
`station 114a may employ multiple-input multiple output (MIMO) technology and,
`
`therefore, may utilize multiple transceivers for each sector of the cell.
`
`[0023]
`
`The base stations 114a, 114b may communicate with one or more of
`
`the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any
`
`suitable wireless communication link (e.g.,
`
`radio frequency (RF), microwave,
`
`infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be
`
`established using any suitable radio access technology (RAT).
`
`[0024]
`
`More specifically, as noted above, the communications system 100 may
`
`be a multiple access system and may employ one or more channel access schemes,
`
`such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the
`
`base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement
`
`a radio technology such as Universal Mobile Telecommunications System (UMTS)
`
`Terrestrial Radio Access (UTRA), which may establish the air interface 116 using
`
`wideband CDMA (WCDMA). WCDMA may include communication protocols such
`
`as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may
`
`include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink
`
`Packet Access (HSUPA).
`
`[0025]
`
`In another embodiment, the base station 114a and the WTRUs 102a,
`
`102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial
`
`Radio Access (E-UTRA), which may establish the air interface 116 using Long Term
`
`Evolution (LTE) and/or LTE-Advanced (LTE-A).
`
`[0026]
`
`In other embodiments, the base station 114a and the WTRUs 102a,
`
`102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide
`
`Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X,
`
`CDMA2000 EV—DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95),
`
`Interim Standard 856 (IS-856), Global System for Mobile communications (GSM),
`
`Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the
`
`like.
`
`4530815-1
`
`

`

`IDC-11614USO3
`
`[0027]
`
`The base station 114b in FIG. 1A may be a wireless router, Home Node
`
`B, Home eNode B, or access point, for example, and may utilize any suitable RAT
`
`for facilitating wireless connectivity in a localized area, such as a place of business,
`
`a home, a vehicle, a campus, and the like. In one embodiment, the base station 114b
`
`and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11
`
`to establish a wireless local area network (WLAN). In another embodiment, the
`
`base station 114b and the WTRUs 102c, 102d may implement a radio technology
`
`such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet
`
`another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize
`
`a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to
`
`establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may
`
`have a direct connection to the Internet 110. Thus, the base station 114b may not be
`
`required to access the Internet 1 10 via the core network 106.
`
`[0028]
`
`The RAN 104 may be in communication with the core network 106,
`
`which may be any type of network configured to provide voice, data, applications,
`
`and/or voice over internet protocol (VoIP) services to one or more of the WTRUs
`
`102a, 102b, 102c, 102d. For example, the core network 106 may provide call control,
`
`billing services, mobile
`
`location-based services, pre-paid calling,
`
`Internet
`
`connectivity, video distribution, etc., and/or perform high-level security functions,
`
`such as user authentication. Although not shown in FIG. 1A, it will be appreciated
`
`that the RAN 104 and/or the core network 106 may be in direct or indirect
`
`communication with other RANs that employ the same RAT as the RAN 104 or a
`
`different RAT. For example, in addition to being connected to the RAN 104, which
`
`may be utilizing an E-UTRA radio technology, the core network 106 may also be in
`
`communication with another RAN (not shown) employing a GSM radio technology.
`
`[0029]
`
`The core network 106 may also serve as a gateway for the WTRUs
`
`102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other
`
`networks 112. The PSTN 108 may include circuit-switched telephone networks that
`
`provide plain old telephone service (POTS). The Internet 110 may include a global
`
`system of interconnected computer networks and devices
`
`that use common
`
`4530815-1
`
`-6-
`
`

`

`IDC-11614USO3
`
`communication protocols, such as the transmission control protocol (TCP), user
`
`datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet
`
`protocol suite. The networks 112 may include wired or wireless communications
`
`networks owned and/or operated by other service providers. For example,
`
`the
`
`networks 112 may include another core network connected to one or more RANs,
`
`which may employ the same RAT as the RAN 104 or a different RAT.
`
`[0030]
`
`Some or
`
`all of
`
`the WTRUs
`
`102a,
`
`102b,
`
`102c,
`
`102d in the
`
`communications system 100 may include multi-mode capabilities, i.e., the WTRUs
`
`102a, 102b, 102c, 102d may include multiple transceivers for communicating with
`
`different wireless networks over different wireless links. For example, the WTRU
`
`102c shown in FIG. 1A may be configured to communicate with the base station
`
`114a, which may employ a cellular-based radio technology, and with the base
`
`station 114b, which may employ an IEEE 802 radio technology.
`
`[0031]
`
`FIG. 1B is a system diagram of an example WTRU 102. As shown in
`
`FIG. 1B,
`
`the WTRU 102 may include a processor 118, a transceiver 120, a
`
`transmit/receive element
`
`122,
`
`a speaker/microphone
`
`124,
`
`a keypad 126,
`
`a
`
`display/touchpad 128, non-removable memory 130, removable memory 132, a power
`
`source 134, a global positioning system (GPS) chipset 136, and other peripherals
`
`138. It will be appreciated that the WTRU 102 may include any sub-combination of
`
`the foregoing elements while remaining consistent with an embodiment.
`
`[0032]
`
`The processor 118 may be a general purpose processor, a special
`
`purpose processor, a conventional processor, a digital signal processor (DSP), a
`
`plurality of microprocessors, one or more microprocessors in association with a DSP
`
`core, a controller, a microcontroller, Application Specific Integrated Circuits
`
`(ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of
`
`integrated circuit
`
`(IC), a state machine, and the like. The processor 118 may
`
`perform signal coding, data processing, power control,
`
`input/output processing,
`
`and/or any other functionality that enables the WTRU 102 to operate in a wireless
`
`environment. The processor 118 may be coupled to the transceiver 120, which may
`
`be coupled to the transmit/receive element 122. While FIG. 1B depicts the processor
`
`4530815-1
`
`-7-
`
`

`

`IDC-11614USO3
`
`118 and the transceiver 120 as separate components, it will be appreciated that the
`
`processor 118 and the transceiver 120 may be integrated together in an electronic
`
`package or chip.
`
`[0033]
`
`The transmit/receive element 122 may be configured to transmit
`
`signals to, or receive signals from, a base station (e.g., the base station 114a) over
`
`the air interface 116. For example, in one embodiment, the transmit/receive element
`
`122 may be an antenna configured to transmit and/or receive RF signals. In another
`
`embodiment,
`
`the transmit/receive element
`
`122 may be an emitter/detector
`
`configured to transmit and/or receive IR, UV, or visible light signals, for example. In
`
`yet another embodiment, the transmit/receive element 122 may be configured to
`
`transmit and receive both RF and light signals. It will be appreciated that the
`
`transmit/receive element 122 may be configured to transmit and/or receive any
`
`combination of Wireless signals.
`
`[0034]
`
`In addition, although the transmit/receive element 122 is depicted in
`
`FIG.
`
`1B as a single element,
`
`the WTRU 102 may include any number of
`
`transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO
`
`technology. Thus, in one embodiment, the WTRU 102 may include two or more
`
`transmit/receive elements 122 (e.g., multiple antennas)
`
`for
`
`transmitting and
`
`receiving Wireless signals over the air interface 1 16.
`
`[0035]
`
`The transceiver 120 may be configured to modulate the signals that
`
`are to be transmitted by the transmit/receive element 122 and to demodulate the
`
`signals that are received by the transmit/receive element 122. As noted above, the
`
`WTRU 102 may have multi-mode capabilities. Thus,
`
`the transceiver 120 may
`
`include multiple transceivers for enabling the WTRU 102 to communicate via
`
`multiple RATs, such as UTRA and IEEE 802.11, for example.
`
`[0036]
`
`The processor 118 of the WTRU 102 may be coupled to, and may
`
`receive user input data from, the speaker/microphone 124, the keypad 126, and/or
`
`the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic
`
`light-emitting diode (OLED) display unit). The processor 118 may also output user
`
`data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad
`
`4530815-1
`
`-8-
`
`

`

`IDC-11614USO3
`
`128. In addition, the processor 118 may access information from, and store data in,
`
`any type of suitable memory, such as the non-removable memory 130 and/or the
`
`removable memory 132. The non-removable memory 130 may include random-
`
`access memory (RAM), read-only memory (ROM), a hard disk, or any other type of
`
`memory storage device. The removable memory 132 may include a subscriber
`
`identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and
`
`the like. In other embodiments, the processor 118 may access information from, and
`
`store data in, memory that is not physically located on the WTRU 102, such as on a
`
`server or a home computer (not shown).
`
`[0037]
`
`The processor 118 may receive power from the power source 134, and
`
`may be configured to distribute and/or control the power to the other components in
`
`the WTRU 102. The power source 134 may be any suitable device for powering the
`
`WTRU 102. For example, the power source 134 may include one or more dry cell
`
`batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride
`
`(NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
`
`[0038]
`
`The processor 118 may also be coupled to the GPS chipset 136, which
`
`may be configured to provide location information (e.g., longitude and latitude)
`
`regarding the current location of the WTRU 102. In addition to, or in lieu of, the
`
`information from the GPS chipset 136,
`
`the WTRU 102 may receive location
`
`information over the air interface 116 from a base station (e.g., base stations 114a,
`
`1 14b) and/or determine its location based on the timing of the signals being received
`
`from two or more nearby base stations. It will be appreciated that the WTRU 102
`
`may acquire location information by way of any suitable location-determination
`
`method while remaining consistent with an embodiment.
`
`[0039]
`
`The processor 118 may further be coupled to other peripherals 138,
`
`which may include one or more software and/or hardware modules that provide
`
`additional
`
`features,
`
`functionality and/or wired or wireless connectivity. For
`
`example,
`
`the peripherals 138 may include an accelerometer, an e-compass, a
`
`satellite transceiver, a digital camera (for photographs or video), a universal serial
`
`bus (USB) port, a vibration device, a television transceiver, a hands free headset, a
`
`4530815-1
`
`-9-
`
`

`

`IDC-11614USO3
`
`Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player,
`
`a media player, a video game player module, an Internet browser, and the like.
`
`[0040]
`
`FIG. 1C is a system diagram of the RAN 104 and the core network
`
`106 according to an embodiment. As noted above, the RAN 104 may employ an E-
`
`UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the
`
`air interface 116. The RAN 104 may also be in communication with the core
`
`network 106.
`
`[0041]
`
`The RAN 104 may include eNode-Bs 140a, 140b, 140c, though it will be
`
`appreciated that
`
`the RAN 104 may include any number of eNode-Bs while
`
`remaining consistent with an embodiment. The eNode-Bs 140a, 140b, 140c may
`
`each include one or more transceivers for communicating with the WTRUs 102a,
`
`102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 140a, 140b,
`
`140c may implement MIMO technology. Thus, the eNode-B 140a, for example, may
`
`use multiple antennas to transmit wireless signals to, and receive wireless signals
`
`from, the WTRU 102a.
`
`[0042]
`
`Each of the eNode-Bs 140a, 140b, 140c may be associated with a
`
`particular cell
`
`(not shown) and may be configured to handle radio resource
`
`management decisions, handover decisions, scheduling of users in the uplink and/or
`
`downlink, and the like. As shown in FIG. 1C, the eNode-Bs 140a, 140b, 140c may
`
`communicate with one another over an X2 interface.
`
`[0043]
`
`The core network 106 shown in FIG. 1C may include a mobility
`
`management gateway (MME) 142, a serving gateway 144, and a packet data
`
`network (PDN) gateway 146. While each of the foregoing elements are depicted as
`
`part of the core network 106, it will be appreciated that any one of these elements
`
`may be owned and/or operated by an entity other than the core network operator.
`
`[0044]
`
`The MME 142 may be connected to each of the eNode-Bs 142a, 142b,
`
`142c in the RAN 104 via an 81 interface and may serve as a control node. For
`
`example, the MME 142 may be responsible for authenticating users of the WTRUs
`
`102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving
`
`gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The
`
`4530815-1
`
`-10-
`
`

`

`IDC-11614USO3
`
`MME 142 may also provide a control plane function for switching between the RAN
`
`104 and other RANs (not shown) that employ other radio technologies, such as GSM
`
`or WCDMA.
`
`[0045]
`
`The serving gateway 144 may be connected to each of the eNode Bs
`
`140a, 140b, 140c in the RAN 104 via the 81 interface. The serving gateway 144 may
`
`generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
`
`The serving gateway 144 may also perform other functions, such as anchoring user
`
`planes during inter-eNode B handovers, triggering paging when downlink data is
`
`available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the
`
`WTRUs 102a, 102b, 102c, and the like.
`
`[0046]
`
`The serving gateway 144 may also be connected to the PDN gateway
`
`146, which may provide the WTRUs 102a, 102b, 102c with access to packet-
`
`switched networks, such as the Internet 110, to facilitate communications between
`
`the WTRUs 102a, 102b, 102c and IP-enabled devices.
`
`[0047]
`
`The core network 106 may facilitate communications with other
`
`networks. For example, the core network 106 may provide the WTRUs 102a, 102b,
`
`102c with access to circuit-switched networks, such as the PSTN 108, to facilitate
`
`communications between the WTRUs 102a, 102b, 102c and traditional land-line
`
`communications devices. For example, the core network 106 may include, or may
`
`communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server)
`
`that serves as an interface between the core network 106 and the PSTN 108. In
`
`addition, the core network 106 may provide the WTRUs 102a, 102b, 102c with
`
`access to the networks 112, which may include other wired or wireless networks
`
`that are owned and/or operated by other service providers.
`
`[0048]
`
`Proximity-based Services may involve the WTRU proximity discovery,
`
`the WTRU consent
`
`to being discoverable, contactable or conversational,
`
`the
`
`proximity WTRU to WTRU communications and the controllability and policies by
`
`the network or operators to the discovery, discoverability and the subsequent forms
`
`of communication.
`
`4530815-1
`
`-11-
`
`

`

`IDC-11614USO3
`
`[0049]
`
`FIG. 2 shows a WTRUl 205, a WTRU2 210, an eNB 215, an eNB 220
`
`and a Serving Gateway (SGW) and Packet Data Network Gateway (PDN GW)
`
`SGW/PDN GW 225 in an example embodiment where the network or WTRUs,
`
`(WTRUl 205, WTRU2 210 or both), determine that they are within a predetermined
`
`proximity. In this embodiment, communication between WTRUl 205 and WTRU2
`
`210 is performed via eNB 215, eNB 220 and the core network (CN) nodes such as
`
`the SGW/PDN GW 225.
`
`[0050]
`
`Communications between proximity WTRUs may be enhanced to take
`
`other paths such as direct, (i.e. direct radio path in licensed/unlicensed spectrum
`
`within certain distances), or indirect, (through network elements — intra/inter-cell
`
`or intra/inter-eNB), or S-GW, and the like), which may be controlled by the network
`
`or by operators.
`
`[0051]
`
`FIG. 3 shows a WTRUl 305, a WTRU2 310, an eNB 315, an eNB 320
`
`and a SGW/PDN GW 325 in an embodiment of an indirect path for proximity
`
`communication. In this embodiment, the network or WTRUs, (WTRUl 305, WTRU2
`
`310 or both), determine that they are within a predetermined proximity. The
`
`communication between WTRUl 305 and WTRU2 310 is performed via eNB 315.
`
`[0052]
`
`FIG. 4 shows a WTRUl 405, a WTRU2 410, an eNB 415, an eNB 420
`
`and a SGW/PDN GW 425 in an embodiment of a direct path for proximity
`
`communication. In this embodiment, the network or WTRUs, (WTRUl 405, WTRU2
`
`410 or both), determine that they are within a predetermined proximity. The
`
`communication between WTRUl 405 and WTRU2 310 is performed directly over
`
`the air interface.
`
`[0053]
`
`The proximity service data path selection, (direct, or indirect over a
`
`certain path in the infrastructure), may be determined by the radio or network
`
`coverage, load conditions or by policies set by network or operators. Proximity-
`
`Based Services are expected to be supported in network sharing deployments.
`
`[0054]
`
`In another embodiment, a direct communication may be used between
`
`proximity service (ProSe) enabled WTRUs that have wireless local area network
`
`(WLAN) capability. To enable such communication,
`
`the Third Generation
`
`4530815-1
`
`_ 12 _
`
`

`

`IDC-11614USO3
`
`Partnership Project
`
`(3GPP) Evolved Packet Core (EPC) may provide WLAN
`
`configuration information to the WTRUs involved in proximity communication.
`
`[0055]
`
`In another embodiment, the cellular network may be configured to
`
`switch a communication from a cellular infrastructure path to a WLAN ProSe path
`
`and vice versa. This switch may be initiated, for example, when two WTRUs are
`
`engaged in a data session, (including one or more flows), routed over the mobile
`
`network operator’s (MNO’s) core network infrastructure and these WTRUs move
`
`within WLAN communication range. The cellular system may switch their data
`
`session to the WLAN ProSe communication path. Later, when the same WTRUs
`
`move out of WLAN communication range, the cellular system may switch their data
`
`session back to the MNO’s infrastructure path.
`
`[0056]
`
`Wi-Fi (WLANs) may be used to offload a 3GPP Long Term Evolution
`
`(LTE) system from user plane traffic. In one embodiment, an eNB may be collocated
`
`with a Wi-Fi access point (AP), the eNB may dynamically or semi-statically send
`
`data over an LTE air interface and a Wi-Fi AP air interface. The LTE user plane
`
`traffic may be partially or totally offloaded on to Wi-Fi. The offload method, e.g. the
`
`protocol layer, (such as Packet Data Convergence Protocol (PDCP), Radio Link
`
`Control (RLC) and the like), at which offload may occur may be preconfigured or
`
`dynamically selected.
`
`[0057]
`
`FIG.
`
`5
`
`shows
`
`an
`
`example
`
`embodiment
`
`and method where
`
`communication traffic is offloaded over Wi-Fi. The embodiment shows an AP 505,
`
`an eNB 510, a WTRU 515, a SGW 520, a MME 525 and a PDN GW 530. The AP 505
`
`is connected to the collocated eNB 510 via link 540,
`
`(including interface for
`
`exchanging information). The eNB 510 is configured to offload a portion of the
`
`download traffic being sent over LTE link/air interface 550 over the Wi-Fi link/air
`
`interface 560. On a condition that the eNB 510 has determined that the WTRU 515
`
`is connected to the Wi-Fi AP 505, the eNB 510 may offload downlink traffic over the
`
`Wi-Fi AP link 560. The WTRU 515 may be configured to receive data from the eNB
`
`510 and the Wi-Fi AP 505 nearly simultaneously. In the uplink, the WTRU 515 may
`
`be configured to transmit a portion of data over the LTE air interface 550 and
`
`4530815-1
`
`-13-
`
`

`

`IDC-11614USO3
`
`another portion of data over the Wi-Fi air interface 560. The Wi-Fi AP 505 may
`
`then be configured to forward to the eNB 510 data received from the WTRU 515, via
`
`interface 540 that connects the eNB 510 and the AP 505.
`
`[0058]
`
`To enable proximity connection between two WTRUs, a new network
`
`node is being defined in the 3GPP network architecture called a proximity service
`
`(ProSe) server or function. The ProSe server in the network, (as part of EPS), has a
`
`reference point towards the ProSe Application Server, towards the EPC and the
`
`WTRU. The functionality may include, but is not restricted to: interworking via a
`
`reference point towards third party applications; authorization and configuration of
`
`the WTRU for discovery and direct communication are controlled by a home public
`
`land mobile network (HPLMN) ProSe function in a non-roaming case and by the
`
`HPLMN or visited public land mobile network (VPLMN) ProSe function in a
`
`roaming case; enable the functionality of the EPC level ProSe discovery; ProSe
`
`related new subscriber data and /handling of data storage; handling of ProSe
`
`identities; security related functionality; provide control towards the EPC for policy
`
`related functionality; and provide functionality for charging, (via or outside of EPC,
`
`e.g. offline charging).
`
`[0059]
`
`FIG. 6 shows two example embodiments or cases of enabling ProSe
`
`using WLAN. A first case or embodiment 600 includes an eNB 605, a WLAN AP
`
`610, a WTRUl 615 and a WTRUl 620. The eNB 605 is connected to the WLAN AP
`
`610 via a link 612, which may be, for example, an I/F interface. A WLAN ProSe
`
`connection 622 is shown between devices connected to the WLAN AP 610, which
`
`may be controlled by a 3GPP system, for example, via eNB 605. A second case or
`
`embodiment 650 shows a direct link connection 672 between WTRU3 660 and
`
`WTRU4 670. In this case 650, there may be no WLAN AP in the WLAN ProSe
`
`connection 672. This
`
`type of direct WLAN ProSe connection 672 may be
`
`implemented as a WLAN ad hoc connection, a Wi-Fi direct type of connection or any
`
`other direct
`
`link connection. As described herein below,
`
`the WLAN ProSe
`
`connections 622 and 672 may be managed by the eNB 605 or the 3GPP system. The
`
`configuration for the WLAN AP 610 may be provided by the 3GPP system. The
`
`4530815-1
`
`_ 14-
`
`

`

`IDC-11614USO3
`
`3GPP system may be able to request when to start or tear down the WLAN ProSe
`
`connection or change it back to the 3GPP based ProSe connection. A ProSe server
`
`680 may be included for use in both embodiments 600 and 650 as described herein
`
`below. Communication between the ProSe server 680 and a WTRU, such as WTRUs
`
`615, 620, 660 and 670 may take place either via user plane or control plane. For
`
`example, communications may take place between a mobility management entity
`
`(MME) or Non-access stratum (NAS) messaging. The ProSe server 680 authorizes
`
`the ProSe connection and assigns ProSe IDs. The term cellular system or network
`
`includes, but is not limited to, a 3GPP system or network, which in turn includes,
`
`but is not limited to, a LTE system or network. The term WLAN includes, but is not
`
`limited to, WiFi, 802.11 based systems and the like. The terms system and network
`
`are used interchangeably.
`
`[0060]
`
`Described herein are triggers for establishing a WLAN ProSe
`
`connection. The triggers for establishing the WLAN ProSe connection may be based
`
`on triggers initiated by the WTRU or triggers that may be signaled from the cellular
`
`network such as a 3GPP network. The cellular network may establish a WLAN
`
`ProSe connection between WLAN-capable WTRUs based on these triggers. These
`
`triggers may also be used to move an existing LTE based ProSe connection to a
`
`WLAN based ProSe connection, for example.
`
`[0061]
`
`The WTRU may initiate triggers including user preference triggers,
`
`application preference triggers, WTRU switch triggers, and public safety triggers.
`
`[0062]
`
`In an embodiment, user preference triggers may be used for
`
`establishing a WLAN ProSe connection. A user may prefer to use WLAN for ProSe
`
`communication, for example, for billing reasons or saving network bandwidth. The
`
`WTRU may include a configuration/setting to select a preference for WLAN ProSe
`
`offloading. The user may select WLAN ProSe as a preferred choice for ProSe. This
`
`preference may be indicated to the network upon initial registration or separate
`
`signaling requesting a ProSe connection.
`
`If the request
`
`is sent upon initial
`
`registration the WTR