Communications – Marian Rudolf, Benoit Pelletier, Diana Pani, Paul Marinier, Samian Kaur, Martino Freda, InterDigital Patent Holdings Inc

Abstract for “Device to device (D2D), pre-emption, and access control”

“Systems, methods and instrumentalities are disclosed for determining access control, channel and signaling priority. A wireless transmit/receive device (WTRU), may include a processor that determines the device-to-device data (D2D), to be transmitted. The WTRU can determine whether D2D data can be transmitted. The WTRU might determine the availability of scheduling assignment (SA), resources for priority-based D2D data signal signals. The WTRU can select from a number of available SA resources to transmit priority-based D2D data signals. The WTRU can transmit D2D data. D2D data may only be transmitted to the selected SA resources.

Background for “Device to device (D2D), pre-emption, and access control”

For public safety communications, “Device to device (D2D), communications can be used for a variety of purposes. D2D communications can be linked to standard technologies such as LTE and IEEE. Access control and/or priority handling can be used in LTE systems to allow terminals to access and/or use wireless resources.

“Systems, methods and instrumentalities are disclosed for determining access control, channel and signaling priority. A wireless transmit/receive device (WTRU), may include a processor that determines the device-to-device data (D2D), to be transmitted. The WTRU can determine whether D2D data can be transmitted. The WTRU might determine the availability of scheduling assignment (SA), resources for priority-based D2D data signal signals. The WTRU can select from a number of available SA resources to transmit priority-based D2D data signals. The WTRU can transmit D2D data. D2D data may only be transmitted to the selected SA resources.

“The WTRU could be configured to select available SA resources from a preconfigured list of SA resources. The WTRU can be configured to either receive configuration signaling or determine the available SA resource from that signaling.

“Embodiments may contemplate priority reception or transmission for D2D relays (e.g., guaranteed resources). Embodiments envisage signaling for the use of (e.g. guaranteed) segregated resource.

A wireless transmit/receive device (WTRU), may include a receiver. The receiver can be set up to receive one or more radio resources in order to perform one or more scheduling assignments (SA). A processor may be part of the WTRU. The processor can be used to determine the first frequency domain SA (FDSA) pool. One or more SA may be allocated to at least one priority device-to?device (D2D), transmission in the first FD SA pool. A second FD SA pool may be determined by the processor. One or more SA may be allocated to at least one second priority D2D transmission in the second FD SA pool. A transmitter may be part of the WTRU. The transmitter could be set up to send at least one priority D2D transmission by using at least one radio resource to the one or more SAs from the first FD SA pools. The transmitter could be set up to send at least one second priority D2D transmitting using at least one radio resource for one or more SAs from the second FD SA Pool.

“A wireless transmit/receive device (WTRU), may be capable to communicate between devices (D2D). A receiver may be part of the WTRU. The receiver could be set up to receive at most one of the following: a D2D channel, or a D2D signal. A processor may be part of the WTRU. The processor can be programmed to determine whether at least one: a second D2D channel, or a first D2D signals is to be transmitted while at least one: the first D2D channel is being received. A processor could be programmed to determine the relative priority of the at most one of the following: The first D2D channel, the first D2D signals and the least one between: The second D2D channels or D2D signals. If the processor determines that the at minimum one of the: A second D2D Channel or D2D Signal is to be transmitted while at least the one of the first D2D channels or first D2D signals is being received, the processor may also be programmed to determine the number of D2D subframes to be used for D2D2D channels or D2Dchannel or the D2Dchannel or first D2Dchannel or the D2Dd channel or first D2Dchannel or the D2D subframes to be used to determine the higher relative priority The processor can be programmed to determine the number of D2D subframes that are to be used to receive which D2D channel, first D2D signal or second D2D signals.

“A wireless transmit/receive device (WTRU), may be capable to communicate between devices (D2D). A processor may be part of the WTRU. A processor could be programmed to send a pre-emption signal. The processor could be programmed to send the pre-emption indicator via a scheduling assignment. A transmitter may be part of the WTRU. The transmitter could be programmed to transmit the SA to another WTRU that is capable of D2D communication.

A wireless transmit/receive device (WTRU), may include a receiver. The receiver can be set up to receive one or more radio resources in order to perform one or more scheduling assignments (SA). A processor may be part of the WTRU. A processor could be used to create a first SA pool. One or more SA may be allocated to at least one D2D (first priority device-to?device) transmission. A second SA pool may be determined by the processor. One or more SA may be allocated to at least one of the second priority D2D transmissions. The processor can be programmed to compare the number of first priority scheduling events associated with one or several resources for the one or two SAs of the first SA pool to determine a threshold. A transmitter may be part of the WTRU. The transmitter can be set up to transmit at least one priority D2D transmission by using at least one radio resource. This radio resource will allow for one or more SAs from the first SA pool if the threshold is met.

“This section will provide a detailed description of the various Figures, as well as a reference to the various figures. This description gives an example of possible implementations. However, the details do not limit the scope or intent of the application. The articles?a? and?an? are used herein. Without further qualification or characterization, the articles?a? and?an? may be taken to refer to?one or more? For example,?at least one?.

“FIG. “FIG. Multiple access systems can be used to provide content to multiple wireless users. This includes voice, data and video as well as broadcasting, messaging, broadcast, and other services. Multiple wireless users may be able to access the same content via the communications system 100. This is possible through sharing system resources, including wireless broadband. One or more channel access methods may be used by communications systems 100, including code division multiple acces (CDMA), time division multiple access, TDMA, frequency division multiple accessibility (FDMA), orthogonal FDMA, OFDMA, single-carrier FDMA, SC-FDMA, and others.

“As shown at FIG. “As shown in FIG. Any type of device that can operate in a wireless environment, including the WTRUs 101 a, 102, 102, 102, and 102c, may be included in the WTRUs. The WTRUs 101 a,102 b and 102c may be used to transmit or receive wireless signals. They may also include user equipment (WTRU), mobile stations, fixed or mobile subscribers units, pagers, personal digital assistants (PDA), smartphones, laptops, netbooks, personal computers, wireless sensors, consumer electronics and other similar devices.

“Communications systems 100 may also contain a base stations 114a and 114b. Each of the base station 114a,114b can be any device that is capable of wirelessly interfacing with at least one WTRU 102a,102b,102c,102c,102d. This allows access to one or more networks such as the Internet 110, core network 106/107/109 and/or networks 112. The base stations 114a,114b could be any type of device that can wirelessly interface with at least one of the WTRUs 102 a,102 b, 102 c, 102 d to facilitate access to one or more communication networks such as the core network 106/107/109, the Internet 110, and/or the networks 112. Although the base stations of 114 and 114 are shown as one element, it is possible to see that the base stations of 114 and 114 may contain multiple interconnected bases stations or network elements.

“The base station (114a) may be part the RAN 103/104/105. This may include other base stations or network elements (not illustrated), such as a controller (BSC), radio network controller (RNC), relay nosdes, and so on. The base station (114 a) and/or base station (114 b) may be configured to transmit/or receive wireless signals within an area, which can be called a cell (not illustrated). Further, the cell can be broken down into cell sectors. The cell that is associated with base station 114a could be broken down into three sections. In one embodiment, the base stations 114a could include three transceivers. One for each sector. Another embodiment of the base station 114a may use multiple-input multiple out (MIMO) technology. Therefore, multiple transceivers may be used for each sector.

“The base stations (114 a,114 b) may communicate with one of the WTRUs (102 a), 102 (b), 102 (c), 102 (d), 102 (d) over an air interface (115/116/117), which could be any wireless communication link (e.g. radio frequency (RF), microwave (IR), ultraviolet(UV), visible light (UV), etc.). Any suitable radio access technology (RAT) may be used to establish the air interface 115/116/117.

“Moreover, the communications system 100 could be a multi-access system, which may use one or more channel access systems, such as CDMA and TDMA. The base station 114 a within the RAN 103/104/105, and the WTRUs 102 a, 102 b, 102 c, may implement a radio technology like Universal Mobile Telecommunications System, 102 a, 102 b or 102 c. This may establish the air interface 115/116/117 via wideband CDMA (WCDMA). WCDMA can include communication protocols like High-Speed Packet Access and/or Evolved HSPA. HSPA could include High Speed Downlink Packet Access, (HSDPA), and/or High Speed Uplink Packet Access, (HSUPA).

“Another embodiment may include the base station 114 a as well as the WTRUs 102 a-102 b and 102 c. This radio technology, Evolved UMTS Terrestrial Radio Access, (E-UTRA), may be used to establish the air interface 115/116/117 using LTE-Advanced and/or Long Term Evolution (LTE).

“The base station (114 b) in FIG. “The base station 114 b in FIG. One embodiment of the WTRUs (102 c,102 d) and base station 114 may use a radio technology like IEEE 802.11 to establish wireless local area networks (WLAN). Another embodiment is that the WTRUs 101 c,102 d and the base station 112 b may use a radio technology like IEEE 802.15 in order to establish a wireless personal network (WPAN). Another embodiment is that the WTRUs 101 c, 102 and 114 b may use a cell-based RAT (e.g. WCDMA, CDMA2000 GSM LTE-A, LTE-A). To establish a picocell and femtocell. FIG. FIG. 1A shows that the base station (114 b) may have an internet connection to the Internet 110. The base station 114b may not need to be connected to the Internet 110 via core network 106/107/109.

“The RAN 103/104/105 could be in communication to the core network106/107/109. This network may be any type that can provide voice, data and applications to one or more WTRUs (102 a,102 b and 102c), and/or high-level security functions such as user authentication. FIG. It is not shown in FIG. 1A. However, it is possible that the RAN 103/105/105 and/or core network 106/107/109 are in direct or indirect communications with other RANs using the same RAT or a different RAT. The core network 106/107/109 could be connected to the RAN 103/104/105 which may use an E-UTRA radio tech.

“The core network 106/107/109 could also be used as a gateway to the WTRUs 102 a and 102 b. The WTRUs 102 c, 102 d, 102 c, 102 d can access the PSTN 108, Internet 110 and/or other networks 112. The PSTN 108 could include circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 could include a global network of interconnected computer networks as well as devices that use common communication protocols such the transmission control protocol, user datagram protocol and internet protocol (IP) from the TCP/IP protocol suite. Other service providers may also own or operate wired and wireless communications networks. The networks 112 could include a core network that is connected to one or more of the RANs 103/104/105, or a different type of RAT.

“Some or all the WTRUs 101 a-102 b and 102c-102c,102c,102d in the communications network 100 may have multimode capabilities. For example, the WTRUs 102/102/102 b,102c,102c,102d in the communications systems 100 may contain multiple transceivers that allow communication with wireless networks using different wireless links. FIG. 2 shows the WTRU102 c. 1A could be set up to communicate with base station (114a), which may use a cellular radio technology, or with base station (114b), which may use an IEEE 802 radio tech.

