WO2015062260A1 - 设备到设备组播/广播通信处理方法、装置及用户设备 - Google Patents

设备到设备组播/广播通信处理方法、装置及用户设备 Download PDF

Info

Publication number
WO2015062260A1
WO2015062260A1 PCT/CN2014/078347 CN2014078347W WO2015062260A1 WO 2015062260 A1 WO2015062260 A1 WO 2015062260A1 CN 2014078347 W CN2014078347 W CN 2014078347W WO 2015062260 A1 WO2015062260 A1 WO 2015062260A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
broadcast
air interface
interface identifier
broadcast communication
Prior art date
Application number
PCT/CN2014/078347
Other languages
English (en)
French (fr)
Inventor
陈琳
朱进国
黄莹
李大鹏
黄河
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2015062260A1 publication Critical patent/WO2015062260A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup

Definitions

  • the present invention relates to the field of communications, and in particular to a device-to-device D2D multicast/broadcast communication processing method, apparatus, and user equipment.
  • BACKGROUND With the development of wireless multimedia services, the demand for high data rates and user experiences is increasing, which places high demands on the system capacity and coverage of traditional cellular networks.
  • application scenarios such as public safety, social networking, close-range data sharing, and local advertising have led to an increasing demand for understanding and communicating with nearby people or things (Proximity Services).
  • the traditional base station-centric cellular network has obvious limitations in supporting high data rates and proximity services. In the context of this demand, it represents a new device-to-device (Device-to-Device) for future communication technologies.
  • D2D Referred to as D2D
  • the application of D2D technology can reduce the burden on the cellular network, reduce the battery power consumption of the user equipment, increase the data rate, and improve the robustness of the network infrastructure, which satisfies the requirements of the above high data rate services and proximity services.
  • the D2D broadcast/multicast communication establishment in the case of a shortage of public communication resources or congestion or network infrastructure is not provided in the public security scenario, that is, the related technology is Among them, there is a problem that the UE cannot implement D2D multicast and broadcast communication without coverage or coverage and partial coverage scenarios.
  • the present invention provides a device-to-device D2D multicast/broadcast communication processing method, apparatus, and user equipment, to at least solve the related art, where the UE cannot implement D2D multicast in the case of no coverage or coverage and partial coverage scenarios. And the issue of broadcast communication.
  • a device-to-device D2D multicast/broadcast communication processing method including: obtaining an air interface identifier for identifying a user equipment and/or D2D multicast/broadcast communication, and the D2D multicast Resource information of the broadcast communication; performing D2D multicast/broadcast communication processing on the resource corresponding to the resource information according to the air interface identifier.
  • the performing D2D multicast/broadcast communication processing on the resource corresponding to the resource information according to the air interface identifier includes: transmitting, according to the air interface identifier, a D2D multicast/broadcast communication data packet on a resource corresponding to the resource information; And/or receiving, according to the air interface identifier, a D2D multicast/broadcast communication data packet on a resource corresponding to the resource information.
  • the obtaining the air interface identifier for identifying the user equipment and/or the D2D multicast/broadcast communication includes at least one of: acquiring the air interface identifier from a D2D application server; and multicasting the D2D according to the first predetermined rule.
  • the air interface identifier is obtained by mapping the D2D multicast/broadcast IP address to the air interface identifier according to the second predetermined rule.
  • the air interface identifier is generated according to the D2D multicast/broadcast application layer identifier and/or the user equipment pass-through identifier; the air interface identifier is obtained from the neighboring node, where the neighboring node periodically broadcasts the air interface identifier Receiving the air interface identifier from the central node, where the central node is configured to control the D2D multicast/broadcast communication.
  • the obtaining the air interface identifier from the central node includes: transmitting, to the central node, a D2D multicast/broadcast communication request including a user equipment pass-through identifier and/or a D2D multicast/broadcast application layer identifier; receiving the central node The air interface identifier allocated according to the D2D multicast/broadcast communication request.
  • the obtaining the air interface identifier from the central node includes: receiving a message that includes the air interface identifier, where the message is sent by the central node by means of periodic broadcast.
  • the obtaining the resource information for the D2D multicast/broadcast communication includes at least one of: acquiring the resource information from a D2D application server; acquiring the resource information that is defaulted by the system; acquiring the Resource information; acquiring the resource information from a neighboring node, wherein the neighboring node periodically broadcasts a message including the resource information; acquiring the resource information from a central node, where the central node is used for The D2D multicast/broadcast communication is controlled.
  • the obtaining the resource information from the central node includes: receiving a message that includes the resource information, where the message is sent by the central node by means of periodic broadcast.
  • the obtaining the resource information from the central node includes: sending a D2D multicast/broadcast communication request to the central node; and receiving the resource of the resource allocated by the central node according to the D2D multicast/broadcast communication request information.
  • the multicast/broadcast communication request includes at least one of the following: a D2D multicast/broadcast application layer identifier, a user equipment pass-through identifier, a D2D multicast/broadcast IP address, a multicast/broadcast communication indication, and a D2D multicast/ Broadcast priority, one or more multicast/broadcast traffic flow quality of service QoS information.
  • the multicast/broadcast communication request includes one or more multicast/broadcast communication service flow quality of service
  • the receiving the resource information of the resource allocated by the central node according to the D2D multicast/broadcast communication request includes: receiving a multicast/broadcast communication confirmation message sent by the central node, where The central node performs admission control according to the one or more multicast/broadcast communication service flow quality of service QoS information included in the multicast/broadcast communication request, and determines an accepted multicast/broadcast communication service flow, the multicast/ The broadcast communication confirmation message includes at least one of the following: resource information of the resource allocated by the central node, and the received multicast/broadcast communication service flow.
  • the resource information includes at least one of: frequency information of multicast/broadcast communication, frequency band resource information of multicast/broadcast communication, frame offset information of multicast/broadcast communication, and multicast/broadcast communication Subframe offset information, subframe mode information of multicast/broadcast communication, slot information of multicast/broadcast communication, resource block information of multicast/broadcast communication, resource repetition period information of multicast/broadcast communication, and The D2D multicast/broadcast air interface identifier corresponding to the resource information, and the air interface identifier information of the user equipment that sends the D2D multicast/broadcast communication data packet.
  • the resource information includes at least one of the following: resource bearer identifier, media access control MAC configuration information, radio link control RLC configuration information, packet data convergence protocol PDCP configuration information, logical channel configuration information.
  • the transmitting the D2D multicast/broadcast communication data packet on the resource corresponding to the resource information according to the air interface identifier includes: transmitting, by the resource, the air interface identifier of the user equipment, the D2D multicast/ The D2D multicast/broadcast communication packet of at least one of the broadcast air interface identifier and the D2D multicast/broadcast indication.
  • the D2D multicast/broadcast communication packet carrying at least one of a user equipment air interface identifier, a D2D multicast/broadcast air interface identifier, and a D2D multicast/broadcast indication is sent on the resource by using at least one of the following manners:
  • the user equipment is carried in a media access control MAC subheader and/or a control unit of the D2D multicast/broadcast communication data packet, or a radio link control RLC subheader, or a packet data convergence protocol PDCP subheader
  • the air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication are transmitted on the resource, where the user equipment air interface identifier is carried, and the D2D multicast/broadcast air interface is carried.
  • the D2D multicast/broadcast indicating at least one of the D2D multicast/broadcast communication data packets using the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, the D2D multicast/ Broadcasting, instructing at least one of the D2D multicast/broadcast communication resource allocation control information and/or the data packet to be scrambled, and transmitting, on the resource, the air interface identifier of the user equipment Said D2D multicast/broadcast air interface identifier, said D2D multicast/broadcast indication at least one of said D2D multicast/broadcast communication data packets; resource location implicitly used by transmitting said D2D multicast/broadcast communication data packet Carrying the user equipment air interface identifier, the D2D multicast/broadcast empty And transmitting, by the resource identifier, the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, the D2D multicast/broad
  • the receiving the D2D multicast/broadcast communication data packet on the resource corresponding to the resource information according to the air interface identifier includes: determining, according to the D2D multicast/broadcast air interface identifier, the D2D multicast/broadcast communication data packet Whether the recipient belongs to the multicast/broadcast communication group corresponding to the air interface identifier; if the determination result is yes, the D2D multicast/broadcast communication data packet is parsed, and the parsed data packet is sent. To the upper layer; and/or, in the case of a negative decision, discard the D2D multicast/broadcast communication packet.
  • a device-to-device D2D multicast/broadcast communication processing apparatus comprising: an obtaining module configured to acquire an air interface identifier for identifying a user equipment and/or a D2D multicast/broadcast communication, And the resource information of the D2D multicast/broadcast communication; the processing module is configured to perform D2D multicast/broadcast communication processing on the resource corresponding to the resource information according to the air interface identifier.
  • the processing module includes: a sending unit, configured to send, according to the air interface identifier, a D2D multicast/broadcast communication data packet on a resource corresponding to the resource information; and/or, a receiving unit, configured to be according to the air interface Identifying that the D2D multicast/broadcast communication data packet is received on the resource corresponding to the resource information.
  • the acquiring module includes at least one of the following: a first acquiring unit, configured to acquire the air interface identifier from a D2D application server, and a second acquiring unit, configured to: use a D2D multicast/broadcast application according to the first predetermined rule Obtaining the air interface identifier in a manner that the layer identifier is mapped to the air interface identifier; the third acquiring unit is configured to obtain the air interface identifier by mapping the D2D multicast/broadcast IP address to the air interface identifier according to the second predetermined rule; The acquiring unit is configured to obtain the air interface identifier that is preset by the system in advance; the generating unit is configured to generate the air interface identifier according to the D2D multicast/broadcast application layer identifier and/or the user equipment pass-through identifier; and the fifth acquiring unit is set to be The neighboring node obtains the air interface identifier, where the neighboring node periodically broadcasts the message that includes the air interface identifier;
  • the fifth obtaining unit includes: a first sending subunit, configured to send, to the central node, a D2D multicast/broadcast communication request including a user equipment pass-through identifier and/or a D2D multicast/broadcast application layer identifier; a receiving subunit, configured to receive the air interface identifier allocated by the central node according to the D2D multicast/broadcast communication request.
  • the acquiring module includes at least one of the following: a seventh obtaining unit, configured to acquire the resource information from a D2D application server; an eighth obtaining unit, configured to acquire the resource information that is defaulted by the system; and a ninth acquiring unit,
  • the tenth acquiring unit is configured to acquire the resource information from a neighboring node, where the neighboring node periodically broadcasts a message including the resource information;
  • an acquiring unit configured to acquire the resource information from a central node, where the central node is configured to control the D2D multicast/broadcast communication.
  • the eleventh acquiring unit includes: a second sending subunit, configured to send a D2D multicast/broadcast communication request to the central node; and a second receiving subunit configured to receive the central node according to the D2D
  • the multicast/broadcast communication requests the resource information of the allocated resource.
  • the sending unit includes: a third sending subunit, configured to send, on the resource, at least one of the air interface identifier of the user equipment, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication The D2D multicast/broadcast communication packet.
  • the third transmitting subunit includes at least one of the following: a first sending secondary subunit, configured to control a MAC subheader and/or a control unit by media access in the D2D multicast/broadcast communication data packet, Or the radio link control RLC sub-header, or the packet data convergence protocol PDCP sub-header carrying the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication at least one of the manners Transmitting, on the resource, the D2D multicast/broadcast communication data packet carrying at least one of the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication; And transmitting, by the second sub-unit, the D2D multicast/broadcast communication resource allocation control by using at least one of the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast
  • the multicast/broadcast indicates at least one of the D2D multicast/broadcast communication data packets, where the resource location used to send the D2D multicast/broadcast communication data packet corresponds to the user equipment air interface identifier, At least one of a D2D multicast/broadcast air interface identifier, the D2D multicast/broadcast indication.
  • the receiving unit includes: a determining subunit, configured to determine, according to the D2D multicast/broadcast air interface identifier, whether the receiver of the D2D multicast/broadcast communication data packet belongs to the multicast/broadcast corresponding to the air interface identifier a communication group; the analysis subunit, configured to analyze the D2D multicast/broadcast communication data packet when the determination result of the determination subunit is YES, and send the parsed data packet to a higher layer; and / or, Discarding the subunit, and setting the discarding of the D2D multicast if the judgment result of the judging subunit is NO
  • a user equipment comprising the apparatus of any of the above.
  • the present invention uses the air interface identifier for identifying the user equipment and/or the D2D multicast/broadcast communication, and the resource information of the D2D multicast/broadcast communication; and the resource corresponding to the resource information according to the air interface identifier.
  • the D2D multicast/broadcast communication processing is performed on the device, and the related technologies have the problem that the UE cannot implement D2D multicast and broadcast communication in the case of no coverage or coverage and partial coverage scenarios, thereby achieving the UE without coverage or The effect of smooth D2D multicast and broadcast communication under coverage and partial coverage scenarios.
  • FIG. 1 is a flowchart of a device-to-device D2D multicast/broadcast communication processing method according to an embodiment of the present invention
  • FIG. 2 is a device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention
  • FIG. 3 is a processing module in a device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention
  • FIG. 4 is a block diagram of a preferred structure of the acquisition module 22 in the device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention
  • FIG. 5 is a device-to-device D2D group according to an embodiment of the present invention.
  • FIG. 6 is a block diagram showing a preferred structure of the obtaining module 22 in the device-to-device D2D multicast/broadcast communication processing device according to an embodiment of the present invention.
  • Figure 7 is a block diagram showing a preferred structure of the eleventh acquisition unit 65 in the acquisition module 22 of the device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention
  • Figure 8 is a device-to-device D2D according to an embodiment of the present invention
  • 9 is a block diagram showing a preferred structure of a third transmitting subunit 82 in the transmitting unit 32 in the processing module 24 of the device to device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention
  • FIG. 10 is a diagram of a device according to an embodiment of the present invention.
  • FIG. 11 is a structural block diagram of a user equipment according to an embodiment of the present invention
  • FIG. 12 is a device through system according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of D2D multicast/broadcast for different coverage scenarios according to an embodiment of the present invention;
  • FIG. 14 is a flowchart of a non-coverage scenario D2D multicast communication according to Example 1 of the present invention;
  • FIG. FIG. 16 is a flow chart of a non-coverage scenario D2D multicast communication according to Example 3 of the present invention;
  • FIG. 17 is a flow chart of a non-coverage scenario D2D multicast communication according to Example 4 of the present invention
  • 18 is a flow chart of a non-coverage scene D2D broadcast communication according to Example 5 of the present invention
  • FIG. 19 is a flow chart of a covered scene D2D multicast communication according to Example 6 of the present invention
  • 20 is a flow chart of a covered scene D2D multicast communication according to Example 7 of the present invention
  • FIG. 21 is a flowchart of a covered scene D2D multicast communication according to Example 8 of the present invention
  • FIG. 22 is a covered according to Example 9 of the present invention.
  • FIG. 23 is a flow chart of a covered scene D2D broadcast communication according to Example 10 of the present invention
  • FIG. 24 is a flowchart of a covered scene D2D broadcast communication according to Example 11 of the present invention; Partial coverage scenario D2D multicast communication flow diagram of Example 12. BEST MODE FOR CARRYING OUT THE INVENTION
  • FIG. 1 is a flowchart of a device-to-device D2D multicast/broadcast communication processing method according to an embodiment of the present invention, as shown in FIG.
  • Step S102 Obtain an air interface identifier for identifying a user equipment and/or a D2D multicast/broadcast communication, and resource information of the D2D multicast/broadcast communication; Step S104, corresponding to the resource information according to the air interface identifier
  • the D2D multicast/broadcast communication processing is performed on the resources.
  • the D2D multicast/broadcast communication processing is performed according to the air interface identifier of the D2D multicast/broadcast communication and/or the resource information of the D2D multicast/broadcast communication, and the related technology is adopted, where the UE has no coverage or coverage, and The problem of D2D multicast and broadcast communication cannot be realized in a partial coverage scenario, and the effect of enabling the UE to smoothly perform D2D multicast and broadcast communication without coverage or coverage and partial coverage scenarios is achieved.
  • the performing D2D multicast/broadcast communication processing on the resource corresponding to the resource information according to the air interface identifier may include: transmitting, according to the air interface identifier, the D2D multicast/broadcast communication data packet on the resource corresponding to the resource information; and/or, according to the air interface identifier The D2D multicast/broadcast communication data packet is received on the resource corresponding to the resource information.
  • Obtaining the air interface identifier for identifying the user equipment and/or the D2D multicast/broadcast communication may be performed in multiple manners.
  • At least one of the following manners may be adopted: obtaining an air interface identifier from the D2D application server; according to the first predetermined rule U, The air interface identifier is obtained by mapping the D2D multicast/broadcast application layer identifier to the air interface identifier. The air interface identifier is obtained by mapping the D2D multicast/broadcast IP address to the air interface identifier according to the second predetermined rule.
  • An air interface identifier is generated according to the D2D multicast/broadcast application layer identifier and/or the user equipment pass-through identifier; the air interface identifier is obtained from the neighboring node, wherein the neighboring node periodically broadcasts the message including the air interface identifier; An air interface identifier, where the central node is used to control D2D multicast/broadcast communication.
  • the method for obtaining the air interface identifier from the central node may be as follows: sending a D2D multicast/broadcast communication request including the user equipment pass-through identifier and/or the D2D multicast/broadcast application layer identifier to the central node; receiving the central node according to D2D multicast / The air interface identifier assigned by the broadcast communication request.
  • the air interface identifier is obtained from the central node by means of dedicated signaling and/or periodic broadcast, for example, including receiving an air interface identifier allocated by the central node according to the D2D multicast/broadcast communication request.
  • the resource information for obtaining the D2D multicast/broadcast communication may also be in multiple manners.
  • At least one of the following methods may be adopted: obtaining resource information from the D2D application server; acquiring default resource information of the system; acquiring resources by using a competitive manner.
  • Information acquiring resource information from a neighboring node, wherein the neighboring node periodically broadcasts a message including resource information; and acquiring resource information from a central node, wherein the central node is configured to control D2D multicast/broadcast communication.
  • the resource information can be obtained from the central node in the following manner: The resource information can also be obtained from the central node by using the dedicated signaling and/or periodic broadcast, for example,
  • the D2D multicast/broadcast communication request is sent to the central node; and the resource information of the resource allocated by the central node according to the D2D multicast/broadcast communication request is received.
  • the multicast/broadcast communication request may include at least one of the following: D2D multicast/broadcast application layer identifier, user equipment pass-through identifier, D2D multicast/broadcast IP address, multicast/broadcast communication indication, D2D multicast/ Broadcast priority, one or more multicast/broadcast traffic flow quality of service QoS information.
  • the resource information of the resource allocated by the central node according to the D2D multicast/broadcast communication request may be adopted as follows Processing: receiving a multicast/broadcast communication confirmation message sent by the central node, where the central node performs admission control according to one or more multicast/broadcast communication service flow quality of service QoS information included in the multicast/broadcast communication request, and determines the accepted The multicast/broadcast communication service flow, the multicast/broadcast communication confirmation message includes at least one of the following: resource information of the resource allocated by the central node, and accepted multicast/broadcast communication service flow.
  • the foregoing resource information may include multiple types of information, for example, at least one of the following: frequency information of multicast/broadcast communication, frequency band resource information of multicast/broadcast communication, and multicast/broadcast communication Frame offset information, subframe offset information for multicast/broadcast communication, subframe mode information for multicast/broadcast communication, slot information for multicast/broadcast communication, resource block information for multicast/broadcast communication, multicast Resource repetition period information of the broadcast communication, D2D multicast/broadcast air interface identifier corresponding to the resource information, and air interface identification information of the user equipment transmitting the D2D multicast broadcast communication data packet.
  • frequency information of multicast/broadcast communication frequency band resource information of multicast/broadcast communication
  • multicast/broadcast communication Frame offset information subframe offset information for multicast/broadcast communication
  • subframe mode information for multicast/broadcast communication subframe mode information for multicast/broadcast communication
  • slot information for multicast/broadcast communication resource block information for multicast
  • the resource configuration information of the resource corresponding to the resource information may include at least one of the following: a resource bearer identifier, a media access control MAC configuration information, a radio link control RLC configuration information, a packet data convergence protocol PDCP configuration information, a logical channel Configuration information.
  • a resource bearer identifier a media access control MAC configuration information
  • a radio link control RLC configuration information a packet data convergence protocol PDCP configuration information
  • a logical channel Configuration information logical channel Configuration information.
  • sending, by the air interface identifier, the D2D multicast/broadcast communication data packet on the resource corresponding to the resource information including: transmitting, by the resource, at least one of a user equipment air interface identifier, a D2D multicast/broadcast air interface identifier, and a D2D multicast/broadcast indication D2D multicast/broadcast communication packet.
  • the D2D multicast/broadcast communication data packet carrying at least one of the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication may be sent on the resource by using at least one of the following manners:
  • the media access control MAC sub-header and/or the control unit of the D2D multicast/broadcast communication data packet, or the radio link control RLC sub-header, or the packet data convergence protocol PDCP sub-header carries the user equipment air interface identifier
  • the D2D group A D2D multicast carrying at least one of a user equipment air interface identifier, a D2D multicast/broadcast air interface identifier, and a D2D multicast/broadcast indication is transmitted on the resource in a manner of at least one of a broadcast/broadcast air interface identifier and a D2D multicast/broadcast indication.
  • D2D multicast/broadcast communication data packet scrambling D2D multicast/broadcast communication resource allocation control information and/or data packet by using at least one of user equipment air interface identifier, D2D multicast/broadcast air interface identifier, D2D multicast/broadcast indication
  • the D2D multicast/broadcast communication number carrying at least one of the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication is sent on the resource.
  • the resource location used by the D2D multicast/broadcast communication packet implicitly carries the user device air interface identifier
  • a D2D carrying at least one of a user equipment air interface identifier, a D2D multicast/broadcast air interface identifier, and a D2D multicast/broadcast indication is transmitted on the resource in a manner of at least one of a D2D multicast/broadcast air interface identifier and a D2D multicast/broadcast indication.
  • the multicast/broadcast communication data packet wherein the resource location used for transmitting the D2D multicast/broadcast communication data packet corresponds to at least one of a user equipment air interface identifier, a D2D multicast/broadcast air interface identifier, and a D2D multicast/broadcast indication.
  • Receiving the D2D multicast/broadcast communication data packet on the resource corresponding to the resource information according to the air interface identifier includes: determining, according to the D2D multicast/broadcast air interface identifier, whether the receiver of the D2D multicast/broadcast communication data packet belongs to the multicast corresponding to the air interface identifier/ Broadcast communication group; when the determination result is YES, the D2D multicast/broadcast communication data packet is parsed, and the parsed data packet is sent to the upper layer; and/or, if the determination result is negative, Discard D2D multicast/broadcast communication packets.
  • a device-to-device D2D multicast/broadcast communication processing device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again.
  • the term "module" may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable.
  • 2 is a structural block diagram of a device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention. As shown in FIG. 2, the apparatus includes an acquisition module 22 and a processing module 24. The apparatus will be described below.
  • the obtaining module 22 is configured to obtain an air interface identifier for identifying the user equipment and/or the D2D multicast/broadcast communication, and resource information of the D2D multicast/broadcast communication.
  • the processing module 24 is connected to the obtaining module 22, and is configured as The air interface identifier performs D2D multicast/broadcast communication processing on the resource corresponding to the resource information.
  • 3 is a processing module in a device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention
  • a preferred block diagram of 24, as shown in Figure 3, includes a transmitting unit 32 and/or a receiving unit 34, the apparatus being described below.
  • the sending unit 32 is configured to send the D2D multicast/broadcast communication data packet on the resource corresponding to the resource information according to the air interface identifier
  • the receiving unit 34 is configured to receive the D2D multicast/broadcast communication data on the resource corresponding to the resource information according to the air interface identifier. package.
  • FIG. 4 is a block diagram of a preferred structure of the acquisition module 22 in the device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention. As shown in FIG. 4, the acquisition module 22 includes at least one of the following: 41.
  • the acquiring module 22 is described below.
  • the first obtaining unit 41 is configured to obtain an air interface identifier from the D2D application server.
  • the second obtaining unit 42 is configured to obtain the air interface identifier by mapping the D2D multicast/broadcast application layer identifier to the air interface identifier according to the first predetermined rule.
  • the third obtaining unit 43 is configured to obtain the air interface identifier by mapping the D2D multicast/broadcast IP address to the air interface identifier according to the second predetermined rule.
  • the fourth obtaining unit 44 is configured to obtain the default air interface identifier of the system.
  • the unit 45 is configured to generate an air interface identifier according to the D2D multicast/broadcast application layer identifier and/or the user equipment pass-through identifier.
  • the fifth obtaining unit 46 is configured to obtain an air interface identifier from the neighboring node, where the neighboring node periodically broadcasts the The air interface identifies the message;
  • the sixth obtaining unit 47 is configured to obtain the air interface identifier from the central node, where the central node is used to control the D2D multicast/broadcast communication.
  • 5 is a block diagram of a preferred structure of the fifth obtaining unit 46 in the acquiring module 22 of the device-to-device D2D multicast/broadcast communication processing apparatus according to the embodiment of the present invention. As shown in FIG.
  • the fifth obtaining unit 46 includes the first The transmitting subunit 52 and the first receiving subunit 54 are described below.
  • the first sending subunit 52 is configured to send a D2D multicast/broadcast communication request including the user equipment pass-through identifier and/or the D2D multicast/broadcast application layer identifier to the central node;
  • the first receiving sub-unit 54 is connected to the first The sending subunit 52 is configured to receive the air interface identifier allocated by the central node according to the D2D multicast/broadcast communication request.
  • 6 is an acquisition module in a device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention.
  • the acquiring module 22 includes at least one of the following: a seventh obtaining unit 61, an eighth obtaining unit 62, a ninth obtaining unit 63, a tenth obtaining unit 64, and an eleventh
  • the obtaining unit 65, the acquisition module 22 will be described below.
  • the seventh obtaining unit 61 is configured to acquire the resource information from the D2D application server; the eighth obtaining unit 62 is configured to acquire the default resource information of the system; the ninth obtaining unit 63 is configured to acquire the resource information in a competitive manner;
  • the unit 64 is configured to acquire the resource information from the neighboring node, where the neighboring node periodically broadcasts the message including the resource information;
  • the eleventh acquiring unit 65 is configured to acquire the resource information from the central node, where the central node is used to D2D multicast/broadcast communication is controlled.
  • FIG. 7 is a block diagram showing a preferred structure of the eleventh obtaining unit 65 in the acquiring module 22 of the device-to-device D2D multicast/broadcast communication processing apparatus according to the embodiment of the present invention.
  • the eleventh obtaining unit 65 includes The second transmitting subunit 72 and the second receiving subunit 74, the following description of the first obtaining unit 65 will be described.
  • the second sending subunit 72 is configured to send a D2D multicast/broadcast communication request to the central node;
  • the second receiving subunit 74 is connected to the second sending subunit 72, and is configured to receive the central node according to the D2D multicast/broadcast communication.
  • the resource information of the resource requesting the allocation. 8 is a block diagram showing a preferred structure of a transmitting unit 32 in a processing module 24 in a device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention. As shown in FIG.
  • the transmitting unit 32 includes a third transmitting sub-unit 82.
  • the third transmitting subunit 82 will be described below.
  • the third sending sub-unit 82 is configured to send, on the resource, a D2D multicast/broadcast communication data packet carrying at least one of a user equipment air interface identifier, a D2D multicast/broadcast air interface identifier, and a D2D multicast/broadcast indication.
  • 9 is a block diagram showing a preferred structure of a third transmitting sub-unit 82 in the transmitting unit 32 of the processing module 24 in the device-to-device D2D multicast/broadcast communication processing apparatus according to an embodiment of the present invention. As shown in FIG. 9, the third sending is shown in FIG.
  • the subunit 82 includes at least one of the following: a first transmission sub-sub-unit 92, a second transmission sub-sub-unit 94, and a third transmission sub-sub-unit 96.
  • the third transmission sub-unit 82 will be described below.
  • the first transmission sub-subunit 92 is configured to pass media access control in the D2D multicast/broadcast communication packet
  • the MAC sub-header and/or the control unit, or the radio link control RLC sub-header, or the packet data convergence protocol PDCP sub-head carries the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication at least In one mode, a D2D multicast/broadcast communication packet carrying at least one of a user equipment air interface identifier, a D2D multicast/broadcast air interface identifier, and a D2D multicast/broadcast indication is sent on the resource; the second sending sub-subunit 94,
  • the method is configured to perform scrambling on the D2D multicast/broadcast communication resource allocation control information and/or the data packet by using at least one of the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication.
  • the third sending sub-subunit 96 is configured to send the D2D group
  • the resource location used by the broadcast/broadcast communication packet implicitly carries at least one of the user equipment air interface identifier, the D2D multicast/broadcast air interface identifier, and the D2D multicast/broadcast indication.
  • FIG. 10 is a block diagram showing a preferred structure of the receiving unit 34 in the processing module 24 in the device-to-device D2D multicast/broadcast communication processing apparatus according to the embodiment of the present invention. As shown in FIG.
  • the receiving unit 34 includes: a determining sub-unit 102, The parsing subunit 104 and/or the discarding subunit 106 are described below.
  • the determining subunit 102 is configured to determine, according to the D2D multicast/broadcast air interface identifier, whether the receiver of the D2D multicast/broadcast communication data packet belongs to a multicast/broadcast communication group corresponding to the air interface identifier; the parsing subunit 104 is connected to the foregoing determining
  • the unit 102 is configured to, if the determination result of the determining subunit 102 is YES, parse the D2D multicast/broadcast communication data packet, and send the parsed data packet to the upper layer; and/or discard the subunit 106.
  • FIG. 11 is a structural block diagram of a user equipment according to an embodiment of the present invention.
  • the user equipment 112 includes the D2D multicast/broadcast communication processing apparatus 114 of any of the above.
  • D2D technology can work in licensed or unlicensed bands, allowing multiple D2D-enabled user equipment (D2D User Equipment, D2D UE) to directly discover without network infrastructure or network infrastructure. / Direct communication.
  • FIG. 12 is a schematic diagram of a communication mode of a device through-system according to an embodiment of the present invention. As shown in FIG. 12, there are three main application scenarios of the D2D:
  • UE1 and UE2 perform data interaction under the coverage of the cellular network, and the user plane data does not pass through the network infrastructure, as shown in mode 1 of FIG. 1;
  • D2D communication in public security scenarios includes the following types: unicast, multicast, and broadcast.
  • Unicast refers to a one-to-one communication mode between D2D user equipments
  • multicast and broadcast are one-to-many communication modes for D2D user equipment.
  • Unicast communication can be regarded as a special form of multicast communication.
  • a D2D communication group contains only two user equipments.
  • D2D multicast communication is equivalent to unicast communication.
  • the communication requirements of public safety scenarios are highly robust, and can still provide maximum service in the event of current communication resources shortage or congestion or network infrastructure. Therefore, public safety requires that D2D communication not only work in a network coverage scenario, but also requires partial coverage and no network coverage scenarios.
  • the D2D user equipment can work in a self-organizing manner, or select some D2D user equipments as central nodes (CNs) in a non-coverage environment. These central nodes provide similar base station functions. .
  • CNs central nodes
  • FIG. 13 is a schematic diagram of D2D multicast/broadcasting for different coverage scenarios according to an embodiment of the present invention.
  • FIG. 13 a schematic diagram of D2D multicast broadcast communication in a public security scenario is given, wherein FIG. 13(a) is in FIG. The multicast broadcast communication between the D2D user equipments in the non-coverage scenario, and FIG. 13(b) is the multicast broadcast communication between the D2D user equipments in the coverage scenario or without the network coverage but in the CN scenario.
  • the CN here can be There is an e B in the coverage scenario, or it can be played by the D2D user equipment in the uncovered scenario.
  • FIG. 13 a schematic diagram of D2D multicast broadcast communication in a public security scenario is given, wherein FIG. 13(a) is in FIG. The multicast broadcast communication between the D2D user equipments in the non-coverage scenario, and FIG. 13(b) is the multicast broadcast communication between the D2D user equipments in the coverage scenario or without the network coverage
  • 13(c) shows a scenario in which a part of the D2D user equipment performing group communication is covered by the central node, and part of the D2D user equipment is not covered by the central node.
  • a method for establishing a D2D broadcast/multicast communication when a UE has no coverage or coverage and partial coverage in a public security scenario is provided, by using the D2D broadcast/multicast communication establishment method and In the system, the user equipment can quickly and flexibly establish D2D multicast and broadcast communication through simple processes in various scenarios such as network coverage and no network coverage and partial network coverage to ensure smooth multicast and broadcast communication.
  • the D2D multicast and broadcast communication establishment method includes: the user equipment acquires an air interface identifier and resource information of the D2D multicast/broadcast communication; and the user equipment uses the air interface identifier to send/receive a D2D multicast/broadcast communication data packet on the resource.
  • the user equipment referred to above includes: a first user equipment that initiates D2D multicast/broadcast communication, and a second user equipment that receives D2D multicast/broadcast communication; the second user equipment involves one or more and the first The user equipment is adjacent to the user equipment; the air interface identifier refers to the D2D multicast/broadcast communication identifier, where the multicast air interface identifier refers to all D2D multicast communication or a specific D2D multicast communication group (ie, a predetermined D2D group) that can be identified in the air interface. Broadcast communication group), and the broadcast air interface identifier can identify D2D broadcast communication in the air interface.
  • the user equipment can obtain the air interface identification information of the D2D multicast/broadcast communication in multiple manners. For example, the user equipment can obtain the air interface of the D2D multicast/broadcast that is added to the D2D application server.
  • the user equipment maps the D2D multicast application layer identifier to the air interface identifier of the D2D group according to the predefined rule; the user equipment acquires the IP multicast address of the joined D2D group from the D2D application server, and sets the IP address of the D2D group according to a predefined rule.
  • the multicast address is mapped to the air interface identifier of the D2D group.
  • the air interface identifier of the D2D group is generated according to the D2D multicast application layer identifier, and the D2D multicast application layer identifier and the air interface identifier are periodically broadcasted.
  • the mapping relationship between the D2D multicast application layer identifier and the air interface identifier periodically broadcasted by the first user equipment is obtained by the second user equipment, so as to obtain the air interface identifier of the D2D group; the user equipment obtains the default D2D multicast/broadcast communication in advance.
  • the foregoing central node may be a base station, or a user equipment that performs a central control function, and the central node does not participate in the transmission of multicast/broadcast data, and only performs signaling control of the corresponding control plane.
  • the user equipment obtains the air interface identifier of the D2D group from the central node, and may adopt the following simple processing manner, including: the first user equipment sends a D2D group communication request including the D2D application layer group identifier to the central node; and the central node receives the D2D group communication.
  • the central node will include the D2D group air interface identifier, or the D2D group air interface identifier and the D2D group application layer identifier through dedicated signaling and or periodic broadcast.
  • the message of the information is sent to the user equipment; the user equipment receives the message that the central node sends the D2D group air interface identification information.
  • the method further includes: the first user equipment wants to initiate D2D multicast communication.
  • the user equipment obtains the D2D broadcast air interface identifier from the central node, and may also adopt the following simple processing manner, including: the first user equipment sends a D2D broadcast communication request to the central node; the central node receives the D2D broadcast communication request, and allocates the D2D broadcast air interface identifier.
  • the central node may send the message including the D2D broadcast air interface identifier to the user equipment by using dedicated signaling and/or periodic broadcast; the user equipment receives the message that the central node sends the D2D broadcast air interface identifier information.
  • the user equipment may obtain the resource information of the D2D multicast/broadcast communication, and may also adopt multiple processing manners.
  • the user equipment acquires the D2D multicast/broadcast communication resource from the D2D application server.
  • the user equipment acquires the default D2D multicast/broadcast communication resource information of the system;
  • the first user equipment acquires the time-frequency resource for transmitting the multicast/broadcast communication data packet in a contention manner;
  • the user equipment acquires the D2D multicast/broadcast from the central node. Resource information for communication.
  • the user equipment may obtain the resource information of the D2D multicast/broadcast communication from the central node, and may also adopt the following simple processing, including: the first user equipment sends a multicast/broadcast communication request to the central node; and the central node receives the multicast/broadcast. After the communication request message, the air interface resource is allocated for the multicast/broadcast communication, and the message including the multicast/broadcast air interface resource information is sent to the user equipment; the user equipment receives the message including the multicast/broadcast air interface resource information.
  • the multicast/broadcast communication request message may include but is not limited to the following fields: D2D group identifier, multicast/broadcast communication indication, D2D Group priority, one or more multicast/broadcast communication service flow QoS information; wherein, the D2D group identifier may be at least one of the following: a D2D group application layer identifier, a D2D IP multicast address, and a system default D2D group air interface identifier.
  • the central node After receiving the multicast/broadcast communication request message, the central node allocates the air interface resource for the multicast/broadcast communication and sends the message containing the multicast/broadcast air interface resource information to the user equipment.
  • the multicast/broadcast can perform the following processing: The central node performs admission control on the multicast/broadcast communication request; the central node may determine the accepted multicast/broadcast communication service flow according to the multicast/broadcast communication service flow QoS information included in the multicast/broadcast communication request message.
  • the central node may send: the central node sends a multicast/broadcast communication confirmation message to the first user equipment, where the multicast/broadcast communication confirmation message may be Contains resources allocated to multicast/broadcast communications and/or accepted traffic flow information.
  • the central node sends a message including the multicast/broadcast air interface resource information to the user equipment, different central transmission information may be used to send different resource information.
  • the central node may send multicast/broadcast by means of periodic broadcast.
  • the sub-frame mode information corresponding to the communication; the central node may broadcast and transmit the resource information including the multicast/broadcast communication, where the multicast/broadcast air interface resource information may include any combination of the following fields: Frequency of the multicast/broadcast communication , band resource, frame/subframe offset, subframe mode, time slot, resource block, resource repetition period, etc.; the resource information of the multicast/broadcast communication includes at least one of the following: corresponding D2D group air interface identifier / D2D broadcast The air interface identifier and the identification information of the first user equipment.
  • resource information including multicast/broadcast communication sent by the central node may also be periodically sent.
  • the method includes: the first user equipment sends the D2D multicast/broadcast communication data packet on the resource, and the data packet implicitly or explicitly carries the D2D a group air interface identifier/D2D broadcast identifier; the second user equipment receives the D2D multicast data packet in the resource, and determines whether further analysis is needed according to the D2D group air interface identifier, and further performs MAC/RLC/PDCP parsing processing and delivers to the upper layer if necessary, otherwise The data packet is discarded; or the second user equipment sends the D2D broadcast communication data packet to the upper layer after completing the MAC/RLC/PDCP layer analysis processing.
  • the data packet implicitly or explicitly carries the D2D group air interface identifier/D2D broadcast identifier, including: the D2D multicast/broadcast that the first user equipment sends
  • the communication data packet carries at least one of the following: D2D group air interface identifier / D2D broadcast identifier, D2D multicast/broadcast indication.
  • the D2D group air interface identifier/D2D broadcast identifier may be carried in the following manner: at least one of the following may be carried in the MAC/RLC/PDCP sub-header of the D2D multicast/broadcast communication data packet: D2D group air interface identifier/D2D Broadcast identifier, D2D multicast/broadcast indication field; D2D multicast/broadcast communication data packet sent by the first user equipment is scrambled using the D2D group air interface identifier/D2D broadcast identifier; D2D multicast/broadcast sent by the first user equipment
  • the communication data packet uses the resource corresponding to the D2D group air interface identifier/D2D broadcast identifier allocated by the central node, and the D2D multicast/broadcast communication data packet implicitly carries the D2D group air interface identifier/D2D broadcast identifier information by using the resource location used for sending the data packet.
  • the second user equipment Before receiving the D2D multicast/broadcast communication data packet, the second user equipment further includes: the second user equipment is interested in receiving the D2D multicast/broadcast, and obtains the D2D multicast/broadcast air interface identifier and resource information; The user equipment receives the D2D multicast data packet in the resource, determines whether the further analysis is needed according to the D2D group air interface identifier, performs MAC/RLC/PDCP parsing processing if necessary, and delivers the data to the upper layer, otherwise discards the data packet. It should be noted that, if the second user equipment is a member of the D2D group corresponding to the D2D group air interface identifier, the second user equipment needs to parse the data packet.
  • the D2D multicast and broadcast communication establishment may take the air interface identification and resource information of the D2D multicast/broadcast communication of the user equipment, and then the user equipment uses the air interface label. The way to send/receive D2D multicast/broadcast communication packets on the resource is completed.
  • the user equipment can quickly and flexibly establish D2D multicast and broadcast communication in a scenario with coverage, no coverage, and partial coverage, thereby ensuring smooth multicast and broadcast communication.
  • Embodiment 1 This embodiment provides a method for establishing D2D multicast broadcast communication in a no-coverage scenario.
  • Example 1 In the public security scenario, Officer A, B, C, D use public safety UE1, UE2, UE3 and UE4 with D2D capabilities. Officer A, B, C, and D all subscribe to the public security service, and UE1, UE2, UE3 configurations belong to D2D communication group X, and UE4 belongs to D2D communication group Y.
  • FIG. 14 is a flowchart of a non-coverage scenario D2D multicast communication according to Example 1 of the present invention, as shown in FIG.
  • the transmitted data packet carries the pre-assigned D2D group identifier in the MAC control unit and/or the sub-header, or the RLC sub-header, or the PDCP sub-header.
  • the multicast communication data packet may carry the D2D multicast communication indication and the air interface identification information of the UE1 in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • UE2, UE3 and UE4 of Officer B, C, D listen to the public safety radio resources that are known in advance. It is assumed that UE2, UE3, and UE4 receive the data packet transmission, receive the data packet, and parse the MAC control unit and/or the sub-header, or the RLC sub-header, or the D2D group identifier of the PDCP sub-header. UE2 and UE3 determine that they belong to the D2D group corresponding to the D2D group identifier, and then UE2 and UE3 further perform MAC/RLC/PDCP parsing processing and deliver to the upper layer.
  • Example 2 In the public safety scenario, Officer A, B, C, D use public safety UE1, UE2, UE3 and UE4 with D2D capabilities. Officer A, B, C, and D all subscribe to the public security service, and UE1, UE2, UE3 configurations belong to D2D communication group X, and UE4 belongs to D2D communication group Y. Before the OfficeA, B, C, and D arrive at the rescue location, the D2D communication group application layer identifier GID and the wireless resource information for public security are known in advance, wherein the radio resource information may include frequency and frequency band information.
  • the UE After reaching the rescue location, the UE is not within the network coverage, but UE1, UE2, UE3, and UE4 are within the D2D communication range of each other.
  • OfficerA hopes to initiate a multicast communication and inform other Office related information in the group.
  • UE2, UE3, UE4 of Officer B, C, D want to be able to receive multicast information.
  • the UE2, UE2, UE3, and UE4 first map the D2D communication group application layer identifier GID to the D2D group air interface identifier according to a predefined rule, and then listen to the pre-allocated radio resource.
  • the UE 1 that wants to transmit data acquires resources in a contention manner.
  • the UE1 After competing to the resource, the UE1 broadcasts the multicast communication data, and the transmitted data packet is mapped to the D2D group air interface identifier according to a predefined rule in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • the multicast communication data packet may carry the D2D multicast communication indication and the air interface identification information of the UE1 in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • UE2, UE3 and UE4 of Officer B, C, D listen to pre-known public safety radio resources. It is assumed that UE2, UE3, and UE4 receive the data packet transmission, and then receive the data packet, and parse the MAC control unit and/or the sub-header, or the RLC sub-header, or the D2D group air interface identifier of the PDCP sub-header. UE2 and UE3 determine that the D2D air interface identifier is consistent with the D2D air interface identifier mapped by the D2D communication group to which the UE belongs, and then UE2 and UE3 further perform MAC/RLC/PDCP analysis processing and deliver to the upper layer.
  • the pre-defined mapping rule may generate different D2D communication group application layer identifiers mapped to the same D2D group air interface identifier. In this case, the UE may continue to pass the multicast address of the IP layer or the D2D carried by the application layer.
  • the group information is further used to determine whether the corresponding D2D communication group corresponds to whether the data packet is received or discarded by the upper layer.
  • Example 3 In the public security scenario, OfficerA, B, C, and D use public security UE1, UE2 with D2D capabilities.
  • Officer A, B, C, and D all subscribe to the public security service, and UE1, UE2, UE3 configurations belong to D2D communication group X, and UE4 belongs to D2D communication group Y.
  • the radio resource information may include frequency and frequency band information.
  • the UE is not within the network coverage, but UE1, UE2, UE3, and UE4 are within the D2D communication range of each other.
  • OfficerA hopes to initiate a multicast communication and inform other Office related information in the group.
  • FIG. 16 is a flowchart of the uncovered scenario D2D multicast communication according to Example 3 of the present invention, as shown in FIG. 16.
  • UE1 After competing to the resource, UE1 broadcasts the multicast communication data, and the transmitted data packet is mapped to the D2D group air interface identifier according to a predefined rule in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • the multicast communication data packet may carry the D2D multicast communication indication information and the air interface identifier of the UE1 in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • UE2, UE3 and UE4 of Officer B, C, D listen to the public safety radio resources that are known in advance. It is assumed that UE2, UE3, and UE4 receive the data packet transmission, and then receive the data packet, and parse the MAC control unit and/or the sub-header, or the RLC sub-header, or the D2D group air interface identifier of the PDCP sub-header. UE2 and UE3 determine that the D2D air interface identifier is consistent with the D2D air interface identifier mapped by the D2D communication group to which the UE belongs, and then UE2 and UE3 further perform MAC/RLC/PDCP analysis processing and deliver to the upper layer.
  • This pre-defined mapping rule may generate different IP multicast addresses of D2D communication groups to be mapped to the same D2D group air interface identifier. In this case, the UE may continue to determine whether it is through the IP address of the IP layer. Corresponding to the correct D2D communication group, it is up to the higher layer to determine whether to receive the packet or discard it.
  • Officer A, B, C, D use public safety UE1, UE2, UE3 and UE4 with D2D capabilities.
  • Officer A, B, C, and D all subscribe to the public security service, and UE1, UE2, UE3 configurations belong to D2D communication group X, and UE4 belongs to D2D communication group Y.
  • the D2D communication group application layer identifier GID and the wireless resource information for public security are known in advance, wherein the radio resource information may include frequency and frequency band information.
  • the UE is not within the network coverage, but UE1, UE2, UE3, and UE4 are within the D2D communication range of each other.
  • OfficerA wants to initiate multicast communication and inform other Office related information in the group.
  • FIG. 17 is a diagram according to Example 4 of the present invention. Cover the scenario D2D multicast communication flow chart, as shown in Figure 17.
  • the UE2, UE3, and UE4 listen to the pre-allocated radio resources, obtain the mapping information of the D2D communication group application layer identifier GID and the D2D group air interface identifier, and then determine whether they also join the D2D communication group application layer identifier GID corresponding group, if yes
  • the mapping information of the D2D communication group application layer identifier GID and the D2D group air interface identifier is saved.
  • the UE1 broadcasts the multicast communication data after competing for the resource, and the transmitted data packet carries the generated D2D in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • Group air interface identification the multicast communication data packet may carry the D2D multicast communication indication information and the air interface identifier of the UE1 in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • UE2, UE3 and UE4 of Officer B, C, D listen to pre-known public safety radio resources. It is assumed that UE2, UE3, and UE4 receive the data packet transmission, and then receive the data packet, and parse the MAC control unit and/or the sub-header, or the RLC sub-header, or the D2D group air interface identifier of the PDCP sub-header. UE2 and UE3 determine that the D2D air interface identifier is consistent with the D2D air interface identifier corresponding to the D2D communication group to which the UE belongs, and then UE2 and UE3 further perform MAC/RLC/PDCP analysis processing and deliver to the upper layer.
  • the UE4 For UE4, it is determined that it does not belong to the member of the D2D group corresponding to the D2D group identifier, and therefore the data packet is discarded.
  • the manner in which the UE generates the D2D group air interface identifier by itself may generate different UEs to map different D2D communication group application layer identifiers to the same D2D group air interface identifier. In this case, the UE may continue to pass the multicast communication data.
  • the air interface identifier of the UE1 carried by the packet, or the multicast address of the IP layer or the D2D group information carried by the application layer, is further determined whether the corresponding D2D communication group is corresponding, and the higher layer determines whether the data packet is received or discarded.
  • the air interface identifier of the transmitting UE is used for judging processing of subsequent multicast communication data packet reception.
  • OfficerA, B, C, and D use public safety UE1, UE2, UE3, and UE4 with D2D capabilities.
  • Officer A, B, C, and D all subscribe to the public security service, and UE1, UE2, and UE3 are configured to belong to D2D communication group X, and UE4 belongs to D2D communication group Y.
  • the D2D broadcast communication identifier BID and the wireless resource information for public safety are known in advance, and the radio resource information may include frequency and frequency band information.
  • the UE is not within the network coverage, but UE1, UE2, UE3, and UE4 are within the D2D communication range of each other.
  • Officer A wishes to initiate a broadcast communication to inform other officers of the group about the information. then
  • FIG. 18 A flowchart of a non-coverage scenario D2D broadcast communication according to Example 5 of the present invention is shown in FIG. After competing for the resource, UE1 broadcasts a data packet, the transmitted data packet is in the MAC control unit and/or the sub-header, or the RLC sub-header, or the PDCP sub-header carries the pre-assigned D2D broadcast communication identifier BID.
  • the broadcast communication data packet may carry the D2D broadcast communication indication and the air interface identification information of the UE1 in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • UE2, UE3 and UE4 of Officer B, C, D listen to pre-known public safety radio resources. It is assumed that UE2, UE3, and UE4 receive the data packet transmission, receive the data packet, and parse the MAC control unit and/or the sub-header, or the RLC sub-header, or the D2D broadcast communication identifier of the PDCP sub-header, and determine that it is broadcast communication. Then, MAC/RLC/PDCP analysis processing is further performed and delivered to the upper layer.
  • Embodiment 2 provides a method for establishing D2D multicast broadcast communication in a scenario with a central node coverage.
  • the feature of this embodiment is that there is a central node for resource coordination and allocation of D2D multicast/broadcast air interface identifiers.
  • the central node may be e B, or may be an ordinary UE that performs the resource and identity allocation that the UE acts as.
  • This embodiment can be used in public security scenarios as well as in commercial scenarios. The following is explained in detail by way of Example 6 to Example 9.
  • Example 6 In the public security scenario, OfficerA, B, C, and D use public safety UE1, UE2, UE3, and UE4 with D2D capabilities.
  • Officer A, B, C, and D all subscribe to the public security service, and UE1, UE2, and UE3 are configured to belong to D2D communication group X, and UE4 belongs to D2D communication group Y.
  • the D2D communication group application layer identifier is known in advance. After arriving at the rescue location, the UE is within the network coverage or although there is no network coverage but within the selected central node coverage, and UE1, UE2, UE3, UE4 are within the D2D communication range of each other.
  • Officer A wishes to initiate a multicast communication and inform other officers of the group about the information.
  • the UE1 of the OfficeA first sends a group communication request message to the CN/e B, the message includes the pre-acquired allocated D2D communication group application layer identifier, and FIG. 19 is a flowchart of the coverage scenario D2D multicast communication according to the example 6 of the present invention.
  • the group communication request message may further include a communication group priority, QoS information of one or more multicast service flows, and the like.
  • the CN/eNB node After receiving the message, the CN/eNB node performs admission control, determines the accepted multicast/broadcast communication service flow according to the multicast communication service flow QoS information included in the multicast communication request message, and allocates the group communication air interface identifier and Air interface resource configuration. If the traffic flow needs to last for a period of time, such as voice or video, the CN/eNB can assign a semi-static resource schedule to it.
  • the group communication confirmation message is sent to the UE1, which includes the received service flow, the assigned group communication air interface identifier, and the air interface resource and configuration information allocated to the multicast communication.
  • the multicast air interface resource information includes any combination of the following fields: frequency of multicast communication, band resource, frame/subframe offset, subframe mode, time slot, resource block, resource repetition period, and the like.
  • resource configuration information of the corresponding resource such as resource bearer identifier, media access control MAC configuration information, radio link control RLC configuration information, packet data convergence protocol PDCP configuration information, and logical channel configuration information.
  • the CN/eNB periodically broadcasts the mapping information of the D2D communication group application layer identifier and the group communication air interface identifier, and the subframe mode information corresponding to the multicast communication.
  • resource configuration information of the corresponding resource such as a resource bearer identifier, a medium access control MAC configuration information, a radio link control RLC configuration information, a packet data convergence protocol PDCP configuration information, and a logical channel configuration information, may be broadcasted.
  • UE1, UE2, UE3, and UE4 receive mapping information of the periodically broadcasted D2D communication group application layer identifier GID and the group communication air interface identifier.
  • UE2 and UE3 determine that the received D2D communication group application layer identifier is consistent with the pre-known D2D communication group application layer identifier, and UE2 and UE3 maintain the mapping of the D2D communication group application layer identifier and the group communication air interface identifier, and the subframe corresponding to the multicast communication.
  • the mode and resource configuration information are configured accordingly according to the resource configuration information.
  • the UE1 sends a D2D multicast communication data packet on the resource allocated by the CN/eNB, and the data packet can carry the D2D group air interface identifier.
  • UE1 may carry a D2D group air interface identifier and/or a D2D multicast indication field in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • the D2D multicast communication packet sent by UE1 is scrambled by using the D2D group air interface identifier.
  • the D2D multicast communication data packet sent by the UE1 uses the resource corresponding to the D2D group air interface identifier allocated by the CN/eNB, and the D2D multicast communication data packet implicitly carries the D2D group air interface identifier information by using the resource location used for sending the data packet.
  • UE2, UE3 and UE4 are interested in receiving D2D multicast, and UE2 and UE3 have acquired the D2D group air interface identifier of D2D communication group X.
  • the UE2 and the UE3 listen to the corresponding subframe and receive the D2D multicast data packet according to the subframe mode information corresponding to the previously acquired multicast communication. If the D2D multicast packet is received, the D2D air interface identifier corresponding to the D2D multicast packet is further determined according to the scrambling situation, the resource location or the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader. .
  • UE2 and UE3 complete the MAC/RLC/PDCP parsing process and deliver to the upper layer.
  • Example 7 In the public safety scenario, Officer A, B, C, D use public safety UE1, UE2, UE3 and UE4 with D2D capabilities. Officers A, B, C, and D all subscribe to the public security service, and UE1, UE2, and UE3 are all configured to belong to D2D communication group X, and UE4 belongs to D2D communication group Y. Before the Office A, B, C, D arrives at the rescue location, the D2D communication group application layer identifier GID is known in advance.
  • FIG. 20 is a flow chart of the covered scene D2D multicast communication according to Example 7 of the present invention. , as shown in Figure 20.
  • the group communication request message may further include a communication group priority, QoS information of one or more multicast service flows, and the like.
  • the CN/eNB node After receiving the message, the CN/eNB node performs admission control, determines the accepted multicast communication service flow according to the multicast communication service flow QoS information included in the multicast communication request message, and allocates the group communication air interface identifier and the air interface resource configuration. After the CN/eNB completes the admission control and the resource allocation, the group communication confirmation message is sent to the UE1, and the group communication confirmation message may include the accepted service flow information. In addition, the CN/eNB periodically broadcasts the mapping information of the D2D communication group application layer identifier and the group communication air interface identifier.
  • UE1, UE2, UE3, and UE4 receive mapping information of the periodically broadcasted D2D communication group application layer identifier and the group communication air interface identifier.
  • UE2 and UE3 determine that the received D2D communication group application layer identifier is consistent with the pre-known D2D communication group application layer identifier, and UE2 and UE3 maintain mapping information of the D2D communication group application layer identifier and the group communication air interface identifier.
  • the CN/eNB broadcasts the scheduling information including the D2D group communication resource allocation, and the scheduling information may include the indication information of the transmitting UE1.
  • UE2, UE3 monitors and receives the D2D multicast data packet on the detected resource allocation corresponding to the D2D communication group X, completes the MAC/RLC/PDCP parsing process, and delivers it to the upper layer.
  • Example 8 In the public safety scenario, Officer A, B, C, D use public safety UE1, UE2, UE3 and UE4 with D2D capabilities. Officer A, B, C, D are all subscribed to public safety services, and UE1, UE2, UE3 are both The configuration belongs to the D2D communication group X, and the UE4 belongs to the D2D communication group Y. Before the Office A, B, C, D arrives at the rescue location, the D2D communication group application layer identifier GID is known in advance.
  • the UE After arriving at the rescue location, the UE is within the network coverage or although there is no network coverage but within the selected central node coverage, and UE1, UE2, UE3, UE4 are within the D2D communication range of each other.
  • Officer A hopes to initiate a multicast communication and inform other Office related information in the group. then
  • FIG. 21 is a flowchart of the coverage scenario D2D multicast communication according to the eighth embodiment of the present invention. As shown in Figure 21.
  • the CN/eNB node After receiving the message, the CN/eNB node performs admission control and allocates a group communication air interface identifier and an air interface resource configuration. If the traffic flow needs to last for a period of time, such as voice or video, the CN/eNB can assign a semi-static resource schedule to it.
  • the CN/eNB After completing the admission control and resource allocation, the CN/eNB sends a group communication confirmation message to the UE1.
  • the CN/eNB periodically broadcasts the mapping information of the D2D communication group application layer identifier GID and the group communication air interface identifier and the D2D multicast communication resource that is not specific to the UE.
  • the multicast air interface resource information includes any combination of the following fields: frequency of multicast communication, band resource, frame/subframe offset, subframe mode, time slot, resource block, resource repetition period, and so on.
  • UE1, UE2, UE3, and UE4 receive mapping information of the D2D communication group application layer identifier and the group communication air interface identifier that are periodically broadcasted.
  • UE1, UE2, and UE3 determine that the received D2D communication group application layer identifier is consistent with the pre-known D2D communication group application layer identifier, and UE1, UE2, and UE3 maintain mapping information of the D2D communication group application layer identifier and the group communication air interface identifier, and the D2D group. Broadcast communication air interface resource information.
  • the UE1 then listens to the D2D multicast communication radio resource usage that is not allocated to the specific UE by the CN/eNB, and acquires the resources in a competitive manner.
  • the UE1 After competing to the resource, the UE1 broadcasts the multicast communication data, and the transmitted data packet carries the pre-assigned D2D group identifier in the MAC control unit and/or the sub-header, or the RLC sub-header, or the PDCP sub-header.
  • the multicast communication data packet may carry the D2D multicast communication indication and the air interface identification information of the UE1 in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • the UE2 of the Officer B, C, D, the UE3 monitors the radio resource according to the acquired D2D multicast communication radio resource information that is not specific to the UE.
  • UE2, UE3, receives the data packet transmission, receives the data packet, and parses the MAC control unit and/or the sub-header, or the RLC sub-header, or the D2D group identifier of the PDCP sub-header.
  • UE2 and UE3 determine that they belong to the D2D group corresponding to the D2D group identifier, and UE2 and UE3 further perform MAC/RLC/PDCP parsing processing and deliver to the upper layer.
  • Example 9 In the public safety scenario, Officer A, B, and C use public safety UE1, UE2, UE3 with D2D capabilities. Officers A, B, and C are all subscribed to public safety services.
  • the UE After arriving at the rescue location, the UE is within the network coverage or although there is no network coverage but within the selected central node coverage, and UE1, UE2, UE3 are within D2D communication range of each other.
  • Officer A wants to initiate a broadcast communication to inform other Office related information, then Office
  • the UE1 of A first transmits a broadcast communication request message to the CN/e B, the message containing QoS information that may include the communication group priority, one or more broadcast service flows, etc., and FIG. 22 is a covered scene D2D according to Example 9 of the present invention.
  • the multicast communication flow chart is shown in Figure 22.
  • the CN/e B node After receiving the message, the CN/e B node performs admission control, allocates the broadcast communication air interface identifier, and the air interface resource configuration. If the traffic flow needs to last for a period of time, such as voice or video, the CN/eNB can assign a semi-static resource schedule to it.
  • the CN/eNB After completing the admission control and the resource allocation, the CN/eNB sends a broadcast communication confirmation message to the UE1, which includes the received service flow, the allocated broadcast communication air interface identifier, and the air interface resource allocated to the broadcast communication.
  • the broadcast air interface resource information includes any combination of the following fields: frequency of broadcast communication, band resource, frame/subframe offset, subframe mode, time slot, resource block, resource repetition period, and so on.
  • the CN/eNB periodically broadcasts the broadcast communication air interface identifier and the subframe mode information corresponding to the broadcast communication.
  • UE1, UE2, and UE3 hold the broadcast communication air interface identifier that receives the periodic broadcast and the broadcast communication subframe mode information.
  • the UE1 sends a D2D broadcast communication data packet on the resource allocated by the CN/eNB, and the data packet can carry the D2D broadcast air interface identifier.
  • the data packet can carry the D2D broadcast air interface identifier.
  • UE1 may carry a D2D broadcast identifier and or a D2D broadcast indication field in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • the D2D broadcast communication packet sent by UE1 is scrambled using the D2D broadcast air interface identifier.
  • UE2 and UE3 are interested in receiving D2D broadcast, and UE2 and UE3 have acquired the D2D broadcast air interface identifier.
  • the UE2 and the UE3 monitor the corresponding subframe according to the subframe mode information corresponding to the previously acquired broadcast communication and receive the D2D broadcast data packet. If the data packet is received, it is further determined according to the scrambling condition or the MAC control unit and/or the sub-header, or the RLC sub-header, or the broadcast air port identifier protected by the PDCP sub-header, whether the data packet corresponds to the broadcast packet, and if Then, UE2 and UE3 complete the parsing process of MAC/RLC/PDCP and deliver it to the upper layer.
  • Example 10 In the public safety scenario, Officer A, B, and C use public safety UE1, UE2, UE3 with D2D capabilities. Officers A, B, and C are all subscribed to public safety services. Before Office A, B, and C arrive at the rescue location, the D2D broadcast communication air interface identification information is known in advance. After arriving at the rescue location, the UE is within the network coverage or although there is no network coverage but within the selected central node coverage, and UE1, UE2, UE3 are within D2D communication range of each other. At the rescue location, Officer A hopes to initiate a broadcast communication to inform other Office related information in the group. Then, UE1 of Office A first sends a broadcast communication request message to CN/e B, and FIG.
  • Example 23 is a flowchart of broadcast communication with coverage scene D2D according to Example 10 of the present invention.
  • the CN/eNB node receives the message. , perform admission control, and assign and or adjust broadcast communication air interface resource configuration. After completing the admission control and resource allocation, the CN/eNB sends a broadcast communication confirmation message to the UE1.
  • the CN/eNB sends a broadcast communication confirmation message to the UE1.
  • the CN/eNB periodically broadcasts D2D broadcast communication resources that are not directed to a particular UE.
  • the broadcast air interface resource information includes any combination of the following fields: frequency of broadcast communication, band resource, frame/subframe offset, subframe mode, time slot, resource block, resource repetition period, and so on.
  • UE1, UE2, and UE3 receive and save the periodically broadcasted D2D broadcast communication resource information. Then, the UE1 monitors the use of the D2D broadcast communication radio resource allocated by the CN/eNB and does not target the specific UE, and acquires the resource in a competitive manner.
  • UE1 After competing to the resource, UE1 broadcasts the broadcast communication data, and the transmitted data packet is carried in the MAC control unit and/or the sub-header, or the RLC sub-header, or the PDCP sub-header carries the pre-assigned D2D broadcast air interface identifier.
  • the broadcast communication data packet may carry the D2D broadcast communication indication and the air interface identification information of the UE1 in the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader.
  • UE2, UE3 monitors the radio resource according to the acquired D2D broadcast communication radio resource information that is not specific to the UE.
  • UE3 receives the data packet transmission, receives the data packet, parses the MAC control unit and/or the sub-header, or the RLC sub-header, or the D2D broadcast air interface identifier of the PDCP sub-header, and further performs MAC/RLC/PDCP analysis. Processed and delivered to the top.
  • Embodiment 3 provides a method for establishing D2D multicast broadcast communication in a partial coverage scenario.
  • the feature of this embodiment is that the central node cannot cover all the UEs that perform D2D multicast/broadcast communication, and the UE still needs to complete the resource competition and the mapping of the D2D multicast/broadcast air interface identifier or the predefined manner.
  • the following is elaborated through examples 11-12.
  • Example 11 In the public safety scenario, Officer A, B, and C use public safety UE1, UE2, UE3 with D2D capabilities. Officer A, B, and C all subscribe to the public security service, and UE1, UE2, and UE3 are all configured to belong to D2D communication group X.
  • FIG. 24 is a flowchart of broadcast communication with overlay scene D2D according to Example 11 of the present invention, as shown in FIG.
  • the CN/eNB node After receiving the message, the CN/eNB node performs admission control, and allocates and/or adjusts a broadcast/multicast communication air interface resource configuration that is not specific to the UE, and the resource configuration should be in advance with the UE to learn the D2D broadcast/multicast communication.
  • the resource collection information is consistent and can be a subset thereof.
  • the CN/eNB After completing the admission control and resource allocation, the CN/eNB sends a broadcast/multicast communication confirmation message to UE1.
  • the CN/eNB periodically broadcasts the broadcast/multicast air interface identifier and the corresponding D2D broadcast/multicast communication resources that are not specific to the UE.
  • the broadcast/multicast air interface resource information includes any combination of the following fields: frequency of multicast/broadcast communication, band resource, frame/subframe offset, subframe mode, time slot, resource block, resource repetition period, and so on.
  • UE1, UE2, and UE3 receive and save the periodically broadcasted D2D broadcast/multicast communication resource information.
  • UE1 monitors the radio resource usage of the D2D multicast communication that is not allocated to the UE by the CN/eNB, and acquires resources in a competitive manner. After competing to the resource, UE1 broadcasts the multicast communication data, and the transmitted data packet carries the pre-assigned D2D broadcast/multicast air interface identifier in the MAC control unit and/or the sub-header, or the RLC sub-header, or the PDCP sub-header.
  • the broadcast/multicast communication data packet may carry the D2D broadcast/multicast communication indication and the air interface identification information of UE1 in the MAC control unit and/or the sub-header, or the RLC sub-header, or the PDCP sub-header.
  • UE2 and UE3 listen on the corresponding resources according to resource collection information that is known in advance for possible broadcast/multicast communication. Assume that UE2, UE3 receives the data packet transmission, receives the data packet, parses the MAC control unit and/or the sub-header, or the RLC sub-header, or the D2D broadcast air interface identifier of the PDCP sub-header, and further performs MAC/RLC/PDCP analysis. Processed and delivered to the top.
  • Example 12 In the public safety scenario, Officer A, B, and C use public safety UE1, UE2 with D2D capabilities.
  • UE3 UE3. Officer A, B, and C all subscribe to the public security service, and UE1, UE2, and UE3 are all configured to belong to D2D communication group X. Before Office A, B, and C arrive at the rescue location, D2D multicast/broadcast communication air interface identification information and resource set information that may be used for broadcast/multicast communication are known in advance. After arriving at the rescue location, IJE1 Within the network coverage, UE2 and UE3 have no network coverage, and UE1, UE2, and UE3 are within the D2D communication range of each other. At the rescue location, Officer A hopes to initiate a multicast communication and inform other Office related information in the group.
  • FIG. 25 is a partial coverage scenario D2D multicast communication flow according to Example 12 of the present invention.
  • the group communication request message may further include a communication group priority, QoS information of one or more multicast service flows, and the like.
  • the CN/eNB node After receiving the message, the CN/eNB node performs admission control, determines the accepted multicast/broadcast communication service flow according to the multicast communication service flow QoS information included in the multicast communication request message, and allocates the group communication air interface identifier and the air interface resource. Configuration. If the traffic flow needs to last for a period of time, such as voice or video, the CN/eNB can assign a semi-static resource schedule to it.
  • the group communication confirmation message is sent to the UE1, which includes the received service flow, the assigned group communication air interface identifier, and the air interface resource and configuration information allocated to the multicast communication.
  • the multicast air interface resource information includes any combination of the following fields: frequency of multicast communication, band resource, frame/subframe offset, subframe mode, time slot, resource block, resource repetition period, and the like.
  • resource configuration information of the corresponding resource such as resource bearer identifier, media access control MAC configuration information, radio link control RLC configuration information, packet data convergence protocol PDCP configuration information, and logical channel configuration information.
  • the CN/eNB periodically broadcasts the mapping information of the D2D communication group application layer identifier and the group communication air interface identifier, and the subframe mode information corresponding to the multicast communication.
  • resource configuration information of the corresponding resource such as a resource bearer identifier, a medium access control MAC configuration information, a radio link control RLC configuration information, a packet data convergence protocol PDCP configuration information, and a logical channel configuration information, may be broadcasted.
  • the UE1 receives the mapping information of the D2D communication group application layer identifier and the group communication air interface identifier of the periodic broadcast.
  • UE1 periodically broadcasts the mapping information of the D2D communication group application layer identifier and the group communication air interface identifier, and the resource information corresponding to the multicast communication.
  • resource configuration information of the corresponding resource may be broadcasted.
  • UE2 and UE3 determine that the received D2D communication group application layer identifier is consistent with the pre-known D2D communication group application layer identifier, and UE2 and UE3 maintain the mapping of the D2D communication group application layer identifier and the group communication air interface identifier, and the resources corresponding to the multicast communication and Resource configuration information, and corresponding configuration according to resource configuration information.
  • the UE1 sends a D2D multicast communication data packet on the resource allocated by the CN/eNB, and the data packet can carry the D2D group air interface identifier.
  • UE1 may carry a D2D group air interface identifier and/or a D2D multicast indication field in a MAC control unit and/or a subheader, or an RLC subheader, or a PDCP subheader.
  • the D2D multicast communication data packet sent by UE1 is scrambled by using the D2D group air interface identifier.
  • the D2D multicast communication packet sent by UE1 is used.
  • the resources allocated by the CN/e B corresponding to the D2D group air interface identifier, and the D2D multicast communication data packet implicitly carrying the D2D group air interface identifier information by using the resource location used for sending the data packet.
  • UE2 UE3 is interested in receiving D2D multicast, and UE2 and UE3 have acquired the D2D group air interface identifier of D2D communication group X.
  • the UE2 and the UE3 monitor the corresponding subframe according to the subframe mode information corresponding to the previously acquired multicast communication and receive the D2D multicast packet. If the D2D multicast packet is received, the D2D communication group corresponding to the D2D multicast packet is further determined according to the scrambling situation, the resource location or the MAC control unit and/or the subheader, or the RLC subheader, or the PDCP subheader. Air interface identification.
  • UE2 and UE3 complete the MAC/RLC/PDCP parsing process and deliver to the upper layer.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the present invention and the preferred embodiments not only solve the problem that the UE cannot implement D2D multicast and broadcast communication in the case of no coverage or coverage and partial coverage scenarios in the related art, and thus the UE is not covered or Smooth D2D multicast and broadcast communication under coverage and partial coverage scenarios.

