WO2017028610A1 - 设备到设备标识冲突的解决方法、设备到设备用户设备 - Google Patents

设备到设备标识冲突的解决方法、设备到设备用户设备 Download PDF

Info

Publication number
WO2017028610A1
WO2017028610A1 PCT/CN2016/085302 CN2016085302W WO2017028610A1 WO 2017028610 A1 WO2017028610 A1 WO 2017028610A1 CN 2016085302 W CN2016085302 W CN 2016085302W WO 2017028610 A1 WO2017028610 A1 WO 2017028610A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal identifier
identifier
allocated
conflict
receiving
Prior art date
Application number
PCT/CN2016/085302
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 中兴通讯股份有限公司
Priority to EP16836474.3A priority Critical patent/EP3337194A4/en
Priority to US15/752,219 priority patent/US10484866B2/en
Publication of WO2017028610A1 publication Critical patent/WO2017028610A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5046—Resolving address allocation conflicts; Testing of addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present application relates to, but is not limited to, a wireless communication technology, in particular, a device-to-device (D2D) device-to-device (D2D, Device-to-Device User Equipment).
  • D2D device-to-device
  • D2D Device-to-Device User Equipment
  • D2D technology which represents a new direction for future communication technologies, has emerged.
  • the application of D2D technology can reduce the burden of cellular networks, reduce the battery power consumption of 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.
  • D2D technology can work in licensed or unlicensed bands, allowing multiple D2D-enabled user equipment (ie, D2D UEs) to perform direct discovery/direct communication with or without a network infrastructure.
  • D2D UEs D2D-enabled user equipment
  • D2D UE1 and D2D 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;
  • the D2D UE4 with poor signal quality is allowed to communicate with the network through the D2D UE3 with network coverage nearby, which can help the operator to expand coverage, Increase capacity;
  • D2D technology generally includes D2D discovery technology and D2D communication technology:
  • D2D discovery technology refers to determining/determining the proximity between two or more D2D UEs (for example, within the scope of direct D2D communication) or for judging/ A technique of determining that the first D2D UE is adjacent to the second D2D UE.
  • D2D communication technology refers to a technology in which some or all of the communication data between D2D UEs can communicate directly without going through the network infrastructure.
  • the D2D UE communication in a D2D communication group can adopt a one-to-many multicast communication mode. In this manner, all D2D UEs in the group can receive data sent by a D2D UE in the group.
  • the D2D UE can serve as a relay node, so that the remote D2D UE of the coverage edge or the coverage of the cellular network can perform cellular communication with the network by relaying the D2D UE.
  • D2D communication is performed between the D2D UEs through the relay D2D UE.
  • the remote D2D UE and the relay D2D UE communicate by using one-to-one D2D communication.
  • the Media Access Control Protocol Data Unit (MAC PDU) header of the D2D communication data packet includes a source and a target ID field.
  • the content of the target ID field in the MAC PDU header is a D2D group identifier.
  • the D2D group identifier is 24 bits, and is allocated by a DPF (Direct Provisioning Function, a component of ProSe Function).
  • the target ID field content in the MAC PDU header is the terminal identifier (ProSe UE ID) of the target D2D UE, and the terminal identifier is also 24 bits, which may be pre-configured on the mobile device (ME, Mobile Equipment).
  • one-to-one unicast communication and one-to-many multicast communication may exist at the same time, and there may be one-to-one unicast communication between the ProSe UE ID of the one-to-one unicast communication of the D2D UE and other D2D UEs.
  • the ProSe UE ID is the same, or the ProSe UE ID of the one-to-one unicast communication of the D2D UE is the same as the D2D group ID (ProSe Layer-2 Group ID) of the one-to-many multicast communication.
  • a D2D UE having the same ID and all D2D UEs in the D2D communication group will be caused to receive unicast or multicast MAC PDU packets destined for the same ID.
  • D2D UE2 and D2D UE3 belong to the same D2D communication group, and D2D group communication can be performed.
  • D2D UE1 does not belong to the D2D communication group, but D2D UE1 can perform one-to-one D2D discovery/communication with D2D UE2 or D2D UE3. .
  • the unicast ProSe UE ID of the D2D UE1 is the same as the ProSe Layer-2 Group ID of the ProSe communication group
  • both the D2D UE1 and the D2D UE of the D2D communication group (including the D2D UE2, D2D UE3) will receive the target ID as the same ID.
  • MAC PDU The related art has not yet solved the above D2D identification conflict problem.
  • the embodiment of the invention provides a solution for D2D identification conflict, and a D2D UE.
  • the solution to the D2D identifier conflict provided by the embodiment of the present invention is applied to the first D2D UE, and the method includes:
  • the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE, re-assigning the terminal identifier to the first D2D UE;
  • the terminal identifier that is re-allocated by the first D2D UE to the second D2D UE, where the second D2D UE is a neighboring D2D UE of the first D2D UE, or a D2D UE that has established a PC5 connection with the first D2D UE.
  • the determining whether the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE includes:
  • the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the ID conflict indication information sent by the third D2D UE determines that the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE; the ID conflict indication information is used to indicate the The terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the unable to parse the received data packet includes:
  • the Packet Data Convergence Protocol (PDCP) layer of the first D2D UE cannot decrypt the received data packet;
  • the first D2D UE determines that the target IP address of the received data packet and its own IP address are not Character; or,
  • the first D2D UE application layer determines that the received data packet is in error.
  • the receiving the ID conflict indication information sent by the third D2D UE includes:
  • the ID conflict indication information sent by the third D2D UE is received by the D2D discovery message.
  • the third D2D UE before the receiving the ID conflict indication information sent by the third D2D UE, the third D2D UE detects the terminal identifier of the first D2D UE and the terminal identifier or the D2D group identifier of the other D2D UE. A conflict has occurred.
  • the third D2D UE detects that the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE, including:
  • the third D2D UE detects that the terminal identifier of the first D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received D2D discovery message sent by the first D2D UE; or
  • the third D2D UE detects that the terminal identifier of the first D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received PC5 interface signaling sent by the first D2D UE; or
  • the third D2D UE detects that the terminal identifier of the first D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received data packet MAC PDU sent by the first D2D UE.
  • the first D2D UE is a remote remote D2D UE or a relay relay D2D UE or a D2D UE;
  • the second D2D UE is a remote D2D UE or a relay D2D UE or a D2D UE;
  • the D2D UE is a remote D2D UE or a relay D2D UE or a D2D UE.
  • the sending, by the first D2D UE, the terminal identifier that is re-allocated to the second D2D UE includes:
  • the first D2D UE old terminal identity and/or the reassigned terminal identity and/or the connection release indication and/or the ID change indication are sent to the second D2D UE through the D2D communication data packet.
  • the method further includes:
  • the base station Transmitting the terminal identifier that is re-allocated by the first D2D UE to the base station, and after receiving the terminal identifier re-allocated by the first D2D UE, the base station stores the terminal identifier and updates to the context information of the first D2D UE.
  • the second D2D UE after receiving the terminal identifier re-allocated by the first D2D UE, the second D2D UE starts to send the D2D to the first D2D UE by using the terminal identifier re-allocated by the first D2D UE as the target ID. Data; accordingly,
  • the method further includes: after receiving the data packet sent by the second D2D UE with the terminal identifier re-allocated by the first D2D UE as the target ID, starting to use the terminal identifier re-allocated by the first D2D UE as the source ID. Transmitting D2D data to the second D2D UE;
  • the second D2D UE sends the terminal identifier receiving confirmation information to the first D2D UE by using the D2D communication data packet after receiving the terminal identifier re-allocated by the first D2D UE; correspondingly,
  • the method further includes: after receiving the terminal identification confirmation information sent by the second D2D UE, starting to send the D2D data to the second D2D UE by using the terminal identifier re-allocated by the first D2D UE as a source ID.
  • the second D2D UE receives the connection sent by the first D2D UE. After the release indication and/or the ID change indication, the PC5 connection with the first D2D UE is released.
  • the method further includes:
  • the first D2D UE and the second D2D UE start to use the reassigned terminal identifier for data transmission after the current modification period;
  • the second D2D UE is a D2D UE that has established a PC5 connection with the first D2D UE;
  • the modification period is configured by a base station or a ProSe server or a core network element.
  • a solution to the D2D identification conflict provided by another embodiment of the present invention is applied to a fourth D2D UE, where the method includes:
  • the ID conflict indication information is sent to the fifth D2D UE, so that the fifth D2D UE is the fourth D2D.
  • the UE reassigns the terminal identifier
  • the determining whether the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE includes:
  • the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the ID conflict indication information sent by the sixth D2D UE determines that the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE; the ID conflict indication information is used to indicate the The terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the receiving the ID conflict indication information sent by the sixth D2D UE includes:
  • the ID conflict indication information sent by the sixth D2D UE is received by the D2D discovery message.
  • the sixth D2D UE before the receiving the ID conflict indication information sent by the sixth D2D UE, the sixth D2D UE detects that the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE. .
  • the sixth D2D UE detects that the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE, including:
  • the sixth D2D UE detects that the terminal identifier of the fourth D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received D2D discovery message sent by the fourth D2D UE; or
  • the sixth D2D UE detects that the terminal identifier of the fourth D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received PC5 interface signaling sent by the fourth D2D UE; or
  • the sixth D2D UE detects that the terminal identifier of the fourth D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received data packet MAC PDU sent by the fourth D2D UE.
  • the sending the ID conflict indication information to the fifth D2D UE includes:
  • the ID conflict indication is sent to the fifth D2D UE by the D2D discovery message.
  • the receiving, by the fifth D2D UE, a terminal identifier that is re-allocated by the fourth D2D UE includes:
  • the method further includes:
  • the method further includes:
  • the fourth D2D UE is a remote D2D UE
  • the fifth D2D UE is a relay D2D UE.
  • the D2D UE provided by the embodiment of the present invention includes:
  • the first determining unit is configured to: determine whether the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • a first allocation unit configured to: when the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE, re-assign the terminal identifier to the D2D UE;
  • the first sending unit is configured to: send the terminal identifier re-allocated by the D2D UE to the second D2D UE, where the second D2D UE is a neighboring D2D UE of the D2D UE, or has established a PC5 connection with the D2D UE. D2D UE.
  • the first determining unit includes:
  • the first parsing subunit is configured to: when the received data packet cannot be parsed, determine that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE; or
  • the first receiving subunit is configured to: when receiving the ID conflict indication information sent by the third D2D UE, determine that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the indication information is used to indicate that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the first parsing subunit is configured to: when the packet data convergence protocol PDCP layer of the D2D UE cannot decrypt the received data packet; or, the D2D UE determines the received data packet.
  • the target IP address does not match its own IP address; or, when the D2D UE application layer determines that the received data packet is in error, the received data packet cannot be parsed.
  • the first receiving subunit is configured to: receive the ID conflict indication information sent by the third D2D UE by using the unicast D2D communication physical channel MAC CE; or receive the third through the PC5 interface signaling.
  • the ID conflict indication information sent by the D2D UE; or the ID conflict indication information sent by the third D2D UE is received by the unicast D2D communication data packet; or the ID conflict indication information sent by the third D2D UE is received by the D2D discovery message.
  • the D2D UE is a remote remote D2D UE or a relay relay D2D UE or a D2D UE;
  • the second D2D UE is a remote D2D UE or a relay D2D UE or a D2D UE;
  • the third D2D UE It is a remote D2D UE or a relay D2D UE or a D2D UE.
  • the first sending unit is configured to send, by using a D2D discovery message, the D2D UE old terminal identifier and/or the reassigned terminal identifier and/or the connection release indication and/or the ID change indication to the first a second D2D UE; or, by the D2D communication MAC CE, transmitting the D2D UE old terminal identifier and/or the reassigned terminal identifier and/or the connection release indication and/or the ID change indication to the second D2D UE; or, through the PC5 interface Transmitting, by the D2D UE, the old terminal identifier and/or the reassigned terminal identifier and/or the connection release indication and/or the ID change indication to the second D2D UE; or the D2D UE old terminal identifier by using the D2D communication data packet And/or a reassigned terminal identity and/or a connection release indication and/or an ID change indication are sent to the second D2D UE.
  • the D2D UE further includes:
  • the second sending unit is configured to: send the terminal identifier that is re-allocated by the D2D UE to the base station, and after receiving the terminal identifier re-allocated by the D2D UE, the base station stores the terminal identifier and updates to the context information of the D2D UE. .
  • the second D2D UE after receiving the terminal identifier re-allocated by the D2D UE, the second D2D UE starts to use the terminal identifier re-allocated by the D2D UE as the target ID to send D2D data to the D2D UE;
  • the D2D UE further includes:
  • the first receiving unit is configured to: receive a data packet that is sent by the second D2D UE and that is re-allocated by the D2D UE as the target ID;
  • a third sending unit configured to: send the D2D data to the second D2D UE by using the terminal identifier re-allocated by the D2D UE as a source ID;
  • the second D2D UE sends the terminal identifier receiving confirmation information to the D2D UE through the D2D communication data packet after receiving the terminal identifier re-allocated by the D2D UE;
  • the D2D UE further includes:
  • the second receiving unit is configured to: receive terminal identification confirmation information sent by the second D2D UE;
  • the fourth sending unit is configured to: send the D2D data to the second D2D UE by using the terminal identifier re-allocated by the D2D UE as a source ID.
  • a D2D UE provided by another embodiment of the present invention includes:
  • the second determining unit is configured to: determine whether the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the fifth sending unit is configured to: when the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE, send the ID conflict indication information to the fifth D2D UE, so that the fifth D2D UE Reassigning the terminal identifier to the D2D UE;
  • the third receiving unit is configured to: receive, by the fifth D2D UE, a terminal identifier that is re-allocated for the D2D UE.
  • the second determining unit includes:
  • the second parsing subunit is configured to: when the received data packet cannot be parsed, determine that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE; or
  • the second receiving subunit is configured to: when receiving the ID conflict indication information sent by the sixth D2D UE, determine that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the indication information is used to indicate that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the second receiving subunit is configured to: receive the ID conflict indication information sent by the sixth D2D UE by using the unicast D2D communication MAC CE; or receive the sixth D2D UE by using the PC5 interface signaling.
  • the ID conflict indication information is sent; or the ID conflict indication information sent by the sixth D2D UE is received by the unicast D2D communication data packet; or the ID conflict indication information sent by the sixth D2D UE is received by the D2D discovery message.
  • the fifth sending unit is configured to: send the ID conflict indication to the fifth D2D UE by using the unicast D2D communication MAC CE; or send the ID conflict indication to the fifth D2D by using the PC5 interface signaling.
  • the UE transmits the ID conflict indication to the fifth D2D UE through the unicast D2D communication data packet; or sends the ID conflict indication to the fifth D2D UE through the D2D discovery message.
  • the third receiving unit is configured to: receive, by using a unicast D2D communication MAC CE, a terminal identifier that is re-allocated by the fifth D2D UE for the D2D UE; or, by using a PC5 interface signaling Receiving, by the fifth D2D UE, a terminal identifier that is re-allocated for the D2D UE; or receiving, by using a unicast D2D communication data packet, a terminal identifier that is re-allocated by the fifth D2D UE for the D2D UE; or Receiving, by the D2D discovery message, a terminal identifier that is sent by the fifth D2D UE and re-allocated for the D2D UE.
  • the D2D UE further includes:
  • a sixth sending unit configured to: send the terminal identifier re-allocated by the D2D UE to a neighboring D2D UE or a D2D UE that has established a connection with the D2D UE.
  • the D2D UE further includes:
  • the seventh sending unit is configured to: send the terminal identifier that is re-allocated by the D2D UE to the base station, and the base station receives the terminal identifier that is re-allocated by the D2D UE, stores the terminal identifier, and updates the context information of the D2D UE. .
  • the D2D UE is a remote D2D UE
  • the fifth D2D UE is a relay D2D UE.
  • Another embodiment of the present invention provides a computer readable storage medium storing computer executable instructions that are implemented by a processor to implement the above method.
  • the first D2D UE determines whether the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE; when the terminal identifier of the first D2D UE and other When the terminal identifier or the D2D group identifier of the D2D UE conflicts, the terminal identifier is re-allocated to the first D2D UE, and the terminal identifier re-allocated by the first D2D UE is sent to the second D2D UE.
  • the D2D UE can detect the conflict of the terminal identifier in time and re-acquire the new terminal identifier, thereby ensuring the smooth progress of the D2D communication.
  • the conflict between the terminal identifiers of the D2D UEs of the D2D unicast communication, or the terminal identifiers of the D2D unicast communication and the D2D group identifiers of the multicast communication group is avoided.
  • 1 is a schematic diagram of an application mode of D2D technology
  • FIG. 2 is a schematic diagram of a D2D communication scenario
  • FIG. 3 is a schematic flowchart of a method for solving a D2D identifier conflict according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a method for solving a D2D identifier conflict according to another embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a scenario according to Embodiment 1 of the present invention.
  • FIG. 6 is a schematic flowchart of a method for solving a D2D identifier conflict according to Embodiment 1 of the present invention.
  • FIG. 7 is a schematic diagram of a scenario according to Embodiment 2 of the present invention.
  • FIG. 8 is a schematic flowchart of a method for solving a D2D identifier conflict according to Embodiment 2 of the present invention.
  • FIG. 9 is a schematic diagram of a scenario according to Embodiment 3 of the present invention.
  • FIG. 10 is a schematic flowchart of a method for solving a D2D identifier conflict according to Embodiment 3 of the present invention.
  • FIG. 11 is a schematic diagram of a scenario according to Embodiment 4 of the present invention.
  • FIG. 12 is a schematic flowchart of a method for solving a D2D identification conflict according to Embodiment 4 of the present invention.
  • FIG. 13 is a schematic structural diagram of a D2D UE according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a D2D UE according to another embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for solving a D2D identifier conflict according to an embodiment of the present invention.
  • the solution for the D2D identifier conflict in the present example is applied to a first D2D UE.
  • the solution for the D2D identifier conflict includes The following steps:
  • Step 301 Determine whether the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • determining whether the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE may be performed in the following manner:
  • the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the ID conflict indication information sent by the third D2D UE determines that the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE; the ID conflict indication information is used to indicate the The terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the data packets that cannot be parsed include the following cases:
  • the packet data convergence protocol PDCP layer of the first D2D UE cannot decrypt the received data packet
  • the first D2D UE determines that the target IP address of the received data packet does not match its own IP address; or
  • the first D2D UE application layer determines that the received data packet is in error.
  • the ID conflict indication information sent by the first D2D UE to the third D2D UE may be received by, but not limited to, the following forms:
  • the ID conflict indication information sent by the third D2D UE is received by the D2D discovery message.
  • the third D2D UE detects the terminal identifier of the first D2D UE and the terminal identifier or D2D of the other D2D UE.
  • the group ID conflicts.
  • the third D2D UE detects that the terminal identifier of the first D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received D2D discovery message sent by the first D2D UE; or
  • the third D2D UE detects that the terminal identifier of the first D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received PC5 interface signaling sent by the first D2D UE; or
  • the third D2D UE detects that the terminal identifier of the first D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received data packet MAC PDU sent by the first D2D UE.
  • the foregoing solution is to obtain the terminal identifiers of the first D2D UEs and detect the transmission conflicts, which are respectively: 1) D2D discovery messages; 2) PC5 interface signaling; and 3) IDs included in the MAC PDUs.
  • the PC5 interface signaling may be a PC5 connection setup message, such as a direct communication request message, and the PC5 connection is different from the other two.
  • the first D2D UE is a remote remote D2D UE or a relay relay D2D UE or a D2D UE;
  • the second D2D UE is a remote D2D UE or a relay D2D UE or a D2D UE;
  • D2D UE is remote D2D UE or relay D2D UE or D2D UE.
  • the D2D UE refers to a normal D2D UE that is not a remote D2D UE or a non-relay D2D UE.
  • Step 302 Re-assign the terminal identifier to the first D2D UE when the terminal identifier of the first D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the first D2D UE re-allocates a new terminal identifier for itself, and the re-allocated new terminal identifier is different from the old terminal identifier of the original first D2D UE.
  • Step 303 Send the terminal identifier re-allocated by the first D2D UE to the second D2D UE, where the second D2D UE is a neighboring D2D UE of the first D2D UE, or has established a PC5 connection with the first D2D UE. D2D UE.
  • the first D2D UE sends the terminal identifier re-allocated by the first D2D UE to the second D2D UE.
  • the first D2D UE old terminal identity and/or the reassigned terminal identity and/or the connection release indication and/or the ID change indication are sent to the second D2D UE through the D2D communication data packet.
  • the original PC5 connection is released, and the D2D UE re-establishes the connection by using the terminal identifier re-allocated by the first D2D UE. Therefore, the first D2D UE will be the old terminal. While the identified and/or reassigned terminal identifier is sent to the second D2D UE, the connection release indication and/or the ID change indication may also be sent to the second D2D UE.
  • the first D2D UE after the terminal identifier is re-assigned to the first D2D UE, the first D2D UE sends the terminal identifier re-allocated by the first D2D UE to the base station, and the base station receives the first D2D UE reallocation. After identifying the terminal, the terminal identifier is stored and updated to the context information of the first D2D UE.
  • the second D2D UE after receiving the connection release indication and/or the ID change indication sent by the first D2D UE, the second D2D UE releases the PC5 connection with the first D2D UE.
  • the second D2D UE after receiving the terminal identifier re-allocated by the first D2D UE, the second D2D UE starts to use the terminal identifier re-allocated by the first D2D UE as the target ID to send D2D data to the first D2D UE.
  • the first D2D UE after receiving, by the second D2D UE, the terminal identifier that is re-allocated by the first D2D UE as the target ID, the first D2D UE starts to use the terminal identifier re-allocated by the first D2D UE as a source.
  • the ID transmits D2D data to the second D2D UE.
  • the second D2D UE after receiving the terminal identifier re-allocated by the first D2D UE, the second D2D UE sends the terminal identifier receiving confirmation information to the first D2D UE by using the D2D communication data packet; correspondingly, the first D2D UE receives the After the terminal identification confirmation information sent by the second D2D UE, the terminal identifier that is re-allocated by the first D2D UE is used as the source ID to send the D2D data to the second D2D UE.
  • the first D2D UE and the second D2D UE start to use the reassigned terminal identifier to perform data transmission after the current modification period;
  • the second D2D UE is a D2D UE that has established a PC5 connection with the first D2D UE; the modification period is configured by a base station or a ProSe server or a core network element.
  • FIG. 4 is a schematic flowchart of a method for solving a D2D identifier conflict according to another embodiment of the present invention.
  • the solution for the D2D identifier conflict in this example is applied to a fourth D2D UE. As shown in FIG. 4, the D2D identifier conflict is resolved.
  • the method includes the following steps:
  • Step 401 Determine whether the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • determining whether the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE may be performed in the following manner:
  • the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the terminal identifier of the UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the ID conflict indication information is used to indicate that the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the ID conflict indication information sent by the fourth D2D UE to the sixth D2D UE may be received by, but not limited to, the following manner:
  • the ID conflict indication information sent by the sixth D2D UE is received by the D2D discovery message.
  • the sixth D2D UE detects the terminal identifier of the fourth D2D UE and the terminal identifier or the D2D group identifier of the other D2D UE. A conflict has occurred.
  • the sixth D2D UE detects that the terminal identifier of the fourth D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received D2D discovery message sent by the fourth D2D UE; or
  • the sixth D2D UE detects that the terminal identifier of the fourth D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received PC5 interface signaling sent by the fourth D2D UE; or
  • the sixth D2D UE detects that the terminal identifier of the fourth D2D UE is the same as the terminal identifier or the D2D group identifier of the other D2D UE by using the received data packet MAC PDU sent by the fourth D2D UE.
  • Step 402 When the terminal identifier of the fourth D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE, send the ID conflict indication information to the fifth D2D UE, so that the fifth D2D UE is the The fourth D2D UE reassigns the terminal identity.
  • the fourth D2D UE sends the ID conflict indication information to the fifth D2D UE, but may be sent by, but not limited to, the following manner:
  • the ID conflict indication is sent to the fifth D2D UE by the D2D discovery message.
  • Step 403 Receive, by the fifth D2D UE, a terminal identifier that is re-allocated for the fourth D2D UE.
  • the fourth D2D UE receives the terminal identifier that is re-allocated by the fifth D2D UE for the fourth D2D UE, that is, the terminal that the fifth D2D UE will re-allocate for the fourth D2D UE.
  • the identity is sent to the fourth D2D UE.
  • the fourth D2D UE after obtaining the reassigned terminal identifier, the fourth D2D UE sends the reassigned terminal identifier to the neighboring D2D UE or the D2D UE that has established a connection with the fourth D2D UE.
  • the fourth D2D UE after obtaining the reassigned terminal identifier, the fourth D2D UE sends the re-assigned terminal identifier to the base station, and the base station receives the terminal identifier re-allocated by the fourth D2D UE, stores the terminal identifier, and updates the terminal identifier to In the context information of the fourth D2D UE.
  • the fourth D2D UE is a remote D2D UE
  • the fifth D2D UE is a relay D2D UE.
  • the D2D UE in the embodiment of the present invention may be a relay D2D UE, or a remote D2D UE, or a normal D2D UE.
  • FIG. 5 is a schematic diagram of the scenario in the embodiment.
  • the D2D UE3 and the D2D UE2 belong to the same D2D communication group, and can perform D2D group communication.
  • the D2D UE1 (relay D2D UE) does not belong to the D2D communication group, but the D2D UE1 can communicate with the D2D UE2.
  • D2D UE3 performs one-to-one D2D discovery/communication.
  • FIG. 6 is a schematic flowchart of a method for solving a D2D identifier conflict according to the embodiment of the present invention. As shown in FIG. 6, the method in this embodiment includes the following steps:
  • Step 601 The remote D2D UE obtains the unicast ProSe D2D UE ID of the relay D2D UE through the D2D discovery process.
  • the remote D2D UE obtains the unicast ProSe D2D UE ID of the relay D2D UE by using the received D2D discovery message sent by the relay D2D UE.
  • Step 602 The remote D2D UE detects that the unicast ProSe D2D UE ID of the relay D2D UE is the same as the layer 2Group ID of the D2D communication group that is added by the UE, and determines that the ProSe D2D UE ID of the relay D2D UE has an ID conflict with the D2D group ID.
  • the remote D2D UE may also obtain the unicast ProSe D2D UE ID of the relay D2D UE in the PC5 connection establishment process, and detect that the ID of the relay D2D UE conflicts with the own group ID.
  • the remote D2D UE may obtain the unicast ProSe D2D UE ID of the relay D2D UE by using the received PC5 connection setup response message sent by the relay D2D UE.
  • the remote D2D UE may learn the D2D UE ID of the relay D2D UE and detect the relay D2D UE by receiving the D2D communication data packet of the relay D2D UE after establishing the PC5 connection with the relay D2D UE.
  • the ProSe D2D UE ID conflicts with its own group ID.
  • Step 603 The remote D2D UE sends ID conflict indication information to the relay D2D UE, where it is used to indicate that the ProSe D2D UE ID of the relay D2D UE conflicts with other D2D UE IDs or group IDs.
  • the remote D2D UE may send the ID conflict indication information to the relay D2D UE in the following manner:
  • the remote D2D UE After the establishment of the PC5 connection between the remote D2D UE and the relay D2D UE, the remote D2D UE sends the ID conflict indication information to the relay D2D UE through the unicast D2D communication MAC CE; or
  • the relay D2D UE After the relay D2D UE completes the relay discovery with the relay D2D UE, it sends an ID conflict indication information to the relay D2D UE through the PC5 interface signaling, where the PC5 interface signaling may be a PC5 connection establishment request message, or a new PC5 interface signaling is added. ;or,
  • the remote D2D UE After the establishment of the PC5 connection with the relay D2D UE, the remote D2D UE sends the ID conflict indication information to the relay D2D UE by unicasting the D2D communication data packet; or
  • the remote D2D UE sends an ID conflict indication information to the relay D2D UE by using a D2D discovery message, where the D2D discovery message further includes a ProSe D2D UE ID of the relay D2D UE.
  • Step 604 After receiving the ID conflict indication information sent by the remote D2D UE, the relay D2D UE re-allocates its own ProSe D2D UE ID.
  • Step 605 After the relay D2D UE re-allocates its own ProSe D2D UE ID, it sends the updated ProSe D2D UE ID to the remote D2D UE that has established its connection with the PC5 and the nearby D2D UE.
  • the relay D2D UE can send ID change notification information in the following manner:
  • the relay D2D UE sends its own updated ProSe D2D UE ID to the remote D2D UE that has established a PC5 connection with the unicast D2D communication MAC CE; or
  • the relay D2D UE sends the self-updated ProSe D2D UE ID to the remote D2D UE through the PC5 interface signaling, where the PC5 interface signaling may establish a response message for the PC5 connection, or add a PC5 interface signaling; or
  • the relay D2D UE sends its own updated ProSe D2D UE ID to the remote D2D UE with which the PC5 connection has been established by unicasting the D2D communication data packet;
  • the relay D2D UE sends the self-updated ProSe D2D UE ID to the remote D2D UE through the D2D discovery message, where the D2D discovery message includes the new ProSe D2D UE ID of the relay D2D UE, or contains the new sum of the relay D2D UE. Old ProSe D2D UE ID.
  • the relay D2D UE sends a connection release indication and/or an ID change indication to the remote D2D UE with which the PC5 connection has been established.
  • Step 606 After the remote D2D UE that has established the PC5 connection with the relay D2D UE receives the updated ProSe D2D UE ID sent by the relay D2D UE, the remote D2D UE sends the ID change notification acknowledgement information to the relay D2D UE.
  • the ID change notification acknowledgement information may be a data packet with the ProSe D2D UE ID updated by the relay D2D UE as the target ID, or the D2D communication data packet whose content is the ID change notification acknowledgement, or may be through the unicast D2D communication MAC CE.
  • Send or, can be sent through the PC5 interface signaling, or can be sent through the D2D discovery message.
  • the remote D2D UE After receiving the updated ProSe D2D UE ID sent by the relay D2D UE, the remote D2D UE starts to send the D2D communication data packet to the relay D2D UE by using the updated ProSe D2D UE ID as the target ID.
  • the relay D2D UE starts to send the D2D communication data packet to the remote D2D UE by using the updated ProSe D2D UE ID as the source ID after receiving the ID change notification acknowledgement information sent by the remote D2D UE.
  • the relay D2D UE and the remote D2D UE that has established a PC5 connection with it start to use the new ProSe D2D UE ID identification information after the current modification period.
  • the remote D2D UE receives the connection release indication and/or the ID change indication sent by the relay D2D UE, the Remote D2D UE releases the PC5 connection between it and the relay D2D UE, and re-initiates the relay discovery/PC5 connection establishment process. If the remote D2D UE further receives the updated ProSe D2D UE ID sent by the relay D2D UE, the remote D2D UE may directly initiate a PC5 connection establishment procedure to the relay D2D UE.
  • FIG. 7 is a schematic diagram of the scenario in this embodiment.
  • D2D UE3 D2D UE2 (relay D2D UE) belongs to the same D2D communication group, and D2D group communication can be performed.
  • D2D UE1 (remote D2D UE) does not belong to the D2D communication group, but D2D UE1 can perform one-to-one D2D with D2D UE2 or D2D UE3. Discovery/communication.
  • FIG. 8 is a schematic flowchart of a method for solving a D2D identifier conflict according to Embodiment 2 of the present invention. As shown in FIG. 8, the method in this embodiment includes the following steps:
  • Step 801 The relay D2D UE obtains the unicast ProSe D2D UE ID of the remote D2D UE by using a D2D discovery process.
  • the relay D2D UE obtains the unicast ProSe D2D UE ID of the relay D2D UE by receiving the D2D discovery message sent by the remote D2D UE.
  • Step 802 The relay D2D UE obtains the unicast ProSe D2D UE ID of the remote D2D UE in the PC5 connection establishment process.
  • the relay D2D UE may obtain the unicast ProSe D2D UE ID of the remote D2D UE by using the received PC5 connection setup request message sent by the remote D2D UE. Alternatively, the relay D2D UE may learn the D2D UE ID of the remote D2D UE by receiving the D2D communication data packet of the remote D2D UE after establishing a PC5 connection with the remote D2D UE.
  • Step 803 The relay D2D UE detects that the unicast ProSe D2D UE ID of the remote D2D UE is the same as the layer 2Group ID of the D2D communication group that is added by the UE, and determines that the ProSe D2D UE ID of the remote D2D UE has an ID conflict with the D2D group ID.
  • Step 804 The relay D2D UE sends ID conflict indication information to the remote D2D UE, where it is used to indicate that the ProSe D2D UE ID of the remote D2D UE conflicts with other D2D UE IDs or group IDs.
  • the relay D2D UE may send the ID conflict indication information to the remote D2D UE in the following manner:
  • the relay D2D UE is connected to the remote D2D UE after the PC5 connection is established.
  • the unicast D2D communication MAC CE sends an ID conflict indication message to the remote D2D UE; or
  • the relay D2D UE sends the ID conflict indication information to the remote D2D UE through the PC5 interface signaling after the relay discovery is completed with the remote D2D UE, where the PC5 interface signaling may be a PC5 connection setup request message, or a new PC5 interface signaling is added. ;or,
  • the relay D2D UE After the completion of the establishment of the PC5 connection with the remote D2D UE, the relay D2D UE sends the ID conflict indication information to the remote D2D UE by unicasting the D2D communication data packet; or
  • the relay D2D UE sends the ID conflict indication information to the remote D2D UE through the D2D discovery message, where the D2D discovery message further includes the ProSe D2D UE ID of the remote D2D UE.
  • Step 805 After receiving the ID conflict indication information sent by the relay D2D UE, the remote D2D UE re-allocates its own ProSe D2D UE ID.
  • Step 806 After the remote D2D UE re-allocates its own ProSe D2D UE ID, it sends its updated ProSe D2D UE ID to the relay D2D UE and its nearby D2D UE that have established a PC5 connection with it.
  • the remote D2D UE can send the ID change notification information in the following manner:
  • the remote D2D UE sends its own updated ProSe D2D UE ID to the relay D2D UE that has established a PC5 connection with the unicast D2D communication MAC CE; or
  • the remote D2D UE sends the self-updated ProSe D2D UE ID to the relay D2D UE through the PC5 interface signaling, where the PC5 interface signaling may be a PC5 connection setup request message or a new PC5 interface signaling; or
  • the remote D2D UE sends its own updated ProSe D2D UE ID to the relay D2D UE that has established the PC5 connection with the unicast D2D communication data packet;
  • the remote D2D UE sends a self-updated ProSe D2D UE ID to the relay D2D UE through the D2D discovery message in the MODE B discovery process, and the D2D discovery message includes the new ProSe D2D UE ID of the remote D2D UE, or the remote D2D is included.
  • the new and old ProSe D2D UE ID of the UE is included.
  • the remote D2D UE sends a connection release indication and/or an ID change indication to the relay D2D UE with which the PC5 connection has been established.
  • Step 807 After the relay D2D UE that has established the PC5 connection with the remote D2D UE receives the updated ProSe D2D UE ID sent by the remote D2D UE, the relay D2D UE sends an ID change notification confirmation message to the remote D2D UE.
  • the ID change notification acknowledgement information may be a data packet with the ProSe D2D UE ID updated by the remote D2D UE as the target ID, or the D2D communication data packet whose content is the ID change notification acknowledgement, or may be through the unicast D2D communication MAC CE.
  • Send or, can be sent through the PC5 interface signaling, or can be sent through the D2D discovery message.
  • the relay D2D UE After receiving the updated ProSe D2D UE ID sent by the remote D2D UE, the relay D2D UE starts to send the D2D communication data packet to the remote D2D UE by using the updated ProSe D2D UE ID as the target ID.
  • the remote D2D UE After receiving the ID change notification acknowledgement message sent by the relay D2D UE, the remote D2D UE starts to send the D2D communication data packet to the relay D2D UE by using the updated ProSe D2D UE ID as the source ID.
  • the remote D2D UE and the relay D2D UE that has established a PC5 connection with it start to use the new ProSe D2D UE ID identification information after the current modification period.
  • the relay D2D UE receives the connection release indication and/or the ID change indication sent by the remote D2D UE, the relay D2D UE releases the PC5 connection between the remote D2D UE and the remote D2D UE, and the remote D2D UE re-initiates the relay discovery/PC5 connection establishment. process.
  • FIG. 9 is a schematic diagram of a scenario in this embodiment.
  • the remote D2D UE1 performs D2D communication by relaying the relay of the D2D UE, and then the remote D2D UE2 discovers the relay D2D UE and wants to establish a PC5 connection with the relay D2D UE, and the remote D2D UE1 and the remote D2D UE1 ProSe.
  • the D2D UE ID is the same.
  • FIG. 10 is a schematic flowchart of a method according to Embodiment 3 of the present invention. As shown in FIG. 10, the method in this embodiment includes the following steps:
  • Step 111 The remote D2D UE1 finds the relay D2D UE, and the relay D2D UE obtains the ProSe D2D UE ID of the remote D2D UE1.
  • the relay D2D UE may obtain the ProSe D2D UE ID of the remote D2D UE1 through a D2D discovery process or a PC5 connection establishment process or a D2D communication packet.
  • Step 112 The relay D2D UE obtains the unicast ProSe D2D UE ID of the remote D2D UE2 through the D2D discovery process.
  • the relay D2D UE obtains the unicast ProSe D2D UE ID of the relay D2D UE by receiving the D2D discovery message sent by the remote D2D UE2.
  • Step 113 The relay D2D UE obtains the unicast ProSe D2D UE ID of the remote D2D UE2 in the PC5 connection establishment process.
  • the relay D2D UE may obtain the unicast ProSe D2D UE ID of the remote D2D UE by using the received PC5 connection setup request message sent by the remote D2D UE2. Alternatively, the relay D2D UE may learn the D2D UE ID of the remote D2D UE by receiving the D2D communication data packet of the remote D2D UE2 after establishing a PC5 connection with the remote D2D UE2.
  • Step 114 The relay D2D UE detects that the ProSe D2D UE IDs of the remote D2D UE1 and the remote D2D UE2 are the same, and determines that an ID conflict occurs between the ProD D2D UE IDs of the remote D2D UE1 and the remote D2D UE2.
  • Step 115 The relay D2D UE sends ID conflict indication information to the remote D2D UE2, and is used to indicate that the ProSe D2D UE ID of the remote D2D UE2 conflicts with other D2D UE IDs or group IDs.
  • the relay D2D UE may send the ID conflict indication information to the remote D2D UE2 in the following manner:
  • the relay D2D UE sends the ID conflict indication information to the remote D2D UE2 through the unicast D2D communication MAC CE after the establishment of the PC5 connection with the remote D2D UE2; or
  • the relay D2D UE sends the ID conflict indication information to the remote D2D UE2 through the PC5 interface signaling after the relay discovery is completed with the remote D2D UE2, wherein the PC5 interface signaling may be a PC5 connection establishment request message or a new PC5 interface signaling. ;or,
  • the relay D2D UE sends the ID conflict indication information to the remote D2D UE2 by unicasting the D2D communication data packet after the establishment of the PC5 connection with the remote D2D UE2 is completed; or
  • the relay D2D UE sends the ID conflict indication information to the remote D2D UE2 through the D2D discovery message, and the D2D discovery message further includes the ProSe D2D UE ID of the remote D2D UE2.
  • Step 116 After receiving the ID conflict indication information sent by the relay D2D UE, the remote D2D UE2 re-allocates its own ProSe D2D UE ID.
  • Step 117 After the remote D2D UE2 re-allocates its own ProSe D2D UE ID, it sends its updated ProSe D2D UE ID to the relay D2D UE and its nearby D2D UE that have established a PC5 connection with it.
  • the remote D2D UE2 can send the ID change notification information in the following manner:
  • remote D2D UE2 sends its own updated ProSe D2D UE ID to the relay D2D UE that has established its PC5 connection through the unicast D2D communication MAC CE;
  • remote D2D UE2 sends its own updated ProSe D2D UE ID to the relay D2D UE through the PC5 interface signaling, where the PC5 interface signaling may be a PC5 connection setup request message or a new PC5 interface signaling; or
  • remote D2D UE2 sends its own updated ProSe D2D UE ID to the relay D2D UE that has established a PC5 connection by means of unicasting D2D communication data packets;
  • the remote D2D UE2 sends a self-updated ProSe D2D UE ID to the relay D2D UE through the D2D discovery message in the MODE B discovery process, and the D2D discovery message includes the new ProSe D2D UE ID of the remote D2D UE, or the remote D2D is included.
  • the new and old ProSe D2D UE ID of the UE is included.
  • the remote D2D UE2 sends a connection release indication and/or an ID change indication to the relay D2D UE with which the PC5 connection has been established.
  • Step 118 After the relay D2D UE that has established the PC5 connection with the remote D2D UE2 receives the updated ProSe D2D UE ID sent by the remote D2D UE2, the relay D2D UE sends the ID change notification acknowledgement information to the remote D2D UE2.
  • the ID change notification confirmation information may be a data packet with the ProSe D2D UE ID updated by the remote D2D UE2 as the target ID, or the D2D communication data packet whose content is the ID change notification acknowledgement, or may be through the unicast D2D communication MAC CE.
  • Send or, can be sent through the PC5 interface signaling, or can be sent through the D2D discovery message.
  • the relay D2D UE After receiving the updated ProSe D2D UE ID sent by the remote D2D UE2, the relay D2D UE starts to send the D2D communication data packet to the remote D2D UE2 by using the updated ProSe D2D UE ID as the target ID.
  • the remote D2D UE2 starts to send the D2D communication data packet to the relay D2D UE by using the updated ProSe D2D UE ID as the source ID after receiving the ID change notification acknowledgement information sent by the relay D2D UE.
  • remote D2D UE2 and the relay D2D UE that has established a PC5 connection with it start to use the new ProSe D2D UE ID identification information after the current modification period.
  • the relay D2D UE receives the connection release indication and/or the ID change indication sent by the remote D2D UE2, the relay D2D UE releases the PC5 connection between it and the remote D2D UE2, and the remote D2D UE2 re-initiates the relay discovery/PC5 connection establishment. process.
  • FIG. 11 is the embodiment. Schematic diagram of the scene. As shown in FIG. 11, D2D UE3 (D2D remote UE) performs D2D communication through relay of D2D UE4 (relay D2D UE). D2D UE1 and D2D UE2 belong to the same D2D communication group, and can perform D2D group communication.
  • FIG. 12 is a schematic flowchart of a method for solving a D2D identifier conflict according to an embodiment of the present invention. As shown in FIG. 12, the method in this embodiment includes the following steps:
  • Step 121 The D2D UE2 obtains the unicast ProSe UE ID of the remote D2D UE through the D2D discovery process.
  • the UE2 obtains the unicast ProSe UE ID of the relay D2D UE by receiving the D2D discovery message sent by the remote D2D UE.
  • Step 122 The D2D UE2 obtains the unicast ProSe UE ID of the remote D2D UE in the PC5 connection establishment process.
  • the D2D UE2 may obtain the unicast ProSe UE ID of the remote D2D UE by using the received PC5 connection setup request message sent by the remote D2D UE. Alternatively, the D2D UE2 may learn the UE ID of the remote D2D UE by receiving the D2D communication data packet of the remote D2D UE after establishing a PC5 connection with the remote D2D UE.
  • Step 123 The D2D UE2 detects that the unicast ProSe UE ID of the D2D UE3 (remote D2D UE) is the same as the ProSe Layer-2 Group ID of the ProSe communication group (composed of the D2D UE1 and the D2D UE2), and determines that the UE ID of the remote D2D UE occurs. ID conflict.
  • Step 124 The D2D UE2 sends an ID conflict indication information to the remote D2D UE, where it is used to indicate that the ProSe UE ID of the remote D2D UE conflicts with other UE IDs or group IDs.
  • the D2D UE2 may send the ID conflict indication information to the remote D2D UE in the following manner:
  • the D2D UE2 After the PC5 connection establishment with the remote D2D UE is completed, the D2D UE2 sends the ID conflict indication information to the remote D2D UE through the unicast D2D communication MAC CE; or
  • the D2D UE2 sends the ID conflict indication information to the remote D2D UE through the PC5 interface signaling after the D2D discovery is completed with the remote D2D UE, where the PC5 interface signaling may be a PC5 connection setup request message or a new PC5 interface signaling. or,
  • the D2D UE2 After the establishment of the PC5 connection with the remote D2D UE, the D2D UE2 sends the ID conflict indication information to the remote D2D UE by unicasting the D2D communication data packet; or
  • the D2D UE2 sends an ID conflict indication information to the remote D2D UE through the D2D discovery message, where the D2D discovery message further includes the ProSe UE ID of the remote D2D UE.
  • Step 125 After receiving the ID conflict indication information sent by the D2D UE2, the remote D2D UE sends the ID conflict indication information to the relay D2D UE.
  • the remote D2D UE may send the ID conflict indication information to the relay D2D UE in the following manner:
  • the remote D2D UE After the establishment of the PC5 connection between the remote D2D UE and the relay D2D UE, the remote D2D UE sends the ID conflict indication information to the relay D2D UE through the unicast D2D communication MAC CE; or
  • the remote D2D UE is connected through the PC5 after completing the relay discovery with the relay D2D UE.
  • the port signaling sends ID conflict indication information to the relay D2D UE, where the PC5 interface signaling may be a PC5 connection setup request message or a new PC5 interface signaling. or,
  • the remote D2D UE After the establishment of the PC5 connection with the relay D2D UE, the remote D2D UE sends the ID conflict indication information to the relay D2D UE by unicasting the D2D communication data packet; or
  • the remote D2D UE sends the ID conflict indication information to the relay D2D UE through the D2D discovery message, where the D2D discovery message further includes the ProSe UE ID of the remote D2D UE.
  • Step 126 The relay D2D UE re-allocates the ProSe UE ID for the remote D2D UE.
  • Step 127 After the relay D2D UE reassigns the ProSe UE ID to the remote D2D UE, the new ProSe UE ID of the remote D2D UE is sent to the remote D2D UE.
  • the relay D2D UE may send the new ProSe UE ID of the remote D2D UE to the remote D2D UE by:
  • the relay D2D UE transmits the reassigned ProSe UE ID to the remote D2D UE that has established the PC5 connection with the unicast D2D communication MAC CE; or
  • the relay D2D UE sends the reassigned ProSe UE ID to the remote D2D UE through the PC5 interface signaling, where the PC5 interface signaling may be a PC5 connection setup request message or a new PC5 interface signaling; or
  • the relay D2D UE sends the reassigned ProSe UE ID to the remote D2D UE that has established the PC5 connection with the unicast D2D communication data packet;
  • the relay D2D UE sends the re-allocated ProSe UE ID to the remote D2D UE through the D2D discovery message, where the D2D discovery message includes the new ProSe UE ID of the remote D2D UE, or contains the new and old of the remote D2D UE. ProSe UE ID.
  • Step 128 The remote D2D UE sends its own new ProSe UE ID to the D2D UE and the nearby D2D UE that have established a PC5 connection with it.
  • the remote D2D UE can send the ID change notification information in the following manner:
  • the remote D2D UE sends its own updated ProSe UE ID to the D2D UE that has established a PC5 connection with the unicast D2D communication MAC CE; or
  • the remote D2D UE sends the self-updated ProSe UE ID to the D2D UE that has established the PC5 connection with the PC5 interface, and the PC5 interface signaling may be a PC5 connection establishment request message or a new PC5 interface signaling; or
  • the remote D2D UE sends its own updated ProSe UE ID to the D2D UE that has established the PC5 connection with the unicast D2D communication data packet;
  • the remote D2D UE sends a self-updated ProSe UE ID to the D2D UE or the neighboring D2D UE that has established a PC5 connection with the D2D discovery message, where the D2D discovery message includes the new ProSe UE ID of the remote D2D UE, or includes The new and old ProSe UE ID of the remote D2D UE.
  • the remote D2D UE sends a connection release indication and/or an ID change indication to the D2D UE with which the PC5 connection has been established.
  • the remote D2D UE obtains the new ProSe UE ID, and then reports the new ProSe UE ID to the base station, and the base station receives and stores the new ProSe UE ID of the remote D2D UE. Update the D2D UE context.
  • Step 129 After receiving the updated ProSe UE ID sent by the remote D2D UE, the D2D UE that has established the PC5 connection with the remote D2D UE sends the ID change notification confirmation information to the remote D2D UE.
  • the ID change notification confirmation information may be a data packet with the ProSe UE ID updated by the remote D2D UE as the target ID, or the D2D communication data packet whose content is the ID change notification acknowledgement, or may be sent through the unicast D2D communication MAC CE. Or, it can be sent through the PC5 interface signaling, or it can be sent through the D2D discovery message.
  • the D2D UE after receiving the updated ProSe UE ID sent by the remote D2D UE, the D2D UE starts to send the D2D communication data packet to the remote D2D UE by using the updated ProSe UE ID as the target ID.
  • the remote D2D UE starts to send the D2D communication data packet to the D2D UE by using the updated ProSe UE ID as the source ID after receiving the ID change notification acknowledgement information sent by the D2D UE.
  • the remote D2D UE and the D2D UE with which the PC5 connection has been established start to use the new ProSe UE ID identification information after the current modification period.
  • the D2D UE receives the connection release indication and/or ID sent by the remote D2D UE The change indication, the D2D UE releases its PC5 connection with the remote D2D UE, and the remote D2D UE re-initiates the D2D discovery/PC5 connection establishment process with the D2D UE.
  • FIG. 13 is a schematic structural diagram of a D2D UE according to an embodiment of the present invention. As shown in FIG. 13, the D2D UE includes:
  • the first determining unit 31 is configured to: determine whether the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the first allocating unit 32 is configured to: when the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE, re-assign the terminal identifier to the D2D UE;
  • the first sending unit 33 is configured to: send the terminal identifier that is re-allocated by the D2D UE to the second D2D UE, where the second D2D UE is a neighboring D2D UE of the D2D UE, or has established a PC5 connection with the D2D UE. D2D UE.
  • the first determining unit 31 includes:
  • the first parsing sub-unit 311 is configured to: when the received data packet cannot be parsed, determine that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE; or
  • the first receiving sub-unit 312 is configured to: when receiving the ID conflict indication information sent by the third D2D UE, determine that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the conflict indication information is used to indicate that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the first parsing sub-unit 311 is configured to: when the packet data convergence protocol PDCP layer of the D2D UE cannot decrypt the received data packet; or, the D2D UE determines the received data packet.
  • the target IP address does not match its own IP address; or, when the D2D UE application layer determines that the received data packet is in error, the received data packet cannot be parsed.
  • the first receiving sub-unit 312 is configured to: receive the ID conflict indication information sent by the third D2D UE by using the unicast D2D communication physical channel MAC CE; or receive the first through the PC5 interface signaling.
  • the ID conflict indication information sent by the third D2D UE is received; or the ID conflict indication information sent by the third D2D UE is received by the unicast D2D communication data packet; or the ID conflict indication information sent by the third D2D UE is received by the D2D discovery message.
  • the D2D UE is a remote remote D2D UE or a relay relay D2D UE or a D2D UE;
  • the second D2D UE is a remote D2D UE or a relay D2D UE or a D2D UE;
  • the third D2D UE It is a remote D2D UE or a relay D2D UE or a D2D UE.
  • the first sending unit 33 is configured to: send, by using a D2D discovery message, the D2D UE old terminal identifier and/or the reassigned terminal identifier and/or the connection release indication and/or the ID change indication to a second D2D UE; or, by the D2D communication MAC CE, transmitting the D2D UE old terminal identifier and/or the reassigned terminal identifier and/or the connection release indication and/or the ID change indication to the second D2D UE; or, through the PC5
  • the interface signaling sends the D2D UE old terminal identifier and/or the reassigned terminal identifier and/or the connection release indication and/or the ID change indication to the second D2D UE; or the D2D UE old terminal through the D2D communication data packet
  • the identified and/or reassigned terminal identity and/or connection release indication and/or ID change indication are sent to the second D2D UE.
  • the D2D UE further includes:
  • the second sending unit 34 is configured to: send the terminal identifier that is re-allocated by the D2D UE to the base station, and after receiving the terminal identifier re-allocated by the D2D UE, the base station stores the terminal identifier and updates the context information of the D2D UE. in.
  • the second D2D UE after receiving the terminal identifier re-allocated by the D2D UE, the second D2D UE starts to use the terminal identifier re-allocated by the D2D UE as the target ID to send D2D data to the D2D UE;
  • the D2D UE further includes:
  • the first receiving unit 35 is configured to: receive a data packet that is sent by the second D2D UE and that is re-allocated by the D2D UE as the target ID;
  • the third sending unit 36 is configured to: send the D2D data to the second D2D UE by using the terminal identifier re-allocated by the D2D UE as a source ID;
  • the second D2D UE sends the terminal identifier receiving confirmation information to the D2D UE through the D2D communication data packet after receiving the terminal identifier re-allocated by the D2D UE;
  • the D2D UE further includes:
  • the second receiving unit 37 is configured to: receive terminal identification confirmation information sent by the second D2D UE;
  • the fourth sending unit 38 is configured to: send the D2D data to the second D2D UE by using the terminal identifier re-allocated by the D2D UE as a source ID.
  • FIG. 14 is a schematic structural diagram of a D2D UE according to another embodiment of the present invention. As shown in FIG. 14, the D2D UE includes:
  • the second determining unit 41 is configured to: determine whether the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the fifth sending unit 42 is configured to: when the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE, send the ID conflict indication information to the fifth D2D UE, so that the fifth D2D Re-assigning a terminal identifier to the D2D UE by the UE;
  • the third receiving unit 43 is configured to: receive, by the fifth D2D UE, a terminal identifier that is re-allocated for the D2D UE.
  • the second determining unit 41 includes:
  • the second parsing sub-unit 411 is configured to: when the received data packet cannot be parsed, determine that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE; or
  • the second receiving sub-unit 412 is configured to: when receiving the ID conflict indication information sent by the sixth D2D UE, determine that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE;
  • the conflict indication information is used to indicate that the terminal identifier of the D2D UE conflicts with the terminal identifier or the D2D group identifier of the other D2D UE.
  • the second receiving sub-unit 412 is configured to: receive the ID conflict indication information sent by the sixth D2D UE by using the unicast D2D communication MAC CE; or receive the sixth D2D by using the PC5 interface signaling.
  • the ID conflict indication information sent by the UE is received; or the ID conflict indication information sent by the sixth D2D UE is received by the unicast D2D communication data packet; or the ID conflict indication information sent by the sixth D2D UE is received by the D2D discovery message.
  • the fifth sending unit 42 is configured to: send an ID conflict indication to the fifth D2D UE by using a unicast D2D communication MAC CE; or send the ID through the PC5 interface signaling.
  • the conflict indication is sent to the fifth D2D UE; or the ID conflict indication is sent to the fifth D2D UE by the unicast D2D communication data packet; or the ID conflict indication is sent to the fifth D2D UE by the D2D discovery message.
  • the third receiving unit 43 is configured to: receive, by using a unicast D2D communication MAC CE, a terminal identifier that is re-allocated by the fifth D2D UE for the D2D UE; or, by using a PC5 interface Receiving, by the fifth D2D UE, a terminal identifier that is re-allocated for the D2D UE; or receiving, by using a unicast D2D communication data packet, a terminal identifier that is re-allocated by the fifth D2D UE for the D2D UE; Or receiving, by using a D2D discovery message, a terminal identifier that is sent by the fifth D2D UE and re-allocated for the D2D UE.
  • the D2D UE further includes:
  • the sixth sending unit 44 is configured to: send the terminal identifier re-allocated by the D2D UE to a neighboring D2D UE or a D2D UE that has established a connection with the D2D UE.
  • the D2D UE further includes:
  • the seventh sending unit 45 is configured to: send the terminal identifier that is re-allocated by the D2D UE to the base station, and after receiving the terminal identifier re-allocated by the D2D UE, the base station stores the terminal identifier, and updates the context information of the D2D UE. in.
  • the D2D UE is a remote D2D UE
  • the fifth D2D UE is a relay D2D UE.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented by the processor to implement the above-mentioned D2D identification conflict resolution method.
  • the disclosed method and smart device may be implemented in other manners.
  • the device embodiments described above are merely illustrative,
  • the division of the unit is only a logical function division, and the actual implementation may have another division manner, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be ignored. Or not.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. .
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • the functional units in the embodiments of the present invention may all be integrated into one other processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the D2D UE can detect the conflict of the terminal identifier in time and re-acquire the new terminal identifier, thereby ensuring the smooth progress of the D2D communication.
  • the conflict between the terminal identifiers of the D2D UEs of the D2D unicast communication, or the terminal identifiers of the D2D unicast communication and the D2D group identifiers of the multicast communication group is avoided.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本文公布一种设备到设备标识冲突的解决方法、D2D UE，所述方法包括：第一D2D UE判断所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；当所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，重新为所述第一D2D UE分配终端标识；将第一D2D UE重新分配的终端标识发送给第二D2D UE，所述第二D2D UE为所述第一D2D UE的邻近D2D UE，或已经与所述第一D2D UE建立PC5连接的D2D UE。