“FIG. 1B is a system schematic of WTRU 102. FIG. FIG. 1B shows that the WTRU 102 could include a processor 118 and a transceiver 120. A transmit/receive device 122 may also be included. While the WTRU102 may contain any combination of the above elements, it will still be consistent with an embodiment. Embodiments may also contemplate that base stations (114 a) and (or the nodes base stations (114 b) may represent, such that but not limited to a transceiver station, (BTS), an access point, (AP), a Node B, a Node B, a Node B, an evolved node B (eNodeB), an home evolved node B (HeNB), and proxy nodes. 1B, and are described herein.

The processor 118 can be a general-purpose processor or a special-purpose processor. It may also include a conventional processor, a processor with digital signal processing (DSP), a plurality microprocessors and one or more DSP cores. A controller, a microcontroller as well as Application Specific Integrated Circuits. FPGAs circuits. Any other type of integrated circuit (IC), a state computer, and the like. The processor 118 can perform signal coding and data processing as well as power control, input/output, and/or other functionality that allows the WTRU102 to function in a wireless environment. The processor 118 can be connected to the transceiver 120. It may also be attached to the transmit/receive 122. FIG. FIG.

“The transmit/receive 122 can be used to transmit or receive signals from a base station (e.g. the base station 114a) via the air interfaces 115/116/117. One example is that the transmit/receive 122 could be an antenna capable of transmitting and/or receiving RF signals. Another embodiment of the transmit/receive 122 could be an emitter/detector that can transmit and/or receive IR, UV or visible light signals. Another embodiment of the transmit/receive 122 could be configured to transmit and/or receive light signals as well as RF. The transmit/receive device 122 can be configured to transmit and/or obtain any combination of wireless signals.

FIG. 1B is a single element. However, the WTRU 102 can include multiple transmit/receive components 122. MIMO technology may be used in the WTRU 102. In one embodiment, the WTRU 102 could include multiple transmit/receive elements 122 (e.g. multiple antennas) that transmit and receive wireless signals over the air interface 115/116/117.

“The transceiver 120 can be set up to modulate signals to be transmitted by transmit/receive elements 122 and demodulate signals to be received by transmit/receive elements 122. The WTRU 102 may be capable of multi-mode communication, as noted above. The transceiver 120 could include multiple transceivers to enable the WTRU 102 communicate via multiple RATs such as UTRA or IEEE 802.11, for instance.

“The processor 118 may be coupled to the WTRU102 speaker/microphone, keypad 126 and/or display/touchpad 128 and may receive user input data (e.g., liquid crystal display (LCD), organic light-emitting dime (OLED), display unit). The processor 118 can also output user data from the speaker/microphone, keypad 126 and/or display/touchpad 128, respectively. The processor 118 can access and store information in any type of memory. This includes the removable memory 132 and the non-removable storage 130. Non-removable memory 130 can include random-access memory, read-only memory and hard drives. A subscriber identity card (SIM), a memory stick or a secure digital card (SD) may be included in the removable memory 132. Other embodiments of the WTRU102 may allow the processor 118 to access and store information on memory other than that on the WTRU102. This could include data on a server or home computer (not illustrated).

“The power source 134 may supply power to processor 118. It may also be used to control and distribute power to other components of the WTRU 101. Any suitable device may be used to power the WTRU102. One example of a power source 134 is a set of dry cells (e.g. nickel-cadmium, nickel-zinc, nickel metal hydride, NiMH, lithium-ion, etc. “, solar cells, fuel cell, and other similar items.”

The processor 118 can also be connected to the GPS chipset 136. This chip may be used to provide location information, such as longitude and latitude, regarding the WTRU 102’s current location. The WTRU102 can receive information via the GPS chipset, 116, and 117. This information may be in addition to or instead of the GPS chipset. 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.”

“FIG. “FIG. The RAN 103 could use a UTRA radio to communicate with WTRUs 102 a and 102 b over the air interface 115. The RAN 103 could also be communicating with the core network 106. FIG. 1C: The RAN 103 could include Node-Bs 140 a. 140 b. 140 c. These may each contain one or more transceivers to communicate with the WTRUs 102 a. 102 b. 102 c via the air interface 115. Each of the Node-Bs 140 a to 140 b and 140 c can be associated with a specific cell within the RAN 103. RNCs 142 a and 142 b may be included in the RAN 103. While the RAN 103 could include as many Node-Bs or RNCs as you like, it will still be consistent with an embodiment.

“As shown at FIG. “As shown in FIG. 140 a-140 b, 140c and 140c can communicate with respective RNCs 140a, 140b, 140c via an Iub interface. An Iur interface may allow RNCs 142a, 142b to communicate with each other. Each of the RNCs 142 a, 142 b can be set up to control the Node-Bs 140, 140, and 140 c to whom it is connected. Each of the RNCs 142-142 a, 142-142 b can be configured to support or carry out other functions such as load control, outer loop power control and admission control.

“The core network (106) shown in FIG. 1C could include a media gateway 144, a mobile switch center (MSC), 146, a serving GPRS service node SGSN 148, and/or a gateway GPRS help node GGSN 150. Each of the elements shown above is part of the core network (106), but it should be noted that each element may be owned or operated by another entity.

“The RNC 142 a may be connected to MSC 146 in core network 106 via an IuCS Interface. MSC 146 could be connected to MGW 144. MSC 146 or MGW 144 could provide WTRUs 102 a to 102 b to 102 c access to circuit-switched network, such as the PSTN 108 to facilitate communications between WTRUs 102 a to 102 b and 102 c.

“The RNC 142 a may be connected to the SGSN 148 within the core network 106 via IuPS. The GGSN 150 may be connected to SGSN 148. The GGSN 150 and the SGSN 148 may connect to the WTRUs 102 a and 102 b and 102 c. They can also access packet-switched networks such as the Internet 110 to facilitate communications between the WTRUs 102 a and 102 b and 102 c.

“As mentioned above, the core network106 could also be connected with the networks 112, which might include other wired and wireless networks owned or operated by other service providers.

“FIG. “FIG. The RAN 104 could use an E-UTRA radio technique to communicate with WTRUs 102 a and 102 b over the air interface 116. The RAN 104 could also be communicating with the core network 107.

“The RAN 104 could include eNode Bs 160 a. 160 b. 160 c. However, it is possible that the RAN 104 can include as many eNode Bs as you like while still being consistent with an embodiment. Each of the eNodeBs 160, 160, and 160 c can include one or more transceivers to communicate with the WTRUs 101 a, 102, 102, and 102 over the air interface. 116 One embodiment may use MIMO technology in the eNode -Bs 160, 160, b, 160, c. The eNode -B 160a may, for instance, use multiple antennas to transmit and receive wireless signals to the WTRU102a.

“Each of eNode -Bs 160a, 160b, 160c may be associated to a particular cell (not illustrated) and configured to handle radio resource management, handover decisions and scheduling of users in uplink or downlink. FIG. FIG. 1D shows that the eNode Bs 160 a and 160 b may communicate with each other over an X2 interface.

“The core network (107) shown in FIG. “1D could include a mobility management gateway (162), a serving gateway (164) and a packet network (PDN (166) gateway 166. Each of the elements shown above is part of the core networks 107. However, it should be noted that any of these elements could be owned or operated by another entity than the core network operator.

The MME 162 could be connected to each eNode B 160 a, 160 b or 160 c in RAN 104 via an interface S1 and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102 a, 102 b, 102 c, and the like. The MME 162 could also serve as a control plane function to switch between the RAN 104 or other RANs (not illustrated) that use other radio technologies such as GSM and WCDMA.

The S1 interface may connect the serving gateway 164 to the eNode Bs 160 a and 160 b in the RAN 104. The serving gateway 164 can route and forward user information packets to/from WTRUs 102 a and 102 b. 102 c via the S1 interface.

“The serving gateway 164 may be connected to PDN gateway 166. This may allow the WTRUs 102 a, 101 b, and 102c to have access to packet-switched network, such as the Internet 110. This will facilitate communication between WTRUs 102, 102, and 102.

“The core network (107) may allow for communications with other networks. The core network 107 could provide WTRUs 102, 102, and 102 with access to circuit switched networks such as the PSTN108 to facilitate communication between WTRUs 101, 102, and 102. The core network 107 might communicate with an IP gateway (e.g. an IP multimedia server or subsystem (IMS-server)) that acts as an interface between core network 107, PSTN 108, and other networks. The core network 107 can also provide access to WTRUs 101 a,102 b, and 102c. These networks may include wired or wireless networks owned and/or operated other service providers.

“FIG. “FIG. The RAN 105 could be an access network (ASN), which uses IEEE 802.16 radio technology for communication with the WTRUs 102 a-102 b and 102 c via the air interface 117. The communication links between different functional entities of WTRUs (102 a-102 b,102 c), 102.c, and RAN 105 may be considered as reference points.

“As shown at FIG. “As shown in FIG. Base stations 180 a to 180 b and 180 c can be associated with a cell in the RAN 105. They may also include one or more transceivers that allow them to communicate with the WTRUs 102 a through the air interface 117. MIMO technology may be implemented by the base stations 180a, 180b, and 180c in one embodiment. The base station 180a may, for instance, use multiple antennas to transmit and receive wireless signals from the WTRU102a. Base stations 180 a-180 b and 180 c can also perform mobility management functions such as handoff trigger, tunnel establishment, radio resource management traffic classification, policy enforcement, QoS, and quality of service (QoS). The ASN gateway 182 can be used as a traffic aggregation station and may also serve to cache subscriber profiles and route to the core network.

“The air interface 117 of the WTRUs 102 a and 102 b may be considered an R1 reference point which implements IEEE 802.16. Each of the WTRUs 101 a, 102b, and 102c may also establish a logical connection (not shown), with the core network. The WTRUs 101 a, 102b, 102c, and core network 109 could establish a logical interface that may be used to authenticate, authorize, manage IP host configurations, and/or mobility management.

“The communication link that connects each base station 180 a, 180b, and 180c can be considered an R8 reference point. It includes protocols to facilitate WTRU handovers as well as data transfer between bases stations. An R6 reference point may be the communication link between base stations 180a, 180b, 180c, and the ASN gateway 182. Protocols for mobility management may be included in the R6 reference point. These protocols can be based on mobility events that are associated with each WTRU 102a, 102b, and 102c.

“As shown at FIG. 1E shows that the RAN 105 can be connected to the core networking 109. An R3 reference point may be defined as the communication link between RAN 105, core network 109. This includes protocols that facilitate data transfer and mobility management capabilities. Core network 109 could include a mobile IP-HA (MIP-HA), 186 and 188. Although each of the elements above are shown as part of core network 109 it is possible that one or more of these elements could be owned or operated by another entity.

The MIP-HA could be responsible for IP address management and may allow the WTRUs 102 a to roam between different ASNs or core networks. MIP-HA 184 could provide access to packet-switched networks such as Internet 110 to enable communications between WTRUs 102 a and 102 b. AAA server 186 could be responsible for user authentication as well as supporting user services. Interworking with other networks may be possible through the gateway 188. The gateway 188 could provide WTRUs 101 a,102 b and 102c with access to circuit switched networks such as the PSTN108 to facilitate communications between WTRUs 101 a,102 b,102c and traditional land-line communication devices. The gateway 188 could also provide access to WTRUs 101 a, 102b, and 102c. These networks may include wired or wireless networks owned or operated by third-party service providers.

“Although it is not shown in FIG. “Although not shown in FIG. 1E, it is obvious that the RAN 105 could be connected with other ASNs and that the core network 109 might be connected to another core networks. The communication link between RAN 105 and other ASNs could be considered an R4 reference point. This may include protocols to coordinate the mobility of WTRUs 102 a-102 b and 102 c between RAN 105. The communication link between core network 109, the other core networks could be considered an R5 reference. This may include protocols to facilitate interworking between core networks at home and core networks visited.

Support for D2D communications is possible for 3GPP or LTE-based radio access. This will allow for high-capability and cost-efficient public safety communications using LTE technology. This could be due to the need to harmonize radio access technology across jurisdictions to lower the CAPEX/OPEX radio-access technology available to the public safety (PS) types of applications. LTE, a scalable wideband radio solution that can allow for efficient multiplexing different types of services like voice or video, may motivate this.

PS applications might require radio communications, which may include radio communications in areas that are not covered by an LTE network. In tunnels, deep basements, or after catastrophic system outages, it may be possible to support D2D communications for PS without an operating network and/or before the arrival of AdHoc-deployed radio infrastructure. PS communications can use (e.g., often require) greater reliability than commercial services even when they are connected to an operating network.

Applications that are “PS type”, e.g. Direct push-to-talk speech services may be used by first responders to provide communication between them. PS types of applications can include services like video push or downloading, for example, in order to make the most of LTE broadband radio’s capabilities.

“D2D communications might be available for PS type applications and/or commercial uses cases, for instance, when deployed. Utility companies, for example, might also need support for 2-way radio communications beyond the network infrastructure. D2D services such as discovery are suitable signaling mechanisms for commercial use cases that allow for proximity-based services and/or traffic onload using LTE-based radio access.

“Access control could be disclosed herein. This document may contain priority handling information.

“In LTE networks, access control and/or priority-handling mechanisms may be used to regulate the access to and/or use of wireless resources by terminals.”

“For example, system data broadcast (SIB), messages transmitted on broadcast channel (BCH), may contain information about which access service class terminals are permitted to connect to the cell. Emergency only, maintenance only and/or any other type. If a terminal device has been connected to an LTE phone, access control might be possible. Access Stratum and/or Non Access Stratum connections may be terminated if more terminals are connected to a cell than can reliably be supported. The terminal devices could be redirected to channels or bands of another radio access technology, such as GSM and 3G HSPA within the operator’s network.

Access control in LTE networks can exist in many forms. LTE networks can have a common feature: terminal devices might be denied or limited access to wireless resources. This could happen prior to connection attempts and/or while connected to cell(s).

LTE systems can offer priority handling for concurrently running wireless services. Priority handling can be used to guarantee higher Quality of Service (QoS). Data streams such as video, voice and conversation may be served first with guaranteed bit rates or guaranteed latency. Priority handling can be used for control signaling (e.g. useful/essential signaling) such as serving (e.g. first serve).

“In LTE systems, priority handling data with multiple users may be possible through the base station (e.g. first) scheduling high-priority data within the Downlink (DL). The base station may artificially reduce or throttle service data rates to allow for data downloads of lower priority. This could make prioritization possible with multiple users. E911 call support systems may use priority handling to ensure successful call setup percentages and/or the occurrence of dropped calls (e.g. much) that are lower than what is usually guaranteed for regular voice calls. Rules may allow a single terminal device to transmit multiple types of data simultaneously. For example, lower priority data might be completed (e.g. later) once packets with higher logical channel priority have been transmitted.

LTE systems may implement priority handling in different ways depending on whether it is implemented from a single user’s perspective or from a system perspective. They may share the commonality that higher priority data can be transmitted (e.g. first), if it is useful. Lower priority data may also be pre-empted from transmission in cases where concurrent services are being supported simultaneously.

“D2D communications could use LTE-based radio access.”

“D2D communications using LTE-based radio access can be set up to operate in network control mode and/or WTRU autonomous modes. WTRU autonomous mode can be called Mode 2 and network-control mode Mode 1. Mode 1 (Network controlled), may be possible under certain conditions. For example, the D2D terminal must be within radio range of an LTE base station. If it is unable to communicate with LTE base stations, the D2D terminal could fall back into Mode 2 (WTRU independent) operation. It may use channel access parameters stored on the terminal in this instance.

“D2D communications using Mode 1 may be possible through the LTE base station. A select set of UL subframes may be reserved to enable D2D transmissions. LTE base stations may announce a list of UL subframes and associated parameters that allow D2D communications to neighbor cells and/or Mode2 terminals. D2D transmissions may not be possible in all LTE bandwidth (BW). The serving cell may grant radio resources to D2D terminals when they are operating in Mode 1. An UL transmission from the terminal on the cellular UL may precede the D2D grant. This will indicate to the base station how much D2D data is available. D2D terminals may be granted a D2D grant from LTE base stations on the cellular DL. This grant allows them to access certain radio resources, such as radio blocks (RBs), that occur in certain subframes during a specific scheduling period.

“The D2D terminal can transmit a Scheduling Assignment message (SA) in a set of one or more D2D Subframe(s), and/or transmit D2D data within a set of D2D Subframes (e.g. second set) during a scheduling period. Scheduling assignments, such as those from D2D, may include an identifier, MCS, resource indicator, and TA fields. D2D data packets, e.g., may include a MAC header that includes source and destination addresses. Multiple logical channels can be multiplexed or sent together in one transport block (TB), within a D2D subframe.

D2D terminals can select (e.g. autonomously select) frequency/time radio resources for D2D communications using Mode 2. Channel access parameters such as subframes to be used with transmissions of SA control message and/or corresponding D2D information, scheduling periods and monitoring subframes may be pre-configured and/or stored on the D2D Terminal. Mode 2 terminals might have the same or similar transmission behavior to Mode 1 terminals. They may transmit SAs and D2D data during scheduling periods. Mode 1 terminals might have a different or more similar transmission behavior to the UL traffic volume indicator and/or DL grant phase.

“D2D communication in Mode 1 or Mode 2 may be enabled by D2D terminals transmitting auxiliary D2D signals such as D2D sync signals and/or channel messages. This aids receivers in demodulating the transmissions.”

“D2D communications via LTE-based radio access can carry voice channels, data packets, and/or streams. D2D communications can include D2D discovery. D2D discovery, which is not voice channels, may only use small packet transmissions. These transmissions may fit into one, two, or a few (e.g. at most) subframes. These packets could contain application data, indicating the availability of devices or SW applications for participating in D2D data transfers with terminals nearby.

“D2D Discovery may use a different or similar channel access protocol to voice or generic D2D data. D2D Discovery resources can be used to discover D2D services, for example, when there is coverage from an LTE base station. These resources could be separate or combined with those that are used for D2D communications using voice or generic D2D information. D2D terminals may select radio resources to D2D discovery messages (e.g. autonomously) from a set that may be reserved or recurring (e.g. periodically recurring) in UL subframes (e.g. Type 1 discovery) or may be explicitly allocated by the LTE serving cells to the D2D termins (e.g. Type 2 discovery). These resources may look similar to D2D communications mode 1. Transmissions of scheduling assignments may not be allowed when sending D2D discovery messages. D2D terminals that transmit (e.g. only transmitting) D2D Discovery messages can be used to transmit D2D synchronization signals for receivers.

This document may describe access control, priority handling, and/or preemption mechanisms for D2D communications using LTE-based radio access comparable with conventional LTE networks.

“D2D terminals such as those used with public safety applications may (e.g. inherently) be able to operate without an LTE radio network infrastructure. These devices could be capable of operating autonomously with regard to channel access and handling D2D data transmissions. D2D terminal devices, unlike LTE terminal devices that are mostly controlled by the network via control signaling messages exchanges with LTE network, may store some, if not all, parameters that can determine channel access and/or transmission behavior.

“Transmission protocols and/or channel acces protocols for D2D communications using LTE-based radio access might not allow random access to differentiate priorities for individual devices or to allow data transmission under consideration for quality-of-service for D2D data. There may be a mechanism that allows a device or user to block, limit or restrict their access to D2D radio resources.

“Perhaps, when within radio range of LTE cells, among other scenarios for example, certain restrictions onto allowable UL Subframes that could be reserved for D2D terminals nearby may be imposed. Different users may have different priorities and channels access. This could be problematic for certain types of data or priority handling. For example, if the D2D radio resources within the LTE serving cells are not sufficient, channel access to high-priority terminals may not be possible. However, the successful transmission of data with higher priority might be possible in the statistical sense. Without an operating LTE radio network infrastructure it is possible to have less control over the D2D radio resource usage.

“A D2D terminal may not be able to distinguish between different types D2D data, such as for radio resource allocation tradeoffs.”

“D2D communications via LTE-based radio access may permit (e.g. implicit) distinction between different types of D2D communication received. For example, D2D SW applications use D2D service IDs to identify D2D payloads and transmit them. A transmitting D2D terminal and a receiving D2D terminus may not be able distinguish higher priority users or/and higher priority types of D2D data until they have physically demodulated and/or decoded such D2D transmissions. D2D devices may not consider priority of ongoing or planned D2D communications when determining their transmission and/or receipt behavior. D2D terminals that are ready to transmit might not stop accessing channels until they have (e.g. physically) demodulated all or some of the channels. This is in case it is dealing with ongoing critical D2D communication. D2D terminals may not have been configured (e.g. never configured) with the knowledge or one or more D2D identifiers, derived payload encryption and/or key integrity protection keys that could be used by other D2D terminuses in their vicinity. One or more D2D terminals (e.g. most) may not be aware of the type and/or nature of D2D data they are trying to decode and distinguish using the D2D payload contents. In the absence of keys or associated identifiers, it is possible that the payload cannot be decoded. It is possible that no information about the D2D payload carried might be available.

This document describes “Mechanisms to enable D2D communications using LTE radio accessibility technology. They may include priority based channel access, priority-based handling of D2D communication as a function D2D terminal, type of D2D information to ensure service availability, QoS and/or pre-emption in emergency situations.” Access to priority-based transmission and/or access mechanisms can improve the efficiency of wireless transmissions and/or reduce D2D radio resource usage. It may also improve channel and/or service availability for D2D customers, as well as improve on existing LTE networks.

D2D data can refer to D2D-related communication between D2D terminals. D2D data could include data packets, such as voice, or segments thereof. It may also include IP packets, such as those used for file upload or download, streaming, or bi-directional video. It may also include D2D control signals, D2D discovery, service or availability messages, and so forth. These features can be used in conjunction with 3GPP D2D communications. Other features, such as D2D Discovery, may also be included.

Channel access may determine D2D priority. Access may be based on priority. Priority-based access can be made possible by using one or more data pools and/or SAs. Access mechanisms can be based on radio resources sets (e.g. segregated radio resource set).

“Priority-based access to D2D communications may be used in frequency-domain and/or time-domain segregated radio resource set.”

“Segregated radio resources sets in time and/or frequency for prioritized D2D access might be realized on radio ressources that may be used to Scheduling Assignments(SA), D2D Data, control or signaling such D2D discovery, one of these D2D signals/channels and/or more than one of them.”

“FIG. 2. is an example of priority-based access through TDM within the SA and D2D subframes. Priority based access for D2D communications may be realized through Time-Division-Multiplex (TDM) of the SA and/or the D2D data pools.”

FIG. 2 shows N=2 different SA pool and M=2 corresponding data pools. These 2 distinct SA pools are defined using different subframe subsets within the time domain. FIG. FIG. 2. There are L1=1 SA subframes for each SA pool during a scheduling period of P=160ms. Two D2D data pool may be divided over subframes. FIG. FIG. 2. There are L2=18 subframes available per D2D datapool per scheduling period.

An SA pool (e.g. the first SA pool shown in FIG. 2) may have SAs to accompany D2D transmissions (e.g. high priority D2D transmissions) within the D2D pool (e.g. first D2D pool) for the duration of a scheduling window. High priority transmissions could correspond to a responder chat group (e.g. first responder conversation group) or a high-priority vocal channel. An SA pool, such as FIG. 2’s second SA pool, may contain SAs for lower priority D2D transmissions. 2) can carry SAs for lower priority D2D transmissions within a D2D pool (e.g. the second SA pool in FIG. A background file download, and/or non-time critical D2D service data exchange may constitute a lower priority transmission.

“High-priority D2D Data Transmissions” may be made (e.g. only) using radio resources provided by the SA (e.g. first SA in FIG. 2), and/or the D2D pool (e.g. first D2D pool in FIG. 2). D2D data transmissions of lower priority may occur (e.g. only occur) depending on the radio resources that were used to transmit the SA (e.g. second SA) or D2D pool (e.g. second D2D pool). A subframe of the high priority (e.g. first) SA pool might not announce D2D information on radio resources for low priority (e.g. second) D2D pool. An SA carrying in a subframe from the low-priority (e.g. second) SA pool might not be able to announce D2D information on radio resources for high priority (e.g. first) D2D pool.

TDM in lower priority D2D transmitting might not be possible on higher priority SA/data pool, which could improve priority handling of D2D transmissions. The network-controlled radio resource allocation of the SA/D2D data on high priority pools may not allow for low priority D2D channels and devices to compete for TDM radio resources. WTRU autonomous contention resolution of such SA/data resources might not allow the channels and D2D devices with low priority to compete for the TDM radio resources. The segregated TDM radio resources might not be available to the lowest priority D2D channels and devices for random radio resource selection of SA/data. Higher priority D2D information may have a greater chance of being transmitted successfully, either during the initial determination of radio resources or during ongoing transmissions due to less interference from lower priority D2D. Resource segregation may prevent legacy D2D terminals from being able to access the new SA/data data pools of higher priority.

“FIG. 3. An example diagram showing priority-based access to D2D communications via TDM of SA within shared D2D subframes. Priority based access for D2D communications may be realized through Time-Division-Multiplex (TDM) of the SA pools, such as while using shared D2D data pool(s).”

“In FIG. FIG. 3 shows N=2 different SA pool and M=1 D2D data pools. These two distinct SA pools can be separated by subframes that are different or different in time-domain. FIG. FIG. 3. There are L1=1 SA subframes per SA pool for a scheduling period of P=160ms. There are L2=38 subframes available in the D2D data pool per scheduling period.

“The SA pool (e.g. first SA pool in FIG. 3.) may have SAs to accompany high priority D2D data transmissions. The SA pool (e.g. second SA pool in FIG. 3.) may have SAs to accompany lower priority D2D transmissions.

High-priority D2D data transmissions can be transmitted (e.g. only by) using radio resources of the high-priority SA pools (e.g. first SA pool). D2D data transmissions with lower priority may be transmitted using radio resources from the lower-priority SA pools (e.g. second). SAs transmitted from the D2D pool’s shared radio resources may be sent either from the high-priority SA pools (e.g. the first SA pool) or the lower-priority SA pools (e.g. the second).

“Priority handling of D2D transmissions could be improved. Priority handling for D2D transmissions could be improved if lower priority D2D transmits do not occur in the higher priority SA pool(s). The network-controlled radio resource allocation of the SA for the high priority pool(s) might be made by the network. Channels and devices with low priority D2D may not be able to compete for these segregated TDM radio radio resources. WTRU autonomous contention resolution may not allow the channels and D2D devices with low priority to compete for these segregated TDM radio resource. The random radio resource selection that determines the SA by D2D terminals might require the use of low priority D2D channels and devices. High priority D2D data might have a greater chance of being transmitted. This could be due to the avoidance of interference or contention on the SA radio resources. Priority-based access mechanisms can be used while maintaining the principle and/or resources utilization (e.g. inherent resource utilization) efficiency shared D2D data pool.

“FIG. “FIG. Priority based access for D2D communications may be realized through Frequency-Division-Multiplex (FDM) of the SA and/or the D2D data pools.”

FIG. 4 there is N=1 SA pool and M=1 D2D data pools in time domain. FIG. FIG. 4. There may be L1=2 subframes of the SA per SA pool for a scheduling period of P=160ms. FIG. FIG. 4 shows that there are L2=38 subframes available in the D2D database pool for each scheduling period. Radio resources in the SA pool have L2=2 distinct radio block subsets that are frequency-domain. Subframes containing SAs can contain SAs that allow high priority D2D Data transmission in RBs 10-30, and SAs that allow for low priority D2D Data transmission in RBs 40-60. D2D data subframes may contain high-priority or low priority transmissions (e.g. only in RBs 10-30, and RBs40-60, respectively). These subframes may be called frequency-domain SA or D2D data pool.

“The frequency domain SA pool (e.g. first frequency-domain SA Pool in FIG. The frequency-domain SA pool (e.g. first frequency domain SA pool in FIG. 4) may contain SAs to accompany high priority D2D transmissions in frequency=domain D2D pool (e.g. first frequency-domain D2D pool in FIG. 4, for example, during a time period. The frequency-domain SA Pool (e.g. second frequency-domain SA Pool in FIG. 4.) may contain SAs to accompany lower priority D2D transmissions within the frequency-domain D2D pool (e.g. second frequency-domain D2D pool in FIG. 4).”

“High-priority D2D Data Transmissions May (e.g. may only) Be Conducted on Radio Resources in Frequency Domain, Such as the frequency domain used for the SA (e.g. first SA) or the corresponding D2D pool (e.g. First D2D data pool. D2D data transmissions with lower priority may occur (e.g. may only) on radio resources used by the SA (e.g. second SA) or the data pool (e.g. second data pool) within frequency-domain. An SA that is carried in the subframe of the high priority SA frequency domain (e.g. first SA frequency domain) may not announce D2D information on radio resources used with low priority D2D (e.g. second D2D) frequency-domain. A SA carrying in the low priority frequency-domain SA region may not announce D2D information on radio resources within the high priority D2D frequency-domain (e.g. first D2D domain frequency-domain).

“Priority handling of D2D transmissions could be improved, for instance, when lower priority D2D transmits don’t occur on higher priority SA/data frequency domain pools. The segregated FDM radio resources might not be available to low priority D2D devices or channels. A higher priority D2D device or channel may have a greater chance (e.g., a significantly higher chance) to be transmitted during determination radio resources and/or ongoing transmissions, such as a transmission due lower interference from D2D data of lower priority.

“FIG. “FIG.5″ shows an example diagram showing priority-based access to D2D communications via FDM of SA within shared D2D subframes. Priority based access for D2D communications may be realized through Frequency-Division-Multiplex (FDM) of the SA pools while using shared D2D data pool(s).”

“In FIG. FIG. 5. There is N=1 SA pool and M=1 corresponding data pool in the time-domain. FIG. FIG. 5. There are L1=2 subframes of SAs per scheduling period P=160 ms. FIG. FIG. 5 shows that there are L2=38 subframes available in the D2D database pool for each scheduling period. Radio resources within the SA pool could include L2=2 distinct and/or different radio block subsets, in frequency-domain. SAs in subframes that contain SAs can include SAs for high priority D2D transmissions in RBs 10–30 and SAs in RBs 40-60. These are sometimes referred to in frequency-domain as SA pools. D2D data subframes may contain high-priority or low priority transmissions. For example, where indicated in one or more (e.g. all) RBs.

“The frequency domain SA pool (e.g. first frequency-domain SA Pool in FIG. 5) may be equipped with SAs to accompany high priority D2D transmissions such as those in the D2D pool for the duration of a scheduled period. The frequency-domain SA Pool (e.g. the second frequency-domain SA Pool in FIG. 5) could carry SAs to accompany lower priority D2D transmissions (e.g., in the D2D pool).

High-priority D2D data transmissions can (e.g. may only) be transmitted using radio resources from high-priority SA pools (e.g. first SA pool) within frequency-domain. D2D data transmissions with lower priority may be transmitted using radio resources in frequency-domain that are used for the lower-priority SA pools (e.g. second SA pool). SAs from the first SA pool, which is the highest priority, and/or the second SA pool, which are lower priorities, may be transmitted using radio resources used for the D2D pool’s shared radio resources.

Summary for “Device to device (D2D), pre-emption, and access control”

For public safety communications, “Device to device (D2D), communications can be used for a variety of purposes. D2D communications can be linked to standard technologies such as LTE and IEEE. Access control and/or priority handling can be used in LTE systems to allow terminals to access and/or use wireless resources.

“Systems, methods and instrumentalities are disclosed for determining access control, channel and signaling priority. A wireless transmit/receive device (WTRU), may include a processor that determines the device-to-device data (D2D), to be transmitted. The WTRU can determine whether D2D data can be transmitted. The WTRU might determine the availability of scheduling assignment (SA), resources for priority-based D2D data signal signals. The WTRU can select from a number of available SA resources to transmit priority-based D2D data signals. The WTRU can transmit D2D data. D2D data may only be transmitted to the selected SA resources.

“The WTRU could be configured to select available SA resources from a preconfigured list of SA resources. The WTRU can be configured to either receive configuration signaling or determine the available SA resource from that signaling.

“Embodiments may contemplate priority reception or transmission for D2D relays (e.g., guaranteed resources). Embodiments envisage signaling for the use of (e.g. guaranteed) segregated resource.

A wireless transmit/receive device (WTRU), may include a receiver. The receiver can be set up to receive one or more radio resources in order to perform one or more scheduling assignments (SA). A processor may be part of the WTRU. The processor can be used to determine the first frequency domain SA (FDSA) pool. One or more SA may be allocated to at least one priority device-to?device (D2D), transmission in the first FD SA pool. A second FD SA pool may be determined by the processor. One or more SA may be allocated to at least one second priority D2D transmission in the second FD SA pool. A transmitter may be part of the WTRU. The transmitter could be set up to send at least one priority D2D transmission by using at least one radio resource to the one or more SAs from the first FD SA pools. The transmitter could be set up to send at least one second priority D2D transmitting using at least one radio resource for one or more SAs from the second FD SA Pool.

“A wireless transmit/receive device (WTRU), may be capable to communicate between devices (D2D). A receiver may be part of the WTRU. The receiver could be set up to receive at most one of the following: a D2D channel, or a D2D signal. A processor may be part of the WTRU. The processor can be programmed to determine whether at least one: a second D2D channel, or a first D2D signals is to be transmitted while at least one: the first D2D channel is being received. A processor could be programmed to determine the relative priority of the at most one of the following: The first D2D channel, the first D2D signals and the least one between: The second D2D channels or D2D signals. If the processor determines that the at minimum one of the: A second D2D Channel or D2D Signal is to be transmitted while at least the one of the first D2D channels or first D2D signals is being received, the processor may also be programmed to determine the number of D2D subframes to be used for D2D2D channels or D2Dchannel or the D2Dchannel or first D2Dchannel or the D2Dd channel or first D2Dchannel or the D2D subframes to be used to determine the higher relative priority The processor can be programmed to determine the number of D2D subframes that are to be used to receive which D2D channel, first D2D signal or second D2D signals.

“A wireless transmit/receive device (WTRU), may be capable to communicate between devices (D2D). A processor may be part of the WTRU. A processor could be programmed to send a pre-emption signal. The processor could be programmed to send the pre-emption indicator via a scheduling assignment. A transmitter may be part of the WTRU. The transmitter could be programmed to transmit the SA to another WTRU that is capable of D2D communication.

A wireless transmit/receive device (WTRU), may include a receiver. The receiver can be set up to receive one or more radio resources in order to perform one or more scheduling assignments (SA). A processor may be part of the WTRU. A processor could be used to create a first SA pool. One or more SA may be allocated to at least one D2D (first priority device-to?device) transmission. A second SA pool may be determined by the processor. One or more SA may be allocated to at least one of the second priority D2D transmissions. The processor can be programmed to compare the number of first priority scheduling events associated with one or several resources for the one or two SAs of the first SA pool to determine a threshold. A transmitter may be part of the WTRU. The transmitter can be set up to transmit at least one priority D2D transmission by using at least one radio resource. This radio resource will allow for one or more SAs from the first SA pool if the threshold is met.

“This section will provide a detailed description of the various Figures, as well as a reference to the various figures. This description gives an example of possible implementations. However, the details do not limit the scope or intent of the application. The articles?a? and?an? are used herein. Without further qualification or characterization, the articles?a? and?an? may be taken to refer to?one or more? For example,?at least one?.

“FIG. “FIG. Multiple access systems can be used to provide content to multiple wireless users. This includes voice, data and video as well as broadcasting, messaging, broadcast, and other services. Multiple wireless users may be able to access the same content via the communications system 100. This is possible through sharing system resources, including wireless broadband. One or more channel access methods may be used by communications systems 100, including code division multiple acces (CDMA), time division multiple access, TDMA, frequency division multiple accessibility (FDMA), orthogonal FDMA, OFDMA, single-carrier FDMA, SC-FDMA, and others.

“As shown at FIG. “As shown in FIG. Any type of device that can operate in a wireless environment, including the WTRUs 101 a, 102, 102, 102, and 102c, may be included in the WTRUs. The WTRUs 101 a,102 b and 102c may be used to transmit or receive wireless signals. They may also include user equipment (WTRU), mobile stations, fixed or mobile subscribers units, pagers, personal digital assistants (PDA), smartphones, laptops, netbooks, personal computers, wireless sensors, consumer electronics and other similar devices.

“Communications systems 100 may also contain a base stations 114a and 114b. Each of the base station 114a,114b can be any device that is capable of wirelessly interfacing with at least one WTRU 102a,102b,102c,102c,102d. This allows access to one or more networks such as the Internet 110, core network 106/107/109 and/or networks 112. The base stations 114a,114b could be any type of device that can wirelessly interface with at least one of the WTRUs 102 a,102 b, 102 c, 102 d to facilitate access to one or more communication networks such as the core network 106/107/109, the Internet 110, and/or the networks 112. Although the base stations of 114 and 114 are shown as one element, it is possible to see that the base stations of 114 and 114 may contain multiple interconnected bases stations or network elements.

“The base station (114a) may be part the RAN 103/104/105. This may include other base stations or network elements (not illustrated), such as a controller (BSC), radio network controller (RNC), relay nosdes, and so on. The base station (114 a) and/or base station (114 b) may be configured to transmit/or receive wireless signals within an area, which can be called a cell (not illustrated). Further, the cell can be broken down into cell sectors. The cell that is associated with base station 114a could be broken down into three sections. In one embodiment, the base stations 114a could include three transceivers. One for each sector. Another embodiment of the base station 114a may use multiple-input multiple out (MIMO) technology. Therefore, multiple transceivers may be used for each sector.

“The base stations (114 a,114 b) may communicate with one of the WTRUs (102 a), 102 (b), 102 (c), 102 (d), 102 (d) over an air interface (115/116/117), which could be any wireless communication link (e.g. radio frequency (RF), microwave (IR), ultraviolet(UV), visible light (UV), etc.). Any suitable radio access technology (RAT) may be used to establish the air interface 115/116/117.

“Moreover, the communications system 100 could be a multi-access system, which may use one or more channel access systems, such as CDMA and TDMA. The base station 114 a within the RAN 103/104/105, and the WTRUs 102 a, 102 b, 102 c, may implement a radio technology like Universal Mobile Telecommunications System, 102 a, 102 b or 102 c. This may establish the air interface 115/116/117 via wideband CDMA (WCDMA). WCDMA can include communication protocols like High-Speed Packet Access and/or Evolved HSPA. HSPA could include High Speed Downlink Packet Access, (HSDPA), and/or High Speed Uplink Packet Access, (HSUPA).

“Another embodiment may include the base station 114 a as well as the WTRUs 102 a-102 b and 102 c. This radio technology, Evolved UMTS Terrestrial Radio Access, (E-UTRA), may be used to establish the air interface 115/116/117 using LTE-Advanced and/or Long Term Evolution (LTE).

“The base station (114 b) in FIG. “The base station 114 b in FIG. One embodiment of the WTRUs (102 c,102 d) and base station 114 may use a radio technology like IEEE 802.11 to establish wireless local area networks (WLAN). Another embodiment is that the WTRUs 101 c,102 d and the base station 112 b may use a radio technology like IEEE 802.15 in order to establish a wireless personal network (WPAN). Another embodiment is that the WTRUs 101 c, 102 and 114 b may use a cell-based RAT (e.g. WCDMA, CDMA2000 GSM LTE-A, LTE-A). To establish a picocell and femtocell. FIG. FIG. 1A shows that the base station (114 b) may have an internet connection to the Internet 110. The base station 114b may not need to be connected to the Internet 110 via core network 106/107/109.

“The RAN 103/104/105 could be in communication to the core network106/107/109. This network may be any type that can provide voice, data and applications to one or more WTRUs (102 a,102 b and 102c), and/or high-level security functions such as user authentication. FIG. It is not shown in FIG. 1A. However, it is possible that the RAN 103/105/105 and/or core network 106/107/109 are in direct or indirect communications with other RANs using the same RAT or a different RAT. The core network 106/107/109 could be connected to the RAN 103/104/105 which may use an E-UTRA radio tech.

“The core network 106/107/109 could also be used as a gateway to the WTRUs 102 a and 102 b. The WTRUs 102 c, 102 d, 102 c, 102 d can access the PSTN 108, Internet 110 and/or other networks 112. The PSTN 108 could include circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 could include a global network of interconnected computer networks as well as devices that use common communication protocols such the transmission control protocol, user datagram protocol and internet protocol (IP) from the TCP/IP protocol suite. Other service providers may also own or operate wired and wireless communications networks. The networks 112 could include a core network that is connected to one or more of the RANs 103/104/105, or a different type of RAT.

“Some or all the WTRUs 101 a-102 b and 102c-102c,102c,102d in the communications network 100 may have multimode capabilities. For example, the WTRUs 102/102/102 b,102c,102c,102d in the communications systems 100 may contain multiple transceivers that allow communication with wireless networks using different wireless links. FIG. 2 shows the WTRU102 c. 1A could be set up to communicate with base station (114a), which may use a cellular radio technology, or with base station (114b), which may use an IEEE 802 radio tech.

“FIG. 1B is a system schematic of WTRU 102. FIG. FIG. 1B shows that the WTRU 102 could include a processor 118 and a transceiver 120. A transmit/receive device 122 may also be included. While the WTRU102 may contain any combination of the above elements, it will still be consistent with an embodiment. Embodiments may also contemplate that base stations (114 a) and (or the nodes base stations (114 b) may represent, such that but not limited to a transceiver station, (BTS), an access point, (AP), a Node B, a Node B, a Node B, an evolved node B (eNodeB), an home evolved node B (HeNB), and proxy nodes. 1B, and are described herein.

The processor 118 can be a general-purpose processor or a special-purpose processor. It may also include a conventional processor, a processor with digital signal processing (DSP), a plurality microprocessors and one or more DSP cores. A controller, a microcontroller as well as Application Specific Integrated Circuits. FPGAs circuits. Any other type of integrated circuit (IC), a state computer, and the like. The processor 118 can perform signal coding and data processing as well as power control, input/output, and/or other functionality that allows the WTRU102 to function in a wireless environment. The processor 118 can be connected to the transceiver 120. It may also be attached to the transmit/receive 122. FIG. FIG.

“The transmit/receive 122 can be used to transmit or receive signals from a base station (e.g. the base station 114a) via the air interfaces 115/116/117. One example is that the transmit/receive 122 could be an antenna capable of transmitting and/or receiving RF signals. Another embodiment of the transmit/receive 122 could be an emitter/detector that can transmit and/or receive IR, UV or visible light signals. Another embodiment of the transmit/receive 122 could be configured to transmit and/or receive light signals as well as RF. The transmit/receive device 122 can be configured to transmit and/or obtain any combination of wireless signals.

FIG. 1B is a single element. However, the WTRU 102 can include multiple transmit/receive components 122. MIMO technology may be used in the WTRU 102. In one embodiment, the WTRU 102 could include multiple transmit/receive elements 122 (e.g. multiple antennas) that transmit and receive wireless signals over the air interface 115/116/117.

“The transceiver 120 can be set up to modulate signals to be transmitted by transmit/receive elements 122 and demodulate signals to be received by transmit/receive elements 122. The WTRU 102 may be capable of multi-mode communication, as noted above. The transceiver 120 could include multiple transceivers to enable the WTRU 102 communicate via multiple RATs such as UTRA or IEEE 802.11, for instance.

“The processor 118 may be coupled to the WTRU102 speaker/microphone, keypad 126 and/or display/touchpad 128 and may receive user input data (e.g., liquid crystal display (LCD), organic light-emitting dime (OLED), display unit). The processor 118 can also output user data from the speaker/microphone, keypad 126 and/or display/touchpad 128, respectively. The processor 118 can access and store information in any type of memory. This includes the removable memory 132 and the non-removable storage 130. Non-removable memory 130 can include random-access memory, read-only memory and hard drives. A subscriber identity card (SIM), a memory stick or a secure digital card (SD) may be included in the removable memory 132. Other embodiments of the WTRU102 may allow the processor 118 to access and store information on memory other than that on the WTRU102. This could include data on a server or home computer (not illustrated).

“The power source 134 may supply power to processor 118. It may also be used to control and distribute power to other components of the WTRU 101. Any suitable device may be used to power the WTRU102. One example of a power source 134 is a set of dry cells (e.g. nickel-cadmium, nickel-zinc, nickel metal hydride, NiMH, lithium-ion, etc. “, solar cells, fuel cell, and other similar items.”

The processor 118 can also be connected to the GPS chipset 136. This chip may be used to provide location information, such as longitude and latitude, regarding the WTRU 102’s current location. The WTRU102 can receive information via the GPS chipset, 116, and 117. This information may be in addition to or instead of the GPS chipset. 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.”

“FIG. “FIG. The RAN 103 could use a UTRA radio to communicate with WTRUs 102 a and 102 b over the air interface 115. The RAN 103 could also be communicating with the core network 106. FIG. 1C: The RAN 103 could include Node-Bs 140 a. 140 b. 140 c. These may each contain one or more transceivers to communicate with the WTRUs 102 a. 102 b. 102 c via the air interface 115. Each of the Node-Bs 140 a to 140 b and 140 c can be associated with a specific cell within the RAN 103. RNCs 142 a and 142 b may be included in the RAN 103. While the RAN 103 could include as many Node-Bs or RNCs as you like, it will still be consistent with an embodiment.

“As shown at FIG. “As shown in FIG. 140 a-140 b, 140c and 140c can communicate with respective RNCs 140a, 140b, 140c via an Iub interface. An Iur interface may allow RNCs 142a, 142b to communicate with each other. Each of the RNCs 142 a, 142 b can be set up to control the Node-Bs 140, 140, and 140 c to whom it is connected. Each of the RNCs 142-142 a, 142-142 b can be configured to support or carry out other functions such as load control, outer loop power control and admission control.

“The core network (106) shown in FIG. 1C could include a media gateway 144, a mobile switch center (MSC), 146, a serving GPRS service node SGSN 148, and/or a gateway GPRS help node GGSN 150. Each of the elements shown above is part of the core network (106), but it should be noted that each element may be owned or operated by another entity.

“The RNC 142 a may be connected to MSC 146 in core network 106 via an IuCS Interface. MSC 146 could be connected to MGW 144. MSC 146 or MGW 144 could provide WTRUs 102 a to 102 b to 102 c access to circuit-switched network, such as the PSTN 108 to facilitate communications between WTRUs 102 a to 102 b and 102 c.

“The RNC 142 a may be connected to the SGSN 148 within the core network 106 via IuPS. The GGSN 150 may be connected to SGSN 148. The GGSN 150 and the SGSN 148 may connect to the WTRUs 102 a and 102 b and 102 c. They can also access packet-switched networks such as the Internet 110 to facilitate communications between the WTRUs 102 a and 102 b and 102 c.

“As mentioned above, the core network106 could also be connected with the networks 112, which might include other wired and wireless networks owned or operated by other service providers.

“FIG. “FIG. The RAN 104 could use an E-UTRA radio technique to communicate with WTRUs 102 a and 102 b over the air interface 116. The RAN 104 could also be communicating with the core network 107.

“The RAN 104 could include eNode Bs 160 a. 160 b. 160 c. However, it is possible that the RAN 104 can include as many eNode Bs as you like while still being consistent with an embodiment. Each of the eNodeBs 160, 160, and 160 c can include one or more transceivers to communicate with the WTRUs 101 a, 102, 102, and 102 over the air interface. 116 One embodiment may use MIMO technology in the eNode -Bs 160, 160, b, 160, c. The eNode -B 160a may, for instance, use multiple antennas to transmit and receive wireless signals to the WTRU102a.

“Each of eNode -Bs 160a, 160b, 160c may be associated to a particular cell (not illustrated) and configured to handle radio resource management, handover decisions and scheduling of users in uplink or downlink. FIG. FIG. 1D shows that the eNode Bs 160 a and 160 b may communicate with each other over an X2 interface.

“The core network (107) shown in FIG. “1D could include a mobility management gateway (162), a serving gateway (164) and a packet network (PDN (166) gateway 166. Each of the elements shown above is part of the core networks 107. However, it should be noted that any of these elements could be owned or operated by another entity than the core network operator.

The MME 162 could be connected to each eNode B 160 a, 160 b or 160 c in RAN 104 via an interface S1 and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102 a, 102 b, 102 c, and the like. The MME 162 could also serve as a control plane function to switch between the RAN 104 or other RANs (not illustrated) that use other radio technologies such as GSM and WCDMA.

The S1 interface may connect the serving gateway 164 to the eNode Bs 160 a and 160 b in the RAN 104. The serving gateway 164 can route and forward user information packets to/from WTRUs 102 a and 102 b. 102 c via the S1 interface.

“The serving gateway 164 may be connected to PDN gateway 166. This may allow the WTRUs 102 a, 101 b, and 102c to have access to packet-switched network, such as the Internet 110. This will facilitate communication between WTRUs 102, 102, and 102.

“The core network (107) may allow for communications with other networks. The core network 107 could provide WTRUs 102, 102, and 102 with access to circuit switched networks such as the PSTN108 to facilitate communication between WTRUs 101, 102, and 102. The core network 107 might communicate with an IP gateway (e.g. an IP multimedia server or subsystem (IMS-server)) that acts as an interface between core network 107, PSTN 108, and other networks. The core network 107 can also provide access to WTRUs 101 a,102 b, and 102c. These networks may include wired or wireless networks owned and/or operated other service providers.

“FIG. “FIG. The RAN 105 could be an access network (ASN), which uses IEEE 802.16 radio technology for communication with the WTRUs 102 a-102 b and 102 c via the air interface 117. The communication links between different functional entities of WTRUs (102 a-102 b,102 c), 102.c, and RAN 105 may be considered as reference points.

“As shown at FIG. “As shown in FIG. Base stations 180 a to 180 b and 180 c can be associated with a cell in the RAN 105. They may also include one or more transceivers that allow them to communicate with the WTRUs 102 a through the air interface 117. MIMO technology may be implemented by the base stations 180a, 180b, and 180c in one embodiment. The base station 180a may, for instance, use multiple antennas to transmit and receive wireless signals from the WTRU102a. Base stations 180 a-180 b and 180 c can also perform mobility management functions such as handoff trigger, tunnel establishment, radio resource management traffic classification, policy enforcement, QoS, and quality of service (QoS). The ASN gateway 182 can be used as a traffic aggregation station and may also serve to cache subscriber profiles and route to the core network.

“The air interface 117 of the WTRUs 102 a and 102 b may be considered an R1 reference point which implements IEEE 802.16. Each of the WTRUs 101 a, 102b, and 102c may also establish a logical connection (not shown), with the core network. The WTRUs 101 a, 102b, 102c, and core network 109 could establish a logical interface that may be used to authenticate, authorize, manage IP host configurations, and/or mobility management.

“The communication link that connects each base station 180 a, 180b, and 180c can be considered an R8 reference point. It includes protocols to facilitate WTRU handovers as well as data transfer between bases stations. An R6 reference point may be the communication link between base stations 180a, 180b, 180c, and the ASN gateway 182. Protocols for mobility management may be included in the R6 reference point. These protocols can be based on mobility events that are associated with each WTRU 102a, 102b, and 102c.

“As shown at FIG. 1E shows that the RAN 105 can be connected to the core networking 109. An R3 reference point may be defined as the communication link between RAN 105, core network 109. This includes protocols that facilitate data transfer and mobility management capabilities. Core network 109 could include a mobile IP-HA (MIP-HA), 186 and 188. Although each of the elements above are shown as part of core network 109 it is possible that one or more of these elements could be owned or operated by another entity.

The MIP-HA could be responsible for IP address management and may allow the WTRUs 102 a to roam between different ASNs or core networks. MIP-HA 184 could provide access to packet-switched networks such as Internet 110 to enable communications between WTRUs 102 a and 102 b. AAA server 186 could be responsible for user authentication as well as supporting user services. Interworking with other networks may be possible through the gateway 188. The gateway 188 could provide WTRUs 101 a,102 b and 102c with access to circuit switched networks such as the PSTN108 to facilitate communications between WTRUs 101 a,102 b,102c and traditional land-line communication devices. The gateway 188 could also provide access to WTRUs 101 a, 102b, and 102c. These networks may include wired or wireless networks owned or operated by third-party service providers.

“Although it is not shown in FIG. “Although not shown in FIG. 1E, it is obvious that the RAN 105 could be connected with other ASNs and that the core network 109 might be connected to another core networks. The communication link between RAN 105 and other ASNs could be considered an R4 reference point. This may include protocols to coordinate the mobility of WTRUs 102 a-102 b and 102 c between RAN 105. The communication link between core network 109, the other core networks could be considered an R5 reference. This may include protocols to facilitate interworking between core networks at home and core networks visited.

Support for D2D communications is possible for 3GPP or LTE-based radio access. This will allow for high-capability and cost-efficient public safety communications using LTE technology. This could be due to the need to harmonize radio access technology across jurisdictions to lower the CAPEX/OPEX radio-access technology available to the public safety (PS) types of applications. LTE, a scalable wideband radio solution that can allow for efficient multiplexing different types of services like voice or video, may motivate this.

PS applications might require radio communications, which may include radio communications in areas that are not covered by an LTE network. In tunnels, deep basements, or after catastrophic system outages, it may be possible to support D2D communications for PS without an operating network and/or before the arrival of AdHoc-deployed radio infrastructure. PS communications can use (e.g., often require) greater reliability than commercial services even when they are connected to an operating network.

Applications that are “PS type”, e.g. Direct push-to-talk speech services may be used by first responders to provide communication between them. PS types of applications can include services like video push or downloading, for example, in order to make the most of LTE broadband radio’s capabilities.

“D2D communications might be available for PS type applications and/or commercial uses cases, for instance, when deployed. Utility companies, for example, might also need support for 2-way radio communications beyond the network infrastructure. D2D services such as discovery are suitable signaling mechanisms for commercial use cases that allow for proximity-based services and/or traffic onload using LTE-based radio access.

“Access control could be disclosed herein. This document may contain priority handling information.

“In LTE networks, access control and/or priority-handling mechanisms may be used to regulate the access to and/or use of wireless resources by terminals.”

“For example, system data broadcast (SIB), messages transmitted on broadcast channel (BCH), may contain information about which access service class terminals are permitted to connect to the cell. Emergency only, maintenance only and/or any other type. If a terminal device has been connected to an LTE phone, access control might be possible. Access Stratum and/or Non Access Stratum connections may be terminated if more terminals are connected to a cell than can reliably be supported. The terminal devices could be redirected to channels or bands of another radio access technology, such as GSM and 3G HSPA within the operator’s network.

Access control in LTE networks can exist in many forms. LTE networks can have a common feature: terminal devices might be denied or limited access to wireless resources. This could happen prior to connection attempts and/or while connected to cell(s).

LTE systems can offer priority handling for concurrently running wireless services. Priority handling can be used to guarantee higher Quality of Service (QoS). Data streams such as video, voice and conversation may be served first with guaranteed bit rates or guaranteed latency. Priority handling can be used for control signaling (e.g. useful/essential signaling) such as serving (e.g. first serve).

“In LTE systems, priority handling data with multiple users may be possible through the base station (e.g. first) scheduling high-priority data within the Downlink (DL). The base station may artificially reduce or throttle service data rates to allow for data downloads of lower priority. This could make prioritization possible with multiple users. E911 call support systems may use priority handling to ensure successful call setup percentages and/or the occurrence of dropped calls (e.g. much) that are lower than what is usually guaranteed for regular voice calls. Rules may allow a single terminal device to transmit multiple types of data simultaneously. For example, lower priority data might be completed (e.g. later) once packets with higher logical channel priority have been transmitted.

LTE systems may implement priority handling in different ways depending on whether it is implemented from a single user’s perspective or from a system perspective. They may share the commonality that higher priority data can be transmitted (e.g. first), if it is useful. Lower priority data may also be pre-empted from transmission in cases where concurrent services are being supported simultaneously.

“D2D communications could use LTE-based radio access.”

“D2D communications using LTE-based radio access can be set up to operate in network control mode and/or WTRU autonomous modes. WTRU autonomous mode can be called Mode 2 and network-control mode Mode 1. Mode 1 (Network controlled), may be possible under certain conditions. For example, the D2D terminal must be within radio range of an LTE base station. If it is unable to communicate with LTE base stations, the D2D terminal could fall back into Mode 2 (WTRU independent) operation. It may use channel access parameters stored on the terminal in this instance.

“D2D communications using Mode 1 may be possible through the LTE base station. A select set of UL subframes may be reserved to enable D2D transmissions. LTE base stations may announce a list of UL subframes and associated parameters that allow D2D communications to neighbor cells and/or Mode2 terminals. D2D transmissions may not be possible in all LTE bandwidth (BW). The serving cell may grant radio resources to D2D terminals when they are operating in Mode 1. An UL transmission from the terminal on the cellular UL may precede the D2D grant. This will indicate to the base station how much D2D data is available. D2D terminals may be granted a D2D grant from LTE base stations on the cellular DL. This grant allows them to access certain radio resources, such as radio blocks (RBs), that occur in certain subframes during a specific scheduling period.

“The D2D terminal can transmit a Scheduling Assignment message (SA) in a set of one or more D2D Subframe(s), and/or transmit D2D data within a set of D2D Subframes (e.g. second set) during a scheduling period. Scheduling assignments, such as those from D2D, may include an identifier, MCS, resource indicator, and TA fields. D2D data packets, e.g., may include a MAC header that includes source and destination addresses. Multiple logical channels can be multiplexed or sent together in one transport block (TB), within a D2D subframe.

D2D terminals can select (e.g. autonomously select) frequency/time radio resources for D2D communications using Mode 2. Channel access parameters such as subframes to be used with transmissions of SA control message and/or corresponding D2D information, scheduling periods and monitoring subframes may be pre-configured and/or stored on the D2D Terminal. Mode 2 terminals might have the same or similar transmission behavior to Mode 1 terminals. They may transmit SAs and D2D data during scheduling periods. Mode 1 terminals might have a different or more similar transmission behavior to the UL traffic volume indicator and/or DL grant phase.

“D2D communication in Mode 1 or Mode 2 may be enabled by D2D terminals transmitting auxiliary D2D signals such as D2D sync signals and/or channel messages. This aids receivers in demodulating the transmissions.”

“D2D communications via LTE-based radio access can carry voice channels, data packets, and/or streams. D2D communications can include D2D discovery. D2D discovery, which is not voice channels, may only use small packet transmissions. These transmissions may fit into one, two, or a few (e.g. at most) subframes. These packets could contain application data, indicating the availability of devices or SW applications for participating in D2D data transfers with terminals nearby.

“D2D Discovery may use a different or similar channel access protocol to voice or generic D2D data. D2D Discovery resources can be used to discover D2D services, for example, when there is coverage from an LTE base station. These resources could be separate or combined with those that are used for D2D communications using voice or generic D2D information. D2D terminals may select radio resources to D2D discovery messages (e.g. autonomously) from a set that may be reserved or recurring (e.g. periodically recurring) in UL subframes (e.g. Type 1 discovery) or may be explicitly allocated by the LTE serving cells to the D2D termins (e.g. Type 2 discovery). These resources may look similar to D2D communications mode 1. Transmissions of scheduling assignments may not be allowed when sending D2D discovery messages. D2D terminals that transmit (e.g. only transmitting) D2D Discovery messages can be used to transmit D2D synchronization signals for receivers.

This document may describe access control, priority handling, and/or preemption mechanisms for D2D communications using LTE-based radio access comparable with conventional LTE networks.

“D2D terminals such as those used with public safety applications may (e.g. inherently) be able to operate without an LTE radio network infrastructure. These devices could be capable of operating autonomously with regard to channel access and handling D2D data transmissions. D2D terminal devices, unlike LTE terminal devices that are mostly controlled by the network via control signaling messages exchanges with LTE network, may store some, if not all, parameters that can determine channel access and/or transmission behavior.

“Transmission protocols and/or channel acces protocols for D2D communications using LTE-based radio access might not allow random access to differentiate priorities for individual devices or to allow data transmission under consideration for quality-of-service for D2D data. There may be a mechanism that allows a device or user to block, limit or restrict their access to D2D radio resources.

“Perhaps, when within radio range of LTE cells, among other scenarios for example, certain restrictions onto allowable UL Subframes that could be reserved for D2D terminals nearby may be imposed. Different users may have different priorities and channels access. This could be problematic for certain types of data or priority handling. For example, if the D2D radio resources within the LTE serving cells are not sufficient, channel access to high-priority terminals may not be possible. However, the successful transmission of data with higher priority might be possible in the statistical sense. Without an operating LTE radio network infrastructure it is possible to have less control over the D2D radio resource usage.

“A D2D terminal may not be able to distinguish between different types D2D data, such as for radio resource allocation tradeoffs.”

“D2D communications via LTE-based radio access may permit (e.g. implicit) distinction between different types of D2D communication received. For example, D2D SW applications use D2D service IDs to identify D2D payloads and transmit them. A transmitting D2D terminal and a receiving D2D terminus may not be able distinguish higher priority users or/and higher priority types of D2D data until they have physically demodulated and/or decoded such D2D transmissions. D2D devices may not consider priority of ongoing or planned D2D communications when determining their transmission and/or receipt behavior. D2D terminals that are ready to transmit might not stop accessing channels until they have (e.g. physically) demodulated all or some of the channels. This is in case it is dealing with ongoing critical D2D communication. D2D terminals may not have been configured (e.g. never configured) with the knowledge or one or more D2D identifiers, derived payload encryption and/or key integrity protection keys that could be used by other D2D terminuses in their vicinity. One or more D2D terminals (e.g. most) may not be aware of the type and/or nature of D2D data they are trying to decode and distinguish using the D2D payload contents. In the absence of keys or associated identifiers, it is possible that the payload cannot be decoded. It is possible that no information about the D2D payload carried might be available.

This document describes “Mechanisms to enable D2D communications using LTE radio accessibility technology. They may include priority based channel access, priority-based handling of D2D communication as a function D2D terminal, type of D2D information to ensure service availability, QoS and/or pre-emption in emergency situations.” Access to priority-based transmission and/or access mechanisms can improve the efficiency of wireless transmissions and/or reduce D2D radio resource usage. It may also improve channel and/or service availability for D2D customers, as well as improve on existing LTE networks.

D2D data can refer to D2D-related communication between D2D terminals. D2D data could include data packets, such as voice, or segments thereof. It may also include IP packets, such as those used for file upload or download, streaming, or bi-directional video. It may also include D2D control signals, D2D discovery, service or availability messages, and so forth. These features can be used in conjunction with 3GPP D2D communications. Other features, such as D2D Discovery, may also be included.

Channel access may determine D2D priority. Access may be based on priority. Priority-based access can be made possible by using one or more data pools and/or SAs. Access mechanisms can be based on radio resources sets (e.g. segregated radio resource set).

“Priority-based access to D2D communications may be used in frequency-domain and/or time-domain segregated radio resource set.”

“Segregated radio resources sets in time and/or frequency for prioritized D2D access might be realized on radio ressources that may be used to Scheduling Assignments(SA), D2D Data, control or signaling such D2D discovery, one of these D2D signals/channels and/or more than one of them.”

“FIG. 2. is an example of priority-based access through TDM within the SA and D2D subframes. Priority based access for D2D communications may be realized through Time-Division-Multiplex (TDM) of the SA and/or the D2D data pools.”

FIG. 2 shows N=2 different SA pool and M=2 corresponding data pools. These 2 distinct SA pools are defined using different subframe subsets within the time domain. FIG. FIG. 2. There are L1=1 SA subframes for each SA pool during a scheduling period of P=160ms. Two D2D data pool may be divided over subframes. FIG. FIG. 2. There are L2=18 subframes available per D2D datapool per scheduling period.

An SA pool (e.g. the first SA pool shown in FIG. 2) may have SAs to accompany D2D transmissions (e.g. high priority D2D transmissions) within the D2D pool (e.g. first D2D pool) for the duration of a scheduling window. High priority transmissions could correspond to a responder chat group (e.g. first responder conversation group) or a high-priority vocal channel. An SA pool, such as FIG. 2’s second SA pool, may contain SAs for lower priority D2D transmissions. 2) can carry SAs for lower priority D2D transmissions within a D2D pool (e.g. the second SA pool in FIG. A background file download, and/or non-time critical D2D service data exchange may constitute a lower priority transmission.

“High-priority D2D Data Transmissions” may be made (e.g. only) using radio resources provided by the SA (e.g. first SA in FIG. 2), and/or the D2D pool (e.g. first D2D pool in FIG. 2). D2D data transmissions of lower priority may occur (e.g. only occur) depending on the radio resources that were used to transmit the SA (e.g. second SA) or D2D pool (e.g. second D2D pool). A subframe of the high priority (e.g. first) SA pool might not announce D2D information on radio resources for low priority (e.g. second) D2D pool. An SA carrying in a subframe from the low-priority (e.g. second) SA pool might not be able to announce D2D information on radio resources for high priority (e.g. first) D2D pool.

TDM in lower priority D2D transmitting might not be possible on higher priority SA/data pool, which could improve priority handling of D2D transmissions. The network-controlled radio resource allocation of the SA/D2D data on high priority pools may not allow for low priority D2D channels and devices to compete for TDM radio resources. WTRU autonomous contention resolution of such SA/data resources might not allow the channels and D2D devices with low priority to compete for the TDM radio resources. The segregated TDM radio resources might not be available to the lowest priority D2D channels and devices for random radio resource selection of SA/data. Higher priority D2D information may have a greater chance of being transmitted successfully, either during the initial determination of radio resources or during ongoing transmissions due to less interference from lower priority D2D. Resource segregation may prevent legacy D2D terminals from being able to access the new SA/data data pools of higher priority.

“FIG. 3. An example diagram showing priority-based access to D2D communications via TDM of SA within shared D2D subframes. Priority based access for D2D communications may be realized through Time-Division-Multiplex (TDM) of the SA pools, such as while using shared D2D data pool(s).”

“In FIG. FIG. 3 shows N=2 different SA pool and M=1 D2D data pools. These two distinct SA pools can be separated by subframes that are different or different in time-domain. FIG. FIG. 3. There are L1=1 SA subframes per SA pool for a scheduling period of P=160ms. There are L2=38 subframes available in the D2D data pool per scheduling period.

“The SA pool (e.g. first SA pool in FIG. 3.) may have SAs to accompany high priority D2D data transmissions. The SA pool (e.g. second SA pool in FIG. 3.) may have SAs to accompany lower priority D2D transmissions.

High-priority D2D data transmissions can be transmitted (e.g. only by) using radio resources of the high-priority SA pools (e.g. first SA pool). D2D data transmissions with lower priority may be transmitted using radio resources from the lower-priority SA pools (e.g. second). SAs transmitted from the D2D pool’s shared radio resources may be sent either from the high-priority SA pools (e.g. the first SA pool) or the lower-priority SA pools (e.g. the second).

“Priority handling of D2D transmissions could be improved. Priority handling for D2D transmissions could be improved if lower priority D2D transmits do not occur in the higher priority SA pool(s). The network-controlled radio resource allocation of the SA for the high priority pool(s) might be made by the network. Channels and devices with low priority D2D may not be able to compete for these segregated TDM radio radio resources. WTRU autonomous contention resolution may not allow the channels and D2D devices with low priority to compete for these segregated TDM radio resource. The random radio resource selection that determines the SA by D2D terminals might require the use of low priority D2D channels and devices. High priority D2D data might have a greater chance of being transmitted. This could be due to the avoidance of interference or contention on the SA radio resources. Priority-based access mechanisms can be used while maintaining the principle and/or resources utilization (e.g. inherent resource utilization) efficiency shared D2D data pool.

“FIG. “FIG. Priority based access for D2D communications may be realized through Frequency-Division-Multiplex (FDM) of the SA and/or the D2D data pools.”

FIG. 4 there is N=1 SA pool and M=1 D2D data pools in time domain. FIG. FIG. 4. There may be L1=2 subframes of the SA per SA pool for a scheduling period of P=160ms. FIG. FIG. 4 shows that there are L2=38 subframes available in the D2D database pool for each scheduling period. Radio resources in the SA pool have L2=2 distinct radio block subsets that are frequency-domain. Subframes containing SAs can contain SAs that allow high priority D2D Data transmission in RBs 10-30, and SAs that allow for low priority D2D Data transmission in RBs 40-60. D2D data subframes may contain high-priority or low priority transmissions (e.g. only in RBs 10-30, and RBs40-60, respectively). These subframes may be called frequency-domain SA or D2D data pool.

“The frequency domain SA pool (e.g. first frequency-domain SA Pool in FIG. The frequency-domain SA pool (e.g. first frequency domain SA pool in FIG. 4) may contain SAs to accompany high priority D2D transmissions in frequency=domain D2D pool (e.g. first frequency-domain D2D pool in FIG. 4, for example, during a time period. The frequency-domain SA Pool (e.g. second frequency-domain SA Pool in FIG. 4.) may contain SAs to accompany lower priority D2D transmissions within the frequency-domain D2D pool (e.g. second frequency-domain D2D pool in FIG. 4).”

“High-priority D2D Data Transmissions May (e.g. may only) Be Conducted on Radio Resources in Frequency Domain, Such as the frequency domain used for the SA (e.g. first SA) or the corresponding D2D pool (e.g. First D2D data pool. D2D data transmissions with lower priority may occur (e.g. may only) on radio resources used by the SA (e.g. second SA) or the data pool (e.g. second data pool) within frequency-domain. An SA that is carried in the subframe of the high priority SA frequency domain (e.g. first SA frequency domain) may not announce D2D information on radio resources used with low priority D2D (e.g. second D2D) frequency-domain. A SA carrying in the low priority frequency-domain SA region may not announce D2D information on radio resources within the high priority D2D frequency-domain (e.g. first D2D domain frequency-domain).

“Priority handling of D2D transmissions could be improved, for instance, when lower priority D2D transmits don’t occur on higher priority SA/data frequency domain pools. The segregated FDM radio resources might not be available to low priority D2D devices or channels. A higher priority D2D device or channel may have a greater chance (e.g., a significantly higher chance) to be transmitted during determination radio resources and/or ongoing transmissions, such as a transmission due lower interference from D2D data of lower priority.

“FIG. “FIG.5″ shows an example diagram showing priority-based access to D2D communications via FDM of SA within shared D2D subframes. Priority based access for D2D communications may be realized through Frequency-Division-Multiplex (FDM) of the SA pools while using shared D2D data pool(s).”

“In FIG. FIG. 5. There is N=1 SA pool and M=1 corresponding data pool in the time-domain. FIG. FIG. 5. There are L1=2 subframes of SAs per scheduling period P=160 ms. FIG. FIG. 5 shows that there are L2=38 subframes available in the D2D database pool for each scheduling period. Radio resources within the SA pool could include L2=2 distinct and/or different radio block subsets, in frequency-domain. SAs in subframes that contain SAs can include SAs for high priority D2D transmissions in RBs 10–30 and SAs in RBs 40-60. These are sometimes referred to in frequency-domain as SA pools. D2D data subframes may contain high-priority or low priority transmissions. For example, where indicated in one or more (e.g. all) RBs.

“The frequency domain SA pool (e.g. first frequency-domain SA Pool in FIG. 5) may be equipped with SAs to accompany high priority D2D transmissions such as those in the D2D pool for the duration of a scheduled period. The frequency-domain SA Pool (e.g. the second frequency-domain SA Pool in FIG. 5) could carry SAs to accompany lower priority D2D transmissions (e.g., in the D2D pool).

High-priority D2D data transmissions can (e.g. may only) be transmitted using radio resources from high-priority SA pools (e.g. first SA pool) within frequency-domain. D2D data transmissions with lower priority may be transmitted using radio resources in frequency-domain that are used for the lower-priority SA pools (e.g. second SA pool). SAs from the first SA pool, which is the highest priority, and/or the second SA pool, which are lower priorities, may be transmitted using radio resources used for the D2D pool’s shared radio resources.

Click here to view the patent on Google Patents.

How to Search for Patents

A patent search is the first step to getting your patent. You can do a google patent search or do a USPTO search. Patent-pending is the term for the product that has been covered by the patent application. You can search the public pair to find the patent application. After the patent office approves your application, you will be able to do a patent number look to locate the patent issued. Your product is now patentable. You can also use the USPTO search engine. See below for details. You can get help from a patent lawyer. Patents in the United States are granted by the US trademark and patent office or the United States Patent and Trademark office. This office also reviews trademark applications.

Are you interested in similar patents? These are the steps to follow:

1. Brainstorm terms to describe your invention, based on its purpose, composition, or use.

Write down a brief, but precise description of the invention. Don’t use generic terms such as “device”, “process,” or “system”. Consider synonyms for the terms you chose initially. Next, take note of important technical terms as well as keywords.

Use the questions below to help you identify keywords or concepts.

  • What is the purpose of the invention Is it a utilitarian device or an ornamental design?
  • Is invention a way to create something or perform a function? Is it a product?
  • What is the composition and function of the invention? What is the physical composition of the invention?
  • What’s the purpose of the invention
  • What are the technical terms and keywords used to describe an invention’s nature? A technical dictionary can help you locate the right terms.

2. These terms will allow you to search for relevant Cooperative Patent Classifications at Classification Search Tool. If you are unable to find the right classification for your invention, scan through the classification’s class Schemas (class schedules) and try again. If you don’t get any results from the Classification Text Search, you might consider substituting your words to describe your invention with synonyms.

3. Check the CPC Classification Definition for confirmation of the CPC classification you found. If the selected classification title has a blue box with a “D” at its left, the hyperlink will take you to a CPC classification description. CPC classification definitions will help you determine the applicable classification’s scope so that you can choose the most relevant. These definitions may also include search tips or other suggestions that could be helpful for further research.

4. The Patents Full-Text Database and the Image Database allow you to retrieve patent documents that include the CPC classification. By focusing on the abstracts and representative drawings, you can narrow down your search for the most relevant patent publications.

5. This selection of patent publications is the best to look at for any similarities to your invention. Pay attention to the claims and specification. Refer to the applicant and patent examiner for additional patents.

6. You can retrieve published patent applications that match the CPC classification you chose in Step 3. You can also use the same search strategy that you used in Step 4 to narrow your search results to only the most relevant patent applications by reviewing the abstracts and representative drawings for each page. Next, examine all published patent applications carefully, paying special attention to the claims, and other drawings.

7. You can search for additional US patent publications by keyword searching in AppFT or PatFT databases, as well as classification searching of patents not from the United States per below. Also, you can use web search engines to search non-patent literature disclosures about inventions. Here are some examples:

  • Add keywords to your search. Keyword searches may turn up documents that are not well-categorized or have missed classifications during Step 2. For example, US patent examiners often supplement their classification searches with keyword searches. Think about the use of technical engineering terminology rather than everyday words.
  • Search for foreign patents using the CPC classification. Then, re-run the search using international patent office search engines such as Espacenet, the European Patent Office’s worldwide patent publication database of over 130 million patent publications. Other national databases include:
  • Search non-patent literature. Inventions can be made public in many non-patent publications. It is recommended that you search journals, books, websites, technical catalogs, conference proceedings, and other print and electronic publications.

To review your search, you can hire a registered patent attorney to assist. A preliminary search will help one better prepare to talk about their invention and other related inventions with a professional patent attorney. In addition, the attorney will not spend too much time or money on patenting basics.

Download patent guide file – Click here