Abstract

本发明提供了一种设备到设备D2D组播/广播通信处理方法、装置及用户设备，该方法包括：获取用于标识D2D组播/广播通信的空口标识和/或D2D组播/广播通信的资源信息；依据空口标识在资源信息对应的资源上进行D2D组播/广播通信处理，通过本发明，解决了相关技术中，存在UE在无覆盖或有覆盖以及部分覆盖场景下无法实现D2D组播及广播通信的问题，进而达到了使得UE在无覆盖或有覆盖以及部分覆盖场景下顺利进行D2D组播及广播通信的效果。

Description

设备到设备组播 /广播通信处理方法、 装置及用户设备 技术领域 本发明涉及通信领域， 具体而言， 涉及一种设备到设备 D2D组播 /广播通信处理 方法、 装置及用户设备。 背景技术 随着无线多媒体业务的发展， 人们对高数据速率和用户体验的需求日益增长， 从 而对传统蜂窝网络的系统容量和覆盖提出了较高要求。另一方面公共安全、社交网络、 近距离数据共享、 本地广告等应用场景使得人们对了解附近人或事物并与之通信 (Proximity Services, 邻近服务） 的需求逐渐增加。 传统的以基站为中心的蜂窝网络 在高数据速率以及邻近服务的支持方面存在明显的局限性， 在这种需求背景下， 代表 未来通信技术发展新方向的设备到设备（Device-to-Device， 简称为 D2D)技术应运而 生。 D2D技术的应用， 可以减轻蜂窝网络的负担、 减少用户设备的电池功耗、 提高数 据速率， 并改善网络基础设施的鲁棒性， 很好地满足上述高数据速率业务和邻近服务 的要求。 然而， 在现有技术中并未对公共安全场景下， 在当前通信资源短缺或者拥塞或者 网络基础设施瘫痪的情况下的 D2D广播 /组播通信建立给出系统完善的解决方案， 即 在相关技术中，存在 UE在无覆盖或有覆盖以及部分覆盖场景下无法实现 D2D组播及 广播通信的问题。 发明内容 本发明提供了一种设备到设备 D2D组播 /广播通信处理方法、 装置及用户设备， 以至少解决相关技术中， 存在 UE 在无覆盖或有覆盖以及部分覆盖场景下无法实现 D2D组播及广播通信的问题。 根据本发明的一方面， 提供了一种设备到设备 D2D组播 /广播通信处理方法， 包 括： 获取用于标识用户设备和 /或 D2D组播 /广播通信的空口标识， 以及所述 D2D组播 /广播通信的资源信息； 依据所述空口标识在所述资源信息对应的资源上进行 D2D组 播 /广播通信处理。 其中， 依据所述空口标识在所述资源信息对应的资源上进行 D2D组播 /广播通信 处理包括： 依据所述空口标识在所述资源信息对应的资源上发送 D2D组播 /广播通信 数据包； 和 /或， 依据所述空口标识在所述资源信息对应的资源上接收 D2D组播 /广播 通信数据包。 其中， 获取用于标识用户设备和 /或 D2D组播 /广播通信的所述空口标识包括以下 至少之一： 从 D2D应用服务器获取所述空口标识； 根据第一预定规则， 通过将 D2D 组播 /广播应用层标识映射到空口标识的方式获取所述空口标识； 根据第二预定规则， 通过将 D2D组播 /广播 IP地址映射到空口标识的方式获取所述空口标识； 获取系统预 先默认的所述空口标识； 根据 D2D组播 /广播应用层标识和 /或用户设备直通标识生成 所述空口标识； 从相邻节点获取所述空口标识， 其中， 所述相邻节点周期性广播包含 所述空口标识的消息； 从中央节点获取所述空口标识， 其中， 所述中央节点用于对所 述 D2D组播 /广播通信进行控制。 其中， 从所述中央节点获取所述空口标识包括： 向所述中央节点发送包含用户设 备直通标识和 /或 D2D组播 /广播应用层标识的 D2D组播 /广播通信请求； 接收所述中 央节点依据所述 D2D组播 /广播通信请求分配的所述空口标识。 其中， 从所述中央节点获取所述空口标识包括： 接收包含所述空口标识的消息， 所述消息通过周期性广播的方式由所述中央节点发送。 其中， 获取用于所述 D2D组播 /广播通信的所述资源信息包括以下至少之一： 从 D2D应用服务器获取所述资源信息； 获取系统默认的所述资源信息； 采用竞争的方式 获取所述资源信息； 从相邻节点获取所述资源信息， 其中， 所述相邻节点周期性广播 包含所述资源信息的消息； 从中央节点获取所述资源信息， 其中， 所述中央节点用于 对所述 D2D组播 /广播通信进行控制。 其中， 从所述中央节点获取所述资源信息包括： 接收包含所述资源信息的消息， 所述消息通过周期性广播的方式由所述中央节点发送。 其中， 从所述中央节点获取所述资源信息包括： 向所述中央节点发送 D2D组播 / 广播通信请求； 接收所述中央节点依据所述 D2D组播 /广播通信请求分配的资源的所 述资源信息。 其中， 所述组播 /广播通信请求包含有以下至少之一： D2D组播 /广播应用层标识、 用户设备直通标识、 D2D组播 /广播 IP地址、 组播 /广播通信指示、 D2D组播 /广播优 先级、 一个或多个组播 /广播通信业务流服务质量 QoS信息。 其中， 在所述组播 /广播通信请求包括一个或多个组播 /广播通信业务流服务质量
QoS信息的情况下， 接收所述中央节点依据所述 D2D组播 /广播通信请求分配的资源 的所述资源信息包括： 接收所述中央节点发送的组播 /广播通信确认消息， 其中， 所述中央节点根据所述 组播 /广播通信请求包括的所述一个或多个组播 /广播通信业务流服务质量 QoS信息进 行接纳控制，确定接受的组播 /广播通信业务流，所述组播 /广播通信确认消息包括以下 至少之一： 所述中央节点分配的所述资源的资源信息、 接受的所述组播 /广播通信业务 流。 其中， 所述资源信息包含有以下至少之一： 组播 /广播通信的频点信息、组播 /广播 通信的频带资源信息、 组播 /广播通信的帧偏移信息、 组播 /广播通信的子帧偏移信息、 组播 /广播通信的子帧模式信息、 组播 /广播通信的时隙信息、 组播 /广播通信的资源块 信息、 组播 /广播通信的资源重复周期信息、 与所述资源信息对应的所述 D2D组播 /广 播空口标识、 发送 D2D组播 /广播通信数据包的用户设备的空口标识信息。 其中， 所述资源信息包含对应的资源的资源配置信息以下至少之一： 资源承载标 识， 媒体接入控制 MAC配置信息， 无线链路控制 RLC配置信息， 分组数据汇聚协议 PDCP配置信息， 逻辑信道配置信息。 其中， 依据所述空口标识在所述资源信息对应的资源上发送所述 D2D组播 /广播 通信数据包包括： 在所述资源上发送携带有所述用户设备空口标识、 所述 D2D组播 / 广播空口标识、 D2D组播 /广播指示至少之一的所述 D2D组播 /广播通信数据包。 其中， 通过以下方式至少之一在所述资源上发送携带有用户设备空口标识、 D2D 组播 /广播空口标识、 D2D组播 /广播指示至少之一的所述 D2D组播 /广播通信数据包： 通过在所述 D2D组播 /广播通信数据包的媒体接入控制 MAC子头和 /或控制单元， 或 者无线链路控制 RLC子头，或者分组数据汇聚协议 PDCP子头中携带有所述用户设备 空口标识、 所述 D2D组播 /广播空口标识、 所述 D2D组播 /广播指示至少之一的方式， 在所述资源上发送携带有所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 所 述 D2D组播 /广播指示至少之一的所述 D2D组播 /广播通信数据包；通过采用所述用户 设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D组播 /广播指示至少之一对所 述 D2D组播 /广播通信资源分配控制信息和 /或数据包进行加扰的方式， 在所述资源上 发送携带有所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 所述 D2D组播 / 广播指示至少之一的所述 D2D组播 /广播通信数据包；通过发送所述 D2D组播 /广播通 信数据包使用的资源位置隐式的携带所述用户设备空口标识、 所述 D2D组播 /广播空 口标识、 所述 D2D组播 /广播指示至少之一的方式， 在所述资源上发送携带有所述用 户设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D组播 /广播指示至少之一的 所述 D2D组播 /广播通信数据包， 其中， 发送所述 D2D组播 /广播通信数据包使用的所 述资源位置对应于所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 所述 D2D 组播 /广播指示至少之一。 其中， 依据所述空口标识在所述资源信息对应的资源上接收所述 D2D组播 /广播 通信数据包包括：依据所述 D2D组播 /广播空口标识判断所述 D2D组播 /广播通信数据 包的接收者是否属于所述空口标识对应的组播 /广播通信组； 在判断结果为是的情况 下， 对所述 D2D组播 /广播通信数据包进行解析处理， 并将解析后的数据包发送给高 层； 和 /或， 在判断结果为否的情况下， 丢弃所述 D2D组播 /广播通信数据包。 根据本发明的另一方面， 提供了一种设备到设备 D2D组播 /广播通信处理装置， 包括： 获取模块，设置为获取用于标识用户设备和 /或 D2D组播 /广播通信的空口标识， 以及所述 D2D组播 /广播通信的资源信息； 处理模块， 设置为依据所述空口标识在所 述资源信息对应的资源上进行 D2D组播 /广播通信处理。 其中， 所述处理模块包括： 发送单元， 设置为依据所述空口标识在所述资源信息 对应的资源上发送 D2D组播 /广播通信数据包； 和 /或， 接收单元， 设置为依据所述空 口标识在所述资源信息对应的资源上接收 D2D组播 /广播通信数据包。 其中， 所述获取模块包括以下至少之一： 第一获取单元， 设置为从 D2D应用服务 器获取所述空口标识； 第二获取单元， 设置为根据第一预定规则， 通过将 D2D组播 / 广播应用层标识映射到空口标识的方式获取所述空口标识； 第三获取单元， 设置为根 据第二预定规则， 通过将 D2D组播 /广播 IP地址映射到空口标识的方式获取所述空口 标识； 第四获取单元， 设置为获取系统预先默认的所述空口标识； 生成单元， 设置为 根据 D2D组播 /广播应用层标识和 /或用户设备直通标识生成所述空口标识； 第五获取 单元， 设置为从相邻节点获取所述空口标识， 其中， 所述相邻节点周期性广播包含所 述空口标识的消息； 第六获取单元， 设置为从中央节点获取所述空口标识， 其中， 所 述中央节点用于对所述 D2D组播 /广播通信进行控制。 其中， 所述第五获取单元包括： 第一发送子单元， 设置为向所述中央节点发送包 含用户设备直通标识和 /或 D2D组播 /广播应用层标识的 D2D组播 /广播通信请求； 第 一接收子单元， 设置为接收所述中央节点依据所述 D2D组播 /广播通信请求分配的所 述空口标识。 其中， 所述获取模块包括以下至少之一： 第七获取单元， 设置为从 D2D应用服务 器获取所述资源信息； 第八获取单元， 设置为获取系统默认的所述资源信息； 第九获 取单元， 设置为采用竞争的方式获取所述资源信息； 第十获取单元， 设置为从相邻节 点获取所述资源信息， 其中， 所述相邻节点周期性广播包含所述资源信息的消息； 第 十一获取单元， 设置为从中央节点获取所述资源信息， 其中， 所述中央节点用于对所 述 D2D组播 /广播通信进行控制。 其中， 所述第十一获取单元包括： 第二发送子单元， 设置为向所述中央节点发送 D2D组播 /广播通信请求； 第二接收子单元， 设置为接收所述中央节点依据所述 D2D 组播 /广播通信请求分配的资源的所述资源信息。 其中， 所述发送单元包括： 第三发送子单元， 设置为在所述资源上发送携带有所 述用户设备空口标识、 所述 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一的 所述 D2D组播 /广播通信数据包。 其中， 所述第三发送子单元包括以下至少之一： 第一发送次子单元， 设置为通过 在所述 D2D组播 /广播通信数据包的媒体接入控制 MAC子头和 /或控制单元， 或者无 线链路控制 RLC子头，或者分组数据汇聚协议 PDCP子头中携带有所述用户设备空口 标识、所述 D2D组播 /广播空口标识、所述 D2D组播 /广播指示至少之一的方式， 在所 述资源上发送携带有所述用户设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D 组播 /广播指示至少之一的所述 D2D组播 /广播通信数据包； 第二发送次子单元， 设置 为通过采用所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 所述 D2D组播 / 广播指示至少之一对所述 D2D组播 /广播通信资源分配控制信息和 /或数据包进行加扰 的方式， 在所述资源上发送携带有所述用户设备空口标识、 所述 D2D组播 /广播空口 标识、所述 D2D组播 /广播指示至少之一的所述 D2D组播 /广播通信数据包； 第三发送 次子单元， 设置为通过发送所述 D2D组播 /广播通信数据包使用的资源位置隐式的携 带所述用户设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D组播 /广播指示至 少之一的方式， 在所述资源上发送携带有所述用户设备空口标识、 所述 D2D组播 /广 播空口标识、所述 D2D组播 /广播指示至少之一的所述 D2D组播 /广播通信数据包， 其 中， 发送所述 D2D组播 /广播通信数据包使用的所述资源位置对应于所述用户设备空 口标识、 所述 D2D组播 /广播空口标识、 所述 D2D组播 /广播指示至少之一。 其中， 所述接收单元包括： 判断子单元， 设置为依据所述 D2D组播 /广播空口标 识判断所述 D2D组播 /广播通信数据包的接收者是否属于所述空口标识对应的组播 /广 播通信组； 解析子单元， 设置为在所述判断子单元的判断结果为是的情况下， 对所述 D2D 组播 /广播通信数据包进行解析处理， 并将解析后的数据包发送给高层； 和 /或， 丢弃子单元， 设置为在所述判断子单元的判断结果为否的情况下， 丢弃所述 D2D组播
/广播通信数据包。 根据本发明的还一方面， 提供了一种用户设备， 包括上述任一项所述的装置。 通过本发明， 采用获取用于标识用户设备和 /或 D2D组播 /广播通信的空口标识， 以及所述 D2D组播 /广播通信的资源信息； 依据所述空口标识在所述资源信息对应的 资源上进行 D2D组播 /广播通信处理，解决了相关技术中，存在 UE在无覆盖或有覆盖 以及部分覆盖场景下无法实现 D2D组播及广播通信的问题，进而达到了使得 UE在无 覆盖或有覆盖以及部分覆盖场景下顺利进行 D2D组播及广播通信的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中： 图 1是根据本发明实施例的设备到设备 D2D组播 /广播通信处理方法的流程图； 图 2是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置的结构框图； 图 3是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中处理模块
24的优选结构框图； 图 4是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中获取模块 22的优选结构框图一； 图 5是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中获取模块 22中第五获取单元 46的优选结构框图； 图 6是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中获取模块 22的优选结构框图二； 图 7是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中获取模块 22中第十一获取单元 65的优选结构框图； 图 8是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中处理模块 24中发送单元 32的优选结构框图； 图 9是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中处理模块 24中发送单元 32中第三发送子单元 82的优选结构框图； 图 10是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中处理模块 24中接收单元 34的优选结构框图； 图 11是根据本发明实施例的用户设备的结构框图； 图 12是根据本发明实施例的设备直通系统通信模式示意图； 图 13是根据本发明实施例的 D2D组播 /广播针对不同覆盖场景的示意图； 图 14是根据本发明实例 1的无覆盖场景 D2D组播通信流程图； 图 15 是根据本发明实例 2的无覆盖场景 D2D组播通信流程图； 图 16 是根据本发明实例 3的无覆盖场景 D2D组播通信流程图； 图 17是根据本发明实例 4的无覆盖场景 D2D组播通信流程图； 图 18 是根据本发明实例 5的无覆盖场景 D2D广播通信流程图； 图 19是根据本发明实例 6的有覆盖场景 D2D组播通信流程图； 图 20 是根据本发明实例 7的有覆盖场景 D2D组播通信流程图； 图 21是根据本发明实例 8的有覆盖场景 D2D组播通信流程图； 图 22是根据本发明实例 9的有覆盖场景 D2D组播通信流程图； 图 23是根据本发明实例 10的有覆盖场景 D2D广播通信流程图； 图 24是根据本发明实例 11的有覆盖场景 D2D广播通信流程图； 图 25是根据本发明实例 12的部分覆盖场景 D2D组播通信流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在不冲突的 情况下， 本申请中的实施例及实施例中的特征可以相互组合。 在本实施例中提供了一种设备到设备 D2D组播 /广播通信处理方法， 图 1是根据 本发明实施例的设备到设备 D2D组播 /广播通信处理方法的流程图， 如图 1所示， 该 流程包括如下步骤： 步骤 S102, 获取用于标识用户设备和 /或 D2D 组播 /广播通信的空口标识， 以及 D2D组播 /广播通信的资源信息； 步骤 S104,依据空口标识在资源信息对应的资源上进行 D2D组播 /广播通信处理。 通过上述步骤， 依据 D2D组播 /广播通信的空口标识和 /或 D2D组播 /广播通信的 资源信息进行 D2D组播 /广播通信处理，解决了相关技术中，存在 UE在无覆盖或有覆 盖以及部分覆盖场景下无法实现 D2D组播及广播通信的问题，进而达到了使得 UE在 无覆盖或有覆盖以及部分覆盖场景下顺利进行 D2D组播及广播通信的效果。 其中， 依据空口标识在资源信息对应的资源上进行 D2D组播 /广播通信处理可以 包括： 依据空口标识在资源信息对应的资源上发送 D2D组播 /广播通信数据包； 和 /或， 依据空口标识在资源信息对应的资源上接收 D2D组播 /广播通信数据包。 获取用于标识用户设备和 /或 D2D组播 /广播通信的空口标识可以有多种方式， 例 如， 可以采用以下方式至少之一： 从 D2D应用服务器获取空口标识； 根据第一预定规 贝 U， 通过将 D2D组播 /广播应用层标识映射到空口标识的方式获取空口标识； 根据第 二预定规则， 通过将 D2D组播 /广播 IP地址映射到空口标识的方式获取空口标识； 获 取系统预先默认的空口标识； 根据 D2D组播 /广播应用层标识和 /或用户设备直通标识 生成空口标识； 从相邻节点获取空口标识， 其中， 该相邻节点周期性广播包含空口标 识的消息； 从中央节点获取空口标识， 其中， 中央节点用于对 D2D组播 /广播通信进 行控制。 其中， 从中央节点获取空口标识可以采用以下处理方式： 向中央节点发送包 含用户设备直通标识和 /或 D2D组播 /广播应用层标识的 D2D组播 /广播通信请求； 接 收中央节点依据 D2D组播 /广播通信请求分配的空口标识。 较优地， 可以通过专有信 令和 /或周期性广播的方式从中央节点获取空口标识， 例如， 包括接收中央节点依据 D2D组播 /广播通信请求分配的空口标识。 获取用于 D2D组播 /广播通信的资源信息也可以采用多种方式， 例如， 可以采用 以下方式至少之一： 从 D2D应用服务器获取资源信息； 获取系统默认的资源信息； 采 用竞争的方式获取资源信息； 从相邻节点获取资源信息， 其中， 该相邻节点周期性广 播包含资源信息的消息； 从中央节点获取资源信息， 其中， 该中央节点用于对 D2D组 播 /广播通信进行控制。 其中， 从中央节点获取资源信息可以采用以下处理方式： 也可 以通过上述的专用信令和 /或周期性广播的方式从中央节点获取该资源信息， 例如， 可 以向中央节点发送 D2D组播 /广播通信请求；接收中央节点依据 D2D组播 /广播通信请 求分配的资源的资源信息。 其中， 该组播 /广播通信请求可以包含有以下至少之一： D2D 组播 /广播应用层标 识、 用户设备直通标识、 D2D组播 /广播 IP地址、 组播 /广播通信指示、 D2D组播 /广 播优先级、 一个或多个组播 /广播通信业务流服务质量 QoS信息。 优选地，在组播 /广播通信请求包括一个或多个组播 /广播通信业务流服务质量 QoS 信息的情况下， 接收中央节点依据 D2D组播 /广播通信请求分配的资源的资源信息可 以采用以下处理： 接收中央节点发送的组播 /广播通信确认消息， 其中， 中央节点根据 组播 /广播通信请求包括的一个或多个组播 /广播通信业务流服务质量 QoS信息进行接 纳控制，确定接受的组播 /广播通信业务流，组播 /广播通信确认消息包括以下至少之一： 中央节点分配的资源的资源信息、 接受的组播 /广播通信业务流。 需要说明的是， 上述资源信息可以包括多种信息， 例如， 可以包含有以下至少之 一： 组播 /广播通信的频点信息、 组播 /广播通信的频带资源信息、 组播 /广播通信的帧 偏移信息、 组播 /广播通信的子帧偏移信息、 组播 /广播通信的子帧模式信息、 组播 /广 播通信的时隙信息、组播 /广播通信的资源块信息、组播 /广播通信的资源重复周期信息、 与资源信息对应的 D2D组播 /广播空口标识、 发送 D2D组播广播通信数据包的用户设 备的空口标识信息。 其中， 该资源信息所对应的资源的资源配置信息可以包括以下至 少之一： 资源承载标识，媒体接入控制 MAC配置信息，无线链路控制 RLC配置信息， 分组数据汇聚协议 PDCP配置信息， 逻辑信道配置信息。 依据空口标识在资源信息对应的资源上发送 D2D组播 /广播通信数据包包括： 在 资源上发送携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示 至少之一的 D2D组播 /广播通信数据包。 较佳地， 可以通过以下方式至少之一在资源 上发送携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少 之一的 D2D组播 /广播通信数据包：通过在 D2D组播 /广播通信数据包的媒体接入控制 MAC子头和 /或控制单元，或者无线链路控制 RLC子头，或者分组数据汇聚协议 PDCP 子头中携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少 之一的方式， 在资源上发送携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D 组播 /广播指示至少之一的 D2D组播 /广播通信数据包； 通过采用用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一对 D2D组播 /广播通信资源分 配控制信息和 /或数据包进行加扰的方式， 在资源上发送携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一的 D2D组播 /广播通信数据包； 通过发送 D2D组播 /广播通信数据包使用的资源位置隐式的携带用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一的方式， 在资源上发送携带有 用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一的 D2D组 播 /广播通信数据包， 其中， 发送 D2D组播 /广播通信数据包使用的资源位置对应于用 户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一。 依据空口标识在资源信息对应的资源上接收 D2D组播 /广播通信数据包包括： 依 据 D2D组播 /广播空口标识判断 D2D组播 /广播通信数据包的接收者是否属于空口标识 对应的组播 /广播通信组； 在判断结果为是的情况下， 对 D2D组播 /广播通信数据包进 行解析处理， 并将解析后的数据包发送给高层； 和 /或， 在判断结果为否的情况下， 丢 弃 D2D组播 /广播通信数据包。 在本实施例中还提供了一种设备到设备 D2D组播 /广播通信处理装置， 该装置用 于实现上述实施例及优选实施方式， 已经进行过说明的不再赘述。 如以下所使用的， 术语 "模块"可以实现预定功能的软件和 /或硬件的组合。 尽管以下实施例所描述的装 置较佳地以软件来实现， 但是硬件， 或者软件和硬件的组合的实现也是可能并被构想 的。 图 2是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置的结构框图， 如图 2所示， 该装置包括获取模块 22和处理模块 24， 下面对该装置进行说明。 获取模块 22，设置为获取用于标识用户设备和 /或 D2D组播 /广播通信的空口标识， 以及 D2D组播 /广播通信的资源信息； 处理模块 24， 连接至上述获取模块 22， 设置为 依据空口标识在资源信息对应的资源上进行 D2D组播 /广播通信处理。 图 3是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中处理模块
24的优选结构框图， 如图 3所示， 该处理模块 24包括发送单元 32和 /或接收单元 34， 下面对该装置进行说明。 发送单元 32， 设置为依据空口标识在资源信息对应的资源上发送 D2D组播 /广播 通信数据包； 接收单元 34， 设置为依据空口标识在资源信息对应的资源上接收 D2D 组播 /广播通信数据包。 图 4是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中获取模块 22的优选结构框图一， 如图 4所示， 该获取模块 22包括以下至少之一： 第一获取单 元 41、 第二获取单元 42、 第三获取单元 43、 第四获取单元 44、 生成单元 45、 第五获 取单元 46、 第六获取单元 47， 下面对该获取模块 22进行说明。 第一获取单元 41， 设置为从 D2D应用服务器获取空口标识； 第二获取单元 42， 设置为根据第一预定规则， 通过将 D2D组播 /广播应用层标识映射到空口标识的方式 获取空口标识； 第三获取单元 43， 设置为根据第二预定规则， 通过将 D2D组播 /广播 IP地址映射到空口标识的方式获取空口标识； 第四获取单元 44， 设置为获取系统预先 默认的空口标识； 生成单元 45， 设置为根据 D2D组播 /广播应用层标识和 /或用户设备 直通标识生成空口标识； 第五获取单元 46， 设置为从相邻节点获取空口标识， 其中， 相邻节点周期性广播包含空口标识的消息； 第六获取单元 47， 设置为从中央节点获取 空口标识， 其中， 中央节点用于对 D2D组播 /广播通信进行控制。 图 5是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中获取模块 22中第五获取单元 46的优选结构框图， 如图 5所示， 该第五获取单元 46包括第一发 送子单元 52和第一接收子单元 54， 下面对该第五获取单元 46进行说明。 第一发送子单元 52， 设置为向中央节点发送包含用户设备直通标识和 /或 D2D组 播 /广播应用层标识的 D2D组播 /广播通信请求； 第一接收子单元 54， 连接至上述第一 发送子单元 52， 设置为接收中央节点依据 D2D组播 /广播通信请求分配的空口标识。 图 6是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中获取模块
22的优选结构框图二， 如图 6所示， 该获取模块 22包括以下至少之一： 第七获取单 元 61、 第八获取单元 62、 第九获取单元 63、 第十获取单元 64、 第十一获取单元 65， 下面对该获取模块 22进行说明。 第七获取单元 61， 设置为从 D2D应用服务器获取资源信息； 第八获取单元 62， 用于获取系统默认的资源信息； 第九获取单元 63， 设置为采用竞争的方式获取资源信 息； 第十获取单元 64， 设置为从相邻节点获取资源信息， 其中， 相邻节点周期性广播 包含资源信息的消息； 第十一获取单元 65， 设置为从中央节点获取资源信息， 其中， 中央节点用于对 D2D组播 /广播通信进行控制。 图 7是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中获取模块 22中第十一获取单元 65的优选结构框图， 如图 7所示， 该第十一获取单元 65包括第 二发送子单元 72和第二接收子单元 74， 下面对该第 ^一获取单元 65进行说明。 第二发送子单元 72， 设置为向中央节点发送 D2D组播 /广播通信请求； 第二接收 子单元 74， 连接至上述第二发送子单元 72， 设置为接收中央节点依据 D2D组播 /广播 通信请求分配的资源的资源信息。 图 8是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中处理模块 24中发送单元 32的优选结构框图， 如图 8所示， 该发送单元 32包括第三发送子单元 82， 下面对该第三发送子单元 82进行说明。 第三发送子单元 82， 设置为在资源上发送携带有用户设备空口标识、 D2D组播 / 广播空口标识、 D2D组播 /广播指示至少之一的 D2D组播 /广播通信数据包。 图 9是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中处理模块 24中发送单元 32中第三发送子单元 82的优选结构框图， 如图 9所示， 该第三发送子 单元 82包括以下至少之一： 第一发送次子单元 92、 第二发送次子单元 94、 第三发送 次子单元 96， 下面对该第三发送子单元 82进行说明。 第一发送次子单元 92， 设置为通过在 D2D组播 /广播通信数据包的媒体接入控制
MAC子头和 /或控制单元，或者无线链路控制 RLC子头，或者分组数据汇聚协议 PDCP 子头中携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少 之一的方式， 在资源上发送携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D 组播 /广播指示至少之一的 D2D组播 /广播通信数据包； 第二发送次子单元 94， 设置为 通过采用用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一 对 D2D组播 /广播通信资源分配控制信息和 /或数据包进行加扰的方式， 在资源上发送 携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一的 D2D组播 /广播通信数据包； 第三发送次子单元 96， 设置为通过发送 D2D组播 /广播通 信数据包使用的资源位置隐式的携带用户设备空口标识、 D2D 组播 /广播空口标识、 D2D 组播 /广播指示至少之一的方式， 在资源上发送携带有用户设备空口标识、 D2D 组播 /广播空口标识、 D2D组播 /广播指示至少之一的 D2D组播 /广播通信数据包，其中， 发送 D2D组播 /广播通信数据包使用的资源位置对应于用户设备空口标识、 D2D组播 / 广播空口标识、 D2D组播 /广播指示至少之一。 图 10是根据本发明实施例的设备到设备 D2D组播 /广播通信处理装置中处理模块 24中接收单元 34的优选结构框图，如图 8所示，该接收单元 34包括：判断子单元 102、 解析子单元 104和 /或丢弃子单元 106， 下面对该接收单元 34进行说明。 判断子单元 102， 设置为依据 D2D组播 /广播空口标识判断 D2D组播 /广播通信数 据包的接收者是否属于空口标识对应的组播 /广播通信组； 解析子单元 104， 连接至上 述判断子单元 102， 设置为在判断子单元 102的判断结果为是的情况下， 对 D2D组播 /广播通信数据包进行解析处理， 并将解析后的数据包发送给高层； 和 /或， 丢弃子单元 106，连接至上述判断子单元 102，设置为在判断子单元 102的判断结果为否的情况下， 丢弃 D2D组播 /广播通信数据包。 图 11是根据本发明实施例的用户设备的结构框图，如图 11所示，该用户设备 112 包括上述任一项的 D2D组播 /广播通信处理装置 114。 D2D技术可以工作在授权频段或非授权频段， 允许多个支持 D2D功能的用户设 备 （即 D2D用户设备， D2D User Equipment, D2D UE) 在有网络基础设施或无网络 基础设施的情况下进行直接发现 /直接通信。 图 12是根据本发明实施例的设备直通系 统通信模式示意图， 如图 12所示， 该 D2D的应用场景主要有三种：
( 1 ) UE1和 UE2在蜂窝网络的覆盖下进行数据交互， 用户面数据不经过网络基 础设施， 如图 1的模式 1 ;
(2)在弱 /无覆盖区域的 UE中继传输， 如图 1中的模式 2， 允许信号质量较差的 UE4通过附近有网络覆盖的 UE3与网络进行通信，能帮助运营商扩展覆盖、提高容量；
(3 )在发生地震或紧急情况， 蜂窝网络不能正常工作的情况下， 允许设备间直接 通信， 如图 12中的模式 3， UE5, UE6和 UE7间控制面和用户面都不经过网络基础设 施而进行一跳或多跳的数据通信。 从公共安全的角度来看， 公共安全网络系统需要为第一响应人提供多媒体等服务 手段来完成任务，要求具有单点通信和组内通信功能。具体来讲，公共安全场景的 D2D 通信包含如下类型： 单播，组播，广播。单播指 D2D用户设备之间一对一的通信模式， 而组播与广播是针对 D2D用户设备一对多的通信模式。单播通信可看成是组播通信的 特殊形式， 如 D2D通信组内只包含两个用户设备， 此时 D2D组播通信相当于单播通 信。 与此同时， 公共安全场景的通信要求具有很强的鲁棒性， 能够在当前通信资源短 缺或者拥塞或者网络基础设施瘫痪的情况下仍然能够最大限度的提供服务。 因此公共 安全要求 D2D通信不仅在有网络覆盖场景下工作，也要求在部分覆盖以及无网络覆盖 场景下工作。 在无网络覆盖场景下， D2D用户设备可以通过自组织的方式工作， 也可 以在无覆盖环境下选取一些 D2D用户设备作为中央节点（Central Node, 简称为 CN)， 这些中央节点提供类似基站的功能。 图 13是根据本发明实施例的 D2D组播 /广播针对不同覆盖场景的示意图，如图 13 所示， 给出了公共安全场景下 D2D组播广播通信的示意图， 其中图 13 (a) 是在无覆 盖场景下的 D2D用户设备之间的组播广播通信， 而图 13 (b) 是在有覆盖场景下或是 无网络覆盖但引入 CN场景下 D2D用户设备之间的组播广播通信。这里的 CN可以是 有覆盖场景下的 e B， 也可以是无覆盖场景下由 D2D用户设备充当。 图 13 (c)给出 了进行组通信的部分 D2D用户设备在中央节点覆盖下， 而部分 D2D用户设备不在中 央节点覆盖下的场景。 基于上述场景， 在本实施例中， 提供了一种公共安全场景下 UE在无覆盖或有覆 盖以及部分覆盖时的 D2D广播 /组播通信建立方法，通过该 D2D广播 /组播通信建立方 法及系统， 用户设备可以在有网络覆盖及无网络覆盖和部分网络覆盖等各种场景下通 过简单的流程快速灵活的建立 D2D 组播及广播通信， 确保组播及广播通信的顺利进 行。 此外， 上述方法也可应用于单播通信， 如广播或者组播通信只有一个接收用户设 备的情况。 该 D2D组播及广播通信建立方法包括： 用户设备获取 D2D组播 /广播通信的空口 标识以及资源信息； 用户设备使用该空口标识在上述资源上发送 /接收 D2D组播 /广播 通信数据包。 其中， 上述所指的用户设备包括： 发起 D2D组播 /广播通信的第一用户 设备， 以及接收 D2D组播 /广播通信的第二用户设备； 该第二用户设备涉及一个或多 个与第一用户设备相邻的用户设备； 空口标识指 D2D组播 /广播通信标识， 其中的组 播空口标识指可在空口标识所有的 D2D组播通信或特定的 D2D组播通信组 （即预定 的 D2D组播通信组）， 而广播空口标识可在空口标识 D2D广播通信。 一方面， 用户设备获取 D2D组播 /广播通信的空口标识信息可以采用多种方式， 例如， 可以采用以下方式至少之一来获取： 用户设备从 D2D 应用服务器获取所加入 D2D组播 /广播的空口标识； 用户设备根据预定义规则将 D2D组播应用层标识映射到 D2D组的空口标识； 用户设备从 D2D应用服务器获取所加入 D2D组的 IP组播地址， 并根据预定义规则将 D2D组的 IP组播地址映射到 D2D组的空口标识； 第一用户设备 发起 D2D组播通信之前， 根据 D2D组播应用层标识生成 D2D组的空口标识， 并周期 性的广播 D2D组播应用层标识与空口标识的映射关系，第二用户设备接收第一用户设 备周期性广播的 D2D组播应用层标识与空口标识的映射关系， 从而获取 D2D组的空 口标识； 用户设备预先获取默认的 D2D组播 /广播通信空口标识； 用户设备从中央节 点获取 D2D组播 /广播空口标识。 其中， 需要说明的是， 上述中央节点可以是基站， 或执行中央控制功能的用户设备， 该中央节点不参与组播 /广播数据的传输， 只进行相 应的控制面的信令控制。 其中，用户设备从中央节点获取 D2D组的空口标识可以采用以下较为简单的处理 方式， 包括： 第一用户设备向中央节点发送包含 D2D应用层组标识的 D2D组通信请 求； 中央节点接收 D2D组通信请求， 分配 D2D组空口标识； 中央节点通过专有信令 和或周期性广播将包含 D2D组空口标识，或 D2D组空口标识与 D2D组应用层标识映 射信息的消息发送给用户设备；用户设备接收中央节点发送的包含 D2D组空口标识信 息的消息。 较优地， 用户设备从中央节点获取 D2D组的空口标识之前， 还包括： 第一用户设 备希望发起 D2D组播通信。 其中，用户设备从中央节点获取 D2D广播空口标识也可以采用以下较为简单的处 理方式， 包括： 第一用户设备向中央节点发送 D2D广播通信请求； 中央节点接收 D2D 广播通信请求， 分配 D2D广播空口标识； 中央节点可通过专有信令和 /或周期性广播 将包含 D2D广播空口标识的消息发送给用户设备；用户设备接收中央节点发送的包含 D2D广播空口标识信息的消息。 另一方面， 用户设备获取 D2D组播 /广播通信的资源信息， 也可以采用多种处理 方式， 例如， 也可以采用以下方式至少之一： 用户设备从 D2D应用服务器获取 D2D 组播 /广播通信资源信息； 用户设备获取系统默认的 D2D组播 /广播通信资源信息； 第 一用户设备采用竞争的方式获取发送组播 /广播通信数据包的时频资源； 用户设备从中 央节点获取 D2D组播 /广播通信的资源信息。 其中， 用户设备从中央节点获取 D2D组播 /广播通信的资源信息也可以采用以下 较为简单的处理， 包括： 第一用户设备发送组播 /广播通信请求给中央节点； 中央节点 接收组播 /广播通信请求消息后， 为组播 /广播通信分配空口资源， 并发送包含组播 /广 播空口资源信息的消息给用户设备； 用户设备接收包含组播 /广播空口资源信息的消 息。 较优地，在第一用户设备发送组播 /广播通信请求消息给中央节点时，该组播 /广播 通信请求消息可包含但不限于以下字段： D2D组标识， 组播 /广播通信指示， D2D组 优先级， 一个或多个组播 /广播通信业务流 QoS信息； 其中， D2D组标识可以是以下 至少之一： D2D组应用层标识、 D2D IP组播地址、 系统默认的 D2D组空口标识。 中央节点接收组播 /广播通信请求消息后，为组播 /广播通信分配空口资源，并发送 包含组播 /广播空口资源信息的消息给用户设备时， 对该组播 /广播可以进行以下处理: 中央节点对组播 /广播通信请求进行接纳控制；中央节点可根据组播 /广播通信请求消息 包含的组播 /广播通信业务流 QoS信息， 确定接受的组播 /广播通信业务流。在此之后， 中央节点发送包含组播 /广播空口资源信息的消息给用户设备可以包括： 中央节点发送 组播 /广播通信确认消息给第一用户设备，其中，该组播 /广播通信确认消息可包含分配 给组播 /广播通信的资源和 /或被接受的业务流信息。 另外， 中央节点发送包含组播 /广播空口资源信息的消息给用户设备时， 可以采用 不同的发送方式来发送不同的资源信息， 例如， 该中央节点可以采用周期性广播的方 式发送组播 /广播通信对应的子帧模式信息;该中央节点可以广播发送包含组播 /广播通 信的资源信息， 其中， 该组播 /广播空口资源信息可以包含以下字段的任意组合： 组播 /广播通信的频点， 频带资源， 帧 /子帧偏移， 子帧模式， 时隙， 资源块， 资源重复周期 等； 该组播 /广播通信的资源信息包含以下至少之一： 对应的 D2D组空口标识/ D2D广 播空口标识、 第一用户设备的标识信息。 另外， 中央节点发送的包含组播 /广播通信的 资源信息也可以周期性发送。 用户设备使用空口标识在资源上发送 /接收 D2D组播 /广播通信数据包时， 包括： 第一用户设备在资源上发送 D2D组播 /广播通信数据包，其数据包隐式或显式携带 D2D 组空口标识/ D2D广播标识； 第二用户设备在资源接收 D2D组播数据包， 根据 D2D组 空口标识判断是否需要进一步解析， 如果需要则进一步进行 MAC/RLC/PDCP解析处 理并投递给高层， 否则丢弃该数据包； 或者， 第二用户设备在资源接收 D2D广播通信 数据包， 完成 MAC/RLC/PDCP层解析处理后， 投递给高层。 第一用户设备在资源上发送 D2D组播 /广播通信数据包时， 其数据包隐式或显式 携带 D2D组空口标识/ D2D广播标识， 包括： 第一用户设备在发送的 D2D组播 /广播 通信数据包携带以下至少之一： D2D组空口标识/ D2D广播标识， D2D组播 /广播指示。 较佳地， 可以通过以下方式来携带该 D2D组空口标识/ D2D广播标识： 可在 D2D组播 /广播通信数据包的 MAC/RLC/PDCP子头携带以下至少之一： D2D组空口标识/ D2D 广播标识、 D2D组播 /广播指示字段； 使用 D2D组空口标识/ D2D广播标识对第一用户 设备发送的 D2D组播 /广播通信数据包进行加扰；第一用户设备发送的 D2D组播 /广播 通信数据包使用中央节点分配的对应于 D2D组空口标识/ D2D广播标识的资源， D2D 组播 /广播通信数据包通过发送数据包使用的资源位置隐式的携带 D2D 组空口标识 /D2D广播标识信息。 第二用户设备在资源接收 D2D组播 /广播通信数据包之前， 还包括： 第二用户设 备对接收 D2D组播 /广播有兴趣， 并获取了 D2D组播 /广播空口标识及资源信息； 第二 用户设备在资源接收 D2D组播数据包， 根据 D2D组空口标识判断是否需要进一步解 析， 如果需要则进行 MAC/RLC/PDCP解析处理并投递给高层， 否则丢弃该数据包。 需要说明的是， 如果第二用户设备是 D2D组空口标识对应的 D2D组的成员， 则第二 用户设备需要解析数据包。
UE在无覆盖或有覆盖以及部分覆盖场景下， D2D组播及广播通信建立可采取用 户设备获取 D2D组播 /广播通信的空口标识以及资源信息， 之后用户设备使用空口标 识在资源上发送 /接收 D2D组播 /广播通信数据包的方式完成。 通过上述实施例及优选 实施方式， 用户设备可以在有覆盖、 无覆盖和部分覆盖等场景下通过简单的流程快速 灵活的建立 D2D组播及广播通信， 确保组播及广播通信的顺利进行。 针对图 13给出的三种覆盖场景， 下面分别介绍相应的实施例。 实施例一 本实施例给出无覆盖场景下 D2D组播广播通信建立方法。该实施例的特征是没有 中央节点进行资源协调以及 D2D组播 /广播空口标识的分配，需要 UE独立的完成资源 竞争以及 D2D组播 /广播空口标识的映射或预定义的方式获取。 以下通过实例 1至实 例 5详细阐述。 实例 1 在公共安全场景， OfficerA, B， C， D使用具备 D2D功能的公共安全 UE1， UE2, UE3及 UE4。 OfficerA, B， C， D都订阅了公共安全服务， 并且 UE1， UE2, UE3配 置属于 D2D通信组 X， 而 UE4属于 D2D通信组 Y。 在 OfficerA, B， C， D到达救援 地点之前， 预先获知 D2D通信组标识 GID以及用于公共安全的无线资源信息， 其中 无线资源信息可包含频点及频带信息。 在到达救援地点之后， 他们都不在网络覆盖范 围内， 但是 UE1， UE2, UE3 , UE4彼此在 D2D通信范围内。 在救援地点， Officer A希望发起组播通信，告知组内其他 Officer相关信息。 Officer A的 UE1监听预分配的无线资源使用情况， 通过竞争的方式获取资源， 图 14是根据 本发明实例 1的无覆盖场景 D2D组播通信流程图，如图 14所示。竞争到资源之后 UE1 广播发送组播通信数据， 所发送数据包在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带预分配的 D2D组标识。 此外， 组播通信数据包可在 MAC控制单 元和 /或子头， 或者 RLC子头，或者 PDCP子头携带 D2D组播通信指示以及 UE1的空 口标识信息。
Officer B, C， D的 UE2， UE3及 UE4对预先获知的公共安全无线资源进行监听。 假设 UE2， UE3 , UE4监听到有数据包发送， 则接收该数据包， 解析 MAC控制单元 和 /或子头， 或者 RLC子头， 或者 PDCP子头的 D2D组标识。 UE2和 UE3判断自己属 于该 D2D组标识对应的 D2D组的成员， 则 UE2和 UE3进一步进行 MAC/RLC/PDCP 解析处理并投递给高层。而对于 UE4则判断自己不属于该 D2D组标识对应的 D2D组 的成员， 因此丢弃该数据包。 实例 2 在公共安全场景， OfficerA, B， C， D使用具备 D2D功能的公共安全 UE1， UE2, UE3及 UE4。 OfficerA, B， C， D都订阅了公共安全服务， 并且 UE1， UE2, UE3配 置属于 D2D通信组 X， 而 UE4属于 D2D通信组 Y。 在 OfficerA, B， C， D到达救援 地点之前， 预先获知 D2D通信组应用层标识 GID以及用于公共安全的无线资源信息， 其中无线资源信息可包含频点及频带信息。在到达救援地点之后， UE都不在网络覆盖 范围内， 但是 UE1， UE2, UE3 , UE4彼此在 D2D通信范围内。 在救援地点， OfficerA希望发起组播通信， 告知组内其他 Officer相关信息。 与此 同时， Officer B, C， D的 UE2， UE3 , UE4希望能够接收到组播信息。 贝 U UE1， UE2, UE3 , UE4首先将 D2D通信组应用层标识 GID根据预定义规则映射到 D2D组空口标 识， 之后监听预分配的无线资源。 想要发送数据的 UE1通过竞争的方式获取资源， 图 15是根据本发明实例 2的无覆盖场景 D2D组播通信流程图， 如图 15所示。 竞争到资 源之后 UE1广播发送组播通信数据， 所发送数据包在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带根据预定义规则映射到 D2D组空口标识。 可此外， 组播通信数据包可在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带 D2D组播通信指示以及 UE1的空口标识信息。
Officer B, C， D的 UE2， UE3及 UE4对预先获知的公共安全无线资源进行监听。 假设 UE2， UE3 , UE4监听到有数据包发送， 则接收该数据包， 解析 MAC控制单元 和 /或子头， 或者 RLC子头， 或者 PDCP子头的 D2D组空口标识。 UE2和 UE3判断该 D2D空口标识与自己所属的 D2D通信组映射的 D2D空口标识一致， 则 UE2和 UE3 进一步进行 MAC/RLC/PDCP解析处理并投递给高层。 而对于 UE4则判断自己不属于 该 D2D组标识对应的 D2D组的成员， 因此丢弃该数据包。 这种预定义映射规则有可能产生不同的 D2D 通信组应用层标识映射到同一个 D2D组空口标识的情况， 对于这种情况， UE可继续通过 IP层的组播地址或是应用层 携带的 D2D组信息来进一步判断是否是对应正确的 D2D通信组， 由高层判断是接收 该数据包还是丢弃。 实例 3 在公共安全场景， OfficerA, B， C， D使用具备 D2D功能的公共安全 UE1， UE2,
UE3及 UE4。 OfficerA, B， C， D都订阅了公共安全服务， 并且 UE1， UE2, UE3配 置属于 D2D通信组 X， 而 UE4属于 D2D通信组 Y。 在 OfficerA, B， C， D到达救援 地点之前， 预先获知 D2D通信组的 IP组播地址以及用于公共安全的无线资源信息， 其中无线资源信息可包含频点及频带信息。在到达救援地点之后， UE都不在网络覆盖 范围内， 但是 UE1， UE2, UE3 , UE4彼此在 D2D通信范围内。 在救援地点， OfficerA希望发起组播通信， 告知组内其他 Officer相关信息。 与此 同时， Officer B, C， D的 UE2， UE3 , UE4希望能够接收到组播信息。 贝 U UE1， UE2, UE3 , UE4首先将 D2D通信组的 IP组播地址根据预定义规则映射到 D2D组空口标识， 之后监听预分配的无线资源。 想要发送数据的 UE1 通过竞争的方式获取资源， 图 16 是根据本发明实例 3的无覆盖场景 D2D组播通信流程图， 如图 16所示。 竞争到资源 之后 UE1 广播发送组播通信数据， 所发送数据包在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头子头携带根据预定义规则映射到 D2D组空口标识。 此外， 组播通信数据包可在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带 D2D组播通信指示信息以及 UE1的空口标识。
Officer B, C， D的 UE2， UE3及 UE4对预先获知的公共安全无线资源进行监听。 假设 UE2， UE3 , UE4监听到有数据包发送， 则接收该数据包， 解析 MAC控制单元 和 /或子头， 或者 RLC子头， 或者 PDCP子头的 D2D组空口标识。 UE2和 UE3判断该 D2D空口标识与自己所属的 D2D通信组映射的 D2D空口标识一致， 则 UE2和 UE3 进一步进行 MAC/RLC/PDCP解析处理并投递给高层。 而对于 UE4则判断自己不属于 该 D2D组标识对应的 D2D组的成员， 因此丢弃该数据包。 这种预定义映射规则有可能产生不同的 D2D通信组的 IP组播地址映射到同一个 D2D组空口标识的情况， 对于这种情况， UE可继续通过 IP层的组播地址来进一步判 断是否是对应正确的 D2D通信组， 由高层判断是接收该数据包还是丢弃。 实例 4 在公共安全场景， OfficerA, B， C， D使用具备 D2D功能的公共安全 UE1， UE2, UE3及 UE4。 OfficerA, B， C， D都订阅了公共安全服务， 并且 UE1， UE2, UE3配 置属于 D2D通信组 X， 而 UE4属于 D2D通信组 Y。 在 OfficerA, B， C， D到达救援 地点之前， 预先获知 D2D通信组应用层标识 GID以及用于公共安全的无线资源信息， 其中无线资源信息可包含频点及频带信息。 在到达救援地点之后， UE都不在网络覆 盖范围内， 但是 UE1， UE2, UE3 , UE4彼此在 D2D通信范围内。 在救援地点， OfficerA希望发起组播通信， 告知组内其他 Officer相关信息， 与此 同时， Officer B, C， D的 UE2， UE3 , UE4希望能够接收到组播信息。 想要发送数据 的 UE1首先生成 D2D组空口标识， 通过竞争的方式获取资源并周期性的发送 D2D通 信组应用层标识 GID与 D2D组空口标识的映射信息， 图 17是根据本发明实例 4的 覆盖场景 D2D组播通信流程图， 如图 17所示。 UE2， UE3 , UE4监听预分配的无线 资源， 获取 D2D通信组应用层标识 GID与 D2D组空口标识的映射信息， 然后判断自 己是否也加入了 D2D通信组应用层标识 GID对应的组， 如果是则保存 D2D通信组应 用层标识 GID与 D2D组空口标识的映射信息。 除了周期性的广播组标识映射信息， UE1竞争到资源之后会广播发送组播通信数 据， 所发送数据包在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带 生成的 D2D组空口标识。此外， 组播通信数据包可在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带 D2D组播通信指示信息以及 UE1的空口标识。
Officer B, C， D的 UE2， UE3及 UE4对预先获知的公共安全无线资源进行监听。 假设 UE2， UE3 , UE4监听到有数据包发送， 则接收该数据包， 解析 MAC控制单元 和 /或子头， 或者 RLC子头， 或者 PDCP子头的 D2D组空口标识。 UE2和 UE3判断该 D2D空口标识与自己所属的 D2D通信组对应的 D2D空口标识一致， 则 UE2和 UE3 进一步进行 MAC/RLC/PDCP解析处理并投递给高层。 而对于 UE4则判断自己不属于 该 D2D组标识对应的 D2D组的成员， 因此丢弃该数据包。 这种 UE自己生成 D2D组空口标识的方式有可能产生不同的 UE将不同的 D2D通 信组应用层标识映射到同一个 D2D组空口标识的情况， 对于这种情况， UE可继续通 过组播通信数据包携带的 UE1的空口标识，或 IP层的组播地址或是应用层携带的 D2D 组信息来进一步判断是否是对应正确的 D2D通信组，由高层判断是接收该数据包还是 丢弃。此外也有可能出现不同的 UE将同一个 D2D通信组应用层标识映射到不同 D2D 组空口标识的情况， 因此监听 UE需要在保存 D2D通信组应用层标识和 D2D组空口 标识映射关系的同时， 记录相应的发送 UE的空口标识， 用于后续组播通信数据包接 收的判断处理。 实例 5 在公共安全场景， OfficerA, B， C， D使用具备 D2D功能的公共安全 UE1， UE2, UE3及 UE4。 OfficerA, B， C， D都订阅了公共安全服务， 并且 UE1， UE2, UE3配 置属于 D2D通信组 X， 而 UE4属于 D2D通信组 Y。 在 OfficerA, B， C， D到达救援 地点之前， 预先获知 D2D广播通信标识 BID以及用于公共安全的无线资源信息， 其 中无线资源信息可包含频点及频带信息。在到达救援地点之后， UE都不在网络覆盖范 围内， 但是 UE1， UE2, UE3 , UE4彼此在 D2D通信范围内。 在救援地点， Officer A希望发起广播通信， 告知组内其他 Officer相关信息。 则
OfficerA的 UE1监听预分配的无线资源使用情况，通过竞争的方式获取资源，图 18 是 根据本发明实例 5的无覆盖场景 D2D广播通信流程图， 如图 18所示。 竞争到资源之 后 UE1广播发送数据包， 所发送数据包在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带预分配的 D2D广播通信标识 BID。 此外， 广播通信数据包可在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带 D2D广播通信指示 以及 UE1的空口标识信息。
Officer B, C， D的 UE2， UE3及 UE4对预先获知的公共安全无线资源进行监听。 假设 UE2， UE3 , UE4监听到有数据包发送， 则接收该数据包， 解析 MAC控制单元 和 /或子头， 或者 RLC子头， 或者 PDCP子头的 D2D广播通信标识， 判断是广播通信 后， 则进一步进行 MAC/RLC/PDCP解析处理并投递给高层。
实施例二 本实施例给出有中央节点覆盖场景下 D2D组播广播通信建立方法。该实施例的特 征是有中央节点进行资源协调以及 D2D组播 /广播空口标识的分配。 中央节点可以是 e B, 也可以是 UE充当的执行资源及标识分配的普通 UE。 该实施例可用于公共安全 场景， 也可用于商业场景。 以下通过实例 6至实例 9详细阐述。 实例 6 在公共安全场景， OfficerA, B， C， D使用具备 D2D功能的公共安全 UE1， UE2, UE3及 UE4。 OfficerA, B， C， D都订阅了公共安全服务， 并且 UE1， UE2, UE3配 置属于 D2D通信组 X， 而 UE4属于 D2D通信组 Y。 在 OfficerA, B， C， D到达救援 地点之前， 预先获知 D2D通信组应用层标识。 在到达救援地点之后， UE在网络覆盖 范围内或是虽然无网络覆盖但是在已选好的中央节点覆盖范围内， 并且 UE1， UE2, UE3 , UE4彼此在 D2D通信范围内。 在救援地点， Officer A希望发起组播通信， 告知组内其他 Officer相关信息。 则 OfficerA的 UE1首先向 CN/e B发送组通信请求消息，该消息包含预先获取的分配的 D2D通信组应用层标识， 图 19是根据本发明实例 6的有覆盖场景 D2D组播通信流程 图， 如图 19所示。此外组通信请求消息中还可包含通信组优先级， 一个或多个组播业 务流的 QoS信息等。
CN/eNB 节点收到该消息后， 进行接纳控制， 根据组播通信请求消息包含的组播 通信业务流 QoS信息，确定接受的组播 /广播通信业务流，并分配组通信空口标识以及 空口资源配置。 如果业务流需要持续一段时间， 如语音或是视频， 则 CN/eNB可为其 分配半静态的资源调度。
CN/eNB完成接纳控制及资源分配后， 发送组通信确认消息给 UE1， 其中包含接 纳的业务流， 分配的组通信空口标识， 分配给组播通信的空口资源及配置信息等。 组 播空口资源信息包含以下字段的任意组合：组播通信的频点，频带资源，帧 /子帧偏移， 子帧模式， 时隙， 资源块， 资源重复周期等。 此外还可包含对应的资源的资源配置信 息， 如资源承载标识， 媒体接入控制 MAC配置信息， 无线链路控制 RLC配置信息， 分组数据汇聚协议 PDCP配置信息， 逻辑信道配置信息。 此外 CN/eNB周期性的广播发送 D2D通信组应用层标识与组通信空口标识的映射 信息， 以及组播通信对应的子帧模式信息。 此外还可以广播发送对应的资源的资源配 置信息， 如资源承载标识， 媒体接入控制 MAC配置信息， 无线链路控制 RLC配置信 息， 分组数据汇聚协议 PDCP配置信息， 逻辑信道配置信息。 相应的， UE1， UE2, UE3 , UE4接收周期性广播的 D2D通信组应用层标识 GID与组通信空口标识的映射 信息。 UE2和 UE3判断接收到的 D2D通信组应用层标识和预先获知 D2D通信组应用 层标识一致， 则 UE2和 UE3保存 D2D通信组应用层标识与组通信空口标识的映射， 组播通信对应的子帧模式以及资源配置信息， 并根据资源配置信息进行相应的配置。
UE1在 CN/eNB分配的资源上发送 D2D组播通信数据包， 其数据包可携带 D2D 组空口标识。 如 UE1可在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子 头携带 D2D组空口标识和 /或 D2D组播指示字段。 或者 UE1发送的 D2D组播通信数 据包使用 D2D 组空口标识进行加扰。 或者 UE1 发送的 D2D 组播通信数据包使用 CN/eNB分配的对应于 D2D组空口标识的资源， D2D组播通信数据包通过发送数据包 使用的资源位置隐式的携带 D2D组空口标识信息。
UE2, UE3及 UE4对接收 D2D组播有兴趣， 并且 UE2和 UE3 已经获取了 D2D 通信组 X的 D2D组空口标识。 UE2和 UE3根据之前获取的组播通信对应的子帧模式 信息对相应的子帧进行监听并接收 D2D组播数据包。 如果接收 D2D组播数据包， 则 进一步根据加扰情况， 资源位置或是 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头判断对应于该 D2D组播数据包的 D2D空口标识。 如果判断该 D2D空口标 识对应于 UE2和 UE3加入的 D2D组，则 UE2和 UE3完成 MAC/RLC/PDCP的解析处 理并投递给高层。 实例 7 在公共安全场景， Officer A, B， C， D使用具备 D2D功能的公共安全 UE1， UE2, UE3及 UE4。 Officer A, B， C， D都订阅了公共安全服务， 并且 UE1， UE2, UE3都 配置属于 D2D通信组 X， 而 UE4属于 D2D通信组 Y。 在 Officer A, B， C， D到达救 援地点之前， 预先获知 D2D通信组应用层标识 GID。 在到达救援地点之后， UE在网 络覆盖范围内或是虽然无网络覆盖但是在已选好的中央节点覆盖范围内， 并且 UE1， UE2, UE3 , UE4彼此在 D2D通信范围内。 在救援地点， Officer A希望发起组播通信， 告知组内其他 Officer相关信息。 则 Officer A的 UE1首先向 CN/e B发送组通信请求消息，该消息包含预先获取的分配的 D2D通信组应用层标识， 图 20是根据本发明实例 7的有覆盖场景 D2D组播通信流程 图， 如图 20所示。此外组通信请求消息中还可包含通信组优先级， 一个或多个组播业 务流的 QoS信息等。
CN/eNB 节点收到该消息后， 进行接纳控制， 根据组播通信请求消息包含的组播 通信业务流 QoS信息， 确定接受的组播通信业务流， 并分配组通信空口标识以及空口 资源配置。 CN/eNB完成接纳控制及资源分配后， 发送组通信确认消息给 UE1， 组通信确认 消息可包含接纳的业务流信息。此外 CN/eNB周期性的广播发送 D2D通信组应用层标 识与组通信空口标识的映射信息。 相应的， UE1， UE2, UE3 , UE4接收周期性广播的 D2D通信组应用层标识与组通信空口标识的映射信息。UE2和 UE3判断接收到的 D2D 通信组应用层标识和预先获知 D2D通信组应用层标识一致，则 UE2和 UE3保存 D2D 通信组应用层标识与组通信空口标识的映射信息。 之后 CN/eNB广播发送包含 D2D组通信资源分配的调度信息，该调度信息中可包 含发送端 UE1的指示信息。对 D2D通信组 X感兴趣的 UE1， UE2和 UE3检测针对相 应的 D2D组空口标识对应的资源分配信息。 如果检测到资源分配信息存在， 则 UE1 在 CN/eNB分配的资源上发送 D2D组播通信数据包， D2D组播通信数据包通过发送 数据包使用的资源位置隐式的携带 D2D组空口标识信息。
UE2, UE3在检测到的对应于 D2D通信组 X的资源分配上监听并接收 D2D组播 数据包， 完成 MAC/RLC/PDCP的解析处理并投递给高层。 实例 8 在公共安全场景， Officer A, B， C， D使用具备 D2D功能的公共安全 UE1， UE2, UE3及 UE4。 Officer A, B， C， D都订阅了公共安全服务， 并且 UE1， UE2, UE3都 配置属于 D2D通信组 X， 而 UE4属于 D2D通信组 Y。 在 Officer A， B， C， D到达救 援地点之前， 预先获知 D2D通信组应用层标识 GID。 在到达救援地点之后， UE在网 络覆盖范围内或是虽然无网络覆盖但是在已选好的中央节点覆盖范围内， 并且 UE1， UE2, UE3 , UE4彼此在 D2D通信范围内。 在救援地点， Officer A希望发起组播通信， 告知组内其他 Officer相关信息。 则
Officer A的 UE1首先向 CN/e B发送组通信请求消息，该消息包含预先获取的分配的 D2D通信组应用层标识， 图 21是根据本发明实例 8的有覆盖场景 D2D组播通信流程 图， 如图 21所示。
CN/eNB 节点收到该消息后， 进行接纳控制， 并分配组通信空口标识以及空口资 源配置。 如果业务流需要持续一段时间， 如语音或是视频， 则 CN/eNB可为其分配半 静态的资源调度。
CN/eNB完成接纳控制及资源分配后，发送组通信确认消息给 UE1。此外 CN/eNB 周期性的广播发送 D2D通信组应用层标识 GID与组通信空口标识的映射信息以及不 针对特定 UE的 D2D组播通信资源。 组播空口资源信息包含以下字段的任意组合： 组 播通信的频点， 频带资源， 帧 /子帧偏移， 子帧模式， 时隙， 资源块， 资源重复周期等。 相应的， UE1， UE2, UE3 , UE4接收周期性广播的 D2D通信组应用层标识与组通信 空口标识的映射信息。 UE1， UE2和 UE3判断接收到的 D2D通信组应用层标识和预 先获知 D2D通信组应用层标识一致， 则 UE1， UE2和 UE3保存 D2D通信组应用层标 识与组通信空口标识的映射信息以及 D2D组播通信空口资源信息。 之后 UE1监听 CN/eNB分配的不针对特定 UE的 D2D组播通信无线资源使用情 况， 通过竞争的方式获取资源。 竞争到资源后 UE1广播发送组播通信数据， 所发送数 据包在 MAC控制单元和 /或子头，或者 RLC子头，或者 PDCP子头携带预分配的 D2D 组标识。 此外， 组播通信数据包可在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头携带 D2D组播通信指示以及 UE1的空口标识信息。 Officer B， C， D的 UE2， UE3根据获取到的不针对特定 UE的 D2D组播通信无 线资源信息， 在无线资源进行监听。 假设 UE2， UE3监听到有数据包发送， 则接收该 数据包， 解析 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头的 D2D组 标识。 UE2和 UE3判断自己属于该 D2D组标识对应的 D2D组的成员，则 UE2和 UE3 进一步进行 MAC/RLC/PDCP解析处理并投递给高层。 实例 9 在公共安全场景， Officer A， B， C使用具备 D2D功能的公共安全 UE1， UE2, UE3。 Officer A， B， C都订阅了公共安全服务。 在到达救援地点之后， UE在网络覆 盖范围内或是虽然无网络覆盖但是在已选好的中央节点覆盖范围内， 并且 UE1， UE2, UE3彼此在 D2D通信范围内。 在救援地点， Officer A希望发起广播通信， 告知其他 Officer相关信息， 则 Officer
A的 UE1首先向 CN/e B发送广播通信请求消息， 该消息包含可包含通信组优先级， 一个或多个广播业务流的 QoS信息等， 图 22是根据本发明实例 9的有覆盖场景 D2D 组播通信流程图， 如图 22所示。
CN/e B 节点收到该消息后， 进行接纳控制， 分配广播通信空口标识以及空口资 源配置。 如果业务流需要持续一段时间， 如语音或是视频， 则 CN/eNB可为其分配半 静态的资源调度。
CN/eNB完成接纳控制及资源分配后， 发送广播通信确认消息给 UE1， 其中包含 接纳的业务流， 分配的广播通信空口标识， 分配给广播通信的空口资源等。 广播空口 资源信息包含以下字段的任意组合： 广播通信的频点， 频带资源， 帧 /子帧偏移， 子帧 模式， 时隙， 资源块， 资源重复周期等。 此外 CN/eNB周期性的广播发送广播通信空口标识以及广播通信对应的子帧模式 信息。 相应的， UE1， UE2, UE3 并保存接收周期性广播的广播通信空口标识以及广 播通信子帧模式信息。
UE1在 CN/eNB分配的资源上发送 D2D广播通信数据包， 其数据包可携带 D2D 广播空口标识。 如 UE1可在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP 子头携带 D2D广播标识和或 D2D广播指示字段。 或者 UE1发送的 D2D广播通信数 据包使用 D2D广播空口标识进行加扰。
UE2及 UE3对接收 D2D广播有兴趣， 并且 UE2和 UE3已经获取了 D2D广播空 口标识。 UE2和 UE3根据之前获取的广播通信对应的子帧模式信息对相应的子帧进行 监听并接收 D2D广播数据包。 如果接收到数据包， 则进一步根据加扰情况或是 MAC 控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头保护的广播空口标识判断对应 于该数据包是否是广播包，如果是则 UE2和 UE3完成 MAC/RLC/PDCP的解析处理并 投递给高层。 实例 10 在公共安全场景， Officer A， B， C使用具备 D2D功能的公共安全 UE1， UE2, UE3。 Officer A, B， C都订阅了公共安全服务。 在 Officer A， B， C到达救援地点之 前， 预先获知 D2D广播通信空口标识信息。 在到达救援地点之后， UE在网络覆盖范 围内或是虽然无网络覆盖但是在已选好的中央节点覆盖范围内， 并且 UE1， UE2, UE3 彼此在 D2D通信范围内。 在救援地点， Officer A希望发起广播通信， 告知组内其他 Officer相关信息。 则 Officer A的 UE1首先向 CN/e B发送广播通信请求消息， 图 23是根据本发明实例 10 的有覆盖场景 D2D广播通信流程图， 如图 23所示， CN/eNB节点收到该消息后， 进 行接纳控制， 并分配和或调整广播通信空口资源配置。 CN/eNB 完成接纳控制及资源分配后， 发送广播通信确认消息给 UE1。 此外
CN/eNB周期性的广播发送不针对特定 UE的 D2D广播通信资源。 广播空口资源信息 包含以下字段的任意组合： 广播通信的频点， 频带资源， 帧 /子帧偏移， 子帧模式， 时 隙， 资源块， 资源重复周期等。 相应的， UE1， UE2, UE3 接收并保存周期性广播的 D2D广播通信资源信息。 之后 UE1监听 CN/eNB分配的不针对特定 UE的 D2D广播通信无线资源使用情 况， 通过竞争的方式获取资源。 竞争到资源后 UE1广播发送广播通信数据， 所发送数 据包在 MAC控制单元和 /或子头，或者 RLC子头，或者 PDCP子头携带预分配的 D2D 广播空口标识。此外，广播通信数据包可在 MAC控制单元和 /或子头，或者 RLC子头， 或者 PDCP子头携带 D2D广播通信指示以及 UE1的空口标识信息。 UE2, UE3根据获取到的不针对特定 UE的 D2D广播通信无线资源信息， 在无线 资源进行监听。 假设 UE2， UE3监听到有数据包发送， 则接收该数据包， 解析 MAC 控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头的 D2D广播空口标识， 进一步 进行 MAC/RLC/PDCP解析处理并投递给高层。
实施例三 本实施例给出部分覆盖场景下 D2D组播广播通信建立方法。该实施例的特征是中 央节点不能覆盖所有的进行 D2D组播 /广播通信的 UE， UE依然需要独立的完成资源 竞争以及 D2D 组播 /广播空口标识的映射或预定义的方式获取。 以下通过实例 11-12 详细阐述。 实例 11 在公共安全场景， Officer A， B， C使用具备 D2D功能的公共安全 UE1， UE2, UE3。 Officer A， B， C都订阅了公共安全服务， 并且 UE1， UE2, UE3 都配置属于 D2D通信组 X。 在 Officer A， B， C到达救援地点之前， 预先获知 D2D组播 /广播通信 空口标识信息以及可能用于广播 /组播通信的资源集合信息。 到达救援地点之后， UE1 在网络覆盖范围内， 而 UE2和 UE3无网络覆盖， 此外 UE1， UE2, UE3彼此在 D2D 通信范围内。 在救援地点， Officer A希望发起广播 /组播通信， 告知组内其他 Officer相关信息。 则 Officer A的 UE1首先向 CN/e B发送广播 /组播通信请求消息，图 24是根据本发明 实例 11的有覆盖场景 D2D广播通信流程图， 如图 24所示。 CN/eNB节点收到该消息 后， 进行接纳控制， 并分配和 /或调整不针对特定 UE的广播 /组播通信空口资源配置， 该资源配置应该与 UE预先获知的 D2D广播 /组播通信的资源集合信息一致，可以是其 子集。
CN/eNB完成接纳控制及资源分配后， 发送广播 /组播通信确认消息给 UE1。 此外 CN/eNB周期性的广播发送广播 /组播空口标识以及相应的不针对特定 UE的 D2D广播 /组播通信资源。 广播 /组播空口资源信息包含以下字段的任意组合： 组播 /广播通信的 频点， 频带资源， 帧 /子帧偏移， 子帧模式， 时隙， 资源块， 资源重复周期等。 相应的， UE1 , UE2, UE3接收并保存周期性广播的 D2D广播 /组播通信资源信息。 之后 UE1监听 CN/eNB分配的不针对特定 UE的 D2D组播通信无线资源使用情 况， 通过竞争的方式获取资源。 竞争到资源后 UE1广播发送组播通信数据， 所发送数 据包在 MAC控制单元和 /或子头，或者 RLC子头，或者 PDCP子头携带预分配的 D2D 广播 /组播空口标识。 此外， 广播 /组播通信数据包可在 MAC 控制单元和 /或子头， 或 者 RLC子头，或者 PDCP子头携带 D2D广播 /组播通信指示以及 UE1的空口标识信息。
UE2和 UE3根据预先获知可能用于广播 /组播通信的资源集合信息， 在相应的资 源上进行监听。 假设 UE2， UE3监听到有数据包发送， 则接收该数据包， 解析 MAC 控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子头的 D2D广播空口标识， 进一步 进行 MAC/RLC/PDCP解析处理并投递给高层。 实例 12 在公共安全场景， Officer A， B， C使用具备 D2D功能的公共安全 UE1， UE2,
UE3。 Officer A， B， C都订阅了公共安全服务， 并且 UE1， UE2, UE3 都配置属于 D2D通信组 X。 在 Officer A， B， C到达救援地点之前， 预先获知 D2D组播 /广播通信 空口标识信息以及可能用于广播 /组播通信的资源集合信息。 到达救援地点 后， IJE1 在网络覆盖范围内， 而 UE2和 UE3无网络覆盖， 此外 UE1， UE2, UE3彼此在 D2D 通信范围内。 在救援地点， Officer A希望发起组播通信， 告知组内其他 Officer相关信息。 则 Officer A的 UEl首先向 CN/e B发送组通信请求消息，该消息包含预先获取的分配的 D2D通信组应用层标识 GID， 图 25是根据本发明实例 12的部分覆盖场景 D2D组播 通信流程图， 如图 25所示。此外组通信请求消息中还可包含通信组优先级， 一个或多 个组播业务流的 QoS信息等。
CN/eNB 节点收到该消息后， 进行接纳控制， 根据组播通信请求消息包含的组播 通信业务流 QoS信息，确定接受的组播 /广播通信业务流，并分配组通信空口标识以及 空口资源配置。 如果业务流需要持续一段时间， 如语音或是视频， 则 CN/eNB可为其 分配半静态的资源调度。
CN/eNB完成接纳控制及资源分配后， 发送组通信确认消息给 UE1， 其中包含接 纳的业务流， 分配的组通信空口标识， 分配给组播通信的空口资源及配置信息等。 组 播空口资源信息包含以下字段的任意组合：组播通信的频点，频带资源，帧 /子帧偏移， 子帧模式， 时隙， 资源块， 资源重复周期等。 此外还可包含对应的资源的资源配置信 息， 如资源承载标识， 媒体接入控制 MAC配置信息， 无线链路控制 RLC配置信息， 分组数据汇聚协议 PDCP配置信息， 逻辑信道配置信息。 此外 CN/eNB周期性的广播发送 D2D通信组应用层标识与组通信空口标识的映射 信息， 以及组播通信对应的子帧模式信息。 此外还可以广播发送对应的资源的资源配 置信息， 如资源承载标识， 媒体接入控制 MAC配置信息， 无线链路控制 RLC配置信 息， 分组数据汇聚协议 PDCP配置信息， 逻辑信道配置信息。 相应的， UE1接收周期 性广播的 D2D通信组应用层标识与组通信空口标识的映射信息。与此同时， UE1周期 性的广播发送 D2D通信组应用层标识与组通信空口标识的映射信息，以及组播通信对 应的资源信息。此外还可以广播发送对应的资源的资源配置信息。 UE2和 UE3判断接 收到的 D2D通信组应用层标识和预先获知 D2D通信组应用层标识一致， 则 UE2和 UE3保存 D2D通信组应用层标识与组通信空口标识的映射，组播通信对应的资源以及 资源配置信息， 并根据资源配置信息进行相应的配置。
UE1在 CN/eNB分配的资源上发送 D2D组播通信数据包， 其数据包可携带 D2D 组空口标识。 如 UE1可在 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP子 头携带 D2D组空口标识和 /或 D2D组播指示字段。 或者 UE1发送的 D2D组播通信数 据包使用 D2D 组空口标识进行加扰。 或者 UE1 发送的 D2D 组播通信数据包使用 CN/e B分配的对应于 D2D组空口标识的资源， D2D组播通信数据包通过发送数据包 使用的资源位置隐式的携带 D2D组空口标识信息。
UE2, UE3对接收 D2D组播有兴趣， 并且 UE2和 UE3已经获取了 D2D通信组 X 的 D2D组空口标识。 UE2和 UE3根据之前获取的组播通信对应的子帧模式信息对相 应的子帧进行监听并接收 D2D组播数据包。 如果接收 D2D组播数据包， 则进一步根 据加扰情况， 资源位置或是 MAC控制单元和 /或子头， 或者 RLC子头， 或者 PDCP 子头判断对应于该 D2D组播数据包的 D2D通信组空口标识。如果判断该 D2D通信组 空口标识对应于 UE2和 UE3加入的 D2D组， 则 UE2和 UE3完成 MAC/RLC/PDCP 的解析处理并投递给高层。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 并且在某些情况下， 可以以不同于此处 的顺序执行所示出或描述的步骤， 或者将它们分别制作成各个集成电路模块， 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明不限制于任 何特定的硬件和软件结合。 以上仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技术人 员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的任何 修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。 工业实用性 通过本发明实施例及优选实施方式， 不仅解决了相关技术中存在 UE在无覆盖或 有覆盖以及部分覆盖场景下无法实现 D2D组播及广播通信的问题， 进而使得 UE在无 覆盖或有覆盖以及部分覆盖场景下顺利进行 D2D组播及广播通信。

