Systems and methods for configuring a semi-persistent scheduler

Using a scheduler, communication may be scheduled between an access node and a plurality of wireless devices, wherein the plurality of wireless devices comprise one or more relay wireless devices or device to device (D2D) wireless devices. Using the scheduler, at least one relay wireless device or D2D wireless device may be scheduled using a semi-persistent scheduler comprising an adjusted periodicity, wherein a default periodicity used by the semi-persistent scheduler for end-user wireless devices is different from the adjusted periodicity. Data may be communicated between the access node and the at least one relay wireless device or D2D wireless device using the adjusted periodicity.

TECHNICAL BACKGROUND

As wireless networks evolve and grow, there are ongoing challenges in providing high-quality service to increasing numbers of wireless devices or user equipment (UE) in various coverage areas of a wireless network. One approach to improving service quality and coverage is to designate a wireless device as a relay node or relay wireless device for relaying communication between a base station or access node (donor access node), and an end-user wireless device. Other instances of wireless relay points, such as device to device (D2D) communication, may similarly be used. Relay wireless devices and D2D wireless devices may be implemented at the edge of a coverage area of an access node to improve coverage and/or service, as well as in crowded areas having a high number of other wireless devices to increase the available throughput to the end-user wireless devices being relayed. However, such relays may give rise to latency issues and other delay issues due to the additional step of relaying communication from access node to end-user wireless device. A scheduler that considers service requirements, such as latency, for particular types of data with particular service requirements may enhance the service provided to the end-user of the system.

OVERVIEW

Exemplary embodiments described herein include systems, methods, and nodes for configuring a semi-persistent scheduler. Using a scheduler, communication may be scheduled between an access node and a plurality of wireless devices, wherein the plurality of wireless devices comprise one or more relay wireless devices or device to device (D2D) wireless devices. Using the scheduler, at least one relay wireless device or D2D wireless device may be scheduled using a semi-persistent scheduler comprising an adjusted periodicity, wherein a default periodicity used by the semi-persistent scheduler for end-user wireless devices is different from the adjusted periodicity. Data may be communicated between the access node and the at least one relay wireless device or D2D wireless device using the adjusted periodicity.

DETAILED DESCRIPTION

In an embodiment, methods and system are described for configuring a semi-persistent scheduler. For example, a relay wireless device may connect a small cell to an access node such that the relay wireless device relays backhaul traffic to and from the access node and small cell. Further, a device to device (D2) communication group may be formed such that a particular one of the wireless devices within the group serves as a relay to the access node for the remaining devices. In such configurations, and other configurations that use a relay to connect to an access node or otherwise add an additional hop among a network path to a wireless device, certain service conditions such as latency and/or delay may be impacted. For example, data may take time to traverse the additional hop from access node to relay and then relay to end-user wireless device. In some embodiments, a scheduler that considers this delay for certain data, such as data with particular latency requirements or other service requirements, may schedule communication to mitigate against the additional time associated with relay devices.

FIG. 1depicts an exemplary system100for configuring a semi-persistent scheduler. System100may comprise a communication network101, gateway node102, controller node104, database105, communication link106, access node110, relay wireless device130, wireless devices140,142,144,146, and148, which may comprise end-user wireless devices, and coverage areas115and132. In an embodiment, access node110provides wireless services to wireless devices140,142, and144, and the illustrated relay access node that comprises a combination of relay wireless device130and small cell131, which may comprise a relay access point or node. For instance, small cell131may provide wireless services to wireless devices146and148, which may comprise end-user wireless device, and relay wireless device130may access communication network101via access node110. Consequently, access node110may be referred to as a donor access node. Relay wireless device130is thus configured to relay services from access node110to wireless devices146and148. In an embodiment, wireless devices144may comprise a device to device (D2D) communication group such that a particular wireless device from among the group connects to access node110and servers as a relay such that the remainder of the devices may communicate with access node110. Wireless devices144are further described with reference toFIG. 4.