Description

设备到设备标识冲突的解决方法、设备到设备用户设备 技术领域
本申请涉及但不限于无线通信技术，尤其是一种设备到设备(D2D，Device-to-Device)标识冲突的解决方法、设备到设备用户设备(D2D UE，Device-to-Device User Equipment)。
背景技术
随着无线多媒体业务的发展，人们对高数据速率和用户体验的需求日益增长，从而对传统蜂窝网络的系统容量和覆盖提出了较高要求。另一方面社交网络、近距离数据共享、本地广告等应用的流行使得人们对了解附近感兴趣的人或事物并与之通信(即邻近服务)的需求逐渐增加。传统的基于小区的蜂窝网络在高数据速率以及邻近服务的支持方面存在明显的局限性，在这种需求背景下，代表未来通信技术发展新方向的D2D技术应运而生。D2D技术的应用，可以减轻蜂窝网络的负担、减少用户设备的电池功耗、提高数据速率，并改善网络基础设施的鲁棒性，很好地满足上述高数据速率业务和邻近服务的要求。
D2D技术可以工作在授权频段或非授权频段，允许多个支持D2D功能的用户设备(即D2D UE)在有网络基础设施或无网络基础设施的情况下进行直接发现/直接通信。D2D的应用场景主要有三种：
1)D2D UE1和D2D UE2在蜂窝网络的覆盖下进行数据交互，用户面数据不经过网络基础设施，如图1的模式1；
2)在弱/无覆盖区域的UE中继传输，如图1中的模式2，允许信号质量较差的D2D UE4通过附近有网络覆盖的D2D UE3与网络进行通信，能帮助运营商扩展覆盖、提高容量；
3)在发生地震或紧急情况，蜂窝网络不能正常工作的情况下，允许设备间直接通信，如图1中的模式3，D2D UE5，D2D UE6和D2D UE7间控制面和用户面都不经过网络基础设施而进行一跳或多跳的数据通信。
D2D技术通常包括D2D发现技术和D2D通信技术：D2D发现技术是指用于判断/确定两个或多个D2D UE之间相互邻近(例如在可进行D2D直接通信范围之内)或用于判断/确定第一D2D UE邻近第二D2D UE的技术。D2D通信技术是指D2D UE之间部分或全部通信数据可以不通过网络基础设施而直接进行通信的技术。
一个D2D通信组内的D2D UE通信可采用一对多的组播通信方式，这种方式下组内所有D2D UE都可接收组内某D2D UE发送的数据。而在以上场景2)和3)中，D2D UE可以作为中继节点，使得蜂窝网络覆盖边缘或覆盖外的远端(remote)D2D UE能通过中继(relay)D2D UE与网络进行蜂窝通信，且使得D2D UE间通过relay D2D UE进行D2D通信。该场景下，remote D2D UE和relay D2D UE之间采用一对一D2D通信的方式进行通信。D2D通信数据包的媒体接入控制协议数据单元(MAC PDU，Media Access Control Protocol Data Unit)头部包含源和目标ID域，对于D2D通信组，MAC PDU头部中目标ID域内容为D2D组标识(ProSe Layer-2Group ID)，该D2D组标识为24比特，是由DPF(Direct Provisioning Function，ProSe Function的组成部分)分配。而对于一对一D2D通信，MAC PDU头部中目标ID域内容为目标D2D UE的终端标识(ProSe UE ID)，该终端标识也为24比特，有可能预配置在移动设备(ME，Mobile Equipment)或通用集成电路卡(UICC，Universal Integrated Circuit Card)中，或由Prose function配置给D2D UE，或由D2D UE自身分配，并不保证全局唯一性。D2D通信中，一对一单播通信和一对多组播通信可同时存在，有可能会出现D2D UE的一对一单播通信的ProSe UE ID与其它D2D UE的一对一单播通信的ProSe UE ID相同，或D2D UE的一对一单播通信的ProSe UE ID与一对多组播通信的D2D组标识(ProSe Layer-2Group ID)相同的情况。将导致具有该相同ID的D2D UE及D2D通信组内所有D2D UE都将接收目标为该相同ID的单播或组播MAC PDU数据包。例如，图2中D2D UE2与D2D UE3属于同一个D2D通信组，可进行D2D组通信，D2D UE1不属于该D2D通信组，但D2D UE1可以与D2D UE2或D2D UE3进行一对一D2D发现/通信。假定D2D UE1的单播ProSe UE ID与ProSe通信组的ProSe Layer-2Group ID相同，则D2D UE1和该D2D通信组的D2D UE(包含D2D UE2，D2D UE3)都将接收目标ID为该相同ID的 MAC PDU。而相关技术尚未有能解决上述D2D标识冲突问题的方法。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种D2D标识冲突的解决方法、D2D UE。
本发明实施例提供的D2D标识冲突的解决方法应用于第一D2D UE，所述方法包括：
判断所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
当所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，重新为所述第一D2D UE分配终端标识；
将第一D2D UE重新分配的终端标识发送给第二D2D UE，所述第二D2D UE为所述第一D2D UE的邻近D2D UE，或已经与所述第一D2D UE建立PC5连接的D2D UE。
本发明实施例中，所述判断所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突，包括：
无法解析所接收到的数据包时，则判定所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
接收到第三D2D UE发送的ID冲突指示信息时，则判定所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，所述无法解析所接收到的数据包，包括：
所述第一D2D UE的分组数据汇聚协议(PDCP，Packet Data Convergence Protocol)层无法解密所接收的数据包；或者，
所述第一D2D UE判断所接收的数据包的目标IP地址与自身IP地址不 符；或者，
所述第一D2D UE应用层判断所接收的数据包出错。
本发明实施例中，所述接收到第三D2D UE发送的ID冲突指示信息，包括：
通过单播D2D通信物理信道MAC CE接收到第三D2D UE发送的ID冲突指示信息；或者，
通过PC5接口信令接收到第三D2D UE发送的ID冲突指示信息；或者，
通过单播D2D通信数据包接收到第三D2D UE发送的ID冲突指示信息；或者，
通过D2D发现消息接收到第三D2D UE发送的ID冲突指示信息。
本发明实施例中，所述接收到第三D2D UE发送的ID冲突指示信息之前，所述第三D2D UE检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，所述第三D2D UE检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突，包括：
所述第三D2D UE通过所接收的第一D2D UE发送的D2D发现消息检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同；或者，
所述第三D2D UE通过所接收的第一D2D UE发送的PC5接口信令检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同；或者，
所述第三D2D UE通过所接收的第一D2D UE发送的数据包MAC PDU检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同。
本发明实施例中，所述第一D2D UE为远端remote D2D UE或中继relay D2D UE或D2D UE；所述第二D2D UE为remote D2D UE或relay D2D UE或D2D UE；所述第三D2D UE为remote D2D UE或relay D2D UE或D2D UE。
本发明实施例中，所述将第一D2D UE重新分配的终端标识发送给第二D2D UE，包括：
通过D2D发现消息将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
通过D2D通信MAC CE将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
通过PC5接口信令将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
通过D2D通信数据包将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE。
本发明实施例中，所述重新为所述第一D2D UE分配终端标识后，所述方法还包括：
将所述第一D2D UE重新分配的终端标识发送给基站，基站接收到所述第一D2D UE重新分配的终端标识后存储该终端标识并更新至所述第一D2D UE的上下文信息中。
本发明实施例中，所述第二D2D UE接收到所述第一D2D UE重新分配的终端标识后，开始使用第一D2D UE重新分配的终端标识作为目标ID向所述第一D2D UE发送D2D数据；相应地，
所述方法还包括：接收到所述第二D2D UE发送的以第一D2D UE重新分配的终端标识作为目标ID的数据包后，开始使用所述第一D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据；
或者，所述第二D2D UE接收到第一D2D UE重新分配的终端标识后，通过D2D通信数据包将终端标识接收确认信息发送给所述第一D2D UE；相应地，
所述方法还包括：接收到所述第二D2D UE发送的终端标识确认信息后，开始使用所述第一D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据。
本发明实施例中，所述第二D2D UE接收到所述第一D2D UE发送的连 接释放指示和/或ID更改指示后，释放与所述第一D2D UE之间的PC5连接。
本发明实施例中，所述将第一D2D UE重新分配的终端标识发送给第二D2D UE后，所述方法还包括：
所述第一D2D UE和第二D2D UE在当前修改周期之后开始使用重新分配的终端标识进行数据传输；所述第二D2D UE为已经与所述第一D2D UE建立PC5连接的D2D UE；所述修改周期由基站或者ProSe服务器或核心网网元配置。
本发明另一实施例提供的D2D标识冲突的解决方法应用于第四D2D UE，所述方法包括：
判断所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
当所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，将ID冲突指示信息发送给第五D2D UE，从而所述第五D2D UE为所述第四D2D UE重新分配终端标识；
接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识。
本发明实施例中，所述判断所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突，包括：
无法解析所接收到的数据包时，则判定所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
接收到第六D2D UE发送的ID冲突指示信息时，则判定所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，所述接收到第六D2D UE发送的ID冲突指示信息，包括：
通过单播D2D通信MAC CE接收到第六D2D UE发送的ID冲突指示信 息；或者，
通过PC5接口信令接收到第六D2D UE发送的ID冲突指示信息；或者，
通过单播D2D通信数据包接收到第六D2D UE发送的ID冲突指示信息；或者，
通过D2D发现消息接收到第六D2D UE发送的ID冲突指示信息。
本发明实施例中，所述接收到第六D2D UE发送的ID冲突指示信息之前，所述第六D2D UE检测到第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，所述第六D2D UE检测到第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识发生冲突，包括：
所述第六D2D UE通过所接收的第四D2D UE发送的D2D发现消息检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同；或者，
所述第六D2D UE通过所接收的第四D2D UE发送的PC5接口信令检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同；或者，
所述第六D2D UE通过所接收的第四D2D UE发送的数据包MAC PDU检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同。
本发明实施例中，所述将ID冲突指示信息发送给第五D2D UE，包括：
通过单播D2D通信MAC CE将ID冲突指示发送给第五D2D UE；或者，
通过PC5接口信令将ID冲突指示发送给第五D2D UE；或者，
通过单播D2D通信数据包将ID冲突指示发送给第五D2D UE；或者，
通过D2D发现消息将ID冲突指示发送给第五D2D UE。
本发明实施例中，所述接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识，包括：
通过单播D2D通信MAC CE接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
通过PC5接口信令接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
通过单播D2D通信数据包接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
通过D2D发现消息接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识。
本发明实施例中，所述接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识后，所述方法还包括：
将所述第四D2D UE重新分配的终端标识发送给邻近的D2D UE或已经与所述第四D2D UE建立连接的D2D UE。
本发明实施例中，所述接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识后，所述方法还包括：
将所述第四D2D UE重新分配的终端标识发送给基站，基站接收所述第四D2D UE重新分配的终端标识后存储该终端标识，并更新至所述第四D2D UE的上下文信息中。
本发明实施例中，所述第四D2D UE为remote D2D UE，所述第五D2D UE为relay D2D UE。
本发明实施例提供的D2D UE包括：
第一判断单元，设置为：判断所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
第一分配单元，设置为：当所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，重新为所述D2D UE分配终端标识；
第一发送单元，设置为：将D2D UE重新分配的终端标识发送给第二D2D UE，所述第二D2D UE为所述D2D UE的邻近D2D UE，或已经与所述D2D UE建立PC5连接的D2D UE。
本发明实施例中，所述第一判断单元包括：
第一解析子单元，设置为：当无法解析所接收到的数据包时，则判定所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
第一接收子单元，设置为：接收到第三D2D UE发送的ID冲突指示信息时，则判定所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，所述第一解析子单元，设置为：当所述D2D UE的分组数据汇聚协议PDCP层无法解密所接收的数据包；或者，所述D2D UE判断所接收的数据包的目标IP地址与自身IP地址不符；或者，所述D2D UE应用层判断所接收的数据包出错时，则无法解析所接收到的数据包。
本发明实施例中，所述第一接收子单元，设置为：通过单播D2D通信物理信道MAC CE接收到第三D2D UE发送的ID冲突指示信息；或者，通过PC5接口信令接收到第三D2D UE发送的ID冲突指示信息；或者，通过单播D2D通信数据包接收到第三D2D UE发送的ID冲突指示信息；或者，通过D2D发现消息接收到第三D2D UE发送的ID冲突指示信息。
本发明实施例中，所述D2D UE为远端remote D2D UE或中继relay D2D UE或D2D UE；所述第二D2D UE为remote D2D UE或relay D2D UE或D2D UE；所述第三D2D UE为remote D2D UE或relay D2D UE或D2D UE。
本发明实施例中，所述第一发送单元，设置为：通过D2D发现消息将D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，通过D2D通信MAC CE将D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，通过PC5接口信令将D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，通过D2D通信数据包将D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE。
本发明实施例中，所述D2D UE还包括：
第二发送单元，设置为：将所述D2D UE重新分配的终端标识发送给基站，基站接收到所述D2D UE重新分配的终端标识后存储该终端标识并更新至所述D2D UE的上下文信息中。
本发明实施例中，所述第二D2D UE接收到所述D2D UE重新分配的终端标识后，开始使用D2D UE重新分配的终端标识作为目标ID向所述D2D UE发送D2D数据；相应地，
所述D2D UE还包括：
第一接收单元，设置为：接收所述第二D2D UE发送的以D2D UE重新分配的终端标识作为目标ID的数据包；
第三发送单元，设置为：使用所述D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据；
或者，所述第二D2D UE接收到D2D UE重新分配的终端标识后，通过D2D通信数据包将终端标识接收确认信息发送给所述D2D UE；
所述D2D UE还包括：
第二接收单元，设置为：接收所述第二D2D UE发送的终端标识确认信息；
第四发送单元，设置为：使用所述D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据。
本发明另一实施例提供的D2D UE包括：
第二判断单元，设置为：判断所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
第五发送单元，设置为：当所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，将ID冲突指示信息发送给第五D2D UE，从而所述第五D2D UE为所述D2D UE重新分配终端标识；
第三接收单元，设置为：接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识。
本发明实施例中，所述第二判断单元包括：
第二解析子单元，设置为：当无法解析所接收到的数据包时，则判定所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
第二接收子单元，设置为：接收到第六D2D UE发送的ID冲突指示信息时，则判定所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，所述第二接收子单元，设置为：通过单播D2D通信MAC CE接收到第六D2D UE发送的ID冲突指示信息；或者，通过PC5接口信令接收到第六D2D UE发送的ID冲突指示信息；或者，通过单播D2D通信数据包接收到第六D2D UE发送的ID冲突指示信息；或者，通过D2D发现消息接收到第六D2D UE发送的ID冲突指示信息。
本发明实施例中，所述第五发送单元，设置为：通过单播D2D通信MAC CE将ID冲突指示发送给第五D2D UE；或者，通过PC5接口信令将ID冲突指示发送给第五D2D UE；或者，通过单播D2D通信数据包将ID冲突指示发送给第五D2D UE；或者，通过D2D发现消息将ID冲突指示发送给第五D2D UE。
本发明实施例中，所述第三接收单元，设置为：通过单播D2D通信MAC CE接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识；或者，通过PC5接口信令接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识；或者，通过单播D2D通信数据包接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识；或者，通过D2D发现消息接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识。
本发明实施例中，所述D2D UE还包括：
第六发送单元，设置为：将所述D2D UE重新分配的终端标识发送给邻近的D2D UE或已经与所述D2D UE建立连接的D2D UE。
本发明实施例中，所述D2D UE还包括：
第七发送单元，设置为：将所述D2D UE重新分配的终端标识发送给基站，基站接收所述D2D UE重新分配的终端标识后存储该终端标识，并更新至所述D2D UE的上下文信息中。
本发明实施例中，所述D2D UE为remote D2D UE，所述第五D2D UE为relay D2D UE。
本发明另一实施例提供的计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述方法。
本发明实施例的技术方案中，第一D2D UE判断所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；当所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，重新为所述第一D2D UE分配终端标识；将第一D2D UE重新分配的终端标识发送给第二D2D UE。如此，D2D UE能够及时检测到终端标识的冲突并重新获取新的终端标识，保证了D2D通信顺利进行。避免了D2D单播通信的D2D UE的终端标识之间，或D2D单播通信的终端标识与组播通信组的D2D组标识之间的冲突。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1是D2D技术应用模式示意图；
图2是D2D通信场景示意图；
图3为本发明实施例的D2D标识冲突的解决方法的流程示意图；
图4为本发明另一实施例的D2D标识冲突的解决方法的流程示意图；
图5为本发明实施例一的场景示意图；
图6为本发明实施例一的D2D标识冲突的解决方法流程示意图；
图7为本发明实施例二的场景示意图；
图8为本发明实施例二的D2D标识冲突的解决方法流程示意图；
图9为本发明实施例三的场景示意图；
图10为本发明实施例三的D2D标识冲突的解决方法流程示意图；
图11为本发明实施例四的场景示意图；
图12为本发明实施例四的D2D标识冲突的解决方法流程示意图；
图13为本发明实施例的D2D UE的结构组成示意图；
图14为本发明另一实施例的D2D UE的结构组成示意图。
本发明的实施方式
下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
图3为本发明实施例的D2D标识冲突的解决方法的流程示意图，本示例中的D2D标识冲突的解决方法应用于第一D2D UE，如图3所示，所述D2D标识冲突的解决方法包括以下步骤：
步骤301：判断所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突。
本发明实施例中，判断所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突可通过以下方式进行：
无法解析所接收到的数据包时，则判定所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
接收到第三D2D UE发送的ID冲突指示信息时，则判定所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
上述方案中，无法解析所接收到的数据包包括以下几种情况：
所述第一D2D UE的分组数据汇聚协议PDCP层无法解密所接收的数据包；或者，
所述第一D2D UE判断所接收的数据包的目标IP地址与自身IP地址不符；或者，
所述第一D2D UE应用层判断所接收的数据包出错。
上述方案中，第一D2D UE接收到第三D2D UE发送的ID冲突指示信息可通过但不局限于以下形式接收：
通过单播D2D通信物理信道MAC CE接收到第三D2D UE发送的ID冲突指示信息；或者，
通过PC5接口信令接收到第三D2D UE发送的ID冲突指示信息；或者，
通过单播D2D通信数据包接收到第三D2D UE发送的ID冲突指示信息；或者，
通过D2D发现消息接收到第三D2D UE发送的ID冲突指示信息。
本发明实施例中，第一D2D UE接收到第三D2D UE发送的ID冲突指示信息之前，所述第三D2D UE检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
其中，所述第三D2D UE通过所接收的第一D2D UE发送的D2D发现消息检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同；或者，
所述第三D2D UE通过所接收的第一D2D UE发送的PC5接口信令检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同；或者，
所述第三D2D UE通过所接收的第一D2D UE发送的数据包MAC PDU检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同。
上述方案是三种获取第一D2D UE的终端标识并检测出发送冲突的方式，分别是通过1)D2D发现消息；2)PC5接口信令；3)MAC PDU中包含的ID。其中，PC5接口信令可以是PC5连接建立消息，例如直连请求(direct communication request)消息，PC5连和其它两个是不同的方式。
本发明实施例中，所述第一D2D UE为远端remote D2D UE或中继relay D2D UE或D2D UE；所述第二D2D UE为remote D2D UE或relay D2D UE或D2D UE；所述第三D2D UE为remote D2D UE或relay D2D UE或D2D  UE。
这里，D2D UE是指非remote D2D UE、非relay D2D UE的普通的D2D UE。
步骤302：当所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，重新为所述第一D2D UE分配终端标识。
本发明实施例中，由第一D2D UE重新为其自己分配新的终端标识，重新分配的新的终端标识与原来的第一D2D UE的旧的终端标识不同。
步骤303：将第一D2D UE重新分配的终端标识发送给第二D2D UE，所述第二D2D UE为所述第一D2D UE的邻近D2D UE，或已经与所述第一D2D UE建立PC5连接的D2D UE。
本发明实施例中，由第一D2D UE将第一D2D UE重新分配的终端标识发送给第二D2D UE。
通过D2D发现消息将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
通过D2D通信MAC CE将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
通过PC5接口信令将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
通过D2D通信数据包将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE。
上述方案中，第一D2D UE的终端标识重新分配后，释放原有的PC5连接，D2D UE之间使用第一D2D UE重新分配的终端标识重新建立连接，因此，第一D2D UE将旧的终端标识和/或重新分配的终端标识发送给第二D2D UE的同时，还可以将连接释放指示和/或ID更改指示发送给第二D2D UE。
本发明实施例中，重新为所述第一D2D UE分配终端标识后，第一D2D UE将所述第一D2D UE重新分配的终端标识发送给基站，基站接收到所述第一D2D UE重新分配的终端标识后存储该终端标识并更新至所述第一D2D UE的上下文信息中。
基于上述方案，第二D2D UE接收到所述第一D2D UE发送的连接释放指示和/或ID更改指示后，释放与所述第一D2D UE之间的PC5连接。
本发明实施例中，第二D2D UE接收到所述第一D2D UE重新分配的终端标识后，开始使用第一D2D UE重新分配的终端标识作为目标ID向所述第一D2D UE发送D2D数据；相应地，第一D2D UE接收到所述第二D2D UE发送的以第一D2D UE重新分配的终端标识作为目标ID的数据包后，开始使用所述第一D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据。或者，第二D2D UE接收到第一D2D UE重新分配的终端标识后，通过D2D通信数据包将终端标识接收确认信息发送给所述第一D2D UE；相应地，第一D2D UE接收到所述第二D2D UE发送的终端标识确认信息后，开始使用所述第一D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据。
本发明实施例中，将第一D2D UE重新分配的终端标识发送给第二D2D UE后，第一D2D UE和第二D2D UE在当前修改周期之后开始使用重新分配的终端标识进行数据传输；所述第二D2D UE为已经与所述第一D2D UE建立PC5连接的D2D UE；所述修改周期由基站或者ProSe服务器或核心网网元配置。
图4为本发明另一实施例的D2D标识冲突的解决方法的流程示意图，本示例中的D2D标识冲突的解决方法应用于第四D2D UE，如图4所示，所述D2D标识冲突的解决方法包括以下步骤：
步骤401：判断所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突。
本发明实施例中，判断所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突可通过以下方式进行：
无法解析所接收到的数据包时，则判定所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
接收到第六D2D UE发送的ID冲突指示信息时，则判定所述第四D2D  UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，第四D2D UE接收到第六D2D UE发送的ID冲突指示信息可以通过但不局限于以下方式接收：
通过单播D2D通信MAC CE接收到第六D2D UE发送的ID冲突指示信息；或者，
通过PC5接口信令接收到第六D2D UE发送的ID冲突指示信息；或者，
通过单播D2D通信数据包接收到第六D2D UE发送的ID冲突指示信息；或者，
通过D2D发现消息接收到第六D2D UE发送的ID冲突指示信息。
本发明实施例中，第四D2D UE接收到第六D2D UE发送的ID冲突指示信息之前，所述第六D2D UE检测到第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识发生冲突。
其中，所述第六D2D UE通过所接收的第四D2D UE发送的D2D发现消息检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同；或者，
所述第六D2D UE通过所接收的第四D2D UE发送的PC5接口信令检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同；或者，
所述第六D2D UE通过所接收的第四D2D UE发送的数据包MAC PDU检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同。
步骤402：当所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，将ID冲突指示信息发送给第五D2D UE，从而所述第五D2D UE为所述第四D2D UE重新分配终端标识。
本发明实施例中，第四D2D UE将ID冲突指示信息发送给第五D2D UE可通过但不局限于以下方式发送：
通过单播D2D通信MAC CE将ID冲突指示发送给第五D2D UE；或者，
通过PC5接口信令将ID冲突指示发送给第五D2D UE；或者，
通过单播D2D通信数据包将ID冲突指示发送给第五D2D UE；或者，
通过D2D发现消息将ID冲突指示发送给第五D2D UE。
步骤403：接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识。
本发明实施例中，第四D2D UE接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识，也即第五D2D UE将为所述第四D2D UE重新分配的终端标识发送至第四D2D UE。
第四D2D UE通过单播D2D通信MAC CE接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
通过PC5接口信令接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
通过单播D2D通信数据包接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
通过D2D发现消息接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识。
本发明实施例中，第四D2D UE获得重新分配的终端标识后，将重新分配的终端标识发送给邻近的D2D UE或已经与所述第四D2D UE建立连接的D2D UE。
本发明实施例中，第四D2D UE获得重新分配的终端标识后，将重新分配的终端标识发送给基站，基站接收所述第四D2D UE重新分配的终端标识后存储该终端标识，并更新至所述第四D2D UE的上下文信息中。
上述方案中，所述第四D2D UE为remote D2D UE，所述第五D2D UE为relay D2D UE。
下面结合实际场景对本发明实施例的D2D标识冲突的解决方法做进一 步详细阐述。需要注意的是，本发明实施例中的D2D UE可以为relay D2D UE、或者remote D2D UE、或者普通的D2D UE。
实施例一
本实施例描述的是relay D2D UE的单播ProSe D2D UE ID与ProSe通信组ID相同的场景，图5为本实施例场景示意图。如图5所示，D2D UE3与D2D UE2(remote D2D UE)属于同一个D2D通信组，可进行D2D组通信，D2D UE1(relay D2D UE)不属于该D2D通信组，但D2D UE1可以与D2D UE2或D2D UE3进行一对一D2D发现/通信。假定relay D2D UE的单播ProSe D2D UE ID与ProSe通信组(由remote D2D UE和D2D UE3组成)的ProSe Layer-2Group ID相同，也即发生ID冲突，则relay D2D UE和该D2D通信组的D2D UE(包含D2D UE2，D2D UE3)都将接收目标ID为该相同ID的MAC PDU。为解决上述ID冲突问题，可采用本发明实施例的方案，图6为本发明实施例一D2D标识冲突的解决方法流程示意图，如图6所示，本实施例方法包括以下步骤：
步骤601：remote D2D UE通过D2D发现过程获得relay D2D UE的单播ProSe D2D UE ID。
其中，remote D2D UE在通过接收到的relay D2D UE发送的D2D发现消息获得relay D2D UE的单播ProSe D2D UE ID。
步骤602：remote D2D UE检测到relay D2D UE的单播ProSe D2D UE ID与自身加入的D2D通信组的layer 2Group ID相同，则判定relay D2D UE的ProSe D2D UE ID与D2D组ID发生了ID冲突。
可选地，remote D2D UE还可以在PC5连接建立过程中获得relay D2D UE的单播ProSe D2D UE ID，并检测到relay D2D UE的ID与自身组ID冲突。其中，remote D2D UE可以通过接收到的relay D2D UE发送的PC5连接建立响应消息获得relay D2D UE的单播ProSe D2D UE ID。或者，remote D2D UE可以在与relay D2D UE建立PC5连接后，通过接收relay D2D UE的D2D通信数据包得知relay D2D UE的D2D UE ID并检测到relay D2D UE的 ProSe D2D UE ID与自身组ID冲突。
步骤603：remote D2D UE向relay D2D UE发送ID冲突指示信息，用于指示relay D2D UE的ProSe D2D UE ID与其它D2D UE ID或组ID发生冲突。
其中，remote D2D UE可通过以下方式向relay D2D UE发送ID冲突指示信息：
1)remote D2D UE在与relay D2D UE之间的PC5连接建立完成后，通过单播D2D通信MAC CE向relay D2D UE发送ID冲突指示信息；或者，
2)remote D2D UE在与relay D2D UE完成relay发现之后，通过PC5接口信令向relay D2D UE发送ID冲突指示信息，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令；或者，
3)remote D2D UE在与relay D2D UE之间的PC5连接建立完成后，通过单播D2D通信数据包的方式向relay D2D UE发送ID冲突指示信息；或者，
4)remote D2D UE通过D2D发现消息向relay D2D UE发送ID冲突指示信息，该D2D发现消息中还包含relay D2D UE的ProSe D2D UE ID。
步骤604：relay D2D UE接收到remote D2D UE发送的ID冲突指示信息后，重新分配自身ProSe D2D UE ID。
步骤605：relay D2D UE重新分配自身ProSe D2D UE ID后，将自身更新的ProSe D2D UE ID发送给已经与其建立PC5连接的remote D2D UE以及附近的D2D UE。
relay D2D UE可通过以下方式发送ID更改通知信息：
1)relay D2D UE通过单播D2D通信MAC CE向已经与其建立PC5连接的remote D2D UE发送自身更新的ProSe D2D UE ID；或者，
2)relay D2D UE通过PC5接口信令向remote D2D UE发送自身更新的ProSe D2D UE ID，其中PC5接口信令可以为PC5连接建立响应消息，或者新增PC5接口信令；或者，
3)relay D2D UE通过单播D2D通信数据包的方式向已经与其建立PC5连接的remote D2D UE发送自身更新的ProSe D2D UE ID；或者，
4)relay D2D UE通过D2D发现消息向remote D2D UE发送自身更新的ProSe D2D UE ID，该D2D发现消息中包含该relay D2D UE的新的ProSe D2D UE ID，或者包含该relay D2D UE的新的和旧的ProSe D2D UE ID。
relay D2D UE将连接释放指示和/或ID更改指示发送给已经与其建立PC5连接的remote D2D UE。
步骤606：已经与relay D2D UE建立PC5连接的remote D2D UE接收到relay D2D UE发送的更新的ProSe D2D UE ID后，remote D2D UE向relay D2D UE发送ID更改通知确认信息。
例如，ID更改通知确认信息可以为以relay D2D UE更新的ProSe D2D UE ID为目标ID的数据包，或者，内容为ID更改通知确认的D2D通信数据包，或者，可通过单播D2D通信MAC CE发送，或者，可通过PC5接口信令发送，或者，可通过D2D发现消息发送。
可选地，remote D2D UE收到relay D2D UE发送的更新的ProSe D2D UE ID后开始使用更新的ProSe D2D UE ID作为目标ID向relay D2D UE发送D2D通信数据包。而relay D2D UE在接收到remote D2D UE发送的ID更改通知确认信息后开始使用更新的ProSe D2D UE ID作为源ID向该remote D2D UE发送D2D通信数据包。或者，relay D2D UE和已经与其建立PC5连接的remote D2D UE在当前修改周期之后开始使用新的ProSe D2D UE ID标识信息。
另外，若remote D2D UE接收到relay D2D UE发送的连接释放指示和/或ID更改指示，则Remote D2D UE释放其与relay D2D UE之间的PC5连接，并重新发起relay发现/PC5连接建立过程。若remote D2D UE还接收到relay D2D UE发送的更新的ProSe D2D UE ID，则remote D2D UE可直接向该relay D2D UE重新发起PC5连接建立过程。
实施例二
本实施例描述的是remote D2D UE的单播ProSe D2D UE ID与ProSe通信组ID相同的场景，图7为本实施例场景示意图。如图7所示，D2D UE3 与D2D UE2(relay D2D UE)属于同一个D2D通信组，可进行D2D组通信，D2D UE1(remote D2D UE)不属于该D2D通信组，但D2D UE1可以与D2D UE2或D2D UE3进行一对一D2D发现/通信。假定remote D2D UE的单播ProSe D2D UE ID与ProSe通信组(由D2D UE2和D2D UE3组成)的ProSe Layer-2Group ID相同，也即发生ID冲突，则remote D2D UE和该D2D通信组的D2D UE(包含D2D UE2，D2D UE3)都将接收目标ID为该相同ID的MAC PDU。为解决上述ID冲突问题，可采用本发明实施例的方案，图8为本发明实施例二D2D标识冲突的解决方法流程示意图，如图8所示，本实施例方法包括以下步骤：
步骤801：relay D2D UE通过D2D发现过程获得remote D2D UE的单播ProSe D2D UE ID。
relay D2D UE通过接收到remote D2D UE发送的D2D发现消息获得relay D2D UE的单播ProSe D2D UE ID。
步骤802：relay D2D UE在PC5连接建立过程中获得remote D2D UE的单播ProSe D2D UE ID。
其中，relay D2D UE可以通过接收到的remote D2D UE发送的PC5连接建立请求消息获得remote D2D UE的单播ProSe D2D UE ID。或者，relay D2D UE可以在与remote D2D UE建立PC5连接后，通过接收remote D2D UE的D2D通信数据包得知remote D2D UE的D2D UE ID。
步骤803：relay D2D UE检测到remote D2D UE的单播ProSe D2D UE ID与自身加入的D2D通信组的layer 2Group ID相同，则判定remote D2D UE的ProSe D2D UE ID与D2D组ID发生了ID冲突。
步骤804：relay D2D UE向remote D2D UE发送ID冲突指示信息，用于指示remote D2D UE的ProSe D2D UE ID与其它D2D UE ID或组ID发生冲突。
其中relay D2D UE可通过以下方式向remote D2D UE发送ID冲突指示信息：
1)relay D2D UE在与remote D2D UE之间的PC5连接建立完成后，通 过单播D2D通信MAC CE向remote D2D UE发送ID冲突指示信息；或者，
2)relay D2D UE在与remote D2D UE完成relay发现之后，通过PC5接口信令向remote D2D UE发送ID冲突指示信息，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令；或者，
3)relay D2D UE在与remote D2D UE之间的PC5连接建立完成后，通过单播D2D通信数据包的方式向remote D2D UE发送ID冲突指示信息；或者，
4)relay D2D UE通过D2D发现消息向remote D2D UE发送ID冲突指示信息，该D2D发现消息中还包含remote D2D UE的ProSe D2D UE ID。
步骤805：remote D2D UE接收到relay D2D UE发送的ID冲突指示信息后，重新分配自身ProSe D2D UE ID。
步骤806：remote D2D UE重新分配自身ProSe D2D UE ID后，将自身更新的ProSe D2D UE ID发送给已经与其建立PC5连接的relay D2D UE以及附近的D2D UE。
其中，remote D2D UE可通过以下方式发送ID更改通知信息：
1)remote D2D UE通过单播D2D通信MAC CE向已经与其建立PC5连接的relay D2D UE发送自身更新的ProSe D2D UE ID；或者，
2)remote D2D UE通过PC5接口信令向relay D2D UE发送自身更新的ProSe D2D UE ID，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令；或者，
3)remote D2D UE通过单播D2D通信数据包的方式向已经与其建立PC5连接的relay D2D UE发送自身更新的ProSe D2D UE ID；或者，
4)remote D2D UE通过MODE B发现过程中D2D发现消息向relay D2D UE发送自身更新的ProSe D2D UE ID，该D2D发现消息中包含该remote D2D UE的新的ProSe D2D UE ID，或者包含该remote D2D UE的新的和旧的ProSe D2D UE ID。
remote D2D UE将连接释放指示和/或ID更改指示发送给已经与其建立PC5连接的relay D2D UE。
步骤807：已经与remote D2D UE建立PC5连接的relay D2D UE接收到remote D2D UE发送的更新的ProSe D2D UE ID后，relay D2D UE向remote D2D UE发送ID更改通知确认信息。
例如，ID更改通知确认信息可以为以remote D2D UE更新的ProSe D2D UE ID为目标ID的数据包，或者，内容为ID更改通知确认的D2D通信数据包，或者，可通过单播D2D通信MAC CE发送，或者，可通过PC5接口信令发送，或者，可通过D2D发现消息发送。
可选地，relay D2D UE收到remote D2D UE发送的更新的ProSe D2D UE ID后开始使用更新的ProSe D2D UE ID作为目标ID向remote D2D UE发送D2D通信数据包。而remote D2D UE在接收到relay D2D UE发送的ID更改通知确认信息后开始使用更新的ProSe D2D UE ID作为源ID向该relay D2D UE发送D2D通信数据包。或者，remote D2D UE和已经与其建立PC5连接的relay D2D UE在当前修改周期之后开始使用新的ProSe D2D UE ID标识信息。
另外，若relay D2D UE接收到remote D2D UE发送的连接释放指示和/或ID更改指示，则relay D2D UE释放其与remote D2D UE之间的PC5连接，remote D2D UE重新发起relay发现/PC5连接建立过程。
实施例三
本实施例描述的是一个relay D2D UE下的两个remote D2D UE的单播ProSe D2D UE ID之间发生冲突的场景，图9为本实施例场景示意图。如图9所示，remote D2D UE1通过relay D2D UE的中继进行D2D通信，然后remote D2D UE2发现了该relay D2D UE并想与该relay D2D UE建立PC5连接，remote D2D UE1和remote D2D UE1的ProSe D2D UE ID相同。图10为本发明实施例三方法流程示意图，如图10所示，本实施例方法包括以下步骤：
步骤111：remote D2D UE1发现relay D2D UE，relay D2D UE获得remote D2D UE1的ProSe D2D UE ID。
relay D2D UE可以通过D2D发现过程或PC5连接建立过程或D2D通信数据包获得remote D2D UE1的ProSe D2D UE ID。
步骤112：relay D2D UE通过D2D发现过程获得remote D2D UE2的单播ProSe D2D UE ID。
relay D2D UE通过接收到remote D2D UE2发送的D2D发现消息获得relay D2D UE的单播ProSe D2D UE ID。
步骤113：relay D2D UE在PC5连接建立过程中获得remote D2D UE2的单播ProSe D2D UE ID。
relay D2D UE可以通过接收到的remote D2D UE2发送的PC5连接建立请求消息获得remote D2D UE的单播ProSe D2D UE ID。或者，relay D2D UE可以在与remote D2D UE2建立PC5连接后，通过接收remote D2D UE2的D2D通信数据包得知remote D2D UE的D2D UE ID。
步骤114：relay D2D UE检测到remote D2D UE1和remote D2D UE2的ProSe D2D UE ID相同，则判定remote D2D UE1和remote D2D UE2的ProSe D2D UE ID发生了ID冲突。
步骤115：relay D2D UE向remote D2D UE2发送ID冲突指示信息，用于指示remote D2D UE2的ProSe D2D UE ID与其它D2D UE ID或组ID发生冲突。
其中，relay D2D UE可通过以下方式向remote D2D UE2发送ID冲突指示信息：
1)relay D2D UE在与remote D2D UE2之间的PC5连接建立完成后，通过单播D2D通信MAC CE向remote D2D UE2发送ID冲突指示信息；或者，
2)relay D2D UE在与remote D2D UE2完成relay发现之后，通过PC5接口信令向remote D2D UE2发送ID冲突指示信息，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令；或者，
3)relay D2D UE在与remote D2D UE2之间的PC5连接建立完成后，通过单播D2D通信数据包的方式向remote D2D UE2发送ID冲突指示信息；或者，
4)relay D2D UE通过D2D发现消息向remote D2D UE2发送ID冲突指示信息，该D2D发现消息中还包含remote D2D UE2的ProSe D2D UE ID。
步骤116：remote D2D UE2接收到relay D2D UE发送的ID冲突指示信息后，重新分配自身ProSe D2D UE ID。
步骤117：remote D2D UE2重新分配自身ProSe D2D UE ID后，将自身更新的ProSe D2D UE ID发送给已经与其建立PC5连接的relay D2D UE以及附近的D2D UE。
其中，remote D2D UE2可通过以下方式发送ID更改通知信息：
1)remote D2D UE2通过单播D2D通信MAC CE向已经与其建立PC5连接的relay D2D UE发送自身更新的ProSe D2D UE ID；或者，
2)remote D2D UE2通过PC5接口信令向relay D2D UE发送自身更新的ProSe D2D UE ID，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令；或者，
3)remote D2D UE2通过单播D2D通信数据包的方式向已经与其建立PC5连接的relay D2D UE发送自身更新的ProSe D2D UE ID；或者，
4)remote D2D UE2通过MODE B发现过程中D2D发现消息向relay D2D UE发送自身更新的ProSe D2D UE ID，该D2D发现消息中包含该remote D2D UE的新的ProSe D2D UE ID，或者包含该remote D2D UE的新的和旧的ProSe D2D UE ID。
remote D2D UE2将连接释放指示和/或ID更改指示发送给已经与其建立PC5连接的relay D2D UE。
步骤118：已经与remote D2D UE2建立PC5连接的relay D2D UE接收到remote D2D UE2发送的更新的ProSe D2D UE ID后，relay D2D UE向remote D2D UE2发送ID更改通知确认信息。
例如，ID更改通知确认信息可以为以remote D2D UE2更新的ProSe D2D UE ID为目标ID的数据包，或者，内容为ID更改通知确认的D2D通信数据包，或者，可通过单播D2D通信MAC CE发送，或者，可通过PC5接口信令发送，或者，可通过D2D发现消息发送。
可选地，relay D2D UE收到remote D2D UE2发送的更新的ProSe D2D UE ID后开始使用更新的ProSe D2D UE ID作为目标ID向remote D2D UE2发送D2D通信数据包。而remote D2D UE2在接收到relay D2D UE发送的ID更改通知确认信息后开始使用更新的ProSe D2D UE ID作为源ID向该relay D2D UE发送D2D通信数据包。或者，remote D2D UE2和已经与其建立PC5连接的relay D2D UE在当前修改周期之后开始使用新的ProSe D2D UE ID标识信息。
另外，若relay D2D UE接收到remote D2D UE2发送的连接释放指示和/或ID更改指示，则relay D2D UE释放其与remote D2D UE2之间的PC5连接，remote D2D UE2重新发起relay发现/PC5连接建立过程。
实施例四
本实施例描述的是一个relay D2D UE为remote D2D UE分配单播ProSe UE ID的方式下，remote D2D UE的标识与其它D2D UE的UE ID或组ID发生冲突的场景，图11为本实施例场景示意图。如图11所示，D2D UE3(D2D remote UE)通过D2D UE4(relay D2D UE)的中继进行D2D通信。D2D UE1与D2D UE2属于同一个D2D通信组，可进行D2D组通信，D2D UE3(remote D2D UE)不属于该D2D通信组，但D2D UE3可以与D2D UE1或D2D UE2进行一对一D2D发现/通信。假定D2D UE3(remote D2D UE)的单播ProSe UE ID与ProSe通信组(由D2D UE1和D2D UE2组成)的ProSe Layer-2Group ID相同，也即发生ID冲突，则remote D2D UE和该D2D通信组的D2D UE(包含D2D UE1，D2D UE2)都将接收目标ID为该相同ID的MAC PDU。图12为本发明实施例四D2D标识冲突的解决方法流程示意图，如图12所示，本实施例方法包括以下步骤：
步骤121：D2D UE2通过D2D发现过程获得remote D2D UE的单播ProSe UE ID。
UE2通过接收到remote D2D UE发送的D2D发现消息获得relay D2D UE的单播ProSe UE ID。
步骤122：D2D UE2在PC5连接建立过程中获得remote D2D UE的单播ProSe UE ID。
D2D UE2可以通过接收到的remote D2D UE发送的PC5连接建立请求消息获得remote D2D UE的单播ProSe UE ID。或者，D2D UE2可以在与remote D2D UE建立PC5连接后，通过接收remote D2D UE的D2D通信数据包得知remote D2D UE的UE ID。
步骤123：D2D UE2检测到D2D UE3(remote D2D UE)的单播ProSe UE ID与ProSe通信组(由D2D UE1和D2D UE2组成)的ProSe Layer-2Group ID相同，则判定remote D2D UE的UE ID发生了ID冲突。
步骤124：D2D UE2向remote D2D UE发送ID冲突指示信息，用于指示remote D2D UE的ProSe UE ID与其它UE ID或组ID发生冲突。
D2D UE2可通过以下方式向remote D2D UE发送ID冲突指示信息：
1)D2D UE2在与remote D2D UE之间的PC5连接建立完成后，通过单播D2D通信MAC CE向remote D2D UE发送ID冲突指示信息；或者，
2)D2D UE2在与remote D2D UE完成D2D发现之后，通过PC5接口信令向remote D2D UE发送ID冲突指示信息，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令；或者，
3)D2D UE2在与remote D2D UE之间的PC5连接建立完成后，通过单播D2D通信数据包的方式向remote D2D UE发送ID冲突指示信息；或者，
4)D2D UE2通过D2D发现消息向remote D2D UE发送ID冲突指示信息，该D2D发现消息中还包含remote D2D UE的ProSe UE ID。
步骤125：remote D2D UE接收到D2D UE2发送的ID冲突指示信息后，向relay D2D UE发送ID冲突指示信息。
其中，remote D2D UE可通过以下方式向relay D2D UE发送ID冲突指示信息：
1)remote D2D UE在与relay D2D UE之间的PC5连接建立完成后，通过单播D2D通信MAC CE向relay D2D UE发送ID冲突指示信息；或者，
2)remote D2D UE在与relay D2D UE完成relay发现之后，通过PC5接 口信令向relay D2D UE发送ID冲突指示信息，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令。或者，
3)remote D2D UE在与relay D2D UE之间的PC5连接建立完成后，通过单播D2D通信数据包的方式向relay D2D UE发送ID冲突指示信息；或者，
4)remote D2D UE通过D2D发现消息向relay D2D UE发送ID冲突指示信息，该D2D发现消息中还包含remote D2D UE的ProSe UE ID。
步骤126：relay D2D UE为remote D2D UE重新分配ProSe UE ID。
步骤127：relay D2D UE为remote D2D UE重新分配ProSe UE ID后，将remote D2D UE的新的ProSe UE ID发送给remote D2D UE。
relay D2D UE可通过以下方式将remote D2D UE的新的ProSe UE ID发送给remote D2D UE：
1)relay D2D UE通过单播D2D通信MAC CE向已经与其建立PC5连接的remote D2D UE发送重新分配的ProSe UE ID；或者，
2)relay D2D UE通过PC5接口信令向remote D2D UE发送重新分配的ProSe UE ID，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令；或者，
3)relay D2D UE通过单播D2D通信数据包的方式向已经与其建立PC5连接的remote D2D UE发送重新分配的ProSe UE ID；或者，
4)relay D2D UE通过D2D发现消息向remote D2D UE发送重新分配的ProSe UE ID，该D2D发现消息中包含该remote D2D UE的新的ProSe UE ID，或者包含该remote D2D UE的新的和旧的ProSe UE ID。
步骤128：remote D2D UE将自身新的ProSe UE ID发送给已经与其建立PC5连接的D2D UE以及附近的D2D UE。
其中，remote D2D UE可通过以下方式发送ID更改通知信息：
1)remote D2D UE通过单播D2D通信MAC CE向已经与其建立PC5连接的D2D UE发送自身更新的ProSe UE ID；或者，
2)remote D2D UE通过PC5接口信令向已经与其建立PC5连接的D2D UE发送自身更新的ProSe UE ID，其中PC5接口信令可以为PC5连接建立请求消息，或者新增PC5接口信令；或者，
3)remote D2D UE通过单播D2D通信数据包的方式向已经与其建立PC5连接的D2D UE发送自身更新的ProSe UE ID；或者，
4)remote D2D UE通过D2D发现消息向已经与其建立PC5连接的D2D UE或邻近的D2D UE发送自身更新的ProSe UE ID，该D2D发现消息中包含该remote D2D UE的新的ProSe UE ID，或者包含该remote D2D UE的新的和旧的ProSe UE ID。
或者，remote D2D UE将连接释放指示和/或ID更改指示发送给已经与其建立PC5连接的D2D UE。
可选地，若remote D2D UE在蜂窝小区覆盖内，则remote D2D UE获得新的ProSe UE ID后，将新的ProSe UE ID上报给基站，基站接收后存储该remote D2D UE新的ProSe UE ID并更新该D2D UE上下文。
步骤129：已经与remote D2D UE建立PC5连接的D2D UE接收到remote D2D UE发送的更新的ProSe UE ID后，该D2D UE向remote D2D UE发送ID更改通知确认信息。
例如，ID更改通知确认信息可以为以remote D2D UE更新的ProSe UE ID为目标ID的数据包，或者，内容为ID更改通知确认的D2D通信数据包，或者，可通过单播D2D通信MAC CE发送，或者，可通过PC5接口信令发送，或者，可通过D2D发现消息发送。
可选地，D2D UE收到remote D2D UE发送的更新的ProSe UE ID后开始使用更新的ProSe UE ID作为目标ID向remote D2D UE发送D2D通信数据包。而remote D2D UE在接收到D2D UE发送的ID更改通知确认信息后开始使用更新的ProSe UE ID作为源ID向该D2D UE发送D2D通信数据包。或者，remote D2D UE和已经与其建立PC5连接的D2D UE在当前修改周期之后开始使用新的ProSe UE ID标识信息。
另外，若D2D UE接收到remote D2D UE发送的连接释放指示和/或ID 更改指示，则D2D UE释放其与remote D2D UE之间的PC5连接，remote D2D UE重新发起与该D2D UE的D2D发现/PC5连接建立过程。
图13为本发明实施例的D2D UE的结构组成示意图，如图13所述，所述D2D UE包括：
第一判断单元31，设置为：判断所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
第一分配单元32，设置为：当所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，重新为所述D2D UE分配终端标识；
第一发送单元33，设置为：将D2D UE重新分配的终端标识发送给第二D2D UE，所述第二D2D UE为所述D2D UE的邻近D2D UE，或已经与所述D2D UE建立PC5连接的D2D UE。
本发明实施例中，所述第一判断单元31包括：
第一解析子单元311，设置为：当无法解析所接收到的数据包时，则判定所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
第一接收子单元312，设置为：接收到第三D2D UE发送的ID冲突指示信息时，则判定所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，所述第一解析子单元311，设置为：当所述D2D UE的分组数据汇聚协议PDCP层无法解密所接收的数据包；或者，所述D2D UE判断所接收的数据包的目标IP地址与自身IP地址不符；或者，所述D2D UE应用层判断所接收的数据包出错时，则无法解析所接收到的数据包。
本发明实施例中，所述第一接收子单元312，设置为：通过单播D2D通信物理信道MAC CE接收到第三D2D UE发送的ID冲突指示信息；或者，通过PC5接口信令接收到第三D2D UE发送的ID冲突指示信息；或者，通过单播D2D通信数据包接收到第三D2D UE发送的ID冲突指示信息；或者，通过D2D发现消息接收到第三D2D UE发送的ID冲突指示信息。
本发明实施例中，所述D2D UE为远端remote D2D UE或中继relay D2D UE或D2D UE；所述第二D2D UE为remote D2D UE或relay D2D UE或D2D UE；所述第三D2D UE为remote D2D UE或relay D2D UE或D2D UE。
本发明实施例中，所述第一发送单元33，设置为：通过D2D发现消息将D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，通过D2D通信MAC CE将D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，通过PC5接口信令将D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，通过D2D通信数据包将D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE。
本发明实施例中，所述D2D UE还包括：
第二发送单元34，设置为：将所述D2D UE重新分配的终端标识发送给基站，基站接收到所述D2D UE重新分配的终端标识后存储该终端标识并更新至所述D2D UE的上下文信息中。
本发明实施例中，所述第二D2D UE接收到所述D2D UE重新分配的终端标识后，开始使用D2D UE重新分配的终端标识作为目标ID向所述D2D UE发送D2D数据；相应地，
所述D2D UE还包括：
第一接收单元35，设置为：接收所述第二D2D UE发送的以D2D UE重新分配的终端标识作为目标ID的数据包；
第三发送单元36，设置为：使用所述D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据；
或者，所述第二D2D UE接收到D2D UE重新分配的终端标识后，通过D2D通信数据包将终端标识接收确认信息发送给所述D2D UE；
所述D2D UE还包括：
第二接收单元37，设置为：接收所述第二D2D UE发送的终端标识确认信息；
第四发送单元38，设置为：使用所述D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据。
本领域技术人员应当理解，图13所示的D2D UE中的单元的实现功能可参照前述D2D标识冲突的解决方法的相关描述而理解。
图14为本发明另一实施例的D2D UE的结构组成示意图，如图14所示，所述D2D UE包括：
第二判断单元41，设置为：判断所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
第五发送单元42，设置为：当所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，将ID冲突指示信息发送给第五D2D UE，从而所述第五D2D UE为所述D2D UE重新分配终端标识；
第三接收单元43，设置为：接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识。
本发明实施例中，所述第二判断单元41包括：
第二解析子单元411，设置为：当无法解析所接收到的数据包时，则判定所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
第二接收子单元412，设置为：接收到第六D2D UE发送的ID冲突指示信息时，则判定所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
本发明实施例中，所述第二接收子单元412，设置为：通过单播D2D通信MAC CE接收到第六D2D UE发送的ID冲突指示信息；或者，通过PC5接口信令接收到第六D2D UE发送的ID冲突指示信息；或者，通过单播D2D通信数据包接收到第六D2D UE发送的ID冲突指示信息；或者，通过D2D发现消息接收到第六D2D UE发送的ID冲突指示信息。
本发明实施例中，所述第五发送单元42，设置为：通过单播D2D通信MAC CE将ID冲突指示发送给第五D2D UE；或者，通过PC5接口信令将ID 冲突指示发送给第五D2D UE；或者，通过单播D2D通信数据包将ID冲突指示发送给第五D2D UE；或者，通过D2D发现消息将ID冲突指示发送给第五D2D UE。
本发明实施例中，所述第三接收单元43，设置为：通过单播D2D通信MAC CE接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识；或者，通过PC5接口信令接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识；或者，通过单播D2D通信数据包接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识；或者，通过D2D发现消息接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识。
本发明实施例中，所述D2D UE还包括：
第六发送单元44，设置为：将所述D2D UE重新分配的终端标识发送给邻近的D2D UE或已经与所述D2D UE建立连接的D2D UE。
本发明实施例中，所述D2D UE还包括：
第七发送单元45，设置为：将所述D2D UE重新分配的终端标识发送给基站，基站接收所述D2D UE重新分配的终端标识后存储该终端标识，并更新至所述D2D UE的上下文信息中。
本发明实施例中，所述D2D UE为remote D2D UE，所述第五D2D UE为relay D2D UE。
本领域技术人员应当理解，图14所示的D2D UE中的单元的实现功能可参照前述D2D标识冲突的解决方法的相关描述而理解。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述D2D标识冲突的解决方法。
本发明实施例所记载的技术方案之间，在不冲突的情况下，可以任意组合。
在本发明所提供的几个实施例中，应该理解到，所揭露的方法和智能设备，可以通过其它的方式实现。以上所描述的设备实施例仅仅是示意性的， 例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元，即可以位于一个地方，也可以分布到多个网络单元上；可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案的目的。
另外，在本发明实施例中的功能单元可以全部集成在一个其他处理单元中，也可以是每个单元分别单独作为一个单元，也可以两个或两个以上单元集成在一个单元中；上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
以上所述，仅为本发明的实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。
工业实用性
通过本发明实施例，D2D UE能够及时检测到终端标识的冲突并重新获取新的终端标识，保证了D2D通信顺利进行。避免了D2D单播通信的D2D UE的终端标识之间，或D2D单播通信的终端标识与组播通信组的D2D组标识之间的冲突。