Claims

权 利 要 求 书
1. 一种设备到设备 D2D组播 /广播通信处理方法， 包括： 获取用于标识用户设备和 /或 D2D 组播 /广播通信的空口标识， 以及所述 D2D组播 /广播通信的资源信息；
依据所述空口标识在所述资源信息对应的资源上进行 D2D组播 /广播通信 处理。
2. 根据权利要求 1所述的方法， 其中， 依据所述空口标识在所述资源信息对应的 资源上进行 D2D组播 /广播通信处理包括： 依据所述空口标识在所述资源信息对应的资源上发送 D2D组播 /广播通信 数据包； 和 /或，
依据所述空口标识在所述资源信息对应的资源上接收 D2D组播 /广播通信 数据包。
3. 根据权利要求 1所述的方法， 其中， 获取用于标识用户设备和 /或 D2D组播 /广 播通信的所述空口标识包括以下至少之一：
从 D2D应用服务器获取所述空口标识； 根据第一预定规则， 通过将 D2D组播 /广播应用层标识映射到空口标识的 方式获取所述空口标识；
根据第二预定规则， 通过将 D2D组播 /广播 IP地址映射到空口标识的方式 获取所述空口标识； 获取系统预先默认的所述空口标识；
根据 D2D 组播 /广播应用层标识和 /或用户设备直通标识生成所述空口标 识；
从相邻节点获取所述空口标识， 其中， 所述相邻节点周期性广播包含所述 空口标识的消息；
从中央节点获取所述空口标识，其中，所述中央节点用于对所述 D2D组播
/广播通信进行控制。
4. 根据权利要求 3所述的方法， 其中， 从所述中央节点获取所述空口标识包括： 向所述中央节点发送包含用户设备直通标识和 /或 D2D组播 /广播应用层标 识的 D2D组播 /广播通信请求；
接收所述中央节点依据所述 D2D组播 /广播通信请求分配的所述空口标识。
5. 根据权利要求 3所述的方法， 其中， 从所述中央节点获取所述空口标识包括： 接收包含所述空口标识的消息， 所述消息通过周期性广播的方式由所述中 央节点发送。
6. 根据权利要求 1所述的方法， 其中， 获取用于所述 D2D组播 /广播通信的所述 资源信息包括以下至少之一：
从 D2D应用服务器获取所述资源信息； 获取系统默认的所述资源信息； 采用竞争的方式获取所述资源信息；
从相邻节点获取所述资源信息， 其中， 所述相邻节点周期性广播包含所述 资源信息的消息；
从中央节点获取所述资源信息，其中，所述中央节点用于对所述 D2D组播
/广播通信进行控制。
7. 根据权利要求 6所述的方法， 其中， 从所述中央节点获取所述资源信息包括： 接收包含所述资源信息的消息， 所述消息通过周期性广播的方式由所述中 央节点发送。
8. 根据权利要求 6所述的方法， 其中， 从所述中央节点获取所述资源信息包括： 向所述中央节点发送 D2D组播 /广播通信请求；
接收所述中央节点依据所述 D2D组播 /广播通信请求分配的资源的所述资 源信息。
9. 根据权利要求 8所述的方法， 其中， 所述组播 /广播通信请求包含有以下至少之
D2D组播 /广播应用层标识、 用户设备直通标识、 D2D组播 /广播 IP地址、 组播 /广播通信指示、 D2D组播 /广播优先级、 一个或多个组播 /广播通信业务流 服务质量 QoS信息。
10. 根据权利要求 9所述的方法， 其中， 在所述组播 /广播通信请求包括一个或多个 组播 /广播通信业务流服务质量 QoS 信息的情况下， 接收所述中央节点依据所 述 D2D组播 /广播通信请求分配的资源的所述资源信息包括： 接收所述中央节点发送的组播 /广播通信确认消息， 其中， 所述中央节点根 据所述组播 /广播通信请求包括的所述一个或多个组播 /广播通信业务流服务质 量 QoS信息进行接纳控制， 确定接受的组播 /广播通信业务流， 所述组播 /广播 通信确认消息包括以下至少之一： 所述中央节点分配的所述资源的资源信息、 接受的所述组播 /广播通信业务流。
11. 根据权利要求 6至 10中任一项所述的方法，其中，所述资源信息包含有以下至 少之一： 组播 /广播通信的频点信息、 组播 /广播通信的频带资源信息、 组播 /广播通 信的帧偏移信息、 组播 /广播通信的子帧偏移信息、 组播 /广播通信的子帧模式 信息、 组播 /广播通信的时隙信息、 组播 /广播通信的资源块信息、 组播 /广播通 信的资源重复周期信息、与所述资源信息对应的所述 D2D组播 /广播空口标识、 发送 D2D组播 /广播通信数据包的用户设备的空口标识信息。
12. 根据权利要求 6至 10中任一项所述的方法，其中，所述资源信息包含对应的资 源的资源配置信息以下至少之一：
资源承载标识， 媒体接入控制 MAC配置信息， 无线链路控制 RLC配置信 息， 分组数据汇聚协议 PDCP配置信息， 逻辑信道配置信息。
13. 根据权利要求 2所述的方法， 其中， 依据所述空口标识在所述资源信息对应的 资源上发送所述 D2D组播 /广播通信数据包包括： 在所述资源上发送携带有所述用户设备空口标识、 所述 D2D组播 /广播空 口标识、 D2D组播 /广播指示至少之一的所述 D2D组播 /广播通信数据包。
14. 根据权利要求 13所述的方法，其中，通过以下方式至少之一在所述资源上发送 携带有用户设备空口标识、 D2D组播 /广播空口标识、 D2D组播 /广播指示至少 之一的所述 D2D组播 /广播通信数据包： 通过在所述 D2D组播 /广播通信数据包的媒体接入控制 MAC子头和 /或控 制单元， 或者无线链路控制 RLC子头，或者分组数据汇聚协议 PDCP子头中携 带有所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 所述 D2D组播 / 广播指示至少之一的方式， 在所述资源上发送携带有所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 所述 D2D组播 /广播指示至少之一的所述 D2D 组播 /广播通信数据包；
通过采用所述用户设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D 组播 /广播指示至少之一对所述 D2D 组播 /广播通信资源分配控制信息和 /或数 据包进行加扰的方式， 在所述资源上发送携带有所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 所述 D2D组播 /广播指示至少之一的所述 D2D组播 / 广播通信数据包；
通过发送所述 D2D组播 /广播通信数据包使用的资源位置隐式的携带所述 用户设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D组播 /广播指示至 少之一的方式，在所述资源上发送携带有所述用户设备空口标识、所述 D2D组 播 /广播空口标识、 所述 D2D组播 /广播指示至少之一的所述 D2D组播 /广播通 信数据包， 其中， 发送所述 D2D组播 /广播通信数据包使用的所述资源位置对 应于所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 所述 D2D组播 / 广播指示至少之一。
15. 根据权利要求 2所述的方法， 其中， 依据所述空口标识在所述资源信息对应的 资源上接收所述 D2D组播 /广播通信数据包包括：
依据所述 D2D组播 /广播空口标识判断所述 D2D组播 /广播通信数据包的接 收者是否属于所述空口标识对应的组播 /广播通信组；
在判断结果为是的情况下， 对所述 D2D组播 /广播通信数据包进行解析处 理， 并将解析后的数据包发送给高层； 和 /或， 在判断结果为否的情况下， 丢弃 所述 D2D组播 /广播通信数据包。
16. 一种设备到设备 D2D组播 /广播通信处理装置， 包括： 获取模块， 设置为获取用于标识用户设备和 /或 D2D组播 /广播通信的空口 标识， 以及所述 D2D组播 /广播通信的资源信息； 处理模块， 设置为依据所述空口标识在所述资源信息对应的资源上进行 D2D组播 /广播通信处理。
17. 根据权利要求 16所述的装置， 其中， 所述处理模块包括： 发送单元， 设置为依据所述空口标识在所述资源信息对应的资源上发送 D2D组播 /广播通信数据包； 和 /或， 接收单元， 设置为依据所述空口标识在所述资源信息对应的资源上接收 D2D组播 /广播通信数据包。
18. 根据权利要求 16所述的装置， 其中， 所述获取模块包括以下至少之一：
第一获取单元， 设置为从 D2D应用服务器获取所述空口标识； 第二获取单元， 设置为根据第一预定规则， 通过将 D2D组播 /广播应用层 标识映射到空口标识的方式获取所述空口标识；
第三获取单元， 设置为根据第二预定规则， 通过将 D2D组播 /广播 IP地址 映射到空口标识的方式获取所述空口标识； 第四获取单元， 设置为获取系统预先默认的所述空口标识；
生成单元， 设置为根据 D2D组播 /广播应用层标识和 /或用户设备直通标识 生成所述空口标识；
第五获取单元， 设置为从相邻节点获取所述空口标识， 其中， 所述相邻节 点周期性广播包含所述空口标识的消息；
第六获取单元， 设置为从中央节点获取所述空口标识， 其中， 所述中央节 点用于对所述 D2D组播 /广播通信进行控制。
19. 根据权利要求 18所述的装置， 其中， 所述第五获取单元包括： 第一发送子单元， 设置为向所述中央节点发送包含用户设备直通标识和 / 或 D2D组播 /广播应用层标识的 D2D组播 /广播通信请求； 第一接收子单元， 设置为接收所述中央节点依据所述 D2D组播 /广播通信 请求分配的所述空口标识。
20. 根据权利要求 16所述的装置， 其中， 所述获取模块包括以下至少之一： 第七获取单元， 设置为从 D2D应用服务器获取所述资源信息； 第八获取单元， 设置为获取系统默认的所述资源信息； 第九获取单元， 设置为采用竞争的方式获取所述资源信息；
第十获取单元， 设置为从相邻节点获取所述资源信息， 其中， 所述相邻节 点周期性广播包含所述资源信息的消息； 第十一获取单元， 设置为从中央节点获取所述资源信息， 其中， 所述中央 节点用于对所述 D2D组播 /广播通信进行控制。
21. 根据权利要求 20所述的装置， 其中， 所述第十一获取单元包括： 第二发送子单元， 设置为向所述中央节点发送 D2D组播 /广播通信请求； 第二接收子单元， 设置为接收所述中央节点依据所述 D2D组播 /广播通信 请求分配的资源的所述资源信息。
22. 根据权利要求 17所述的装置， 其中， 所述发送单元包括： 第三发送子单元，设置为在所述资源上发送携带有所述用户设备空口标识、 所述 D2D组播 /广播空口标识、 D2D组播 /广播指示至少之一的所述 D2D组播 / 广播通信数据包。
23. 根据权利要求 22所述的装置， 其中， 所述第三发送子单元包括以下至少之一： 第一发送次子单元， 设置为通过在所述 D2D组播 /广播通信数据包的媒体 接入控制 MAC子头和 /或控制单元，或者无线链路控制 RLC子头，或者分组数 据汇聚协议 PDCP子头中携带有所述用户设备空口标识、 所述 D2D组播 /广播 空口标识、 所述 D2D组播 /广播指示至少之一的方式， 在所述资源上发送携带 有所述用户设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D组播 /广播 指示至少之一的所述 D2D组播 /广播通信数据包； 第二发送次子单元， 设置为通过采用所述用户设备空口标识、所述 D2D组 播 /广播空口标识、 所述 D2D组播 /广播指示至少之一对所述 D2D组播 /广播通 信资源分配控制信息和 /或数据包进行加扰的方式，在所述资源上发送携带有所 述用户设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D组播 /广播指示 至少之一的所述 D2D组播 /广播通信数据包；
第三发送次子单元， 设置为通过发送所述 D2D组播 /广播通信数据包使用 的资源位置隐式的携带所述用户设备空口标识、所述 D2D组播 /广播空口标识、 所述 D2D组播 /广播指示至少之一的方式， 在所述资源上发送携带有所述用户 设备空口标识、所述 D2D组播 /广播空口标识、所述 D2D组播 /广播指示至少之 一的所述 D2D组播 /广播通信数据包，其中，发送所述 D2D组播 /广播通信数据 包使用的所述资源位置对应于所述用户设备空口标识、 所述 D2D组播 /广播空 口标识、 所述 D2D组播 /广播指示至少之一。
24. 根据权利要求 17所述的装置， 其中， 所述接收单元包括： 判断子单元， 设置为依据所述 D2D组播 /广播空口标识判断所述 D2D组播
/广播通信数据包的接收者是否属于所述空口标识对应的组播 /广播通信组； 解析子单元， 设置为在所述判断子单元的判断结果为是的情况下， 对所述 D2D组播 /广播通信数据包进行解析处理，并将解析后的数据包发送给高层；和 /或， 丢弃子单元， 设置为在所述判断子单元的判断结果为否的情况下， 丢弃所 述 D2D组播 /广播通信数据包。
25. 一种用户设备， 包括权利要求 16至 24中任一项所述的装置。
PCT/CN2014/078347 2013-11-01 2014-05-23 设备到设备组播/广播通信处理方法、装置及用户设备 WO2015062260A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310535994.2A CN104619008B (zh) 2013-11-01 2013-11-01 设备到设备组播/广播通信处理方法、装置及用户设备
CN201310535994.2 2013-11-01