In an embodiment, to achieve this, relay wireless device130may comprise a customer premise equipment (CPE), which may be any stationary LTE wireless device having a stronger computational & RF capability versus standard wireless devices, as well as a directional antenna and a dedicated power supply. Relay wireless device130also may be communicatively coupled to small cell131. Small cell131may include a mini-macro, picocell, femtocell, or the like that are capable of providing a wireless access point for wireless devices146and148, of which wireless devices148comprise a cluster of wireless devices. Access node110is illustrated as having coverage area115, small cell131is illustrated as having coverage area132. Relay wireless device130is located within coverage area115, as are wireless devices140,142, and144. Wireless device146is located outside of coverage area115but within coverage area132of small cell131and wireless devices148are located within both coverage areas115and132. In an embodiment, wireless devices148may access network services using the combination of relay wireless device130and small cell131, rather than overload access node110, which may be serving numerous other devices, such as wireless devices140,142, and144. Moreover, wireless device146that is outside coverage area115may access network services from access node110by virtue of being connected to relay wireless device130via small cell131.

In an embodiment, relay wireless device130can be configured to function as one or more of a layer 1 (L1), layer 2 (L2), or layer 3 (L3) relay. A layer 1 relay functions as a booster or repeater. In other words, a layer 1 relay device performs an amplify and forward (AF) function. RF signals received from access node110are amplified and transmitted by relay wireless device130to one or more of wireless devices146and148. Likewise, RF signals received from wireless devices146and148are amplified and transmitted by relay wireless device130to access node110. Alternatively or in addition, a layer 2 relay device performs a decode and forward (DF) function. RF signals received from access node110are demodulated and decoded, then encoded and modulated again before being transmitted by relay wireless device130to one or more of wireless devices146and148. Likewise, RF signals received from one or more of wireless devices146and148are demodulated and decoded, then encoded and modulated again before being transmitted by relay wireless device130to access node110. Alternatively or in addition, a layer 3 relay device also performs a decode and forward function. However, a layer 3 relay device also performs additional processing (such as ciphering and/or data concatenation/segmentation/reassembly). In other words, relay wireless device130may perform demodulation and decoding of the received RF signals (either uplink or downlink), processing of the received data, then encode, modulate, and transmit the data to one or more of wireless devices146and148.

Relay wireless device130and wireless devices140,142,144,146and148may be any device, system, combination of devices, or other such communication platform capable of communicating wirelessly with access node110using one or more frequency bands deployed by access node110. Relay wireless device130and wireless devices140,142,144,146and148may be, for example, a mobile phone, a wireless phone, a wireless modem, a personal digital assistant (PDA), a voice over internet protocol (VoIP) phone, a voice over packet (VOP) phone, or a soft phone, as well as other types of devices or systems that can exchange audio or data via access node110. Other types of communication platforms are possible. In some embodiments, relay wireless device130includes stronger computational & radiofrequency capabilities than an average wireless device, as well as a directional antenna, and dedicated power supply, so that they can sustain an over-the-air backhaul link for wireless devices146and148that attach to small cell131.

Communication link106can use various communication media, such as air, space, metal, optical fiber, or some other signal propagation path—including combinations thereof. Communication link106can be wired or wireless and use various communication protocols such as Internet, Internet protocol (IP), local-area network (LAN), optical networking, hybrid fiber coax (HFC), telephony, T1, or some other communication format—including combinations, improvements, or variations thereof. Wireless communication links can be a radio frequency, microwave, infrared, or other similar signal, and can use a suitable communication protocol, for example, Global System for Mobile telecommunications (GSM), Code Division Multiple Access (CDMA), or Long Term Evolution (LTE), or combinations thereof. Communication link106may include S1 communications links. Other wireless protocols can also be used. Communication link106can be a direct link or might include various equipment, intermediate components, systems, and networks. Communication link106may comprise many different signals sharing the same link

Gateway nodes102can be any network node or plurality of network nodes that are configured to interface with other network nodes using various protocols. Gateway nodes102can communicate user data over system100. Gateway nodes102can be standalone computing devices, computing systems, or network components, and can be accessible, for example, by a wired or wireless connection, or through an indirect connection such as through a computer network or communication network. For example, gateway nodes102can include a serving gateway (S-GW) and/or a public data network gateway (P-GW), etc. Gateway nodes102can include a relay S-GW/P-DW combination for providing gateway services to relay wireless device130, as well as a wireless device S-GW/P-DW combination for providing gateway services to one or more of wireless devices140,142,144,146, and148. In embodiments, data packets such as voice over IP (VoIP) data packets may be routed from one or more of wireless devices142,144,146, and148to a relay S-GW/P-GW first, and then to a UE S-GW/P-GW. However, persons having ordinary skill in the art would recognize that gateway nodes102are not limited to any specific technology architecture, such as Long Term Evolution (LTE), and can be used with any network architecture and/or protocol.