Claims (24)

  1. 一种设备到设备标识冲突的解决方法，应用于第一设备到设备用户设备D2D UE，所述方法包括：
    判断所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
    当所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，重新为所述第一D2D UE分配终端标识；
    将第一D2D UE重新分配的终端标识发送给第二D2D UE，所述第二D2D UE为所述第一D2D UE的邻近D2D UE，或已经与所述第一D2D UE建立PC5连接的D2D UE。
  2. 根据权利要求1所述的设备到设备标识冲突的解决方法，其中，所述判断所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突，包括：
    无法解析所接收到的数据包时，则判定所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
    接收到第三D2D UE发送的ID冲突指示信息时，则判定所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
  3. 根据权利要求2所述的设备到设备标识冲突的解决方法，其中，所述无法解析所接收到的数据包，包括：
    所述第一D2D UE的分组数据汇聚协议PDCP层无法解密所接收的数据包；或者，
    所述第一D2D UE判断所接收的数据包的目标IP地址与自身IP地址不符；或者，
    所述第一D2D UE应用层判断所接收的数据包出错。
  4. 根据权利要求2所述的设备到设备标识冲突的解决方法，其中，所 述接收到第三D2D UE发送的ID冲突指示信息，包括：
    通过单播D2D通信物理信道MAC CE接收到第三D2D UE发送的ID冲突指示信息；或者，
    通过PC5接口信令接收到第三D2D UE发送的ID冲突指示信息；或者，
    通过单播D2D通信数据包接收到第三D2D UE发送的ID冲突指示信息；或者，
    通过D2D发现消息接收到第三D2D UE发送的ID冲突指示信息。
  5. 根据权利要求2所述的设备到设备标识冲突的解决方法，其中，所述接收到第三D2D UE发送的ID冲突指示信息之前，所述第三D2D UE检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
  6. 根据权利要求5所述的设备到设备标识冲突的解决方法，其中，所述第三D2D UE检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突，包括：
    所述第三D2D UE通过所接收的第一D2D UE发送的D2D发现消息检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同；或者，
    所述第三D2D UE通过所接收的第一D2D UE发送的PC5接口信令检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同；或者，
    所述第三D2D UE通过所接收的第一D2D UE发送的数据包MAC PDU检测到所述第一D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识相同。
  7. 根据权利要求2至6任一项所述的设备到设备标识冲突的解决方法，其中，
    所述第一D2D UE为远端remote D2D UE或中继relay D2D UE或D2D UE；所述第二D2D UE为remote D2D UE或relay D2D UE或D2D UE；所述第三D2D UE为remote D2D UE或relay D2D UE或D2D UE。
  8. 根据权利要求1所述的设备到设备标识冲突的解决方法，其中，所述将第一D2D UE重新分配的终端标识发送给第二D2D UE，包括：
    通过D2D发现消息将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
    通过D2D通信MAC CE将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
    通过PC5接口信令将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE；或者，
    通过D2D通信数据包将第一D2D UE旧的终端标识和/或重新分配的终端标识和/或连接释放指示和/或ID更改指示发送给第二D2D UE。
  9. 根据权利要求1所述的设备到设备标识冲突的解决方法，其中，所述重新为所述第一D2D UE分配终端标识后，所述方法还包括：
    将所述第一D2D UE重新分配的终端标识发送给基站，基站接收到所述第一D2D UE重新分配的终端标识后存储该终端标识并更新至所述第一D2D UE的上下文信息中。
  10. 根据权利要求1所述的设备到设备标识冲突的解决方法，其中，
    所述第二D2D UE接收到所述第一D2D UE重新分配的终端标识后，开始使用第一D2D UE重新分配的终端标识作为目标ID向所述第一D2D UE发送D2D数据；相应地，
    所述方法还包括：接收到所述第二D2D UE发送的以第一D2D UE重新分配的终端标识作为目标ID的数据包后，开始使用所述第一D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据；
    或者，所述第二D2D UE接收到第一D2D UE重新分配的终端标识后，通过D2D通信数据包将终端标识接收确认信息发送给所述第一D2D UE；相应地，
    所述方法还包括：接收到所述第二D2D UE发送的终端标识确认信息后，开始使用所述第一D2D UE重新分配的终端标识作为源ID向所述第二D2D UE发送D2D数据。
  11. 根据权利要求8所述的设备到设备标识冲突的解决方法，其中，所述第二D2D UE接收到所述第一D2D UE发送的连接释放指示和/或ID更改指示后，释放与所述第一D2D UE之间的PC5连接。
  12. 根据权利要求1所述的设备到设备标识冲突的解决方法，其中，所述将第一D2D UE重新分配的终端标识发送给第二D2D UE后，所述方法还包括：
    所述第一D2D UE和第二D2D UE在当前修改周期之后开始使用重新分配的终端标识进行数据传输；所述第二D2D UE为已经与所述第一D2D UE建立PC5连接的D2D UE；所述修改周期由基站或者ProSe服务器或核心网网元配置。
  13. 一种设备到设备标识冲突的解决方法，应用于第四D2D UE，所述方法包括：
    判断所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
    当所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，将ID冲突指示信息发送给第五D2D UE，从而所述第五D2DUE为所述第四D2D UE重新分配终端标识；
    接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识。
  14. 根据权利要求13所述的设备到设备标识冲突的解决方法，其中，所述判断所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突，包括：
    无法解析所接收到的数据包时，则判定所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；或者，
    接收到第六D2D UE发送的ID冲突指示信息时，则判定所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突；所述ID冲突指示信息用于指示所述第四D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突。
  15. 根据权利要求14所述的设备到设备标识冲突的解决方法，其中，所述接收到第六D2D UE发送的ID冲突指示信息，包括：
    通过单播D2D通信MAC CE接收到第六D2D UE发送的ID冲突指示信息；或者，
    通过PC5接口信令接收到第六D2D UE发送的ID冲突指示信息；或者，
    通过单播D2D通信数据包接收到第六D2D UE发送的ID冲突指示信息；或者，
    通过D2D发现消息接收到第六D2D UE发送的ID冲突指示信息。
  16. 根据权利要求14所述的设备到设备标识冲突的解决方法，其中，所述接收到第六D2D UE发送的ID冲突指示信息之前，所述第六D2D UE检测到第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识发生冲突。
  17. 根据权利要求16所述的设备到设备标识冲突的解决方法，其中，所述第六D2D UE检测到第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识发生冲突，包括：
    所述第六D2D UE通过所接收的第四D2D UE发送的D2D发现消息检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同；或者，
    所述第六D2D UE通过所接收的第四D2D UE发送的PC5接口信令检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同；或者，
    所述第六D2D UE通过所接收的第四D2D UE发送的数据包MAC PDU检测到所述第四D2D UE的终端标识与其它D2D UE的终端标识或D2D组标识相同。
  18. 根据权利要求13所述的设备到设备标识冲突的解决方法，其中，所述将ID冲突指示信息发送给第五D2D UE，包括：
    通过单播D2D通信MAC CE将ID冲突指示发送给第五D2D UE；或者，
    通过PC5接口信令将ID冲突指示发送给第五D2D UE；或者，
    通过单播D2D通信数据包将ID冲突指示发送给第五D2D UE；或者，
    通过D2D发现消息将ID冲突指示发送给第五D2D UE。
  19. 根据权利要求13所述的设备到设备标识冲突的解决方法，其中，所述接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识，包括：
    通过单播D2D通信MAC CE接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
    通过PC5接口信令接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
    通过单播D2D通信数据包接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识；或者，
    通过D2D发现消息接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识。
  20. 根据权利要求13所述的设备到设备标识冲突的解决方法，其中，所述接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识后，所述方法还包括：
    将所述第四D2D UE重新分配的终端标识发送给邻近的D2D UE或已经与所述第四D2D UE建立连接的D2D UE。
  21. 根据权利要求13所述的设备到设备标识冲突的解决方法，其中，所述接收所述第五D2D UE发送的为所述第四D2D UE重新分配的终端标识后，所述方法还包括：
    将所述第四D2D UE重新分配的终端标识发送给基站，基站接收所述第四D2D UE重新分配的终端标识后存储该终端标识，并更新至所述第四D2D UE的上下文信息中。
  22. 根据权利要求13至23任一项所述的设备到设备标识冲突的解决方法，其中，所述第四D2D UE为remote D2D UE，所述第五D2D UE为relay D2D UE。
  23. 一种D2D UE，所述D2D UE包括：
    第一判断单元，设置为：判断所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
    第一分配单元，设置为：当所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，重新为所述D2D UE分配终端标识；
    第一发送单元，设置为：将D2D UE重新分配的终端标识发送给第二D2D UE，所述第二D2D UE为所述D2D UE的邻近D2D UE，或已经与所述D2D UE建立PC5连接的D2D UE。
  24. 一种D2D UE，所述D2D UE包括：
    第二判断单元，设置为：判断所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识是否发生冲突；
    第五发送单元，设置为：当所述D2D UE的终端标识与其他D2D UE的终端标识或D2D组标识发生冲突时，将ID冲突指示信息发送给第五D2D UE，从而所述第五D2D UE为所述D2D UE重新分配终端标识；
    第三接收单元，设置为：接收所述第五D2D UE发送的为所述D2D UE重新分配的终端标识。