Publications (1)

Publication Number Publication Date
WO2015062260A1 true WO2015062260A1 (zh) 2015-05-07

Family

ID=53003251

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/078347 WO2015062260A1 (zh) 2013-11-01 2014-05-23 设备到设备组播/广播通信处理方法、装置及用户设备

Country Status (2)

Country Link
CN (1) CN104619008B (zh)
WO (1) WO2015062260A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112399559A (zh) * 2019-08-13 2021-02-23 大唐移动通信设备有限公司 一种反馈资源选择方法和终端

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341774B (zh) * 2015-07-10 2020-03-20 华为技术有限公司 一种数据传输方法、网络设备及用户设备
CN106470449B (zh) * 2015-08-14 2020-04-10 电信科学技术研究院 一种数据收发、中继方法、装置及通信系统
CN106612554B (zh) * 2015-10-23 2020-06-02 华为技术有限公司 分配时域资源的方法、基站和用户设备
CN106792564B (zh) * 2015-11-20 2020-05-29 中兴通讯股份有限公司 一种系统广播消息的传输方法和装置
CN108605232B (zh) * 2016-06-30 2021-05-11 华为技术有限公司 一种组通信的方法、设备及系统
CN108401226B (zh) * 2017-02-04 2021-11-30 中兴通讯股份有限公司 信息传输、处理方法及装置、设备、终端和系统
CN111065166B (zh) * 2018-10-17 2022-08-19 大唐移动通信设备有限公司 直接通信链路的资源调度方法、终端及网络侧设备
CN111148231B (zh) * 2018-11-02 2022-06-10 大唐移动通信设备有限公司 一种信息传输方法及节点设备
WO2020206682A1 (zh) * 2019-04-12 2020-10-15 北京小米移动软件有限公司 加扰处理方法、解扰处理方法及装置
CN112118542B (zh) * 2019-06-21 2022-03-29 中国移动通信有限公司研究院 多播处理方法、装置及通信设备
CN112261671B (zh) * 2019-07-22 2022-07-29 华为技术有限公司 通信方法和通信装置
WO2023050372A1 (zh) * 2021-09-30 2023-04-06 华为技术有限公司 应用于点对多点的短距离无线通信系统的通信方法及设备
CN117202157A (zh) * 2023-10-07 2023-12-08 青海建筑职业技术学院 基于北斗短报文的无人区救援通信方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150466A (zh) * 2006-09-18 2008-03-26 华为技术有限公司 组播广播业务的传输方法、系统及终端
CN102547592A (zh) * 2012-01-06 2012-07-04 电信科学技术研究院 一种数据传输方法及装置
CN102833691A (zh) * 2012-09-12 2012-12-19 北京理工大学 基于波束成形和喷泉码的d2d多媒体广播和组播方法
CN103037448A (zh) * 2011-09-30 2013-04-10 华为技术有限公司 内容发布方法和用户设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150466A (zh) * 2006-09-18 2008-03-26 华为技术有限公司 组播广播业务的传输方法、系统及终端
CN103037448A (zh) * 2011-09-30 2013-04-10 华为技术有限公司 内容发布方法和用户设备
CN102547592A (zh) * 2012-01-06 2012-07-04 电信科学技术研究院 一种数据传输方法及装置
CN102833691A (zh) * 2012-09-12 2012-12-19 北京理工大学 基于波束成形和喷泉码的d2d多媒体广播和组播方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112399559A (zh) * 2019-08-13 2021-02-23 大唐移动通信设备有限公司 一种反馈资源选择方法和终端