Controller node104can be any network node configured to communicate information and/or control information over system100. Controller node104can be configured to transmit control information associated with a handover procedure. Controller node104can be a standalone computing device, computing system, or network component, and can be accessible, for example, by a wired or wireless connection, or through an indirect connection such as through a computer network or communication network. For example, controller node104can include a mobility management entity (MME), a Home Subscriber Server (HSS), a Policy Control and Charging Rules Function (PCRF), an authentication, authorization, and accounting (AAA) node, a rights management server (RMS), a subscriber provisioning server (SPS), a policy server, etc. One of ordinary skill in the art would recognize that controller node104is not limited to any specific technology architecture, such as Long Term Evolution (LTE) and can be used with any network architecture and/or protocol.

Controller node104can comprise a processor and associated circuitry to execute or direct the execution of computer-readable instructions to obtain information. Controller node104can retrieve and execute software from storage, which can include a disk drive, a flash drive, memory circuitry, or some other memory device, and which can be local or remotely accessible. In an exemplary embodiment, controller node104includes a database105for storing access node characteristics. The software comprises computer programs, firmware, or some other form of machine-readable instructions, and may include an operating system, utilities, drivers, network interfaces, applications, or some other type of software, and combinations thereof. Controller node104can receive instructions and other input at a user interface.

Access node110can be any network node configured to provide communication between relay wireless device130and/or wireless devices140,142,144,146, and148, and communication network101. Access node110can be a macrocell access node such as a base transceiver station, a radio base station, an eNodeB device, or an enhanced eNodeB device, or the like. In an exemplary embodiment, a macrocell access node can have a coverage area115in the range of approximately five kilometers to thirty five kilometers and an output power in the tens of watts.

Small cell131may comprise a small access node, microcell access node, a picocell access node, a femtocell access node, or the like such as a home NodeB or a home eNodeB device. A coverage area for a small cell may be smaller than the overage area for a macro cell (e.g., access node110). Moreover, it is noted that while access node110and small cell131are illustrated inFIG. 1, any number of access nodes and/or small cells can be implemented within system100.

Access node110and small cell131can comprise a processor and associated circuitry to execute or direct the execution of computer-readable instructions to obtain information. Access node110and small cell131can retrieve and execute software from storage, which can include a disk drive, a flash drive, memory circuitry, or some other memory device, and which can be local or remotely accessible. The software comprises computer programs, firmware, or some other form of machine-readable instructions, and may include an operating system, utilities, drivers, network interfaces, applications, or some other type of software, including combinations thereof. Access node110and small cell131can receive instructions and other input at a user interface. Access node110communicates with gateway nodes102and controller node104via communication link106. Operations performed by one or all of access node110and small cell131are further described herein with reference toFIGS. 5 and 6.

Other network elements may be present in system100to facilitate communication but are omitted for clarity, such as base stations, base station controllers, mobile switching centers, dispatch application processors, and location registers such as a home location register or visitor location register. Furthermore, other network elements that are omitted for clarity may be present to facilitate communication, such as additional processing nodes, routers, gateways, and physical and/or wireless data links for carrying data among the various network elements, e.g. between access node110and communication network101.

FIG. 2depicts an exemplary relay wireless device230, or relay user equipment (UE), coupled to a small cell231, which may comprise a picocell. Relay wireless device230is illustrated as comprising an antenna251for direct (e.g., unrelayed) communication with access node210via communication link232, a transceiver252, a processor253, and a memory254for storing instructions that enable relay wireless device230to perform operations described herein. In some embodiments, relay wireless device230is referred to as a customer premise equipment (CPE), which includes any stationary LTE wireless device having a stronger computational & RF capability versus standard wireless devices, as well as a directional antenna and a dedicated power supply, enabling relay wireless device230to efficiently provide resources to wireless devices240, which may comprise end-user wireless devices, via small cell231. Consequently, small cell231may be co-located with relay wireless device230, and is connected to relay wireless device230via a communication interface233. Communication interface233may be any interface that enables direct communication between relay wireless device230and small cell231, such as USB, FireWire, Ethernet, or any other serial, parallel, analog, or digital interface. Small cell231is illustrated as comprising an antenna255for wireless communication with wireless devices240, a transceiver256, a processor257, and a memory258for storing instructions that enable small cell231to perform operations described herein. In some embodiments, small cell231may be a Home eNodeB. Moreover, although only one transceiver is depicted in each of relay wireless device230and small cell231, additional transceivers may be incorporated in order to facilitate communication across interface233and other network elements.

