APPARATUSES, SYSTEMS, AND METHODS FOR DIFFERENTIATION OF PAYLOAD SIZE FOR D2D DISCOVERY

• US 20150271657A1
• Filed: 12/15/2014
• Published: 09/24/2015
• Est. Priority Date: 03/24/2014
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Xiong, Gang, Chatterjee, Debdeep
• Granted Patent: US 9,578,484 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04W 8/005 Discovery of network devices, e.g. terminals

Abstract

Wireless mobile devices or user equipments (UEs) may communicate directly with other UEs, e.g., using device-to-device (“D2D”) direct discovery and communication. D2D direct discovery and communication may be used, for example, when UEs communicate with each other while within direct wireless range of each other. Different service types for D2D direct discovery and communication sessions, such as public safety (PS) services, non-PS services, etc., may utilize different data characteristics for the discovery message (e.g., data types and data structures). Data associated with the at least one data frame of a D2D direct discovery transmission can be configured to indicate these different data characteristics.

Claims

1. A user equipment (UE) comprising:

circuitry configured to;

transmit a device-to-device (D2D) discovery request to an eNodeB to establish a D2D direct discovery link with a second UE, the D2D discovery request associated with a D2D service type;

receive resource allocation information associated with the D2D direct discovery link to transmit a discovery message to at least the second UE from the eNodeB, wherein the information is received via common or dedicated Radio Resource Control (RRC) signaling;

transmit a D2D data transmission to the second UE via the D2D direct discovery link, including at least one data frame comprising a data payload, a size of the data payload determined based on the D2D service type; and

configure data associated with the at least one data frame of the D2D data transmission to indicate the data payload size.

2. The UE of claim 1, wherein the D2D service type is to comprise at least one of a public safety (PS) service or a non-PS service.

3. The UE of claim 2, wherein a data payload size for the PS service is to comprise a larger size than a data payload size of the non-PS service.

4. The UE of claim 1, the circuitry to further comprise a medium access control layer (MAC), wherein the MAC is to configure the data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size, and is to further assert one or more bits in a MAC header of the at least one data frame.

5. The UE of claim 1, the circuitry to further comprise a physical layer (PHY), wherein the PHY is to configure the data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size, and is to further select a cyclic redundancy check (CRC) code associated with the D2D service type for the data payload.

6. The UE of claim 5, wherein the CRC code associated with the D2D service type for a data payload mask comprises a CRC masked with a data mask value associated with the D2D service type.

7. The UE of claim 1, the circuitry to further comprise a physical layer (PHY), wherein the PHY is to configure the data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size, and is to further request a resource block allocated by the eNodeB exclusively for use with the D2D service type.

8. The UE of claim 1, the circuitry to further comprise a medium access control layer (MAC), wherein the MAC is to configure the data associated with the at least one data frame of the D2D data transmission to indicate the data payload size, and is to further append the data payload with one or more zeros to match a bit count of a data payload size associated with a second D2D service type.

9. The UE of claim 1, wherein the circuitry is further configured to transmit the D2D discovery request to the eNodeB via a physical uplink shared channel (PUSCH).

10. The UE of claim 1, wherein the circuitry further comprises one or more antennas to transmit the D2D discovery request and the D2D data transmission.

11. An eNodeB comprising:

circuitry configured to;

allocate a set of physical resource blocks (PRBs) for a plurality of device-to-device (D2D) discovery service types, including a first subset of PRBs and subframes for a first D2D discovery service type, and a second subset of PRBs and subframes for a second D2D discovery service type, the first subset of PRBs and subframes and the second subset of PRBs and subframes to comprise non-overlapping subsets; and

configure transmission information comprising PRB allocation information for transmission to one or more user equipments (UEs) for transmission via at least one of common Radio Resource Control (RRC) or dedicated RRC signaling.

12. The eNodeB of claim 11, wherein the first D2D discovery service type comprises a public safety (PS) service, and the second D2D discovery service type comprises a non-PS service.

13. The eNodeB of claim 11, wherein the circuitry further configured to allocate one or more demodulation reference signals (DMRS) for each of the plurality of D2D discovery service types.

14. A method comprising:

transmitting a device-to-device (D2D) discovery request to an eNodeB for establishing a D2D direct discovery link with a user equipment (UE), the D2D discovery request associated with a D2D discovery service type comprising at least one of a public safety (PS) service or a non-PS service;

receiving resource allocation information associated with the D2D communication link from the eNodeB, wherein the resource allocation information comprises UE-specific or UE-common information; and

generating a D2D discovery message for transmission to the UE via the D2D communication link, the D2D discovery message including;

at least one data frame comprising a data payload, a size of the data payload determined based on the D2D service type, and

data associated with the at least one data frame of the D2D discovery message configured to indicate the data payload size.

15. The method of claim 14, wherein configuring data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size includes asserting one or more bits in a MAC header of the data frame.

16. The method of claim 14, wherein configuring data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size includes selecting a cyclic redundancy check (CRC) code associated with the D2D discovery service type for the data payload.

17. The method of claim 14, wherein configuring data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size includes masking a cyclic redundancy check (CRC) code for the data payload with a data mask value associated with the D2D service type.

18. A non-transitory computer-readable storage medium whose contents, when executed by a computing system, cause the computing system to perform operations, comprising

transmitting a device-to-device (D2D) discovery request to an eNodeB for establishing a D2D direct discovery link with a user equipment (UE), the D2D discovery request associated with a D2D discovery service type comprising at least one of a public safety (PS) service or a non-PS service;

receiving resource allocation information associated with the D2D communication link from the eNodeB, wherein the resource allocation information comprises UE-specific or UE-common information;

transmitting a D2D discovery message transmission to the UE via the D2D communication link, including at least one data frame comprising a data payload, a size of the data payload determined based on the D2D service type; and

configuring data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size

19. The non-transitory computer-readable storage medium of claim 18, further comprising:

requesting a discovery resource allocated by the eNodeB exclusively for use with the D2D discovery service type during a UE-specific discovery resource allocation procedure.

20. The non-transitory computer-readable storage medium of claim 18, wherein configuring data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size includes appending the data payload with one or more zeros to match a bit count of a data payload size associated with a second D2D service type.

21. The non-transitory computer-readable storage medium of claim 18, wherein the D2D discovery request is transmitted to the eNodeB via a physical uplink shared channel (PUSCH).

22. The non-transitory computer-readable storage medium of claim 18, wherein configuring data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size includes asserting one or more bits in a MAC header of the data frame.

23. The non-transitory computer-readable storage medium of claim 18, wherein configuring data associated with the at least one data frame of the D2D discovery message transmission to indicate the data payload size includes at least one of:

selecting a cyclic redundancy check (CRC) code associated with the D2D discovery service type for the data payload;

or

masking a CRC code for the data payload with a data mask value associated with the D2D service type.