Also Published As

Publication number Publication date
CN104619008A (zh) 2015-05-13
CN104619008B (zh) 2019-04-23

Similar Documents

Publication Publication Date Title
WO2015062260A1 (zh) 设备到设备组播/广播通信处理方法、装置及用户设备
CN104811892B (zh) 一种资源分配方法、装置及系统
CN104812025B (zh) 设备间发现及通信方法和系统
EP2939484B1 (en) Multi-band device-to-device multicast or broadcast communication
CN108207036B (zh) 一种半持久调度的方法及装置
CN103733657B (zh) 识别ue对embms的计数结果
WO2016202227A1 (zh) 一种层2链路标识的选择、通知方法及装置
WO2016183782A1 (zh) 一种终端设备、网络设备及数据传输方法
US9750066B2 (en) Method and a network structure for providing device connectivity to a radio access network
WO2016173310A1 (zh) 资源的配置方法及装置
KR20090101977A (ko) 이동 통신 시스템, 멀티캐스트 데이터 분배 방법, 코어 네트워크 장치, 및 액세스 네트워크 장치
WO2016019739A1 (zh) 用户状态的处理方法及装置
WO2014023240A1 (zh) 一种群组小数据的发送方法及系统
CN113055812B (zh) 一种数据传输方法、基站及核心网网元
KR20160111927A (ko) 통신 디바이스
CN105743663B (zh) 一种数据传输装置和方法
US9265071B2 (en) Signalling method for direct communication between terminals
KR20130008482A (ko) 인프라 통신을 이용하여 직접 통신을 지원하는 단말 및 그의 직접 통신 방법
WO2013067941A1 (zh) 一种分配标识的方法及装置
WO2022028277A1 (en) Methods and apparatuses for resource allocation to terminal device
TW201521494A (zh) 在蜂窩網路中實現基於設備到設備的組播通信的方法
Tsolkas et al. A device discovery scheme for proximity services in LTE networks
WO2016070615A1 (zh) 设备到设备d2d数据传输方法、装置及d2d ue
US20240114592A1 (en) Session setup method and apparatus
WO2023061152A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14858465

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14858465

Country of ref document: EP

Kind code of ref document: A1