In operation, relay wireless device230relays network services from access node210to wireless devices240via small cell231. Relay wireless device230may begin to function as a relay by sending a message to access node210to indicate to access node210that relay wireless device230is functioning as a relay wireless device. Access node210may consequently alter how relay wireless device230is assigned resources. In some embodiments, relay wireless device230can request to send a buffer status report to access node210. Access node210can grant this request in a conventional manner. Relay wireless device230may respond to the grant by sending a short buffer status report. This short buffer status report is associated with a logical channel group that indicates the buffer status report is communicating the status of the UE as a relay, and thus is not asking for additional resource allocations (like a ‘conventional’ buffer status report would indicate). In other words, when a UE responds with a buffer status report for a predetermined logical channel group, it indicates that the UE is functioning as a relay rather than serving as a conventional buffer status report. Once status of relay wireless device230is established, relay wireless device230may instruct small cell231to start accepting connection requests from one or more of wireless devices240.

FIG. 3depicts an exemplary access node310which may comprise, for example, a macro access node. As described herein, access node310provides access to network services from network301to wireless devices340,341,342,343, which may comprise end-user wireless devices, either directly, or via relay wireless device330and small cell331. In this embodiment, access node310is illustrated as being in communication with network301via communication link306, and comprising a memory311for storing instructions that enable access node310to perform operations described herein. Further, access node310comprises a processor312for executing operations, and a transceiver313coupled to an antenna314for wireless communication with one or more wireless devices, such as end-user wireless device340, or relay wireless device330. Further, communication link306may be any interface that enables communication between access node310and network301, such as an S1 interface. In some embodiments, access node310may be in communication with multiple relay wireless devices connected to small cell331, such as relay wireless devices330and332. Here, access node310provides access to network services from network301to end-user wireless devices340,341,342,343, via relay wireless devices330and332, and small cell331. Other network nodes such as gateways and controllers may be present but are not shown for purposes of simplicity.

FIG. 4depicts a device to device (D2D) communication group of wireless devices.FIG. 4illustrates access node110and wireless devices144ofFIG. 1, where wireless devices144comprise a D2D communication group comprising wireless devices402,404,406, and408. In an embodiment, wireless devices144may use device to device (D2D) communication in order to communicate data between the devices (e.g., without using the access node).

As illustrated, wireless device402may comprise a connection with access node110(e.g., radio resource connection (RRC) or data bearer connection) while the remaining wireless devices do not comprise a connection with the access node. When access node110receives data for one or more of wireless devices404,406, and408, the data may be transmitted to wireless device402which in turn transmits the data to the recipient wireless device using a D2D transmission. In some embodiments, one or more of wireless devices144may comprise a connection with access node110, where the one or more wireless devices may connect the remaining wireless devices in the D2D communication group with access node110. For example, other than wireless device402, one or more of wireless devices404,406, and408may comprise a connection with access node110. As such, communication with access node110may be scheduled with the connected wireless devices of the D2D communication group.

In an embodiment, the D2D communication between wireless devices144may include a transmission of data from wireless device402to wireless device404. For example, wireless device402may transmit a number of transmissions over a period of time, such as a video stream or any other suitable transmission. In this example, data to be transmitted to wireless device404from wireless device402may be buffered at wireless device402in a buffer (e.g., memory). In some embodiments, the data may be transmitted between wireless device402and wireless device404according to one or more services requirements (e.g., quality of service class identifier (QCI) requirements or any other suitable service requirements). Communication between other wireless devices within the D2D communication group may be similarly implemented. For example, where multiple wireless devices comprise a connection with access node110, similar techniques may be implemented to achieve the D2D communication between group members.

In an embodiment, a D2D communication group may communicate data over one or more frequency bands using a communication protocol similar to the protocol used by access node110. For example, one of wireless devices144may transmit data to the other wireless device using an antenna. In an embodiment, wireless devices144may communicate data using wireless resources that are used by access node110when communicating with wireless devices over signal area115. In this example, the wireless resources used by the D2D communication group are shared with access node110, and thus do not comprise dedicated wireless resources. In another embodiment, wireless devices144may communicate using dedicated wireless resources (e.g., not shared with access node110).