PCT/CN2016/085302 2015-08-14 2016-06-08 设备到设备标识冲突的解决方法、设备到设备用户设备 WO2017028610A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16836474.3A EP3337194A4 (en) 2015-08-14 2016-06-08 Device-to-device identification conflict solution method and device-to-device user equipment
US15/752,219 US10484866B2 (en) 2015-08-14 2016-06-08 Device-to-device identification conflict solution method and device-to-device user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510502023.7A CN106470380A (zh) 2015-08-14 2015-08-14 设备到设备标识冲突的解决方法、设备到设备用户设备
CN201510502023.7 2015-08-14

Publications (1)

Publication Number Publication Date
WO2017028610A1 true WO2017028610A1 (zh) 2017-02-23

Family

ID=58050428

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/085302 WO2017028610A1 (zh) 2015-08-14 2016-06-08 设备到设备标识冲突的解决方法、设备到设备用户设备

Country Status (4)

Country Link
US (1) US10484866B2 (zh)
EP (1) EP3337194A4 (zh)
CN (1) CN106470380A (zh)
WO (1) WO2017028610A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109120314A (zh) * 2017-06-23 2019-01-01 华为技术有限公司 一种数据传输方法、通信设备和数据传输系统
US11291059B2 (en) * 2018-08-03 2022-03-29 Telefonaktiebolaget LM Ericsson (Publ) Stockholm, Sweden Methods, user equipment and base station for sidelink identification

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017161570A1 (zh) * 2016-03-25 2017-09-28 华为技术有限公司 一种通信方法、装置和系统
WO2018061760A1 (ja) * 2016-09-30 2018-04-05 京セラ株式会社 無線端末及びネットワーク装置
WO2018157924A1 (en) * 2017-03-01 2018-09-07 Telefonaktiebolaget Lm Ericsson (Publ) D2d communications in a cellular network
CN111586649B (zh) * 2019-02-15 2022-02-01 大唐高鸿智联科技(重庆)有限公司 一种近距离通信用户设备标识的更新方法及用户设备
CN111726770B (zh) * 2019-03-18 2023-09-12 成都华为技术有限公司 通信方法及其装置
US20200322839A1 (en) * 2019-04-05 2020-10-08 Qualcomm Incorporated On-demand relaying of messages for side-link communications
CN111615219B (zh) * 2019-04-30 2022-02-22 维沃移动通信有限公司 一种pc5链路建立方法、设备及系统
US20210315024A1 (en) * 2020-04-06 2021-10-07 Qualcomm Incorporated Indication of resource collisions in sidelink
CN117941381A (zh) * 2021-10-30 2024-04-26 华为技术有限公司 通信方法及装置、存储介质、程序产品
CN116847332A (zh) * 2022-03-25 2023-10-03 维沃移动通信有限公司 远端终端的识别符的分配方法、装置及终端
GB2617614A (en) * 2022-04-14 2023-10-18 Samsung Electronics Co Ltd User equipment identifiers
WO2024065117A1 (zh) * 2022-09-26 2024-04-04 北京小米移动软件有限公司 临时标识调度方法、装置、设备、存储介质与芯片

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1324852C (zh) 2004-05-15 2007-07-04 中兴通讯股份有限公司 一种通讯系统中地址冲突检测方法
KR20130036937A (ko) 2011-10-05 2013-04-15 삼성전자주식회사 멀티 홉 네트워크에서 릴레이 노드가 간섭을 관리하는 방법 및 간섭을 관리하는 릴레이 노드
WO2013163634A1 (en) * 2012-04-27 2013-10-31 Interdigital Patent Holdings, Inc. Systems and methods for personalizing and/or tailoring a service interface
CN103428789B (zh) 2012-05-21 2016-08-10 普天信息技术研究院有限公司 一种中继设备的切换方法
US9084241B2 (en) * 2012-05-21 2015-07-14 Qualcomm Incorporated Methods and apparatus for determining available resources for D2D communications
CN103686740B (zh) 2012-09-03 2016-12-21 华为技术有限公司 一种用户设备标识分配的方法、装置及系统
EP2987361B1 (en) * 2013-05-10 2020-02-26 Huawei Technologies Co., Ltd. System and methods for controlling out-of-network d2d communications
US20150148049A1 (en) * 2013-11-25 2015-05-28 Motorola Mobility Llc Method and apparatus for allocating resources for device-to-device communication
US9699154B2 (en) * 2015-01-19 2017-07-04 Intel IP Corporation Systems, methods and devices for direct communication using a PC5 protocol
EP3627723A1 (en) * 2015-07-24 2020-03-25 Panasonic Intellectual Property Corporation of America Improved prose relay ue activation

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on extended architecture support for proximity-based services (Release 13", 3GPP TR 23.713 VL.5.0, July 2015 (2015-07-01), XP055363617 *
ERICSSON.: "ProSe Group Priorities in Rel-12", 3GPP TSG-RAN WG3 #86 R3-142915, 8 November 2014 (2014-11-08), XP050887201 *
INTEL.: "On ProSe UE ID and ProSe Layer-2 Group ID format (preventing future backwards compatibility issues", SA WG2 MEETING #108 S 2-151051, 7 April 2015 (2015-04-07), XP050962372 *
See also references of EP3337194A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109120314A (zh) * 2017-06-23 2019-01-01 华为技术有限公司 一种数据传输方法、通信设备和数据传输系统
EP3627717A4 (en) * 2017-06-23 2020-07-08 Huawei Technologies Co., Ltd. DATA TRANSMISSION METHOD, COMMUNICATION DEVICE, AND DATA TRANSMISSION SYSTEM
CN109120314B (zh) * 2017-06-23 2021-09-21 华为技术有限公司 一种数据传输方法、通信设备和数据传输系统
US11258541B2 (en) 2017-06-23 2022-02-22 Huawei Technologies Co., Ltd. Data transmission method and device
US11291059B2 (en) * 2018-08-03 2022-03-29 Telefonaktiebolaget LM Ericsson (Publ) Stockholm, Sweden Methods, user equipment and base station for sidelink identification

Also Published As

Publication number Publication date
US10484866B2 (en) 2019-11-19
CN106470380A (zh) 2017-03-01
EP3337194A1 (en) 2018-06-20
US20190007827A1 (en) 2019-01-03
EP3337194A4 (en) 2018-06-20

Similar Documents

Publication Publication Date Title
WO2017028610A1 (zh) 设备到设备标识冲突的解决方法、设备到设备用户设备
CN105992364B (zh) 资源处理方法及装置
CN104812025B (zh) 设备间发现及通信方法和系统
AU2014299437B2 (en) Method and apparatus for performing device-to-device communication
CN104811892B (zh) 一种资源分配方法、装置及系统
CN108307528B (zh) 一种信息传输方法、装置及系统
WO2016161867A1 (zh) 终端直通中继节点的确定、使用方法及装置
WO2016202227A1 (zh) 一种层2链路标识的选择、通知方法及装置
CN111901847A (zh) sidelink中继通信方法、装置、设备及介质
CN106162930B (zh) 在设备直通系统中承载的管理方法和装置
WO2016161764A1 (zh) 一种中继承载控制方法、装置和计算机存储介质
WO2016184370A1 (zh) 更换中继节点的方法及系统、d2d用户设备及控制节点
WO2014161383A1 (zh) 接收设备发现信息、发送设备发现信息的方法和用户设备
WO2015154392A1 (zh) D2d业务的切换实现方法及装置
JP6093037B2 (ja) グループコールコンテキストを確立する方法、システム、基地局、及びクラスタｅｐｃ
JP7544974B2 (ja) リモート端末業務識別方法、装置、機器及び記憶媒体
US20140237125A1 (en) Method, apparatus, and system for establishing device-to-device connection
CN104185299B (zh) 近距离通信方法、用户设备及移动管理实体
WO2016070555A1 (zh) 资源的获取、配置方法及装置，资源池的配置方法及装置
WO2017024909A1 (zh) 一种进行数据传输的方法和设备
WO2018137364A1 (zh) 数据发送方法、数据发送终端以及基站
WO2016173310A1 (zh) 资源的配置方法及装置
JP2023536000A (ja) マルチキャストおよびブロードキャストサービスのための方法および装置
WO2016070601A1 (zh) 设备到设备d2d数据传输方法、装置及d2d ue
WO2016019739A1 (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: 16836474

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016836474

Country of ref document: EP