Referring back toFIG. 1, in operation, system100may use a plurality of carriers in order to provide wireless communication services. For example, a plurality of carriers that comprise bandwidth for wireless communications (e.g., one or more carriers over a 1.25 GHz spectrum, one or more carriers over a 1900 MHz spectrum, one or more carriers over a 800 MHz spectrum, and the like) may include a plurality of channels (e.g., 5 MHz channels, 10 MHz channels, 15 MHz channels, and the like) that may further be divided into subcarriers. In an embodiment, a frequency band may comprise a carrier, a channel, a subcarrier, a plurality of any of these, or any other suitable frequency band.

In an embodiment, access node110may comprise a scheduler that schedules communication between wireless devices and access node110. The scheduler may comprise hardware and associated circuitry or software implementing computer code to perform scheduling functions. The scheduler may be communicatively connected to one or more antennas of access node110such that the scheduler may configure the access node to transmit downlink signals and receive uplink signals according to a schedule (e.g., resource block allocations).

In an embodiment, the scheduler may schedule communication with access node110using semi-persistent scheduling. For example, bandwidth may be scheduled for a wireless device (e.g., based on a QCI for the wireless device) for a semi-persistent duration (e.g., over a limited period of time). Once scheduled, a physical resource block (PRB) and transmission time interval (TTI) combination may be reserved for a particular wireless device for a period of time (e.g., duration of a call). In an embodiment, the semi-persistent assigned resources for a wireless device may comprise a periodicity. For example, the assigned wireless resources (e.g., transmission of a physical resource block from access node110to a wireless device) may be repeated based on the periodicity for the assignment (e.g., 10 ms, 15 ms, 20 ms, and the like). In an embodiment, the semi-persistent assignment of resource to a wireless device may comprise both downlink resources (e.g., physical resource blocks on the Physical Downlink Shared Channel (PDSCH)) and uplink resources (e.g., physical resource blocks on the Physical Uplink Shared Channel (PUSCH)).

In some embodiments, as illustrated, one or more relay wireless devices may overlap with coverage area115of access node110, such as relay wireless device130. Since the relay wireless devices serve as backhaul for one or more small cells (e.g., small cell131), the scheduler of access node110may schedule communication with relay wireless device130. In turn, small cell131may service a number of end-user wireless devices, as illustrated inFIG. 1.

In some embodiments, end-user wireless devices that communicate with access node110using a relay (e.g., relay wireless device130or a relay from a D2D communication group) may encounter delays and/or latency issues with data that comprises certain service requirements. For example, voice data (e.g., VoIP data) may comprise minimum latency requirements in order to effectively execute a voice call. Accordingly, it may be beneficial to configure the scheduler of access node110to consider the service conditions of end-user wireless devices that communicate with the access node using a relay when scheduling wireless resources for the relays that connect these end-user wireless devices.

FIG. 5illustrates an exemplary method for configuring a semi-persistent scheduler according to an embodiment. The method will be discussed with reference to the exemplary communication system100illustrated inFIG. 1, however, the method can be implemented with any suitable communication system.

Referring toFIG. 5, at step502, using a scheduler, communication may be scheduled between an access node and a plurality of wireless devices, wherein the plurality of wireless devices comprise one or more relay wireless devices or device to device (D2D) wireless devices. For example, access node110may comprise a scheduler that schedules communication (e.g. uplink and downlink communication) with wireless devices130,140,142, and144. The scheduler may use a round robin scheduling, proportional fairness scheduling, max C/I scheduling, semi-persistent scheduling, delay based scheduling, a combination of these, or any other suitable scheduling protocol.

In an embodiment that implements semi-persistent scheduling, bandwidth may be scheduled for a wireless device (e.g., based on a QCI for the wireless device) for a semi-persistent duration (e.g., over a limited period of time). Once scheduled, a physical resource block (PRB) and transmission time interval (TTI) combination may be reserved for a particular wireless device for a period of time (e.g., duration of a call). In an embodiment, the semi-persistent assigned resources for a wireless device may comprise a periodicity. For example, the assigned wireless resources (e.g., transmission of a physical resource block from access node110to a wireless device) may be repeated based on the periodicity for the assignment (e.g., 10 ms, 15 ms, 20 ms, and the like). In an embodiment, the semi-persistent assignment of resource to a wireless device may comprise both downlink resources (e.g., physical resource blocks on the Physical Downlink Shared Channel (PDSCH)) and uplink resources (e.g., physical resource blocks on the Physical Uplink Shared Channel (PUSCH)).

In an embodiment that implements delay based scheduling, the scheduler may consider the age of a packet received at access node110when scheduling communication. For example, packets received at access node110may be time stamped and queued in a buffer for transmission. For each packet in the queue, a packet delay may be computed. The packets may then be transmitted to wireless devices in communication with access node110based on a packet delay budget. A packet delay budget may comprise a tolerable delay for a data packet that may be based on the application associated with the data packet or a service associated with the data packet (e.g., streaming video). In an embodiment, the remaining time for a packet (di(t)), may be calculated as shown: di(t)=Ti−Wi,t, where Timay be the packet delay budget and Wi,tmay be the packet delay for the packet based on the timestamp. In an example, a user with the lowest calculated di(t) may be scheduled the next transmission by access node110.

In an embodiment, one or more wireless devices in communication with access node110may not comprise end-user wireless devices or may otherwise comprise a device used as a relay for an end-user wireless device. For example, relay wireless device130may serve as a relay backhaul for small cell131, as described herein with reference toFIG. 1. Further, wireless device402, which is part of the D2D communication group comprised of wireless devices144, as described with reference toFIG. 4, may relay communication to connect wireless device404,406, and408to access node110.

At step504, it may determined to schedule communication between the access node and the at least one relay wireless device or D2D wireless device using semi-persistent scheduling. For example, it may be determined that the scheduler at access node110is to schedule wireless resource for one or both of relay wireless device130and wireless device402using semi-persistent scheduling, as described herein.

In an embodiment, one or more wireless devices that communicate with small cell131may have initiated a voice call or VoIP call (e.g., may be communicating voice data with small cell131). As a result, the backhaul communication between relay wireless device130and access node110may include voice data. In some instances, voice data may comprise certain service requirements. For example, when wireless device146uses small cell131(as well as relay wireless device130and access node110) to initiate a voice call or a VoIP call, the wireless device may communicate with small cell131with a particular data bearer that comprises service requirements. For example, the service requirements for the data bearer may be associated with a particular QCI. A QCI may comprise a set of service requirements for communication between an access point and a wireless device. For example, the set of service requirements may include permitted packet delay budget, latency requirements, permitted packet error loss rate, guaranteed or non-guaranteed bit rate, priority, and the like. In this example, wireless device146may communicate with small cell131with a data bearer associated with a QCI for voice traffic.

In some embodiments, one or more of wireless devices404,406, and408may have initiated a voice call or VoIP call (e.g., may be communicating voice data with wireless device402). As a result, the communication between wireless device402and access node110may include voice data. Similar to the QCI requirements associated with the data bearer between small cell131and wireless device146, the communication between wireless device402and the wireless device that initiated the voice call may comply with certain service requirements associated with voice data.

In an embodiment, it may determined to schedule communication between the access node and the at least one relay wireless device or D2D wireless device using semi-persistent scheduling based on identified data communicated that comprise an indication of voice data. For example, the scheduler at access node110may use semi-persistent scheduling when an end-user wireless device initiates a voice call or VoIP call. Similarly, when an end-user wireless device that communicates with access node110via a relay (e.g., relay wireless device130or wireless device402) initiates a voice call or VoIP call, access node110may determine to schedule the wireless device that relays communication to the end-user wireless device with semi-persistent scheduling. For example, when one of wireless device404,406, and408initiates a voice call or VoIP call, access node110may determine to schedule wireless device402using semi-persistent scheduling. In another example, when wireless device146initiates a voice call or VoIP call, access node110may determine to schedule relay wireless device130using semi-persistent scheduling.

In an embodiment, access node110may receive an indication that one of the wireless devices in communication with small cell131has initiated a voice call or VoIP call. For example, header information in the data communicated between relay wireless device130and access node110may indicate that one or more end-user wireless devices in communication with small cell131have initiated a voice call or VoIP call. For instance, because relay wireless device130transmits backhaul communication for these end-user wireless devices, the backhaul data communicated will comprise voice data when one or more of these end-users have initiated a call. In some examples, predetermined header information may indicate that the communicated data comprises voice data. Similarly, data communicated between wireless device402and access node110may indicates that one or more wireless devices within the D2D communication group have initiated a voice call or VoIP call. In some embodiments, other control information communicated between relay wireless device130and access node110or wireless device402and access node110may indicate such voice data. For example, an indication may be transmitted by relay wireless device130over the Physical Uplink Control Channel (PUCCH).

At step506, using a scheduler, communication may be scheduled between the access node and at least one relay wireless device or D2D wireless device using semi-persistent scheduling comprising an adjusted periodicity. For example, it may be determined that one or both of relay wireless device130and wireless device402are to be scheduled using semi-persistent scheduling. Here, because these wireless devices relay communication back to other end-user wireless devices, the periodicity for the semi-persistent scheduling may be adjusted.

For example, relay device130may be scheduled with semi-persistent scheduling and, because the device relays communication to end-user wireless devices (e.g., via small cell131), a periodicity for the scheduling between relay wireless device130and access node110may be adjusted. In some embodiments, the periodicity may be decreased from a default periodicity value. For example, where a default periodicity value is 20 ms, the periodicity for the semi-persistent scheduling of relay wireless device130may be decreased to 15 ms, 10 ms, 5 ms, and the like. The default periodicity may comprise the periodicity used to schedule semi-persistent resources to normal end-user wireless devices (e.g., wireless devices that do not relay communication to other end-user wireless devices), or to end-user wireless devices that initiate a voice call or VoIP call. In other examples where wireless device402is scheduled with semi-persistent scheduling, a similar adjustment may be made to the periodicity for the scheduling.

In an embodiment, access node110may receive an indication for one or both of relay wireless device130and wireless device402that indicates these wireless devices relay communication to other end-user wireless devices. For example, a buffer status received from these wireless devices may be predetermined to indicate the relay status. In another example, a PLMN-ID for the wireless devices may be predetermined to indicate their relay status to access node110. Any other suitable indication of the relay status for these wireless devices may be implemented. The adjusted periodicity for these wireless devices may be based on this indication of relay status.

In some embodiments, a number of end-user wireless devices that communicate voice data with the access node via the at least one relay wireless device or D2D wireless device may be determined, and the periodicity for the semi-persistent scheduling used to schedule communications between the access node and the at least one relay wireless device or D2D wireless device may be adjusted based on the determined number. In this example, the adjusted periodicity may be inversely related to the determined number.FIG. 6further describes embodiments where the adjusted periodicity is related this determined number.

At step508, data may be communicated between the access node and the at least one relay wireless device or D2D wireless device using the adjusted periodicity. For example, data may be communicate between access node110and one or both of relay wireless device130and wireless device402using semi-persistent scheduling comprising the adjusted periodicity. Accordingly, the semi-persistent scheduled resources (e.g., downlink and/or uplink physical resources blocks) may be repeated based on the adjusted periodicity.

In an embodiment, based on the semi-persistent scheduling from access node110, relay wireless device130may communicate with small cell131and small cell131may communicate with one or more end-user devices that have initiated a voice call or VoIP call. Similarly, based on the semi-persistent scheduling from access node110, wireless device402may communicate with one or more end-user wireless devices that have initiated a voice call or VoIP call. Accordingly, the semi-persistent scheduling and adjusted periodicity may provide voice services to end-user wireless devices that leverage relays (e.g., relay wireless device130and/or wireless device402that is part of a D2D communication group) to communication with an access node.

FIG. 6illustrates an exemplary method for configuring a semi-persistent scheduler using an adjusted periodicity according to an embodiment. The method ofFIG. 6may be implemented together with the method ofFIG. 5, for instance at step506. The method will be discussed with reference to the exemplary communication system100illustrated inFIG. 1, however, the method can be implemented with any suitable communication system.

Referring toFIG. 6, at step602, end-user wireless device connections that meet a criteria may be counted. For example, one or more wireless devices in communication with access node110may not comprise end-user wireless devices or may otherwise comprise a wireless device used as a relay for an end-user wireless device, such as relay wireless device130and D2D communication group wireless device402, as described herein. In an embodiment, end-user wireless devices that use one of more of these wireless devices to relay communication to access node110and that also comprise a connection that meets a connection criteria may be counted.

In an embodiment, one or more wireless devices that communicate with small cell131may have initiated a voice call or VoIP call (e.g., may be communicating voice data with small cell131). For example, when wireless device146uses small cell131(as well as relay wireless device130and access node110) to initiate a voice call or a VoIP call, the wireless device may communicate with small cell131with a particular data bearer that comprises certain service requirements. For example, the service requirements for the data bearer may be associated with a particular QCI, such as a predetermined QCI for voice traffic. In some embodiments, a plurality of wireless devices in communication with small cell131may similarly communicate with a data bearer associated with a QCI for voice traffic. In this example, the number of wireless devices that communicate with small cell131with a QCI that meets a criteria (e.g., with a QCI that is associated with voice traffic) may be counted.

In some embodiments, one or more of wireless devices404,406, and408may have initiated a voice call or VoIP call (e.g., may be communicating voice data with wireless device402). As a result, and based on the D2D communication group comprising these wireless devices, the communication between wireless device402and access node110may include voice data. Similar to the QCI requirements associated with the data bearer between small cell131and wireless device146, the communication between wireless device402and the wireless device that initiated the voice call may comply with certain service requirements associated with voice data (e.g., latency requirements, data rate requirements, error rates requirements, and the like). In some embodiments, a plurality of wireless devices in communication with wireless device402as part of the D2D communication group may communicate with a connection that meets certain service requirements associated with voice data. In this example, the number of wireless devices that communicate with wireless device402as part of the D2D communication group with a connection that comprises service requirements that meet a criteria (e.g., services requirements associated with voice traffic) may be counted.

In some embodiments, access node110may receive an indication of the number of wireless devices that comprise a connection that meets this criteria. For example, the communication between access node110and relay wireless device130may indicate to the access node the number of data bearers between small cell131and end-user wireless devices that meets the criteria. Similarly, the communication between access node110and wireless device402may indicate to the access node the number of connections between wireless device402and other end-user wireless device members of the D2D communication group that meet the criteria. In some embodiments, the indication may comprise control data predetermined to indicate a traffic condition at the small cell131and/or wireless device402. In some embodiments, relay wireless device130may transmit an indication of this number of wireless devices over the PUCCH when communicating with access node110.

At step508, a periodicity for semi-persistent scheduling used to schedule resources between the access node and one or both of the relay wireless device and the D2D wireless device may be adjusted based on the counted numbers of connections. For example, access node110may receive an indication of the number of end-user wireless devices in communication with small cell131that comprise data bearers that meet a criteria. Based on this number, the scheduler at access node110may adjust the periodicity for the semi-persistent scheduling used to schedule relay wireless device130. The periodicity may be inversely related to this number. Accordingly, where a default periodicity comprises 20 ms, the periodicity may be reduced to 15 ms when the numbers meets a first threshold, 10 ms when the number meets a second threshold, and 5 ms when the number meets a third threshold, where the second threshold is greater than the first threshold and the third threshold is greater than the second threshold.

In an embodiment, access node110may receive an indication of the number of end-user wireless devices in communication with wireless device402as part of a D2D communication group that comprise connections that meet a criteria. Based on this number, the scheduler at access node110may adjust the periodicity for the semi-persistent scheduling used to schedule wireless device402. The periodicity may be inversely related to this number. Accordingly, where a default periodicity comprises 20 ms, the periodicity may be reduced to 15 ms when the numbers meets a first threshold, 10 ms when the number meets a second threshold, and 5 ms when the number meets a third threshold, where the second threshold is greater than the first threshold and the third threshold is greater than the second threshold

In an embodiment where the method ofFIG. 6is implemented with the method ofFIG. 5, the adjusted periodicity may be used to schedule wireless resource between access node110and one or both of relay wireless device130and wireless device402, as described in step506. Data may then be communicated between access node110and one or both of relay wireless device130and wireless device402

FIG. 7depicts an exemplary processing node700comprising communication interface702, user interface704, and processing system706in communication with communication interface702and user interface704. Processing system8includes storage708, which can comprise a disk drive, flash drive, memory circuitry, or other memory device. Storage708can store software710which is used in the operation of the processing node700. Storage708may include a disk drive, flash drive, data storage circuitry, or some other memory apparatus. Software710may include computer programs, firmware, or some other form of machine-readable instructions, including an operating system, utilities, drivers, network interfaces, applications, or some other type of software. For example, software710may include modules for performing the operations described with reference toFIGS. 5 and 6. Processing system706may include a microprocessor and other circuitry to retrieve and execute software710from storage708. Processing node700may further include other components such as a power management unit, a control interface unit, etc., which are omitted for clarity. Communication interface702permits processing node700to communicate with other network elements. User interface704permits the configuration and control of the operation of processing node700.